When a service is
ordered through the NFVO UI, NFVO sends a deploy request to ESC. The request is
in the form of a template, consisting of xml payload with names, interfaces,
day-0 configuration and so on. During VNF deployment, an instance of the
registered VNF is created.
you can update dep.xml with any new policies, affinity and anti-affinity rules,
startup order dependency and single deployment details.
See the Elastics Services Controller Registration and Deployment Attributes page for details.
While deploying a VNF, you can either use the existing tenant, network or subnetwork, or create them as part of the VNF deployment request. You can place a single deployment request to create tenant, network and subnetwork along with the VNF. For more details, see Unified Deployment Request.
If you are using the NETCONF / YANG interface, then a success notification is triggered after the deployment is complete. You can also refer to the operational data details to query the list of successful deployments.
If you are using the REST APIs, you will receive callbacks for each VM that gets deployed. You will receive callback at different stages of deployment. A callback is triggered when the VM is being processed for deployment, when the VM is successfully deployed, and when the VM is alive. A final callback is triggered when the deployment of the VM group is completed successfully.
A sample REST Request is as follows:
POST /v0/deployments/123 HTTP/1.1
. . .
First stage callback for deployment is as follows:
HTTP/1.1 200 OK
Content-Type: application/xml; charset=UTF-8
ESC-Status-Message: VM successfully created
Date: Sun, 1 Jan 2011 9:00:00 GMT
<?xml version="1.0" encoding="UTF-8"?>
See the Cisco Elastic Services Controller 1.0 REST API Guide for other details.
Using the Network Universal
Unique Identifier (UUID)
You can either use
network UUID or name to refer to a network created using ESC or OpenStack.
While using a
network name in the interface, if there are networks with duplicate network
names, and the tenant that is getting deployed already has a network by that
name in its own network pool, then the tenant's own network will take
precedence over others and will be used for the deployment. If the deploying
tenant does not have a network by that name in its own pool then it will query
for any shared networks for that name and if there is only one network by that
name then it will use that one otherwise if there are duplicate shared networks
then the deployment will be rejected altogether.
If the tenant really
wants to deploy using a specific network and might already have a network with
the same name as that desired network then the a Network UUID should be passed
in the interface instead.
through unified deployments are private networks only. ESC rejects creating
shared and external networks.