RHSS: On-Premise Config Trusted pool

Add a Server to a trusted Pool

The master server is the first server in the trusted pool. Each other server that is going to be part of the pool must be probed from the master server. There is no need to probe the local host.

gluster peer probe <hostname | ip address>

Once the servers have been probed the list of peers can be checked:

[root@rhs-srv-1 ~]# gluster peer status

Number of Peers: 3

Hostname: rhs-srv-2.cloud.lab.eng.bos.redhat.com
Uuid: 2920376c-56a3-418d-96ed-ec538fc19b58
State: Accepted peer request (Connected)

Hostname: rhs-srv-3.cloud.lab.eng.bos.redhat.com
Uuid: 2c51f9fa-2ea0-4f6e-beea-3af925eba173
State: Peer in Cluster (Connected)

Hostname: rhs-srv-4.cloud.lab.eng.bos.redhat.com
Uuid: e8f5a479-f81e-48d9-8c87-ce9634984bf6
State: Peer in Cluster (Connected)

Configure a Distributed Volume

The trused volumer must then be configured into a distributed volume:

[root@rhs-srv-1 ~]# gluster volume create namespace_two \
transport tcp \
rhs-srv-1:/mnt/brick1 rhs-srv-2:/mnt/brick1 \
rhs-srv-3:/mnt/brick1 rhs-srv-4:/mnt/brick1
Creation of volume namespace_two has been successful. Please start the volume to access data.

Start the Volume

[root@rhs-srv-1 ~]# gluster volume status
Volume namespace_two is not started

[root@rhs-srv-1 ~]# gluster volume start namespace_two
Starting volume namespace_two has been successful