<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:宋体;
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:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">There are some discussions on the spec review and Kyle suggested the discussion should be on openstack-dev. And also we want to get more attention on this topic
to ensure that ML3 is the right approach.<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">Problem description:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">At this point, only a single L3 router plugin can be exclusively specified by configuration. As the result, only a single type of router can be deployed. Multiple
types of L3 routers can't be deployed simultaneously. For example, neutron native L3 router(legacy/ha/dvr) can't coexist with other opensource/vendor routers. <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">The basic idea that we are proposing is a L3 router plugin version of ML2. Implement a new modular L3 router plugin and port the existing reference L3 plugin
(neutron/services/l3_router/l3_router_plugin.py) to the router driver of L3 router plugin. (Agent side doesn't need modification). It's up to each vendor if they will port their L3 router plugin into ML3 router driver. Armando and Paul made good points in
the spec review ( FYI <a href="https://review.openstack.org/#/c/105078/">https://review.openstack.org/#/c/105078/</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">The information we are seeking is:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">1) Whether there is a broader requirement for running multiple types for L3 routers in OpenStack deployment.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">2) Whether ML3 is the right approach to achieve so.<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,<br>
Zang, Rui<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"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Kyle Mestery [mailto:mestery@mestery.com]
<br>
<b>Sent:</b> Tuesday, June 2, 2015 9:17 PM<br>
<b>To:</b> CARVER, PAUL; Maru Newby; Assaf Muller<br>
<b>Cc:</b> Zang, Rui; Isaku Yamahata; YAMAMOTO Takashi; Stephen Wong; IWAMOTO Toshihiro; Bob Melander; mark mcclain; Carl Baldwin; Salvatore Orlando; Gal Sagie; vikram.choudhary; Armando Migliaccio; Robert Kukura; Sukhdev Kapur; Wang, Yalei; vishwanath jayaraman<br>
<b>Subject:</b> Re: Change in openstack/neutron-specs[master]: L3 plugin: modular l3 router plugin<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Two items:<br>
<br>
1. This seems like a candidate for an RFE following our new RFE process [1].<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">2. This discussion really should be happening on openstack-dev.<o:p></o:p></p>
</div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<p class="MsoNormal">Kyle<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><br>
[1] <a href="https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst">
https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jun 2, 2015 at 6:27 AM, CARVER, PAUL <<a href="mailto:pc2929@att.com" target="_blank">pc2929@att.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Replying directly rather than adding side noise to review.o.o: Yes, I'm going to send the survey to the OpenStack General list and the OpenStack Operators list. I'm not sure if it's actually appropriate to send the survey to the -dev list
although I'll certainly post the summary results there. I just wanted to give Armando and anyone else following the ML3 review discussion an opportunity to comment on whether I've asked the right questions before I send the survey out.<br>
<br>
For those who didn't see it, the survey link is here: <a href="https://www.surveymonkey.com/s/BTMH7V5" target="_blank">
https://www.surveymonkey.com/s/BTMH7V5</a> and the purpose is to gather data on how people are currently doing L3 in OpenStack and whether a modular (i.e. supporting multiple L3 technologies/vendors per Neutron instance) L3 is something that people see a need
for.<br>
<br>
Comments are welcome on the wording of the questions and the multiple choice answers I provided. I'll send the survey out to the mailing lists sometime after noon EDT (UTC-4). Any comments I receive before then, I'll happily tweak the wording before sending.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: Rui Zang (Code Review) [mailto:<a href="mailto:review@openstack.org">review@openstack.org</a>]<br>
Sent: Tuesday, June 02, 2015 02:31<br>
To: Isaku Yamahata<br>
Cc: YAMAMOTO Takashi; Stephen Wong; IWAMOTO Toshihiro; Bob Melander; mark mcclain; Carl Baldwin; Kyle Mestery; Salvatore Orlando; Gal Sagie; vikram.choudhary; Armando Migliaccio; Robert Kukura; Sukhdev Kapur; CARVER, PAUL; yalei wang; vishwanath jayaraman<br>
Subject: Change in openstack/neutron-specs[master]: L3 plugin: modular l3 router plugin<br>
<br>
Rui Zang has posted comments on this change.<br>
<br>
Change subject: L3 plugin: modular l3 router plugin<br>
......................................................................<br>
<br>
<br>
Patch Set 10:<br>
<br>
(1 comment)<br>
<br>
<a href="https://review.openstack.org/#/c/105078/10/specs/liberty/ml3-router-plugin.rst" target="_blank">https://review.openstack.org/#/c/105078/10/specs/liberty/ml3-router-plugin.rst</a><br>
File specs/liberty/ml3-router-plugin.rst:<br>
<br>
Line 24: L3 routers can't be deployed simultaneously. For example, neutron native<br>
> That's a really good point, but I'm not sure what the right answer is. Bein<br>
Paul, I assume you are going to send this survey to the mailing list, right?<br>
<br>
<br>
--<br>
To view, visit <a href="https://review.openstack.org/105078" target="_blank">https://review.openstack.org/105078</a><br>
To unsubscribe, visit <a href="https://review.openstack.org/settings" target="_blank">
https://review.openstack.org/settings</a><br>
<br>
Gerrit-MessageType: comment<br>
Gerrit-Change-Id: I1c476156eb9788056e50e48c85c3d9b17e336b38<br>
Gerrit-PatchSet: 10<br>
Gerrit-Project: openstack/neutron-specs<br>
Gerrit-Branch: master<br>
Gerrit-Owner: Isaku Yamahata <<a href="mailto:yamahata.review@gmail.com">yamahata.review@gmail.com</a>><br>
Gerrit-Reviewer: Armando Migliaccio <<a href="mailto:armamig@gmail.com">armamig@gmail.com</a>><br>
Gerrit-Reviewer: Bob Melander <<a href="mailto:bob.melander@gmail.com">bob.melander@gmail.com</a>><br>
Gerrit-Reviewer: Carl Baldwin <<a href="mailto:carl@ecbaldwin.net">carl@ecbaldwin.net</a>><br>
Gerrit-Reviewer: Gal Sagie <<a href="mailto:gal.sagie@huawei.com">gal.sagie@huawei.com</a>><br>
Gerrit-Reviewer: IWAMOTO Toshihiro <<a href="mailto:iwamoto@valinux.co.jp">iwamoto@valinux.co.jp</a>><br>
Gerrit-Reviewer: Isaku Yamahata <<a href="mailto:yamahata.review@gmail.com">yamahata.review@gmail.com</a>><br>
Gerrit-Reviewer: Jenkins<br>
Gerrit-Reviewer: Kyle Mestery <<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>><br>
Gerrit-Reviewer: Paul Carver <<a href="mailto:pcarver@att.com">pcarver@att.com</a>><br>
Gerrit-Reviewer: Robert Kukura <<a href="mailto:kukura@noironetworks.com">kukura@noironetworks.com</a>><br>
Gerrit-Reviewer: Rui Zang <<a href="mailto:rui.zang@intel.com">rui.zang@intel.com</a>><br>
Gerrit-Reviewer: Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com">salv.orlando@gmail.com</a>><br>
Gerrit-Reviewer: Stephen Wong <<a href="mailto:stephen.kf.wong@gmail.com">stephen.kf.wong@gmail.com</a>><br>
Gerrit-Reviewer: Sukhdev Kapur <<a href="mailto:sukhdev@aristanetworks.com">sukhdev@aristanetworks.com</a>><br>
Gerrit-Reviewer: YAMAMOTO Takashi <<a href="mailto:yamamoto@midokura.com">yamamoto@midokura.com</a>><br>
Gerrit-Reviewer: mark mcclain <<a href="mailto:mark@mcclain.xyz">mark@mcclain.xyz</a>><br>
Gerrit-Reviewer: vikram.choudhary <<a href="mailto:vikram.choudhary@huawei.com">vikram.choudhary@huawei.com</a>><br>
Gerrit-Reviewer: vishwanath jayaraman <<a href="mailto:vishwanathj@hotmail.com">vishwanathj@hotmail.com</a>><br>
Gerrit-Reviewer: yalei wang <<a href="mailto:yalei.wang@intel.com">yalei.wang@intel.com</a>><br>
Gerrit-HasComments: Yes<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>