I have successfully used the openstack-install on my MAAS server to install the Landscape managed option.
I have successfully configured the Openstack Autopilot beta options in the Landscape web console and run install.
I now have a clean Openstack deployment across my MAAS nodes (6).
I'd like to understand how Openstack services were distributed across my MAAS nodes by Autopoilot.
If on my MAAS server I type:
export JUJU_HOME=~/.cloud-install/juju
juju status
I can see how Landscape itself was deployed into lots of LXC containers on one of the MAAS nodes. What I can't see anywhere is how the Landscape Autopilot tool went on to use juju to deploy Openstack across the other nodes.
I really would like to understand what juju did in order to gain a better understanding of a) what I ended up with and b) how the Ubuntu Openstack reference deployment hangs together. How might I go about doing viewing the "juju status" of the Autopilot outcome?
- The command openstack-install run on the MAAS server offers me three install types for Openstack. I chose the Landscape Autopilot option.
- Having taken this option openstack-install then bootstraps juju to one of my MAAS nodes
- Juju deploys Landscape to a MAAS node. That's the end of it for openstack-install.
- Switching to the Landscape web console and doing the Openstack install initiates another series of juju deployments to fully configure an Openstack cloud. Is the same juju boostrap node used?
– Andrew Love Apr 08 '15 at 09:51