<div dir="ltr">Hi folks,<div><br></div><div><span style="line-height:1.5">It's a shame that etherpad was down during the </span><span style="line-height:1.5">ODS kolla/bifrost</span><span style="line-height:1.5"> session. </span><span style="line-height:1.5">My recollection is that we agreed *not* to re-invent it Bifrost in containers, but to just stick with running it in a VM (as it is today) because that is the quickest path, and allows the Kolla community to leverage the work that the Ironic/Bifrost community is already doing.</span></div><div><br></div><div>I'd like to respond to several of the emails in this thread and, hopefully, clear up some misunderstandings. Pardon the coming series of responses, but it's easier than trying to respond to one email.</div><div><br></div><div><br></div><div>--Deva</div><div><br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, May 9, 2016 at 11:06 AM Mooney, Sean K <<a href="mailto:sean.k.mooney@intel.com" target="_blank">sean.k.mooney@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Hi <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">If we choose to use bifrost to deploy ironic standalone I think combining kevins previous<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">suggestion of modifying the bifrost install playbook with Steve Dake’s suggestion of creating a series
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">of supervisord configs for running each of the service is a reasonable approch.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">I am currently look to scope how much effort would be required to split the main task in the bifrost-ironic-install role
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><a href="https://github.com/openstack/bifrost/blob/master/playbooks/roles/bifrost-ironic-install/tasks/main.yml" target="_blank">https://github.com/openstack/bifrost/blob/master/playbooks/roles/bifrost-ironic-install/tasks/main.yml</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">into 3 files which would be included in the main.yml:<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:36pt"><span style="color:rgb(31,73,125)">Install_componets.yml (executed when skip_install is not defiend)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:36pt"><span style="color:rgb(31,73,125)">Bootstrap_components.yml (executed when skip_bootstrap is not defiend)<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:36pt"><span style="color:rgb(31,73,125)">Start_components.yml (executed when skip_start is not defiend)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">By default all three would be executed maintain the current behavior of bifrost today,.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">During the kolla build of the biforst image the
<a href="https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml" target="_blank">
https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml</a> would be in<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">run with skip_bootstrap and skip_start defined as true so only Install_componets.yml will be executed by the main task.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">This would install all software components of bifrost/ironic without preforming configuration or starting the services.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">At deployment time during the bootstrap phase we would spawn an instance of the biforst-base container and invoke
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><a href="https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml" target="_blank">https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml</a> with skip_install and skip_start defined executing
Bootstrap_components.yml<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Bootstrap_components.yml would encapsulate all logic related to creating the ironic db(running migration scripts) and generating the configuration
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Files for the biforst components.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Finally in the start phase we have 3 options<u></u><u></u></span></p>
<p><u></u><span style="color:rgb(31,73,125)"><span>a)<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="color:rgb(31,73,125)">Spawn an instance of the bifrost-supervisor container and use supervisord to run the bifrost/ironic services (fat container)<u></u><u></u></span></p>
<p><u></u><span style="color:rgb(31,73,125)"><span>b)<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="color:rgb(31,73,125)">Spawn an instance of the bifrost-base container and Invoke
<a href="https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml" target="_blank">
https://github.com/openstack/bifrost/blob/master/playbooks/install.yaml</a> with <br>
skip_install and skip_bootstrap and allow biforst to star the services.(fat container)<u></u><u></u></span></p>
<p><u></u><span style="color:rgb(31,73,125)"><span>c)<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="color:rgb(31,73,125)">Spawn a series of containers each running a single service sharing the required volumes to allow them to communicate (app containers)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">I would welcome any input for the bifrost community on this especially related to the decomposition of the main.yml into 3 phases.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Im hoping to do a quick poc this week to see how easy it is to do this decomposition.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">I would also like to call out upfront that depending on the scope of this item I may have to withdraw from contributing to it.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">I work in intel’s network platforms group so enabling baremetal installation is somewhat outside the standard<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Work our division undertakes. If we can reuse bifrost to do most of the heavy lifting of creating the bifrost container and deploying ironic then<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">The scope of creating the bifrost container is small enough that I can justify spending some of my time working on it. if it requires<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Significant changes to bifrost or rework of kolla’s ironic support then I will have to step back and focus more on feature that are closer aligned to<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Our teams core networking and orchestration focus such as enhancing kolla to be able to deploy ovs with dpdk and/or opendaylight which are<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Also items I would like to contribute to this cycle. I don’t want to commit to delivering this feature unless I know I will have the time to work on<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">It but am happy to help where I can.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">@kevin some replies to your questions inline.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Sean.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Fox, Kevin M [mailto:<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>] <br>
<b>Sent:</b> Friday, May 6, 2016 9:17 PM</p></div></div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0cm 0cm"><p class="MsoNormal"><br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Subject:</b> Re: [openstack-dev] [kolla] [bifrost] bifrost container.<u></u><u></u></p></div></div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0cm 0cm"><p class="MsoNormal"></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black">I was under the impression bifrost was 2 things, one, an installer/configurator of ironic in a stand alone mode, and two, a management tool for getting machines
deployed without needing nova using ironic.</span><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] yes this is correct, bifrost does provide both install playbooks for deploying ironic in standalone mode and a series of playbooks for dynamically enrolling node in ironic and dynamically
deploy imanges to host<u></u><u></u></span></i></b></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">Without requiring nova. Bifrost also provides intergration with Disk image builder to generate machine images if desired.<u></u><u></u></span></i></b></p></div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"><br>
<br>
The first use case seems like it should just be handled by enhancing kolla's ironic container stuff to directly to handle the use case, doing things the kolla way. This seems much cleaner to me. Doing it at runtime looses most of the benefits of doing it in
a container at all.</span><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] I was not suggestiong doing the installation at runtime. Option 2 and 3 suggested spawning a container as part of the build in which the install playbook would be run.<u></u><u></u></span></i></b></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">That container would then be stopped and exported to form the base image for the bifrost continer(s). The base image (bifrost-postinstall) would either be use to create a fat containter using an init
system such as supervisord to run each of the services<u></u><u></u></span></i></b></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">or be used as the base image for a set of bifrost container each of which ran a single component.
<u></u><u></u></span></i></b></p></div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"><br>
<br>
The second adds a lot of value I think, and thats what the bifrost container should be?</span><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] yes it does and I think it can be reused regarless or how we decide to deploy ironic.<u></u><u></u></span></i></b></p></div></div></div></div><div lang="EN-US" link="#0563C1" vlink="#954F72"><div><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt"><div>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)"><u></u> <u></u></span></i></b></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"><br>
<br>
Thanks,<br>
Kevin<u></u><u></u></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12pt;font-family:'Times New Roman',serif;color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"> Mooney, Sean K [<a href="mailto:sean.k.mooney@intel.com" target="_blank">sean.k.mooney@intel.com</a>]<br>
<b>Sent:</b> Friday, May 06, 2016 12:54 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [kolla] [bifrost] bifrost container.</span><span style="font-size:12pt;font-family:'Times New Roman',serif;color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Steven Dake (stdake) [<a href="mailto:stdake@cisco.com" target="_blank">mailto:stdake@cisco.com</a>]
<br>
<b>Sent:</b> Friday, May 6, 2016 6:56 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Subject:</b> Re: [openstack-dev] [kolla] [bifrost] bifrost container.<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Sean,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Thanks for taking this on :) I didn't know you had such an AR :)</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] well if other want to do the work that ok with me too but I was planning on deploying bifrost
</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">At home again anyway so I taught I might as well try to automate the process while im at it.</span></i></b><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">"Mooney, Sean K" <<a href="mailto:sean.k.mooney@intel.com" target="_blank">sean.k.mooney@intel.com</a>><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Date: </b>Friday, May 6, 2016 at 10:14 AM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Subject: </b>[openstack-dev] [kolla] [bifrost] bifrost container.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0cm 0cm 0cm 4pt;margin:5pt 0cm 5pt 3.75pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black">Hi everyone.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Following up on my AR from the kolla host repository session<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"><a href="https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kolla-host-repo" target="_blank">https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kolla-host-repo</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">I started working on creating a kolla bifrost container.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Are some initial success it have hit a roadblock with the current install playbook provided by bifrost.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">In particular the install playbook both installs the ironic dependencies and configure and runs the services.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">What I'd do here is ignore the install playbook and duplicate what it installs. We don't want to install at run time, we want to install at build time. You weren't clear if that is what your
doing.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] that is certainly an option but bifrost is an installer for ironic and its supporting service. Not using its installation scripts significantly reduces the value of
</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">Integrating with bifrost vs fixing the existing ironic support in kolla and using that to provision the undercloud.
</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">The reason we would ignore the install playbook is because it runs the services. We need to run the services in a different way. This will (as we discussed at ODS) be a fat container on the underlord
cloud – which I guess is ok. I'd recommend not using systemd, as that will break systemd systems badly. Instead use a different init system, such as supervisord.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] if we don’t use the bifrost install playbook then yes supervisord would be a good choice for the init system.
</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">Looking at the official centos docker image
<a href="https://hub.docker.com/_/centos/" target="_blank">https://hub.docker.com/_/centos/</a> they do provided instruction for running systemd containers tough I have had issues with this in the past.</span></i></b><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0cm 0cm 0cm 4pt;margin:5pt 0cm 5pt 3.75pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black">The installation of ironic and its dependencies would not be a problem but the ansible service module is not cable able of starting the<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Infrastructure services (mysql,rabbit …) without a running init system which is not present during the docker build.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">When I created a biforst container in the past is spawned a Ubuntu upstart container then docker exec into the container and ran<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Bifrost install script. This works because the init system is running and the service module could test and start the relevant services.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">This leave me with 3 paths forward.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p><span style="color:black">1.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">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.<u></u><u></u></span></p>
<p><span style="color:black">2.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">I can use the kolla build system to build only part of the image<u></u><u></u></span></p>
<p style="margin-left:72pt"><span style="color:black">a.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black"> the bifrost-base image would be build with the kolla build system without running the bifrost playbook. This<br>
would allow the existing allow the existing features of the build system such as adding headers/footers to be used.<u></u><u></u></span></p>
<p style="margin-left:72pt"><span style="color:black">b.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">After the base image is built by kolla I can spawn an instance of bifrost-base with systemd running
<u></u><u></u></span></p>
<p style="margin-left:72pt"><span style="color:black">c.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">I can then connect to this running container and run the bifrost install script unmodified.<u></u><u></u></span></p>
<p style="margin-left:72pt"><span style="color:black">d.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">Once it is finished I can stop the container and export it to an image “bifros-postinstall”.
<u></u><u></u></span></p>
<p style="margin-left:72pt"><span style="color:black">e.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">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)<u></u><u></u></span></p>
<p><span style="color:black">3.</span><span style="font-size:7pt;font-family:'Times New Roman',serif;color:black">
</span><span style="color:black">I can skip the kolla build system entirely and create a script/playbook that will build the bifrost container similar to 2.<u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">4.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Make a supervisord set of init scripts and make the docker file do what it was intended – install the files. This is kind of a mashup of your 1-3 ideas. Good thinking :)</span><span style="color:black"><u></u><u></u></span></p>
</div>
<blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0cm 0cm 0cm 4pt;margin:5pt 0cm 5pt 3.75pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">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.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Docker really was not designed to run systemd as part of docker build.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">For option 2 and 3 I can provide a single playbook/script that will fully automate the build but the real question I have<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Is should I use the kolla build system to make the base image or not.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">If anyone else has suggestion on how I can progress please let me know but currently I am leaning towards option 2.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">If you have questions about my suggestion to use supervisord, hit me up on IRC. Ideally we would also contribute these init scripts back into bifrost code base assuming they want them, which I
think they would. Nobody will run systemd in a container, and we all have an interest in seeing BiFrost as the standard bare metal deployment model inside or outside of containers.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] I have briefly used supervisord before for a pet project
<a href="https://github.com/SeanMooney/docker-devstack" target="_blank">https://github.com/SeanMooney/docker-devstack</a> to create a container for running devstack so it did hot pollute my host.</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">supervisord is a nice tool. Im just about to head home for the weekend but I might grab you on irc on Monday to follow up.</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Regards</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">-steve</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0cm 0cm 0cm 4pt;margin:5pt 0cm 5pt 3.75pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black">The only other option I see would be to not use a container and either install biforst on the host or in a vm.<u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">GROAN – one advantage containers provide us is not mucking up the host OS with a bajillion dependencies. I'd like to keep that part of Kolla intact :)</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">[Mooney, Sean K] yes I would prefer not to break that too. This was basically the option of we don’t actually do the integration and instead just tell</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">The user how to use bifrost to do the deployment but leave it up to them do decide how to install it. so for me that was plan Z so we have a couple of letter</span></i></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><i><span style="color:rgb(31,73,125)">Go through first.</span></i></b><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0cm 0cm 0cm 4pt;margin:5pt 0cm 5pt 3.75pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black">These would essentially be a no op for kolla as we would simply have to document how to install bifrost which is covered<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Quite well as part of the bifrost project.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Regards<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Sean.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div></div></div></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>