> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of David McBride
> Sent: 13 June 2006 23:30
> To: [log in to unmask]
> Subject: Re: Top 5 Things to change in the LCG Middleware?
>
> On Tue, 2006-06-13 at 22:51 +0100, Gordon, JC (John) wrote:
>
> > 1. The ability to query the status of a grid service by talking
directly
> > to it, not by writing a test which tries to use its functionality.
The
> > equivalent of ping which asks a service 'what state are you in' and
to
> > which various status replies can be returned.
>
> This is interesting. What kinds of status information would you be
> looking for from, say, a Globus gatekeeper, that the various
information
> systems of the day don't already report?
The minimum would be 'are you up?'. Having to telnet to the port and
consider the answer shouldn't be the option. Services which can exist in
multiple states should be able to report them running/quiesed/whatever.
>
> > 2. Remote management of a service - the ability with appropriate
> > authorisation to STOP, and START a service without logging on to the
> > host.
>
> What's wrong with SSH? You can authenticate as root and perform any
> systems administration activity, including service management.
Two answers:-
a) I envisaged people having management rights over a service without
the complete control of root. Say remote grid operators having the right
to stop/start an RB at your site which has a wider grid role than just
your site. You would allow them to do this but wouldn't want them to
have carte blanche of root.
b) I am told that for some services (eg RB) it is no simple matter to
get them working so a simple command would be a big step forward whether
you executed it as root via ssh or directly via an API.
John
|