Sachidananda Urs

@kristvanbesien @johnsimcall earlier there was a requirement that backend-reset had to be kept separate since it is destructive operation. And had to be run separately. However, now I see that...

Martin it does. The initial design once upon a time was to do backend-setup first, irrespective of whereever it was listed in the config file. However it does not make...

Hi @ShyamsundarR the backend-rest works for me. These are the variables used in group_vars/all : ``` lvs: - GLUSTER_lv1 - GLUSTER_lv2 master: 10.70.42.122 mountpoints: - /gluster/brick1 - /gluster/brick2 pvs: -...

@ShyamsundarR this worked too: ``` --- - hosts: gluster_servers remote_user: root gather_facts: no tasks: - name: Cleans up backend backend_reset: pvs="{{ item }}" unmount="yes" with_items: - /dev/vdb - /dev/vdc ```

@mbukatov the current design is the brick_dirs are passed to gluster as is. And gluster takes care of creating brick directories. gdeploy creates only mount points. The reason is, since...

@mbukatov you are right about `brick_dirs=` option being a confusion in backend_setup section. So, initially we had brick_dirs in backend-setup and when `[volume]` section was mentioned it would use this...

@tsailiming @johnsimcall Ack! I will fix this.

@tsailiming @johnsimcall latest master updates to gdeploy should fix this. Please find example configuration at: https://github.com/gluster/gdeploy/blob/master/examples/geo-replication.conf You can find more example configuration files at: https://github.com/gluster/gdeploy/tree/master/examples

Ack! Will add this.

Commit: https://github.com/gluster/gdeploy/pull/393/commits/9ec1c08aec fixes the issue.