HPA Impact on the VNF SDK Project
- Alex Vul
Background
Assumptions & Decisions
Assumption/Decision | ||
|---|---|---|
| 1 | Hardware platform capability requirements shall be specified as a VNFD encoding agnostic format, order to accommodate alternative VNFD representations and encoding formats, such as YANG, HEAT, etc... The requirements shall be specified as a comma separated list of of tuples, as defined on the HPA Requirement & Capability Specification page. | |
| 2 | Hardware platform capability requirement specificaiton shall be limited to TOSCA grammar based VNFD templates, encoded using OASIS TOSCA YAML grammar and based on the ONAP VNFD information model definition for R2. | |
| 3 | For TOSCA grammar based VNFDs, hardware platform capability requirements shall be specified using one or more TOSCA capability clauses, with opaque string values containing comma separated tuples, as described above. | |
| 4 | If use of alternatively encoded VNF descriptors is desired, additional migration tools shall be provided as part of the VNF SDK. | |
| 5 | HEAT to TOSCA migration tools shall be provided for already existing VNFs certified for use with ECOMP. |
Work Items
Work Item | Priority | Status | |
|---|---|---|---|
1 | Creation of a VNFD template for use in R2 (Beijing). | P1 | |
2 | Implementation of parsing/search utilities for the hardware platform requirement specification format | P1 | |
3 | Implementation of HEAT to TOSCA template migration tools for ECOMP VNF packages | P2 |