MasterScope Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option

Transcription

1 MasterScope Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option Cluster Configuration Guide 1 Edition March, 2018 NEC Corporation

2 Disclaimer The copyrighted information noted in this document shall belong to NEC Corporation. Copying or revising this document, in whole or in part, is strictly prohibited without the permission of NEC Corporation. This document may be changed without prior notice. NEC Corporation shall not be liable for any technical or editing errors or omissions in this document. NEC Corporation shall not be liable for the accuracy, usability, or certainty of information noted in this document. Copyright information SigmaSystemCenter and MasterScope are registered trademarks of NEC Corporation. Microsoft, Windows, Windows logo, Windows Server, Internet Explorer, and SQL Server are trademarks or registered trademarks of Microsoft Corporation in the United States of America and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States of America and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the United States of America and other countries. Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of Apache Software Foundation. Firefox is a registered trademark or trademark of Mozilla Foundation. Google Chrome is a registered trademark or trademark of Google Inc. The OpenStack Word Mark and the OpenStack logos are registered trademarks or trademarks of the OpenStack Foundation in the United States of America and other countries. MySQL is a registered trademark of Oracle Corporation and/or its affiliates in the United States of Amerida and other countries. Other system names, company names, and product names in this document are trademarks or registered trademarks of their respective companies. Note that mark and the mark are not indicated in this document. Notes on exporting this product If this product (including its software) is subject to regulation under the Foreign Exchange and Foreign Trade Law, it will be necessary to follow the procedures required by this law when exporting this product, such as obtaining an export license from the Japanese Government. If you require documents from NEC in order to obtain an export license, please contact the dealer where you purchased your MasterScope product, or your local NEC sales office. i

3 Preface Target readers and objective This document is intended for system administrators who are responsible for constructing a cluster system for a stack management server by using EXPRESSCLUSTER X. This document describes the construction procedure. Overview of this document This document describes the procedure for constructing a cluster system for a stack management server by using EXPRESSCLUSTER X. For an overview of cluster systems, see "Chapter 1. Overview (page 1)". For details about the procedure for constructing a cluster system, see "Chapter 2. Cluster configuration (page 5)". For details about the procedure for uninstalling a cluster system, see "Chapter 3. Uninstallation (page 22)". Related manuals For the construction of a cluster system, also see the following manuals. Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide EXPRESSCLUSTER X 3.3 for Linux Installation & Configuration Guide SigmaSystemCenter Cluster Construction Virtual DataCenter Automation Standard Edition Portal User Manual (Install) Notation rules of this document This document describes precautions, important items, and related information as follows. Note Indicates precautions, warnings, and supplementary notes for the function, operation, and setting. Notation rules In addition, the following notation rules are applied in this document. Notation How to use Example Arial bold " " Double quotation marks [ ] in a command line Indicates the items to be displayed on the screens (text boxes, check boxes, etc.) Indicates a window name or reference manual Indicates that the specification of the value in [ ] can be omitted. Enter the machine name in the Machine name text box. All check box "Setting" window "Installation Guide" add [/a] Gr1 ii

4 Notation How to use Example Monospace font (courier new) Italicized monospace font (courier new) Indicates the outputs from the command line or system (messages, prompts, and others) Indicates the items to be replaced with a valid value and input by users. When a space is included in the value, enclose the value in " ". Run the following command: replace Gr1 add GroupName InstallPath="Install Path" iii

5 Contents Chapter 1. Overview Hardware requirements Software requirements...4 Chapter 2. Cluster configuration Changing data directories Changing a data directory of an active stack management server Changing a data directory of a standby stack management server Changing the configuration file directories Changing a file directory of an active stack management server Changing a file directory of a standby stack management server Changing to floating IP addresses Changing the endpoint of OpenStack Identity(keystone) Changing the endpoint of OpenStack Orchestration(heat-api) Changing the endpoint of RabbitMQ Changing the endpoint of MySQL Stopping and disabling services Creating cluster configuration data Setting up the network configuration Adding a group resource (floating IP address) Adding a group resource (disk resource) Adding a group resource (mirror disk resource) Adding a group resource (EXEC resource) Adding a process name monitor resource...20 Chapter 3. Uninstallation Stopping and unconfiguring a cluster...23 Appendix A. Revision history iv

6

7 Chapter 1. Overview Chapter 1. Overview In Virtual DataCenter Automation Standard Edition, a different cluster system configuration procedure is used for each of the functions described in Roles of Each Function of the Virtual DataCenter Automation Standard Edition Setup Guide. This document describes the procedure for configuring a cluster system for stack management servers. For details about the procedure for configuring a cluster system for management servers, see the following manuals. SigmaSystemCenter Cluster Construction Virtual DataCenter Automation Standard Edition Portal User Manual (Install) This document describes the procedure for configuring a shared-disk type or mirror-disk type failover cluster system for stack management servers as shown in the following figures. Figure 1-1 Configuration example of a shared disk type cluster system Figure 1-2 Configuration example of a mirror disk type cluster system For details about the above configurations, see Determining a system configuration of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. 1

