Bug 885861 - implement alias capability so more than one name can refer to the same volume
Summary: implement alias capability so more than one name can refer to the same volume
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 20:07 UTC by Shawn Heisey
Modified: 2014-12-14 19:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-14 19:40:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shawn Heisey 2012-12-10 20:07:52 UTC
Currently if you want to use gluster-swift with keystone, you have to name your volume after the 32 byte hex string that represents the tenant ID in keystone.  This means that you can't have a meaningful name for your volume.

A workaround would be to make it possible to create volume aliases, so you can use the meaningful name for the actual volume name and when mounting via /etc/fstab, but give it the 32-byte hex string as an alias, so gluster-swift can mount it that way.

I'm sure others can come up with other use-cases for this functionality as well.

Comment 1 Niels de Vos 2014-11-27 14:54:06 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.


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