<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
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.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='color:#1F497D'>Quick question: it seems we are
calling one end of the virtual wire a port and the other a vif. Is there a
reason to do that? Can we just call say that that a wire connects 2 ports?<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'>Also another interesting network
scenario is when there is a wire connecting 2 ports and you have a tap (for all
sorts of scenarios). I think the semantics of the tap might be quite
basic. <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'>debo <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 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
openstack-bounces+dedutta=cisco.com@lists.launchpad.net
[mailto:openstack-bounces+dedutta=cisco.com@lists.launchpad.net] <b>On Behalf
Of </b>Alex Neefus<br>
<b>Sent:</b> Monday, May 23, 2011 1:05 PM<br>
<b>To:</b> Ying Liu (yinliu2); openstack@lists.launchpad.net<br>
<b>Subject:</b> Re: [Openstack] [NetStack] Quantum Service API extension
proposal<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Hi All – <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 wanted to lend support to this
proposal, however I don’t think we should be so quick to say this whole
thing is an extension. <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'>We benefit a lot from having a
standard capabilities mechanism as part of our core Quantum API. I like
Ying’s key value method as well. I think it’s logical, clean and
scalable. I propose that basic read access of “cap” off of our
major objects: network, port, interface be included in our first release. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>So in summary I would like to
encourage us to add:<o:p></o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET /networks/{net_id}/conf<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET
/networks/{net_id}/ports/{port_id}/conf/<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET {entity}/VIF/conf/<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'><o:p> </o:p></span></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Each of these would return a
list of keys.<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'>Additionally Quantum base should
support <o:p></o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET /networks/{net_id}/conf/{key}<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET
/networks/{net_id}/ports/{port_id}/conf/{key}<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'>GET {entity}/VIF/conf/{key}<o:p></o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'><o:p> </o:p></span></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Where {key} is the name of
either a standard capability or an extention capability. We can define an error
code now to designate a capability not supported by the plugin. (i.e. 472
– CapNotSupported)<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'>Finally we don’t need to
standardize on every capability that might be supported if we provide this
simple mechanism. Specific capabilities Key,Value sets can be added later but
or included as vendor specific extensions.<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’m happy to add this to
the wiki if there is consensus. <span style='background:yellow;mso-highlight:
yellow'>Rick/Dan</span> – Maybe this should be a topic for Tuesdays
meeting. <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'>Alex</span><span
class=apple-style-span><span style='font-size:10.0pt;font-family:"Courier New";
color:black'><o:p></o:p></span></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>---<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Alex Neefus<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Senior System Engineer |
Mellanox Technologies<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>(o) 617.337.3116 | (m)
201.208.5771 | (f) 617.337.3019<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'><o:p> </o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'><o:p> </o:p></span></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Courier New";color:black'><o:p> </o:p></span></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 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
openstack-bounces+alex=mellanox.com@lists.launchpad.net
[mailto:openstack-bounces+alex=mellanox.com@lists.launchpad.net] <b>On Behalf
Of </b>Ying Liu (yinliu2)<br>
<b>Sent:</b> Saturday, May 21, 2011 1:10 PM<br>
<b>To:</b> openstack@lists.launchpad.net<br>
<b>Subject:</b> [Openstack] [NetStack] Quantum Service API extension proposal<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi all,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>We just posted a proposal for OpenStack Quantum Service API
extension on community wiki page at <a
href="http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view&target=quantum_api_extension.pdf">http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view&target=quantum_api_extension.pdf</a><o:p></o:p></p>
<p class=MsoNormal>or <o:p></o:p></p>
<p class=MsoNormal><a
href="http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view&target=quantum_api_extension.docx">http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view&target=quantum_api_extension.docx</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Please review and let us know your comments/suggestions. An
etherpad page is created for API extension discussion <a
href="http://etherpad.openstack.org/uWXwqQNU4s">http://etherpad.openstack.org/uWXwqQNU4s</a><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Best,<o:p></o:p></p>
<p class=MsoNormal>Ying<o:p></o:p></p>
</div>
</body>
</html>