Bug 1262310 - [RFE]: [SNAPSHOT]: snap_scheduler.py should have an unintialize option as well.
[RFE]: [SNAPSHOT]: snap_scheduler.py should have an unintialize option as well.
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot (Show other bugs)
3.1
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: rjoseph
storage-qa-internal@redhat.com
: FutureFeature, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-11 07:51 EDT by Shashank Raj
Modified: 2017-03-25 12:25 EDT (History)
2 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Shashank Raj 2015-09-11 07:51:40 EDT
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.