The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Step 1 | Launch the RHEL-OSP Installer graphical user interface (GUI). | ||||||||||||||||||||||
Step 2 | From the Red Hat Enterprise Linux OpenStack Platform Installer window, choose OpenStack Installer > Deployments. | ||||||||||||||||||||||
Step 3 | From the OpenStack Deployments window, click an existing deployment. Alternatively, you can create a new deployment. For information on creating a new deployment, see Creating a New OpenStack Deployment. | ||||||||||||||||||||||
Step 4 | From the Red Hat Enterprise Linux OpenStack Platform Installer window, choose Configure > Puppet Classes. | ||||||||||||||||||||||
Step 5 | In the Search field, enter n1kv_vsm. | ||||||||||||||||||||||
Step 6 | Click the n1k_vsm class name. The Edit Puppet Class pane opens. | ||||||||||||||||||||||
Step 7 | In the Puppet Class tab, in the Host Group field, choose base_RedHat/<Deployment name>/Generic RHEL7. | ||||||||||||||||||||||
Step 8 | Click the Smart Class Parameter tab. | ||||||||||||||||||||||
Step 9 | In the
Smart
Class Parameter pane, click the required parameters. See table
below.
| ||||||||||||||||||||||
Step 10 | For each
parameter, check the
Override checkbox and configure the appropriate
default value.
| ||||||||||||||||||||||
Step 11 | Click Submit. |
Installing a VSM as a VM on a Physical Server
The Virtual Supervisor Module (VSM) can be installed in stand-alone or high-availability (HA) mode. Although we highly recommend high availability mode, it is not mandatory. This procedure covers installation for both stand-alone and HA modes.
If you are installing VSMs in HA mode, deploy the first VSM (including setting up the initial configuration), then repeat step 4 to create the second VSM and proceed with setting up the initial configuration. See Setting Up the Initial Configuration of the VSM.
Make sure that you have RHEL7 physical servers for VSM active and standby hosts, as recommended. (See Topology with OpenStack in Standalone Mode and Topology with OpenStack in High-Availability Mode.)
Make sure that the Cisco Yum repository has been set up correctly. For information, see Setting Up the Cisco Yum Repository.
Make sure the servers in the provisioning network have connectivity to the RHEL7 physical sever where the VSM is installed as a VM.
Proceed to Setting Up the Initial Configuration of the VSM.
Before you can use your VSM, you must configure some initial information on it. You can accept most of the default configuration. However, you must configure some required parameters.
Step 1 | Log in to the VSM. |
Step 2 | Create a
default port profile named default-pp by entering the following commands:
configure terminal port-profile type vethernet default-pp no shutdown state enabled publish port-profile copy running-config startup-config |
Step 3 | Create a port
profile named uplink by entering the following commands:
configure terminal port-profile type ethernet uplink switchport mode trunk switchport trunk allowed starting_vlan-ending_vlan no shutdown state enabled publish port-profile copy running-config startup-config |
Step 4 | Define the VLAN
range to be used:
configure terminal vlan starting_vlan-ending_vlan copy running-config startup-config |
Installing a VSM on a Cloud Services Platform
If you choose to install a Virtual Supervisor Module (VSM) on the Cisco Nexus Cloud Services Platform, you must install all primary and secondary VSMs on the Cisco Nexus Cloud Services Platform. You cannot install any other VSMs as a VM.
Copy the VSM ISO or OVA file to the bootflash:repository/ of the Cisco Nexus Cloud Services Platform.
Step 1 | Create a
virtual service blade.
switch(config)# show virtual-service-blade summary --------------------------------------------------------------------------------- Name HA-Role HA-Status Status Location --------------------------------------------------------------------------------- switch(config)# virtual-service-blade vsm-1 switch(config-vsb-config)# virtual-service-blade-type new nexus-1000v-dk9.5.2.1.SK3.1.2.iso switch(config-vsb-config)# show virtual-service-blade summary -------------------------------------------------------------------------------------- Name HA-Role HA-Status Status Location -------------------------------------------------------------------------------------- vsm-1 PRIMARY NONE VSB NOT PRESENT PRIMARY vsm-1 SECONDARY NONE VSB NOT PRESENT SECONDARY switch(config-vsb-config)# |
Step 2 | Configure the
control, packet, and management interface VLANs for static and flexible
topologies.
switch(config-vsb-config)# interface management vlan 100 switch(config-vsb-config)# interface control vlan 101 switch(config-vsb-config)# interface packet vlan 101 |
Step 3 | Configure two
vCPUs and the size of the RAM to 4 GB for the VSM.
switch(config-vsb-config)# ramsize 4096 switch(config-vsb-config)# numcpu 2 If desired, you can verify these settings with the following command: switch(config-vsb-config)# show virtual-service-blade name vsm-1 |
Step 4 | Configure the
Cisco Nexus 1000V for KVM on the
Cisco Nexus Cloud Services
Platform.
switch(config-vsb-config)# enable Enter vsb image: [nexus-1000v.4.2.1.SV2.2.1.iso] Enter domain id[1-1023]: 127 Management IP version [V4/V6]: [V4] Enter Management IP address: 192.0.2.79 Enter Management subnet mask: 255.255.255.0 IPv4 address of the default gateway: 192.0.2.1 Enter HostName: n1000v Enter the password for ‘admin’: password Note: VSB installation is in progress, please use show virtual-service-blade commands to check the installation status. switch(config-vsb-config)# |
Step 5 | Display the
primary and secondary VSM status.
switch(config-vsb-config)# show virtual-service-blade summary -------------------------------------------------------------------------------------- Name HA-Role HA-Status Status Location -------------------------------------------------------------------------------------- vsm-1 PRIMARY NONE VSB POWER ON IN PROGRESS PRIMARY vsm-1 SECONDARY ACTIVE VSB POWERED ON SECONDARY |
Step 6 | Log in to the
VSM.
switch(config)# virtual-service-blade vsm-1 switch(config-vsb-config)# login virtual-service-blade vsm-1 Telnet escape character is ‘^\’. Trying 192.0.2.18... Connected to 192.0.2.18. Escape character is ‘^\’. Nexus 1000v Switch n1000v login: admin Password: Cisco Nexus operating System (NX-OS) Software TAC support: http://www/cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php switch# |
Step 7 | Enable the following features in the VSM to ensure that OpenStack can configure the networks appropriately: |
Collect the information required for the site.pp file, as described in VSM-Related Configuration.
Create the build server, as described in Creating the Build Server.
The neutron plugin retrieves the policy profile information from all available VSMs. The policy profile reconciliation displays profiles that are common to all available VSMs. You must ensure that the policy profile table supports more than one VSM.
The N1KV plugin dispatches the network creation and port creation requests to all available VSMs.
The VM creation can be localized by creating host aggregates, where each aggregate is mapped to one VSM.
Step 1 | Configure the IP addresses of the VSMs in the Neutron service.
|
Step 2 | Configure the VEM puppet class to support multiple VSMs.
|