Dell EMC Ready Solution for VMware vCloud NFV 3.1 ... · 5 Dell EMC Ready Solution for VMware...

Dell EMC Ready Solution for VMware vCloud NFV 3.1 OpenStack Edition Platform

Deployment Automation Architecture Guide for VMware NFV 3.1 with VMware Integrated OpenStack 5.1 with Kubernetes

Dell Engineering May 2019

2 Dell EMC Ready Solution for VMware vCloud NFV 3.1 OpenStack Edition Platform

Revisions

Date Description

May 2019 Initial release for Deployment Automation framework SW v3.1.1.1

The information in this publication is provided “as is.” Dell Inc. and its suppliers makes no representations or warranties of any kind with respect to the

information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any software that is described in this publication requires an applicable software license.

Copyright © 2019 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Big

Cloud Fabric (BCF) is the trademark or registered trademark of Big Switch Networks, Inc. Other trademarks may be the property of their respective

owners. Published in the USA.

Dell believes that the information in this document is accurate as of its publication date. The information is subject to change without notice.


Table of contents

Revisions............................................................................................................................................................................. 2

Overview ............................................................................................................................................................................. 5

1 Hardware support ......................................................................................................................................................... 6

1.1 Servers ............................................................................................................................................................... 6

1.1.1 Dell EMC PowerEdge R640 and R740 servers .................................................................................................. 6

1.1.2 Dell EMC PowerEdge R740xd servers .............................................................................................................. 6

1.2 iDRAC ................................................................................................................................................................. 6

2 Solution architecture ..................................................................................................................................................... 7

2.1 Architecture diagram .......................................................................................................................................... 7

2.2 Framework description ....................................................................................................................................... 8

2.2.1 User input file ...................................................................................................................................................... 8

2.2.2 Orchestrator ........................................................................................................................................................ 8

3 Logging and reporting .................................................................................................................................................. 9

4 Remediation ............................................................................................................................................................... 10

4.1 Workflows ......................................................................................................................................................... 10

4.1.1 Pre-deployment validation ................................................................................................................................ 11

4.1.2 ESXi installation and configuration ................................................................................................................... 11

4.1.3 vSAN pre-configuration .................................................................................................................................... 12

4.1.4 Auxiliary components workflow (AD, DNS, and NTP) ...................................................................................... 12

4.1.5 VCSA deployment and configuration ............................................................................................................... 12

4.1.6 vSAN post-configuration ................................................................................................................................... 13

4.1.7 VCSA HA configuration .................................................................................................................................... 13

4.1.8 NSX-T deployment and configuration .............................................................................................................. 14

4.1.9 vRLI deployment and configuration .................................................................................................................. 14

4.1.10 vRealize operations manager ...................................................................................................................... 15

4.1.11 VMware Integrated OpenStack Manager ..................................................................................................... 15

4.1.12 Kubernetes ................................................................................................................................................... 16

5 Solution bundle network, virtual network design, and topology ................................................................................. 17

5.1 Solution bundle physical network design and topology .................................................................................... 17

5.2 Solution bundle virtual network design and topology ....................................................................................... 19

6 Supported hardware and software versions ............................................................................................................... 21

6.1 Dell NFV hardware ........................................................................................................................................... 21


6.2 VMware stack ................................................................................................................................................... 21

6.3 Auxiliary components ....................................................................................................................................... 22

6.4 Pre-requisite software ....................................................................................................................................... 22

7 Deployment process ................................................................................................................................................... 23

A Reference Documents ................................................................................................................................................ 25


Overview

This Architecture document is a reference document that describes the design and creation of a Greenfield

Network Functions Virtualization (NFV) environment using VMware vCloud NFV OpenStack Edition 3.1 with

NSX-T and Dell EMC PowerEdge servers. The current edition of VMware vCloud NFV OpenStack uses:

• NFV Infrastructure (NFVI) with VMware Integrated OpenStack to create a network function Virtualized

Infrastructure Manager (VIM)

