<div dir="ltr">Hongbin, I think the offer to support different OS options is a perfect example both of what we want and what we don't want. We definitely want to allow for someone like yourself to maintain templates for whatever OS they want and to have that option be easily integrated in to a Magnum deployment. However, when developing features or bug fixes, we can't wait for you to have time to add it for whatever OS you are promising to maintain. Instead, we would all be forced to develop the feature for that OS as well. If every member of the team had a special OS like that we'd all have to maintain all of them.<div><br></div><div>Alternatively, what was agreed on by most at the midcycle was that if someone like yourself wanted to support a specific OS option, we would have an easy place for those contributions to go without impacting the rest of the team. The team as a whole would agree to develop all features for at least the reference OS. Then individuals or companies who are passionate about an alternative OS can develop the features for that OS.</div><div><span style="line-height:1.5"><br></span></div><div><span style="line-height:1.5">Corey</span></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Mar 5, 2016 at 12:30 AM Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-CA" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Adrian Otto [mailto:<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a>]
<br>
<b>Sent:</b> March-04-16 6:31 PM</span></p></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
</span></p></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><b>Subject:</b> Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro<u></u><u></u></span></p></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:36.0pt">Steve, <u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Mar 4, 2016, at 2:41 PM, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>> wrote:<u></u><u></u></p>
</div>
</blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.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, March 4, 2016 at 12:48 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] [magnum] Discussion of supporting single/multiple OS distro<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
</div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hongbin,
<u></u><u></u></span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div></div></div></div></blockquote></div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm"><div><div><div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">To be clear, this pursuit is not about what OS options cloud operators can select. We will be offering a method of choice. It has to do with what
we plan to build comprehensive testing for,<span style="color:#1f497d"><u></u><u></u></span></span></p>
</div></div></div></blockquote></div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm"><div><div><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This is easy. Once we build comprehensive tests for the first OS, just re-run it for other OS(s).<u></u><u></u></span></p></div></div></div></blockquote></div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm"><div><div><div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">and the implications that has on our pace of feature development. My guidance here is that we resist the temptation to create a system with more
permutations than we can possibly support. The relation between bay node OS, Heat Template, Heat Template parameters, COE, and COE dependencies (could-init, docker, flannel, etcd, etc.) are multiplicative in nature. From the mid cycle, it was clear to me that:<u></u><u></u></span></p>
</div></div></div></blockquote></div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm"><div><div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">1) We want to test at least one OS per COE from end-to-end with comprehensive functional tests.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">2) We want to offer clear and precise integration points to allow cloud operators to substitute their own OS in place of whatever one is the default
for the given COE.<u></u><u></u></span></p>
</div>
</div></div></blockquote></div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">A COE shouldn’t have a default necessarily that locks out other defaults. Magnum devs are the experts in how these systems operate, and as such
need to take on the responsibility of the implementation for multi-os support.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">3) We want to control the total number of configuration permutations to simplify our efforts as a project. We agreed that gate testing all possible
permutations is intractable.<u></u><u></u></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I disagree with this point, but I don't have the bandwidth available to prove it ;) <u></u><u></u></span></p>
</div>
</div></div></blockquote></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt">That’s exactly my point. It takes a chunk of human bandwidth to carry that responsibility. If we had a system engineer assigned from each of the various upstream OS distros working with Magnum, this would not
be a big deal. Expecting our current contributors to support a variety of OS variants is not realistic.<span style="color:#1f497d"><u></u><u></u></span></p>
</div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">You have my promise to support an additional OS for 1 or 2 popular COEs.<u></u><u></u></span></p></div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:36.0pt">Change velocity among all the components we rely on has been very high. We see some of our best contributors frequently sidetracked in the details of the distros releasing versions of code that won’t work with
ours. We want to upgrade a component to add a new feature, but struggle to because the new release of the distro that offers that component is otherwise incompatible. Multiply this by more distros, and we expect a real problem.<u></u><u></u></p>
</div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">At Magnum upstream, the overhead doesn’t seem to come from the OS. Perhaps, that is specific to your downstream?<u></u><u></u></span></p>
</div></div></div></div><div lang="EN-CA" link="blue" vlink="purple"><div><div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><br>
<br>
<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">There is no harm if you have 30 gates running the various combinations. Infrastructure can handle the load. Whether devs have the cycles to make
a fully bulletproof gate is the question I think you answered with the word intractable.<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt">Actually, our existing gate tests are really stressing out our CI infra. At least one of the new infrastructure providers that replaced HP have equipment that runs considerably slower. For example, our swam functional
gate now frequently fails because it can’t finish before the allowed time limit of 2 hours where it could finish substantially faster before. If we expanded the workload considerably, we might quickly work to the detriment of other projects by perpetually
clogging the CI pipelines. We want to be a good citizen of the openstack CI community. Testing configuration of third party software should be done with third party CI setups. That’s one of the reasons those exist. Ideally, each would be maintained by those
who have a strategic (commercial?) interest in support for that particular OS.<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I can tell you in Kolla we spend a lot of cycles just getting basic gating going of building containers and then deploying them. We have even
made inroads into testing the deployment. We do CentOS, Ubuntu, and soon Oracle Linux, for both source and binary and build and deploy. Lots of gates and if they aren't green we know the patch is wrong.<u></u><u></u></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt">Remember that COE’s are tested on nova instances within heat stacks. Starting lots of nova instances within devstack in the gates is problematic. We are looking into using a libvirt-lxc instance type from nova
instead of a libvirt-kvm instance to help alleviate this. Until then, limiting the scope of our gate tests is appropriate. We will continue our efforts to make them reasonably efficient.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Adrian<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">-steve<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Note that it will take a thoughtful approach (subject to discussion) to balance these interests. Please take a moment to review the interest above.
Do you or others disagree with these? If so, why?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Adrian<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">On Mar 4, 2016, at 9:09 AM, Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com" target="_blank">hongbin.lu@huawei.com</a>> wrote:<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I don’t think there is any consensus on supporting single distro. There are multiple disagreements on this thread, including several
senior team members and a project co-founder. This topic should be re-discussed (possibly at the design summit).</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hongbin</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Corey
O'Brien [<a href="mailto:coreypobrien@gmail.com" target="_blank">mailto:coreypobrien@gmail.com</a>]<span> </span><br>
<b>Sent:</b><span> </span>March-04-16 11:37 AM<br>
<b>To:</b><span> </span>OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b><span> </span>Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">I don't think anyone is saying that code should somehow block support for multiple distros. The discussion at midcycle was about what the we should gate on and ensure feature parity for as a team. Ideally, we'd
like to get support for every distro, I think, but no one wants to have that many gates. Instead, the consensus at the midcycle was to have 1 reference distro for each COE, gate on those and develop features there, and then have any other distros be maintained
by those in the community that are passionate about them.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">The issue also isn't about how difficult or not it is. The problem we want to avoid is spending precious time guaranteeing that new features and bug fixes make it through multiple distros. <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Corey<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"> <u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Fri, Mar 4, 2016 at 11:18 AM Steven Dake (stdake) <<a href="mailto:stdake@cisco.com" target="_blank"><span style="color:purple">stdake@cisco.com</span></a>> wrote:<u></u><u></u></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">My position on this is simple.</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Operators are used to using specific distros because that is what they used in the 90s,and the 00s, and the 10s. Yes, 25 years of using a distro,
and you learn it inside and out. This means you don't want to relearn a new distro, especially if your an RPM user going to DEB or a DEB user going to RPM. These are non-starter options for operators, and as a result, mean that distro choice is a must.
Since CoreOS is a new OS in the marketplace, it may make sense to consider placing it in "third" position in terms of support.</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Besides that problem, various distribution companies will only support distros running in Vms if it matches the host kernel, which makes total
sense to me. This means on an Ubuntu host if I want support I need to run Ubuntu vms, on a RHEL host I want to run RHEL vms, because, hey, I want my issues supported.</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">For these reasons and these reasons alone, there is no good rationale to remove multi-distro support from Magnum. All I've heard in this thread
so far is "its too hard". Its not too hard, especially with Heat conditionals making their way into Mitaka.</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Regards</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">-steve</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:<span> </span></span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com" target="_blank"><span style="color:purple">hongbin.lu@huawei.com</span></a>><br>
<b>Reply-To:<span> </span></b>"<a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="color:purple">openstack-dev@lists.openstack.org</span></a>" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="color:purple">openstack-dev@lists.openstack.org</span></a>><br>
<b>Date:<span> </span></b>Monday, February 29, 2016 at 9:40 AM<br>
<b>To:<span> </span></b>"<a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="color:purple">openstack-dev@lists.openstack.org</span></a>" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><span style="color:purple">openstack-dev@lists.openstack.org</span></a>><br>
<b>Subject:<span> </span></b>[openstack-dev] [magnum] Discussion of supporting single/multiple OS distro</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">Hi team,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">This is a continued discussion from a review [1]. Corey O'Brien suggested to have Magnum support a single OS distro (Atomic). I disagreed. I think we should bring the discussion to
here to get broader set of inputs.<span> </span></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Corey O'Brien</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>From the midcycle, we decided we weren't going to continue to support 2 different versions of the k8s template. Instead, we were going to maintain the Fedora Atomic version of k8s and remove the coreos templates
from the tree. I don't think we should continue to develop features for coreos k8s if that is true.</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>In addition, I don't think we should break the coreos template by adding the trust token as a heat parameter.</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i> </i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Hongbin Lu</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>I was on the midcycle and I don't remember any decision to remove CoreOS support. Why you want to remove CoreOS templates from the tree. Please note that this is a very big decision and please discuss it with
the team thoughtfully and make sure everyone agree.</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i> </i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Corey O'Brien</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Removing the coreos templates was a part of the COE drivers decision. Since each COE driver will only support 1 distro+version+coe we discussed which ones to support in tree. The decision was that instead of
trying to support every distro and every version for every coe, the magnum tree would only have support for 1 version of 1 distro for each of the 3 COEs (swarm/docker/mesos). Since we already are going to support Atomic for swarm, removing coreos and keeping
Atomic for kubernetes was the favored choice.</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i> </i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Hongbin Lu</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Strongly disagree. It is a huge risk to support a single distro. The selected distro could die in the future. Who knows. Why make Magnum take this huge risk? Again, the decision of supporting single distro
is a very big decision. Please bring it up to the team and have it discuss thoughtfully before making any decision. Also, Magnum doesn't have to support every distro and every version for every coe, but should support *more than one* popular distro for some
COEs (especially for the popular COEs).</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i> </i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Corey O'Brien</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>The discussion at the midcycle started from the idea of adding support for RHEL and CentOS. We all discussed and decided that we wouldn't try to support everything in tree. Magnum would provide support in-tree
for 1 per COE and the COE driver interface would allow others to add support for their preferred distro out of tree.</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i> </i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>Hongbin Lu</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i>I agreed the part that "we wouldn't try to support everything in tree". That doesn't imply the decision to support single distro. Again, support single distro is a huge risk. Why make Magnum take this huge
risk?</i><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">[1]<span> </span><a href="https://review.openstack.org/#/c/277284/" target="_blank"><span style="color:purple">https://review.openstack.org/#/c/277284/</span></a></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">Best regards,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">Hongbin</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<span> </span><a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank"><span style="color:purple">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</span></a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><span style="color:purple">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span></a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u><u></u></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><u></u> <u></u></p>
</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>