Contents

1   Introduction

This document provides information on configuring or reconfiguring settings in a running Cloud Execution Environment (CEE). It is a collection of independent procedures. Use the table of contents to select the section relevant to the task to be performed.

Note:  

This document is not used for CEE installation.

1.1   Prerequisites

This section states the prerequisites that must be fulfilled.

1.1.1   Conditions

Ensure that the following condition is met:

• The CEE is installed and it is up and running.

1.1.2   Tools and Equipment

Ensure that the following tool is available:

• Management tool for the node configuration

1.1.3   Documents

Ensure that the following document has been read:

• User Guide for the used management tool
• CEE Connectivity User Guide

2   Fencing

Use the relevant section:

• To reconfigure the fencing behavior, see Section 2.1.
• To reconfigure the access of fencing to out-of-band management, see Section 2.2.

2.1   Fencing Behavior

To change the settings for fencing behavior, perform the following steps:

1. Modify the fencing-related parameters in the cmha section of the config.yaml configuration file in the CEE_RELEASE directory on the Fuel node. Refer to the Configuration File Guide for the parameters and their possible values.
2. Validate the updated configuration file by using the following command on the Fuel node:

   validate_config_yaml /mnt/cee_config/config.yaml

3. If the command output contains errors for some of the parameters, fix the reported problems and repeat Step 2. If the command output does not contain errors, continue with Step 4.
4. Rerun the CM-HA Ansible playbook:

   cd /usr/share/ericsson-orchestration/playbooks/ && openstack-ansible eri-cmha-install.yml

   cd /usr/share/ericsson-orchestration/playbooks/ ⇒<nl
   />&& openstack-ansible eri-cmha-install.yml

5. Perform a Fuel synchronization as described in Fuel Synchronization.

2.2   Fencing Access to Out-of-Band Management

In case the out-of-band management access has been changed, fencing must be reconfigured accordingly to make sure that it works with the new password. Perform the following steps to change the settings for fencing:

1. Modify the out-of-band management access parameters in the shelf section of the config.yaml configuration file in the CEE_RELEASE directory on the Fuel node. Refer to the Configuration File Guide for the parameters. Fencing uses the usernames and passwords configured for blade management.
2. Validate the updated configuration file by using the following command on the Fuel node:

   validate_config_yaml /mnt/cee_config/config.yaml

3. If the command output contains errors for some of the parameters, fix the reported problems and repeat Step 2 in Section 2.1. If the command output does not contain errors, continue with Step 4 in Section 2.1.
4. Rerun the CM-HA Ansible playbook:

   cd /usr/share/ericsson-orchestration/playbooks/ && openstack-ansible eri-cmha-install.yml

   cd /usr/share/ericsson-orchestration/playbooks/ ⇒<nl
   />&& openstack-ansible eri-cmha-install.yml

5. Perform a Fuel synchronization as described in Fuel Synchronization.

3   Legal Text at Logon

The legal text presented at logon can be updated depending on the deployment as follows.

Multi-Server deployment

1. Modify the legaltext section of the config.yaml configuration file in the CEE_RELEASE directory on the Fuel node. Refer to the Configuration File Guide for the parameters.
2. Validate the updated configuration file by using the following command on the Fuel node:

   validate_config_yaml /mnt/cee_config/config.yaml

3. If the command output contains errors for some of the parameters, fix the reported problems and repeat Step 2 in Section 2.1. If the command output does not contain errors, continue with Step 4 in Section 2.1.
4. Rerun the Ansible playbook:

   cd /usr/share/ericsson-orchestration/playbooks/ && openstack-ansible eri-hardening.yaml

   cd /usr/share/ericsson-orchestration/playbooks/ ⇒<nl
   />&& openstack-ansible eri-hardening.yaml

5. Perform a Fuel synchronization as described in Fuel Synchronization.

Single Server deployment

1. Log on to the vCIC:

   ssh ceeadm@<cic_address>

2. Update the /etc/issue and /etc/issue.net files. Sudo privileges are required.
3. Log on to the compute host:

   ssh ceeadm@<compute_address>

4. Update the /etc/issue and /etc/issue.net files. Sudo privileges are required.
5. The legaltext section in config.yaml on Fuel also has to be updated.
   1. Login to the installation laptop hosting the Fuel.
   2. Log on to Fuel.
   3. Update config.yaml. Sudo privileges are required.

4   Static Routes

This section is only applicable to configurations with Neutron managed Extreme switches.

The maximum number of static routes is defined in the neutron.conf file. If more static routes are needed, the default setting must be changed by performing the following steps:

1. Log on to the CIC:

   ssh ceeadm@<cic_address>

2. Add the following option to the /etc/neutron.conf file:

   ext_max_routes = <value>

3. Repeat Step 1 and Step 2 for each CIC.
4. Restart the Neutron server by using the following command:

   crm resource restart neutron-server

Note:  

For setting the ext_max_routes value at CEE installation, refer to the Neutron Configuration Options in the Configuration File Guide.