<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 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Hi Jay-<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks for the suggestions, we have improved this to an extent [1].
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal">For 'openstack vnf service function chain create' we agreed to go with, 'openstack nfv chain create' or 'openstack vnf chain create'<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For ' openstack vnf forwardinggraph create' , you suggestion sounds good. We are thinking on 'openstack vnffg create' in simple terms.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have come up with a rule for certain commands which conflict with other OpenStack projects,'nfv' is prefixed to differentiate the commands.<o:p></o:p></p>
<p class="MsoNormal">The commands that may conflict include ``network-service``, ``classifier``, ``nfp``, ``chain`` and ``event``.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">[1] https://review.openstack.org/#/c/455188/14/specs/pike/python-openstackclient.rst<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks,<o:p></o:p></p>
<p class="MsoPlainText">Trinath Somanchi.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Digital Networking | NXP – Hyderabad – INDIA.<o:p></o:p></p>
<p class="MsoPlainText">Email: trinath.somanchi@nxp.com<o:p></o:p></p>
<p class="MsoPlainText">Mobile: +91 9866235130 | Off: +91 4033504051<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: Jay Pipes [mailto:jaypipes@gmail.com] <br>
Sent: Saturday, April 15, 2017 12:55 AM<br>
To: openstack-dev@lists.openstack.org<br>
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 04/12/2017 03:08 AM, Trinath Somanchi wrote:<o:p></o:p></p>
<p class="MsoPlainText">> Hi OSC team-<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> While implementing tacker-cli commands as OSC plugins [1], We are
<o:p></o:p></p>
<p class="MsoPlainText">> struck in command naming specifications.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
<o:p></o:p></p>
<p class="MsoPlainText">> prefix.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It's not *all* of NFV, though.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This problem, by the way, is an indication that Tacker might have too big a scope...and a scope that is very much tailored/purpose-built for Telcos/NFV. But whatever, I raised this concern during the project application as a member of
the TC and folks ignored me, so it is what it is I guess.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> We were struck in naming the below commands while aligning with the
<o:p></o:p></p>
<p class="MsoPlainText">> OSC naming specs.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> For the below commands, for readability, we have added ‘-‘ within the
<o:p></o:p></p>
<p class="MsoPlainText">> command names.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Like,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> network-service, vnf-forwarding-graph, <o:p>
</o:p></p>
<p class="MsoPlainText">> service-function-chain,<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> network-flow-classifier, network-forwarding-path.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I think what Dean and Akihiro were suggesting is to use "vnf" as the first "word" in the command list and then use space-delimited commands like so:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">openstack vnf network service create<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Or just leave off the "network" above, because, well, Tacker doesn't create any other type of service..., so:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">openstack vnf service create<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">and then<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">openstack vnf forwardinggraph create<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">and<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">openstack vnf service function chain create<o:p></o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">but then, you'll hit on the obvious overlap with networking-sfc, which will bring in the obvious question of "what's the difference between Tacker's SFC and networking-sfc's SFC?" which again should lead folks to question the scope of
Tacker in relation to other OpenStack projects...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best,<o:p></o:p></p>
<p class="MsoPlainText">-jay<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">__________________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">OpenStack Development Mailing List (not for usage questions)<o:p></o:p></p>
<p class="MsoPlainText">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
<span style="color:windowtext;text-decoration:none">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><span style="color:windowtext;text-decoration:none">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span></a><o:p></o:p></p>
</div>
</body>
</html>