Commit 21967a13 authored by Miguel Angel Reina Ortega's avatar Miguel Angel Reina Ortega
Browse files

Corrected editorial mistakes in files etsi_nfv_sol001_vnfd_types.yaml and in...

Corrected editorial mistakes in files etsi_nfv_sol001_vnfd_types.yaml and in etsi_nfv_sol001_common_types.yaml
parent 825d4644
......@@ -25,7 +25,7 @@ data_types:
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.
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 ]
......
......@@ -967,7 +967,7 @@ data_types:
required: false
endpoint_type:
type: string
description: Specifies the type of the endpoint exposing the LCM operation coordination such as other operations supporting or management systems (e.g. an EM) or the VNF instance. If the VNF produces the LCM coordination interface, this property may be omitted or may have the value "vnf". If this attribute is omitted, the type of endpoint that provides the interface is determined at deployment time. If the VNF does not produce the LCM coordination interface but coordination via this interface is needed, it is expected that a management entity such as the EM exposes the coordination interface, and consequently, this attribute shall be present and shall have the value “mgmt�
description: Specifies the type of the endpoint exposing the LCM operation coordination such as other operations supporting or management systems (e.g. an EM) or the VNF instance. If the VNF produces the LCM coordination interface, this property may be omitted or may have the value "vnf". If this attribute is omitted, the type of endpoint that provides the interface is determined at deployment time. If the VNF does not produce the LCM coordination interface but coordination via this interface is needed, it is expected that a management entity such as the EM exposes the coordination interface, and consequently, this attribute shall be present and shall have the value "mgmt"
required: false
constraints:
- valid_values: [ mgmt, vnf ]
......@@ -1667,7 +1667,7 @@ node_types:
constraints:
- valid_values: [ normal, macvtap, direct, baremetal, virtio-forwarder, direct-physical, smart-nic ]
capabilities:
trunk_binding: # This capability is available only the trunk_mode property value of this VduCp is “true�and there is at least one VduSubCp defined as subport of the same trunk.
trunk_binding: # This capability is available only the trunk_mode property value of this VduCp is "true" and there is at least one VduSubCp defined as subport of the same trunk.
type: tosca.capabilities.nfv.TrunkBindable
occurrences: [ 0, UNBOUNDED ]
requirements:
......
Markdown is supported
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