Stalled deployment while using --edit-placement

[Jeff McLamb]

Hi everyone,

I am playing around with openstack-installer using --edit-placement to
manually assign services to my 4 physical nodes.

Due to having only 4 nodes, I have to use several servers as
multi-use. My first question is, are there any functional limitations
on using nodes with multiple services? Will openstack-installer detect
this if there are? I realize that for performance reasons it might not
make sense, but right now I just want to get a working setup with what
I have.

I am trying to deploy 2 bare metal compute nodes, 2 bare metal Ceph
nodes (shared across compute), 1 bare metal Ceph OSD (shared on one of
the compute nodes). Most of the required controller-like services are
in LXC containers on a single node. Neutron services are in LXC
containers on another node.

I also chose to install Juju-GUI in a container on the Juju deployment
node, which itself is a manually deployed KVM node hosted on the MAAS
server, managed by MAAS.

Using the latest installer, deployment has stalled during Juju GUI. It
successfully deployed Keystone, MySQL, NTP to containers, but has been
sitting at Juju GUI. I am suspicious that this is because the chosen
node is one that Juju is not deploying itself?

Is there any way to (A)dd Services and remove Juju GUI during this
stage? I tried to do that, but Remove does not seem to register
anything. And juju-gui does not yet appear in `juju status` so I can't
remove it that way either.

Basically, I'd like to move along with the deployment and forgo Juju
GUI for now, but I can't figure out how to tell it to skip over this
part of the deployment.

Thanks,

Jeff