Virtual Infrastructure Manager Installation Automation

Size: px

Start display at page:

Download "Virtual Infrastructure Manager Installation Automation"

Gwendoline O’Neal’
6 years ago
Views:

Virtual Infrastructure Manager Installation Automation Feature Summary and Revision History, page 1 Feature Description, page 2 VIM Installation Automation Overview, page 2 Sample Configuration

1 Virtual Infrastructure Manager Installation Automation Feature Summary and Revision History, page 1 Feature Description, page 2 VIM Installation Automation Overview, page 2 Sample Configuration Files, page 5 Feature Summary and Revision History Summary Data Applicable Product(s) or Functional Area Ultra M Solution Applicable Platform(s) Ultra Gateway Platform Feature Default Enabled Related Changes in This Release Not applicable Related Documentation USP Deployment Automation Guide Revision History Revision Details Release First Introduced. N

2 Feature Description Virtual Infrastructure Manager Installation Automation Feature Description Note This feature deprecates the NFVI Deployment Automation feature added in Release Leveraging RedHat and OpenStack s TripleO project concepts, UAS supports the ability to automate the deployment of both the virtual infrastructure manager (VIM, the Triple O Overcloud) and the VIM Orchestrator (the TripleO Undercloud). Installing the VIM Orchestrator and the VIM involves deploying the following components as VMs on a RedHat Enterprise Linux (RHEL) server: AutoIT-NVFI AutoDeploy OpenStack Platform Director (OSP-D) VIM Orchestrator and VIM settings are maintained in configuration files which are used by AutoDeploy. AutoDeploy processes the VIM Orchestrator configuration and works with AutoIT-NFVI to automate the deployment of a VM running OSP-D which serves as the Undercloud. Once this operation is successful, AutoDeploy processes the VIM configuration and works with AutoIT-NFVI to deploy the OpenStack Overcloud. Notes: This functionality is supported only with Ultra M deployments based on OSP 10 and that leverage the Hyper-Converged architecture. Before the N5.5 Ultra Service Platform (USP) release, OSP-D was deployed on its own physical server. With this release, this feature leverages this same physical server for the installation of VMs for AutoIT-NFVI, AutoDeploy, and OSP-D. This server is now referred to as the Ultra M Manager. VIM Installation Automation Overview Figure 1: NFVI Deployment Automation Workflow, on page 3 provides an overview of the deployment automation process. Details are provided in Table 1: Virtual Infrastructure Manager Installation Automation Workflow Descriptions, on page 3. This information assumes that all prerequisite hardware has been installed, cabled, and configured. 2

Virtual Infrastructure Manager Installation Automation VIM Installation Automation Overview Note The workflow information in this section assumes a new deployment scenario.

3 Virtual Infrastructure Manager Installation Automation VIM Installation Automation Overview Note The workflow information in this section assumes a new deployment scenario. If you are using this feature in relation with an upgrade process, please contact your support representative for complete details. Figure 1: NFVI Deployment Automation Workflow Table 1: Virtual Infrastructure Manager Installation Automation Workflow Descriptions Callout Description Install RedHat Enterprise Linux (RHEL) operating system on bare metal hardware (Ultra M Manager). Deploy the AutoIT-NFVI VM. Deploy the AutoDeploy VM. 3

