Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1518344

Summary: [RFE] Asymmetric brick configuration
Product: Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: Mugdha Soni <musoni>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhi-1.1CC: rcyriac, rhs-bugs, sabose
Target Milestone: ---   
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Previous versions of RHHI for Virtualization expected each virtualization host to be set up the same way, with the same device types and device names on each. As of version 2.0, you can specify different device and sizes as appropriate for each host, size arbiter bricks appropriately, and specify an SSD to use as a LVM cache logical volume.
Story Points: ---
Clone Of:
: 1518345 1518504 1590636 (view as bug list) Environment:
Last Closed: 2018-11-08 05:37:25 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: 1518345, 1518504    
Bug Blocks: 1520833, 1548985    

Description SATHEESARAN 2017-11-28 16:41:51 UTC
Description of problem:
-----------------------
Cockpit provides option to configure bricks exactly the same way on all the nodes. Example is that the brick could be created from sdb on all the nodes.

If the user wanted to make use of sdb from node1, sdc from node2, and sdd from node3. Then this is not possible with the existing cockpit.

Specifically this requirement becomes essential when arbitrated replicate volume is chosen. Arbitrated replicate volume requires the arbiter brick could be placed on the disk which has less storage space.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
cockpit-ovirt-dashboard-0.10.9

How reproducible:
-----------------
Not Applicable

Steps to Reproduce:
-------------------
1. Start with the installation of RHHI deployment
2. Choose arbitrated replicate volume for 'data' and 'vmstore' volume

Actual results:
----------------
Cockpit limits the user to create bricks symmetrically on the all nodes. 
If 'sdb' is chosen, bricks are created on 'sdb' on all the nodes

Expected results:
-----------------
Asymmetric brick configuration should be allowed for users to create bricks on specific disks

Additional info:
-----------------
With this limitation in place, the users can solve this problem by editing the generated gdeploy configuration. But again this is error prone and hard to edit the generated gdeploy configuration file.

Comment 4 SATHEESARAN 2018-04-04 11:59:41 UTC
Tested with RHV-4.2.2-6 and cockpit-ovirt-dashboard-0.11.19

Bricks could be created asymmetrically on the 3 hosts. For eg. sdb from host1, sdc from host2, sde from host3 could be used for creating gluster volumes

Comment 5 Mugdha Soni 2018-04-17 06:18:48 UTC
Tested with the following-:

1. RedHat-release-virtualization-host-4.2-2.1.el7.x86_64
2. Cockpit-ovirt-dashboard-0.11.20-1

Bricks could be created asymmetrically on the 3 hosts. Following were the steps performed to test:-

1. Logged in to the cockpit UI and configured the brick tab.

2. Under subtab brick configuration , bricks were created asymmetrically.For eg. 
   sdb on host1 , sdc on host2 and sdc on host3 could be used for creating gluster 
   volume.
3. Gluster volumes were successfully created.

Comment 10 errata-xmlrpc 2018-11-08 05:37:25 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-2018:3523