<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Team,
<div class=""><br class="">
</div>
<div class="">We discussed this in today’s team meeting:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://eavesdrop.openstack.org/meetings/containers/2017/containers.2017-01-03-16.00.html" class="">http://eavesdrop.openstack.org/meetings/containers/2017/containers.2017-01-03-16.00.html</a></div>
<div class=""><br class="">
</div>
<div class="">Our consensus was to start iterating on this in-tree and break it out later into a separate repo once we have reasonably mature drivers, and/or further guidance form the TC about handling drivers.</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Nov 26, 2016, at 11:31 PM, Yatin Karel <<a href="mailto:yatin.karel@nectechnologies.in" class="">yatin.karel@nectechnologies.in</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; direction: ltr; font-family: Tahoma; font-size: 10pt;" class="">
<div style="direction: ltr; font-family: Tahoma; font-size: 10pt;" class="">Hi,
<div class=""><span style="font-size: 13.3333px;" class=""><br class="">
</span></div>
<div style="font-size: 13.3333px;" class=""><span style="font-size: 13.3333px;" class="">As it will helpful in adoption of Magnum so i</span><span style="font-size: 13.3333px;" class="">t's good to seperate drivers somehow and make addition/management of new/current
cluster drivers easier.</span></div>
<div style="font-size: 13.3333px;" class=""><span style="font-size: 13.3333px;" class=""><br class="">
</span></div>
<div style="font-size: 13.3333px;" class=""><span style="font-size: 13.3333px;" class="">From Developer's(refering just Myself) point of view i think current approach is Ok as we can manage everything at one place and from Operator perspective i think it should
be easier to add/disable drivers.</span></div>
<div style="font-size: 13.3333px;" class=""><span style="font-size: 13.3333px;" class="">Keeping above points in mind i think for now we should consider more on current contrib drivers development process, as this will lead to how other drivers would be developed/added
in magnum later on. Currently we have three contrib drivers under development:- k8s_opensuse_v1/dcos_centos_v1/dcos_centos_ironic_v1. So we can target atleast finalizing process for their addition to some extent in this cycle.</span></div>
<div class=""><span style="font-size: 13.3333px;" class=""><br class="">
</span></div>
<div class=""><span style="font-size: 13.3333px;" class="">Should we focus more on adding new contrib drivers now. </span><span style="font-size: 13.3333px;" class=""> </span><span style="font-size: 10pt;" class="">I think Adding new cluster drivers should
be made more easier and independent whether by documenting or by other means. </span><span style="font-size: 13.3333px;" class="">As i</span><span style="font-size: 13.3333px;" class=""> believe disabling can just be done by updating setup.cfg or manum.conf.
May be we can provide some option for disabling drivers without manully updating config/setup files.</span></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><< <span style="font-family: 'Times New Roman'; font-size: 16px;" class="">1. in-tree: remove the entrypoints from magnum/setup.cfg to not install them </span>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">by default. This will require some plumbing to manage them like separate python</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">packages, but allows magnum's development team to manage the official drivers</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">inside the service repo.</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">For this approach, what if we add drivers automatically as it is right now. And update doc for operators who want to disable some/all automatically installed drivers and on how they can
add their custom drivers. I think Murali was working on this(process for adding new contrib drivers) so he might have some idea on this.</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><< 2. separate repo: This option sounds cleaner, but requires more refactoring and</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">will separate more the drivers from service, having significant impact in the</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">development process.</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">Yes, This sounds more cleaner but seems not necessary now.</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">Agree with Ricardo for not moving to this approach now as Drago's concern is also valid and it would be difficult to handle that along with other high priorities tasks in the Ocata Cycle.
So it can be revisited later when we have defined process for new drivers and we have more drivers in-tree.</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class=""><br class="">
</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">Regards</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">Yatin Karel</div>
<div style="font-family: 'Times New Roman'; font-size: 16px;" class="">
<hr tabindex="-1" class="">
<div id="divRpF973796" style="direction: ltr;" class=""><font face="Tahoma" size="2" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>Spyros Trigazis [<a href="mailto:strigazi@gmail.com" class="">strigazi@gmail.com</a>]<br class="">
<b class="">Sent:</b><span class="Apple-converted-space"> </span>Friday, November 18, 2016 8:04 PM<br class="">
<b class="">To:</b><span class="Apple-converted-space"> </span>OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b><span class="Apple-converted-space"> </span>[openstack-dev] [magnum] Managing cluster drivers as individual distro packages<br class="">
</font><br class="">
</div>
<div class=""></div>
<div class="">
<div dir="ltr" class="">Hi all,
<div class=""><br class="">
</div>
<div class="">In magnum, we implement cluster drivers for the different combinations</div>
<div class="">of COEs (Container Orchestration Engines) and Operating Systems. The</div>
<div class="">reasoning behind it is to better encapsulate driver-specific logic and to allow</div>
<div class="">operators deploy custom drivers with their deployment specific changes.</div>
<div class=""><br class="">
</div>
<div class="">For example, operators might want to:</div>
<div class="">* have only custom drivers and not install the upstream ones at all</div>
<div class="">* offer user only some of the available drivers</div>
<div class="">* create different combinations of COE + os_distro</div>
<div class="">* create new experimental/staging drivers </div>
<div class=""><br class="">
</div>
<div class="">It would be reasonable to manage magnum's cluster drivers as different</div>
<div class="">packages, since they are designed to be treated as individual entities. To do</div>
<div class="">so, we have two options:</div>
<div class=""><br class="">
</div>
<div class="">1. in-tree: remove the entrypoints from magnum/setup.cfg to not install them </div>
<div class="">by default. This will require some plumbing to manage them like separate python</div>
<div class="">packages, but allows magnum's development team to manage the official drivers</div>
<div class="">inside the service repo.</div>
<div class=""><br class="">
</div>
<div class="">2. separate repo: This option sounds cleaner, but requires more refactoring and</div>
<div class="">will separate more the drivers from service, having significant impact in the</div>
<div class="">development process.</div>
<div class=""><br class="">
</div>
<div class="">Thoughts?</div>
<div class=""><br class="">
</div>
<div class="">Spyros</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">__________________________________________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">OpenStack
Development Mailing List (not for usage questions)</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Unsubscribe:<span class="Apple-converted-space"> </span></span><a href="mailto:OpenStack-dev-request@lists.openstack.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">OpenStack-dev-request@lists.openstack.org</a><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">?subject:unsubscribe</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>