此内容没有您所选择的语言版本。
10.5. Setting up Geo-replication using gdeploy
This section describes how to use gdeploy to configure geo-replication, control and verify geo-replication sessions in your storage environment. The gdeploy tool automates the following processes related to geo-replication:
10.5.1. Setting up geo-replication as root user using gdeploy
Setting up a geo-replication session as a root user involves:
- Creating a common pem pub file
- Creating a geo-replication session
- Configuring the meta-volume
- Starting the geo-replication session
gdeploy helps in automating these tasks by creating a single configuration file. When gdeploy is installed, a sample configuration file is created in the following location:
/usr/share/doc/gdeploy/examples/geo-replication.conf
Procedure 10.1. Setting up geo-replication as root user using gdeploy
Important
Ensure that the prerequisites listed in Section 10.3.3, “Prerequisites” are complete.
- Create a copy of the sample gdeploy configuration file present in the following location:
/usr/share/doc/gdeploy/examples/geo-replication.conf
- Add the required details in the geo-replication section of the configuration file using the following template:
[geo-replication] action=create mastervol=Master_IP:Master_Volname slavevol=Slave_IP:Slave_Volname slavenodes=Slave_IP_1,Slave_IP_2
[Add all slave IP addresses. Each address followed by a comma (,)]force=yes[yes or no]start=yes[yes or no] - After modifying the configuration file, invoke the configuration using the command:
# gdeploy -c txt.conf
Following is an example of the modifications to the configuration file in order to set up geo-replication as a root user:
[geo-replication] action=create mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavesvolume slavenodes=10.1.1.28,10.1.1.86 force=yes start=yes
For more information on other available values, see Section 5.1.7, “Configuration File”
10.5.2. Setting up a secure geo-replication session using gdeploy
Setting up a secure geo-replication session involves:
- Creating a new group with a unprivileged account for all slave nodes
- Setting up the mountbroker
- Creating a common pem pub file
- Creating a geo-replication session
- Configuring the meta-volume
- Starting the geo-replication session
gdeploy helps in automating these tasks by creating a single configuration file. When gdeploy is installed, a sample configuration file is created in the following location:
/usr/share/doc/gdeploy/examples/georep-secure.conf
Procedure 10.2. Setting up a secure geo-replication session using gdeploy
Important
Ensure that the prerequisites listed in Section 10.3.3, “Prerequisites” are complete.
- Create a copy of the sample gdeploy configuration file present in the following location:
/usr/share/doc/gdeploy/examples/georep-secure.conf
- Add the required details in the geo-replication section of the configuration file using the following template:
[geo-replication] action=create georepuser=User_Name
[If the user is not present, gdeploy creates the geo-replication user.]mastervol=Master_IP:Master_Volname slavevol=Slave_IP:Slave_Volname slavenodes=Slave_IP_1,Slave_IP_2[Add all slave IP addresses. Each address followed by a comma (,)]force=yes[yes or no]start=yes[yes or no] - After modifying the configuration file, invoke the configuration using the command:
# gdeploy -c txt.conf
The following is an example of the modifications to the configuration file in order to set up a secure geo-replication session:
[geo-replication] action=create georepuser=testgeorep mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavesvolume slavenodes=10.1.1.28,10.1.1.86 force=yes start=yes
For more information on other available values, see Section 5.1.7, “Configuration File”
10.5.3. Controlling geo-replication sessions using gdeploy
gdeploy version 2.0.2-35 supports controlling geo-replication sessions on Red Hat Gluster Storage 3.5. Using gdeploy, the following actions can be performed for controlling a geo-replication session:
When gdeploy is installed, sample configuration files are created in
/usr/share/doc/gdeploy/examples. The sample configuration file names for each action are as follows:
| Geo-replication Session Control | Configuration File Name |
|---|---|
| Starting a session | georep-start.conf |
| Stopping a session | georep-stop.conf |
| Pausing a session | georep-pause.conf |
| Resuming a session | georep-resume.conf |
| Deleting a session | georep-delete.conf |
Procedure 10.3. Controlling geo-replication sessions using gdeploy
Warning
You must create a geo-replication session before controlling it. For more information, see any one of the following:
Important
Ensure that the prerequisites listed in Section 10.3.3, “Prerequisites” are complete.
- Create a copy of the required gdeploy sample configuration file present in the following location:
/usr/share/doc/gdeploy/examples
- Add the required information in the geo-replication section of the configuration file using the following template:
[geo-replication] action=Action_Name georepuser=User_Name
If georepuser variable is omitted, the user is assumed to be root user.mastervol=Master_IP:Master_Volname slavevol=Slave_IP:Slave_Volname slavenodes=Slave_IP_1,Slave_IP_2[Add all slave IP addresses. Each address followed by a comma (,)]force=yes[yes or no]start=yes[yes or no]Important
Ifgeorepuservariable is omitted, the user is assumed to be root user. - After modifying the configuration file, invoke the configuration using the command:
# gdeploy -c txt.conf
Following are the examples of the modifications to the configuration file in order to control a geo-replication session:
Starting a geo-replication session
[geo-replication] action=start mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavevolume
Stopping a geo-replication session
[geo-replication] action=stop mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavevolume force=yes
Pausing a geo-replication session
[geo-replication] action=pause mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavevolume force=yes
Resuming a geo-replication session
[geo-replication] action=resume mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavevolume force=yes
Deleting a geo-replication session
[geo-replication] action=delete mastervol=10.1.1.29:mastervolume slavevol=10.1.1.25:slavevolume force=yes
For more information on available values, see Section 5.1.7, “Configuration File”
