Cisco Cisco Elastic Services Controller 2.0 Developer's Guide
<vm_target>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_target>
<event>
<type>VM_SCALE_OUT_COMPLETE</type>
</event>
</escEvent>
</notification>
If there are errors during scaling out, a notification indicating the failure
will be sent:
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T23:46:36.276+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>FAILURE</status>
<status_message>VM scaled out failed</status_message>
<svcname>CIRROS_HEZH</svcname>
<svcversion>1.6</svcversion>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<svcid>90044227-1475-45c2-83ff-aed132f77256</svcid>
<depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid>
<vm_group>CSR</vm_group>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_SCALE_OUT_COMPLETE</type>
</event>
</escEvent>
</notification>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_target>
<event>
<type>VM_SCALE_OUT_COMPLETE</type>
</event>
</escEvent>
</notification>
If there are errors during scaling out, a notification indicating the failure
will be sent:
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T23:46:36.276+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>FAILURE</status>
<status_message>VM scaled out failed</status_message>
<svcname>CIRROS_HEZH</svcname>
<svcversion>1.6</svcversion>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<svcid>90044227-1475-45c2-83ff-aed132f77256</svcid>
<depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid>
<vm_group>CSR</vm_group>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_SCALE_OUT_COMPLETE</type>
</event>
</escEvent>
</notification>
6.2.2 Scale In Work Flow
A scale-in work flow will be triggered if the current VNF is underloaded. From the user side, no request is
required to triggered a scale-in. The monitors attached to VNF will trigger it if necessary.
required to triggered a scale-in. The monitors attached to VNF will trigger it if necessary.
6.2.2.1 Event Notifications
There are two notifications sent to NB during a successful scale in:
1. When a scale-in work flow is initiated, the following notifications will be
sent from ESC:
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T23:46:36.276+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>VM scale in triggered</status_message>
<svcname>CIRROS_HEZH</svcname>
<svcversion>1.6</svcversion>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<svcid>90044227-1475-45c2-83ff-aed132f77256</svcid>
<depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid>
<vm_group>CSR</vm_group>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
sent from ESC:
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2015-05-19T23:46:36.276+00:00</eventTime>
<escEvent xmlns="http://www.cisco.com/esc/esc">
<status>SUCCESS</status>
<status_message>VM scale in triggered</status_message>
<svcname>CIRROS_HEZH</svcname>
<svcversion>1.6</svcversion>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<svcid>90044227-1475-45c2-83ff-aed132f77256</svcid>
<depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid>
<vm_group>CSR</vm_group>
<vm_source>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>