System Configuration Management Using the CLI You can use the CLI to make changes to the system configuration after installation.

For information about the types of configuration changes you can make, and guidelines for implementing them on an operational system, see System Configuration Management on page 79. During some configuration changes, system alarms are raised; for help viewing them from the CLI, see System Alarms CLI Commands on page 176.

To make configuration changes using the CLI, you must log in as user wrsroot to the active controller and source the script /etc/nova/openrc to obtain Keystone administrative privileges. See Linux User Accounts on page 18 for details.

With the exception of the DNS Server Configuration, the configuration changes described in this section require that you lock and unlock the indicated hosts after the configuration change is made. For more information about locking and unlocking hosts, see Host Inventory on page 103.

OAM IP Configuration

To view the existing OAM IP configuration, use the following command. ~(keystone_admin)$ system oam-show

To change the OAM IP subnet, floating IP address, gateway IP address, or controller IP addresses, use the following command syntax.

~(keystone_admin)$ system oam-modify oam_subnet=subnet/netmask \ oam_gateway_ip=gateway_ip_address \ oam_floating_ip=floating_IP_address \ oam_c0_ip=controller-0_IP_address \ oam_c1_ip=controller-1_ip_address \ action=apply For example:

~(keystone_admin)$ system oam-modify oam_subnet=10.10.10.0/24 \ oam_gateway_ip=10.10.10.1 \

oam_floating_ip=10.10.10.2 \ oam_c0_ip=10.10.10.3 \

oam_c1_ip=10.10.10.4 \ action=apply

After changing the OAM server configuration, you must lock and unlock the controllers. This process requires a swact on the controllers. Then you must lock and unlock the compute nodes one at a time, ensuring that sufficient resources are available to migrate any running instances.

DNS Server Configuration

To view the existing DNS server configuration, use the following command. ~(keystone_admin)$ system dns-show

To change the DNS server IP addresses, use the following command syntax. The nameservers option takes a comma- delimited list of DNS server IP addresses.

~(keystone_admin)$ system dns-modify \

nameservers=IP_address_1[,IP_address_2][,IP_address_3] action=apply For example:

~(keystone_admin)$ system dns-modify \ nameservers=8.8.8.8,8.8.4.4 action=apply NTP Server Configuration

To view the existing NTP server configuration, use the following command. ~(keystone_admin)$ system ntp-show

To change the NTP server IP addresses, use the following command syntax. The ntpservers option takes a comma- delimited list of NTP server names.

~(keystone_admin)$ system ntp-modify \

ntpservers=server_1[,server_2][,server_3] action=apply For example:

~(keystone_admin)$ system ntp-modify \ ntpservers=0.north-america.pool.ntp.org,\

action=apply

After changing the NTP server configuration, you must lock and unlock both controllers. This process requires a swact on the controllers.

Controller Storage Configuration

To view the existing storage configuration, use the following command. ~(keystone_admin)$ system controllerfs-show

Before you can change storage allotments, you must have enough disk space, including additional headroom required to complete the operation. If there is not enough disk space, changes to the storage allotment are disallowed. For more information, see Changing Storage Space Allotments on the Controller on page 85.

You can replace the disks in the controllers to provide more space. For more information, see Managing Controller Nodes on page 113. To support storage changes, you must reinstall the HP Helion OpenStack Carrier Grade software on each controller during the disk replacement procedure. This is required even if the primary disk is not directly affected by the change. To reinstall the software, you can use the following command:

~(keystone_admin)$ system host-reinstall controller_name Note:

Performing a host reinstall successfully is dependent on your BIOS boot order. Observe the following tips. • Prior to installation, the BIOS should be configured to allow booting from disk and the network.

• During the host re-installation, it is advisable to have a console serial cable attached to the host to observe the boot progress.

• BIOS boot order should be: 1. The boot partition.

Typically, this is the disk associated with /dev/sda and is as defined in /proc/cmdline when the load is booted.

2. The NIC on the boot interface (e.g. management or pxe network).

• Set BIOS boot options to ensure failsafe boot if available, e.g. rotating through available boot interfaces, watchdog timer on boot, retry boot interfaces etc.

If the BIOS boot still fails to progress, it may be necessary to force boot via the network interfaces via the BIOS boot option.

To change the database, image, or backup storage allotment, or the Cinder volume storage allotment on a system with an LVM storage backend, use the following command syntax, where the allotments are in GiB.

~(keystone_admin)$ system controllerfs-modify \ database_gib=database_allotment \

backup_gib=backup_allotment \

cinder_gib=cinder_volume_allotment \ action=apply

For example:

~(keystone_admin)$ system controllerfs-modify \

database_gib=10 image_gib=13 backup_gib=22 action=apply

After changing the controller storage configuration, you must lock each controller and reinstall the HP Helion OpenStack Carrier Grade software, even if you have already done so as part of changing the controller disks. You can use the following command:

~(keystone_admin)]$ system host-reinstall controller_name

Then you can unlock the controller to clear any Configuration out-of-date alarms. A controller swact is required to update both controllers.

In document HP Helion OpenStack Carrier Grade 2.0: KVM Region Administration Guide (Page 88-91)