• VMware OpenStack, Open Application Programming Interface (API) with VMware vCloud NFVI to

create a platform support for Communication Service Providers (CSPs) which realizes the goal of

modernizing the network and transforming the business


1 Hardware support

1.1 Servers The following server solution support is used in this document:

• Dell EMC PowerEdge R640/R740 based on vSAN Ready Node

• Dell EMC PowerEdge R740xd based on vSAN Ready Node

1.1.1 Dell EMC PowerEdge R640 and R740 servers The Dell EMC PowerEdge R640 and R740 servers are hyper-dense, two-socket, 1U rack servers that are

ideal for cloud computing. With the Dell EMC PowerEdge R640 / R740 servers, you can create an NVMe

cache pool and use it for 2.5-inch or 3.5-inch drives for data storage.

1.1.2 Dell EMC PowerEdge R740xd servers The Dell EMC PowerEdge R740xd servers maintain a balance between storage scalability and performance.

The R740xd has a unique ability to combine any type of drive and create a best possible SSD or HDD

configuration to use either for performance, capacity, or both.

This configuration uses the following switches:

• Dell EMC Networking S4048T-ON with one switch used to serve as a Top of Rack (ToR).

• Dell EMC Networking Z9100-ON or S6010-ON unit with a pair of either Z9100-ON or S6010-ON

switches used to act as the Leaf switches.

1.2 iDRAC The integrated Dell Remote Access Controller (iDRAC) is an intelligence control unit that improves the overall

availability of Dell systems. It sends various alerts to System Administrators related to:

• System issues

• Remote system management

• Reduction in the requirement of physical access to the system

Note: Dell EMC recommends the use the iDRAC9 for remote server administration purpose.


2 Solution architecture

2.1 Architecture diagram The automation framework is categorized into following logical layers:

• Orchestrator: Orchestrator manages all the deployment checks and executes the deployment.

• Core Layer: This layer act as python libraries to implement the actual workflow tasks and subtasks

related to automation.

• Remote Communication Layer: This layer manages the connectivity between various hardware and

software used in this deployment.

Architecture diagram


2.2 Framework description

2.2.1 User input file In the USER_INPUT.xlsm file, user will provide the required input data for deployment. The input data is

logically categorized to avoid redundancy. Values for some parameters can be optional and will be defaulted

to standard values if not provided by user.

NOTE: For more information about filling and exporting the values in USER_INPUT.xlsm file, see the Dell

EMC Ready Solution for VMware vCloud NFV 3.1 OpenStack Edition Platform Deployment Automation User

Input Template.

2.2.2 Orchestrator Orchestrator is an end user interface used to trigger the automation deployment. Orchestrator manages the

entire deployment process and is responsible for following tasks:

• Input parameter validation check

• Trigger the workflows in designated order

• Inventory Manager

• Handle logging

• Handle Remediation

2.2.2.1 Inventory manager Inventory manager acts as a central data repository for all the input data required for the automation process.

The Inventory Manager also maintains the inter component dependencies and their location on the

management and resource/edge clusters.


3 Logging and reporting A centralized logger is available to log the information from different modules. The centralized logger has two

stream handlers to log information in file as well as on command line console.

To capture all the logs and high level logs at workflow level separately, two log files are created:

• main.log

• summary.log

A separate inventory.log file is created to capture the summary of deployed component details such as IP

address, FQDN, POD type on which it’s deployed etc.


4 Remediation The remediation feature provides the user the ability to manually remediate a workflow in case of any errors.

After manual remediation, the user may resume the automated deployment from next workflow.

As per the complexity of the workflows, a subset of workflows is included in the Remediation logic.

For additional information related to manual workflow configuration, see Supported Workflow within the

Supported Feature section in the Dell EMC Ready Solution for VMware vCloud NFV 3.1 OpenStack Edition

Platform Deployment Automation Software Guide.

4.1 Workflows Each software component that is part of NFVI, has one or more workflows that are associated with it. Each

