Bug 1262310 - [RFE]: [SNAPSHOT]: snap_scheduler.py should have an unintialize option as well.
Summary: [RFE]: [SNAPSHOT]: snap_scheduler.py should have an unintialize option as well.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-11 11:51 UTC by Shashank Raj
Modified: 2018-04-07 18:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-07 18:52:41 UTC
Embargoed:

Attachments (Terms of Use)

Description Shashank Raj 2015-09-11 11:51:40 UTC 
Description of problem:

Currently there is no option to uninitialize snap_scheduler.py. This is required in case we want snap_scheduler to stop working on specific nodes, after initializing it for the cluster (for all the nodes in the trusted pool).


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

3.7.1-14


How reproducible:
Always

Steps to Reproduce:
1. initialize snap_scheduler.py on all the nodes in the cluster.
2. Now suppose we don't want it to run on specific nodes, so there should be an option to uninitialize it.
3.Disabling snap_scheduler.py will disable it on all the nodes. So a specific uninitialize option is required.

Actual results:


Expected results:

snap_scheculer.py uninitialize option is required.


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