Cisco Cisco Elastic Services Controller 1.1 Developer's Guide
<status>SUCCESS</status>
<status_message>Service group undeployment completed
successfully</status_message>
<svcname>csr-reg</svcname>
<svcversion>1.2</svcversion>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<svcid>a4d6abc8-adaf-4e3c-a7af-382846499a58</svcid>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_source>
</vm_source>
<vm_target>
<status_message>Service group undeployment completed
successfully</status_message>
<svcname>csr-reg</svcname>
<svcversion>1.2</svcversion>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<svcid>a4d6abc8-adaf-4e3c-a7af-382846499a58</svcid>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_source>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>SERVICE_UNDEPLOYED</type>
</event>
</escEvent>
</notification>
<event>
<type>SERVICE_UNDEPLOYED</type>
</event>
</escEvent>
</notification>
Once the
SERVICE_UNDEPLOYED
event is sent, the undeploy Service configuration has been successfully
activated.
Operational data
All of the resource objects and service VMs that have been deleted as part of undeployment will be
removed from operational data.
removed from operational data.
On Failure:
Event notification
Workflows of different types in the configuration activation run in sequence. If an activation failure
occurs in one of these workflows, the Service undeploy workflow is then aborted and no more
workflows will be processed. Along with the abort, an escEvent of type SERVICE_UNDEPLOYED with a
FAILURE status is sent.
occurs in one of these workflows, the Service undeploy workflow is then aborted and no more
workflows will be processed. Along with the abort, an escEvent of type SERVICE_UNDEPLOYED with a
FAILURE status is sent.
Operational data
After an undeploy service configuration has failed activation, there will be no operational data for any
dependent workflows nor the deployment itself (See Handling Activation Failures).
dependent workflows nor the deployment itself (See Handling Activation Failures).
Handling Activation Failures
If a FAILURE event occurs while activating a undeploy service configuration change there is no need to
take any further actions as ESC has already cleaned up its database. Operator may need to manually
remove the resources from the VIM as the VIM may not have deleted them successfully.
take any further actions as ESC has already cleaned up its database. Operator may need to manually
remove the resources from the VIM as the VIM may not have deleted them successfully.
5.1.15 Update Service
Update service allows you to incrementally add VNFs to a deployment. Update service requires a service
registration with all of the potential VNFs that may potentially be used in the future even when they will
not be used right away. Whenever a VNF is to be deployed then the min active under the desired VNF
(vm_group) must be set to 1 and a configuration file has to be provided. The VNFs that are not going to
be deployed must have their min active set to 0 and their interfaces to N/A as well as their configuration
file set to N/A.
registration with all of the potential VNFs that may potentially be used in the future even when they will
not be used right away. Whenever a VNF is to be deployed then the min active under the desired VNF
(vm_group) must be set to 1 and a configuration file has to be provided. The VNFs that are not going to
be deployed must have their min active set to 0 and their interfaces to N/A as well as their configuration
file set to N/A.