Dell Active Fabric Manager OpenStack Guide

Active Fabric Manager (AFM) Plug-in for OpenStack Guide 2.0

Notes, Cautions, and Warnings

NOTE: A NOTE indicates important information that helps you make better use of your computer.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

Trademarks used in this text: PowerConnect of Dell Inc.

AMD Devices, Inc. either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat

™

OpenManage

Intel

Pentium

is a registered trademark and

Microsoft

Enterprise Linux

are registered trademarks of Novell Inc. in the United States and other countries. Corporation and/or its affiliates.

™

Dell

, the Dell logo,

™

EqualLogic

Xeon

Core

AMD Opteron

Windows

are registered trademarks of Red Hat, Inc. in the United States and/or other countries.

Windows Server

Citrix

Xen

and

Dell Boomi

™

Compellent

Celeron

™

XenServer Systems, Inc. in the United States and/or other countries. trademarks or trademarks of VMware, Inc. in the United States or other countries.

™

Dell Precision

™

KACE

are registered trademarks of Intel Corporation in the U.S. and other countries.

AMD Phenom

Internet Explorer

and

VMware

™

XenMotion

™

and

vMotion

FlexAddress

AMD Sempron

MS-DOS

are either registered trademarks or trademarks of Citrix

vCenter

™

OptiPlex

™

Force10

™

Windows Vista

is a registered trademark of Oracle

Oracle

vCenter SRM

is a registered trademark of International

IBM

™

Latitude

are trademarks of Advanced Micro

™

Venue

PowerEdge

™

and

Active Directory

and

™

and

vSphere

Business Machines Corporation.

2013 - 12

Rev. A0X

™

Vostro

Red Hat

Novell

PowerVault

™

are trademarks

are

and

SUSE

are registered

™

Contents

1 AFM Plug-in Overview ...............................................................................................................5

OpenStack Networking Deployment Use Cases...................................................................................................... 6

Supported Deployment Topologies.......................................................................................................................... 7

Pre-requisites for Using the Plug-In......................................................................................................................... 7

Key Considerations...................................................................................................................................................8

Using the AFM Plug-in for OpenStack......................................................................................................................8

2 Step 1: Installing the AFM Plug-in............................................................................................ 9

3 Step 2: Configuring the AFM Plug-in......................................................................................11

4 Step 3: (Optional) Configuring Static Switch Server Connectivity....................................13

5 Step 4: Installing the LLDP and Port Bonding ......................................................................15

Step 4.1: Installing the LLDP Package ................................................................................................................... 15

Step 4.2: Install and Configure Port Bonding ......................................................................................................... 15

6 Step 5: Installing the Dell OVS Agent.....................................................................................19

7 Step 6: Configuring the Dell OVS Agent.................................................................................21

Step 1: Creating the Physical and Integration bridge.............................................................................................21

Step 2: Configuring the Dell OVS Plug-in................................................................................................................ 21

Step 3: Configuring the Rootwrap ..........................................................................................................................22

Step 4: Restart the Dell OVS Agent on Nova Compute Node or Network Node.....................................................23

Step 5: Configure the Nova Compute Node or Network Node .............................................................................. 23

8 Step 7: Connecting to the AFM Server.................................................................................. 25

Step 1: Configure the AFM server IP address and Port..........................................................................................25

Step 2: Configure the AFM User Credentials for the AFM Plug-in..........................................................................25

9 Uninstalling the AFM Plug-in for OpenStack........................................................................27

10 Uninstalling the Dell OVS Agent........................................................................................... 29

AFM Plug-in Overview

Use the Active Fabric Manager (AFM) plug-in for OpenStack to configure VLAN interfaces on the Dell Force10 Network switches to orchestrate virtual networks through the AFM Restful APIs. The AFM plug-in enables you to configure VLANs for a Layer 2 fabric, which is created by AFM administrators. It delegates the physical network configuration logic to the AFM server by making requests to the AFM server through AFM Restful APIs. Upon receiving requests from the OpenStack server restful API, the Dell Open vSwitch (OVS) agent and AFM plug-in create and maintain the logical port infrastructure for the administrator to tag and untag VLANs.

There are 3 components to managing the physical, virtual networks, and bridges. The first component, AFM, manages the physical network. The second and third components, the Dell OVS agent and AFM Plug-in for OpenStack, manages the virtual networks and bridges. The AFM Plug-in runs on the controller. The Dell OVS agent runs on a Nova compute and network node.

The AFM plug-in does the following:

• Plugs into the standard OpenStack Pluggable Networking Architecture.

• Allows the OpenStack Neutron server to communicate with AFM server.

• Integrates with the DELL AFM (Active Fabric Manager) through Restful APIs

• Provides dynamic VLAN configuration to fulfill OpenStack Cloud services Networking requirements.

• Provides dynamic discovery of Switch-Server connections through LLDP.

• Integrates with the AFM Layer 2 VLT topology to achieve switch-server connection redundancy using ‘Port Bonding’.

OpenStack Networking Deployment Use Cases

The AFM plug-in supports the following OpenStack use cases:

1. Single Flat Network — All VMs can talk to each other via the shared network and to external network through the physical route. In the simplest use case, a single OpenStack Networking network exists. This is a "shared" network, meaning it is visible to all tenants through the OpenStack Networking API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network.