8 This document provides an example of configuring a typical cluster system consisting of two active/ standby nodes (stack management servers). The system will be set up in an active-standby configuration. In this configuration, the active stack management server operates during normal operation, whereas the standby stack management server will take over the operation (performs failover operation) if the active server suffers a failure. This document describes mainly the procedure for configuring a cluster system consisting of stack management servers that are in an all-in-one configuration, in which all of the MySQL, OpenStack, and RabbitMQ components are installed on a single server. In some cases, DBMS (MySQL) and application (OpenStack and RabbitMQ) components are installed separately on different servers to enable the scale-up of the application servers. In such load distribution configurations, a cluster system often needs to be configured only for the DBMS server. Taking the possibility of such situations into account, this document also gives supplementary descriptions for specifying servers that require specific procedures to be performed due to the components installed in the servers. For details about the component configuration, see 1.1. Component configuration of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide. The parameters required for configuring the above-described cluster system and their setting values (examples) are listed below. Table 1-1 Examples of settings for cluster system configuration Target Parameter Value (for a shared disk configuration) First stack management server (master server) When a load distribution configuration is used, first data base server (master server) Second stack management server When a load distribution configuration is used, second database server Server Name server1 server1 Public LAN IP Address Interconnect LAN IP Address Mirror Disk Connect (mdc1) Server Name server2 server2 Public LAN IP Address Interconnect LAN IP Address Mirror Disk Connect (mdc1) Value (for a mirror disk configuration) First group resource Type floating ip resource floating ip resource Group Resource Name fip fip IP Address Second group resource Type disk resource mirror disk resource Group Resource Name disk md Mount Point /mnt/sdb2 /mnt/sdb2 File System xfs xfs Device Name /dev/sdb2 Cluster Partition Device Name Data Partition Device Name - - /dev/sdb1 /dev/sdb2 Mirror Disk Connect mdc1 Chapter 1. Overview 2

9 Chapter 1. Overview Target Parameter Value (for a shared disk configuration) Value (for a mirror disk configuration) Perform initial mkfs. Remove the check mark. Third group resource Type execute resource execute resource Group Resource Name exec exec Script Standard script Standard script In the following, the descriptions of the procedure assume that the cluster system will be configured using the above setting values. For the actual configuration, change the values according to your environment. 1.1 Hardware requirements The hardware requirements for both the active and standby stack management servers (database servers when a load distribution configuration is used) are as follows. For the hardware requirements other than the following, see 1.2 Hardware requirements of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide Table 1-2 Hardware requirements for a stack management server Hardware name Network interface card (NIC) Hard disk (for mirroring) 100 Mbps or higher 16 GB or larger Spec The network interface card connects with an interconnect LAN. In the configuration described in this document, the interconnect LAN is separate from the public LAN. When a mirror-disk type cluster system configuration is used, the interconnect LAN is also used as the interconnect LAN for mirroring (mirror disk connect LAN). The hard disk (for mirroring) is required only when a mirror-disk type failover cluster system is to be configured. The hard disk (for mirroring) stores data managed by a stack management server, and inherits the data in the event of a failover. For each stack management server, set up the mirroring hard disk that will be used by EXPRESSCLUSTER X. The storage hardware requirements are as follows. Table 1-3 Hardware requirements for the storage Hard disk (for sharing) Hardware name 16 GB or larger Spec The hard disk (for sharing) is required only when a shared-disk type failover cluster system is to be configured. The hard disk (for sharing) stores data managed by a stack management server, and inherits the data in the event of a failover. A shared disk and a mirror disk store the following data. OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine) databases OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine), OpenStack Orchestration(heat-engine), and SSC Resource Plug-in configuration files 3

10 1.2 Software requirements The software requirements for both the active and standby stack management servers (database servers when a load distribution configuration is used) are as follows. For the software requirements other than the following, see 1.3 Software requirements of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide Table 1-4 Software requirements Chapter 1. Overview Cluster software Component Software name EXPRESSCLUSTER X 3.3 for Linux 4

11 Chapter 2. Cluster configuration Chapter 2. Cluster configuration This chapter describes the procedure for configuring a cluster system of stack management servers. The configuration procedure is overviewed below. Each of the procedures is overviewed below. Figure 2-1 Overview of configuration procedure 5