4 VIM Installation Automation Overview Virtual Infrastructure Manager Installation Automation Callout Description Prepare the VIM Orchestrator configuration file that is used by AutoDeploy to initiate the OSP-D VM deployment process. This file includes all of the configuration information required to deploy OSP-D VM including configurations for constructs such as secure tokens, package images, NFVI point-of-presence descriptors (nfvi-popd), and the VIM Orchestrator descriptor (vim-orchd). Note The VIM Orchestrator and VIM configuration information can be prepared and maintatined in separate files or combined into a single file. Figure 1: NFVI Deployment Automation Workflow, on page 3 depicts the configurations in separate files for illustration purposes. Note, however, that UWS requires that both the the VIM Orchestrator and VIM configuration be provided in a single file. On the AutoDeploy VM, load, commit, and then activate the configuration file prepared in previous step. Once commited, activate the previously loaded VIM Orchestrator configuration file. AutoDeploy passes data from the activated configuration to AutoIT-NFVI requesting that it deploy the OSP-D VM for the Undercloud. AutoIT-NFVI deploys the OSP-D VM which serves as the Undercloud. Prepare the VIM configuration file that is used by AutoDeploy to initiate the VIM (Overcloud) installation process. This file includes all of the configuration information required to deploy the VIM components including configurations for constructs such as secure tokens, node parameters, NFVI point-of-presence descriptors (nfvi-popd), and the VIM descriptor (vimd). Note The VIM Orchestrator and VIM configuration information can be prepared and maintatined in separate files or combined into a single file. Figure 1: NFVI Deployment Automation Workflow, on page 3 depicts the configurations in separate files for illustration purposes. Note, however, that UWS requires that both the the VIM Orchestrator and VIM configuration be provided in a single file. On the AutoDeploy VM, load, commit, and then activate the configuration file prepared in the previous step. AutoDeploy passes data from the activated configuration to AutoIT-NFVI for delivery to the OSP-D VM responsible for installing the VIM. AutoIT-NFVI initiates the VIM installation by passing parameters received from AutoDeploy to the OSP-D VM. The OSP-D VM installs the VIM per the configuration requirements. 4

5 Virtual Infrastructure Manager Installation Automation Related UWS Enhancements Related UWS Enhancements From this release, the Ultra Web Service (UWS) - AutoDeploy web interface can be used to provision and activate the VIM Orchestrator (undercloud) and VIM (overcloud) for sites within a service deployment. Each site can be mapped to one VIM-Orch and VIM. Sites can be activated from the Service Deployment screen only when the VIM-Orch and VIM for the site are activated. A Pod screen in the UWS - AutoDeploy web Interface is available to view the VIM-Orch and VIM nodes. Activation and deactivation of the VIM-Orch and VIM can be monitored using a progress bar on the Pod screen. The UWS - AutoDeploy web interface now supports the following information in the YANG-compliant deployment configuration XML file to identify and deploy VIM-Orch and VIM nodes, and bring up the OSP-D as a VM: nfvi-popd vim-orchd vimd sited auto-it-nfvi nfvi-pop vim-orch vim Sample Configuration Files Sample configuration files for deploying the VIM Orchestrator and VIM through the ConfD command line and/or through UWS are provided in the following sections. Sample VIM Orchestrator Configuration File The VIM Ochestrator configuration file dictates the deployment of the VIM Orchestrator (Undercloud). The parameters within the file are derived from a YANG model as described in USP Deployment Automation Guide. The file below is an example of an VIM Orchestrator configuration file to bring up a single OSP-D VM on the Ultra M Manager. 5

6 Sample VIM Orchestrator Configuration File Virtual Infrastructure Manager Installation Automation Caution This is only a sample configuration file provided solely for your reference. You must create and modify your own configuration file according to the specific needs of your deployment such as: Secure-tokens NFVI PoP details VIM orchestrator details Site details Networking details Service deployment details ## FOR CDN SERVER secure-token autonfvi-subscription ## user ultra-m-install secure-token autonfvi-admin-netconf user admin secure-token autonfvi-oper-netconf user oper secure-token autoit-nfvi-ospd user stack secure-token autoit-nfvi-login user ubuntu secure-token cimc-login user admin secure-token ssh-baremetal user nfvi nfvi-popd uws-nfvi-pop deployment-flavor ucs-1-vnf nfvi-node autoit-nfvi-physical-node description nfvi-pop physical-network-interface [ 00:2c:c8:da:29:4b ] physical-server-manager ip-address vim-orchd sjc-vim-orch hostname sjc-undercloud-ab domain-name cisco.com dns [ ] login-credential autoit-nfvi-ospd ## SATELLITE-SERVER-CONFIG ## satellite-server ip-address satellite-server hostname rh-satellite satellite-server domain-name cisco.com satellite-server organization ultram satellite-server activation-key "openstack 10" satellite-server pool-id 8a977cf75c0ca9df015d2ce1cb4d06ab external-network ip-address external-network netmask provisioning-network ip-address