workflow is responsible for performing tasks in a pre-determined order.

Each workflow and its tasks has their pre-running, running, and post-running functions to perform pre-

deployment checks, run actual task, and do post deployment verification respectively.

List of workflows in the logical order of execution:

List of workflows in the order of execution

Workflow Workflow Description

predeployment The pre-deployment workflow validates the setup before initializing the deployment

esxi The ESXI workflow installs ESXi server on all the available server nodes

preparevsan VSAN datastore is created to deploy auxiliary components and VCSA

auxservices AD, DNS, and NTP server is deployed and configured

managementvcsa On the management pod VCSA with embedded PSC is deployed and configured

mgmtvnetwork Virtual network is configured on management pod

mgmtvsan VSAN is configured on management pod

resourcevcsaw VCSA with embedded PSC is deployed and configured to manage the activity on edge and resource pod

resourcevnetwork Virtual network is configured to manage the edge and resource pod

resourcevsan VSAN is configured to manage the activity on edge and resource pod

vcsaha The VCSA components are configured for high availability

nsxtdeployment NSX-T manager, controllers, and edge nodes are deployed

nsxtconfiguration NSX-T controllers, and edge nodes are configured with NSX-T manager. This workflow also creates and configures the transport zone, host and edge transport nodes, and logical routers.


mgmtpodpostconfig Additional components, such as DRS, vSphere HA, affinity and anti-affinity are configured for management pod

respodpostconfig Additional component, such as DRS, vSphere HA, affinity and anti-affinity are configured for edge and resource pod

vrlivropsvio VRLI, VROPS, and VIO are deployed and configured

kubernetes Kubernetes clusters, and cloud providers are created

4.1.1 Pre-deployment validation The aim of this workflow is to validate the setup before initializing the deployment. This includes the validation

of software components in the software folder of deployment VM.

This workflow also validates the Dell EMC hardware and basic network connectivity. The hardware validation

is based on iDRAC.

List of tasks in their order of execution: Following would be the order of task execution for pre-deployment

validation:

1. Validation of switch connectivity

2. Files and Checksum validation

3. Connectivity to Big Switch Network Big Cloud Fabric (BCF)

Note: This is an additional check for BCF fabric type. For other fabric type it won’t fail the pre-deployment

validation.

4. iDRAC server validation

5. Capacity validation

4.1.2 ESXi installation and configuration VMware vSphere ESXi is a hypervisor software. ESXi is used to extract the physical x86 server resources

from the Virtual Network Functions (VNFs). In the virtual environment, each compute server is known as host.

These ESXi hosts are the fundamental compute building blocks of vCloud NFV.

The purpose of this workflow is to install ESXi server on all the available server nodes.

List of tasks in their order of execution:

• Create custom ESXi installation ISO for all servers

• Mount ESXI installation ISO on iDRAC

• iDRAC Restart

• Verify the IP and SSH connectivity of installed ESXi

• Create an appliance network as VM Management Network


4.1.3 vSAN pre-configuration VMware vSAN is a native vSphere storage component in the NFVI virtualization layer that provides a shared

storage pool between the hosts in a cluster.

The vSAN pre-configuration creates a temporary datastore and this datastore will be merged with vSAN disk

pool once the vSAN Post-Configuration is complete. The datastore will be required to deploy auxiliary

components, and VCSA.


• Create vSAN datastore on 1st ESXi by using all the disks in it

4.1.4 Auxiliary components workflow (AD, DNS, and NTP) The Auxiliary components are required to authorize users, resolve the domain name, and synchronize the

time. The following are the auxiliary components:

• AD: This is a Microsoft directory service used to authenticate and authorize all the users and

computers in NFV platform domain.

• DNS: This service translates the domain names to IP addresses. For internal-communication, all the

NFV platform components use the fully qualified domain names. DNS will internally translate these

FQDNs to their respective IP addresses.

• NTP server: This is a networking protocol used for clock synchronization between compute systems.

