This section describes how to create the virtual system for the cluster system in RHOSP environment.
See
For how to set up RHOSP, refer to the RHOSP manual of Red Hat, Inc.
Use the setting values below to create the user on RHOSP for forcibly shutting down the virtual machines configuring the cluster system.
Item name | Setting value |
---|---|
User name | Any user name |
Project | Project in which the virtual machine is created |
Role | admin |
Create the public LAN (also used as the administrative LAN), subnets such as the cluster interconnect, and the security groups.
1. Creating Provider Network
Create the provider network and connect the virtual instance to the external network directly.
Use the setting values below to create the subnets used by the cluster system in the public LAN (also used as the administrative LAN) and those used by the cluster interconnect.
Item name | Setting value |
---|---|
Existence of automatic assignment by DHCP | true (default) |
IP address assignment pool | The range of IP addresses assigned to each node (The takeover IP addresses are excluded from the range.) |
To communicate with various service end points of RHOSP from the virtual machine, connect to the subnets of public LAN (also used as the administrative LAN).
2. Creating Security Group for Public LAN (also used as Administrative LAN)
Set IP filter rules necessary for the PRIMECLUSTER operations to the security group for the public LAN (also used as the administrative LAN).
Use the setting values below.
Communication direction | Communication target | Protocol information | Start port number | End port number |
---|---|---|---|---|
egress | Not specified | tcp | 443 | 443 |
ingress | Local security group | udp | 9382 | 9382 |
egress | Local security group | udp | 9382 | 9382 |
ingress | Local security group | udp | 9796 | 9796 |
egress | Local security group | udp | 9796 | 9796 |
ingress | Local security group | tcp | 9797 | 9797 |
egress | Local security group | tcp | 9797 | 9797 |
egress | Virtual gateway IP address | icmp | Not specified | Not specified |
ingress | Local security group | tcp | 3260 | 3260 |
egress | Local security group | tcp | 3260 | 3260 |
ingress | Client IP address (*) | tcp | 8081 | 8081 |
ingress | Client IP address (*) | tcp | 9798 | 9798 |
ingress | Client IP address (*) | tcp | 9799 | 9799 |
ingress | Local security group | tcp | 9200 | 9263 |
egress | Local security group | tcp | 9200 | 9263 |
(*) If multiple clients connect to Web-Based Admin View, register IP addresses of all of the connected clients.
When building multiple cluster systems in the same tenant (project), create only one security group in the tenant (project). The security group can be used for the multiple cluster systems in the same tenant (project).
3. Creating Security Group for Cluster Interconnect
Set IP filter rules necessary for the PRIMECLUSTER operations to the security group for the cluster interconnect.
Use the setting values below.
Communication direction | Communication target | Protocol information | Start port number | End port number |
---|---|---|---|---|
egress | Local security group | 123 | Not specified | Not specified |
ingress | Local security group | 123 | Not specified | Not specified |
When building multiple cluster systems in the same tenant (project), create only one security group in the tenant (project). The security group can be used for the multiple cluster systems in the same tenant (project).
4. Setting Other Security Group
Set the security group including IP filter rules necessary for the PRIMECLUSTER installation, maintenance, or operations in the cluster system. Set these IP filter rules based on operation requirements of network services working in or out of the cluster system.
Use the setting values for DNS, NTP, or ssh.
Communication direction | Communication target | Protocol information | Start port number | End port number |
---|---|---|---|---|
ingress | ssh client IP address | tcp | 22 | 22 |
egress | DNS server IP address | udp | 53 | 53 |
egress | NTP server IP address | udp | 123 | 123 |
Note
When the yum command is used, use the setting values below.
Communication direction | Communication target | Protocol information | Start port number | End port number |
---|---|---|---|---|
egress | Repository IP address | tcp | 80 | 80 |
Create server groups appropriate to the cluster type.
Item name | Setting value |
---|---|
Server group name | Any server group name |
Server group behavior* | anti-affinity (for the cluster system between guest OSes on multiple compute nodes) |
* soft-affinity and soft-anti-affinity can also be set. However, it is not recommended because the compute node in which the guest OS is working may change at startup of the guest OS. If soft-affinity or soft-anti-affinity is set, be aware that the server group may work in a different configuration other than "Cluster type" selected in "I.1 Cluster System in RHOSP Environment."
Note
When creating multiple cluster systems, each cluster system needs its own server group.
Create the virtual machine for cluster node.
Perform the following operations for each node configuring the cluster node to create the virtual machine for cluster node.
Creating Port for Public LAN (also used as the administrative LAN)
Creating Port for Cluster Interconnect
Creating Virtual Machine
Connecting Storage Device (iSCSI connection) or Block Storage
Applying errata
Creating .curlrc
1. Creating Port for Public LAN (also used as administrative LAN)
Use the setting values below to set the port for public LAN (also used as the administrative LAN) of virtual machine configuring the cluster system.
Item name | Setting value |
---|---|
Port name | Any port name |
Network ID | Network ID |
Subnet ID | Subnet ID for the public LAN (also used as administrative LAN) created in "1. Creating Provider Network" |
Private IP address | IP address of the public LAN (also used as administrative LAN) |
ID list of security group | - Security group ID created in "2. Creating Security Group for Public LAN (also used as Administrative LAN)" |
Takeover IP address | IP address of taking over between nodes |
2. Creating Port for Cluster Interconnect
Use the setting values below to set the port for cluster interconnect of virtual machine configuring the cluster system.
Item name | Setting value |
---|---|
Port name | Any port name |
Network ID | Network ID |
Subnet ID | Subnet ID for the cluster interconnect created in "1. Creating Provider Network" |
Private IP address | IP address of the cluster interconnect |
ID list of security group | Security group for the cluster interconnect created in "3. Creating Security Group for Cluster Interconnect" |
3. Creating Virtual Machine
Use the setting values below to set the virtual machine configuring the cluster system.
Item name | Setting value |
---|---|
Virtual machine name | Any virtual machine name * Do not specify a duplicate virtual machine name in the same project. |
Virtual machine type | Flavor ID of any virtual machine type appropriate to performance requirements |
OS image | Red Hat Enterprise Linux 6.x (for Intel64) |
Keypair name | Key pair necessary for ssh login to virtual machine |
Port ID | Port ID (eth0) created in "1. Creating Port for Public LAN (also used as administrative LAN)" Port ID (eth1) created in "2. Creating Port for Cluster Interconnect" |
Security group | Not specified (already specified in the port) |
Auto-failover | Disabled |
Server group ID | Server group ID created in "I.2.2.3 Creating Server Group" |
Minimum number of servers | 1 |
Maximum number of servers | 1 |
Availability zone | Availability zone in which the virtual machine is located |
4. Connecting Storage Device (iSCSI connection) or Block Storage
When using the shared disk
Connect the shared disk device of iSCSI connection to the virtual machine.
When using the GDS mirroring among servers function
Attach the block storage provided by the OpenStack Block Storage service (cinder) to the virtual machine.
Attach the block storage with the same capacity to each virtual machine.
When using the GDS local class
Connect the storage device (iSCSI connection) to the virtual machine.
See
For how to connect the iSCSI device to the virtual machine, refer to "Red Hat Enterprise Linux 6 Storage Administration Guide" or "Red Hat Enterprise Linux 7 Storage Administration Guide."
5. Applying errata
Execute the following command to check the version of curl.
# rpm -q curl
Example
# rpm -q curl
curl-7.19.7-52.el6.x86_64
If the version of curl is 7.19.7-43 or older, apply errata to update the curl package to its latest version.
6. Creating .curlrc
Add the following line to the /root/.curlrc file. If there is no file, create it and describe the following line.
tlsv1.2
If the file is created, perform the following items.
# chown root:root /root/.curlrc # chmod 600 /root/.curlrc