Description of problem:
The engine has at least 6 scheduled jobs for the various gluster management taks.
Some of them are fired at rate of 5 seconds, 60, 300, 600. Every job like that would have to take cpu time, db connection, etc, that we can really spare when the system doesn't need those jobs at all. Our default installation, with hosted engine, will configure a cluster support for both Virt and Gluster, but the default cluster itself is set to use virt only
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup which also has Gluster service enabled (set by engine-config or setup question)
2. All cluster must not have the "Gluster service" checked
3. Set the log level to DEBUG and see every 5 seconds gluster job, and wait more you'll see the rest
Gluster job are rescheduled while no one is using it.
Gluster jobs are paused and will be resumed only when a cluster with Gluser service will be checked.