Open Stack

Another option, should the install playbook be enhanced to support simply skipping the steps that wouldn't apply to building in the container?

Seems to me, all the ironic stuff could just be done with the kolla ironic container, so no systemd stuff should be needed.

Thanks,
Kevin
________________________________
From: Mooney, Sean K [sean.k.mooney at intel.com]
Sent: Friday, May 06, 2016 10:14 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [kolla] [bifrost] bifrost container.

Hi everyone.

Following up on my AR from the kolla host repository session
https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kolla-host-repo
I started working on creating a kolla bifrost container.

Are some initial success it have hit a roadblock with the current install playbook provided by bifrost.
In particular the install playbook both installs the ironic dependencies and configure and runs the services.

The installation of ironic and its dependencies would not be a problem but the ansible service module is not cable able of starting the
Infrastructure services (mysql,rabbit …) without a running init system which is not present during the docker build.

When I created a biforst container in the past is spawned a Ubuntu upstart container then docker exec into the container and ran
Bifrost install script. This works because the init system is running and the service module could test and start the relevant services.


This leave me with 3 paths forward.


1.       I can continue to try and make the bifrost install script work with the kolla build system by using sed to modify the install playbook or try start systemd during the docker build.

2.       I can use the kolla build system to build only part of the image

a.        the bifrost-base image would be build with the kolla build system without running the bifrost playbook. This
would allow the existing allow the existing features of the build system such as adding headers/footers to be used.

b.      After the base image is built by kolla I can spawn an instance of bifrost-base with systemd running

c.       I can then connect to this running container and run the bifrost install script unmodified.

d.      Once it is finished I can stop the container and export it to an image “bifros-postinstall”.

e.      This can either be used directly (fat container) or as the base image for other container that run each of the ironic services (thin containers)

3.       I can  skip the kolla build system entirely and create a script/playbook that will build the bifrost container similar to 2.


While option 1 would fully use the kolla build system It is my least favorite as it is both hacky and complicated to make work.
Docker really was not designed to run systemd as part of docker build.

For option 2 and 3 I can provide a single playbook/script that will fully automate the build but the real question I have
Is should I use the kolla build system to make the base image or not.

If anyone else has suggestion on how I can progress  please let me know but currently I am leaning towards option 2.

The only other option I see would be to not use a container and either install biforst on the host or in a vm.
These would essentially be a no op for kolla as we would simply have to document how to install bifrost which is covered
Quite well as part of the bifrost project.

Regards
Sean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160506/caad4b2d/attachment.html>