<html 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:"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;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.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>
</head>
<body lang="EN-CA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Kailun,<o:p></o:p></p>
<p class="MsoNormal">I have no further review comments. Once you receive the final feedback from others, I think it is ready to push it for review in the neutron-specs.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards, Matt<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Qin, Kailun" <kailun.qin@intel.com><br>
<b>Date: </b>Friday, October 12, 2018 at 6:24 AM<br>
<b>To: </b>"Peters, Matt" <Matt.Peters@windriver.com><br>
<b>Cc: </b>"starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io><br>
<b>Subject: </b>Network Segment Range Management - Spec Rework Review<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Hi Matt,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Please kindly find the attached spec rework for StarlingX provider network management feature upstreaming [1][2].
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Any further comments or suggestions would be greatly appreciated.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">BR,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Kailun</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">[1] <a href="https://review.openstack.org/599980">
https://review.openstack.org/599980</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">[2] <a href="https://review.openstack.org/579411">
https://review.openstack.org/579411</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><a name="_____replyseparator"></a><b>From:</b> Peters, Matt [mailto:Matt.Peters@windriver.com]
<br>
<b>Sent:</b> Thursday, October 11, 2018 7:38 PM<br>
<b>To:</b> Qin, Kailun <kailun.qin@intel.com><br>
<b>Cc:</b> Jolliffe, Ian <Ian.Jolliffe@windriver.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Khalil, Ghada <Ghada.Khalil@windriver.com>; Guo, Ruijing <ruijing.guo@intel.com>; Le, Huifeng <huifeng.le@intel.com>; Xu, Chenjie <chenjie.xu@intel.com>; Zhao,
Forrest <forrest.zhao@intel.com><br>
<b>Subject:</b> Re: Provider Segment Range Management - Spec Rework Review<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi Kailun,<o:p></o:p></p>
<p class="MsoNormal">Attached are my latest review comments.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards, Matt<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Qin, Kailun" <<a href="mailto:kailun.qin@intel.com">kailun.qin@intel.com</a>><br>
<b>Date: </b>Tuesday, October 9, 2018 at 11:27 AM<br>
<b>To: </b>"Peters, Matt" <<a href="mailto:Matt.Peters@windriver.com">Matt.Peters@windriver.com</a>><br>
<b>Cc: </b>"Jolliffe, Ian" <<a href="mailto:Ian.Jolliffe@windriver.com">Ian.Jolliffe@windriver.com</a>>, Brent Rowsell <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>, Ghada Khalil <<a href="mailto:Ghada.Khalil@windriver.com">Ghada.Khalil@windriver.com</a>>,
"Guo, Ruijing" <<a href="mailto:ruijing.guo@intel.com">ruijing.guo@intel.com</a>>, "Le, Huifeng" <<a href="mailto:huifeng.le@intel.com">huifeng.le@intel.com</a>>, "Xu, Chenjie" <<a href="mailto:chenjie.xu@intel.com">chenjie.xu@intel.com</a>>, "Zhao, Forrest"
<<a href="mailto:forrest.zhao@intel.com">forrest.zhao@intel.com</a>><br>
<b>Subject: </b>RE: Provider Segment Range Management - Spec Rework Review</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Matt,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for all the comments. Please kindly see the updated spec in the attached.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Let me know if any further suggestion.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">BR,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Kailun</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Peters, Matt [<a href="mailto:Matt.Peters@windriver.com">mailto:Matt.Peters@windriver.com</a>]
<br>
<b>Sent:</b> Tuesday, October 9, 2018 9:17 PM<br>
<b>To:</b> Qin, Kailun <<a href="mailto:kailun.qin@intel.com">kailun.qin@intel.com</a>><br>
<b>Cc:</b> Jolliffe, Ian <<a href="mailto:Ian.Jolliffe@windriver.com">Ian.Jolliffe@windriver.com</a>>; Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>; Khalil, Ghada <<a href="mailto:Ghada.Khalil@windriver.com">Ghada.Khalil@windriver.com</a>>;
Guo, Ruijing <<a href="mailto:ruijing.guo@intel.com">ruijing.guo@intel.com</a>>; Le, Huifeng <<a href="mailto:huifeng.le@intel.com">huifeng.le@intel.com</a>>; Xu, Chenjie <<a href="mailto:chenjie.xu@intel.com">chenjie.xu@intel.com</a>>; Zhao, Forrest <<a href="mailto:forrest.zhao@intel.com">forrest.zhao@intel.com</a>><br>
<b>Subject:</b> RE: Provider Segment Range Management - Spec Rework Review<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">See inline.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Qin, Kailun [<a href="mailto:kailun.qin@intel.com">mailto:kailun.qin@intel.com</a>]
<br>
<b>Sent:</b> Monday, October 08, 2018 5:40 AM<br>
<b>To:</b> Peters, Matt<br>
<b>Cc:</b> Jolliffe, Ian; Rowsell, Brent; Khalil, Ghada; Guo, Ruijing; Le, Huifeng; Xu, Chenjie; Zhao, Forrest<br>
<b>Subject:</b> RE: Provider Segment Range Management - Spec Rework Review</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Matt,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I am working on the update of spec. I have two main questions in response to your comments:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt;text-indent:-18.0pt"><span style="color:#1F497D">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">You recommended to use the generalized “network_segment_ranges” rather than including provider in the DB/API name and description.</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt"><span style="color:#1F497D">Do you also expect the whole spec to avoid using the “provider” terminology and we pick “network segment range management” as the global subject?</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0cm"><b><i><span style="color:#1F497D">[MP>] I think we should try to avoid linking this specifically to provider networks to avoid the same confusion and contention we received with the original spec.</span></i></b><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt;text-indent:-18.0pt"><span style="color:#1F497D">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D">
</span><span style="color:#1F497D">I proposed an extended to attribute to the resource “networks” which you think is not required, as the network entity already has the “provider” extension that can be used to assign the required provider attributes upon creation.</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt"><span style="color:#1F497D">I agree with you. But the initiative of introducing this attribute, is to provide users with admin privilege the ability to specify the underlying provider segment *<b>range</b>*
when creating networks (NOT just a specific segment ID -- what the “provider” extension does). This aims to cover the scenarios described in UseCase III of the spec, which are also proposed in this bp:
<a href="https://blueprints.launchpad.net/neutron/+spec/extend-api-for-hpb">https://blueprints.launchpad.net/neutron/+spec/extend-api-for-hpb</a>.</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:22.8pt"><span style="color:#1F497D">Our proposal is related w/ segment range and has a larger scope, which is able to cover the cases described in the cited bp if with that attribute. Do you suggest that we cover
UseCase III in our bp?</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0cm"><b><i><span style="color:#1F497D">[MP>] I don’t feel we need to support a range at the network level. I feel the tenant level scope is sufficient and solves the use-cases we have encountered. If a customer
really wants to select a segment ID for a network, they can use the provider extension rather than having it specifically selected from a range. I think we should focus on the main use case of having pools of managed segment ranges that can either be shared
or assigned to a specific tenant.</span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span style="color:#1F497D">Please let me know what your thoughts are. Great thanks!</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span style="color:#1F497D">BR,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><span style="color:#1F497D">Kailun</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Peters, Matt [<a href="mailto:Matt.Peters@windriver.com">mailto:Matt.Peters@windriver.com</a>]
<br>
<b>Sent:</b> Monday, October 1, 2018 10:07 PM<br>
<b>To:</b> Qin, Kailun <<a href="mailto:kailun.qin@intel.com">kailun.qin@intel.com</a>><br>
<b>Cc:</b> Jolliffe, Ian <<a href="mailto:Ian.Jolliffe@windriver.com">Ian.Jolliffe@windriver.com</a>>; Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>; Khalil, Ghada <<a href="mailto:Ghada.Khalil@windriver.com">Ghada.Khalil@windriver.com</a>>;
Guo, Ruijing <<a href="mailto:ruijing.guo@intel.com">ruijing.guo@intel.com</a>>; Le, Huifeng <<a href="mailto:huifeng.le@intel.com">huifeng.le@intel.com</a>>; Xu, Chenjie <<a href="mailto:chenjie.xu@intel.com">chenjie.xu@intel.com</a>>; Zhao, Forrest <<a href="mailto:forrest.zhao@intel.com">forrest.zhao@intel.com</a>><br>
<b>Subject:</b> RE: Provider Segment Range Management - Spec Rework Review<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Attached are my review comments and suggested changes.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">NOTE: I had to change the format in order to embed my review comments, but it can continue to be an RST file format.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards, Matt</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Qin, Kailun [</span><a href="mailto:kailun.qin@intel.com"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:kailun.qin@intel.com</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<br>
<b>Sent:</b> Thursday, September 27, 2018 10:36 AM<br>
<b>To:</b> Peters, Matt<br>
<b>Cc:</b> Jolliffe, Ian; Rowsell, Brent; Khalil, Ghada; Guo, Ruijing; Le, Huifeng; Qin, Kailun; Xu, Chenjie; Zhao, Forrest<br>
<b>Subject:</b> Provider Segment Range Management - Spec Rework Review</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi Matt,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please kindly find in the attached the drafted rework of provider segment range management spec.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I made the updates directly on the upstream spec patch so that figures/tables/format can be kept as is. Excuse me for the inconvenience to make comments in a rst file. Please kindly leave a tag where you would like to comment so that I
can filter them out.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Great thanks!<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">BR,<o:p></o:p></p>
<p class="MsoNormal">Kailun<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>