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 section includes the following topics:
You install Prime Network Services Controller on OpenStack by using the ISO image. The installation time varies from 10 to 20 minutes depending on the host and the storage area network load.
To install Prime Network Services Controller on OpenStack, complete the tasks described in the following topics:
Confirm that you have met the requirements in Requirements Overview. OpenStack Havana is required for Prime Network Services Controller 3.4 functionality.
Note | Although you can install Prime Network Services Controller 3.4 on OpenStack Grizzly, you will not have access to 3.4 functionality unless you use OpenStack Havana. |
Gather the information required for configuration as identified in Information Required for Configuration and Installation.
Confirm that you have admin privileges.
Confirm that the Cinder service is up and running.
Create a project on which to install Prime Network Services Controller.
Create a Cinder volume with the size of 20 GB.
Configure a security group that allows TCP, UDP, and ICMP traffic with Prime Network Services Controller.
For information on how to configure these items, see the OpenStack documentation at docs.openstack.org.
Install Prime Network Services Controller as described in Installing Prime Network Services Controller on OpenStack KVM.
This procedure describes how to install the ISO image on a VM that has been configured for Prime Network Services Controller.
Confirm the following items:
All system requirements are met.
You have the information identified in Information Required for Configuration and Installation.
You have configured the hypervisor for the Prime Network Services Controller installation procedure.
A VM has been created for Prime Network Services Controller and has network access.
You can access the VM console.
You have the IP address for the instance launched in OpenStack.
Step 1 | Open the VM console if it is not already open. If you have just finished configuring the hypervisor, the Prime Network Services Controller installer displays within a few minutes. | ||
Step 2 | In the Network Configuration screen, click Edit in the Network Devices area, enter the IP address and netmask for the Prime Network Services Controller VM, and click OK. | ||
Step 3 | In the Network Configuration area, enter the hostname, domain name, and IP addresses for the gateway, DNS server, and NTP server. | ||
Step 4 | In the Modes screen, choose the required modes, and click Next: | ||
Step 5 | In the
Administrative Access screen, enter the administrator and shared secret
passwords with confirming entries.
For information on creating a strong password, see Shared Secret Password Criteria.
| ||
Step 6 | In the Summary screen, confirm that the information is accurate, and then click Finish. Prime Network Services Controller installs on the VM. This takes a few minutes. | ||
Step 7 | When prompted, disconnect from the media source and then click Reboot. Prime Network Services Controller is then installed on the VM. | ||
Step 8 | To confirm that Prime Network Services Controller is accessible, connect to Prime Network Services Controller through the console for the CLI or a browser for the GUI. |
If you reboot a Prime Network Services Controller instance from the OpenStack Horizon UI, the reboot operation fails and the console contains a message stating that no bootable image can be found. This situation occurs for instances that were created using an ISO image, such as Prime Network Services Controller.
In OpenStack, the first time an instance is created by using an ISO image and rebooted, the root device name is set to /dev/hda. After the instance is created, the bootable image is located on vda. However, with the implementation of hard and soft reboot options in OpenStack, the disk definitions change. As a result, a bootable image cannot be found for the Prime Network Services Controller instance.
To reboot Prime Network Services Controller in OpenStack, use either of the following procedures:
Use this procedure to reboot a Prime Network Services Controller instance in OpenStack. For more information about OpenStack, see http://docs.openstack.org/.
Use this procedure to reboot a Prime Network Services Controller instance in OpenStack. For more information about OpenStack, see http://docs.openstack.org.