Cisco Cisco Elastic Services Controller 2.1 Developer's Guide
Multiple workflows of the same type will be processed in parallel, and a failure in any such workflow
results in the Service Deploy workflow being aborted once the remaining parallel workflows have
finished.
results in the Service Deploy workflow being aborted once the remaining parallel workflows have
finished.
If a tenant activation was attempted, then a CREATE_TENANT escEvent with either a SUCCESS or
FAILURE status will be sent describing the outcome of that workflow. Refer to section 5.1.1 for details.
FAILURE status will be sent describing the outcome of that workflow. Refer to section 5.1.1 for details.
If any ephemeral network activations were attempted, then a CREATE_NETWORK escEvent with either a
SUCCESS or FAILURE status will be sent for each network, describing the outcome of each workflow.
Refer to section 5.1.3 for details.
SUCCESS or FAILURE status will be sent for each network, describing the outcome of each workflow.
Refer to section 5.1.3 for details.
If any subnet activations for ephemeral networks were attempted, then a CREATE_SUBNET escEvent
with either a SUCCESS or FAILURE status will be sent for each subnet, describing the outcome of each
workflow. Refer to section 0 for details.
with either a SUCCESS or FAILURE status will be sent for each subnet, describing the outcome of each
workflow. Refer to section 0 for details.
An escEvent notification of type SERVICE_ALIVE with a FAILURE status will be sent to Netconf
subscribers if the configuration action cannot be completed for some reason. If a FAILURE event occurs,
there may be cleanup required as described below under Handling Activation Failures.
subscribers if the configuration action cannot be completed for some reason. If a FAILURE event occurs,
there may be cleanup required as described below under Handling Activation Failures.
Operational data
After a deploy service configuration has failed activation, there may still be operational data for any
dependent workflows that completed successfully.
dependent workflows that completed successfully.
If the tenant was successfully created, then it will show up in operational data. Refer to section 5.1.1 for
details.
details.
If any ephemeral networks were created, then they will show up in operational data. Refer to section
5.1.3 for details. NOTE: it is not possible to differentiate in operational data between regular Tenant
networks, and ephemeral (Deployment) networks.
5.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 a CREATE_SUBNET escEvent will be sent for
each subnet. Refer to section 0 for details.
each subnet. Refer to section 0 for details.
There still will be operational data for the deployment itself but will have missing information.
Handling Activation Failures
If a FAILURE event occurs while activating a deploy 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 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 Service configuration change can then be retried explicitly by the Netconf client once the
underlying issue is resolved.
Note that a tenant will never be removed by an Undeploy Service workflow, even if it was created
initially by the corresponding Deploy Service workflow.
initially by the corresponding Deploy Service workflow.