-
Story
-
Resolution: Done
-
High
-
None
-
None
The ConfigScaleOut action is added to the Reference Data artifact. It has been modified as follows:
- Contains a new block template-id-list which contains a list of the Template Id’s (for display on the CDT tool). This block is not used by run-time.
- The artifact-list contains multiple sets of template and PD artifact names (one pair per template-id)
- The VM block is modified in order to get the VM information specific to each template-id.
Here is an example of the ConfigScaleOut action in the Reference Data model:
{
"action": "ConfigScaleOut",
"action-level": "vnf",
"scope": {
"vnf-type": "newtypeofvnf",
"vnfc-type": ""
}
, "template": "Y",
"vm": [
"vm-instance": 1,
"template-id": "id1",
"vnfc": [
{
"vnfc-instance": "1",
"vnfc-function-code": "fcx",
"ipaddress-v4-oam-vip": "Y",
"group-notation-type": "first-vnfc-name",
"group-notation-value": "pair",
"vnfc-type": "vDBE"
}
]
},
{
"vm-instance": 1,
"template-id": "id2",
"vnfc": [
{
"vnfc-instance": "1",
"vnfc-function-code": "fcx",
"ipaddress-v4-oam-vip": "Y",
"group-notation-type": "first-vnfc-name",
"group-notation-value": "pair",
"vnfc-type": "vDBE"
}
]
},
{
"vm-instance": 2,
"template-id": "id2",
"vnfc": [
{
"vnfc-instance": "1",
"vnfc-function-code": "fcx",
"ipaddress-v4-oam-vip": "Y",
"group-notation-type": "first-vnfc-name",
"group-notation-value": "pair",
"vnfc-type": "vDBE"
}
]
],
"device-protocol": "NETCONF-XML",
"user-name": "netconf",
"port-number": "20",
"artifact-list": [
{
"artifact-name": "template_ConfigScaleOut_newtypeofvnf_0.0.1V_id1.xml",
"artifact-type": "config_template"
}
{
"artifact-name": "pd_ConfigScaleOut_newtypeofvnf_0.0.1V_id1.yaml",
"artifact-type": "parameter_definitions"
}
{
"artifact-name": "template_ConfigScaleOut_newtypeofvnf_0.0.1V_id2.xml",
"artifact-type": "config_template"
}
, {
"artifact-name": "pd_ConfigScaleOut_newtypeofvnf_0.0.1V_id2.yaml",
"artifact-type": "parameter_definitions" }
],
"scopeType": "vnf-type",
"template-id-list": ["id1","id2"]
},
Populate the asdc_artifacts and asdc_reference table as usual. Note that this will create records in the asdc_artifacts table for each artifact listed. The contents of the artifacts will be populated when the other artifacts are uploaded separately.
The ConfigScaleOut action in the Reference Data artifact will be modeled similar to the Configure action (i.e., it will contain a VM block which is populated for one or more VNFC records). When loading the Reference Artifact:
Add/update a record for ConfigScaleOut to the protocol_reference table as usual
Add records for the ConfigScaleOut action to the southbound properties file as usual
Add a record to the device_interface_protocol if there is no record for the vnf-type
Add a record to the config_action_dg table for the ConfigScaleOut action
Add/update the vnfc_reference table with the VNFC records using the same logic as for Configure (except that the action in the vnfc_reference is ConfigScaleOut). A new field ‘template-id’ is added to the vnfc_reference table. If the template-id is populated in the reference data artifact, populate it in the vnfc_reference table.
Loading of the ConfigScaleOut template, Param (name/value pairs), and PD file follows the existing flow.
[note: this functionality will will be delivered over 2 sprints: Sub-tasks will define what is delivered under each JIRA story]