Cisco Cisco Elastic Services Controller 1.1 Developer's Guide

<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
  <eventTime>2015-04-28T23:38:21.656+00:00</eventTime>
  <escEvent xmlns="http://www.cisco.com/esc/esc">
    <status>SUCCESS</status>
    <status_message>Service group deployment completed
successfully!</status_message>
    <svcname>csr-reg</svcname>
    <svcversion>1.2</svcversion>
    <depname>csr-dep</depname>
    <tenant>vnf-tenant</tenant>
    <svcid>e20f8ed6-a9cd-4d30-ac5b-6c3be35e38ba</svcid>
    <depid>3e0d269a-c3a4-454a-832f-44e0528ed2c1</depid>

    <vm_source/>
    <vm_target/>
    <event>
      <type>SERVICE_ALIVE</type>
    </event>
  </escEvent>
</notification>

Once the SERVICE_ALIVE event is sent, the Deploy Service configuration has been successfully activated.

Operational data

If the tenant was created, then it will show up in operational data. Refer to section 6.1.1 for details.

If any ephemeral networks were created, then they will show up in operational data. Refer to section
6.1.3 for details. NOTE: it is not possible to differentiate in operational data between regular Tenant
networks, and ephemeral (Deployment) networks.

If any subnets for ephemeral networks were created, then they will show up in operational data. Refer
to section 6.1.5 for details.

When the Deploy Service completes successfully, the deployment will appear in the operational data. A
Netconf request can be sent using the get method with an appropriate filter to query the operational
data of the deployment:

Netconf Request

Netconf Response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <data>
    <esc_datamodel xmlns="http://www.cisco.com/esc/esc">
      <opdata>
        <tenants>
          <tenant>
            <name>vnf-tenant</name>
            <deployments>
              <deployment_name>csr-dep</deployment_name>
              <service_name>csr-reg</service_name>
              <service_version>1.2</service_version>