Cisco Cisco Elastic Services Controller 2.2 Developer's Guide

    <status_code>200</status_code>
    <status_message>Recovery: Successfully recovered VM [depzz_g1_0_50521f93-7374-
4881-960b-95aa13d55ddf].</status_message>
    <depname>depzz</depname>
    <tenant>ttt</tenant>
    <tenant_id>721d0a0aaf5a40299650d4ec74f48f1a</tenant_id>
    <svcid>NULL</svcid>
    <depid>d4778a3a-deba-4df7-9614-03f31f1beab3</depid>
    <vm_group>g1</vm_group>
    <vm_source>
      <vmid>1dd943b9-93a4-4987-b26b-1b8fd264774d</vmid>
      <hostid>4f926bb44423804ea8d87cac946b80e637c315f4f606bfa788b19b8c</hostid>

          <type>virtual</type>
          <port_id>71fd1601-f78b-41ce-a518-48fae917affb</port_id>
          <network>943fda9e-79f8-400c-b442-3506f102721a</network>
          <subnet>e313b95c-ca1f-4c81-8d60-c9e721a85d0b</subnet>
          <ip_address>192.168.0.75</ip_address>
          <mac_address>fa:16:3e:e9:23:f7</mac_address>
          <netmask>255.255.255.0</netmask>
          <gateway>192.168.0.1</gateway>
        </interface>

      </interfaces>
    </vm_target>
    <event>
      <type>VM_RECOVERY_COMPLETE</type>
    </event>
  </escEvent>
</notification>

7 ESC Triggered Workflows

7.1 Recovery (Healing) Workflow

A VM recovery is triggered in the following scenarios.

• During a service deployment if VM_ALIVE event fromany or all of the VMs being deployed by

the service is not received before the timeout value.

• After the service is deployed, if any of the VMs deployed goes down for some reason and there

are rules defined to activate VM recovery for these cases.

Recovery Initialize

When a VM recovery is triggered, an escEvent of type VM_RECOVERY_INIT with a status of SUCCESS will
be sent to Netconf subscribers. This indicates that the recovery workflow has been started. This will
hard reboot the VM instance and checks if the VM comes back up.
If the VM comes up successfully, an escEvent of type VM_RECOVERY_COMPLETE with a status of
SUCCESS with be sent.