Cisco Cisco Elastic Services Controller 1.1 Developer's Guide

5.2.2.3 Reboot VM

5.2.2.3.1 Netconf Request

    <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.

5.2.2.3.2 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 section

3.2.1 Stage 1:

Acceptance or Rejection of

a Configuration Request for more details.

5.2.2.3.3 Event Notifications

When the VM is successfully rebooted, ESC will send a notification:

<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
  <eventTime>2015-05-19T21:21:00.262+00:00</eventTime>
  <escEvent xmlns="http://www.cisco.com/esc/esc">
    <status>SUCCESS</status>
    <status_message>VM successfully rebooted</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_REBOOTED</type>
    </event>
  </escEvent>
</notification>