12 1. Configure each of the active and standby stack management servers separately. For details, see Chapter 2, Installation and Chapter 3, Before Starting Operation of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide. 2. Set up a shared disk or mirror disk. For details, see Settings after configuring hardware of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. 3. Change the data directory of MySQL that stores the databases for OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine) to that of the shared disk or the mirror disk. For details, see "2.1 Changing data directories (page 7)". 4. Change the storage directories of the configuration files for OpenStack Identity(keystone), OpenStack Orchestration(heat-api), and OpenStack Orchestration(heat-engine) to those of the shared disk or the mirror disk. For details, see "2.2 Changing the configuration file directories (page 9)". 5. Change the IP addresses of the stack management servers to which the management server connects, to floating IP addresses. For details, see "2.3 Changing to floating IP addresses (page 12)". 6. Stop and disable the services of OpenStack Identity(keystone), OpenStack Orchestration(heatapi), OpenStack Orchestration(heat-engine), and MySQL. For details, see "2.4 Stopping and disabling services (page 16)". 7. Install EXPRESSCLUSTER X and register its license on the active and standby stack management servers. For details, see Installing EXPRESSCLUSTER and Registering the license of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. 8. Create cluster configuration data. For details, see "2.5 Creating cluster configuration data (page 16)". 9. Create the cluster by applying the created cluster configuration data to the active and standby stack management servers, and then start the cluster system. For details, see Creating a cluster of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. When an all-in-one configuration is used, each of the above procedures is performed on a single server of each of the active and standby systems. When a load distribution configuration is used, in contrast, it is necessary to perform the procedures while considering which server of the active and standby systems is subject to each of the procedures. Before starting the work, see the following for details about the procedures to be performed on each server. Table 2-1 Procedures to be performed on each server in a load distribution configuration Procedure Refer to Implementation on the DBMS server on which the MySQL component is installed Configuring both active and standby stack management servers Setting a shared disk and mirror disk Chapter 2, Installation and Chapter 3, Before Starting Operation of Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option User's Guide. Settings after configuring hardware of Chapter 2. Cluster configuration Implementation on the application server on which the OpenStack and RabbitMQ components are installed 6

13 Chapter 2. Cluster configuration Procedure Refer to Implementation on the DBMS server on which the MySQL component is installed Changing data directories Changing the configuration file location Changing the connection destination to a floating IP address Stopping and disabling services Installing EXPRESSCLUSTER X. Creating cluster configuration data Creating and starting a cluster EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide "2.1 Changing data directories (page 7)" "2.2 Changing the configuration file directories (page 9)" "2.3 Changing to floating IP addresses (page 12)" "2.4 Stopping and disabling services (page 16)" Installing EXPRESSCLUSTER and Registering the license of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. "2.5 Creating cluster configuration data (page 16)" Creating a cluster of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide Legend: : Necessary to perform; : Unnecessary to perform 2.1 Changing data directories Implementation on the application server on which the OpenStack and RabbitMQ components are installed Change the data directory of MySQL that stores the databases for OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine) to that of the shared disk or the mirror disk. Change the data directories in the following order. Active stack management server (active DBMS server when a load distribution configuration is used) Standby stack management server (standby DBMS server when a load distribution configuration is used) Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". 7

14 Chapter 2. Cluster configuration Table 2-2 Parameters to be referenced in this section Target Parameter Value (for shared disk configuration) Value (for mirror disk configuration) Second group resource Type disk resource mirror disk resource Mount Point /mnt/sdb2 /mnt/sdb2 File System xfs xfs Device Name /dev/sdb2 Data Partition Device Name /dev/sdb Changing a data directory of an active stack management server The procedure described in this section must be performed on the active stack management server. When a load distribution configuration is used, perform this procedure on the active DBMS server on which the MySQL component is installed. 1. Before changing the database storage directory of MySQL, stop the MySQL service. mysql service stop command $ systemctl stop mysqld.service 2. Mount a shared disk or a mirror disk. Mount command for a shared disk configuration $ mount -t file-system -o defaults device-name mount-point Mount command for a mirror disk configuration $ mount -t file-system -o defaults data-partition-device-name mount-point 3. Create a database storage directory for MySQL under the mounted shared disk or mirror disk. In the example shown in this document, the directory is set up at mount-point/mysql. Change the location as needed. mysql directory creation command $ mkdir mount-point/mysql 4. Change the database storage directory of MySQL. Open the /etc/my.cnf file, and change the datadir value to the path to the mysql directory of the mounted shared disk or mirror disk. [mysqld] datadir=mount-point/mysql The following shows an example of making this setting. [mysqld] datadir=/mnt/sdb2/mysql Copy database files stored in the previous database storage directory (default directory: /var/lib/mysql) to the mysql directory under the mounted shared disk or mirror disk. In addition, change the owner. 8

