Cisco Cisco Elastic Services Controller 2.3 Guida Dello Sviluppatore
6.1.15 Deploy Service
In Deploy service, northbound sends the request to do the deployment. ESC datamodel
provides the detailed definition of the deployment request. In a single deployment, we can have
multiple vm groups. Each vm group defines the vnf\vm level deployment details including interface,
image, flavor, scale, placement etc. The kpi\monitoring rules, events, recovery polices, redeploy
policies, life cycle stage customization can all be configured with in a deployment. For a complete list of
supported parameters, please refer the ESC datamodel.
multiple vm groups. Each vm group defines the vnf\vm level deployment details including interface,
image, flavor, scale, placement etc. The kpi\monitoring rules, events, recovery polices, redeploy
policies, life cycle stage customization can all be configured with in a deployment. For a complete list of
supported parameters, please refer the ESC datamodel.
A Deploy Service configuration request may contain multiple dependent workflows, in which case it can
be referred to as a Unified Deployment. These workflows are:
be referred to as a Unified Deployment. These workflows are:
• Create zero or one Tenant (if it doesn’t already exist in ESC)
• Create zero or more Networks (if any networks are specified in the deployment)
• Create zero or more Subnets (if specified for any networks in the deployment)
• Create zero or more Networks (if any networks are specified in the deployment)
• Create zero or more Subnets (if specified for any networks in the deployment)
Networks that are created as part of a Deploy Service workflow are referred to as “ephemeral
networks”, and the lifecycle of these networks is bound to the lifecycle of the Deployment in ESC. An
Un-deploy Service workflow will automatically delete any networks and subnets that were originally
created during the Deploy Service workflow.
networks”, and the lifecycle of these networks is bound to the lifecycle of the Deployment in ESC. An
Un-deploy Service workflow will automatically delete any networks and subnets that were originally
created during the Deploy Service workflow.
Tenants that are created during a Deploy Service workflow are NOT deleted when the service is
undeployed.
undeployed.
Note – Unified Deployment is not supported for VMWare VIM in this release!
6.1.15.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>
<tenant>
<name>vnf-tenant</name>
<deployments>
<deployment>
<name>csr-dep</name>
<networks>
<network>
<network>
<name>mk-yesc-net-u</name>
<shared>false</shared>
<admin_state>true</admin_state>
<subnet>
<name>mk-yesc-subnet-u</name>
<ipversion>ipv4</ipversion>
<dhcp>true</dhcp>
<address>10.91.90.0</address>
<netmask>255.255.255.0</netmask>
<shared>false</shared>
<admin_state>true</admin_state>
<subnet>
<name>mk-yesc-subnet-u</name>
<ipversion>ipv4</ipversion>
<dhcp>true</dhcp>
<address>10.91.90.0</address>
<netmask>255.255.255.0</netmask>