Bug 1406916 - RFE for setting multiple gluster options
Summary: RFE for setting multiple gluster options
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-21 20:17 UTC by Cal Calhoun
Modified: 2020-04-15 15:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-30 01:31:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Cal Calhoun 2016-12-21 20:17:54 UTC
Description of problem:

From the customer:

  It might be useful to have an option to set multiple options with one gluster volume set <something> command.
 
  For example: # gluster volume set option1 value option2 value2 option3 value3

  Or: 

  # gluster volume set volume1,volume2,volume3 option1 value1 option2 value2 option3 value3 (set all 3 options an all listed volumes)

  Or:

  # gluster volume set allvols option1 value1 option2 value2 option3 value3 (set options on all volumes present in storage pool)

Comment 8 Cal Calhoun 2017-03-09 14:49:54 UTC
@atin: From the customer:

>I really like the idea of having volume groups: volume set group. Is this already >in upstream (3.9) or glusterd 2.0 devel??
>
>I understand that developers would like to keep cli commands atomic, do not do >multiple actions with one command. Make sense. Using volume groups above looks >like a better way to achieve expected behaviour. 
>
>Assigning volumes to groups (with defined options) would also solve setting >default options to newly created volumes. This can be achieved by having a >'default' group assigned by default to new volumes.
>
>Please ask developers to  focus on volume groups concept. It will solve all RFE's >mentioned in this case.

Comment 10 Cal Calhoun 2017-03-29 15:00:37 UTC
The customer case 01761085 has been closed.  Feel free to close this BZ.


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