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.
The information provided in this section is generic to OpenStack and it is provided here for your convenience with the exception of ConfigProfile, which is Cisco Nexus fabric specific.
Follow these steps to create a project:
Login to the Horizon dashboard as an administrator. Use the password that you used in the OpenStack configuration file.
Click Projects and then Create Project.
Enter relevant project information and click Create Project to create the project.
Note | The project name is used as vrfName in the fabric (vrfName = “project_name:CTX”) for fabric auto-configuration. The fabric limits the size of the vrfName string to 32 characters. Ensure that the project name length is less than 29 characters when creating the project. Do not use hyphens in the project name. |
You can use OpenStack to configure the DC Inter-connect function. Support is only provided for Layer-3 DCI with the Cisco Prime DCNM 7.1(1) release, and Cisco NX-OS 7.1(0)N1(1) release or later.
As part of the project name string, type xyx:dci_id:129 to enable DCI support ('129' is used here as an example). Type xyz or xyz:dci_id:0 to remove DCI support for this project.
The integer 129 is the DCI ID. Cisco Prime DCNM uses it as an indication that the user desires to auto-configure the border leaf switches with this VRF, and extend to the DCI edge devices(s). If the value is 0, Cisco Prime DCNM removes VRF configurations from the border leaf switches and the configurations that extend the VRF from the border leaf switch to the DC edge device(s).
Follow these steps to create a user for the project:
Follow these steps to create the network:
Login as a user using login credentials created by the administrator.
Click the Project tab.
Click Networks and then click Create Network. Specify a Name for the network and go to the subnet tab. This is mandatory.
Specify a Network Address for the subnet.
By default, for Cisco Prime DCNM with version 7.1, defaultNetworkUniversalEfProfile is the network profile used automatically by the system. Additionally, defaultNetworkUniversalTfProfile can also be specified when creating a network in OpenStack. A sample screen shot is given below:
Following are the supported network profiles with Cisco Prime DCNM version 7.1(1):
The syntax to use non-default profiles when creating a network is given below. In the examples, network_name signifies the name of the network followed by a sub-string of the profile name:
network_name:L2
network_name: Ipv4Ef
network_name: Ipv4Tf
network_name: UniversalTf
network_name: UniversalEf
If this profile is chosen when a network is created in OpenStack, DCNM DHCP server will not assign an IP address for the VM associated with the network. Users are required to configure a static IP address for the VM. Additionally, the following command needs to be run on the OpenStack control node:
$fabric_enabler_cli Cisco Nexus Fabric Command Line Interface (Nexus-Fabric) set_static_ip --mac fa:16:3e:72:ab:dc --ip 136.10.0.16
The MAC address is the VM's vNIC and the IP address is the statically configured VM IP address. When a VM is removed from OpenStack, the above entry is automatically removed by the system.
You need to create and add a security group with appropriate rules before launching the VM. Create a security group and security rules that allow DHCP (from DCNM) and your data traffic to go through. After logging into Horizon as a user, click Project > Compute > Access Security. Use the Create Security Group tab to create a security group. After a security group is created, it appears in the Security Groups tab. A newly added group security_group_ex is displayed in the following sample screen shot.
Click Manage Rules for the security group you just created and add new rules. For example, if the following rule displayed in the Add Rule screen shot is added for the security group, it will allow all traffic.
Follow these steps to launch the VM:
Click Instances and then click Launch Instance.
Click the Image drop-down menu and select the image.
By default, the CirrOS image is selected.
Specify a name for the Instance.
Select the Security tab and choose the security group created (it is recommended to uncheck the default rule and select the one you specified).
Click the Networking tab and select the network from the Available network list.
Click Launch.