Cisco Cisco Elastic Services Controller 2.0 Developer's Guide

              <deployment_id>vnf-tenantcsr-depcsr-reg1.2</deployment_id> 
              <service_id>csr-reg1.2</service_id> 
              <vm_group> 
                <name>csr-vm</name> 
                <vm_instance> 
                  <vm_id>0bee67cc-f415-4f6a-95fe-e00e5d8d7c57</vm_id> 
                  <name>csr-reg__12605__vnf-tenant__vnf-tenantcsr-depcsr-
reg1.2__0__csr-vm__0</name> 
                  
<host_id>109ec6a9b7c4613e5b73942e8cc998ebd9434a17c552e5e01847e402</host_id> 
                  <hostname>compute-host-1</hostname> 
                  <interfaces> 
                    <interface> 
                      <nicid>0</nicid> 
                      <port_id>66ba846f-c02a-4c2b-964b-
4572d938b5e4</port_id> 
                      <network>7af5c7df-6246-4d53-91bd-
aa12a1607656</network> 
                      <subnet>7cb6815e-3023-4420-87d8-2b10efcbe14e</subnet> 
                      <ip_address>192.168.0.58</ip_address> 
                      <mac_address>fa:16:3e:c0:fd:49</mac_address> 
                    </interface> 
                    <interface> 
                      <nicid>1</nicid> 
                      <port_id>f6a1d46d-d5ad-4b7e-a48a-
3d539a920994</port_id> 
                      <network>a39af676-5004-4f2d-8b7b-
d4c804645dc3</network> 
                      <subnet>de4625ad-5465-4812-ab9c-de4a0ed21063</subnet> 
                      <ip_address>10.91.90.2</ip_address> 
                      <mac_address>fa:16:3e:64:8c:a6</mac_address> 
                    </interface> 
                  </interfaces> 
                </vm_instance> 
              </vm_group> 
              <state_machine> 
                <state>SERVICE_ACTIVE_STATE</state> 
                <vm_state_machines> 
                  <vm_state_machine> 
                    <vm_name> csr-reg__12605__vnf-tenant__vnf-tenantcsr-
depcsr-reg1.2__0__csr-vm__0</vm_name> 
                    <state>VM_ALIVE_STATE</state> 
                  </vm_state_machine> 
                </vm_state_machines> 
              </state_machine> 
            </deployments> 
          </tenant> 
        </tenants> 
      </opdata> 
    </esc_datamodel> 
  </data> 
</rpc-reply> 

On Failure: 

A series of escEvent notifications may be sent to Netconf subscribers once the individual workflows in 
the configuration activation have completed.   

Workflows of different types in the configuration activation run in sequence.  If an activation failure 
occurs in one of these workflows, and the appropriate escEvent with a FAILURE status is sent, then the 
Service Deploy workflow is aborted and no more workflows will be processed.