Bug 1569712 - [RFE] Add the ability to specify the snapshot name when running snap_scheduler.py
Summary: [RFE] Add the ability to specify the snapshot name when running snap_schedule...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot
Version: rhgs-3.3
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Mohammed Rafi KC
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-19 21:14 UTC by Andrew Robinson
Modified: 2018-11-19 05:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:03:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrew Robinson 2018-04-19 21:14:00 UTC
Description of problem:

A customer would like the ability to specify the name of the snapshots created by the snap_scheduler.py script. Currently, the script is run like this:

# snap_scheduler.py add "Job Name" "Schedule" "Volume Name"

The customer suggests a syntax such as this:

# snap_scheduler.py add "Job Name" "Schedule" "Volume Name" "Snapshot Name"

The customer also suggested preventing the time stamp from being added to the name:

# snap_scheduler.py add "Job Name" "Schedule" "Volume Name" "Snapshot Name" no-timestamp

The customer wants control over the name of the snapshots to make identifying them easier for scripts that mount the snapshots. 


Version-Release number of selected component (if applicable):

Red Hat Gluster Storage 3.3


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Mohammed Rafi KC 2018-11-19 05:03:31 UTC
This will be addressed in glusterd2, as we are rewriting snapshot scheduler in gd2 and only fixing major issues in 3.x series. The progress can be tracked the progress using the issue https://github.com/gluster/glusterd2/issues/1098.


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