Stalled deployment while using --edit-placement

[Mike McCracken]

Hi Jeff, I'll try to answer inline.

In general, it's helpful to know which ubuntu release you're working with
and what openstack release you're trying to install, as the installer does
try to support a few combinations.
If you don't specify a release, the current default is kilo.

Also, are you using the installer from the 'testing' PPA or the newer
'experimental' one?
If you are using the testing PPA, then switching to the newer one may fix
your bug:

$ sudo apt-add-repository ppa:cloud-installer/experimental
$ sudo apt-get update
$ sudo apt-get install openstack


On Wed, Aug 12, 2015 at 9:37 AM, Jeff McLamb <mclamb at gmail.com> wrote:

> 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.
>

There are some limitations, and the installer does try not to let you do
some things that will break, but it can't guarantee a working setup. In
particular, nova-compute and quantum/neutron need to be deployed onto bare
metal or KVM, not LXC, IIRC because of how they interact with the host
kernel.


> 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.
>

The installer shouldn't allow placing neutron in a container. Can you send
along the contents of ~/.cloud-install/placements.yaml so we can see how
the services are laid out?

Also, if you could include the log at ~/.cloud-install/commands.log, we can
look there for errors explaining why it's hanging at juju gui.

In general if you don't want the juju gui, you can skip it, either just not
placing it or removing it from the default placement.
It's not necessary for the operation of any other services.

Thanks,
-mike


> 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
>
> --
> ubuntu-openstack-installer mailing list
> ubuntu-openstack-installer at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-openstack-installer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-openstack-installer/attachments/20150812/19486c72/attachment.html>