Kvik SH060, Руководство по сборке, Страница: 50 / 82

Once the installation is complete, see Configuring Network Access on CentOS 7.3 Using nmcli, on page 67 .
Deploying the Regional Cluster or Local Cluster on OpenStack
To install the Cisco Prime Network Registrar virtual appliance, you must first download the correct installation
file. There are two files available, a regional virtual appliance and a local cluster virtual appliance. Each of
these virtual appliances are provided as a .ova file.
The names are as follows:
• cpnr_9_1_local.qcow2 for the local virtual appliance
• cpnr_9_1_regional.qcow2 for the regional virtual appliance
Download the virtual appliance of your choice. Every Cisco Prime Network Registrar local cluster installation
must connect to a Cisco Prime Network Registrar regional cluster in order to receive the necessary license
information required to operate. Thus, before you install a Cisco Prime Network Registrar local virtual
appliance you must identify the IP address of the regional cluster to which it will connect to receive the license
information.
To run the local cluster or regional cluster on OpenStack, you must first create a local or regional image out
using the
.qcow2 distribution kit.
After this image exists, you may launch an instance of the local or regional cluster. The Flavor you associate
with the instance needs at least 1 VCPU, 8GB of RAM, and at least 14 GB of root disk storage. In order to
have an operational instance of CPNR, you must allocate more than the absolute minimum of 14 GB of root
disk storage. See the
System Requirements, on page 39 section for the amount of disk space needed for a
local or regional cluster.
An instance of Cisco Prime Network Registrar will be created with a fixed IP address. Cisco Prime Network
Registrar will automatically use any IP addresses associated with interfaces that it can detect when it is started.
If the interface available to Cisco Prime Network Registrar has an IP address allocated to it from a provider
network (i.e., it is accessible to the clients that need the DHCP or DNS capabilities provided by Cisco Prime
Network Registrar), then you can configure Cisco Prime Network Registrar normally.
You have two options when creating an OpenStack instance with respect to root login. When you install a
Cisco Prime Network Registrar virtual appliance on VMware or using the KVM kit, you configure the root
password for the underlying Linux system on the system console when the virtual machine is first booted.
However, usually OpenStack instances are created and deployed in such a way as to only allow logins with
SSH using an SSH key-pair that is configured as part of the OpenStack instance. Many OpenStack instances
do not allow root password login at all, and only allow login using SSH with an SSH key-pair.
A Cisco Prime Network Registrar OpenStack instance can be configured to operate in either of these two
regimes:
Option 1: require root password configuration and allow root login using a password.
Option 2: disable the root password configuration and login, an SSH key-pair is required to login.
Option 1
This is the default approach for all Cisco Prime Network Registrar virtual appliance kits, and requires no
additional actions. You will launch an instance from the Cisco Prime Network Registrar virtual appliance
image, and on first boot you will have to bring up a console window for the Cisco Prime Network Registrar
instance, and enter a root password for the Linux system, and accept the End User License Agreement. After
the first boot, you will not need to access the console. You can also access this instance with an
SSH
key-pair.
Cisco Prime Network Registrar 9.1 Installation Guide
44
Cisco Prime Network Registrar Virtual Appliance
Deploying the Regional Cluster or Local Cluster on OpenStack