7 Virtual Infrastructure Manager Installation Automation Sample VIM Configuration File provisioning-network netmask provisioning-network public-vip provisioning-network admin-vip provisioning-network dhcp-ip-range start provisioning-network dhcp-ip-range end provisioning-network inspection-ip-range start provisioning-network inspection-ip-range end network-cidr /8 masquerade-network /8 nfvi-node id autoit-nfvi-physical-node nfvi-node ip-address nfvi-node login-credential ssh-baremetal ## CDN SERVER CONFIG ## cdn-server login-credential subs cdn-server proxy proxy-wsa.esl.cisco.com:80 cdn-server pool-id 8a85f a01578b1e1cbd2275 ## SUBSCRIPTION MANAGER (DEV SETUP) ## subscription-manager login-credential autonfvi-subscription subscription-manager proxy proxy-wsa.esl.cisco.com:80 image /home/ubuntu/rhel-server-7.3-x86_64-dvd.iso flavor vcpus 4 flavor ram flavor root-disk 100 flavor ephemeral-disk 0 flavor swap-disk 0 sited auto-test-sjc auto-it-vim type openstack auto-it-vim auth-url auto-it-vim tenant core auto-it-nfvi scm-admin autonfvi-admin-netconf auto-it-nfvi scm-oper autonfvi-oper-netconf auto-it-nfvi ip-address auto-it-nfvi authentication-info autoit-nfvi-login nfvi-pop uws-nfvi-pop vim-orch sjc-vim-orch service-deployment north-east description "Single site multiple Vnfs ServiceDeployment" sited auto-test-sjc site-ref auto-test-sjc Sample VIM Configuration File The VIM configuration file dictates the deployment of the VIM (Overcloud). The parameters within the file are derived from a YANG model as described in the USP Deployment Automation Guide. The file below is an example of an VIM configuration file to bring up the VIM within Ultra M deployments based on OSP 10 and that leverage the Hyper-Converged architecture. 7

8 Sample VIM Configuration File Virtual Infrastructure Manager Installation Automation Caution This is only a sample configuration file provided solely for your reference. You must create and modify your own configuration file according to the specific needs of your deployment such as: Secure-tokens NFVI PoP details VIM details VIM node details Site details Networking details Service deployment details ## FOR CDN SERVER secure-token autonfvi-subscription ## user ultra-m-install secure-token autonfvi-admin-netconf user admin secure-token autonfvi-oper-netconf user oper secure-token autoit-nfvi-ospd user stack secure-token autoit-nfvi-login user ubuntu secure-token cimc-login user admin secure-token ssh-baremetal user nfvi nfvi-popd uws-nfvi-pop deployment-flavor ucs-1-vnf nfvi-node autoit-nfvi-physical-node description nfvi-pop physical-network-interface [ 00:2c:c8:da:29:4b ] physical-server-manager ip-address nfvi-node node_1 physical-server-manager ip-address nfvi-node node_2 physical-server-manager ip-address nfvi-node node_3 physical-server-manager ip-address nfvi-node node_4 physical-server-manager ip-address

9 Virtual Infrastructure Manager Installation Automation Sample VIM Configuration File nfvi-node node_5 physical-server-manager ip-address nfvi-node node_6 physical-server-manager ip-address nfvi-node node_7 physical-server-manager ip-address nfvi-node node_8 physical-server-manager ip-address nfvi-node node_9 physical-server-manager ip-address nfvi-node node_10 physical-server-manager ip-address nfvi-node node_11 physical-server-manager ip-address nfvi-node node_12 physical-server-manager ip-address nfvi-node node_13 physical-server-manager ip-address nfvi-node node_14 physical-server-manager ip-address nfvi-node node_15 physical-server-manager ip-address nfvi-node node_16 physical-server-manager ip-address nfvi-node node_17 physical-server-manager ip-address nfvi-node node_18 physical-server-manager ip-address nfvi-node node_19 physical-server-manager ip-address nfvi-node node_20 physical-server-manager ip-address nfvi-node node_21 physical-server-manager ip-address nfvi-node node_22 physical-server-manager ip-address

