[openstack-dev] [Tacker][OSC] Command naming specs
Jay Pipes
jaypipes at gmail.com
Tue Apr 18 13:06:51 UTC 2017
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 using a collection of VNFs/
> openstack vnf graph create - /create a forwarding graph using a
> collection of VNFs/
++ That is concise and easy to understand/read.
> It is not an overlap per-se, it is more at a different abstraction
> level. The later is a general purpose, lower-level SFC API based on
> neutron ports. Former is a higher level YAML (TOSCA) template based
> description of a SFC specially geared for NFV use-cases - implemented
> using the lower-level networking-sfc APIs. It is analogous to Heat
> OS::Nova::Server <-> Nova Compute APIs.
Understood, thanks for the clarification Sridhar!
Best,
-jay
More information about the OpenStack-dev
mailing list