Stalled deployment while using --edit-placement

[Jeff McLamb]

Hey Mike -

Here is the whole thing:

http://paste.ubuntu.com/12065381/

Here is juju status:

http://paste.ubuntu.com/12065399/

Thanks!

Jeff

On Wed, Aug 12, 2015 at 2:59 PM, Mike McCracken
<mike.mccracken at canonical.com> wrote:
> Hi Jeff, that error from the log is telling you that it tried to find a
> machine in the juju environment that matched the MAAS ID for the machine you
> chose for juju-gui, and it couldn't.
> The installer should take care of adding machines to juju that you choose in
> the placement UI, so this should only happen if there was an error in that
> process, which will be slightly earlier on in the log.
>
> If you'd rather not share the whole log, grep for a log line with "calling
> add_machines with params", and see if there are errors after that. But if I
> could see the whole log, it might be faster. You can mail it to me off list
> if you like.
>
> The output of 'juju status' would be useful here too, to see what it knows
> about double-juice
>
> Thanks,
> -mike
>
> On Wed, Aug 12, 2015 at 10:33 AM, Jeff McLamb <mclamb at gmail.com> wrote:
>>
>> Hey Mike -
>>
>> My juju deployment host is trusty and it is commissioning trusty
>> nodes. I am using openstack kilo via the experimental ppa. Juju is
>> version 1.24.5.
>>
>> The installation line is:
>>
>> $ sudo openstack-install --edit-placement --http-proxy <PROXY>
>> --https-proxy <PROXY> --debug
>>
>> Here is my placements.yaml:
>>
>> http://paste.ubuntu.com/12063466/
>>
>> Here is the relevant portion of commands.log, indicating that the node
>> I selected for juju gui is unsuitable I guess? Like I said, I guess I
>> can understand this, because the machine double-juice (which is a KVM
>> instance that I manually deployed via MAAS) is already deployed (it is
>> the juju deployment machine) and not in a Ready state like all the
>> other machines:
>>
>> http://paste.ubuntu.com/12063514/
>>
>> Thanks,
>>
>> Jeff
>>
>>
>> On Wed, Aug 12, 2015 at 1:12 PM, Mike McCracken
>> <mike.mccracken at canonical.com> wrote:
>> > 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
>> >
>> >
>
>