Cisco Cisco Elastic Services Controller 2.2 Developer's Guide
6.1.14.3 Configuration Activation
Workflow Aggregation:
For each dependent delete workflow specified in the configuration, a separate workflow is submitted.
Refer to the specific workflow description for information on configuration activation of each of these
optional workflows. The undeployment starts with undeploying the service VMs first then it moves
onto deleting the dependent resource objects and will be processed in the following order:
Refer to the specific workflow description for information on configuration activation of each of these
optional workflows. The undeployment starts with undeploying the service VMs first then it moves
onto deleting the dependent resource objects and will be processed in the following order:
Section 6.1.6: Delete a Subnet for a Tenant (zero or more)
Section 6.1.4: Delete a Network for a Tenant (zero or more)
Multiple workflows of the same type are executed in parallel, and a failure in any workflow results in a
Undeploy Service activation failure once the remaining workflows of the same type have finished.
Undeploy Service activation failure once the remaining workflows of the same type have finished.
Workflows of different types are processed in sequence, and a failure in any of these workflows will
result in an immediate undeploy Service activation failure.
result in an immediate undeploy Service activation failure.
On Success:
A successful Undeploy Service workflow will trigger events and operational data changes for each of the
dependent workflows, and for the undeploy Service workflow.
dependent workflows, and for the undeploy Service workflow.
Event notification
A series of escEvent notifications with a SUCCESS status will be sent to Netconf subscribers once the
individual workflows in the configuration activation have completed.
individual workflows in the configuration activation have completed.
Once each VM in the deployment is successfully undeployed from the VIM, an escEvent of type
VM_UNDEPLOYED with a SUCCESS status will be sent (one per VM):
VM_UNDEPLOYED with a SUCCESS status will be sent (one per VM):
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T20:48:23.908+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>OpenStack Driver: VM successfully
deleted</status_message>
<eventTime>2015-05-19T20:48:23.908+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>OpenStack Driver: VM successfully
deleted</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_group>csr-vm</vm_group>
<tenant>vnf-tenant</tenant>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>56c4a68f-e79f-4ada-9a59-7bf2b30e3e9e</vmid>
<hostid>c3efa32d511913f8af331959886a94d3c378501266e4fa931915a6d9</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_UNDEPLOYED</type>
</event>
</escEvent>
</notification>
<vmid>56c4a68f-e79f-4ada-9a59-7bf2b30e3e9e</vmid>
<hostid>c3efa32d511913f8af331959886a94d3c378501266e4fa931915a6d9</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_UNDEPLOYED</type>
</event>
</escEvent>
</notification>