...
SOL001 NSD mapping to/from NS SDC AID DM
- ONAP previous analysis
- The SDC NSD node type, org.openecom.resource.vfc.NSD, is
- modeled as a component of a VF to represent an allotted resource. But, it is not derived from the org.openecomp.resource.vfc.AllottedResource, either.
- The SDC NSD might be designed for Volte use case support, and used by the VFC.
- It is recommended to deprecate the current SDC NSD node type, and to replace with SOL001 tosca.nodes.nfv.NSD node type.
- SolutionsSolution:
- SDC generates SOL001 tosca.nodes.nfv.NSD node type
- SDC takes SOL001 NSD with tosca.nodes.nfv.NSD node type as is, without mapping; i.e., no mapping is necessary
- VFC uses the SOL001 NSD
...
SOL001 VNF mapping to/from VNF SDC AID DM
- ONAP previous analysis
- There is no 1:1 mapping between the SOL001 tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.nodes.VF.
- SDC VF node types has very few properties.
- a lot of common properties are added to each node type created by SDC
- new common properties are mainly about networking and ONAP specific properties
- There is no clear mapping logic between the current node types
- SDC creates new data type as ONAP deployment configuration.
- There is no 1:1 mapping between the SOL001 tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.nodes.VF.
- Solutions
- map between SOL001 VNF and SDC AID DM VNF selectively.
- data in the SOL001 that would be considered Cloud Provider automation data could be remained unmapped
- Examples of Service Provider data that would need to be mapped in order to drive ONAP automation would include:
- HPA requirements needed by OOF to determine cloud feasibility
- Input parameters passed to the Cloud provider
- ONAP wants to distinguish between the mode/data required to drive ONAP functionality from a Service Provider perspective from any ancillary mode/data required to drive Cloud Provider automation.
- Identify Cloud Provider automation-related data and remove it from the mapping
- Identify Service Provider data and map it to SDC AID DM
- map between SOL001 VNF and SDC AID DM VNF selectively.
SOL001 VNF (tosca.nodes.nfv.VNF) | SDC AID DM VNF (org.openecomp.resource.abstract.nodes.VF) | org.openecomp.resource.vf.vcpeInfrastructureGwDemoApp (derived from org.openecomp.resource.abstract.nodes.VF) | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
name | required | type | name | required | type | name | required | type | ||
descriptor_id | yes | string | nf_function | string | nf_function | string | ||||
descriptor_version | yes | string | nf_role | string | nf_role | string | ||||
provider | yes | string | nf_type | string | nf_type | string | ||||
product_name | yes | string | nf_naming_code | string | nf_name_code | string | ||||
software_version | yes | string | nf_naming | org.openecomp.datatyhpes.Naming | nf_naming | org.openecomp.datatyhpes.Naming | ||||
product_info_name | no | string | availability_zone_max_count | integer | availablity_zone_max_count | integer | ||||
vnfm_info | yes | list of string | min_instances | integer | min_instances | integer | ||||
localization_languages | no | list of string | max_instances | integer | max_instances | integer | ||||
default_localization_language | no | string | multi_stage_design | boolean | multi_stage_design | boolean | ||||
configurable_properties | no | tosca.datatypes.nfv.VnfconfigurableProperties | vf_module_id | no | ||||||
modifiable_attributes | no | tosca.datatypes.nfv.VnfInfoModifiableAttributes | vcpe_image_name | no | ||||||
lcm_operations_configuraion | no | tosca.datatypes.nfv.VnfLcmOperationsConfiguration | public_net_id | no | ||||||
monitoring_parameters | no | list of tosca.dataypes.nfv.VnfMonitoringParameter | vgw_name_0 | no | ||||||
flavour_id | yes | string | nexus_artifact_repo | no | ||||||
flavour_description | yes | string | mux_ip_addr | no | ||||||
vnf_profile | no | tosca.datatyhpes.nfv.VnfProfile | vnf_id | no | ||||||
cpe_public_net_cidr | no | |||||||||
vg_vgmux_tunnel_vni | no | |||||||||
nf_naming | no | |||||||||
multi_stage_design | no | |||||||||
nf_naming_code | no | |||||||||
vgw_private_ip_0 | no | |||||||||
vgw_private_ip_1 | no | |||||||||
vgw_private_ip_2 | no | |||||||||
pub_key | no | |||||||||
install_script_version | no | |||||||||
onap_private_net_cidr | no | |||||||||
cpe_public_net_id | no | |||||||||
mux_gw_private_net_id | no | |||||||||
dcae_collector_ip | no | |||||||||
dcae_collector_port | no | |||||||||
onap_private_net_id | no | |||||||||
cloud_env | no |
...
SOL001 VL mapping to/from VL SDC AID DM
- ONAP previous analysis
- Each vendor/operator defined their own VL node types (e.g., tosca.nodes.nfv.ext.zte.VL)
- The vendor/operator-specific node types have no direct 1:1 mapping to tosca.nodes.nfv.NsVirtualLink
- Solutions
- Deprecate vendor/operator-specific VLs
- Use SOL001 tosca.nodes.nfv.NsVirtualLink
- ONAP SO NFVO uses the SOL001 tosca.nodes.nfv.NsVirtualLink
- VFC needs to adapt SOL001 tosca.nodes.nfv.NsVirtualLink