<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: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 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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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";
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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: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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Alan,<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">After completing the first pass of this I agree that the results could be misinterpreted. As you correctly point out, most of the network functions that are being looking at will be developed and deployed leveraging
a range of configuration options and taking into account considerations such as performance and topology for that class of device. I reviewed the list primarily thinking about some gaps that the blueprints may be closing relating to higher performing VM based
solutions. The implementations can be so very varied, so even in the bare metal case you mention, SR-IOV can offer some additional benefits to the workloads that some implementations may choose to leverage.
<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 also agree that we need to focus in on a couple of sample applications and prioritise what needs to be done based on a more detailed review of the requirements.
<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,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Adrian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><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:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB"> Alan Kavanagh
[mailto:alan.kavanagh@ericsson.com] <br>
<b>Sent:</b> Wednesday, June 11, 2014 4:32 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions); Steve Gordon; ITAI MENDELSOHN (ITAI); Chris Wright; Stephen Wong; Nicolas Lemieux<br>
<b>Subject:</b> Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and context<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">Hi Adrian et.al<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">Adrian thanks for taking a stab at this, I think the use case list is a little long but good to put on the map. One item I would point out is that its fairly difficult and perhaps misleading to map
the blueprints list to the ETSI NFV use case, for example you can argue that based on configuration and deployment of say vCPE some may require VLAN Trunking, others will not. Similarly for SR-IOV support when you a Transport node that consumes the total CPU
and NIC available on the host and would in some cases be provisioned on bare metal SR-IOV is not a required feature set. Also some of these would not require anything in addition to support apart from what we already have in Openstack, for example in the case
of CDN do we needed additional feature sets, imho apart from the nice state aware scheduling and VM allocation based on specific attributes required (specific PCI device type, topology based placement, on board SSD, etc) and IP end point for delivery, do
we need anything else beyond this?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">Perhaps what might be more beneficial is to ensure we can deploy a given app in the current OS distro and identify the necessary configuration attributes we would need to expose, would that be a
good way forward? Interested to hear from others on this front. A suggestion, is we start with use cases 2 and 7 that are more well defined and simpler to address and this is where I believe Itai had a good statement of “not boiling the ocean”, lets start
with some simple ones that are well defined and well known and don’t have too many intrinsic configurations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">/Alan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><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" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA">
Hoban, Adrian [<a href="mailto:adrian.hoban@intel.com">mailto:adrian.hoban@intel.com</a>]
<br>
<b>Sent:</b> June-10-14 10:20 PM<br>
<b>To:</b> Steve Gordon; ITAI MENDELSOHN (ITAI); Chris Wright; Stephen Wong; Nicolas Lemieux<br>
<b>Cc:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and context<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Hi Folks,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">I'd like to propose the following text for the NFV wiki giving a high level intro to the ETSI-NFV use cases. It builds on the info Itai and Steve posted below.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Reference: <a href="http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf">
http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf</a>
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #1: Network Functions Virtualisation Infrastructure as a Service<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- This is a reasonably generic IaaS requirement.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #2: Virtual Network Function as a Service (VNFaaS).<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- This primarily targets Customer Premise Equipment (CPE) devices such as access routers, enterprise firewall, WAN optimizers etc. with some Provider Edge devices possible at a later date. ETSI-NFV Performance
& portability considerations will apply to deployments that strive to meet high performance and low latency considerations.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #3: Virtual Network Platform as a Service (VNPaaS).
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"> - This is similar to #2 but at the service level. At larger scale and not at the "app" level only.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #4: VNF Forwarding Graphs<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- Dynamic connectivity between apps in a "service chain".<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #5: Virtualisation of Mobile Core Network and IMS.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"> - Primarily focusing on Evolved Packet Core appliances such as the Mobility Management Entity (MME), Serving Gateway (S-GW), etc. and the IP Multimedia Subsystem (IMS).<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #6: Virtualisation of Mobile base station<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- Focusing on parts of the Radio Access Network such as eNodeB's, Radio Link Control and Packet Data Convergence Protocol, etc..<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #7: Virtualisation of the Home Environment.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"> - Similar to #2, but with a focus on virtualising residential devices instead of enterprise devices. Covers DHCP, NAT, PPPoE, Firewall devices, etc.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #8: Virtualisation of CDNs<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- Content Delivery Networks focusing on video traffic delivery.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Use Case #9: Fixed Access Network Functions Virtualisation<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">- Wireline related access technologies.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">========<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">For the ETSI-NFV use case to OpenStack blueprint mapping, I would also like to propose that we add a column to the blueprints. I've taken a first stab at this.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1039" style="width:779.0pt;margin-left:34.85pt;border-collapse:collapse">
<tbody>
<tr style="height:15.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:15.0pt">
<p class="MsoNormal"><b><span style="color:black;mso-fareast-language:EN-GB">Description<o:p></o:p></span></b></p>
</td>
<td width="477" nowrap="" valign="top" style="width:358.0pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt;height:15.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">NFV Use Case Comments<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Support two interfaces from one VM attached to the same network<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 TBD?<br>
#3 TBD?<br>
#4 TBD?<br>
#5 TBD?<br>
#6 TBD?<br>
#7 TBD?<br>
#8 TBD?<br>
#9 TBD?<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">VLAN trunking networks for NFV<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 TBD?<br>
#3 TBD?<br>
#4 TBD?<br>
#5 TBD?<br>
#6 TBD?<br>
#7 TBD?<br>
#8 TBD?<br>
#9 TBD?<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Permit unaddressed interfaces for NFV use cases<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 TBD?<br>
#3 TBD?<br>
#4 TBD?<br>
#5 TBD?<br>
#6 TBD?<br>
#7 TBD?<br>
#8 TBD?<br>
#9 TBD?<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:150.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">SR-IOV Networking Support<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 _Potential_ intersect if forwarding graph makes any particular request about the port connectivity.
<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 TBD?<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Support for NUMA and VCPU topology configuration<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Virt driver guest vCPU topology configuration<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Virt driver guest NUMA node placement & topology<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Virt driver large page allocation for guest RAM *<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Virt driver pinning guest vCPUs to host pCPUs<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">I/O (PCIe) Based NUMA Scheduling<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Soft affinity support for server groups<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 TBD?<br>
#3 TBD?<br>
#4 TBD?<br>
#5 TBD?<br>
#6 TBD?<br>
#7 TBD?<br>
#8 TBD?<br>
#9 TBD?<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:150.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Open vSwitch-based Security Groups: Open vSwitch Implementation of FirewallDriver<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed in the non-SR-IOV based deployments.<br>
#3 TBD?<br>
#4 vSwitch configuration may be needed to complete the forwarding graph (service chain).
<br>
#5 Needed in the non-SR-IOV based deployments.<br>
#6 TBD?<br>
#7 Needed in the non-SR-IOV based deployments.<br>
#8 TBD?<br>
#9 Needed in the non-SR-IOV based deployments.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Framework for Advanced Services in Virtual Machines<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Potential lifecycle management support<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Potential lifecycle management support<br>
#6 Potential lifecycle management support<br>
#7 Potential lifecycle management support<br>
#8 Potential lifecycle management support<br>
#9 Potential lifecycle management support<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Neutron Services Insertion, Chaining, and Steering<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 May need to chain multiple functions to deliver a service.<br>
#3 TBD?<br>
#4 Closely coupled requirement needed to deliver on a forwarding graph.<br>
#5 May need to chain multiple functions to deliver a service.<br>
#6 May need to chain multiple functions to deliver a service.<br>
#7 May need to chain multiple functions to deliver a service.<br>
#8 May need to chain multiple functions to deliver a service.<br>
#9 May need to chain multiple functions to deliver a service.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Schedule vms per flavour cpu overcommit<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:225.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">OVF Meta-Data Import via Glance<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed as one optional path to auto import platform feature requests to meet performance targets.
<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed as one optional path to auto import platform feature requests to meet performance targets.
<br>
#6 Needed as one optional path to auto import platform feature requests to meet performance targets.
<br>
#7 Needed as one optional path to auto import platform feature requests to meet performance targets.
<br>
#8 Needed as one optional path to auto import platform feature requests to meet performance targets.
<br>
#9Needed as one optional path to auto import platform feature requests to meet performance targets.
<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Open vSwitch to use patch ports in place of veth pairs for vlan n/w<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed in the non-SR-IOV based deployments.<br>
#3 TBD?<br>
#4 Closely coupled requirement needed to deliver on a forwarding graph.<br>
#5 Needed in the non-SR-IOV based deployments.<br>
#6 TBD?<br>
#7 Needed in the non-SR-IOV based deployments.<br>
#8 TBD?<br>
#9 Needed in the non-SR-IOV based deployments.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Libvirt hugepage backed memory support<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons.<br>
#3 TBD?<br>
#4 Closely coupled requirement needed to deliver on a forwarding graph.<br>
#5 Needed for performance reasons.<br>
#6 Needed for performance reasons.<br>
#7 Needed for performance reasons.<br>
#8 Needed for performance reasons.<br>
#9 Needed for performance reasons.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Support userspace vhost in ovs vif bindings<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed in the non-SR-IOV based deployments.<br>
#3 TBD?<br>
#4 Closely coupled requirement needed to deliver on a forwarding graph.<br>
#5 Needed in the non-SR-IOV based deployments.<br>
#6 TBD?<br>
#7 Needed in the non-SR-IOV based deployments.<br>
#8 TBD?<br>
#9 Needed in the non-SR-IOV based deployments.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:150.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">NIC state aware scheduling<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:150.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed to help with service delivery<br>
#3 TBD?<br>
#4 Need to understand if the ports are up when deploying the service chain.<br>
#5 Needed to help with service delivery<br>
#6 Needed to help with service delivery<br>
#7 Needed to help with service delivery<br>
#8 Needed to help with service delivery<br>
#9 Needed to help with service delivery<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Add PCI and PCIe device capability aware scheduling<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons<br>
#6 Needed for performance reasons<br>
#7 Needed for performance reasons<br>
#8 Needed for performance reasons<br>
#9 Needed for performance reasons<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Snabb NFVmechanism driver<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed in the non-SR-IOV based deployments.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed in the non-SR-IOV based deployments.<br>
#6 TBD?<br>
#7 Needed in the non-SR-IOV based deployments.<br>
#8 TBD?<br>
#9 Needed in the non-SR-IOV based deployments.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">VIF_SNABB (qemu vhost-user) support<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed in the non-SR-IOV based deployments.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed in the non-SR-IOV based deployments.<br>
#6 TBD?<br>
#7 Needed in the non-SR-IOV based deployments.<br>
#8 TBD?<br>
#9 Needed in the non-SR-IOV based deployments.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:225.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Solver Scheduler - complex constraints scheduler with NFV use cases<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Possibly needed for smarter scheduling decision making to help with performance.
<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Possibly needed for smarter scheduling decision making to help with performance.
<br>
#6 Possibly needed for smarter scheduling decision making to help with performance.<br>
#7 Possibly needed for smarter scheduling decision making to help with performance.<br>
#8 Possibly needed for smarter scheduling decision making to help with performance.<br>
#9 Possibly needed for smarter scheduling decision making to help with performance.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Discless VM<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 TBD?<br>
#3 TBD?<br>
#4 TBD?<br>
#5 TBD?<br>
#6 TBD?<br>
#7 TBD?<br>
#8 TBD?<br>
#9 TBD?<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Network QoS API<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons<br>
#3 TBD?<br>
#4 Needed to capture network QoS aspects of forwarding graph.<br>
#5 Needed for performance reasons<br>
#6 Needed for performance reasons<br>
#7 Needed for performance reasons<br>
#8 Needed for performance reasons<br>
#9 Needed for performance reasons<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Persist scheduler hints<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for performance reasons on migration.<br>
#3 TBD?<br>
#4 TBD?<br>
#5 Needed for performance reasons on migration.<br>
#6 Needed for performance reasons on migration.<br>
#7 Needed for performance reasons on migration.<br>
#8 Needed for performance reasons on migration.<br>
#9 Needed for performance reasons on migration.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:135.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Port mirroring<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:135.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Needed for some specialized use cases.<br>
#3 TBD?<br>
#4 Needed based on forwarding graph for specialized use cases.<br>
#5 Needed for some specialized use cases.<br>
#6 Needed for some specialized use cases.<br>
#7 Needed for some specialized use cases.<br>
#8 TBD?<br>
#9 Needed for some specialized use cases.<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:225.0pt">
<td width="561" nowrap="" valign="top" style="width:421.0pt;border:solid windowtext 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">Traffic Steering Abstraction<o:p></o:p></span></p>
</td>
<td width="477" valign="top" style="width:358.0pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;height:225.0pt">
<p class="MsoNormal"><span style="color:black;mso-fareast-language:EN-GB">#1 is a broadly applicable IaaS requirement.
<br>
#2 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<br>
#3 TBD?<br>
#4 Closely coupled requirement needed to deliver on a forwarding graph.<br>
#5 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<br>
#6 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<br>
#7 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<br>
#8 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<br>
#9 Similar to "Neutron Services Insertion, Chaining, and Steering". May need to chain multiple functions to deliver a service.<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Let’s discuss in our meeting tomorrow.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Regards,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Adrian<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><span lang="EN-US" style="mso-fareast-language:EN-GB">-----Original Message-----<br>
From: Steve Gordon [<a href="mailto:sgordon@redhat.com">mailto:sgordon@redhat.com</a>]
<br>
Sent: Tuesday, June 10, 2014 5:15 PM<br>
To: Stephen Wong<br>
Cc: ITAI MENDELSOHN (ITAI); OpenStack Development Mailing List (not for usage questions); Nicolas Lemieux; Chris Wright; NICOLAS LEMIEUX; Hoban, Adrian<br>
Subject: Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and context</span><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">----- Original Message -----<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> From: "Stephen Wong" <<a href="mailto:stephen.kf.wong@gmail.com"><span style="color:windowtext;text-decoration:none">stephen.kf.wong@gmail.com</span></a>><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> To: "ITAI MENDELSOHN (ITAI)" <<a href="mailto:itai.mendelsohn@alcatel-lucent.com"><span style="color:windowtext;text-decoration:none">itai.mendelsohn@alcatel-lucent.com</span></a>>,
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> "OpenStack Development Mailing List (not for usage questions)"
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <<a href="mailto:openstack-dev@lists.openstack.org"><span style="color:windowtext;text-decoration:none">openstack-dev@lists.openstack.org</span></a>><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> Hi,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> Perhaps I have missed it somewhere in the email thread? Where is
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> the use case => bp document we are supposed to do for this week? Has
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> it been created yet?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> Thanks,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> - Stephen<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Hi,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Itai is referring to the ETSI NFV use cases document [1] and the discussion is around how we distill those - or a subset of them - into a more consumable format for an OpenStack audience on the Wiki. At this
point I think the best approach is to simply start entering one of them (perhaps #5) into the Wiki and go from there. Ideally this would form a basis for discussing the format etc.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Thanks,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Steve<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">[1] <a href="http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf">
<span style="color:windowtext;text-decoration:none">http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf</span></a><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> On Tue, Jun 10, 2014 at 2:00 AM, MENDELSOHN, ITAI (ITAI) <
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <a href="mailto:itai.mendelsohn@alcatel-lucent.com">
<span style="color:windowtext;text-decoration:none">itai.mendelsohn@alcatel-lucent.com</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > Shall we continue this discussion?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > Itai<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > On 6/9/14 8:54 PM, "Steve Gordon" <<a href="mailto:sgordon@redhat.com"><span style="color:windowtext;text-decoration:none">sgordon@redhat.com</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >----- Original Message -----<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> From: "Steve Gordon" <<a href="mailto:sgordon@redhat.com"><span style="color:windowtext;text-decoration:none">sgordon@redhat.com</span></a>><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> To: "ITAI MENDELSOHN (ITAI)"
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >><<a href="mailto:itai.mendelsohn@alcatel-lucent.com"><span style="color:windowtext;text-decoration:none">itai.mendelsohn@alcatel-lucent.com</span></a>>,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>"OpenStack Development Mailing List (not for usage<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> Just adding openstack-dev to the CC for now :).<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ----- Original Message -----<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > From: "ITAI MENDELSOHN (ITAI)"
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > <<a href="mailto:itai.mendelsohn@alcatel-lucent.com"><span style="color:windowtext;text-decoration:none">itai.mendelsohn@alcatel-lucent.com</span></a>><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Subject: Re: NFV in OpenStack use cases and context<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Can we look at them one by one?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 1 - It's pure IaaS<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 2 - Virtual network function as a service. It's
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > actually<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>about<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > exposing services to end customers (enterprises) by the service<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>provider.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 3 - VNPaaS - is similar to #2 but at the service
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > level. At<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>larger<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > scale and not at the "app" level only.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 4 - VNF forwarding graphs. It's actually about dynamic
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > connectivity between apps.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 5 - vEPC and vIMS - Those are very specific (good)
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > examples<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>of SP<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > services to be deployed.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 6 - virtual mobile base station. Another very specific<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>example,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > with different characteristics than the other two above.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 7 - Home virtualisation.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Use case 8 - Virtual CDN<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > As I see it those have totally different relevancy to OpenStack.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Assuming we don't want to boil the ocean hereŠ<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > 1-3 seems to me less relevant here.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > 4 seems to be a Neutron area.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > 5-8 seems to be usefully to understand the needs of the NFV
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > apps. The<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>use<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > case can help to map those needs.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > For 4 I guess the main part is about chaining and Neutron between DCs.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Soma may call it SDN in WAN...<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > For 5-8 at the end an option is to map all those into:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > -performance (net BW, storage BW mainly). That can be mapped to<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>SR-IOV,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > NUMA. Etc'<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > -determinism. Shall we especially minimise "noisy" neighbours.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Not<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>sure<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > how NFV is special here, but for sure it's a major concern for
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > lot of<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>SPs.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > That can be mapped to huge pages, cache QOS, etc'.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > -overcoming of short term hurdles (just because of apps
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > migrations issues). Small example is the need to define the
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > tick policy of KVM<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>just<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > because that's what the app needs. Again, not sure how NFV
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > special it<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>is,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > and again a major concern of mainly application owners in the
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > NFV<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >>domain.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >> > Make sense?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >Hi Itai,<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >This makes sense to me. I think what we need to expand upon, with
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >the ETSI NFV documents as a reference, is a two to three paragraph
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >explanation of each use case explained at a more basic level -
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >ideally on the Wiki page. It seems that use case 5 might make a
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >particularly good initial target to work on fleshing out as an
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >example? We could then look at linking the use case to concrete
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >requirements based on this, I suspect we might want to break them down into:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >a) The bare minimum requirements for OpenStack to support the use
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >case at all. That is, requirements that without which the VNF
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >simply can not function.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >b) The requirements that are not mandatory but would be beneficial
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >for OpenStack to support the use case. In particularly that might
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >be requirements that would improve VNF performance or reliability
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >by some margin (possibly significantly) but which it can function
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >without if absolutely required.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >Thoughts?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > >Steve<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> > ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> ><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">> <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">--<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Steve Gordon, RHCE<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:36.0pt">Product Manager, Red Hat Enterprise Linux OpenStack Platform Red Hat Canada (Toronto, Ontario)<o:p></o:p></p>
<p style="margin-left:36.0pt">--------------------------------------------------------------<br>
Intel Shannon Limited<br>
Registered in Ireland<br>
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare<br>
Registered Number: 308263<br>
Business address: Dromore House, East Park, Shannon, Co. Clare<o:p></o:p></p>
<p style="margin-left:36.0pt">This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact
the sender and delete all copies.<o:p></o:p></p>
</div>
<p>--------------------------------------------------------------<br>
Intel Shannon Limited<br>
Registered in Ireland<br>
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare<br>
Registered Number: 308263<br>
Business address: Dromore House, East Park, Shannon, Co. Clare</p>
<p>This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.</p>
<p></p></body>
</html>