* Fixes#38174: Add remove-brick operation for gluster_volume
Existing gluster_volume module does not support removal of bricks
from a gluster volume. Also, operation remove-brick needs to be
followed by a commit operation.
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add documentation for remove-brick operation
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add support to reduce cluster configuration.
An exceptional scenario exists where the user might want to
reduce the gluster cluster configuration for replicated
volumes from replica 3 to replica 2 that need to be handled
in a different manner than the generic gluster commands,
where the user is expected to mention the replica count
of the new configuration in order to remove the bricks.
Signed-off-by: Devyani Kota <dkota@redhat.com>
* Updates #38174: Add checks for self-heal status prior remove operation.
While reducing the cluster configuration from replica 3
to 2, it needs to be checked for status of self-heal
prior remove-brick operation is executed.
Signed-off-by: Devyani Kota <dkota@redhat.com>
When a non-existent Gluster volume is to be deleted, i.e.:
gluster_volume:
state: absent
name: vol1-does-not-exist
the "gluster_volume" module would always fail with "volume not found
vol1-does-not-exist". The reason is that the code checked whether the
state is "delete", a value which isn't accepted for the "state"
parameter. Instead the expected value for volume deletion is, as above,
"absent".
Devyani Kota
hansmi
Sloane Hertel
Brian Coca