Manage GlusterFS pool.
Add brick(s) to an existing volume
Volume name
List of bricks to add to the volume
myvolume:
glusterfs.add_volume_bricks:
- bricks:
- host1:/srv/gluster/drive1
- host2:/srv/gluster/drive2
Replicated Volume:
glusterfs.add_volume_bricks:
- name: volume2
- bricks:
- host1:/srv/gluster/drive2
- host2:/srv/gluster/drive3
New in version 2019.2.0.
Add brick(s) to an existing volume
Volume name
myvolume:
glusterfs.max_op_version:
- name: volume1
- version: 30707
New in version 2019.2.0.
Add brick(s) to an existing volume
Volume name
Version to which the cluster.op-version should be set
myvolume:
glusterfs.op_version:
- name: volume1
- version: 30707
Check if node is peered.
The remote host with which to peer.
peer-cluster:
glusterfs.peered:
- name: two
peer-clusters:
glusterfs.peered:
- names:
- one
- two
- three
- four
Check if volume has been started
name of the volume
mycluster:
glusterfs.started: []
Ensure that the volume exists
name of the volume
list of brick paths
replica count for volume
use every third brick as arbiter (metadata only)
New in version 2019.2.0.
ensure that the volume is also started
myvolume:
glusterfs.volume_present:
- bricks:
- host1:/srv/gluster/drive1
- host2:/srv/gluster/drive2
Replicated Volume:
glusterfs.volume_present:
- name: volume2
- bricks:
- host1:/srv/gluster/drive2
- host2:/srv/gluster/drive3
- replica: 2
- start: True
Replicated Volume with arbiter brick:
glusterfs.volume_present:
- name: volume3
- bricks:
- host1:/srv/gluster/drive2
- host2:/srv/gluster/drive3
- host3:/srv/gluster/drive4
- replica: 3
- arbiter: True
- start: True