Deployment of a large bundle fails or hoggs the system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hello there,
When i try to deploy a large bundle with several LXD containers the deployment is take very long, and seems to hogg/stall for some reason i couldn't find in the logs.
My base bundle is the openstack-base bundle file, and i added HA via hacluster with 3 units.
In this setup there are a total of 9 machines, 3 neutron-gateway / services nodes and 6 compute nodes.
I install all the services like cinder, glance etc.. in a container on the neutron-gateway nodes. On the nova-compute nodes also function as a ceph-osd, but the ceph-mon's are installed on the neutron-gateway.
Now if i tell the bundle to deploy 3 units of all these services using hacluster as a sub-charm the installation will fail, seems like juju/bootstrap isn't responding or isn't telling what to do to the clients, or clients can't connect to the bootstrap, i couldn't figure that out.
If i tell the bundle to first deploy just one of those services, and after a good deployment i tell all those services to add 2 more unit's it works fine. But not at all at the same time.
Is it an option to let the juju deploy function hold all extra unit's of a specific app and let it deploy once the first one is running?
If i'm correct the juju-deployer for 1.2x did something like this?
ps. i'm not able to test this much (or not even at all any more) on these systems, since they are in use a.t.m.
Any questions just ask :).
Thx.
@Fairbanks,
Could you please clarify what Juju 2.x and openstack versions you were using?
Also, we track Juju 2.x issues in "juju" project in launchpad.
I'll re-target :)