<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: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:"Arial Black";
panose-1:2 11 10 4 2 1 2 2 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;}
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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gal,<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 clarifying the initiative. I added “[Magnum]” to the title so that Magnum team members can cast their inputs to this thread (if any).<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 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""> Gal Sagie [mailto:gal.sagie@gmail.com]
<br>
<b>Sent:</b> March-19-16 6:04 AM<br>
<b>To:</b> Fox, Kevin M<br>
<b>Cc:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Kuryr] Clarification of expanded mission statement<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Russell,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for starting this thread, i have been wanting to do so myself.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">First, to me Kuryr is much more then just providing a "libnetwork driver" or a "CNI driver"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">in the networking part.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kuryr goal (to me at least) is to simplify orchestration, management and performance<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and avoid vendor lock-in by providing these drivers but also being able to expose and enhance additional<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">policy level features that OpenStack has but are lacking in COEs, We are also looking at easier<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">deployment and packaging and providing additional value with features that make things more efficient and address issues<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">operators/users are facing (like attaching to existing Neutron networks).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We see our selfs operating both on OpenStack projects, helping with features needed for this integration but<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">also in any other project (like Kubernetes / Docker) if this will make more sense and show better value.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The plan is to continue this with storage, we will have to examine things and decide where is the best<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">place to locate them the pros and cons.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I personally don't want to run and start implementing things at other communities and under other<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">governance model unless they make much more sense and show better value for the overall solution.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So my initial reaction is that we can show a lot of value in the storage part as part of OpenStack Kuryr and hence<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">the mission statement change.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">There are many features that i believe we can work in that are currently lacking and we will<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">need to examine them one by one and keep doing the design and spec process open with the community<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">so everyone can review and judge the value.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The last thing i am going to do is drive to re-implement things that are already there and in good enough shape,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">none of us have the need or time to do that :)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In the storage area i see the plugins (and not just for Kubernetes), i see the persistent and re-using of storage<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">parts as being interesting to start with.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Another area that i included as storage is mostly disaster recovery and backup, i think we can bring a lot of value<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">to containers deployments by leveraging projects like Smaug and Freezer which offer application backups<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and recovery.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I really prefer we do this thinking process together as a community and i already talked with some people that showed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">interest in some of these features.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My intention was to first get the TC approval to explore this area and make sure it doesnt conflict and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">only then start working on defining the details again with the broad community, openly just like we do<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">everything else.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Mar 18, 2016 at 10:12 PM, Fox, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">I'd assume a volume plugin for cinder support and/or a volume plugin for manila support?<br>
<br>
Either would be useful.<br>
<br>
Thanks,<br>
Kevin<o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Russell Bryant [<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>]<br>
<b>Sent:</b> Friday, March 18, 2016 4:59 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions); <a href="mailto:gal.sagie@gmail.com" target="_blank">
gal.sagie@gmail.com</a><br>
<b>Subject:</b> [openstack-dev] [Kuryr] Clarification of expanded mission statement</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">The Kuryr project proposed an update to its mission statement and I agreed to start a ML thread seeking clarification on the update.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><a href="https://review.openstack.org/#/c/289993" target="_blank">https://review.openstack.org/#/c/289993</a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">The change expands the current networking focus to also include storage integration.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">I was interested to learn more about what work you expect to be doing. On the networking side, it's clear to me: a libnetwork plugin, and now perhaps a CNI plugin. What specific
code do you expect to deliver as a part of your expanded scope? Will that code be in Kuryr, or be in upstream projects?</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">If you don't know yet, that's fine. I was just curious what you had in mind. We don't really have OpenStack projects that are organizing around contributing to other upstreams,
but I think this case is fine.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black">-- <o:p></o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial Black","sans-serif";color:black">Russell Bryant</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal">Best Regards ,<br>
<br>
The G. <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>