...
- For E2E (OSS Service) modeling, use org.openecomp.resource.abstract.nodes.service
- E2E (OSS Service-Level) is outside of ETSI scope, and it could be ONAP-specific that is orchestrated by ONAP SO
- The E2E (OSS Service-Level) model references/includes associated NSs
- For the E2E service level, the org.openecop.resource.abstract.nodes.service type is still used as the base type of the service. SDC will use the ETSI SOL001 NSD type and attach the NSDs to the E2E (OSS Service).
- For NS modeling, use tosca.nodes.nfv.NS
- ONAP SO-NFVO, VFC and external NFVO manage the NS models and packages
ONAP ETSI-Alignment Modeling Hierarchy
- The following diagram depicts ONAP ETSI-Alignment Modeling hierarchy.
- Note: the ONAP VFC model represents the design time VFC, not runtime VFC instance(s).
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
...
Define a new data type based on the org.openecomp.resource.abstract.nodes.VF with ETSI SOL001 VNF data type attributes.
...
- Make the org.openecomp.resource.abstract.nodes.ETSI.VNF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF
- During VNF onboarding, SDC copies SOL001 VNF attribute contents to the corresponding attributes in hte org.openecomp.resource.abstract.nodes.ETSI.VNF
- ONAP specific attributes that are inherited from the org.openecomp.resource.abstract.nodes.VF will be filled up by SDC (design time)
- Those attribute contents will not be mapped back into the SOL001 VNF (reverse mapping). For that case, only the SOL001 VNF corresponding attributes will be copied
SOL001 VNF (tosca.nodes.nfv.VNF) | Mapping | New SDC AID DM VNF (org.openecomp.resource.abstract.nodes.ETSI.VNF) derived from org.openecomp.resource.abstract.nodes.VF | ||||
|---|---|---|---|---|---|---|
| name | required | type | name | required | type | |
| <SOL001 tosca.nodes.nfv.VNF attributes > | <SOL001 tosca.nodes.nfv.VNF attributes > | |||||
| descriptor_id | yes | string | <--> | descriptor_id | yes | string |
| descriptor_version | yes | string | <--> | descriptor_version | yes | string |
| provider | yes | string | <--> | provider | yes | string |
| product_name | yes | string | <--> | product_name | yes | string |
| software_version | yes | string | <--> | software_version | yes | string |
| product_info_name | no | string | <--> | product_info_name | no | string |
| vnfm_info | yes | list of string | <--> | vnfm_info | yes | list of string |
| localization_languages | no | list of string | <--> | localization_languages | no | list of string |
| default_localization_language | no | string | <--> | default_localization_language | no | string |
| configurable_properties | no | tosca.datatypes.nfv.VnfconfigurableProperties | <--> | configurable_properties | no | tosca.datatypes.nfv.VnfconfigurableProperties |
| modifiable_attributes | no | tosca.datatypes.nfv.VnfInfoModifiableAttributes | <--> | modifiable_attributes | no | tosca.datatypes.nfv.VnfInfoModifiableAttributes |
| lcm_operations_configuraion | no | tosca.datatypes.nfv.VnfLcmOperationsConfiguration | <--> | lcm_operations_configuraion | no | tosca.datatypes.nfv.VnfLcmOperationsConfiguration |
| monitoring_parameters | no | list of tosca.dataypes.nfv.VnfMonitoringParameter | <--> | monitoring_parameters | no | list of tosca.dataypes.nfv.VnfMonitoringParameter |
| flavour_id | yes | string | <--> | flavour_id | yes | string |
| flavour_description | yes | string | <--> | flavour_description | yes | string |
| vnf_profile | no | tosca.datatyhpes.nfv.VnfProfile | <--> | vnf_profile | no | tosca.datatyhpes.nfv.VnfProfile |
| <SDC AID DM VF attributes that are inherited from org.openecomp.resource.abstract.nodes.VF> | ||||||
| nf_function | no | string | ||||
| nf_role | no | string | ||||
| nf_type | no | string | ||||
| nf_naming_code | no | string | ||||
| nf_naming | no | org.openecomp.datatypes.Naming | ||||
| availability_zone_max_count | no | integer | ||||
| min_instances | no | integer | ||||
| max_instances | no | integer | ||||
| multi_stage_design | no | boolean | ||||
| sdnc_model_name | no | string | ||||
| sdnc_artifact_name | no | string | ||||
| skip_post_instantiation_configuration | no | boolean (default true)
| ||||
| controller_actor | no | string (default: SO-REF-DATA)
| ||||
Option B
Can we use the additionalAttribute map to represent ONAP specific attributes? If so, we can use the base data type extensively.
...
SOL001 VDU SOL001 VDU mapping to/from VNF SDC AID DM VFC
Current SOL001 VDU vs. SDC AID DM VFC
- no 1:1 mapping
- note: the SDC AID DM VFC represents design-time VFC (like VDU), not VFC instances in runtime
| SOL001 VDU | SDC AID DM VFC (org.openecomp.resource.abstract.nodes.VFC) | ||||
|---|---|---|---|---|---|
| Name | Required | Type | Name | Required | Type |
| name | yes | string | nfc_function | string | |
| description | yes | string | high_availability | no | string |
| boot_order | no | boolean | vm_image_name | string | |
| nfvi_constraints | no | map of string | vm_flavor_name | yes | string |
| monitoring_parameters | no | list of tosca.datatypes.nfv.VnfcMonitoringParameter | nfc_naming_code | no | string |
| configurable_properties | no | map of tosca.datatypes.nfv.VnfcConfigurableProperties | vm_type_tag | no | string |
| boot_data | no | tosca.datatypes.nfv.BootData | nfc_naming | org.openecomp.datatypes.Naming
| |
| vdu_profile | yes | tosca.datatypes.nfv.VduProfile | min_instances | no | integer |
| sw_image_data | no | tosca.datatypes.nfv.SwImageData | |||
...