10 Sample VIM Configuration File Virtual Infrastructure Manager Installation Automation vim-orchd sjc-vim-orch hostname sjc-undercloud-ab domain-name cisco.com dns [ ] login-credential autoit-nfvi-ospd ## SATELLITE-SERVER-CONFIG ## satellite-server ip-address satellite-server hostname rh-satellite satellite-server domain-name cisco.com satellite-server organization ultram satellite-server activation-key "openstack 10" satellite-server pool-id 8a977cf75c0ca9df015d2ce1cb4d06ab external-network ip-address external-network netmask provisioning-network ip-address provisioning-network netmask provisioning-network public-vip provisioning-network admin-vip provisioning-network dhcp-ip-range start provisioning-network dhcp-ip-range end provisioning-network inspection-ip-range start provisioning-network inspection-ip-range end network-cidr /8 masquerade-network /8 nfvi-node id autoit-nfvi-physical-node nfvi-node ip-address nfvi-node login-credential ssh-baremetal ## CDN SERVER CONFIG ## cdn-server login-credential subs cdn-server proxy proxy-wsa.esl.cisco.com:80 cdn-server pool-id 8a85f a01578b1e1cbd2275 ## SUBSCRIPTION MANAGER (DEV SETUP) ## subscription-manager login-credential autonfvi-subscription subscription-manager proxy proxy-wsa.esl.cisco.com:80 image /home/ubuntu/rhel-server-7.3-x86_64-dvd.iso flavor vcpus 4 flavor ram flavor root-disk 100 flavor ephemeral-disk 0 flavor swap-disk 0 vimd vnf1-vim nfvi-nodes node_1 role vim-controller nfvi-nodes node_2 role vim-controller nfvi-nodes node_3 role vim-controller nfvi-nodes node_4 nfvi-nodes node_5 nfvi-nodes node_6 nfvi-nodes node_7 nfvi-nodes node_8 nfvi-nodes node_9 nfvi-nodes node_10 nfvi-nodes node_11 10

11 Virtual Infrastructure Manager Installation Automation Sample VIM Configuration File nfvi-nodes node_12 nfvi-nodes node_13 nfvi-nodes node_14 nfvi-nodes node_15 nfvi-nodes node_16 nfvi-nodes node_17 nfvi-nodes node_18 nfvi-nodes node_19 nfvi-nodes node_20 role vim-osd-compute nfvi-nodes node_21 role vim-osd-compute nfvi-nodes node_22 role vim-osd-compute networking dns [ ] networking nat networking vlan-pool start 20 networking vlan-pool end 200 networking network-types internal-api ip-prefix /24 vlan-id 20 allocation-pool start allocation-pool end networking network-types tenant ip-prefix /24 vlan-id 17 allocation-pool start allocation-pool end networking network-types storage ip-prefix /24 vlan-id 18 allocation-pool start allocation-pool end networking network-types storage-mgmt ip-prefix /24 vlan-id 19 allocation-pool start allocation-pool end networking network-types external ip-prefix /24 vlan-id 522 allocation-pool start allocation-pool end default-route sited auto-test-sjc auto-it-vim type openstack 11

Sample UWS VIM Orchestrator and VIM Configuration File Virtual Infrastructure Manager Installation Automation auto-it-vim auth-url http://172.25.22.67:5000/v2.