15 Database file copy command and database file owner change command Chapter 2. Cluster configuration $ cp -R /var/lib/mysql/* mount-point/mysql $ chown -R mysql:mysql mount-point/mysql 5. Add and apply context mapping to the mysql directory under the mounted shared disk or mirror disk. Context mapping addition and application commands $ semanage fcontext -a -t mysqld_db_t "mount-point/mysql(/.*)?" $ restorecon -R -v mount-point/mysql 6. After making the change, check whether the system starts up without any problems. mysql service start command $ systemctl start mysqld.service Changing a data directory of a standby stack management server The procedure described in this section must be performed on the standby stack management server. When a load distribution configuration is used, perform this procedure on the standby DBMS server on which the MySQL component is installed. 1. Before changing the database storage location of MySQL, stop the MySQL service. mysql service stop command $ systemctl stop mysqld.service 2. Change the database storage location of MySQL. Open the /etc/my.cnf file, and change the datadir value to the path to the mysql directory of the shared disk or the mirror disk to be mounted. Make the settings for the database storage directory that was set up in "2.1.1 Changing a data directory of an active stack management server (page 8)". [mysqld] datadir=mount-point/mysql The following shows an example of making this setting. [mysqld] datadir=/mnt/sdb2/mysql 2.2 Changing the configuration file directories Change the storage directories for the configuration files for OpenStack Identity(keystone), OpenStack Orchestration(heat-api), OpenStack Orchestration(heat-engine), and SSC Resource Plugin to those of the shared disk or the mirror disk. Change the configuration file directories in the following order. Active stack management server Standby stack management server 9

16 Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-3 Parameters to be referenced in this section Target Parameter Value (for shared disk configuration) Value (for mirror disk configuration) Second group resource Type disk resource mirror disk resource Mount Point /mnt/sdb2 /mnt/sdb Changing a file directory of an active stack management server The procedure described in this section must be performed on the active stack management server. When a load distribution configuration is used, this procedure is unnecessary. 1. Before changing the storage directory of the configuration file for OpenStack Identity(keystone), stop the OpenStack Identity(keystone) service. OpenStack Identity(keystone) service stop command Chapter 2. Cluster configuration $ systemctl stop httpd 2. Create a storage directory for the configuration file for OpenStack Identity(keystone) under the shared disk or mirror disk mounted in "2.1.1 Changing a data directory of an active stack management server (page 8)". In the example shown in this document, the directory is set up at mount-point/keystone. Change the location as needed. keystone directory creation command $ mkdir mount-point/keystone 3. Copy files stored in the previous storage directory (default directory: /etc/keystone) of the configuration file for OpenStack Identity(keystone) to the keystone directory under the mounted shared disk or mirror disk. In addition, change the owner. Configuration file copy command and database file owner change command $ cp -R /etc/keystone/* mount-point/keystone $ chown -R keystone:keystone mount-point/keystone 4. Add and apply context mapping to the keystone directory under the mounted shared disk or mirror disk. Context mapping addition and application commands $ semanage fcontext -a -t etc_t "mount-point/keystone(/.*)?" $ restorecon -R -v mount-point/keystone 5. Create a symbolic link for referencing the changed storage directory of the configuration file for OpenStack Identity(keystone). Configuration file storage directory change command $ mv /etc/keystone/ /etc/keystone.org $ ln -s mount-point/keystone/ /etc/keystone 6. After making the change, check whether the system starts up without any problems. 10

17 Chapter 2. Cluster configuration httpd service start command $ systemctl start httpd 7. Subsequently, change the storage directories of the configuration files for OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine). In the example shown in this document, the directories are set up at mount-point/heat. Change the location as needed. The same procedure as that for OpenStack Identity(keystone) described above (Steps 1 to 6) applies. The following shows the necessary commands. $ systemctl stop openstack-heat-api openstack-heat-engine $ mkdir mount-point/heat $ cp -R /etc/heat/* mount-point/heat $ chown -R heat:heat mount-point/heat $ mv /etc/heat/ /etc/heat.org $ semanage fcontext -a -t etc_t "mount-point/heat(/.*)?" $ restorecon -R -v mount-point/heat $ ln -s mount-point/heat/ /etc/heat $ systemctl start openstack-heat-api openstack-heat-engine 8. Change the storage directory of the configuration file for SSC Resource Plug-in. In the example shown in this document, the directories are set up at mount-point/.heat-ssc. Change the location as needed. The same procedure as that for OpenStack Identity(keystone) described above (Steps 1 to 6) applies. The following shows the necessary commands. However, it is not necessary to add or apply context mapping. $ systemctl stop openstack-heat-api openstack-heat-engine $ mkdir mount-point/.heat-ssc $ cp -R /var/lib/heat/.heat-ssc/* mount-point/.heat-ssc $ chown -R heat:heat mount-point/.heat-ssc $ mv /var/lib/heat/.heat-ssc/ /var/lib/heat/.heat-ssc.org $ ln -s mount-point/.heat-ssc /var/lib/heat/.heat-ssc $ systemctl start openstack-heat-api openstack-heat-engine Changing a file directory of a standby stack management server The procedure described in this section must be performed on the standby stack management server. When a load distribution configuration is used, this procedure is unnecessary. 1. Before changing the storage directory of the configuration file for OpenStack Identity(keystone), stop the OpenStack Identity(keystone) service. OpenStack Identity(keystone) service stop command $ systemctl stop httpd 2. Make a setting change to enable reference to the changed storage directory of the configuration file for OpenStack Identity(keystone). Execute commands according to the storage directory of the configuration file that was set up in step "2. (page 10)" of "2.2.1 Changing a file directory of an active stack management server (page 10)". Configuration file storage directory change command 11

18 Chapter 2. Cluster configuration $ mv /etc/keystone/ /etc/keystone.org $ ln -s mount-point/keystone/ /etc/keystone 3. Change the storage directories of the configuration files for OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine). Execute commands according to the storage directories of the configuration files that were set up in Step "7. (page 11)" of "2.2.1 Changing a file directory of an active stack management server (page 10)". The same procedure as that described above applies. The following shows the necessary commands. $ systemctl stop openstack-heat-api openstack-heat-engine $ mv /etc/heat/ /etc/heat.org $ ln -s mount-point/heat/ /etc/heat 4. Change the storage directory of the configuration file for SSC Resource Plug-in. Execute commands according to the storage directory of the configuration file that was set up in Step "8. (page 11)" of "2.2.1 Changing a file directory of an active stack management server (page 10)". The same procedure as that described above applies. The following shows the necessary commands. $ mv /var/lib/heat/.heat-ssc/ /var/lib/heat/.heat-ssc.org $ ln -s mount-point/.heat-ssc /var/lib/heat/.heat-ssc 2.3 Changing to floating IP addresses Change the IP addresses of the stack management servers to which the management server connects, to floating IP addresses. The procedure described in this section must be performed on the active stack management server. When a load distribution configuration is used, perform this procedure on the active application server on which the OpenStack component is installed. Change the endpoint of each component to a floating IP address, in the following order. OpenStack Identity(keystone) OpenStack Orchestration(heat-api) RabbitMQ MySQL Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-4 Parameters to be referenced in this section Target Parameter Value (for shared disk configuration) Value (for mirror disk configuration) First group resource Type floating ip resource floating ip resource IP Address

19 Chapter 2. Cluster configuration Changing the endpoint of OpenStack Identity(keystone) Change the connection destination of OpenStack Identity(keystone) to a floating IP address. When a load distribution configuration is used, this procedure is unnecessary. 1. Change the connection destination of OpenStack Identity(keystone) registered in the database to a floating IP address. a. Assign an authentication token and the endpoint URL to the relevant environment variables. Execute the following command, and make a note of the admin_token value. $ cat /etc/keystone/keystone.conf grep admin_token Assign the noted admin_token value to the OS_TOKEN environment variable. $ export OS_TOKEN=admin_token-value $ export OS_IDENTITY_API_VERSION=3 $ export OS_URL= t-port-number/v3 A command execution example is shown below. $ cat /etc/keystone/keystone.conf grep admin_token admin_token = 3b53d3bd3ce8942c878c # `None`, the value is ignored and the `admin_token` log in mechanism is # effectively disabled. To completely disable `admin_token` in production #admin_token = <None< $ export OS_TOKEN=3b53d3bd3ce8942c878c $ export OS_IDENTITY_API_VERSION=3 $ export OS_URL= b. Check the endpoints that have been set. Execute the following command, and make a note of the endpoint list. $ openstack endpoint list A command execution example is shown below. $ openstack endpoint list ID Region Service Name Service Type Enabled Interface URL e46a7174be848febfbec947fe8eb8f4 RegionOne keystone identity True public b72b4c b6ca7c29075cdd884f1 RegionOne keystone identity True internal cde0c8d8193e4c3e9a2e26cf b RegionOne heat orchestration True public e70a ddf378cf4a16d RegionOne keystone identity True admin c. Change the URL of the endpoint with a Service Name value of keystone to a floating IP address. Execute the following command to change the endpoint. For management-portnumber and public-port-number, use their current setting values as is. 13

20 Chapter 2. Cluster configuration $ openstack endpoint set --url " /v3" public-endpoint-id $ openstack endpoint set --url " /v3" internal-endpoint-id $ openstack endpoint set --url " mber/v3" admin-endpoint-id A command execution example is shown below. $ openstack endpoint set --url " 5e46a7174be848f ebfbec947fe8eb8f4 $ openstack endpoint set --url " b72b4c b6 ca7c29075cdd884f1 $ openstack endpoint set --url " e70a ddf378cf4a16d 2. Change the connection destination of OpenStack Identity(keystone) described in /root/adminopenrc and /root/portal-openrc to a floating IP address. Before change export OS_AUTH_URL= After change export OS_AUTH_URL= 3. Change the endpoint for establishing a connection from OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine) to OpenStack Identity(keystone) to a floating IP address. Change the setting values described in /etc/heat/heat.conf. $ openstack-config --set /etc/heat/heat.conf keystone_authtoken auth_uri -IP-address:public-port-number $ openstack-config --set /etc/heat/heat.conf keystone_authtoken auth_url -IP-address:management-port-number $ openstack-config --set /etc/heat/heat.conf trustee auth_url :management-port-number $ openstack-config --set /etc/heat/heat.conf ec2authtoken auth_uri dress:public-port-number $ openstack-config --set /etc/heat/heat.conf clients_keystone auth_uri P-address:management-port-number The setting values described in the configuration file are changed in response to the execution of the commands. The following shows an example of the execution result. [keystone_authtoken] auth_uri = auth_url = [trustee] auth_url = [ec2authtoken] auth_uri = [clients_keystone] auth_uri = Changing the endpoint of OpenStack Orchestration(heat-api) Change the connection destination of OpenStack Orchestration(heat-api) registered in the database to a floating IP address. When a load distribution configuration is used, this procedure is unnecessary. 1. Assign an authentication token and the endpoint URL to the relevant environment variables. Make the setting in step "a. (page 13)" of "2.3.1 Changing the endpoint of OpenStack Identity(keystone) (page 13)". 14

21 2. Check the endpoints that have been set. Execute the following command. Chapter 2. Cluster configuration $ openstack endpoint list ID Region Service Name Service Type Enabled Interface URL e46a7174be848febfbec947fe8eb8f4 RegionOne keystone identity True public htto:// :5000/v3 b72b4c b6ca7c29075cdd884f1 RegionOne keystone identity True internal cde0c8d8193e4c3e9a2e26cf b RegionOne heat orchestration True public e70a ddf378cf4a16d RegionOne keystone identity True admin Change the URL of the endpoint with a Service Name value of heat to a floating IP address. Execute the following command. For port-number, use its current setting value as is. $ openstack endpoint set --url " /v1/%(tenant_id)s" endpoint-id Changing the endpoint of RabbitMQ Change the endpoint for establishing a connection from OpenStack Orchestration(heat-api) and OpenStack Orchestration(heat-engine) to RabbitMQ to a floating IP address. When a load distribution configuration is used, this procedure is unnecessary. 1. Change the setting values described in /etc/heat/heat.conf. $ openstack-config --set /etc/heat/heat.conf oslo_messaging_rabbit rabbit_hostfloat ing-ip-address The setting values described in the configuration file are changed in response to the execution of the command. The following shows an example of the execution result. [oslo_messaging_rabbit] rabbit_host = Changing the endpoint of MySQL Change the endpoint for establishing a connection from OpenStack Identity(keystone) and OpenStack Orchestration(heat-engine) to MySQL to a floating IP address. When a load distribution configuration is used, perform this procedure on the application server on which the OpenStack component is installed. 1. Change the setting value described in /etc/keystone/keystone.conf. To specify keystone-userpassword, use the value currently described in the file as is. $ openstack-config --set /etc/keystone/keystone.conf database connection mysql://ke ystone:keystone-user-password@floating-ip-address:3306/keystone The setting value described in the configuration file is changed in response to the execution of the command. The following shows an example of the execution result. [database] connection = mysql://keystone:keystone@ :3306/keystone 15

22 Chapter 2. Cluster configuration 2. Change the setting value described in /etc/heat/heat.conf. To specify heat-user-password, use the value currently described in the file as is. $ openstack-config --set /etc/heat/heat.conf database connection mysql://heat:heatuser-password@floating-ip-address:3306/heat The setting value described in the configuration file is changed in response to the execution of the command. The following shows an example of the execution result. [database] connection = mysql://heat:heat@ :3306/heat 2.4 Stopping and disabling services Stop and disable the OpenStack Identity(keystone) and OpenStack Orchestration(heat-api), OpenStack Orchestration(heat-engine), and MySQL services. Each service starts when the cluster system is started. Accordingly, it is necessary to make the necessary settings to prevent the services from automatically starting when the server starts up. The procedure described in this section must be performed on both of the active and standby stack management servers. Disable each OpenStack service. When a load distribution configuration is used, this step is unnecessary. $ systemctl disable httpd $ systemctl disable openstack-heat-engine $ systemctl disable openstack-heat-api Disable the MySQL service. When a load distribution configuration is used, perform this step on both of the active and standby DBMS servers on which the MySQL component is installed. $ systemctl disable mysqld Each service starts when the cluster system starts up. Stop the services in advance. Stop each OpenStack service. When a load distribution configuration is used, this step is unnecessary. $ systemctl stop openstack-heat-api $ systemctl stop openstack-heat-engine $ systemctl stop httpd Stop the MySQL service. When a load distribution configuration is used, perform this step on both of the active and standby DBMS servers on which the MySQL component is installed. $ systemctl stop mysqld 2.5 Creating cluster configuration data Create cluster configuration data. For details about how to create cluster configuration data, see Creating the configuration data of a 2- node cluster of EXPRESSCLUSTER X 3.3 for Linux Installation & Configuration Guide. When a load distribution configuration is used, create cluster configuration data for the DBMS server in which the MySQL component is installed. The following is an overview of the procedure. 16

23 1. Creating a cluster Add a cluster Add a server Set up the network configuration Set up the network partition resolution 2. Creating a failover group Add a failover group Add a group resource (floating IP address) Add a group resource (disk resource) Add a group resource (mirror disk resource) Add a group resource (EXEC resource) 3. Creating a monitor resources Add a monitor resource (disk resource) Add a monitor resource (IP monitor) This section describes the setups unique to this product by focusing on the following steps of the procedure Set up the network configuration 2-2. Add a group resource (floating IP address) 2-4. Add a group resource (disk resource) 2-5. Add a group resource (mirror disk resource) 2-6. Add a group resource (EXEC resource) It also describes the setup for the process name monitor resource as a monitor resource unique to this product Setting up the network configuration Set an interconnect between an active and standby stack management server. Set an interconnect according to 1-3. Set up the network configuration of EXPRESSCLUSTER X 3.3 for Linux Installation and Configuration Guide. Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-5 Parameters to be referenced in this section Target Parameter Value (for a shared disk configuration) First stack management server information (master server) Second stack management server information Server Name server1 server1 Interconnect LAN IP Address Mirror Disk Connect (mdc1) Server Name server2 server2 Chapter 2. Cluster configuration Value (for a mirror disk configuration) 17

24 Chapter 2. Cluster configuration Target Parameter Value (for a shared disk configuration) Interconnect LAN IP Address Mirror Disk Connect (mdc1) Value (for a mirror disk configuration) For a mirror disk configuration, select mdc1 (mirror disk connect) for MDC of the interconnect LAN. For a shared disk configuration, Adding a group resource (floating IP address) Add a group resource (floating IP address). Set a floating IP address according to 2-2. Add a group resource (floating IP address) of EXPRESSCLUSTER X 3.3 for Linux Installation and Configuration Guide. Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-6 Parameters to be referenced in this section Target Parameter Value (for a shared disk configuration) Value (for a mirror disk configuration) First group resource Type floating ip resource floating ip resource Group Resource Name fip fip IP Address Adding a group resource (disk resource) Add a (shared) disk resource to a group resource. Perform this procedure only when a shared disk configuration is used. Set a disk resource according to 2-4. Add a group resource (disk resource) of EXPRESSCLUSTER X 3.3 for Linux Installation and Configuration Guide. Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-7 Parameters to be referenced in this section Target Parameter Value (for a shared disk configuration) Value (for a mirror disk configuration) Second group resource Type disk resource mirror disk resource Group Resource Name disk md Mount Point /mnt/sdb2 /mnt/sdb2 File System xfs xfs Device Name /dev/sdb Adding a group resource (mirror disk resource) Add a mirror disk resource to a group resource. Perform this procedure only when a mirror disk configuration is used. 18

25 Set a disk resource according to 2-5. Add a group resource (mirror disk resource) of EXPRESSCLUSTER X 3.3 for Linux Installation and Configuration Guide. Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-8 Parameters to be referenced in this section Target Parameter Value (for a shared disk configuration) Value (for a mirror disk configuration) Second group resource Type disk resource mirror disk resource Group Resource Name disk md Mount Point /mnt/sdb2 /mnt/sdb2 File System xfs xfs Cluster Partition Device Name Data Partition Device Name /dev/sdb1 /dev/sdb2 Mirror Disk Connect mdc1 Perform initial mkfs. Remove the check mark Adding a group resource (EXEC resource) Add an EXEC resource to a group resource. Set an EXEC resource according to 2-6. Add a group resource (EXEC resource) of EXPRESSCLUSTER X 3.3 for Linux Installation and Configuration Guide. Perform this procedure according to the following parameters of "Table 1-1 Examples of settings for cluster system configuration (page 2)". Table 2-9 Parameters to be referenced in this section Target Parameter Value (for a shared disk configuration) Value (for a mirror disk configuration) Third group resource Type execute resource execute resource When an all-in-one configuration is used Group resource name exec exec Script Standard script Standard script As the script that is to be executed at the startup, set the following. Chapter 2. Cluster configuration #! /bin/sh #*************************************** #* start.sh * #*************************************** # start mysqld systemctl start mysqld exit 1 # start httd(keystone) systemctl start httpd exit 1 # start heat-engine systemctl start openstack-heat-engine exit 1 # start heat-api 19

26 Chapter 2. Cluster configuration systemctl start openstack-heat-api exit 1 exit 0 As the script that is to be executed at the stop, set the following. #! /bin/sh #*************************************** #* stop.sh * #*************************************** # stop heat-api systemctl stop openstack-heat-api exit 1 # stop heat-engine systemctl stop openstack-heat-engine exit 1 # stop httpd(keystone) systemctl stop httpd exit 1 # stop mysqld systemctl stop mysqld exit 1 exit 0 When a load distribution configuration is used As the script that is to be executed at the startup, set the following. #! /bin/sh #*************************************** #* start.sh * #*************************************** # start mysqld systemctl start mysqld exit 1 exit 0 As the script that is to be executed at the stop, set the following. #! /bin/sh #*************************************** #* stop.sh * #*************************************** # stop mysqld systemctl stop mysqld exit 1 exit Adding a process name monitor resource Add a monitor resource for monitoring process names running on a stack management server. Add httpd. 1. On [Group], click [Next]. 2. The [Monitor Resource] screen is displayed. Click [Add]. 3. The [Monitor Resource Definition] dialog box is displayed. On the [information] screen, select a monitor resource type (process name monitor) in the [Type] box and enter a monitor resource name (psw) in the [Name] box. Click [Next]. 4. Enter the monitoring settings. On the [Monitor(common)] tab, select [Active] in [Monitoring Timing] and set [fip] for [Target Resource]. Click [Next]. 20

27 5. On the [Monitor(special)] tab, enter "/usr/sbin/httpd*" in the [Process name] box. For [Minimum Monitored Process Count], set 1. Click [Next]. 6. Set a recovery target. Click the [Browse] button. Chapter 2. Cluster configuration 7. On the displayed tree view, select [Executing failover the recovery target] for [Recovery Action] and [failover] for [Recovery Target]. Click [Finish]. 21

28 Chapter 3. Uninstallation Chapter 3. Uninstallation This chapter describes the procedure for uninstalling a cluster system. The cluster system is unconfigured, and then the stack management server is uninstalled. Perform this procedure on the active stack management server. The uninstallation procedure is overviewed below. Each of the procedures is overviewed below. Figure 3-1 Overview of uninstallation 1. Stop and unconfigure a cluster. For details, see "3.1 Stopping and unconfiguring a cluster (page 23)". 2. Uninstall EXPRESSCLUSTER X. For details, see Uninstallation of EXPRESSCLUSTER X 3.3 for Linux Installation & Configuration Guide. 3. Uninstall both stack management servers. For details, see Chapter 5, Uninstallation of vdc Automation Standard Edition Topology Template Orchestrator Option User's Guide. When an all-in-one configuration is used, each of the above procedures is performed on the single server of the active system. When a load distribution configuration is used, in contrast, it is necessary to perform the procedures while considering which server of the active system is subject to each of the procedures. Before starting the work, see the following for details about the procedures to be performed on each server. Table 3-1 Procedures to be performed when components are installed separately on different servers Procedure Implementation on the DBMS server on which the MySQL component is installed Implementation on the application server on which the OpenStack and RabbitMQ components are installed Stopping and unconfiguring a cluster 22

29 Chapter 3. Uninstallation Procedure Uninstalling EXPRESSCLUSTER X. Uninstalling both stack management servers Implementation on the DBMS server on which the MySQL component is installed Implementation on the application server on which the OpenStack and RabbitMQ components are installed Legend: : Necessary to perform; : Unnecessary to perform 3.1 Stopping and unconfiguring a cluster Stop a cluster. A cluster system can be unconfigured by deleting failover groups from the cluster configuration data and deleting servers. 1. Start WebManager. Access to the WebManager of the active stack management server. For details, see Starting up the WebManager of EXPERSSCLUSTER X 3.3 for Linux Installation and Configuration Guide. 2. From the [View] menu on the screen, select [Operation Mode]. 3. From the [Service] menu on the screen, select [Stop Cluster]. For a mirror disk configuration, run [Stop Mirror Agent] in addition to [Stop Cluster]. 4. From the [View] menu on the screen, select [Config Mode]. 5. From the tree view on the left pane of the screen, select [Group] and delete group resources with the following names: fip disk (for a shared disk configuration) md (for a mirror disk configuration) exec 6. From the tree view on the left pane of the screen, select [Group] and delete a failover group. 7. From the tree view on the left pane of the screen, select [Server] and delete a server with the following name: server2 8. Apply the unconfigured cluster configuration data. From the [File] menu on the screen, run [Apply the Configuration File]. 23

30 Appendix A. Revision history Appendix A. Revision history The following lists the update history of the "Virtual DataCenter Automation Standard Edition Topology Template Orchestrator Option Cluster Configuration Guide". Number First edition Chapter/ Section Table A-1 Manual update history Details