Bug 1028130 - Permit setting options (specifically nfs.disable) on volume creation
Summary: Permit setting options (specifically nfs.disable) on volume creation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.4.1
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 17:50 UTC by Rick
Modified: 2013-11-07 18:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-07 18:08:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Rick 2013-11-07 17:50:34 UTC
Feature request: permit setting volume options during `gluster volume create`

Background:

I use GlusterFS in native (fuse) mode only.  I also have nfsd running on the same machine, handling a completely different filesystem for export.  As such, I need gluster's NFS options disabled for all volumes so gluster won't takeover tcp/2049 unnecessarily.  The current situation involves me creating a volume using `gluster volume create ...`, and then having to say `gluster volume <volname> options nfs.disable true` immediately after.

Ideally, I'd be able to set some options during `gluster volume create`.  I'm fairly sure that NFS capability is enabled by default.

Comment 1 Rick 2013-11-07 18:08:43 UTC
So, with help from #gluster, I now know that the default options don't take effect until `gluster volume start`.  Wish I had thought of that earlier.

So the workflow looks like this:

`gluster volume create ...`
`gluster volume set ...`
`gluster volume start ...`

So, no need to complicate the CLI any further.


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