2. Multiple Flat Network — VMs share the same shared network and can talk to each other and to VMs in other shared networks and to external networks through the physical router. This use case is very similar to the above Single Flat Network use case, except that tenants see multiple shared networks via the OpenStack Networking API and can choose which network (or networks) to plug into.

3. Mixed Flat and Private Network —All VMs can talk to each other through the shared network and to external networks through the physical router. VMs in a Tenant-Private Network can talk to each other but not to other Tenant-Private Networks or external. This use case is an extension of the above flat network use cases in which tenants also optionally have access to private per-tenant networks. In addition to seeing one or more shared networks via the OpenStack Networking API, tenants can create additional networks that are only visible to users of that tenant. When creating VMs, those VMs can have NICs on any of the shared networks and/or any of the private networks belonging to the tenant. This enables the creation of "multi-tier" topologies using VMs with multiple NICs. It also supports a model where a VM acting as a gateway can provide services such as routing, NAT, or load balancing.

Supported Deployment Topologies

The AFM Plug-in supports the following topologies: Six S4810 switches with two aggregation nodes and four access nodes.

The AFM Plugin is installed on the OpenStack Controller Node. The Dell OVS Agent is installed on each Nova Compute node and Network node. At runtime, the OpenStack Neutron Server communicates with the AFM Server through a restful API to manage the physical topology.

Pre-requisites for Using the Plug-In

Before you use the AFM plug-in for OpenStack:

• Install and configure OpenStack software, Ubuntu 12.0.4 (LTS). For information about this topic, see http://

docs.openstack.org/grizzly/basic-install/apt/content/

A typical deployment scenario is one controller node, one network node, and a series of nova compute nodes. The OpenStack Neutron server is installed on the controller node. After the installation, make sure all the services are started on all the nodes and the VMs can be launched before you apply the AFM plug-in for OpenStack.

• Ensure that the DNS is enabled in the OpenStack Neutron server.

• Ensure that the AFM administrator has created a fabric with the Openstack Neutron Managed option enabled at the

Fabric Name and Type screen using the AFM Design Wizard and has deployed a complete fabric that is ready for service.

Key Considerations

When using the AFM plug-in consider the following:

• The AFM Plug-in for OpenStack resides on the OpenStack Neutron server.

• The AFM plug-in supports VLANs.

• The AFM plug-in is supported with fabrics that have 10 Gb Access switches.

Using the AFM Plug-in for OpenStack

To use the AFM plug-in for OpenStack:

1. Install the AFM software and start it.

2. Deploy the physical fabric network using the AFM.

3. Install OpenStack.

4. Install and configure the AFM plug-in for OpenStack onto the OpenStack Controller node.

5. Install the LLDP package (for dynamic discovery of server switch connectivity) and Port Bonding in the compute and network node.

6. Install and configure the Dell OVS Agent in the compute and network node.

7. Configure the OpenStack Neutron server and the AFM plug-in.

8. Use the OpenStack GUI to create network and VM instances..

Step 1: Installing the AFM Plug-in

To install the AFM plug-in for Openstack onto the Controller node where the Neutron server is located:

1. Obtain the AFM Plug-in for Openstack tar file, AFMOpenStackPlugin2.0.0.0.tar.gz from iSupport. See the Release Notes.

2. On the Openstack server, go to the /usr/lib/python2.7/dist-packages/ directory.

3. Untar the AFMOpenStackPlugin2.0.0.0.tar.gz. file using the following syntax:

tar –zxvf AFMOpenStackPlugin2.0.0.0.tar.gz

After you untar this file, the AFM plug-in is located at the /usr/lib/python2.7/dist-packages/quantum/plugins/ directory.

4. Make a backup copy of the quantum-server.conf file. The file is located at the /etc/init/ directory.

5. Add the --config-file /etc/quantum/plugins/dell/dell_quantum_plugins.ini \ statement in the quantum-server.conf file as shown below.

exec start-stop-daemon --start --chuid quantum --exec /usr/bin/quantum-server -- \

--config-file /etc/quantum/quantum.conf \

--config-file /etc/quantum/plugins/dell/quantum-server.conf \

--log-file /var/log/quantum/server.log $CONF_ARG

6. Make a backup copy of the quantum.conf file. This file is located in the /etc/quantum/ directory.

7. Navigate to the /etc/quantum/ directory and modify the quantum.conf file with the following content:

core_plugin = quantum.plugins.dell.network_plugin.PluginV2

8. In the /etc/quantum/plugins/dell directory, create the dell_quantum_plugins.ini file with the following content. The default is to use dynamic port mapping (LLDP) and the parameter static_config is set false. In this file, also, add the network_node_hostname with the network node hostname. For example, network_node_hostname=dev1openstack01

[DELL_PLUGINS]

#vswitch_plugin = quantum.plugins.openvs

afm_plugin = quantum.plugins.dell.afm.afm_plugin_v2.AFMPlugin

vswitch_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2

[DELL]

#model_class=quantum.plugins.dell.models.virt_phy_sw_v2.VirtualPhysicalSwitchModelV2

#static_config=False

network_node_hostname=dev1-openstack01

NOTE: We recommend that you use dynamic port mapping.

9. (Optional) If you want to use static mapping set the static_config= True and then add the port mapping entries using the PORT_MAPPING syntax. .

The following example shows how to add port mapping entries.

+ 20 hidden pages