cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
138
Views
1
Helpful
4
Replies
khgrant
Cisco Employee

ESC Services vs. deployments

 

Hi Team,

 

 

We can successfully interfaced with ESC via the netconf interface. We did a load-merge of our dep.xml file into the ESC config data tree and voila we had a “deployment”.

 

 

So next we wanted to use the vm-manager-esc to do the deployment vs. a load-merge directly into the CDB. But that is where the question comes in.

 

 

What is the difference between a service and a deployment? In the ESC-NSO guide it says that after the VM is deployed it is loaded into the tenants/services area not the tenants/deployments.

 

 

 

The ESC netconf_api guide, and our dep.xml file loads the config into the tenants/deployment part of the ESC yang model – this works great and our “deployment” spun up on the openstack.

 

 

<esc_datamodel xmlns="http://www.cisco.com/esc/esc">

 

    <tenants tags="merge">

 

        <tenant>

 

            <name>Core1</name>

 

            <deployments>

 

                <deployment>

 

                    <name>cisco-vpc1</name>

 

 

 


However, When looking at the vm-manager-esc – the templates and examples in the associated ESC-nso pdf in the virtual_mpls load the data into the tenants/services:

 

 

<config-template xmlns="http://tail-f.com/ns/config/1.0">

 

  <devices xmlns="http://tail-f.com/ns/ncs">

 

    <device tags="nocreate">

 

      <name>{$ESC}</name>

 

      <config>

 

        <esc_datamodel xmlns="http://www.cisco.com/esc/esc">

 

          <tenants tags="merge">

 

            <tenant>

 

              <name>{$TENANT}</name>

 

              <services>

 

                <service_definition>

 

                  <deployment_name>{$DEPNAME}</deployment_name>

 

                  <name>{$SERVICE_NAME}</name>

 

4 REPLIES 4
khgrant
Cisco Employee

 

Hi Julie,

 

 

The tenants/services is an old model that we used to support in ESC.

 

It has been deprecated. The docs you have from NSO are outdated.

 

Please use the tenants/deployments model moving on.

 

 

Thanks,

 

Elie

 

khgrant
Cisco Employee

 

Elie,

 

 

Thanks as usual for the quick response.

 

 

NSO Team – is the vm-manager-esc that is available on devnet for 4.1 – is this going to be updated to use deployments vs. services?

 

 

I’m using:

 

 

[jconnary@localhost packages]$ ls

 

cisco-ios     esc                  mme                                  oamtest

 

cisco-iosxr   esc.tar.gz           ncs-4.1.1-vm-manager-1.0.tar.gz      resource-manager

 

cisco-nx      id-allocator         ncs-4.1.1-vm-manager-esc-1.0.tar.gz  saegw

 

cisco-staros  ipaddress-allocator  nso-util                             vm-manager-esc

 

[jconnary@localhost packages]$

 

 

Thanks, JA

 

khgrant
Cisco Employee

 

Hello Julie,

 

 

All you need is to change XML template located at vm-manager-esc/templates.

 

 

By default, vmRFS.java applies following three files:

 

- vm-esc-tenant-template.xml

 

- vm-esc-scaling-template.xml

 

- vm-esc-interface-template.xml

 

 

Hope this helps.

 

 

Best regards,

 

Hiro

 

khgrant
Cisco Employee

 

Thanks,

 

 

I can update the templates.

 

 

Next question – if my Application consists of multiple VMs, each one a vm-group.

 

 

Can I send in an XML file via REST to the vm-manager-esc with multiple vm-groups and kick off the creation of these multiple VMs? As it appears that vm-manager-esc will instantiate a single VM group?

 

 

The application is vpc-di – our virtual packet core which consists of 6 VMs minimum.

 

 

JA

 

Create
Recognize Your Peers
Content for Community-Ad