Cisco Cisco Elastic Services Controller 1.1 Developer's Guide
5.1.14 Un-deploy Service
An un-deploy Service configuration request may contain multiple dependent workflows, in which case it
can be referred to as a Unified un-deployment. These workflows are:
can be referred to as a Unified un-deployment. These workflows are:
• Delete zero or more Subnets (if specified for any networks in the deployment)
• Delete zero or more Networks (if any networks are specified in the deployment)
• Delete zero or more Networks (if any networks are specified in the deployment)
Tenants that are created during a Deploy Service workflow are NOT deleted when the service is
undeployed.
undeployed.
5.1.14.1 Netconf Request
<rpc message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<tenants>
<edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<running/>
</target>
<config>
<esc_datamodel xmlns="http://www.cisco.com/esc/esc">
<tenants>
<tenant>
<name>vnf-tenant</name>
<services>
<service_definition nc:operation="delete">
<deployment_name>csr-dep</deployment_name>
<name>csr-reg</name>
<version>1.2</version>
</service_definition>
</services>
<name>vnf-tenant</name>
<services>
<service_definition nc:operation="delete">
<deployment_name>csr-dep</deployment_name>
<name>csr-reg</name>
<version>1.2</version>
</service_definition>
</services>
</tenant>
</tenants>
</esc_datamodel>
</tenants>
</esc_datamodel>
</config>
</edit-config>
</rpc>
5.1.14.2 Netconf Response
An rpc-reply response is returned with a status of ok if the request was accepted for activation, or a
status of rpc-error if the request was rejected. See section
status of rpc-error if the request was rejected. See section
5.1.14.3 Configuration Activation
Workflow Aggregation:
For each dependent delete workflow specified in the configuration, a separate workflow is submitted.
Refer to the specific workflow description for information on configuration activation of each of these
optional workflows. The undeployment starts with undeploying the service VMs first then it moves
onto deleting the dependent resource objects and will be processed in the following order:
Refer to the specific workflow description for information on configuration activation of each of these
optional workflows. The undeployment starts with undeploying the service VMs first then it moves
onto deleting the dependent resource objects and will be processed in the following order:
Section 6.1.6: Delete a Subnet for a Tenant (zero or more)
Section 6.1.4: Delete a Network for a Tenant (zero or more)