The NTP server will synchronize all the computers to within a few milliseconds of UTC. Time on all

the NFV platform components must be synchronized for proper working of the ecosystem.

Note: The AD DNS services are configured on Windows 2012 R2 server and NTP services are configured on

CentOS 7.4 VM.


• Install and configure Windows VM using OVA

• Install and configure CentOS VM using OVA

• Install and configure AD, DNS service

• Create reverse lookup domain zone for Mgmt Network, ESXi Mgmt Network and API Access

Network.

• Add ESXi host entries in DNS server

• Restart NTP service on all ESXi hosts

• Add DNS server on automation VM and sync automation VM with deployed NTP server

4.1.5 VCSA deployment and configuration VCSA is the centralized management interface to compute and store the resources in the NFVI. It provides an

inventory of allocated virtual to physical resources, manages inventory related information, and maintains an

overview of the virtual resource catalogs.


This workflow will deploy and configure VCSA with embedded PSC. The supplied ISO file will be mounted on

vSAN datastore created as a part of vSAN pre-configuration workflow.


• Add FQDN entries of VCSA in DNS server

• Mount the ISO to a local disk

• Deploy VCSA using Linux cli installer

• Unmount the ISO

• Verifying IP and FQDN of VCSA

• Join the VCSA domain with AD

4.1.6 vSAN post-configuration This workflow is responsible for vSAN configuration as well as virtual network configuration.

As part of this workflow the temporary datastore created in vSAN pre-configuration and this will be merged

into a single vSAN pool and the remaining hosts added into this pool. This workflow will be executed on both

management and edge/resource clusters.


• Add datacenter to vSAN pool

• Create cluster

• Enable EVC on the cluster

• Add ESXi hosts to cluster

• Create VDS, portgroups and assign uplinks

• vSwitch to VDS migration

• Create Disk groups on ESXi hosts

• Assign VSAN license

• Verify Disk groups

4.1.7 VCSA HA configuration This workflow is an extension of VCSA workflow. As part of this workflow VCSA HA configuration will be

accomplished. Three VCSA component; active, passive and witness for each HA setup will be deployed and

configured in this workflow.


• Connect to vCenter using PyVMomi API

• Assign second Network Adapter VCSA HA PortGroup to vCenter

• Create Active vCenter setup

• Create Passive vCenter setup

• Create Witness vCenter setup

• Deploy vCenter HA using pyvmomi

• Verify the vCenter HA cluster network


4.1.8 NSX-T deployment and configuration In the workflow, a NSX - T manager, three NSX-T controllers, and two edge nodes are deployed and

configured:

• NSX-T Manager: The NSX Manager acts as a management plane for the NSX-T system. The NSX

Manager creates, configures, and monitors NSX-T components, such as:

- Logical switches

- NSX Edge nodes

- Logical routers

The NSX-T Manager is deployed on the management pod as a single node to leverage the vSphere HA for

high availability. The NSX-Manager uses a common management network to communicate with the NSX-

Controller and its edge clusters.

• NSX-T Controller: The NSX-T controller is an advanced distributed state management system. The

NSX-T controller regulates the virtual networks and overlay transport tunnels.

Once the VRLI is deployed and configured then NSX will be integrated with it.


• Deployment of NSX-T components including Manager, Controllers, and Edge nodes

• Configuration of NSX-T controllers and edge nodes with NSX-T manager

• Host preparation

• Create and configure Transport zone

• Create and configure host and edge transport node

• Create and configure logical switches and logical routers

4.1.9 vRLI deployment and configuration vRLI ingests large amounts of syslog data from the physical and virtual NFVI components, to deliver real-time

monitoring, search, and log analytics. It automatically identifies structure from all types of machine generated

log data. vRLI will be deployed and configured in this workflow. Three instances of vRLI will be deployed in

the management cluster:

• One master node

• Two worker nodes

vRLI will be integrated with other management components, such as vCenter, vSAN, NSX-T, VIO, and

vROPS.


