What's in this guide?
In this article you will find a quick guide on how to deploy a cluster in a redBorder Manager.
Before starting with the guide, it is convenient to know what is referred to when talking about cluster. The term cluster applies to groups or conglomerates of computers normally linked together by a high-speed network and which behave as if they were a single computer.
Each machine must be fitted with 2 network adapters minimum (Management and Sync).
That is why this guide will be separated into 2 parts. The first refers to the master machine, and the second to the slave machine.
The first step you must follow is to set the keyboard layout to the desired one (in this case Spanish layout) and then run the rb_sysconf command to access the configurator.
It is convenient to use the wizard. To do this, you must select the w option.
When prompted, you will have to select the cluster mode (2) and then insert the hostname for this machine and the cluster domain. In this case the hostname is master and the domain is rbtest.cluster.
In this part you must set the DNS servers. These can be public (like 22.214.171.124 and 126.96.36.199 by Google) or private in case of a client deploy (in this case it should be asked for them).
Then you set the ntp server. Let it be default or, in case of a client deploy that has a ntp server, it should be asked.
The next step will be to configure the management network:
For this it will be necessary to configure the sync network:
In this case no remotes will be used. You select y to proceed:
The first step is to set the keyboard layout to the desired one (in this case Spanish layout) and run the rb_sysconf command to access the configurator.
Now you must configure the network settings:
And also configure the DNS and domain:
It is convenient that you run the wizard and you configure it like the other manager:
After completing, go to System configuration and select option 3 and set the sync IP of the master manager:
Then, you select the cluster node option. In this case, 1 (master-slave):
And then, it will ask for confirmation. The asked password is the root password of the master manager.
Finally you should only make a series of additional checks:
1. Check the cluster members in the motd:
2. Check the services in all members with rb_get_services.sh all command:
After having performed all the steps outlined in the guide, you should be able to view similar data in the manager of the master to those shown in the image: