<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=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.yiv4408789594msolistparagraph, li.yiv4408789594msolistparagraph, div.yiv4408789594msolistparagraph
{mso-style-name:yiv4408789594msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.yiv4408789594msonormal, li.yiv4408789594msonormal, div.yiv4408789594msonormal
{mso-style-name:yiv4408789594msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.yiv4408789594msochpdefault, li.yiv4408789594msochpdefault, div.yiv4408789594msochpdefault
{mso-style-name:yiv4408789594msochpdefault;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yiv4408789594msohyperlink
{mso-style-name:yiv4408789594msohyperlink;}
span.yiv4408789594msohyperlinkfollowed
{mso-style-name:yiv4408789594msohyperlinkfollowed;}
span.yiv4408789594htmlpreformattedchar
{mso-style-name:yiv4408789594htmlpreformattedchar;}
span.yiv4408789594emailstyle19
{mso-style-name:yiv4408789594emailstyle19;}
p.yiv4408789594msonormal1, li.yiv4408789594msonormal1, div.yiv4408789594msonormal1
{mso-style-name:yiv4408789594msonormal1;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yiv4408789594msohyperlink1
{mso-style-name:yiv4408789594msohyperlink1;
color:blue;
text-decoration:underline;}
span.yiv4408789594msohyperlinkfollowed1
{mso-style-name:yiv4408789594msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
p.yiv4408789594msolistparagraph1, li.yiv4408789594msolistparagraph1, div.yiv4408789594msolistparagraph1
{mso-style-name:yiv4408789594msolistparagraph1;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yiv4408789594htmlpreformattedchar1
{mso-style-name:yiv4408789594htmlpreformattedchar1;
font-family:Consolas;}
span.yiv4408789594emailstyle191
{mso-style-name:yiv4408789594emailstyle191;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.yiv4408789594msochpdefault1, li.yiv4408789594msochpdefault1, div.yiv4408789594msochpdefault1
{mso-style-name:yiv4408789594msochpdefault1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle35
{mso-style-type:personal-reply;
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;}
/* List Definitions */
@list l0
{mso-list-id:1967393772;
mso-list-type:hybrid;
mso-list-template-ids:-2028458980 269025295 269025305 269025307 269025295 269025305 269025307 269025295 269025305 269025307;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Egor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for sharing your insights. I gave it more thoughts. Maybe the goal can be achieved without implementing a shared COE. We could move all the master nodes
out of user tenants, containerize them, and consolidate them into a set of VMs/Physical servers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think we could separate the discussion into two:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Should Magnum introduce a new bay type, in which master nodes are managed by Magnum (not users themselves)? Like what GCE [1] or ECS [2] does.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">How to consolidate the control services that originally runs on master nodes of each cluster?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Note that the proposal is for adding a new COE (not for changing the existing COEs). That means users will continue to provision existing self-managed COE (k8s/swarm/mesos)
if they choose to.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[1]
<a href="https://cloud.google.com/container-engine/">https://cloud.google.com/container-engine/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[2]
<a href="http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html">
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hongbin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><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""> Guz Egor [mailto:guz_egor@yahoo.com]
<br>
<b>Sent:</b> February-12-16 2:34 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Cc:</b> Hongbin Lu<br>
<b>Subject:</b> Re: [openstack-dev] [magnum]swarm + compose = k8s?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div id="yui_3_16_0_1_1455302653460_10863">
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial","sans-serif";color:black">Hongbin,</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">I am not sure that it's good idea, it looks you propose Magnum enter to "schedulers war" (personally I tired from these debates Mesos
vs Kub vs Swarm).<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">If your concern is just utilization you can always run control plane at "agent/slave" nodes, there main reason why operators (at least
in our case) keep them<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">separate because they need different attention (e.g. I almost don't care why/when "agent/slave" node died, but always double check
that master node was <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">repaired or replaced). <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">One use case I see for shared COE (at least in our environment), when developers want run just docker container without installing
anything locally <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">(e.g docker-machine). But in most cases it's just examples from internet or there own experiments ): <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10862">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">But we definitely should discuss it during midcycle next week. <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10857">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10856">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">--- <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10856">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">Egor<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10853">
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10837">
<div id="yui_3_16_0_1_1455302653460_10836">
<div id="yui_3_16_0_1_1455302653460_10835">
<div id="yui_3_16_0_1_1455302653460_10834">
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">
<hr size="1" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>><br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>
<br>
<b>Sent:</b> Thursday, February 11, 2016 8:50 PM<br>
<b id="yui_3_16_0_1_1455302653460_12353">Subject:</b> Re: [openstack-dev] [magnum]swarm + compose = k8s?</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10879">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
<div id="yiv4408789594">
<div id="yui_3_16_0_1_1455302653460_10883">
<div id="yui_3_16_0_1_1455302653460_10882">
<div id="yui_3_16_0_1_1455302653460_11156">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Hi team,</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_11154">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_11334">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Sorry for bringing up this old thread, but a recent debate on container resource [1] reminded me the use case Kris mentioned below.
I am going to propose a preliminary idea to address the use case. Of course, we could continue the discussion in the team meeting or midcycle.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10944">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10881">
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Idea</span></b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">: Introduce a docker-native COE,
which consists of only minion/worker/slave nodes (no master nodes).</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_11155">
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Goal</span></b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">: Eliminate duplicated IaaS resources
(master node VMs, lbaas vips, floating ips, etc.)</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10885">
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Details</span></b><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">: Traditional COE (k8s/swarm/mesos)
consists of master nodes and worker nodes. In these COEs, control services (i.e. scheduler) run on master nodes, and containers run on worker nodes. If we can port the COE control services to Magnum control plate and share them with all tenants, we eliminate
the need of master nodes thus improving resource utilization. In the new COE, users create/manage containers through Magnum API endpoints. Magnum is responsible to spin tenant VMs, schedule containers to the VMs, and manage the life-cycle of those containers.
Unlike other COEs, containers created by this COE are considered as OpenStack-manage resources. That means they will be tracked in Magnum DB, and accessible by other OpenStack services (i.e. Horizon, Heat, etc.).</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10886">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_1_1455302653460_10945">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">What do you feel about this proposal? Let’s discuss.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">[1]
<a href="https://etherpad.openstack.org/p/magnum-native-api" target="_blank">https://etherpad.openstack.org/p/magnum-native-api</a></span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Best regards,</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D">Hongbin</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Helvetica","sans-serif";color:#1F497D"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal" style="background:white"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"> Kris
G. Lindgren [<a href="mailto:klindgren@godaddy.com">mailto:klindgren@godaddy.com</a>]
<br>
<b>Sent:</b> September-30-15 7:26 PM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> Re: [openstack-dev] [magnum]swarm + compose = k8s?</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both
you and josh.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">I agree that managing one large system is going to be a pain and pas experience tells me this wont be practical/scale, however from
experience I also know exactly the pain Josh is talking about.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">We currently have ~4k projects in our internal openstack cloud, about 1/4 of the projects are currently doing some form of containers
on their own, with more joining every day. If all of these projects were to convert of to the current magnum configuration we would suddenly be attempting to support/configure ~1k magnum clusters. Considering that everyone will want it HA, we are looking
at a minimum of 2 kube nodes per cluster + lbaas vips + floating ips. From a capacity standpoint this is an excessive amount of duplicated infrastructure to spinup in projects where people maybe running 10–20 containers per project. From an operator support
perspective this is a special level of hell that I do not want to get into. Even if I am off by 75%, 250 still sucks.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">From my point of view an ideal use case for companies like ours (yahoo/godaddy) would be able to support hierarchical projects in magnum.
That way we could create a project for each department, and then the subteams of those departments can have their own projects. We create a a bay per department. Sub-projects if they want to can support creation of their own bays (but support of the kube
cluster would then fall to that team). When a sub-project spins up a pod on a bay, minions get created inside that teams sub projects and the containers in that pod run on the capacity that was spun up under that project, the minions for each pod would be
a in a scaling group and as such grow/shrink as dictated by load.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">The above would make it so where we support a minimal, yet imho reasonable, number of kube clusters, give people who can't/don’t want
to fall inline with the provided resource a way to make their own and still offer a "good enough for a single company" level of multi-tenancy.</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline;white-space:pre-wrap;widows:1"><span style="font-size:9.0pt;color:#535353">>Joshua,</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">> </span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>If you share resources, you give up multi-tenancy. No COE system has the</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>concept of multi-tenancy (kubernetes has some basic implementation but it</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>is totally insecure). Not only does multi-tenancy have to “look like” it</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>offers multiple tenants isolation, but it actually has to deliver the</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:12.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>goods.</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">> </span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>I understand that at first glance a company like Yahoo may not want</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>separate bays for their various applications because of the perceived</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>administrative overhead. I would then challenge Yahoo to go deploy a COE</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>like kubernetes (which has no multi-tenancy or a very basic implementation</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>of such) and get it to work with hundreds of different competing</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>applications. I would speculate the administrative overhead of getting</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>all that to work would be greater then the administrative overhead of</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>simply doing a bay create for the various tenants.</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline;white-space:pre-wrap"><span style="font-size:9.0pt;color:#535353">> </span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>Placing tenancy inside a COE seems interesting, but no COE does that</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>today. Maybe in the future they will. Magnum was designed to present an</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>integration point between COEs and OpenStack today, not five years down</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>the road. Its not as if we took shortcuts to get to where we are.</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline;white-space:pre-wrap"><span style="font-size:9.0pt;color:#535353">> </span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>I will grant you that density is lower with the current design of Magnum</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>vs a full on integration with OpenStack within the COE itself. However,</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>that model which is what I believe you proposed is a huge design change to</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>each COE which would overly complicate the COE at the gain of increased</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="line-height:13.5pt;background:white;vertical-align:baseline"><span style="font-size:9.0pt;color:#535353">>density. I personally don’t feel that pain is worth the gain.</span><span style="color:black"><o:p></o:p></span></pre>
<pre style="margin-bottom:18.0pt;line-height:13.5pt;background:white;vertical-align:baseline;white-space:pre-wrap;widows:1"><span style="font-size:9.0pt;color:#535353"> </span><span style="color:black"><o:p></o:p></span></pre>
<div>
<div id="yiv4408789594MAC_OUTLOOK_SIGNATURE">
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">___________________________________________________________________</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">Kris Lindgren</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">Senior Linux Systems Engineer</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Helvetica","sans-serif";color:black">GoDaddy</span><span style="font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:"Helvetica","sans-serif";color:black"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">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><br>
<br>
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>