Cisco Cisco Elastic Services Controller 2.3 Developer's Guide

Page of 85
      <serviceAction xmlns="http://www.cisco.com/esc/esc"> 
        <actionType>ENABLE_MONITOR</actionType> 
        <tenantName>sampleTenant</tenantName> 
        <depName>sampleDep </depName> 
      </serviceAction> 
    </config> 
  </edit-config> 
</rpc> 
 
 
6.2.1.5.1  Netconf Response  
 
An rpc-reply response is returned with a status of ok if the request was accepted for 
activation, or a status of rpc-error if the request was rejected.  See sectio
a Configuration Request  for more details. 
 
 
6.2.1.5.2  Event Notifications 
All VMs have their monitors first. When one VM gets alive, ESC will send the notification indicating VM is 
alive:
 
<?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_Alive event received, VM ID: [CIRROS_HEZH__614__hezh-
yesc-0520__hezh-yesc-0520depCIRROS_HEZH1.6__0__CSR__0]</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> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>VM_ALIVE</type> 
    </event> 
  </escEvent> 
</notification> 
 
When all VMs are alive, there is a final notification: 
<?xml version="1.0" encoding="UTF-8"?> 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T23:46:36.487+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>SUCCESS</status> 
    <status_message>Service group set monitor successfully</status_message> 
    <depname>dep</depname> 
    <tenant>hezh-yesc-0520</tenant> 
    <depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>SERVICE_ALIVE</type>