• Configure master node

• Configure worker nodes (2 worker nodes)

• Configure Log Insight integrated load balancer

• Integrate AD and vCenter with vRLI


• Install content packs for different solutions, for example, vSphere, NSX-T, vSAN

4.1.10 vRealize operations manager vROps delivers the intelligent operations management with full stack visibility across physical and virtual

infrastructures. Through the integrated performance and health monitoring functions, vROps:

• Improves system performance

• Avoids service disruption

• Helps the CSP to provide proactive management of the NFV infrastructure.

vROps will be deployed and configured in this workflow. This workflow will deploy the vROPs cluster which

contains master node, data node, and replica node.

vROps will be integrated with other management components such as vCenter, vSAN, NSX-T, VIO, and vRLI.


• Deploy vROps OVA

• Master node configuration

• Data node configuration

• Replica node configuration

• Integrate AD as authentication source

• Configure vCenter adapter instance

• Configure Log Insight adapter instance

• Install and configure adapter instance for NSX-T, VIO and vSAN with vROps

4.1.11 VMware Integrated OpenStack Manager The VMware Integrated OpenStack (VIO) Manager manages the VIO management plane components

deployed in the management pod. It is connected with the vCenter Server instance. It uses the VM template

to deploy the OpenStack Administrator then manage the operations of VIO management plane components

deployed in the management pod.

VIO is integrated with NSX-T and provides tenants with enhanced features and capabilities to manage VNF

network requirement using the Horizon interface and APIs. The tenants provide the NSX-T logical switches

with the east-west VNF component connection and the ability to deploy the NSX-T edge nodes for north-

south traffic. This is required when connecting other tenants to external networks.

VIO Manager will be deployed and configured in this workflow.

List of tasks in their order of execution for VIO Manager:

• Deploy OpenStack Manager using OVA

• Deploy OpenStack

• Create Project and User

• Create External and Internal Networks and their subnets.

• Create Router and add interface of internal network


• Assign floating IP Address from external network

• Create Security Group and create rules

4.1.12 Kubernetes The VIO for Kubernetes uses a common infrastructure management layer to deliver VMs and containers. It

builds a highly available Kubernetes clusters to support scalability and multi-tenancy. The HA Kubernetes

cluster consists of:

• Load-balanced master nodes

• Replicated API servers

• Clustered services

List of tasks in their order of execution for VIO Manager for Kubernetes:

• Deploy Kubernetes Manager OVA

• Create Cloud Provider

• Create Cluster


5 Solution bundle network, virtual network design, and

topology

5.1 Solution bundle physical network design and topology This section provides details about how the physical networks are connected with other network components.

ToR Switch - Top of Rack (S4048T-ON)

Leaf Switch - Z9100-ON or S6010-ON

Figure 2 shows the network topology used in this guide with deployment server:

• ToR switch using 10G interface for BCF (p-switch management network) – vmnic0

• ToR switch using 10G interface for the ESXI management network – vmnic1

• ToR switch using 10G interface for the OOB network – vmnic2

• ToR switch using 10G interface for the customer management private network – vmnic3 (stamp)

• In-band 1 using 10G interface – vmnic4




• Leaf1 switch using 10G/25G interface for physical switch network

• Leaf2 switch using 10G/25G interface for physical switch network

Network connectivity configuration table of Deployment Server

LOM/NDC ports NIC slot 1 NIC slot 2

Port number 1 2 3 4 1 2 1 2

VMware VMNIC port reference

vmnic0 vmnic1 vmnic2 vmnic3 vmnic4 vmnic5 vmnic6 vmnic7

Servers

R640/R740 10G 10G 10G 10G 10G 10G 10G 10G


Deployment server network connections

Figure 3 depicts the Dell EMC PowerEdge nodes network topology:

Note: Big Cloud Fabric (BCF) switch light OS is installed on the leaf switches.


Dell EMC PowerEdge nodes network topology

5.2 Solution bundle virtual network design and topology The vCloud NFV platform consist of two networks:

