Bug 1263751 - [RFE] configurable labels/names for snapshots exposed in .snaps
[RFE] configurable labels/names for snapshots exposed in .snaps
Status: NEW
Product: GlusterFS
Classification: Community
Component: snapshot (Show other bugs)
All All
medium Severity medium
: ---
: ---
Assigned To: bugs@gluster.org
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-09-16 11:13 EDT by Alastair Neil
Modified: 2018-01-29 21:19 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alastair Neil 2015-09-16 11:13:23 EDT
Description of problem:
Currently snapshots are created with a name and an optional timestamp. There is no facility to rename snapshots as far as I can see.  

As is providing self service restore to users via uss is hard becuase the users need to parse the snap shot time stamp to locate the specific snapshot they want amongst a list of very similar names.

If the snap shots had associated lables that could be changed and these lables were exposed in .snaps, a flexible system could be set up ( similar to the timeslider autosnap feature in zfs).

if snapshots are scheduled regularly, for example:

frequent     snapshots every 15 mins, keeping 4 snapshots
hourly	     snapshots every hour, keeping 24 snapshots
daily	     snapshots every day, keeping 31 snapshots
weekly	     snapshots every week, keeping 7 snapshots
monthly	     snapshots every month, keeping 12 snapshots.
They could have labels like:  "Now", "Fifteen Minutes Ago",  "Thirty Minutes Ago", "Sunday", "Last Week" etc.

As the labels are able to be changed, they can be rotated as necessary.

Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
Actual results:
Expected results
Additional info:

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