EGEE is a project funded by the European Union under contract IST-2003-508833

How to avoid coming unstuck

Steve Fisher / RAL

www.eu-egee.org

Some thoughts on GLUE, 16 November 2004 - 2

Computing Element

This is separate – good (I would prefer “status”)

Why separate

Info, Policy and ACPB

Get rid of it RetainRetain!

Some thoughts on GLUE, 16 November 2004 - 3

Site and Service

Why is ServiceStatus not separate

Some thoughts on GLUE, 16 November 2004 - 4

Host etc

This complexity does not help us at all – it is not for batch farms.

If this remains in schema our info providers should not touch it.

Some thoughts on GLUE, 16 November 2004 - 5

A few more details

• The document must define all attributes precisely e.g. Authorization Rule

• Too many optional arguments How to interpret null? Best avoided – otherwise meaning of null must be defined

• Is the assumption that a CE is bound to a single VO good?

• I am concerned to avoid models which are not easily mapped to relational model. Should probably also ensure easy mapping to hierarchical model.

• We want something simple It is hard to get where we want without starting again Tweaking won’t work

Some thoughts on GLUE, 16 November 2004 - 6

SuperGLUE

Site

Service

ServiceStatus

CE

CEStatus

SE

SEStatus

*

Can we make it as simple as this?

In relational model all except site linked by endpoint URL