Description of problem: Now gluster ansible roles only support to create gluster volumes across all nodes, but incase of 6 nodes usecase if user wants to create some volume in 3 nodes and other volumes in other nodes then it's not possible now. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Should have way to create volume for specific nodes Additional info:
PR: https://github.com/gluster/gluster-ansible-features/pull/34
Tested with gluster-ansible-roles-1.0.5-7 and gluster-ansible-features-1.0.5-5 with following steps. node{1..6} were used. Bricks for engine volume are created on node{1,2,3} Bricks for vmstore & data are created on node{4,5,6| [root@ ~]# gluster volume info | grep -i brick Number of Bricks: 1 x 3 = 3 Bricks: Brick1: node10.test.com:/gluster_bricks/data/data Brick2: node11.test.com:/gluster_bricks/data/data Brick3: node12.test.com:/gluster_bricks/data/data Number of Bricks: 1 x 3 = 3 Bricks: Brick1: node7.test.com:/gluster_bricks/engine/engine Brick2: node8.test.com:/gluster_bricks/engine/engine Brick3: node9.test.com:/gluster_bricks/engine/engine Number of Bricks: 1 x (2 + 1) = 3 Bricks: Brick1: node10.test.com:/gluster_bricks/vmstore/vmstore Brick2: node11.test.com:/gluster_bricks/vmstore/vmstore Brick3: node12.test.com:/gluster_bricks/vmstore/vmstore (arbiter)
doc_text provided.
Have updated the doc text in the doc text field, kindly review it.
Hi Anjana, RDT looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0289