Cisco Cisco Elastic Services Controller 1.1 Developer's Guide

Page of 82
Once all the VM’s in the deployment are deployed, an escEvent of type SERVICE_UPDATED with a 
SUCCESS status will be sent: 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T20:48:24.467+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>SUCCESS</status> 
    <status_message>Service group update completed 
successfully</status_message> 
    <svcname>csr-reg</svcname> 
    <svcversion>1.2</svcversion> 
    <depname>csr-dep</depname> 
    <tenant>vnf-tenant</tenant> 
    <svcid>a4d6abc8-adaf-4e3c-a7af-382846499a58</svcid> 
    <depid>62983966-ea7d-40ea-ba83-994b0b9a6357</depid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>SERVICE_UPDATED</type> 
    </event> 
  </escEvent> 
</notification> 
 
Once the 
SERVICE_UPDATED
 event is sent, the update Service configuration has been successfully 
activated. 
Operational data 
When the update Service completes successfully, information about the newly added VNF will appear 
under the deployment 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 updated deployment: 
Netconf Request  
 
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
  <get> 
    <filter select="esc_datamodel/opdata/tenants/tenant[name=’vnf-
tenant’]/deployments[deployment_name=‘csr-dep’]" type="xpath"/> 
  </get> 
</rpc> 
 
 
 
Netconf Response  
<rpc-reply message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> 
  <data> 
    <esc_datamodel xmlns="http://www.cisco.com/esc/esc"> 
      <opdata> 
        <tenants> 
          <tenant> 
            <name>adouha_new</name> 
            <tenant_id>5272fc863c10465cb8e92f58f55248cd</tenant_id> 
            <deployments> 
              <deployment_name>adouha_dep</deployment_name> 
              <service_name>adouha_reg</service_name> 
              <service_version>1.2</service_version> 
              <deployment_id>adouha_newadouha_depadouha_reg1.2</deployment_id> 
              <service_id>adouha_reg1.2</service_id> 
              <vm_group> 
                <name>ADOUHA_ASA</name>