Bug 1214629 - RFE: Remove disperse-data option in the EC volume creation command
Summary: RFE: Remove disperse-data option in the EC volume creation command
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: ankit
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: qe_tracker_everglades 1224186
TreeView+ depends on / blocked
 
Reported: 2015-04-23 09:21 UTC by Bhaskarakiran
Modified: 2016-11-23 23:13 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
: 1224186 (view as bug list)
Environment:
Last Closed: 2016-10-13 16:48:19 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Bhaskarakiran 2015-04-23 09:21:44 UTC
Description of problem:
=======================

Currently there is disperse and disperse-data options that can be used during EC volume creation. This is creating confusion as to which one to be used. Remove disperse-data option to make it consistent.

Version-Release number of selected component (if applicable):
=============================================================
[root@vertigo rhs]# gluster --version
glusterfs 3.7dev built on Apr 18 2015 01:08:09
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.

[root@vertigo ~]# gluster volume create 
Usage: volume create <NEW-VOLNAME> [stripe <COUNT>] [replica <COUNT> [arbiter <COUNT>]] [disperse [<COUNT>]] **[disperse-data <COUNT>]** [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK>?<vg_name>... [force]

The one marked in the *'s should be removed.

Comment 2 Pranith Kumar K 2016-10-13 16:48:19 UTC
This is added based on the requests that people liked creating the volume using k, m in n=k+m equation of ec. So won't be fixing this.


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