Open Stack

Hi Jay-



Thanks for the suggestions, we have improved this to an extent [1].


For  'openstack vnf service function chain create' we agreed to go with, 'openstack nfv chain create' or 'openstack vnf chain create'

For ' openstack vnf forwardinggraph create' , you suggestion sounds good. We are thinking on 'openstack vnffg create' in simple terms.

We have come up with a rule for certain commands which conflict with other OpenStack projects,'nfv' is prefixed to differentiate the commands.
The commands that may conflict include ``network-service``, ``classifier``, ``nfp``, ``chain`` and ``event``.



[1] https://review.openstack.org/#/c/455188/14/specs/pike/python-openstackclient.rst



Thanks,

Trinath Somanchi.



Digital Networking | NXP – Hyderabad – INDIA.

Email: trinath.somanchi at nxp.com

Mobile: +91 9866235130 | Off: +91 4033504051





-----Original Message-----
From: Jay Pipes [mailto:jaypipes at gmail.com]
Sent: Saturday, April 15, 2017 12:55 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs



On 04/12/2017 03:08 AM, Trinath Somanchi wrote:

> Hi OSC team-

>

> While  implementing tacker-cli commands as OSC plugins [1], We are

> struck in command naming specifications.

>

> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the

> prefix.



It's not *all* of NFV, though.



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.



> We were struck in naming the below commands while aligning with the

> OSC naming specs.

>

> For the below commands, for readability, we have added ‘-‘ within the

> command names.

>

> Like,

>

>           network-service,  vnf-forwarding-graph,

> service-function-chain,

>

>     network-flow-classifier, network-forwarding-path.



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:



openstack vnf network service create



Or just leave off the "network" above, because, well, Tacker doesn't create any other type of service..., so:



openstack vnf service create



and then



openstack vnf forwardinggraph create



and



openstack vnf service function chain create





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...



Best,

-jay



__________________________________________________________________________

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170415/7f931d8d/attachment.html>