12 Sample UWS VIM Orchestrator and VIM Configuration File Virtual Infrastructure Manager Installation Automation auto-it-vim auth-url auto-it-vim tenant core auto-it-nfvi scm-admin autonfvi-admin-netconf auto-it-nfvi scm-oper autonfvi-oper-netconf auto-it-nfvi ip-address auto-it-nfvi authentication-info autoit-nfvi-login nfvi-pop uws-nfvi-pop vim-orch sjc-vim-orch vim vnf1-vim service-deployment north-east description "Single site multiple Vnfs ServiceDeployment" sited auto-test-sjc site-ref auto-test-sjc Sample UWS VIM Orchestrator and VIM Configuration File The VIM Orchestrator and VIM configuration file dictates the deployment of the VIM Orchestrator (Undercloud) and VIM (Overcloud). The parameters within the file are derived from a YANG model as described in the USP Deployment Automation Guide. The file below is an example of a combined VIM Orchestrator and VIM configuration file used to install these items through UWS within Ultra M deployments based on OSP 10 and that leverage the Hyper-Converged architecture. Caution This is only a sample configuration file provided solely for your reference. You must create and modify your own configuration file according to the specific needs of your deployment such as: Secure-tokens NFVI PoP details VIM orchestrator details VIM details VIM node details Site details Networking details Service deployment details <?xml version="1.0" encoding="utf-8"?> <config xmlns=" <secure-token xmlns=" <secure-id>autonfvi-admin-netconf</secure-id> <user>admin</user> <password>********</password> </secure-token> <secure-token xmlns=" <secure-id>autonfvi-oper-netconf</secure-id> <user>oper</user> <password>********</password> </secure-token> <secure-token xmlns=" <secure-id>autoit-nfvi-ospd</secure-id> <user>stack</user> <password>********</password> 12

13 Virtual Infrastructure Manager Installation Automation Sample UWS VIM Orchestrator and VIM Configuration File </secure-token> <secure-token xmlns=" <secure-id>autoit-nfvi-login</secure-id> <user>ubuntu</user> <password>********</password> </secure-token> <secure-token xmlns=" <secure-id>cimc-login</secure-id> <user>admin</user> <password>********</password> </secure-token> <secure-token xmlns=" <secure-id>ssh-baremetal</secure-id> <user>nfvi</user> <password>********</password> </secure-token> <nfvi-popd xmlns=" <name>uws-nfvi-pop</name> <deployment-flavor>ucs-1-vnf</deployment-flavor> <nfvi-node-id>autoit-nfvi-physical-node</nfvi-node-id> <description>nfvi-pop</description> <ip-address annotation="physical-network-interface [ 00:2c:c8:da:29:4b ]"> </ip-address> <nfvi-node-id>node_1</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_2</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_3</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_4</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_5</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_6</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_7</nfvi-node-id> 13

14 Sample UWS VIM Orchestrator and VIM Configuration File Virtual Infrastructure Manager Installation Automation <ip-address> </ip-address> <nfvi-node-id>node_8</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_9</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_10</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_11</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_12</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_13</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_14</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_15</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_16</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_17</nfvi-node-id> <ip-address> </ip-address> 14

15 Virtual Infrastructure Manager Installation Automation Sample UWS VIM Orchestrator and VIM Configuration File <nfvi-node-id>node_18</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_19</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_20</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_21</nfvi-node-id> <ip-address> </ip-address> <nfvi-node-id>node_22</nfvi-node-id> <ip-address> </ip-address> </nfvi-popd> <vim-orchd xmlns=" <name>sjc-vim-orch</name> <hostname>sjc-undercloud-ab</hostname> <domain-name>cisco.com</domain-name> <dns> </dns> <login-credential>autoit-nfvi-ospd</login-credential> <satellite-server> <ip-address annotation=" ## SATELLITE-SERVER-CONFIG ## "> </ip-address> <hostname>rh-satellite</hostname> <domain-name>cisco.com</domain-name> <organization>ultram</organization> <activation-key>openstack 10</activation-key> <pool-id>8a977cf75c0ca9df015d2ce1cb4d06ab</pool-id> </satellite-server> <external-network> <ip-address> </ip-address> <netmask> </netmask> </external-network> <provisioning-network> <ip-address> </ip-address> <netmask> </netmask> <public-vip> </public-vip> <admin-vip> </admin-vip> <dhcp-ip-range> <start> </start> <end> </end> </dhcp-ip-range> <inspection-ip-range> <start> </start> <end> </end> </inspection-ip-range> </provisioning-network> <network-cidr> /8</network-cidr> <masquerade-network> /8</masquerade-network> <flavor> 15

