Cisco Cisco Elastic Services Controller 2.1 Developer's Guide
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>
<depname>csr-dep</depname>
<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>
<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>
<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>
If any subnets for ephemeral networks were deleted, then an escEvent of type DELETE_SUBNET will be
sent for each subnet. Refer to section 06 for details.
sent for each subnet. Refer to section 06 for details.
If any ephemeral networks were deleted, then an escEvent of type DELETE_NETWORK will be sent for
each network. Refer to section 5.1.34 for details.
each network. Refer to section 5.1.34 for details.
Once all the VMs in the deployment and dependent resource objects are undeployed and deleted
respectively, an escEvent of type SERVICE_UNDEPLOYED with a SUCCESS status will be sent:
respectively, an escEvent of type SERVICE_UNDEPLOYED with a SUCCESS status will be sent:
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T20:48:24.467+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>Service group undeployment completed
successfully</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_source>
<eventTime>2015-05-19T20:48:24.467+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>Service group undeployment completed
successfully</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid>
<vm_source>