[AG-DEV] Continual of AG services

[Philippe d'Anfray]

Bonjour,

Working with AG, it's nice to have default:
     * Bridge registry
     * Jabber server
     * Certificate Authority
     * Venue server

That's what ANL provided and the available AG software (client/venue 
server)  were configured to use them.

 From my point of view the worldwide AG infrastructure is a network of 
AG servers and bridges
To ensure some sort of consistency, probably the Certificate Authority 
must remain unique but the  other "defaults" can be thought of as local 
services (on a regional, country or continental  scale).

 From an operational point of view it is easier to access a "local" 
bridge registry, but as the list of bridges is a global information 
there should be a way to synchronize the various registry ?

 From an operational point of view too, it is easier to access  a 
"local" jabber service and to default to a "local" venue server.

So my idea (but it's already more or less organized this way)

** One Certificate Authority
** A mechanism to synchronize bridge registry
** A mechanism to be able to provide customized Venue client (and Venue 
server) preconfigured to access local (e.g. european, US, etc...) 
ressources which could be simply redefine (?) and put apart some config 
files

Cordialement

Philippe





Le 16/03/12 10:44, vgoya at uvigo.es a écrit :
> In my oppinion, first of all, is to prepare a TODO list identifying the priority
> of tasks.
>
> My knowledge of AG architecture is a little bit "rusty" but,
> high priority services could be:
>
> ANL Bridge Registry
> ANL Jabber Server
>
>
> So, lets start the discussion with this first TODO list:
>
> * Critical:
> ANL Bridge Registry
> ANL Jabber Server
> AG-Dev Certificate Authority
>
> * Must to have:
> Hosting for accessgrid.org
> AG-related mailing lists
>
> * Nice to have:
> ANL Venue Server
> Source Core repository
>
>   maintaining a repository, but I think it warrants further discussion.
>