Development Time VNF Representations
HEAT
- ETSI NFV SOL001
- K8S HELM
What VNF TOSCA template flavor(s) to adopt for Dublin (e.g. SOL001 templates vs. AID templates)?
On-Boarding Time Representation
- Continue to support SOL001 VNF TOSCA templates
- Use v2.5.1 of SOL001 specification
Design-Time Representation
- Continue to support SOL001 specification (for pure ETSI NVF)
- NOTE - for now, the focus is on VNFD's and PNFD's only. Will need to revisit for specification of NS's
- Use TOSCA templates for K8S support
- Continue to support AID (for HEAT only)
Will SDC design tools in Dublin support creation of VNF TOSCA templates based on agreed upon flavor(s) and version(s)?
Design-Time Representation
SDC design tools will continue to generate AID TOSCA templates for service definitions
- No other template flavor will be generated
What VNF TOSCA template grammar version(s) to adopt for Dublin?
On-Boarding Time Representation
- TOSCA Simple YAML Profile v1.2+
Design-Time Respresention
- TOSCA Simple YAML Profile v1.2+ for SOL001 compliant templates
- AID Grammar version - TBD
Architecture/Design Requirements for ONAP Dublin Release
| ID | Description |
|---|---|
| 1 | Support for multiple flavors/versions of TOSCA VNFD templates |
| 2 | Support for multiple versions of TOSCA language/grammar |
| 3 | Support for ETSI NFV SOL001 specification v2.5.1 templates |
| 4 | Support for for TOSCA Simple YAML Profile v1.2 and v1.3 |
| 5 | A "registry" approach for configurable and modifiable properties |
| 6 | Preservation of original on-boarded template semantics and content |
| 7 | Support for alternative design-time tool chains |
1 Comment
Viswanath Kumar Skand Priya
Hi Alexander Vul,
Is this is the final version of recommendation from TOSCA Task Force ? Has this been endorsed both by ARC and TSC ? Are the respective component PTLs been notified on the changes? Can R4 successfully do a TOSCA orchestration of any VNF ( without hardcoded flows from SO & VF-C side? ) ?