Cisco Cisco Elastic Services Controller 1.1 Developer's Guide

Page of 82
5.1.11.3 Configuration Activation 
On Success: 
Event notification 
A single escEvent notification of type SERVICE_REGISTRATION with a SUCCESS status will be sent to 
Netconf subscribers once the configuration activation has completed.  This indicates that the activation 
workflow is complete and the configuration resource has been successfully created in the VIM. 
 
<?xml version="1.0" encoding="UTF-8"?> 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T19:18:46.342+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>SUCCESS</status> 
    <status_message>Register service completed 
successfully</status_message> 
    <svcname>csr-reg</svcname> 
    <svcversion>1.2</svcversion> 
    <svcid>5a96dcfd-a404-43fa-8b00-01bd68af5048</svcid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>SERVICE_REGISTRATION</type> 
    </event> 
  </escEvent> 
</notification> 
 
 
Operational data 
Not applicable. There is no operational data for service registration. 
On Failure: 
Event notification 
An escEvent notification of type SERVICE_REGISTRATION with a FAILURE status will be sent to Netconf 
subscribers if the configuration action cannot be complete for some reason.  If a FAILURE event occurs, 
there may be cleanup required as described below under 
Handling Activation Failures
Notification example: 
<?xml version="1.0" encoding="UTF-8"?> 
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> 
  <eventTime>2015-05-19T19:18:48.342+00:00</eventTime> 
  <escEvent xmlns="http://www.cisco.com/esc/esc"> 
    <status>FAILURE</status> 
    <status_message>Register service failed</status_message> 
    <svcname>csr-reg</svcname> 
    <svcversion>1.2</svcversion> 
    <svcid>5a96dcfd-a404-43fa-8b00-01bd68af5048</svcid> 
    <vm_source> 
  </vm_source> 
    <vm_target> 
  </vm_target> 
    <event> 
      <type>SERVICE_REGISTRATION</type> 
    </event>