• Infrastructure network

• Virtual machine network

Infrastructure networks are host-level networks used to connect hypervisors with the physical networks. Each

ESXi host has multiple port groups configured on each infrastructure network.

The VMware vSphere Distributed Switch (VDS) is configured on the hosts in each pod. This provides a similar

network configuration across the multiple hosts. One VDS is used to manage infrastructure network and

another is used to manage VM networks. Additionally, N-VDS are used as a transport for telco workload

traffic.

The ESXi hypervisor uses the infrastructure network for Edge overlay, vMotion, and vSAN traffic. The VMs

use the VM network to communicate with each other. In this configuration, two distribution switches, one

switch for infrastructure network and other for VM network, are used to create a separation.

Each distribution switch has a separate uplink connection for physical data center network that separates

uplink traffic from other network traffic. The uplinks are mapped with a pair of physical NICs on each ESXi

host for best performance and resiliency.


NSX-T creates the VLAN-backed logical switches that allow VNF components and VMs to run on the top of it.

On the ESXi hosts, physical NICs act as uplinks to connect the host virtual switches to the physical switch

(ToR).

The following infrastructure networks are used in the pods:

• ESXi management network – network for ESXi host management traffic

• Edge overlay – network for edge overlay Tunnel End Point connectivity

• vMotion network – network for VMware vSphere vMotion traffic

• vSAN network – network for vSAN shared storage traffic

Management pod networking consists of the infrastructure and VM networks previously described. The edge

and resource pod virtual network depends on the network topology required by the VNF workloads. In

general, the edge and resource pod has the infrastructure networks, networks for management, control plane

connectivity, and networks for the workloads.

Solution bundle virtual network design and topology

Note: The minimum infrastructure requirements for VDS, ESXi, and vSAN vMotion, can be combined for

2x10GbE or 2x25GbE.


6 Supported hardware and software versions

6.1 Dell NFV hardware Hardware Details for nodes: The server BIOS and firmware versions that are tested for the Dell EMC Ready

Bundle for NFV platform are as follows:

Dell EMC PowerEdge R640/R740 and R740xd tested BIOS and firmware versions

Product Firmware version

BIOS 1.4.9

iDRAC with Lifecycle Controller 3.32.32.32

rNDC - Intel® 4P X550-t - 10 Gbps 18.5.18

PCIe - Intel® 25 GbE 2P XXV710 18.5.17

(Optional) PCIe - Intel® 10 GbE 2P X710 18.5.17

(Optional) PCIe - QLogic 25GE 2P QL41262 14.07.07

HBA330 ADP/Mini storage Controller (Dell EMC PowerEdge R740xd/R640)

15.17.09.06

Backplane/Storage Enclosures (Dell EMC PowerEdge R640/R740)

4.26

Backplane/Storage Enclosures (Dell EMC PowerEdge R740xd) 2.25

The firmware switch versions that are tested for the Dell EMC Ready Bundle for NFV platform are as follows:

Dell Networking tested BIOS and firmware versions

Product Instance (count) Version

S4048T-ON firmware out of band management 1 Dell OS 9.14

Z9100-ON or S6010-ON firmware leaf-switch 2 SWL-OS-BCF-4.7.0(0)

6.2 VMware stack VMware vCloud NFV product inventory list

Product Version

ESXi 6.7U1

VMware vCenter Server 6.7U1

VMware NSX –T 2.3

VMware vSAN 6.7U1


VMware vRealize Log Insight 4.7

VMware vRealize Operations Manager 7.0

VIO with Kubernetes 5.1

6.3 Auxiliary components Below services must be enabled and configured on Windows Server 2012 R2.

• Domain Name Server (DNS)

• Active Directory (AD-DS)

Below services must be enabled and configured on CentOS7.4

• NTP

6.4 Pre-requisite software • CentOS 7.6

• Python 2.7.13


7 Deployment process Orchestrator consumes the USER_INPUT.xlsm file as an input and generates the yaml file. As a part of input