16 Sample UWS VIM Orchestrator and VIM Configuration File Virtual Infrastructure Manager Installation Automation <vcpus>4</vcpus> <ram>16384</ram> <root-disk>100</root-disk> <ephemeral-disk>0</ephemeral-disk> <swap-disk>0</swap-disk> </flavor> <id>autoit-nfvi-physical-node</id> <ip-address> </ip-address> <login-credential>ssh-baremetal</login-credential> <image annotation=" ## CDN SERVER CONFIG ## cdn-server login-credential subs cdn-server proxy proxy-wsa.esl.cisco.com:80 cdn-server pool-id 8a85f a01578b1e1cbd2275 ## SUBSCRIPTION MANAGER (DEV SETUP) ## subscription-manager login-credential autonfvi-subscription subscription-manager proxy proxy-wsa.esl.cisco.com:80 ">/home/ubuntu/rhel-server-7.3-x86_64-dvd.iso</image> </vim-orchd> <vimd xmlns=" <name>vnf1-vim</name> <id>node_1</id> <role>vim-controller</role> <id>node_2</id> <role>vim-controller</role> <id>node_3</id> <role>vim-controller</role> <id>node_4</id> <id>node_5</id> <id>node_6</id> <id>node_7</id> <id>node_8</id> <id>node_9</id> <id>node_10</id> <id>node_11</id> <id>node_12</id> <id>node_13</id> <id>node_14</id> 16

17 Virtual Infrastructure Manager Installation Automation Sample UWS VIM Orchestrator and VIM Configuration File <id>node_15</id> <id>node_16</id> <id>node_17</id> <id>node_18</id> <id>node_19</id> <id>node_20</id> <role>vim-osd-compute</role> <id>node_21</id> <role>vim-osd-compute</role> <id>node_22</id> <role>vim-osd-compute</role> <networking> <dns> </dns> <nat> </nat> <network-types> <type>internal-api</type> <ip-prefix> /24</ip-prefix> <vlan-id>20</vlan-id> <allocation-pool> <start> </start> <end> </end> </allocation-pool> </network-types> <network-types> <type>tenant</type> <ip-prefix> /24</ip-prefix> <vlan-id>17</vlan-id> <allocation-pool> <start> </start> <end> </end> </allocation-pool> </network-types> <network-types> <type>storage</type> <ip-prefix> /24</ip-prefix> <vlan-id>18</vlan-id> <allocation-pool> <start> </start> <end> </end> </allocation-pool> </network-types> <network-types> <type>storage-mgmt</type> <ip-prefix> /24</ip-prefix> <vlan-id>19</vlan-id> <allocation-pool> <start> </start> <end> </end> </allocation-pool> </network-types> 17

18 Sample UWS VIM Orchestrator and VIM Configuration File Virtual Infrastructure Manager Installation Automation <network-types> <type>external</type> <ip-prefix> /24</ip-prefix> <vlan-id>522</vlan-id> <allocation-pool> <start> </start> <end> </end> </allocation-pool> <default-route> </default-route> </network-types> <vlan-pool> <start>20</start> <end>200</end> </vlan-pool> </networking> </vimd> <sited xmlns=" <sited-id>auto-test-sjc</sited-id> <-- auto-it-vim> <type>openstack</type> <auth-url> <tenant>core</tenant> </auto-it-vim --> <auto-it-nfvi> <scm-admin annotation="auto-it-vim type openstack auto-it-vim auth-url auto-it-vim tenant core">autonfvi-admin-netconf</scm-admin> <scm-oper>autonfvi-oper-netconf</scm-oper> <ip-address> </ip-address> <authentication-info>autoit-nfvi-login</authentication-info> </auto-it-nfvi> <nfvi-pop>uws-nfvi-pop</nfvi-pop> <vim-orch>sjc-vim-orch</vim-orch> <vim>vnf1-vim</vim> </sited> <service-deployment xmlns=" <service-deployment-id>north-east</service-deployment-id> <description>single site multiple Vnfs ServiceDeployment</description> <sited> <sited-id>auto-test-sjc</sited-id> <site-ref>auto-test-sjc</site-ref> </sited> </service-deployment> </config> 18

NFVI Deployment Automation

NFVI Deployment Automation Feature Summary and Revision History, page 1 Feature Description, page 2 AutoDeploy Configuration File Changes, page 3 UWS Service Deployment Configuration File Changes, page 5 Feature Summary and Revision