...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
VNF Data Model
- property "vnfm_info" constraint pattern: "(etsivnfm:v[0-9]?[0-9]\.[0-9]?[0-9]\.[0-9]?[0-9]$)|([0-9]:[a-zA-Z0-9.-]$)"
- values must be in format etsivnfm:v3.3.1 or <int>:<string>
- this is not enforced by constraint in type definition in ONAP
- property "vnf_profile" has not changed, but it is commented out in existing version in ONAP
- new attribute "scale_status" added
...
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
VDU OsContainer Data Model
...
tosca.datatypes.nfv.VnfMonitoringParameter: | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
name | String | 1 | Human readable name of the monitoring parameter | |
performance_metric | String | 1 | - valid_values: [ v_cpu_usage_mean_vnf, v_cpu_usage_peak_vnf, | Identifies the performance metric, according to ETSI GS NFV-IFA 027. |
collection_period | scalar-unit.time | 0..1 | - greater_than: 0 s | Describes the recommended periodicity at which to collect the performance information. |
VnfProfile Data Model
tosca.datatypes.nfv.VnfProfile: | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
instantiation_level | String | 0..1 | Identifier of the instantiation level of the VNF DF to be used for instantiation. If not present, the default instantiation level as declared in the VNFD shall be used | |
min_number_of_instances | Integer | 1 | - greater_or_equal: 0 | Minimum number of instances of the VNF based on this VNFD that is permitted to exist for this VnfProfile. |
max_number_of_instances | Integer | 1 | - greater_or_equal: 0 | Maximum number of instances of the VNF based on this VNFD that is permitted to exist for this VnfProfile. |
| service_availability_level | Integer | 0..1 | greater_or_equal: 1 | If present, specifies the service availability level for the VNF instance created from this profile. |
SwImageData Data Model
- Change: checksum propeorty is used to be string in 2.6.x. Now, it is tosca.datatypes.nfv.ChecksumData. During SDC onboarding, the old type checksum data will be stored in a new property in SDC (e.g., checksum261).
...
vduCp Data Model
- tosca.nodes.nfv.VduCP
- No Change since 2.74.2.1
vnfExtCp Data Model
- added trunk_binding capability
- 4.2.1 removed the container_binding requirement from 4.1.1 based model
- 4.2.1 removed the node Vdu.Compute constraint from the virtual_binding requirement so that VduCp can also reference Vdu.OsContainerDeployableUnit
vnfExtCp Data Model
- tosca.nodes.nfv.VnfExtCP
- No Change since 2.7.1
- tosca.nodes.nfv.VnfExtCP
- No Change since 2.7.1
- There are some changes from 2.6.1 to 2.7.1
- property "vnic_type" has the following extra valid_values:
- macvtap, baremetal, virtio-forwarder, smart-nic
- and the following removed valid_values - backwards incompatible:
- virtio
- requirement "virtual_link" cardinality changed from default (1-1) to 0-1
- requirement "virtual_binding" cardinality changed from default (1-1) to 1-1, i.e. no effective change
- property "vnic_type" has the following extra valid_values:
- requirement "external_virtual_link" cardinality changed from default (1-1) to 0-1
- requirement "internal_virtual_link" cardinality changed from default (1-1) to 1-1, i.e. no effective change
...
tosca.nodes.nfv.VipCp: derived_from: tosca.nodes.nfv.Cp description: Describes a connection point to allocate one or a set of virtual IP addresses | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
vip_function | String | 1 | - valid_values: [ high_availability, load_balance ] | Describes the algorithm used to obtain the checksum value |
requirements: - target: capability: tosca.capabilities.Node relationship: tosca.relationships.DependsOn occurrences: [ 1, UNBOUNDED ] - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VipVirtualLinksTo occurrences: [1, 1] | ||||
...
VirtualCp Data Model
Gliffy Diagram macroId 7382e3d4a3b53088-b2aa8b52-40fe4dbe-86538925-3420b8c9d980e26a5ae6eba4 name v4.12.1 VirtualCp pagePin 1
tosca. |
datatypes.nfv.ServicePortData: derived_from: tosca.datatypes.Root description: describes the service identifying port properties exposed by the VirtualCp | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
name | String | 1 | The name of this port exposed by the VirtualCp. | |
| protocol | String | 1 | valid_values: [ TCP, UDP, SCTP ] | The L4 protocol for this port exposed by the VirtualCp. |
| port | Integer | 1 | The L4 port number exposed by the VirtualCp. | |
PortConfigurable | Boolean | 1 | Specifies whether the port attribute value is allowed to be configurable. | |
tosca.datatypes.nfv.AdditionaServiceData: derived_from: tosca.datatypes.Root description: describes the additional service data of the VirtualCp used to expose properties of the VirtualCp | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
| portData | List of tosca.datatypes.nfv.ServicePortData | 1 | Service port numbers exposed by the VirtualCp. | |
serviceData | String | 0..1 | Service matching information exposed by the VirtualCp. | |
tosca.nodes.nfv.VirtualCp: VirtualCp: derived_from: tosca.nodes.nfv.Cp description: Describes a virtual connection point allowing the access to a number of VNFC instances (based on their respective VDUs). | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
additionalServiceData | list of toscaof tosca.datatypes.nfv.AdditionalServiceData | 1 | References the VDU(s) which implement this service | |
requirements: - target: capability: tosca.capabilities.Node relationship: tosca.relationships.DependsOn occurrences: [ 1, UNBOUNDED ] - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VirtVirtualLinksToVirtualLinksTo occurrences: [10, 1] | ||||
Data types. (Input from Michael Morris)
...