Bug 1543257

Summary:	[RFE] Gdeploy: Support for expand cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	gdeploy	Assignee:	Ramakrishna Reddy Yekulla <rreddy>
Status:	CLOSED NOTABUG	QA Contact:	Manisha Saini <msaini>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.4	CC:	amukherj, bugs, rcyriac, rhs-bugs, sabose, sasundar, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-13 09:30:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1523598

Description Gobinda Das 2018-02-08 05:37:16 UTC

Description of problem:
 Currently "Expand Cluster" feature is not supported by Gdeploy. Now we are coming up with expand cluster feature via cockpit, cockpit will create gdeploy configurations for "expand cluster" which will be invoked by gdeploy to complete the feature.

Version-Release number of selected component (if applicable):


How reproducible:
 Always

Steps to Reproduce:
1.
2.
3.

Actual results:
 Gdeploy does not support expand cluster

Expected results:
Gdeploy should support expand cluster feature.

Additional info:

Comment 2 Sahina Bose 2018-02-08 05:47:24 UTC

gdeploy needs to support adding nodes to existing cluster.

Comment 3 Gobinda Das 2018-02-13 09:29:00 UTC

Discussed with sas and came to know that gdeploy supports "peer probe" feature.

We should have following entries in gdeploy conf file:

[hosts]
current-host(host where currently cockpit running)
newhost1
newhost2
newhost3

[peer]
action=probe

Comment 4 Sahina Bose 2018-02-13 09:30:53 UTC

Closing this as per Comment 3.

Comment 5 SATHEESARAN 2018-02-16 16:44:47 UTC

Resetting the dev_ack on this bug