NFVI Deployment Automation

Transcription

1 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 History Summary Data Applicable Product(s) or Functional Area Ultra M Solution Applicable Platform(s) Ultra Gateway Platform Feature Default Enabled Configuration Required Related Changes in This Release Not Applicable Related Documentation USP Deployment Automation Guide Ultra M Solution Guide Ultra Web Service User Guide Revision History Revision Details Release First Introduced. N5.5 1

2 Feature Description Feature Description In this release, UAS supports the ability to automate the deployment of the network function virtualization infrastructure (NFVI) Undercloud in Hyper-Converged Ultra M Solution deployments. This is accomplished through a new UAS software module, AutoIT-NFVI. Important This is an optional workflow. Manual installation of the Undercloud can still be performed. Ultra M s NFVI and virtual infrastructure manager (VIM) is based on the OpenStack project TripleO ( OpenStack-On-OpenStack") which is the core of the OpenStack Platform Director (OSP-D). The Undercloud is the TripleO cloud concept through which the computes, controller, and storage nodes leveraged by the VNF are deployed and managed. Collectively, these form a second TripleO cloud concept called the Overcloud. Deploying the Undercloud through AutoIT-NFVI involves installing an Ubuntu-based image on the server node hardware that will serve as the OSP-D server. Upon boot, this image intiates all of the AutoIT-NFVI processes. AutoDeploy works with AutoIT-NFVI to automate the deployment of a RedHat Enterprise Linux (RHEL)-based VM running the OpenStack Platform Director (OSP-D). Parameters and constructs within a VIM orchestrator configuration file loaded through AutoDeploy facilitated the automated deployment. Once deployed, this VM serves as the OSP-D Server within the Ultra M solution. Important In order to leverage this functionality, the AutoDeploy VM must be installed on a server on the same server that hosts AutoIT-NFVI and the OSP-D Server VM. Figure 1: AutoIT-NFVI Workflow for Deploying the Hyper-Converged Ultra M solution Undercloud on a UCS-C Server 2

3 AutoIT-NFVI AutoIT-NFVI AutoIT-NFVI is the UAS software module used to automate the process of installing the virtual infrastructure manager (VIM) which manages the network function virtualization infrastructure (NFVI). AutoIT-NFVI performs the installation based on manifests it receives from AutoDeploy. It provides the following functions: Sets up AutoIT-NFVI nodes API endpoint based on ConfD to Auto-Deploy and NSO. Important In this release, AutoIT-NFVI supports only the installation of the Undercloud (VIM orchestrator) and is only supported for use with Ultra M solutions based on the Hyper-Converged architecture. 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 AutoDeploy Configuration File Changes Deploying the Undercloud through AutoIT-NFVI involves installing a an Ubuntu-based image on the server node hardware that will serve as the OSP-D server. Once this image is installed, AutoDeploy is used to automate the deployment of a RedHat Enterprise Linux (RHEL)-based VM running the OpenStack Platform Director (OSP-D). 3

4 AutoDeploy Configuration File Changes Parameters and constructs within the AutoDeploy configuration file facilitated the automated deployment. The following constructs and parameters have been added in support of this feature: 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 nfvi-admin secure-token cimc-login user user1 secure-token subscription user ultra-m-install ## NFVI-POP Descriptor ## nfvi-popd <nfvi_pop_name> nfvi-node <nfvi-node-id> description <nfvi_pop_description> physical-network-interface [ <interface_mac_address> ] physical-server-manager ip-address <ip_address> physical-server-manager login-credential cimc-login ## VIM-ORCH Descriptor Information ## vim-orchd <vim_orchestrator_name> hostname <server_hostname> domain-name <domain> dns [ <DNS_address> ] login-credential autoit-nfvi-ospd ## SATELLITE-SERVER-CONFIG ## ## This would change based on the customer ## 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 ## CDN SERVER CONFIG ## ## cdn-server login-credential subscription cdn-server proxy proxy-wsa.esl.cisco.com:80 cdn-server pool-id 8a85f a01578b1e1cbd2275 external-network ip-address <external_interface_address> external-network netmask <external_interface_mask> provisioning-network ip-address <provisioning_interface_address> provisioning-network netmask <provisioning_interface_mask> nfvi-node autoit-nfvi-physical-node 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 ## Site Specific Config ## sited <site_name> auto-it-nfvi scm-admin autovnf-oper auto-it-nfvi scm-oper autovnf-oper 4

5 UWS Service Deployment Configuration File Changes auto-it-nfvi ip-address <autoit_nfvi_address> auto-it-nfvi authentication-info autoit-nfvi-login nfvi-pop uws-<nfvi_pop_name> vim-orch <vim_orchestrator_name> service-deployment <svc_dep_name> description <site_description> sited <site_name> site-ref <site_ref> UWS Service Deployment Configuration File Changes Deploying the Undercloud through AutoIT-NFVI involves installing a an Ubuntu-based image on the server node hardware that will serve as the OSP-D server. Once this image is installed, the Ultra Web Service (UWS) can be used to automate the deployment of a RedHat Enterprise Linux (RHEL)-based VM running the OpenStack Platform Director (OSP-D). Parameters and constructs within the UWS service deployment configuration file facilitated the automated deployment. The following constructs and parameters have been added in support of this feature: <?xml version="1.0" encoding="utf-8"?> <config xmlns=" <secure-id>autovnf-admin</secure-id> <user>$8$n+chv+ijusp3bldvedmikoeqddlmh0qy00p9vw2ri1a=</user> <secure-token xmlns=" annotation=" ## Tokens for AutoIT-NFVI and VIM-ORCHD ## "> <secure-id>autonfvi-admin-netconf</secure-id> <user>$8$ebxbxw3oomab2yrl7k2ncaawijtaqoa8fomxasohs34=</user> <secure-id>autonfvi-oper-netconf</secure-id> <user>$8$rva6dbz5djgbbwihnssm6c1xrswgdjwsaskugf/4two=</user> <secure-id>autoit-nfvi-ospd</secure-id> <user>$8$akvbhpk4sv5n45csyzmqz81ejwn3aq6c1sy+5gbklyk=</user> <secure-id>autoit-nfvi-login</secure-id> <user>$8$eq8guma9grdvx0w89bwj4am+ieeahoafiq5h+zjnre8=</user> <secure-id>cimc-login</secure-id> <user>$8$vmbzbv3cagae/rirzemh7zwyiwqcbsf+h7eov4ezkza=</user> <nfvi-popd xmlns=" annotation="## NFVI-POP Descriptor ## "> <name>nfvi_pop_name</name> <nfvi-node> <nfvi-node-id>nfvi-node-id</nfvi-node-id> <description>nfvi_pop_description</description> <physical-network-interface>interface_mac_address</physical-network-interface> <physical-server-manager> <ip-address>ip_address</ip-address> <login-credential>cimc-login</login-credential> </physical-server-manager> 5

6 UWS Service Deployment Configuration File Changes </nfvi-node> </nfvi-popd> <vim-orchd xmlns=" annotation="## VIM-ORCH Descriptor Information ## "> <name>vim_orchestrator_name</name> <hostname>server_hostname</hostname> <domain-name>domain</domain-name> <dns>dns_address</dns> <login-credential>autoit-nfvi-ospd</login-credential> <cdn-server> <login-credential>subscription</login-credential> <proxy>proxy-wsa.esl.cisco.com:80</proxy> <pool-id>8a85f a01578b1e1cbd2275</pool-id> </cdn-server> <satellite-server> <ip-address annotation=" ## SATELLITE-SERVER-CONFIG ## ## This would change based on the customer ## ">sat_server_address</ip-address> <hostname>sat_server_hostname</hostname> <domain-name>sat_server_domain</domain-name> <organization>org_name</organization> <activation-key>act_key</activation-key> <pool-id>pool_id</pool-id> </satellite-server> <external-network> <ip-address>external_interface_address</ip-address> <netmask>external_interface_mask</netmask> </external-network> <provisioning-network> <ip-address>provisioning_interface_address</ip-address> <netmask>provisioning_interface_mask</netmask> </provisioning-network> <flavor> <vcpus>4</vcpus> <ram>16384</ram> <root-disk>100</root-disk> <ephemeral-disk>0</ephemeral-disk> <swap-disk>0</swap-disk> </flavor> <nfvi-node>autoit-nfvi-physical-node</nfvi-node> <image>/home/ubuntu/rhel-server-7.3-x86_64-dvd.iso</image> </vim-orchd> <sited xmlns=" annotation="## Site Specific Config ## "> <sited-id>auto-test-sjc</sited-id> <auto-it-nfvi> <scm-admin>autovnf-oper</scm-admin> <scm-oper>autovnf-oper</scm-oper> <ip-address>autoit_nfvi_address</ip-address> <authentication-info>autoit-nfvi-login</authentication-info> </auto-it-nfvi> <nfvi-pop>nfvi_pop_name</nfvi-pop> <vim-orch>vim_orchestrator_name</vim-orch> </sited> <service-deployment xmlns=" annotation="## Service Deployment Config ## "> <service-deployment-id>svc_dep_name</service-deployment-id> <description>site_description</description> <sited> <sited-id>site_name</sited-id> <site-ref>site_ref</site-ref> </sited> </service-deployment> </config> 6