Cisco Cisco Elastic Services Controller 1.0 Developer's Guide
On Failure:
Event notification
A series of escEvents notification may be sent during an activation failure. The notifications will appear
exactly the same as the deployment’s failure cause (See the deployment’s section for failure attempt).
The workflow will be aborted and a final escEvent notification of type SERVICE_UPDATED with a FAILURE
status is sent.
exactly the same as the deployment’s failure cause (See the deployment’s section for failure attempt).
The workflow will be aborted and a final escEvent notification of type SERVICE_UPDATED with a FAILURE
status is sent.
Operational data
After an update service configuration has failed activation, the operational data may or may not change
depending on the timing of the failure.
depending on the timing of the failure.
Handling Activation Failures
If a FAILURE event occurs while activating an update service configuration change, the Netconf client
should explicitly bring the configuration back to a consistent state by sending the corresponding
Undeploy Service configuration change. An Undeploy Service configuration change sent at this stage
should return an <ok> status, and may generate Notifications for any resource that requires cleanup.
The Deploy and Update Service configuration change can then be retried explicitly by the Netconf client
once the underlying issue is resolved.
should explicitly bring the configuration back to a consistent state by sending the corresponding
Undeploy Service configuration change. An Undeploy Service configuration change sent at this stage
should return an <ok> status, and may generate Notifications for any resource that requires cleanup.
The Deploy and Update Service configuration change can then be retried explicitly by the Netconf client
once the underlying issue is resolved.
5.2 Operational Workflows
There are 5 operations that can be done to the entire service or deployment.
• STOP
• START
• REBOOT
• DISABLE_MONITOR
• ENABLE_MONITOR
• START
• REBOOT
• DISABLE_MONITOR
• ENABLE_MONITOR
5.2.1 Service Operations
5.2.1.1 Stop Service
5.2.1.1.1 Netconf Request
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<serviceAction xmlns="http://www.cisco.com/esc/esc">
<actionType>STOP</actionType>
<tenantName>sampleTenant</tenantName>
<edit-config>
<target>
<running/>
</target>
<config>
<serviceAction xmlns="http://www.cisco.com/esc/esc">
<actionType>STOP</actionType>
<tenantName>sampleTenant</tenantName>
<depName>sampleDep </depName>
<serviceName>SampleSvc</serviceName>
<serviceVersion1.1</serviceVersion>
</serviceAction>
</config>
</edit-config>
<serviceName>SampleSvc</serviceName>
<serviceVersion1.1</serviceVersion>
</serviceAction>
</config>
</edit-config>