Bug 1518345

Summary:	[RFE] Asymmetric brick configuration
Product:	[oVirt] cockpit-ovirt	Reporter:	SATHEESARAN <sasundar>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	0.10.8-2.2	CC:	bugs, rhs-bugs, sabose, ylavi
Target Milestone:	ovirt-4.2.2	Keywords:	FutureFeature
Target Release:	---	Flags:	sasundar: ovirt-4.2? sasundar: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1518344	Environment:
Last Closed:	2018-04-05 09:39:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1518344

Description SATHEESARAN 2017-11-28 16:43:12 UTC

+++ This bug was initially created as a clone of Bug #1518344 +++

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.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-11-28 11:41:56 EST ---

This bug is automatically being proposed for the current release of Red Hat Hyperconverged Infrastructure (RHHI) under active development, by setting the release flag 'rhhi‑1.1.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 1 Sahina Bose 2017-12-04 07:05:31 UTC

*** Bug 1518504 has been marked as a duplicate of this bug. ***

Comment 3 SATHEESARAN 2018-04-04 11:59:21 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 4 Sandro Bonazzola 2018-04-05 09:39:40 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.