[13:55] <hazmat> argh.. the state of quantum and openvswitch in precise is rather sad
[14:05] <_mup_> Bug #920000 was filed: 2012-01-22 21:59:44,005 ERROR Failed to launch machine MTMyNzIzOTgxNi44OTA5Nzg5OS43NDY5Mw; attempting to revert. <juju:New> < https://launchpad.net/bugs/920000 >
[15:08] <sara89> ciao
[15:08] <sara89> !list
[17:01] <SpamapS> The SCALE talk went well I think
[17:01] <SpamapS> good questions
[17:01] <SpamapS> lots of interest
[20:03] <pindonga> hi all... juju works against openstack? (ie, can I deploy to openstack instead of ec2?)
[20:39] <SpamapS> pindonga: yes ,using the openstack EC2 api compatibility
[20:40] <SpamapS> pindonga: you will need to set some extra parameters, s3-uri and ec2-uri,
[20:41] <pindonga> SpamapS, I did so, but I get this error: Error Message: The AWS Access Key Id you provided does not exist in our records.
[20:41] <SpamapS> pindonga: http://askubuntu.com/questions/65364/how-can-i-configure-multiple-deployment-environments-for-juju
[20:41] <SpamapS> pindonga: make certain you have changed everything necessary...
[20:46] <pindonga> SpamapS, ah, I was using environment variables for the secrets
[20:47] <pindonga> had to replace them with the real values
[20:47] <pindonga> thx
[21:05] <SpamapS> pindonga: the env vars should still work for the secrets
[23:11] <SpamapS> interesting...
[23:12] <SpamapS> I just now noticed that we don't ever specify AvailabilityZone in juju's ec2 provider .. resulting in random placement
[23:14] <nijaba> SpamapS: random or always East-1 (default)?
[23:15] <SpamapS> random
[23:15] <SpamapS> nijaba: us-east-1 would be the region... then you have 1a, 1b, et
[23:15] <SpamapS> c
[23:18] <SpamapS> nijaba: perhaps the real answer is that 1b has been expanded and so Amazon just started spawning things there