Bug 865487

Summary: FutureFeature:Validate brick settings when creating volumes
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Paul Cuzner <pcuzner>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED DUPLICATE QA Contact: storage-qa-internal <storage-qa-internal>
Severity: low Docs Contact:
Priority: medium    
Version: 2.0CC: rhs-bugs, vbellur
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-23 11:36:13 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:
Embargoed:

Description Paul Cuzner 2012-10-11 14:56:35 UTC 
Description of problem:
Bricks added to the cluster should be validated prior to being eligible as a subvolume. Request comes from an existing RHEL customer currently looking at a storage refresh, and are keen to minimise the potential of operational administration issues.



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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
when you add a brick for management, the bricks sizes should be compared, as well as indoe settings and alloc parameters to ensure all settings are best practice.

Additional info:
Comment 3 Sahina Bose 2015-01-23 11:36:13 UTC 

*** This bug has been marked as a duplicate of bug 845191 ***