Bug 1774852

Summary:	Adding support to create gluster volumes for specific nodes from ansible roles
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.4	CC:	akrishna, asriram, bkunal, mkalinin, pprakash, puebele, rcyriac, rhs-bugs, sabose, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Batch Update 1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.5-7.el7rhgs,gluster-ansible-features-1.0.5-5.el7rhgs	Doc Type:	Enhancement
Doc Text:	Previously, in a standard RHHI deployment, all gluster volumes are created on all nodes and there is no way to specify volumes for specific nodes. With this update, the user has to create separate volumes when you have six or more and specify which nodes the gluster volumes need to be created.	Story Points:	---
Clone Of:	1774851	Environment:
Last Closed:	2020-01-30 06:45:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1774851, 1788914

Description Gobinda Das 2019-11-21 06:12:03 UTC

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:

Comment 1 Gobinda Das 2019-11-21 06:15:01 UTC

PR: https://github.com/gluster/gluster-ansible-features/pull/34

Comment 2 SATHEESARAN 2019-12-30 12:17:00 UTC

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)

Comment 4 Gobinda Das 2020-01-23 13:50:30 UTC

doc_text provided.

Comment 5 Anjana KD 2020-01-29 17:36:20 UTC

Have updated the doc text in the doc text field, kindly review it.

Comment 6 Gobinda Das 2020-01-30 04:48:59 UTC

Hi Anjana,
 RDT looks good to me.

Comment 8 errata-xmlrpc 2020-01-30 06:45:36 UTC

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