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:
Added sample configuration file named hc.conf into examples/ directory. When installed the file can be found in: /usr/share/doc/gdeploy/examples/
the hc.conf file creates the volume with 'force' option. I would recommend to remove 'force'd volume creation in the template.
(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'
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
(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
(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
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.
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
Fixed the ordering. Fixed multipath issue.
Sac, The build is not attached to the errata. Could you pls attach the same.
Bhaskar, it is attached kindly check.
verified with the build and the conf file looks good. Marking this as fixed.
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