5f35b695bf
This patch provides a base to support multi version API. The existing code of functions for SOL specification was hard to understand and enhance since it is based on the code of legacy tacker API and they are connected with each other complicatedly. Therefore the code for SOL specification is newly created which is independent to the legacy tacker API so that it will be easy to maintain and enhance. This patch supports vnflcm v2 API (api_version 2.0.0) as a starting point. It supports less functions than the exsisting v1 API at the moment(Xena) but it will catch up with by the next release (Y). This patch makes supporting another API version easy when it will be supported in the future. Possibly it may thought to add v1 API to this code base. TODO: enhance UT/FT UT/FT is not sufficient at the moment. Additional UTs and FTs will be provided with another patches. Implements: blueprint multi-version-api Implements: blueprint support-nfv-solv3-start-and-terminate-vnf Implements: blueprint support-nfv-solv3-query-vnf-instances Implements: blueprint support-nfv-solv3-query-operation-occurrences Implements: blueprint support-nfv-solv3-subscriptions Change-Id: If76f315d8b3856e0eef9b8808b90f0b15d80d488
25 lines
902 B
YAML
25 lines
902 B
YAML
---
|
|
features:
|
|
- |
|
|
Support multi-version of RESTfulAPI. The client can use
|
|
both VNF LCM API "1.3.0" and "2.0.0" defined by ETSI NFV.
|
|
|
|
- |
|
|
Add new RESTful APIs of List VNF LCM API versions
|
|
and Show VNF LCM API versions based on ETSI NFV specifications.
|
|
They enable the client to retrieve supported versions of VNF LCM API.
|
|
|
|
- |
|
|
Add the following new version of RESTful APIs
|
|
based on ETSI NFV specifications.
|
|
Version "2.0.0" API of Create VNF, Delete VNF,
|
|
Instantiate VNF, Terminate VNF, List VNF, Show VNF,
|
|
List VNF LCM operation occurrence, Show VNF LCM operation occurrence,
|
|
Create subscription, List subscription, and Show subscription are added.
|
|
|
|
- |
|
|
VNF LCM API "2.0.0" provides a new type of userdata script
|
|
and utility functions to describe it.
|
|
They enable the user to freely operate HEAT to meet the unique
|
|
requirements of VNF.
|