Print

Print
Dear All,

A few weeks ago we discussed areas where a service in the GOCDB could be set as "Monitored=N and Production=Y”. We noted three cases in the UK where this setting is (or might be) needed. The EGI.eu response is below. Within this I particularly want to draw attention to the ARC CE publishing case because I know this is going to impact several of our sites:

2 case: Sites had to use the setting for enabling ARC CEs that had a ‘fake’ gLite publisher for APEL enabled (the APEL tests would fail).

Case rejected: This is a known case which was clarified, glite-APEL should be used instead of APEL. APEL is used for Pub and Sync tests, glite-APEL is not monitored as it doesn't have public interfaces.

There is now a deadline of 24th November for all services to be switched to Monitored=Y and Production=Y except for VOMS and Argus. Please let me know immediately (together with underlying reasons) if this is not going to be possible for your site. I will collate any responses (received before 21st Nov) and respond on behalf of the UK.

Many thanks,
Jeremy





Begin forwarded message:

From: "Małgorzata Krakowian - EGI.eu" <[log in to unmask]>
Subject: [Noc-managers] "Monitoring=N and production=Y" combination of flags in GOC DB - use cases
Date: 17 November 2014 18:46:00 GMT
To: NGI Operations Centre managers <[log in to unmask]>

Dear NGI managers,

EGI Operations received 3 cases when "Monitoring=N and production=Y" combination of flags is used. Please see them below with our comment.

1 case: The VOMS probes currently look for the VOMS admin interface which is not present on the mirrors.

Case temporary accepted: Probes should be improved. Ticket to developers will be created by EGI Operations.

2 case: Sites had to use the setting for enabling ARC CEs that had a ‘fake’ gLite publisher for APEL enabled (the APEL tests would fail).

Case rejected: This is a known case which was clarified, glite-APEL should be used instead of APEL. APEL is used for Pub and Sync tests, glite-APEL is not monitored as it doesn't have public interfaces.

3 case: NGI ARGUS's Monitored=N, Production=Y setting might be used because the monitoring requires the opening of ports specifically for the ARGUS monitoring.

Case temporary accepted: These probes were provided by Argus team and added in Update-22. We do not see how to monitor service if it is firewalled. On the other hand if this service should not be opened to public then we should remove the probes and stop monitoring it. Another solution is to open firewall only for Nagios IP. Need for further discussion.


* Except VOMS and Argus all services must be switched to Monitored=Y, Production=Y from Monitored=N, Production=Y. *

We will ask GOC DB to change it on 24th November.

Monitored=N, Production=Y combination will be still possible until above 2 issues will be solved but forbidden for other services than VOMS and Argus for this moment.

Please let us know by 21.November if you have any comments to this mail.

cheers
--
Małgorzata Krakowian
Senior Operations Officer | EGI.eu
[log in to unmask] | skype: malgorzata.krakowian.egi
http://linkedin.com/in/krakowian

"Irony and sarcasm help endure the stupidity of the world."
"If you don't feel stupid, you are not learning fast enough."
_______________________________________________
Noc-managers mailing list
[log in to unmask]
https://mailman.egi.eu/mailman/listinfo/noc-managers