Adding an Operations Database Replica Node

At this step we imply that you have CloudBlue Commerce installed and UI on top of a cluster or on a standalone node configured.

Requirements

You need to add Operations database replica nodes to your system. In case of UI on top of a cluster, you can choose from two options, add a single replica node for all web servers in the cluster on which you want to enable APS Booster, or add one replica node for each web server in the cluster. In case of UI on a standalone node, you need to add a single database replica node.

The database replica servers must meet the same requirements as the Operations database node:

Server Names	LINMNDB
Description	A Linux-based node that hosts the Operations database.
Density	500,000 accounts
Quantity	1
OS	RHEL 7.4 (x64) or higher CentOS 7.4 (x64) or higher
Software	To be installed by customer: OS only
CPU	4 core (2.4 GHz or higher) Important: Depending on the amount of CloudBlue Commerce accounts and users, the number of required physical cores may change: 6 physical cores for 50,000 accounts/250,000 users 7 physical cores for 100,000 accounts/500,000 users 8 physical cores for 200,000 accounts/1,000,000 users 8 physical cores for 300,000 accounts/1,500,000 users 9 physical cores for 400,000 accounts/2,000,000 users 10 physical cores for 500,000 accounts/2,500,000 users
RAM	Important: Depending on the amount of CloudBlue Commerce accounts and users, the amount of required RAM may change: 8 GB for 50,000 accounts/250,000 users 12 GB for 100,000 accounts/500,000 users 20 GB for 200,000 accounts/1,000,000 users 28 GB for 300,000 accounts/1,500,000 users 36 GB for 400,000 accounts/2,000,000 users 44 GB for 500,000 accounts/2,500,000 users
Disks	Array 1:
	OS and software	Important: Depending on the amount of CloudBlue Commerce accounts and users, the amount of required disk space may change: 3 x 260 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 50,000 accounts/250,000 users 3 x 320 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 100,000 accounts/500,000 users 3 x 440 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 200,000 accounts/1,000,000 users 3 x 560 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 300,000 accounts/1,500,000 users 3 x 680 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 400,000 accounts/2,000,000 users 3 x 800 GB, SCSI, SAN storage or RAID 5 (hardware impl.) with Battery Backup Unit for 500,000 accounts/2,500,000 users Note: in case you are going to use APS Booster, the node hosting master database needs extra 256 GB of free disk space for storing WAL files (16384 WAL files * 16 MB each).
Disk Partitioning	Array 1:
	/ - 5 GB	- for OS
	2 x RAM size (16 GB)	- swap
	/usr – at least 20 GB	- for software
	/var - remaining space	- for CloudBlue Commerce system database
NICs	BackNet Note: Bandwidth of at least 10 Gbps is required.

Important: Due to the security reasons, disable IPv6 support in backnet network interface properties on the CloudBlue Commerce management node, UI and branding nodes.
If you use a Virtuozzo container for deploying CloudBlue Commerce management node, UI or branding node, open the container configuration file - /etc/sysconfig/vz-scripts/<container_id>.conf - and remove the IPv6 support for the host-only interface. If you create a new container, make sure that IPv6 support for backnet network interface is not specified in the container creation parameters.
If CloudBlue Commerce management node, UI or branding node is deployed on a real physical server, disable the IPv6 support in backnet network interface using the standard functionality of the OS being installed. For instructions on how to do it, refer to the appropriate documentation of the server OS.

Registering database replicas in CloudBlue Commerce

To add a database replica node do the following:

Log in to Operations provider control panel.
Go to Infrastructure > Service Nodes and click Add New Node.
Pick the Generic Linux Node role for the node.
Enter the IP address or hostname, and the root password. If authentication via public key is configured for the host, you can provide the key instead of the password. Click Next.
Review the configuration and specify a custom host name for the host if needed. After that click Finish.
Wait for the scheduled tasks to complete.

Repeat these steps for every database replica host you want to register.

Authorizing replica nodes

After you register all the nodes, you need to authorize them to act as replicas. For this purpose, do the following:

Connect to the management node via SSH as root.
Add the hostnames of all replica nodes to the /root/auth_hosts file.

Next, you need to configure the database replica nodes.