Bug 865487 - FutureFeature:Validate brick settings when creating volumes
Summary: FutureFeature:Validate brick settings when creating volumes
Keywords:
Status: CLOSED DUPLICATE of bug 845191
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-11 14:56 UTC by Paul Cuzner
Modified: 2015-05-13 18:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-23 11:36:13 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.