Bug 1041583

Summary:	upstream gluster-hadoop packager needs README and new subdirectory logic.
Product:	[Community] GlusterFS	Reporter:	Jay Vyas <jvyas>
Component:	gluster-hadoop-install	Assignee:	Jeff Vance <jvance>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Bukatovic <mbukatov>
Severity:	low	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	eboyd, esammons, matt, mbukatov, mkudlej, shaines
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.62-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-03 16:32:55 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:
Bug Depends On:
Bug Blocks:	1057253

Description Jay Vyas 2013-12-12 18:05:46 UTC

We've decided that upstream glusterfs-hadoop installer needs

1) A more precise README, phrases such as: 
 - "the goal is to create..." 
 - "The tarball is downloaded to one of the cluster nodes or to the user's..."
 - "The tarball should contain...."

Are somewhat confusing.   The readme should clarify which tarball is being 
referenced.  Should we reference the tarball at all ?  I don't think so.

2) Once the fedora subfolder implementation of rhs-hadoop-install is close to 
complete, lets delete or deprecate 
https://github.com/jeffvance/glusterfs-cluster-install entirely to further 
simplify things.

Comment 1 Martin Bukatovic 2013-12-13 14:26:59 UTC

(In reply to Jay Vyas from comment #0)
> We've decided that upstream glusterfs-hadoop installer needs
> 
> 1) A more precise README, phrases such as: 
>  - "the goal is to create..." 
>  - "The tarball is downloaded to one of the cluster nodes or to the
> user's..."
>  - "The tarball should contain...."
> 
> Are somewhat confusing.   The readme should clarify which tarball is being 
> referenced.  Should we reference the tarball at all ?  I don't think so.

I agree here. Basically we need a new README written for the user who just installed the package. So far the README is written for another developer, so besides user centric stuff it also provides introduction to the structure of the git repository, development, packaging and so on (while most of those files are not provided by the package the user will use). 

To avoid duplication, I guess the README may be splitted into user and devel one, where only the user one will be packaged.

Comment 2 Jeff Vance 2014-01-09 17:09:02 UTC

version 0.54 attempts to address this concern.

Comment 4 Jeff Vance 2014-02-03 21:15:32 UTC

should be fixed in version 0.62-1

Comment 5 Martin Bukatovic 2014-02-04 10:15:17 UTC

(In reply to Jeff Vance from comment #4)
> should be fixed in version 0.62-1

Using rhs-hadoop-install-0_62-1.el6rhs.noarch