<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi team,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">For reference, below is a summary of the discussions/decisions in Austin design summit. Please feel free to point out if anything is incorrect or incomplete. Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">1. Bay driver: <a href="https://etherpad.openstack.org/p/newton-magnum-bay-driver">
https://etherpad.openstack.org/p/newton-magnum-bay-driver</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">- Refactor existing code into bay drivers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Each bay driver will be versioned<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Individual bay driver can have API extension and magnum CLI could load the extensions dynamically<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Work incrementally and support same API before and after the driver change<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">2. Bay lifecycle operations: <a href="https://etherpad.openstack.org/p/newton-magnum-bays-lifecycle-operations">
https://etherpad.openstack.org/p/newton-magnum-bays-lifecycle-operations</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Support the following operations: reset the bay, rebuild the bay, rotate TLS certificates in the bay, adjust storage of the bay, scale the bay.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">3. Scalability: <a href="https://etherpad.openstack.org/p/newton-magnum-scalability">
https://etherpad.openstack.org/p/newton-magnum-scalability</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Implement Magnum plugin for Rally<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Implement the spec to address the scalability of deploying multiple bays concurrently:
<a href="https://review.openstack.org/#/c/275003/">https://review.openstack.org/#/c/275003/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">4. Container storage: <a href="https://etherpad.openstack.org/p/newton-magnum-container-storage">
https://etherpad.openstack.org/p/newton-magnum-container-storage</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Allow choice of storage driver<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Allow choice of data volume driver<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Work with Kuryr/Fuxi team to have data volume driver available in COEs upstream<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">5. Container network: <a href="https://etherpad.openstack.org/p/newton-magnum-container-network">
https://etherpad.openstack.org/p/newton-magnum-container-network</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Discuss how to scope/pass/store OpenStack credential in bays (needed by Kuryr to communicate with Neutron).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Several options were explored. No perfect solution was identified.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">6. Ironic Integration: <a href="https://etherpad.openstack.org/p/newton-magnum-ironic-integration">
https://etherpad.openstack.org/p/newton-magnum-ironic-integration</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Start the implementation immediately<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Prefer quick work-around for identified issues (cinder volume attachment, variation of number of ports, etc.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">7. Magnum adoption challenges: <a href="https://etherpad.openstack.org/p/newton-magnum-adoption-challenges">
https://etherpad.openstack.org/p/newton-magnum-adoption-challenges</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- The challenges is listed in the etherpad above<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">8. Unified abstraction for COEs:
<a href="https://etherpad.openstack.org/p/newton-magnum-unified-abstraction">https://etherpad.openstack.org/p/newton-magnum-unified-abstraction</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Create a new project for this efforts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Alter Magnum mission statement to clarify its goal (Magnum is not a container service, it is sort of a COE management service)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">9. Magnum Heat template version:
<a href="https://etherpad.openstack.org/p/newton-magnum-heat-template-versioning">
https://etherpad.openstack.org/p/newton-magnum-heat-template-versioning</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- In each bay driver, version the template and template definition.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Bump template version for minor changes, and bump bay driver version for major changes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">10. Monitoring: <a href="https://etherpad.openstack.org/p/newton-magnum-monitoring">
https://etherpad.openstack.org/p/newton-magnum-monitoring</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Add support for sending notifications to Ceilometer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Revisit bay monitoring and self-healing later<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Container monitoring should not be done by Magnum, but it can be done by cAdvisor, Heapster, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">11. Others: <a href="https://etherpad.openstack.org/p/newton-magnum-meetup">
https://etherpad.openstack.org/p/newton-magnum-meetup</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Clear Container support: Clear Container needs to integrate with COEs first. After the integration is done, Magnum team will revisit bringing the Clear Container COE to Magnum.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Enhance mesos bay to DCOS bay: Need to do it step-by-step: First, create a new DCOS bay type. Then, deprecate and delete the mesos bay type.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Start enforcing API deprecation policy:
<a href="https://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html">
https://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Freeze API v1 after some patches are merged.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Multi-tenancy within a bay: not the priority in Newton cycle<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- Manually manage bay nodes (instead of being managed by Heat ResourceGroup): It can address the use case of heterogeneity of bay nodes (i.e. different availability zones, flavors), but need to elaborate the
details further.<o:p></o:p></span></p>
</div>
</body>
</html>