Cisco Cisco Elastic Services Controller 2.3 Developer's Guide
On Success:
A successful Deploy Service workflow will trigger events and operational data changes for each of the
dependent workflows, and for the Deploy Service workflow.
dependent workflows, and for the Deploy 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.
If the tenant was created, then an escEvent of type CREATE_TENANT will be sent. Refer to section 5.1.1
for details.
for details.
If any ephemeral networks were created, then an escEvent of type CREATE_NETWORK will be sent for
each network. Refer to section 5.1.3 for details.
each network. Refer to section 5.1.3 for details.
If any subnets for ephemeral networks were created, then an escEvent of type CREATE_SUBNET will be
sent for each subnet. Refer to section 5.1.5 for details.
sent for each subnet. Refer to section 5.1.5 for details.
Once each VM in the deployment is successfully deployed in the VIM, an escEvent of type
VM_DEPLOYED with a SUCCESS status will be sent (one per VM):
VM_DEPLOYED with a SUCCESS status will be sent (one per VM):
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-04-28T23:38:04.741+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>OpenStack Driver: VM successfully created, VM Name:
<eventTime>2015-04-28T23:38:04.741+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>OpenStack Driver: VM successfully created, VM Name:
[csr-reg__12605__vnf-tenant__vnf-tenantcsr-depcsr-reg1.2__0__csr-
vm__0]</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>9b252ece-7973-4b1f-832e-fe53c68fb963</vmid>
vm__0]</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>9b252ece-7973-4b1f-832e-fe53c68fb963</vmid>
<hostid>a2f7615e78330dd28697588ddfb9516504b19642f53d39d7cff4f6ab</hostid>
</vm_source>
<vm_target/>
<event>
<type>VM_DEPLOYED</type>
</event>
</escEvent>
</notification>
</vm_source>
<vm_target/>
<event>
<type>VM_DEPLOYED</type>
</event>
</escEvent>
</notification>
Once each VM in the deployment can be reached by the VM Monitor, an escEvent of type VM_ALIVE
with a SUCCESS status will be sent (one per VM):
with a SUCCESS status will be sent (one per VM):
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-04-28T23:38:21.479+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<eventTime>2015-04-28T23:38:21.479+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>VM_Alive event received, VM ID: [csr-reg__12605__vnf-
tenant__vnf-tenantcsr-depcsr-reg1.2__0__csr-vm__0]</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>9b252ece-7973-4b1f-832e-fe53c68fb963</vmid>
tenant__vnf-tenantcsr-depcsr-reg1.2__0__csr-vm__0]</status_message>
<depname>csr-dep</depname>
<tenant>vnf-tenant</tenant>
<depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>
<vm_group>csr-vm</vm_group>
<vm_source>
<vmid>9b252ece-7973-4b1f-832e-fe53c68fb963</vmid>