On 12/06/2012, at 3:50 AM, Steve Linabery wrote:
Been trying these out all day. configure and conductor both seem "ok" enough
to
release. Haven't tried cli stuff yet.
Points worth noting:
+ deltacloud-core is consistently segfaulting at startup, but runs fine when
the service is manually restarted afterwards. (obviously not a problem
with the above rpms per se, but good to be aware of when testing)
+ Launching instances in oVirt and EC2 goes fine. Definitely usable.
+ Finally worked out the cause of launch failures for VMware.
... having spaces in instances names. (will file a BZ in a minute)
ie "Instance E" fails at launch, whereas "InstanceE" works.
Sounds like a string sanitisation problem to me. Extract from the
dbomatic log:
2012-06-12 19:51:40 INFO Deltacloud refresh started
2012-06-12 19:51:40 INFO Deltacloud instances refresh started
2012-06-12 19:51:41 WARN caught deltacloud exception bad URI(is not URI?):
http://localhost:3002/api/instances/Instance E-F16-vmware when updating instance Instance
E/F16-vmware
2012-06-12 19:51:41 INFO known instance missing from provider: Instance E/F16-vmware
Instance E-F16-vmware
2012-06-12 19:51:48 INFO updating instance state for InstanceD/F16-vmware:
InstanceD-F16-vmware
2012-06-12 19:51:54 INFO updating instance state for InstanceC/F16-vmware:
InstanceC-F16-vmware
2012-06-12 19:51:54 INFO Deltacloud instances refresh completed
2012-06-12 19:51:54 INFO Deltacloud refresh completed
Not a blocker IMHO, as we can just tell people not to use spaces in their
instance names for now (and that its a temp measure, should be fixed by
next release).
From my point of view, this will be workable as a stable release.
i.e. lets get release notes written up, screenshots done, updated install
instructions, etc.
How's that all sound to you?
+ Justin
--
Aeolus Community Manager
http://www.aeolusproject.org