Cisco Cisco Elastic Services Controller 2.2 Developer's Guide

      <type>VM_ALIVE</type> 
    </event> 
  </escEvent> 
</notification> 

 

If there are errors during starting the VM, there will be a final notification indicating the error: 

<?xml version="1.0" encoding="UTF-8"?> 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T21:21:00.527+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>FAILURE</status> 
    <status_message>VM start failed</status_message> 
    <depname>dep</depname> 
    <tenant>hezh-yesc-0520</tenant> 
    <svcid>NULL</svcid> 

    <depid>187bc0b5-9d0b-4c01-8353-89454a6a1da6</depid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>VM_STARTED</type> 
    </event> 
  </escEvent> 

</notification> 

 

6.2.2.3.1  Netconf Request  

<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
  <edit-config> 
    <target> 
      <running/> 

    </target> 
    <config> 
      <vmAction xmlns="http://www.cisco.com/esc/esc"> 
        <actionType>REBOOT</actionType> 
        <vmName>sampleVmName</vmName> 
        <force>true/false</force> 

      </vmAction> 
    </config> 
  </edit-config> 
</rpc> 

The “force” option in the request decides if ESC considers the min_vm requirement for the service. 

Since stopping a VM would affect the service availability, after the VM is rebooted the min_vm 

requirement specified in the datamodel may not be satisfitied. If the “force” option is true, ESC will 

ignore the requirement for min_vm.