VNF TOSCA Requirements

11 requirements containing "TOSCA" in Casablanca

ID	Content	Target	Keyword	Section Name
R-95321	The VNFD provided by VNF vendor may use the below described TOSCA relationships. An on-boarding entity (ONAP SDC) MUST support them. tosca.relationships.nfv.VirtualBindsTo This relationship type represents an association relationship between VDU and CP node types. tosca.relationships.nfv.VirtualLinksTo This relationship type represents an association relationship between the VduCpd's and VirtualLinkDesc node types.	VNF	MUST	Relationship Types
R-87234	The VNF package provided by a VNF vendor MAY be either with TOSCA-Metadata directory (CSAR Option 1) or without TOSCA-Metadata directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding entity (ONAP SDC) must support both options. Note: SDC supports only the CSAR Option 1 in Casablanca. The Option 2 will be considered in future ONAP releases,	VNF	MAY	VNF Package Structure and Format
R-67895	The VNFD provided by VNF vendor may use the below described TOSCA capabilities. An on-boarding entity (ONAP SDC) MUST support them. tosca.capabilities.nfv.VirtualBindable A node type that includes the VirtualBindable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualBindsTo relationship type. tosca.capabilities.nfv.VirtualLinkable A node type that includes the VirtualLinkable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualLinksTo relationship. tosca.capabilities.nfv.ExtVirtualLinkable A node type that includes the ExtVirtualLinkable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualLinksTo relationship. Note: This capability type is used in Casablanca how it does not exist in the last SOL001 draft tosca.capabilities.nfv.VirtualCompute and tosca.capabilities.nfv.VirtualStorage includes flavours of VDU	VNF	MUST	Capability Types
R-54876	The below table describes the data types used for LCM configuration and is based on TOSCA constructs specified in draft GS NFV-SOL 001. The LCM configuration data elements used in VNFD MUST comply with the below table.	VNF	MUST	Data Types
R-54356	The below table includes the 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 with the below table.	VNF	MUST	Data Types
R-51347	The VNF package MUST be arranged as a CSAR archive as specified in TOSCA Simple Profile in YAML 1.2.	VNF	MUST	VNF Package Structure and Format
R-35854	The VNF Descriptor (VNFD) provided by VNF vendor MUST comply with TOSCA/YAML based Service template for VNF descriptor specified in ETSI NFV-SOL001. Note: As the ETSI NFV-SOL001 is work in progress the below tables summarizes the TOSCA definitions agreed to be part of current version of NFV profile and that VNFD MUST comply with in ONAP Release 2+ Requirements.	VNF	MUST	General
R-32155	The VNFD provided by VNF vendor may use the below described TOSCA interface types. An on-boarding entity (ONAP SDC) MUST support them. tosca.interfaces.nfv.vnf.lifecycle.Nfv supports LCM operations	VNF	MUST	Interface Types
R-17852	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.	VNF	MAY	General
R-15837	The following table defines the major TOSCA Types specified in ETSI NFV-SOL001 standard draft. The VNFD provided by a VNF vendor MUST comply with the below definitions:	VNF	MUST	General
R-10087	The VNF package MUST contain all standard artifacts as specified in ETSI GS NFV-SOL004 including Manifest file, VNFD (or Main TOSCA/YAML based Service Template) and other optional artifacts. CSAR Manifest file as per SOL004 - for example ROOT\\ MainServiceTemplate.mf	VNF	MUST	VNF Package Contents