Jan Pazdziora wrote:
On Tue, May 26, 2009 at 08:43:26AM -0700, Mike McCune wrote:
I wonder what should be correct behavior of monitoring when you disable
it in WebUI.
Current state is that is you should switch off scout and backend
separately. And if you disable monitoring and nothing else, then scout
is still running.
Is this what we want to? Or is correct solution to switch off scout too?
And if we switch off scout too, what to do with proxy scout?
What would you expect from monitoring switch off in webui?
I would expect it to disable both the Monitoring and the MonitoringScout
service. Leaving the scout running while the Monitoring service is
disabled is largely pointless and confusing.
On the other hand, having the scout run on the same Spacewalk server
is just one possible setup. It can also run on Proxies and it will
probably be hard to shut down the scout on Proxies as well. Are we
OK with the scout on Spacewalk server behaving differently from the
Proxy one?
I'm fine with that. Since they really can't be controlled from
Spacewalk's GUI I don't think there is any expectation that they
(Proxies) would behave the same as the Scout on the Spacewalk box itself.
How about not allowing to disable the monitoring in the WebUI if there
is at least one enabled scout there? Or at least having big fat warning
about the scouts left behind if monitoring is disabled?
I think a message in the GUI after disabling stating: "You have disabled
the Monitoring and MonitoringScout on this Spacewalk server. Any
Spacewalk Proxies with Monitoring Scouts enabled on different machines
will continue to run"
Mike
--
Mike McCune
mmccune AT redhat.com
Engineering | Portland, OR
RHN Satellite | 650.567.9039x79248
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
