EGEE is a project funded by the European Union under contract IST The UK Cluster Steve Fisher / RAL JRA1 meeting at Cork, 19/ April

JRA1 meeting at Cork, 19 April Contents Who we are Organizational things What we plan to do – in very broad terms What we have done so far What we will do over next few months I will try to identify potential problems as I go along

JRA1 meeting at Cork, 19 April People and Roles Based at RAL  Robin Middleton (0.5) Cluster Manager  Steve Fisher Technical Manager, Documentation and Quality  Abdeslem Djaoui Architect, deputy technical manager and developer  Antony Wilson Architect, deputy technical manager and developer  Linda Cornwall (0.5) Documentation and Quality  Rob Byrom Developer  Martin Craig Developer  Steve Hicks Developer  John Walk Developer  A.N.Other Integrator, sysadmin and developer and security Based at QMUL  Roney Cordenonsi Developer

JRA1 meeting at Cork, 19 April Organization We are all in adjacent offices We have short meeting each Monday morning Having looked at various web based project management tools will use dotProject (following CERN cluster)  Allows individual to record their own progress  Allows all members to see the big picture We can be ed at:  No web page yet  Will be rectified soon

JRA1 meeting at Cork, 19 April Some issues All roles in TA will need at least 2 people  To provide coverage during illness and holiday  2 heads are better than 1  Probably need to move people around a bit All developers are assumed to develop unit tests themselves Integrator / sysadmin still to be recruited  This role is not yet well understood Lacking expertise for security and JRA3 liaison

JRA1 meeting at Cork, 19 April Our mission To meet all information and monitoring needs  Expect to base much of our re-engineering work on R-GMA  Inter-work with other information systems and displays  We are not responsible for the contents of the schema but will coordinate as necessary

JRA1 meeting at Cork, 19 April Activities so far New API implemented (partially) as wrapper round the old one for the ARDA prototype  We would value feedback on the new API Registry replication completed and tested on our cluster testbed The new API includes authorisation  Not complete yet – but a good start Web service prototypes written for all components Extensive UML diagrams for new design  Once design agreed we will refactor code towards it

JRA1 meeting at Cork, 19 April Concerns How do we ensure feedback on the new API of the first prototype? We are making decisions which should probably be discussed in dedicated EMT sessions:  Java package names  Mapping between Java, C++ and C. For example: For compatibility with C avoid overloading function names For compatibility with Java avoid C++ overloaded operators  Error handling and exceptions  Where should such issues be discussed? We need guidance (from JRA2?) on document generation i.e. LaTeX or Docbook (XML)

JRA1 meeting at Cork, 19 April Next steps Revise the prototype code as necessary Complete the authorisation design (API and internally) Design the schema replication  Note that the condition we are protecting ourselves from is rather unlikely – can we take advantage of this fact? Enhance the mediator  This is being taken over from Heriot-Watt Clean up the SQL parsing so that it corresponds precisely to one of the SQL92 levels Finalise the design for the first release and complete refactoring Fix the contents of the first release Watch developments elsewhere and seek to inter-work Work with others to understand relationship between new services and I&M.

JRA1 meeting at Cork, 19 April Concerns Convergence between the prototype and the properly engineered code for the first release