...
Define a new data type based on the tosca.nodes.nfv.VNF with optional attributes that are specific to ONAP.
Proposal A
Make the org.openecomp.resource.abstract.nodes.VF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF
New SDC AID DM VNF (org.openecomp.resource.abstract.nodes.VF) | ||
---|---|---|
name | required | type |
<SOL001 tosca.nodes.nfv.VNF attributes> | ||
descriptor_id | yes | string |
descriptor_version | yes | string |
provider | yes | string |
product_name | yes | string |
software_version | yes | string |
product_info_name | no | string |
vnfm_info | yes | list of string |
localization_languages | no | list of string |
default_localization_language | no | string |
configurable_properties | no | tosca.datatypes.nfv.VnfconfigurableProperties |
modifiable_attributes | no | tosca.datatypes.nfv.VnfInfoModifiableAttributes |
lcm_operations_configuraion | no | tosca.datatypes.nfv.VnfLcmOperationsConfiguration |
monitoring_parameters | no | list of tosca.dataypes.nfv.VnfMonitoringParameter |
flavour_id | yes | string |
flavour_description | yes | string |
vnf_profile | no | tosca.datatyhpes.nfv.VnfProfile |
<SDC AID DM VF attributes> | ||
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)
|
Proposal B
Can we use the additionalAttribute map to represent ONAP specific attributes?
...