description:ETSI NFV SOL 001 common types definitions version 3.6.1
description:ETSI NFV SOL 001 common types definitions version 3.7.1
metadata:
template_name:etsi_nfv_sol001_common_types
template_author:ETSI_NFV
template_version:3.6.1
template_version:3.7.1
data_types:
tosca.datatypes.nfv.L2AddressData:
derived_from:tosca.datatypes.Root
description:Describes the information on the MAC addresses to be assigned to a connection point.
properties:
mac_address_assignment:
type:boolean
description:Specifies if the address assignment is the responsibility of management and orchestration function or not. If it is set to True, it is the management and orchestration function responsibility
description:Specifies which mode is used for the MAC address assignment. If it is set to True, a MAC address is expected to be provided by a management entity via the NFV MANO interfaces towards the VNFM using attributes standardized for this purpose in the NFV-MANO information model and is further transferred from the VNFM to the VIM. A MAC address will be automatically assigned by the VIM/NFVI as fallback if not provided. If it is set to False, a MAC address is expected to it will be assigned by means specific to the VNF itself (e.g., by an LCM script, by the EM) and is further transferred from the VNFM to the VIM. A MAC address will be automatically assigned by the VIM/NFVI as fallback if not provided to the VIM.
required:true
tosca.datatypes.nfv.L3AddressData:
@@ -21,10 +21,10 @@ data_types:
properties:
ip_address_assignment:
type:boolean
description:Specify which mode is used for the IP address assignment. If it is set to True, IP configuration information shall be provided for the VNF by a management entity using the NFV MANO interfaces towards the VNFM. If it is set to False, the value of the ip_address_assignment_subtype property defines the method of IP address assignment. Shall be present if the fixed_ip_address property is not present and should be absent otherwise. See note
required:true
description:Specify which mode is used for the IP address assignment. If it is set to True, IP configuration information shall be provided for the VNF by a management entity using the NFV MANO interfaces towards the VNFM. If it is set to False, the value of the ip_address_assignment_subtype property defines the method of IP address assignment. Shall be present if the fixed_ip_address property is not present and should be absent otherwise. See note.
description:Defines address type. The address type should be aligned with the address type supported by the layer_protocols properties of the connetion point
description:Defines address type. The address type should be aligned with the address type supported by the layer_protocols properties of the connection point
required:false
constraints:
-valid_values:[ipv4,ipv6]
@@ -113,8 +113,8 @@ data_types:
properties:
associated_layer_protocol:
type:string
required:true
description:One of the values of the property layer_protocols of the CP
description:Describes the periodicity at which to collect the performance information.
@@ -196,11 +197,13 @@ data_types:
-greater_than:0 s
capability_types:
tosca.capabilities.nfv.VirtualLinkable:
derived_from:tosca.capabilities.Node
description:A node type that includes the VirtualLinkable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualLinksTo relationship type
relationship_types:
tosca.relationships.nfv.VirtualLinksTo:
derived_from:tosca.relationships.DependsOn
description:Represents an association relationship between the VduCp and VnfVirtualLink node types or the association between either a VnfExtCp, a PnfExtCp or a Sap and an NsVirtualLink node types.
description:Identifies the role of the port in the context of the traffic flow patterns in the VNF or parent NS
required:false
@@ -242,10 +246,11 @@ node_types:
type:tosca.datatypes.nfv.CpProtocolData
trunk_mode:
type:boolean
description:Provides information about whether the CP instantiated from this Cp is in Trunk mode (802.1Q or other), When operating in "trunk mode", the Cp is capable of carrying traffic for several VLANs. Absence of this property implies that trunkMode is not configured for the Cp i.e. It is equivalent to boolean value "false".
description:Provides information about whether the CP instantiated from this Cp is in Trunk mode (802.1Q or other). When operating in "trunk mode", the Cp is capable of carrying traffic for several VLANs. Absence of this property implies that trunkMode is not configured for the Cp i.e. It is equivalent to boolean value "false".
required:false
policy_types:
tosca.policies.nfv.Abstract.SecurityGroupRule:
derived_from:tosca.policies.Root
description:The Abstract.SecurityGroupRule type represents an abstract policy type without any target requirements
@@ -256,7 +261,7 @@ policy_types:
required:false
direction:
type:string
description:The direction in which the security group rule is applied. The direction of 'ingress' or 'egress' is specified against the associated CP. I.e., 'ingress' means the packets entering a CP, while 'egress' means the packets sent out of a CP.
description:The direction in which the security group rule is applied. The direction of 'ingress' or 'egress' is specified against the associated CP. I.e. 'ingress' means the packets entering a CP, while 'egress' means the packets sent out of a CP.
