<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" 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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0in;
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:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
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:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Kailun,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m not aware of provider networks being referred to as “admin” networks. The provider network terminology comes from the neutron extension (“providernet”) that defines the attributes for the physical network
(“provider:network_type”, “provider:physical_network”, etc). I agree that the StarlingX definition is of greater scope since it also covers the related configuration file values.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The only distinction that I am aware of between “admin” and “tenant” for provider networks is that they are only exposed to a user with administrative rights (enforced by policy).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I hope that clarifies what I refer to as a provider network.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards, Matt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></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 #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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 [mailto:kailun.qin@intel.com]
<br>
<b>Sent:</b> Wednesday, August 08, 2018 12:01 PM<br>
<b>To:</b> Peters, Matt; Jolliffe, Ian; starlingx-discuss@lists.starlingx.io<br>
<b>Cc:</b> Troyer, Dean; Jones, Bruce E; Chilcote Bacco, Derek A; Le, Huifeng; Xu, Chenjie; Zhao, Forrest; Guo, Ruijing; Rowsell, Brent<br>
<b>Subject:</b> RE: Questions about Provider MTU feature for StarlingX upstreaming<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Matt,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the explanation. One thing that brings a little confusion is the terminology “provider network”:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.25in;text-indent:-.25in"><span style="font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">In StarlingX, the so-called “provider network” is more related w/ physical network, like a superset of “upstream provider networks”, which addresses the values that are currently stored in configuration file parameters only;<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.25in;text-indent:-.25in"><span style="font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">while in upstream neutron, what distinguishes provider networks from tenant networks is who (admin/user) actually creates them and how.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Just correct me if I’m wrong.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If my understanding is correct, yes, I agree with Ian’s response. We’ll work on removing the Neutron configuration file based approach to MTU management and exposing it via a RESTful API as the benefits are clear
to us. Thanks again!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">BR,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Kailun<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><span style="color:#1F497D"><o:p> </o:p></span></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"><a name="_____replyseparator"></a><b>From:</b> Peters, Matt [mailto:Matt.Peters@windriver.com]
<br>
<b>Sent:</b> Wednesday, August 8, 2018 9:05 PM<br>
<b>To:</b> Qin, Kailun <kailun.qin@intel.com>; Jolliffe, Ian <Ian.Jolliffe@windriver.com><br>
<b>Cc:</b> Troyer, Dean <dean.troyer@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Chilcote Bacco, Derek A <derek.a.chilcote.bacco@intel.com>; Le, Huifeng <huifeng.le@intel.com>; Xu, Chenjie <chenjie.xu@intel.com>; Zhao, Forrest <forrest.zhao@intel.com>;
Guo, Ruijing <ruijing.guo@intel.com>; Rowsell, Brent <Brent.Rowsell@windriver.com><br>
<b>Subject:</b> RE: Questions about Provider MTU feature for StarlingX upstreaming<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">HI Kailun,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m not sure from your reply if you are agreeing or disagreeing with Ian’s response.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The intent was to show that the business case for the provider network MTU configuration is to remove the Neutron configuration file based approach to MTU management and expose it via a RESTful API. This is
a similar business case for the managed provider networks as a whole.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It is understood that upstream neutron already supports MTU configuration at the tenant network level, but was trying to show that the provider network MTU configuration addresses the values that are current
stored in configuration file parameters only.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards, Matt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></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 #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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> Wednesday, August 08, 2018 1:34 AM<br>
<b>To:</b> Jolliffe, Ian<br>
<b>Cc:</b> Troyer, Dean; Jones, Bruce E; Chilcote Bacco, Derek A; Le, Huifeng; Xu, Chenjie; Zhao, Forrest; Guo, Ruijing; Rowsell, Brent; Peters, Matt<br>
<b>Subject:</b> RE: Questions about Provider MTU feature for StarlingX upstreaming<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Ian,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the feedback.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The upstream neutron supports:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:22.8pt;text-indent:-.25in"><span style="font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Set/modify a specific MTU on a (provider/tenant) network via REST API. This was introduced via “net-mtu-writable” API extension [1][2]. The requested MTU will work together w/ the MTU configuration options (global_physnet_mtu,
physical_network_mtus and path_mtu) to configure the network MTU [3].<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">However, it does *<b>NOT</b>* support:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:22.8pt;text-indent:-.25in"><span style="font-family:Symbol;color:#1F497D">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Dynamic MTU configuration options (global_physnet_mtu, physical_network_mtus and path_mtu) set/modify via REST API.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">[1] </span><a href="https://bugs.launchpad.net/neutron/+bug/1671634"><span style="font-size:10.0pt">https://bugs.launchpad.net/neutron/+bug/1671634</span></a><span style="font-size:10.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">[2] </span><a href="https://review.openstack.org/#/c/483518/"><span style="font-size:10.0pt">https://review.openstack.org/#/c/483518/</span></a><span style="font-size:10.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">[3] </span><a href="https://docs.openstack.org/neutron/latest/admin/config-mtu.html"><span style="font-size:10.0pt">https://docs.openstack.org/neutron/latest/admin/config-mtu.html</span></a><span style="font-size:10.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So with the current upstream neutron implementation, the MTU configurations options still play a part at the deployment level. They serve as global maximum permissible and default values for network MTUs (of
different network types). Meanwhile, neutron does support a dynamic alternative for users to set/modify specific MTUs across their networks. What do you think? Any use case that the current neutron is not able to cover?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Let me know if anything unclear. Great thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">BR,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Kailun<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></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>From:</b> Jolliffe, Ian [<a href="mailto:Ian.Jolliffe@windriver.com">mailto:Ian.Jolliffe@windriver.com</a>]
<br>
<b>Sent:</b> Wednesday, August 8, 2018 9:52 AM<br>
<b>To:</b> Qin, Kailun <<a href="mailto:kailun.qin@intel.com">kailun.qin@intel.com</a>><br>
<b>Cc:</b> Troyer, Dean <<a href="mailto:dean.troyer@intel.com">dean.troyer@intel.com</a>>; Jones, Bruce E <<a href="mailto:bruce.e.jones@intel.com">bruce.e.jones@intel.com</a>>; Chilcote Bacco, Derek A <<a href="mailto:derek.a.chilcote.bacco@intel.com">derek.a.chilcote.bacco@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>>; Guo, Ruijing <<a href="mailto:ruijing.guo@intel.com">ruijing.guo@intel.com</a>>;
Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>; Peters, Matt <<a href="mailto:Matt.Peters@windriver.com">Matt.Peters@windriver.com</a>><br>
<b>Subject:</b> Re: Questions about Provider MTU feature for StarlingX upstreaming<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"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">The provider network MTU goes along with the business case for managed provider networks.</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-CA" style="color:#1F497D"> </span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-CA" style="color:#1F497D">The feature comparison should not be between provider network MTUs and tenant network MTUs, but more about whether we support MTU values via provider network configuration (REST API).</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-CA" style="color:#1F497D"> </span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-CA" style="color:#1F497D">The comparable feature in OpenStack is the support for the ML2 global_physnet_mtu, physical_network_mtus and path_mtu configuration options.</span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span lang="EN-CA" style="color:#1F497D"> </span><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<a href="https://blueprints.launchpad.net/neutron/+spec/mtu-selection-and-advertisement"><span lang="EN-CA" style="color:#954F72">https://blueprints.launchpad.net/neutron/+spec/mtu-selection-and-advertisement</span></a><span lang="EN-CA" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards;<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ian<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 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-CA" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-CA" style="font-size:12.0pt;color:black">"Qin, Kailun" <</span><a href="mailto:kailun.qin@intel.com"><span lang="EN-CA" style="font-size:12.0pt">kailun.qin@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">><br>
<b>Date: </b>Monday, August 6, 2018 at 3:01 AM<br>
<b>To: </b>Ian Jolliffe <</span><a href="mailto:Ian.Jolliffe@windriver.com"><span lang="EN-CA" style="font-size:12.0pt">Ian.Jolliffe@windriver.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">><br>
<b>Cc: </b>"Troyer, Dean" <</span><a href="mailto:dean.troyer@intel.com"><span lang="EN-CA" style="font-size:12.0pt">dean.troyer@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>, "Jones, Bruce E" <</span><a href="mailto:bruce.e.jones@intel.com"><span lang="EN-CA" style="font-size:12.0pt">bruce.e.jones@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>,
"Chilcote Bacco, Derek A" <</span><a href="mailto:derek.a.chilcote.bacco@intel.com"><span lang="EN-CA" style="font-size:12.0pt">derek.a.chilcote.bacco@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>, "Le, Huifeng" <</span><a href="mailto:huifeng.le@intel.com"><span lang="EN-CA" style="font-size:12.0pt">huifeng.le@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>,
"Qin, Kailun" <</span><a href="mailto:kailun.qin@intel.com"><span lang="EN-CA" style="font-size:12.0pt">kailun.qin@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>, "Xu, Chenjie" <</span><a href="mailto:chenjie.xu@intel.com"><span lang="EN-CA" style="font-size:12.0pt">chenjie.xu@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>,
"Zhao, Forrest" <</span><a href="mailto:forrest.zhao@intel.com"><span lang="EN-CA" style="font-size:12.0pt">forrest.zhao@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">>, "Guo, Ruijing" <</span><a href="mailto:ruijing.guo@intel.com"><span lang="EN-CA" style="font-size:12.0pt">ruijing.guo@intel.com</span></a><span lang="EN-CA" style="font-size:12.0pt;color:black">><br>
<b>Subject: </b>Questions about Provider MTU feature for StarlingX upstreaming<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><a name="_MailOriginalBody"><span lang="EN-CA">Hi Ian,</span></a><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We are analyzing the provider MTU feature for StarlingX upstreaming, in which case the patch
<b>021ae1a</b> introduced providernet MTU and <b>c647127</b> introduced the port granularity bindings for MTU.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Since the upstream neutron already has the network granularity MTU implemented [1] and made it available to be created or updated [2], would you please kindly help check whether we need to upstream this feature?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">If so, would you please share some business use cases or user stories related with us?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:10.0pt">[1] </span><a href="https://review.openstack.org/#/c/480738/"><span lang="EN-CA" style="font-size:10.0pt">https://review.openstack.org/#/c/480738/</span></a><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:10.0pt">[2] </span><a href="https://review.openstack.org/#/c/483091/"><span lang="EN-CA" style="font-size:10.0pt">https://review.openstack.org/#/c/483091/</span></a><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Let me know if any question. Thanks a lot!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">BR,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Kailun<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>