...
Conformance to HEAT or TOSCA Templates, as defined by ONAP Requirements.
- Conformance to ONAP VNFRqmts documentation which will integrate other SDO requirements (ie, 5G, BBF, ETSI,...)
- Conformance to ONAP interfaces.
Documentation of VNF is available.
...
VNF Validation:
On-boarding: Validate the VNF Artifact(s) is able to be "consumed" by an ONAP instance.
Open questions: 1) What are the requirements defined for "On-boarding?" What is the requirement for the "ONAP instance?" 3) Is there a requirement for backwards compatibility? 4) Besides ONAP are there other organizations defining this?
- Open question: 5) ONAP instance: does it mean MANO, or does it include VNFM.
Instantiation: Validate the VNF can be "launched" by an ONAP instance on top of an NFVI.
Open questions: 1) What is the requirements for ONAP Instance? 2) What is the requirements for the NFVI? 3) What are the requirements for the "VNF launch?"
Validate various life-cycle operations are possible with the VNF running on the ONAP Instance.
Open questions: 1) What the required "life-cycle operations?" 2) What the requirements for each "operation?" 3) What are the requirements for the "ONAP instance?"
- Life Cycle Operations of VNF (long term vision) - my version of FCAPS:
- Fault Management
- Capacity Management
- Billing/Accounting Management
- Performance Management
- Security Management
- Open question: does it relate to MANO, or does it include VNFM (generic vs specific).:
- NFVI Validation:
- Instantiate NFVI/VIM
- Life Cycle of NFVI/VIM - Healthcheck?
...