Cisco Cisco Elastic Services Controller 2.3 Developer's Guide
Deploy service configuration change can then be retried explicitly by the Netconf client once the
underlying issue is resolved. Refer to section 6.1.9 for Deploy service configuration.
underlying issue is resolved. Refer to section 6.1.9 for Deploy service configuration.
7.2 Scale Out/Scale in Work Flows
7.2.1
Scale Out Work Flow
A scale-out work flow will be triggered if the current VNF is overloaded. From the user side, no request
is required to trigger a scale-out. The monitors attached to a VNF will trigger it if necessary.
is required to trigger a scale-out. The monitors attached to a VNF will trigger it if necessary.
7.2.1.1 Event Notifications
There are three notifications sent to NB during a successful scale out:
1. When a scale-out 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>
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 out triggered</status_message>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<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>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<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_INIT</type>
</event>
</escEvent>
</notification>
</vm_target>
<event>
<type>VM_SCALE_OUT_INIT</type>
</event>
</escEvent>
</notification>
2. The scale-out deploys a new VM. When the new VM is deployed, a notification
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>SUCCESS</status>
<status_message>VM deployed</status_message>
<depname>dep</depname>
<tenant>hezh-yesc-0520</tenant>
<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>
<vmid>5283bcab-c1c3-4699-9bbe-cf143b26c6aa</vmid>
<hostid>c64e652a4561392ae20ae702eceae53e417302e0d2d63e41d66a15cc</hostid>
</vm_source>
<vm_target>
</vm_target>
<event>
<type>VM_SCALE_OUT_DEPLOYED</type>
</event>
</escEvent>
</notification>
<vm_target>
</vm_target>
<event>
<type>VM_SCALE_OUT_DEPLOYED</type>
</event>
</escEvent>
</notification>