Commit 162a1398 authored by vreck's avatar vreck
Browse files

Update etsi_nfv_sol001_common_types.yaml

parent dcd10108
tosca_definitions_version: tosca_simple_yaml_1_3
description: ETSI NFV SOL 001 common types definitions version 3.5.1
description: ETSI NFV SOL 001 common types definitions version 3.6.1
metadata:
template_name: etsi_nfv_sol001_common_types
template_author: ETSI_NFV
template_version: 3.5.1
template_version: 3.6.1
data_types:
tosca.datatypes.nfv.L2AddressData:
......@@ -21,8 +21,14 @@ data_types:
properties:
ip_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: 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
ip_address_assignment_subtype:
type: boolean
description: Method of IP address assignment in case the IP configuration is not provided using the NFV MANO interfaces towards the VNFM. Description of the valid values: (1) dynamic: the VNF gets an IP address dynamically from the NFVI (i.e., using DHCP), (2) vnf_pkg: an IP address defined by the VNF provider is assigned by means included as part of the VNF package (e.g., LCM script); (3) external: an IP address is provided by an external management entity (such as EM) directly towards the VNF.Shall be present in case the ip_address_assignment property is set to False and shall be absent otherwise.
required: false
constraints:
- valid_values: [ dynamic, vnf_pkg, external ]
floating_ip_activated:
type: boolean
description: Specifies if the floating IP scheme is activated on the Connection Point or not
......@@ -39,6 +45,12 @@ data_types:
required: false
constraints:
- greater_than: 0
fixed_ip_address:
type: list
description: Fixed IP addresses to be assigned to the internal CP instance. This property enables the VNF provider to define fixed IP addresses for internal CP instances to be assigned by the VNFM or the NFVO. This property is only permitted for Cpds without external connectivity, i.e. connectivity outside the VNF. If present, it shall be compatible with the values of the L3ProtocolData of the VnfVirtualLink referred to by the Cp, if L3ProtocolData is included in the VnfVirtualLink
required: false
entry_schema:
type: string
tosca.datatypes.nfv.AddressData:
derived_from: tosca.datatypes.Root
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment