Bug 1038475

Summary: RFE: Include the "gluster-deploy-tool" as part of the unsupported toolset
Product: Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: redhat-storage-serverAssignee: Bala.FA <barumuga>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: barumuga, dpati, dtsang, grajaiya, knarra, mmahoney, pcuzner, pprakash, psriniva, sdharane, ssampat, vagarwal
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: redhat-storage-server-2.1.2.0-3.el6rhs Doc Type: Enhancement
Doc Text:
Enhancements were made to add the gluster-deploy tool as an unsupported tool in Red Hat Storage Server. This tool eases the first time setup of the Red Hat Storage node and reduces the steps that need to be run manually.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 08:07:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Prasanth 2013-12-05 07:46:47 UTC
Description of problem:

Red Hat Storage Console (RHS-C) currently lacks a tool/plugin that helps the user to detect candidate (unused) disks, format disks as bricks, mount them, etc. This leaves the admins at a disadvantage when creating a brick as part of volume creation. They will have to go to the RHS servers and perform these tasks manually and keep the bricks ready (xfs formatted & mounted) before proceeding with creating volume from the UI. 

Paul Cuzner has developed a gluster-deploy tool [1] which now provides the following:

- detect gluster nodes
- create cluster
- distribute ssh keys 
- detect candidate (unused) disks 
- format disks as bricks, and mount them

Since developing a new plugin with this feature or integrating the gluster-deploy tool with RHS-C is not practically possible at this stage, as we are very close to code freeze, this BZ proposes the inclusion of the gluster-deploy tool to be part of the unsupported toolset shipped with RHS 2.x. Having this tool as part of RHS provide an option to the user for creating/formatting/mounting bricks, if required.

[1] https://forge.gluster.org/gluster-deploy/gluster-deploy

Comment 1 Bala.FA 2013-12-10 10:03:55 UTC
patch is under review at https://code.engineering.redhat.com/gerrit/17140

Comment 2 Gowrishankar Rajaiyan 2013-12-12 13:41:18 UTC
why priority and severity is "high" for this bug?

Comment 3 Prasanth 2013-12-18 13:29:38 UTC
Verified in redhat-storage-server-2.1.2.0-2.el6rhs

gluster-deploy-tool is available in: /usr/lib/glusterfs/.unsupported/gluster-deploy-0.3

[root@vm10 gluster-deploy-0.3]# pwd
/usr/lib/glusterfs/.unsupported/gluster-deploy-0.3
[root@vm10 gluster-deploy-0.3]# ll
total 260
-rw-r--r-- 1 root root   2396 Dec 12 11:24 changelog
drwxr-xr-x 2 root root   4096 Dec 18 18:09 functions
-rw-r--r-- 1 root root  11540 Dec 18 18:56 gluster-deploy.log
-rwxr-xr-x 1 root root  18837 Dec 12 11:24 gluster-deploy.py
-rw-r--r-- 2 root root  13684 Dec 12 11:24 gluster-deploy.pyc
-rw-r--r-- 2 root root  13684 Dec 12 11:24 gluster-deploy.pyo
-rw-r--r-- 1 root root   1253 Dec 12 11:24 index.html
-rw-r--r-- 1 root root 162863 Dec 12 11:24 planning.ep
-rw-r--r-- 1 root root   1403 Dec 12 11:24 README.md
drwxr-xr-x 2 root root   4096 Dec 18 18:09 screenshots
drwxr-xr-x 2 root root   4096 Dec 18 18:09 scripts
-rw-r--r-- 1 root root   1059 Dec 12 11:24 todo-list
drwxr-xr-x 2 root root   4096 Dec 18 18:09 utils
drwxr-xr-x 6 root root   4096 Dec 18 18:09 www

Comment 4 Pavithra 2014-01-15 09:38:14 UTC
Bala,

Can you please verify the doc text for technical accuracy?

Comment 5 Bala.FA 2014-01-15 10:50:27 UTC
Doc text looks good to me

Comment 6 Bala.FA 2014-01-20 08:19:07 UTC
updated gluster-deploy tool in redhat-storage-server-2.1.2.0-3.el6rhs

Comment 8 errata-xmlrpc 2014-02-25 08:07:48 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html