Bug 1330026

Summary: There's no gdeploy standard template for ROBO
Product: Red Hat Gluster Storage Reporter: Bhaskarakiran <byarlaga>
Component: gdeployAssignee: Sachidananda Urs <surs>
Status: CLOSED ERRATA QA Contact: Bhaskarakiran <byarlaga>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: asrivast, mzywusko, nvarma, rhinduja, sasundar, surs
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdeploy-2.0-13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 05:30:18 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: 1334705    
Bug Blocks: 1258386, 1311817    

Description Bhaskarakiran 2016-04-25 10:12:02 UTC
Description of problem:
======================

Currently there are sample files which are being used and we are building up the conf file based on the steps to build a ROBO environment. This doesn't standardize the way things are done. We need a standard template which can be used by all to setup the environment. This bug is for the same.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Sachidananda Urs 2016-05-05 08:42:57 UTC
Added sample configuration file named hc.conf into examples/ directory.
When installed the file can be found in: /usr/share/doc/gdeploy/examples/

Comment 4 SATHEESARAN 2016-05-06 05:22:18 UTC
the hc.conf file creates the volume with 'force' option.
I would recommend to remove 'force'd volume creation in the template.

Comment 5 SATHEESARAN 2016-05-06 05:33:35 UTC
(In reply to SATHEESARAN from comment #4)
> the hc.conf file creates the volume with 'force' option.
> I would recommend to remove 'force'd volume creation in the template.

Also note that rdma is not required for RHEV-RHGS HCI deployment, so volume transport should be only 'tcp'

Comment 6 SATHEESARAN 2016-05-06 05:37:48 UTC
I am consolidating all the comments here
1. Remove volume creation with force under [volume]section (i.e) force=yes
2. Remove volume transport rdma (i.e) transport=rdma,tcp
3. Registering the systems to CDN, enabling repos, installing rpms should be the first task before editing multipath.conf

Comment 7 Sachidananda Urs 2016-05-06 09:54:11 UTC
(In reply to SATHEESARAN from comment #6)
> I am consolidating all the comments here
> 1. Remove volume creation with force under [volume]section (i.e) force=yes
> 2. Remove volume transport rdma (i.e) transport=rdma,tcp
> 3. Registering the systems to CDN, enabling repos, installing rpms should be
> the first task before editing multipath.conf

Ack!

I've made these changes and available as part of 2.0-11

Comment 8 SATHEESARAN 2016-05-06 10:06:17 UTC
(In reply to Sachidananda Urs from comment #7)
> (In reply to SATHEESARAN from comment #6)
> > I am consolidating all the comments here
> > 1. Remove volume creation with force under [volume]section (i.e) force=yes
> > 2. Remove volume transport rdma (i.e) transport=rdma,tcp
> > 3. Registering the systems to CDN, enabling repos, installing rpms should be
> > the first task before editing multipath.conf
> 
> Ack!
> 
> I've made these changes and available as part of 2.0-11

Thanks Sac, We will check it out with this gdeploy

Comment 9 Bhaskarakiran 2016-05-11 11:53:36 UTC
The sample conf (hc.conf) which is there in the latest build gdeploy-2.0-11 has to be re-arranged. Have sent the conf file to sac.

Comment 10 SATHEESARAN 2016-05-12 14:02:56 UTC
gdeploy-2.0-11 misses the additional script files which help in disabling the required gluster hooks scripts and multipath 

Bug 1334705 is filed for that issue.

Bug verification is blocked on the issue reported in bz 1334705

Comment 11 Sachidananda Urs 2016-05-13 11:50:58 UTC
Fixed the ordering. Fixed multipath issue.

Comment 12 Bhaskarakiran 2016-05-16 06:58:54 UTC
Sac,

The build is not attached to the errata. Could you pls attach the same.

Comment 13 Sachidananda Urs 2016-05-17 17:16:48 UTC
Bhaskar, it is attached kindly check.

Comment 14 Bhaskarakiran 2016-05-18 05:37:58 UTC
verified with the build and the conf file looks good. Marking this as fixed.

Comment 16 errata-xmlrpc 2016-06-23 05:30:18 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/RHEA-2016:1250