Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-18 Thread Jay Pipes
On 04/17/2017 07:46 PM, Sridhar Ramaswamy wrote: I like this suggestion. Keyword 'vnf' is the closest to the unit of things orchestrated by Tacker. Building on that we can have, openstack vnf create - /create a single VNF based on TOSCA template/ openstack vnf service create - /create a service

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-17 Thread Sridhar Ramaswamy
Hi Jay, See inline ... On Fri, Apr 14, 2017 at 12:25 PM, Jay Pipes wrote: > 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

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-17 Thread Trinath Somanchi
-Original Message- From: Akihiro Motoki [mailto:amot...@gmail.com] Sent: Monday, April 17, 2017 12:32 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs 2017-04-15 12:44

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-17 Thread Akihiro Motoki
riginal Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Saturday, April 15, 2017 12:55 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs > > > > On 04/12/2017 03:08 AM, Trinath Somanchi wrote: > &g

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-14 Thread Trinath Somanchi
Pipes [mailto:jaypi...@gmail.com] Sent: Saturday, April 15, 2017 12:55 AM To: openstack-dev@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 comman

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-14 Thread Jay Pipes
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,

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-13 Thread Trinath Somanchi
ursday, April 13, 2017 8:17 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs networking-sfc has many overlapping areas with tacker and the command names can conflict,

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-12 Thread Akihiro Motoki
n...@nxp.com>* > > Mobile: +91 9866235130 <+91%2098662%2035130> | Off: +91 4033504051 > <+91%2040%203350%204051> > > [image: cid:image001.png@01D28854.B7934C80] > > > > *From:* Dean Troyer [mailto:dtro...@gmail.com] > *Sent:* Wednesday, April 12, 2

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-12 Thread Trinath Somanchi
ist (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi <trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>> wrote: Tacker being NFVO+VNFM - an NFV componen

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-12 Thread Dean Troyer
On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi wrote: > Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the > prefix. > Note that OSC itself does not use 'command prefixes', it names resources with enough specificity to make them unique. Sometimes

[openstack-dev] [Tacker][OSC] Command naming specs

2017-04-12 Thread Trinath Somanchi
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. We were struck in naming the below commands while aligning with the OSC naming specs. For the