I agree with you Ewan but I was overruled. This is a way of monitoring who has installed Argus, not monitoring the service itself.
glite-apel is another node that does not receive calls and is not monitored externally but in that case we use GOCDB to register the hostDN for access control.
JOHN
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Ewan MacMahon
> Sent: 04 August 2011 22:37
> To: [log in to unmask]
> Subject: ARGUS and the GOCdb
>
> Hi all,
>
> There's just been a broadcast saying:
>
> "the emi.ARGUS service type is now available for the registration of ARGUS
> servers deployed in production. Please register your production ARGUS
> server
> end-points in GOCDB at http://goc.egi.eu/, this is necessary for downtime
> management of the service."
>
> As far as I'm aware ARGUS isn't a service that remote systems are supposed
> to be able to access (and that as and when there are central banning lists
> they'll be pulled, not pushed). It therefore doesn't matter if an ARGUS
> server is down, except in so far as it breaks other service (e.g. CEs), in
> which case they're down, and should be marked as such in the gocdb.
>
> Clearly that doesn't align with the broadcast, so can someone explain where
> I'm wrong?
>
> Ewan
|