Support VNF create with direct VNFD template input

Registered by Sridhar Ramaswamy on 2016-08-12

Currently VNF Catalog is an integral part of Tacker solution. VNFD template should've been populated in the VNF Catalog before can instantiated. However, when Tacker is used just as a G-VNFM there are scenarios where the VNF / NFV Catalog exists outside Tacker. For those solutions it doesn't make sense to use Tacker's VNF Catalog. This blueprint will bring in the support for making VNFD id optional for tacker vnf-create. Instead support an option where VNFD template can be passed in directly to the vnf-create API / CLI.

Blueprint information

Status:
Complete
Approver:
Sridhar Ramaswamy
Priority:
Low
Drafter:
Sridhar Ramaswamy
Direction:
Needs approval
Assignee:
Janki Chhatbar
Definition:
Approved
Series goal:
Accepted for ocata
Implementation:
Implemented
Milestone target:
milestone icon ocata-3
Started by
Janki Chhatbar on 2016-12-20
Completed by
Sridhar Ramaswamy on 2017-02-16

Related branches

Sprints

Whiteboard

Targeted for Ocata

Gerrit topic: https://review.openstack.org/#q,topic:bp/vnf-inline-template,n,z

Addressed by: https://review.openstack.org/405381
    Support VNF create with direct VNFD template input

Addressed by: https://review.openstack.org/416215
    Support VNF create from inline template

Addressed by: https://review.openstack.org/426802
    Allow VNF creation from inline template

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.