Bug 1207023

Summary:	[RFE] Snapshot scheduler enhancements (both GUI Console & CLI)
Product:	[Community] GlusterFS	Reporter:	Nagaprasad Sathyanarayana <nsathyan>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, rtalur, sabose, smohan
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-21 10:00:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nagaprasad Sathyanarayana 2015-03-30 05:27:56 UTC

Capturing the change requests from Bob Buckley (Red Hat).

1) On the CLI demo, @ 16:15 time, the "gluster snapshot list vol2" gives a list of snaps but does not seem to have any order to the list.  If a user searches and has many in the list to review, this will be better if sorted in time order.

2) When you referred to local time for the timestamps, just as a reference, many government systems use GMT as their "local" clock for continuity across the globe.  I suspect this would also apply to many global companies as well.

3) In the GUI console version change "Minutely, Hourly, etc." to "Minute, Hour, Day, Week, & Month".

4) In the GUI console version, the "Start at" and "Execution Time" are confusing.  Does this mean to start the job at 2020 and end the job at 2100 or is the "Start At" when the cron job is created and the "Execution Time" is the time at which it starts on the appointed interval?  Sorry, but this just is confusing.

Comment 1 Sahina Bose 2015-04-02 07:07:32 UTC

Logged the UI changes under oVirt component - Bug 1208388

Comment 2 Avra Sengupta 2015-05-07 11:22:57 UTC

Tracking dependency with ovirt scheduler with https://bugzilla.redhat.com/show_bug.cgi?id=1219442

Comment 3 Niels de Vos 2015-06-02 08:20:15 UTC

The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.

Comment 4 Niels de Vos 2015-06-20 10:07:53 UTC

Unfortunately glusterfs-3.7.2 did not contain a code change that was associated with this bug report. This bug is now proposed to be a blocker for glusterfs-3.7.3.

Comment 5 Avra Sengupta 2015-07-23 07:10:04 UTC

Points 1 and 2 are already taken care of. If Points 3 and 4 are also addressed, please close this bug.

Comment 6 Kaushal 2015-07-30 13:17:59 UTC

This bug could not be fixed in time for glusterfs-3.7.3. This is now being tracked for being fixed in glusterfs-3.7.4.

Comment 7 Kaushal 2015-10-28 12:28:49 UTC

This bug could not be fixed in time for glusterfs-3.7.4 or glusterfs-3.7.5. This is now being tracked for being fixed in glusterfs-3.7.6.

Comment 8 Sahina Bose 2015-10-30 11:33:27 UTC

(In reply to Avra Sengupta from comment #5)
> Points 1 and 2 are already taken care of. If Points 3 and 4 are also
> addressed, please close this bug.

I don't think you need to track points 3 & 4 in this bug - as they are being tracked in a separate component (Bug 1208388). So there's no need to tie state of this bug to the UI issues.

Comment 9 Raghavendra Talur 2015-11-08 20:25:44 UTC

This bug could not be fixed in time for glusterfs-3.7.6.
This is now being tracked for being fixed in glusterfs-3.7.7.

Comment 10 Raghavendra Talur 2015-11-08 20:49:33 UTC

This bug is on mainline and not on release-3.7 branch. Removed the 3.7 tracker.

Comment 12 Avra Sengupta 2016-10-21 10:00:47 UTC

Based on comment #5 and #8, as points 1 and 2 are already addressed and 3 and 4 are being tracked separately, closing this RFE