[RFE] Allow users to run oooq from any host OS, from a container

Bug #1676373 reported by Bogdan Dobrelya on 2017-03-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Wishlist
Bogdan Dobrelya

Bug Description

The usecase:
As a OOOQ user, I want to deploy OOO from the localhost running non centos/rhel 7.x OS type.
I have a centos7 container and ansible inventory, a play file and custom vars [0] to deploy with the oooq off-road (like described in the blog post [1]), which is running ansible-playbook directly. That container wraps the oooq installer and allows it to operate the host's libvirt and kvm. In order to achieve that, a few minor changes required to oooq playbooks.

[0] https://github.com/bogdando/oooq-warp
[1] http://blog.oddbit.com/2016/02/19/deploy-an-ha-openstack-development-envir/

Bogdan Dobrelya (bogdando) wrote :
Changed in tripleo-quickstart:
assignee: nobody → Bogdan Dobrelya (bogdando)
status: New → In Progress
description: updated
Attila Darazs (adarazs) on 2017-03-27
tags: added: ci quickstart
affects: tripleo-quickstart → tripleo
Changed in tripleo:
importance: Undecided → Medium
Bogdan Dobrelya (bogdando) wrote :
Changed in tripleo:
milestone: none → pike-1
Bogdan Dobrelya (bogdando) wrote :

note, I decided to create the bug *after* these patches had been submitted, so there is no link to it so I keep posting "addressed by"...

This is probably more a wishlist than a medium

Changed in tripleo:
milestone: pike-1 → pike-2
summary: - Allow users to run oooq from any host OS, from a container
+ [RFE] Allow users to run oooq from any host OS, from a container
Changed in tripleo:
importance: Medium → Wishlist

Reviewed: https://review.openstack.org/447000
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=a4e1ea67f6900ad69c696812f002d12a8eca45df
Submitter: Jenkins
Branch: master

commit a4e1ea67f6900ad69c696812f002d12a8eca45df
Author: Bogdan Dobrelya <email address hidden>
Date: Fri Mar 17 14:29:08 2017 +0100

    Ignore libvirt start if running chrooted

    The use case is when running oooq from a
    privileged container. For examle, running in
    Centos container on the Ubuntu virthost.
    Services can't be restarted in such a container
    unless you run it as a VM (with init as pid 1).
    So oooq can't pass the libvirt startup task and
    proceed with undercloud deployment. This is
    controlled by a new var 'chrooted'. Defaults to
    False.

    Partial-bug: #1676373
    Change-Id: If221a6a8bda496862da6249c46c2bedd955b6eac
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Reviewed: https://review.openstack.org/447409
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=fdb2d5f142ac1be75da3de7e3ac561af1306fcb9
Submitter: Jenkins
Branch: master

commit fdb2d5f142ac1be75da3de7e3ac561af1306fcb9
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Mar 20 09:20:21 2017 +0100

    Allow custom undercloud initrd/vmlinuz

    Preserve default behavior, which is extract
    those from the overcloud image.

    The example use case is when running oooq from
    a priv container. Like running in Centos container
    on the Ubuntu virthost. The virt-copy-out may be
    working fine on the host OS and failing within the
    container with an error like:
    "'/dev/urandom' is not a supported random source".
    So those images may be prepared as well at the host
    OS and reused as external ones.

    Partial-bug: #1676373
    Change-Id: I19db238b4966a59675e42983daccffe3c437019c
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Reviewed: https://review.openstack.org/453056
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=34bd210a55b50b6d53f2cc47bf89e40f51fa895a
Submitter: Jenkins
Branch: master

commit 34bd210a55b50b6d53f2cc47bf89e40f51fa895a
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Mar 21 22:47:27 2017 +0100

    Instack.json for undercloud VM image

    Do not try to copy the instackenv.json configuration
    file to the undercloud VM image, if it wasn't generated
    in the overcloud setup role.

    This may be the case if there are no overcloud nodes
    defined and the overcloud setup role is missing in
    the play, f.e. the containerized undercloud use case.

    Partial-bug: #1676373
    Change-Id: I7a5a564aacdfa2153ad727baf0b5259cb723ec69
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Changed in tripleo:
status: In Progress → Fix Released

Reviewed: https://review.openstack.org/460122
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=0960fbaa286e99b79c5304fb86f8b2e012e28ecd
Submitter: Jenkins
Branch: master

commit 0960fbaa286e99b79c5304fb86f8b2e012e28ecd
Author: Bogdan Dobrelya <email address hidden>
Date: Wed Apr 26 16:25:06 2017 +0200

    Control injection of instackenv.json

    Allow users to control if instackenv.json must be injected
    for undercloud image or omitted. The latter may be the case
    when installing only a virtual undercloud node w/o overcloud
    nodes at all.

    Related-bug: #1676373

    Change-Id: Iac245daceab01302e7e4cb75458901a0c0af47df
    Signed-off-by: Bogdan Dobrelya <email address hidden>

tags: removed: ci

Reviewed: https://review.openstack.org/552579
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=bdc47b9c1394ef3b8161686ebe07e37c7a7503fe
Submitter: Zuul
Branch: master

commit bdc47b9c1394ef3b8161686ebe07e37c7a7503fe
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Mar 13 17:43:54 2018 +0100

    Add chrooted to the common vars

    When building images from a container, the chrooted option
    needs to be extended for the extras repos as well.
    Make it shared via the common defaults.

    Required-By: Ie880a33fbb758240638178c45c43156e80bf4d24
    Related-Bug: #1676373

    Change-Id: I8cc198bd1081e0c1864228dad6228daa92ac32b7
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Reviewed: https://review.openstack.org/552584
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=d991c1033f3a6390720210d682e3c155959bbe71
Submitter: Zuul
Branch: master

commit d991c1033f3a6390720210d682e3c155959bbe71
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Mar 13 17:47:15 2018 +0100

    Do not attempt install kernel when chrooted

    When building images from a container/chroot, do not
    attempt to install kernels.
    Use the shared via the common defaults chrooted param
    to control that behavior.

    Depends-On: I8cc198bd1081e0c1864228dad6228daa92ac32b7
    Related-Bug: #1676373

    Change-Id: Ie880a33fbb758240638178c45c43156e80bf4d24
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Reviewed: https://review.openstack.org/591770
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=6cc1853da1b34a741d27c728302dcc8242b77bc0
Submitter: Zuul
Branch: master

commit 6cc1853da1b34a741d27c728302dcc8242b77bc0
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Aug 14 16:53:35 2018 +0200

    Do not manage users/groups/services when chrooted

    In containers, users/service management does not (and normally should
    not) work with ansible user/group/service modules, so omit those.

    Related-Bug: #1676373

    Change-Id: If2fe57feb6961e367f4b99b810f87a92f8a7ac7c
    Signed-off-by: Bogdan Dobrelya <email address hidden>

Bogdan Dobrelya (bogdando) wrote :

There is related work to improve quickstart.sh supporting containerized mode, also using local connection transport for virthost. See https://review.openstack.org/#/q/topic:localcon+(status:open+OR+status:merged)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers