<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
Hi Yunhong,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
I haven't looked at Mellanox in much detail. I think that we'll get more details from Irena down the road. Regarding your question, I can only answer based on my experience with Cisco's VM-FEX. In a nutshell:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
-- a vNIC is connected to an external switch. Once the host is booted up, all the PFs and VFs provisioned on the vNIC will be created, as well as all the corresponding ethernet interfaces . </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
-- As far as Neutron is concerned, a neutron port can be associated with a VF. One way to do so is to specify this requirement in the —nic option, providing information such as:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span style="font-size: 10.5pt; "> . PCI alias (this is the same alias as defined in your nova blueprints)</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<p class="MsoNormal"><span lang="EN-US" style="font-size: 10.5pt; "> . direct pci-passthrough/macvtap<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; "> . port profileid that is compliant with 802.1Qbh</span></p>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; "> -- similar to how you translate the nova flavor with PCI requirements to PCI requests for scheduling purpose, Nova API (the nova api component) can translate the above to PCI requests for scheduling purpose.
I can give more detail later on this. </span></p>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; "><br>
</span></p>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; ">Regarding your last question, since the vNIC is already connected with the external switch, the vNIC driver will be responsible for communicating the port profile to the external switch. As you have already known,
libvirt provides several ways to specify a VM to be booted up with SRIOV. For example, in the following interface definition: </span></p>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; "> </span></p>
<p class="MsoNormal"></p>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: 'Courier New', Courier, mono; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; line-height: 1.2em; text-align: -webkit-left; background-color: rgb(255, 255, 255); "> <kbd class="userinput"><b><interface type='hostdev' managed='yes'>
<source>
<address type='pci' domain='0' bus='0x09' slot='0x0' function='0x01'/>
</source>
<mac address='01:23:45:67:89:ab' />
<virtualport type='802.1Qbh'>
<parameters profileid='my-port-profile' />
</virtualport>
</interface></b></kbd></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: 'Courier New', Courier, mono; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; line-height: 1.2em; text-align: -webkit-left; background-color: rgb(255, 255, 255); "><kbd class="userinput"><b><br></b></kbd></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em; ">The SRIOV VF (bus 0x09, VF 0x01) will be allocated, and the port profile 'my-port-profile' will be used to provision this VF. Libvirt will be responsible for invoking the vNIC driver to configure this VF with the port profile my-port-porfile. The driver will talk to the external switch using the 802.1qbh standards to complete the VF's configuration </span><span style="line-height: 17px; ">and</span><span style="line-height: 1.2em; "> binding with the VM.</span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em; "><br></span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;">Now that nova PCI passthrough is responsible for discovering/scheduling/allocating a VF, the rest of the </span><span style="line-height: 16px;">puzzle</span><span style="line-height: 1.2em;"> is to associate this PCI device with the feature that's going to use it, and the feature will be </span><span style="line-height: 16px;">responsible</span><span style="line-height: 1.2em;"> for configuring it. You can also see from the above example, in one implementation of SRIOV, the feature (in this case neutron) may not need to do </span><span style="line-height: 16px;">much</span><span style="line-height: 1.2em;"> in terms of working with the external switch, the work is actually done by libvirt behind the scene. </span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;"><br></span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;">Now the questions are:</span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;"> -- how the port profile gets defined/managed</span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;"> -- how the port profile gets associated with a neutron network</span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;">The first question will be specific to the particular product, and therefore a particular neutron plugin has to mange that. </span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><font face="Calibri" size="3"><span style="line-height: 1.2em;">There may be several approaches to address the second question. For example, in the simplest case, a port profile can be associated with a neutron network. This has some significant drawbacks. Since the port profile defines features for all the ports that use it, the one port profile to one neutron network mapping would mean all the ports on the network will have exactly the same features (for example, QoS characteristics). To make it flexible, the binding of a port profile to a port may be done at the port creation time.</span></font></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><br></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; ">Let me know if the above answered your question.</pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; "><br></pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; ">thanks,</pre>
<pre class="codeblock" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; margin-top: 0.5em; margin-bottom: 0em; text-align: -webkit-left; ">Robert</pre>
<p></p>
<p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<span lang="EN-US" style="font-size: 10.5pt; "><br>
</span></p>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px; ">
<div>
<div>On 10/29/13 3:03 AM, "Jiang, Yunhong" <<a href="mailto:yunhong.jiang@intel.com">yunhong.jiang@intel.com</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
/* 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: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:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
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><!--[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]-->
<div lang="ZH-CN" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">Robert, is it possible to have a IRC meeting? I’d prefer to IRC meeting because it’s more openstack style and also can keep the minutes clearly.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">To your flow, can you give more detailed example. For example, I can consider user specify the instance with –nic option specify a network id, and then how nova device the requirement
to the PCI device? I assume the network id should define the switches that the device can connect to , but how is that information translated to the PCI property requirement? Will this translation happen before the nova scheduler make host decision?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">--jyh<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D"><o:p> </o:p></span></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 lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Robert Li (baoli) [<a href="mailto:baoli@cisco.com">mailto:baoli@cisco.com</a>]
<br>
<b>Sent:</b> Monday, October 28, 2013 12:22 PM<br>
<b>To:</b> Irena Berezovsky; <a href="mailto:prashant.upadhyaya@aricent.com">prashant.upadhyaya@aricent.com</a>; Jiang, Yunhong;
<a href="mailto:chris.friesen@windriver.com">chris.friesen@windriver.com</a>; He, Yongli; Itzik Brown<br>
<b>Cc:</b> OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery (kmestery); Sandhya Dasu (sadasu)<br>
<b>Subject:</b> Re: [openstack-dev] [nova] [neutron] PCI pass-through network support<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Hi Irena,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Thank you very much for your comments. See inline. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">--Robert<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">On 10/27/13 3:48 AM, "Irena Berezovsky" <<a href="mailto:irenab@mellanox.com">irenab@mellanox.com</a>> wrote:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Hi Robert,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thank you very much for sharing the information regarding your efforts. Can you please share your idea of the end to end flow? How do you suggest to bind Nova and Neutron?</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">The end to end flow is actually encompassed in the blueprints in a nutshell. I will reiterate it in below. The binding between Nova and Neutron occurs with the neutron v2 API that
nova invokes in order to provision the neutron services. The vif driver is responsible for plugging in an instance onto the networking setup that neutron has created on the host.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Normally, one will invoke "nova boot" api with the —nic options to specify the nic with which the instance will be connected to the network. It currently allows net-id, fixed ip and/or
port-id to be specified for the option. However, it doesn't allow one to specify special networking requirements for the instance. Thanks to the nova pci-passthrough work, one can specify PCI passthrough device(s) in the nova flavor. But it doesn't provide
means to tie up these PCI devices in the case of ethernet adpators with networking services. Therefore the idea is actually simple as indicated by the blueprint titles, to provide means to tie up SRIOV devices with neutron services. A work flow would roughly
look like this for 'nova boot':<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- Specifies networking requirements in the —nic option. Specifically for SRIOV, allow the following to be specified in addition to the existing required information:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> . PCI alias<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> . direct pci-passthrough/macvtap<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> . port profileid that is compliant with 802.1Qbh<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> The above information is optional. In the absence of them, the existing behavior remains.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- if special networking requirements exist, Nova api creates PCI requests in the nova instance type for scheduling purpose<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- Nova scheduler schedules the instance based on the requested flavor plus the PCI requests that are created for networking.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- Nova compute invokes neutron services with PCI passthrough information if any <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- Neutron performs its normal operations based on the request, such as allocating a port, assigning ip addresses, etc. Specific to SRIOV, it should validate the information
such as profileid, and stores them in its db. It's also possible to associate a port profileid with a neutron network so that port profileid becomes optional in the —nic option. Neutron returns nova the port information, especially for PCI passthrough related
information in the port binding object. Currently, the port binding object contains the following information:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> binding:vif_type<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> binding:host_id<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> binding:profile<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> binding:capabilities<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> -- nova constructs the domain xml and plug in the instance by calling the vif driver. The vif driver can build up the interface xml based on the port binding information. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The blueprints you registered make sense. On Nova side, there is a need to bind between requested virtual network and PCI device/interface to be allocated as vNIC.
</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">On the Neutron side, there is a need to support networking configuration of the vNIC. Neutron should be able to identify the PCI device/macvtap interface in order to apply configuration. I think
it makes sense to provide neutron integration via dedicated Modular Layer 2 Mechanism Driver to allow PCI pass-through vNIC support along with other networking technologies.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">I haven't sorted through this yet. A neutron port could be associated with a PCI device or not, which is a common feature, IMHO. However, a ML2 driver may be needed specific to a particular
SRIOV technology. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">During the Havana Release, we introduced Mellanox Neutron plugin that enables networking via SRIOV pass-through devices or macvtap interfaces.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">We want to integrate our solution with PCI pass-through Nova support. I will be glad to share more details if you are interested.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Good to know that you already have a SRIOV implementation. I found out some information online about the mlnx plugin, but need more time to get to know it better. And certainly I'm
interested in knowing its details.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The PCI pass-through networking support is planned to be discussed during the summit:
</span><span lang="EN-US" style="color:black"><a href="http://summit.openstack.org/cfp/details/129">http://summit.openstack.org/cfp/details/129</a>.
</span><span lang="EN-US" style="color:#1F497D">I think it’s worth to drill down into more detailed proposal and present it during the summit, especially since it impacts both nova and neutron projects.
</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">I agree. Maybe we can steal some time in that discussion.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Would you be interested in collaboration on this effort? Would you be interested to exchange more emails or set an IRC/WebEx meeting during this week before the summit?</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Sure. If folks want to discuss it before the summit, we can schedule a webex later this week. Or otherwise, we can continue the discussion with email.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Regards,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Irena</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"> </span><span lang="EN-US" style="color:black"><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: 10pt; font-family: Tahoma, sans-serif; color: black; ">From:</span></b><span lang="EN-US" style="font-size: 10pt; font-family: Tahoma, sans-serif; color: black; "> Robert Li (baoli) [<a href="mailto:baoli@cisco.com">mailto:baoli@cisco.com</a>]
<br>
<b>Sent:</b> Friday, October 25, 2013 11:16 PM<br>
<b>To:</b> <a href="mailto:prashant.upadhyaya@aricent.com">prashant.upadhyaya@aricent.com</a>; Irena Berezovsky;
<a href="mailto:yunhong.jiang@intel.com">yunhong.jiang@intel.com</a>; <a href="mailto:chris.friesen@windriver.com">
chris.friesen@windriver.com</a>; <a href="mailto:yongli.he@intel.com">yongli.he@intel.com</a><br>
<b>Cc:</b> OpenStack Development Mailing List; Brian Bowen (brbowen); Kyle Mestery (kmestery); Sandhya Dasu (sadasu)<br>
<b>Subject:</b> Re: [openstack-dev] [nova] [neutron] PCI pass-through network support</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Hi Irena,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">This is Robert Li from Cisco Systems. Recently, I was tasked to investigate such support for Cisco's systems that support VM-FEX, which is a SRIOV technology supporting 802-1Qbh. I
was able to bring up nova instances with SRIOV interfaces, and establish networking in between the instances that employes the SRIOV interfaces. Certainly, this was accomplished with hacking and some manual intervention. Based on this experience and my study
with the two existing nova pci-passthrough blueprints that have been implemented and committed into Havana (<a href="https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base" id="yui_3_10_3_1_1382711548329_391"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(0, 51, 170); background-color: white; text-decoration: none; background-position: initial initial; background-repeat: initial initial; ">https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base</span></a></span><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(51, 51, 51); background-color: white; background-position: initial initial; background-repeat: initial initial; "> and<br>
</span><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(0, 51, 170); background-color: white; background-position: initial initial; background-repeat: initial initial; "><a href="https://blueprints.launchpad.net/nova/+spec/pci-passthrough-libvirt"><span style="font-size:10.5pt">https://blueprints.launchpad.net/nova/+spec/pci-passthrough-libvirt</span></a>), </span><span lang="EN-US" style="font-size:10.5pt;color:black"> I
registered a couple of blueprints (one on Nova side, the other on the Neutron side):</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><a href="https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov">https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov</a></span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"><a href="https://blueprints.launchpad.net/neutron/+spec/pci-passthrough-sriov">https://blueprints.launchpad.net/neutron/+spec/pci-passthrough-sriov</a></span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">in order to address SRIOV support in openstack. </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Please take a look at them and see if they make sense, and let me know any comments and questions. We can also discuss this in the summit, I suppose.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">I noticed that there is another thread on this topic, so copy those folks from that thread as well.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">thanks,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Robert</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">On 10/16/13 4:32 PM, "Irena Berezovsky" <<a href="mailto:irenab@mellanox.com">irenab@mellanox.com</a>> wrote:</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black"> </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">As one of the next steps for PCI pass-through I would like to discuss is the support for PCI pass-through vNIC.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">While nova takes care of PCI pass-through device resources management and VIF settings, neutron should manage their networking configuration.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">I would like to register asummit proposal to discuss the support for PCI pass-through networking.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">I am not sure what would be the right topic to discuss the PCI pass-through networking, since it involve both nova and neutron. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">There is already a session registered by Yongli on nova topic to discuss the PCI pass-through next steps.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">I think PCI pass-through networking is quite a big topic and it worth to have a separate discussion.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Is there any other people who are interested to discuss it and share their thoughts and experience?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Irena<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>