PNFD validation based on SOL001 v2.5.1
VNF requirement has been updated with which must be supported in the PNFD. 

This Story covers the existing TOSCA validations executed against the the VNF packages. Based on this - test-only Story.
If there are any issues discovered, then this will be reported as a Bug, and Bug report will be linked to this Story.

The following CSAR file will be used here:
sample-pnf-1.0.1-SNAPSHOT.csar

Specific VNF Requirements to be covered:

• r87234
  The VNF or PNF package provided by a VNF or PNF vendor *MUST* be with TOSCA-Metadata directory (CSAR Option 1) as specified in ETSI GS NFV-SOL004.

• r35854
  The VNF Descriptor (VNFD) provided by VNF vendor MUST comply with TOSCA/YAML based Service template for VNF descriptor specified in ETSI NFV-SOL001.

• r15837
  Major TOSCA Types specified in ETSI NFV-SOL001 standard draft.

• r32155
  The VNFD provided by VNF vendor may use the below described TOSCA interface types. An on-boarding entity (ONAP SDC) MUST support them..

• r67895
  The VNFD provided by VNF vendor may use the below described TOSCA capabilities. An on-boarding entity (ONAP SDC) MUST support them.
• r17852
  The VNFD MAY include TOSCA/YAML definitions that are not part of NFV Profile. If provided, these definitions MUST comply with TOSCA Simple Profile in YAML v.1.2.
• r95321
  The VNFD provided by VNF vendor may use the below described TOSCA relationships. An on-boarding entity (ONAP SDC) MUST support them.

• r54356
  Data types used by NFV node and is based on TOSCA/YAML constructs specified in draft GS NFV-SOL 001. The node data definitions/attributes used in VNFD MUST comply.