parameter validation check, orchestrator verifies the user input against expected input. All the input

parameters will be validated at once and errors will be displayed to user if any. Then, pre-deployment

validation workflow will be initialized to check the hardware connectivity status and perform other pre-

deployment checks.

Once the pre-deployment validation is successful, it will execute the Dell EMC NFVI stack deployment

workflow as per the defined order. While executing the workflows if any error or exception occurs,

orchestrator will terminate the execution with appropriate exception message.

Follow the below steps to run the deployment:

1. Open the USER_INPUT.xlsm file.

2. Fill all the required values, and if required, update optional values.

Note: If you don’t want to provide any value to optional keys, fill the corresponding value fields as “NULL”.

3. On the ExportSettings tab, click Export Data button.

A new CSV file named "exported_name_value.csv" will be created in the same directory.

4. Copy the exported_name_value.csv file to /Test/vCloud-Nfv-3.1/src/orchestration in

the deployment VM.

5. Provide the exported_name_value.csv file path while executing the Orchastrator.py as specified in

following example:

a. Case - I: To execute complete deployment, run the following command:

Python orchestrator.py --csvInput "/Test/vCloud-Nfv-

3.1/src/orchestration/exported_name_value.csv"

b. Case - II: To skip workflows: The following command will skip the workflows till the workflow

specified in the command:

Python orchestrator.py –- --csvInput "/Test/vCloud-Nfv-

3.1/src/orchestration/exported_name_value.csv" --skipWorkflowsTill

vrlivropsvio

As specified in above example, orchestrator will skip the workflow till vrlivropsvio workflow and start

the deployment from next workflow i.e., kubernetes.

c. Case III - To clean-up: A clean-up script is used and required to override the previous failed

setup/deployment and restart the deployment from the bare metal. To execute the clean-up

script, run the following command:

python orchestrator_cleanup.py –-csvInput "/Test/vCloud-Nfv-

3.1/src/orchestration/exported_name_value.csv"


Note: The paths provided in above steps are only for reference purposes. If you are copying the

exported_name_value.csv file anywhere else in the deployment VM, then make sure that you are providing

the correct path while executing the commands in orchestrator.

Note: For more information about filling and exporting the values in USER_INPUT.xlsm file, see the Dell EMC

Ready Solution for VMware NFV Platform Deployment Automation User Input Template File 3.1.


A Reference Documents

See the following documentation for more information:

Dell EMC Ready Solution for VMware vCloud NFV 3.1 OpenStack Edition Platform –Deployment Automation

Hardware Guide


Operations Guide


Software Guide


User Input Template File 3.1

VMware vCloud NFV OpenStack Edition Reference Architecture for VMware vCloud NFV OpenStack Edition

3.1

VMware vCloud NFV Documentation

Dell PowerEdge R640 Owner's Manual

Dell PowerEdge R740 Owner’s Manual

Dell PowerEdge R740xd Owner's Manual

https://docs.vmware.com/en/VMware-vCloud-NFV-OpenStack-Edition/3.1/vmware-vcloud-nfv-openstack-edition-ra31.pdf

https://docs.vmware.com/en/VMware-vCloud-NFV-OpenStack-Edition/3.1/vmware-vcloud-nfv-openstack-edition-ra31.pdf

https://www.vmware.com/support/pubs/vmware-vcloud-nfv-pubs.html

http://www.dell.com/support/home/us/en/04/product-support/product/poweredge-r640/manuals

https://www.dell.com/support/home/in/en/indhs1/product-support/product/poweredge-r740/manuals

http://www.dell.com/support/home/us/en/04/product-support/product/poweredge-r740xd/manuals

Dell EMC Ready Solution for VMware vCloud NFV 3.1 ... · 5 Dell EMC Ready Solution for VMware...

Documents

Transcript of Dell EMC Ready Solution for VMware vCloud NFV 3.1 ... · 5 Dell EMC Ready Solution for VMware...