<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: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 12 (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;}
@font-face
{font-family:Verdana;
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:12.0pt;
font-family:"Times New Roman","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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>At the meeting I was not convinced that the name needs to be optional. I believe is need to be ‘not optional’ and ‘unique’.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>My perspective is that a network should be created with a name. It is the systems responsibility to assign a UUID to it as it will be used by the system for referring to it internally. Needless to say that UUID are alright to use between machines and when humans get involved reasonable names are useful.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Example: I create a network with a name ‘vlan3’ – (hopefully used for deploying vlanid=3) and much later (maybe a week later) I want to deploy a VM which will use this network. From the UI is will be hard to refer to this network using a UUID.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>(it is pretty similar to file names and inodes, as a human I am glad I never think in terms of inodes I am happy with filenames)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-Shiv<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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"'> netstack-bounces+sharis=brocade.com@lists.launchpad.net [mailto:netstack-bounces+sharis=brocade.com@lists.launchpad.net] <b>On Behalf Of </b>Yong Sheng Gong<br><b>Sent:</b> Tuesday, July 17, 2012 1:31 AM<br><b>To:</b> Salvatore Orlando<br><b>Cc:</b> OpenStack Development Mailing List; netstack@lists.launchpad.net<br><b>Subject:</b> Re: [Netstack] [openstack-dev] [Quantum] Starting a discussion on the official spec for v2 API<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hi,<br>I thought we agreed to make the name optional and up to user to decide its uniqueness at meeting.<br><br>Thanks<br>Yong Sheng Gong<br><br><br><span style='color:#990099'>-----Salvatore Orlando <a href="mailto:sorlando@nicira.com"><sorlando@nicira.com></a> wrote: -----</span><o:p></o:p></span></p><div><div style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt'><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>From: Salvatore Orlando <a href="mailto:sorlando@nicira.com"><sorlando@nicira.com></a><br>Date: 07/17/2012 03:30PM<br>Cc: <a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a><br>Subject: [openstack-dev] [Quantum] Starting a discussion on the official spec for v2 API<br><br>Hello people of Quantum!<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>As the Folsom release approaches, it is time to gather together and finalize the specification for the v2 API, so that the Openstack-doc team might cast it in stone for the sake of the Quantum users!<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>In order to make this happen, it looks like there are just a few bits that needs to be agreed upon, and I think they can be summarized as follows:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>- 'name' attributes and whether they should be mandatory. It looks like we all agree we want them, but it has to be decided whether <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> i) they should be unique or not.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> ii) they should be mandatory or not.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>- 'public' attribute for networks. As we did not get negative feedback on the proposal, I am going to assume nobody has strong opinions against this decision.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>- security group API. We have a blueprint open and targeted to F-3 (<a href="https://blueprints.launchpad.net/quantum/+spec/quantum-security-groups">https://blueprints.launchpad.net/quantum/+spec/quantum-security-groups</a>). Personally I do not feel it is a good idea at this stage proposing them for the core v2 API in Folsom. Apart from the necessary discussion concerning the APIs, we will need support across all the plugins, which is hardly going to happen IMHO. If you have a different opinion, this is the right thread to shout it!<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> - NOTE: Leaving the security groups outside of Quantum core API also means that we *must* ensure Quantum still allows Nova to use its own firewall drivers. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>- L3 features (<a href="https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat">https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat</a>): among the various sub-blueprints in which this blueprint can be broken, there's one concerning APIs. As I have not followed the development of this particular blueprint, I'll leave it to Dan whether L3 & NAT APIs should be part of Folsom core.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>From my perspective, the above list includes all the items concerning the Quantum v2 API which have not yet stabilized. Please do let me know if I forgot anything.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Thanks and have a good day,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Salvatore<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p></div></div></div></div></body></html>