<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div><font color="#1F497D">Folks:</font></div>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">I captured notes from this morning’s presentation:</font></div>
<div><font color="#1F497D"> </font></div>
<ul style="margin:0;padding-left:18pt;">
<font color="#1F497D">
<li>Brent presented this chart package for Containerization of StarlingX Infrastructure: <a href="https://wiki.openstack.org/wiki/Containerizing_StarlingX_Infrastructure"><font color="#0563C1"><u>https://wiki.openstack.org/wiki/Containerizing_StarlingX_Infrastructure</u></font></a>
</li><li>Some questions/answers that came up during the presentation:</li></font>
</ul>
<ul style="margin:0;padding-left:54pt;">
<font color="#1F497D">
<li>Which configs will move to this containerized infrastructure? Answer: All configs will get the containerized configuration.</li><li>For 1 and 2 node configurations, CEPH will run on the controllers.</li><li>Where will RBD provisioner run? Answer: it will run in the cube space.</li><li>If trying to run an application, where will it run? Will it be possible to run apps in containers? Answer: Yes (Some limitations: eg: no high performance networking, multi-tenant limitation)</li><li>Containerized OpenStack services will require us to build our own docker images and those images will be CentOS based.</li><li>Can we generate these docker images using other O/S’s? Answer: This will be a design consideration.</li><li>Will it be possible to put docker images on docker hub? Answer: Where to put the images will be looked at as part of one of the StoryBoards for this initiative.</li><li>Does the customer network share the same physical network with cluster? Answer: Networks may be physically the same but a different logical network will be used for the cluster.</li><li>Will software update change? Answer: Yes - we will be moving toward a k8s approach to update software/containers.</li><li>Can you provide some schedule info? Answer: Target is for the March release. Specs are expected to be out in the next 1-2 weeks.</li><li>If community folks are interested in participating please contact Brent or Frank.</li><li>In future, to containerize the flock will the decoupling of the flock need to be completed? Answer: No – there is no direct dependency on the decoupling work.</li></font>
</ul>
<div><font color="#1F497D"> </font></div>
<div><font color="#1F497D">Frank</font></div>
<div><font color="#1F497D"> </font></div>
<a name="_MailEndCompose"></a>
<div><font color="#1F497D"> </font></div>
<div>-----Original Appointment-----<br>
<b>From:</b> Rowsell, Brent [<a href="mailto:Brent.Rowsell@windriver.com">mailto:Brent.Rowsell@windriver.com</a>]
<br>
<b>Sent:</b> Saturday, September 29, 2018 10:38 AM<br>
<b>To:</b> Rowsell, Brent; starlingx-discuss@lists.starlingx.io<br>
<b>Subject:</b> [Starlingx-discuss] Containerizing the StarlingX Infrastructure<br>
<b>When:</b> Tuesday, October 02, 2018 10:00 AM-11:00 AM (UTC-05:00) Eastern Time (US & Canada).<br>
<b>Where:</b> <a href="https://zoom.us/j/342730236">https://zoom.us/j/342730236</a> </div>
<div> </div>
<div> </div>
<a name="BM_BEGIN"></a>
<div>Folks,</div>
<div> </div>
<div>Setting up this call to give the community an overview of the StarlingX infrastructure containerization initiative. </div>
<div>Hope you can join.</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>Brent </div>
<div> </div>
<div> </div>
<div> << File: ATT00001.txt >> </div>
<div> </div>
</span></font>
</body>
</html>