ConfigScaleOut
ConfigScaleOut¶
The ConfigScaleOut command is used to apply any actions on a VNF as part of a ScaleOut flow. Actions could include updating the VNF configuration or running a set of other tasks.
The ConfigScaleOut action can have multiple APPC templates associated with it. APPC retrieves the VfModuleModelName from A&AI (model.model-vers.model-name), which is used as the unique identifier to select the correct APPC template. APPC creates or updates VNFC records in A&AI for the newly instantiated VM’s. The orchestration-status of the VNFC’s is set to CONFIGURED.
This action is supported via the Netconf (limited to configuration changes), Chef, and Ansible protocols.
| Target URL | /restconf /operations/appc-provider-lcm:config-scale-out |
| Action | ConfigScaleOut |
| Action-Identifiers | Vnf-id |
| Payload Parameters | See below |
| Revision History | New in Beijing |
| Payload Parameter | Description | Required? | Example |
|---|---|---|---|
| request-parameters | vnf-host-ip-address: optional if Netconf or other direct interface to the VNF. If not provided, the vnf-host-ip-address will be obtained from A&AI. | No | “payload”: “{"request-parameters ": { "vnf-host-ip-address": \”value\”, \”vf-module-id\”: \”value\”, \”controller-template-id\”: \”value\” } "configuration-parameters":{"<CONFIG- PARAMS>"} |
| vf-module-id: used to determine the A&AI VM inventory associated with ConfigScaleOut. | Yes | ||
| controller-template-id: optional. This is a unique identifier that will identify the template associated with the ConfigScaleOut. Will be needed if A&AI does not contain the template identifier. | No | ||
| configuration-parameters | A set of instance specific configuration parameters should be specified. If provided, APP-C replaces variables in the configuration template with the values supplied. | No |
ConfigScaleOut Response¶
Success:
- A successful ConfigScaleOut returns a success status code 400 when completed.
Failure:
- A failed ConfigScaleOut returns a failure code 401 and the failure message.
- If the ConfigScaleOut is successfully performed on the VNF but there is a failure to update A&AI inventory, an intermediate failure message with failure code 501 is returned prior to the final 400 success message.