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.
Logged the UI changes under oVirt component - Bug 1208388
Tracking dependency with ovirt scheduler with https://bugzilla.redhat.com/show_bug.cgi?id=1219442
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.
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.
Points 1 and 2 are already taken care of. If Points 3 and 4 are also addressed, please close this bug.
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.
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.
(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.
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.
This bug is on mainline and not on release-3.7 branch. Removed the 3.7 tracker.
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