1. Steve Fisher / RAL March 2002
WP3 Status and Plans
Steve Fisher / RAL
March 2002

2. Preamble
My laptop was stolen this week - so I am very short of detailed information (no access to Gantt charts etc.)
Thanks to Gavin McCance for the loan of this laptop
Steve Fisher, March 2002
WP3 Status and plans

3. Recent Developments Easier set up for developers (for 1.2)
Automated generation of RPMs (for 1.2)
Bug(s) removed from Archiver (for 1.2)
Good progress with mediator (for 1.2)
C API (started – ready for 1.3)
and SWIG generated Python and Perl
tested via PyUnit
Steve Fisher, March 2002
WP3 Status and plans

4. Discussed this week WP3 meeting Decided on time scale to pursue
Discussed OGSA
CrossGrid – and how we might meet their requirements
looks OK
we consider this to be important
GUIs
various approaches
GRM / PROVE integration with R-GMA
by using R-GMA as transport within GRM
Planned improvement to WEB and Documentation
Steve Fisher, March 2002
WP3 Status and plans

5. Discussed this week (cont)
With WP2
Security
We will make use of the Spitfire security mechanism ASAP
Installation and compatibility issues
Java 1.4
Included JWSDP
MySQL – for performance
May need Postgresql – for transactions
Will both provide scripts to modify tomcat’s server.xml file
Abandon log4j
WP3 will be able to rely upon Spitfire installing first
Steve Fisher, March 2002
WP3 Status and plans

6. Discussed this week (cont)
With WP7
NetSaint and MapCenter
Both will develop R-GMA plugins
Short report on WP3/WP7 R-GMA work
This work will be extended by deploying at Lyon
Steve Fisher, March 2002
WP3 Status and plans

7. Discussed this week (cont)
With WP1 and 4
Schemas
GGF
InterGrid
Some specific criticisms of CE schema
Logging and Bookkeeping with R-GMA
The impact of R-GMA
During discussion it was suggested that R-GMA info should be fed back into MDS (temporarily) for the RB
Existing info provider scripts can be used to populate R-GMA
Steve Fisher, March 2002
WP3 Status and plans

8. A brief history of WP3 TB0 TB1 Post TB1 MDS within Globus 1.1.3
Ftree
R-GMA
Post TB1
Ftree offered to Globus
OGSA appears
R-GMA developed further – the mediator
Steve Fisher, March 2002
WP3 Status and plans

9. R-GMA and OGSA R-GMA is conceptually close to OGSA
OGSA – replaces resources with services
MDS was for locating resources
OGSA has an index for locating services
MDS does not fit naturally though it will no doubt be kept some time for backwards compatibility
R-GMA might (eventually) use OGSA index to provide the functionality needed for the Schema/Registry
In the short term the R-GMA Registry and Schema will instead be OGSA services
We plan to be quick off the mark with this work
Steve Fisher, March 2002
WP3 Status and plans

10. Developments for TB2 Security – via WP2’s Spitfire mechanism
Shift towards web services
Improved mediator
C, Python and Perl APIs
GRM using R-GMA as transport
Much improved documentation for
Users
Developers
Installers
Steve Fisher, March 2002
WP3 Status and plans

11. TB2
For TB2 we plan that the main info service will be R-GMA with MDS as a fall back solution if we can’t get everything ready on time.
“Being ready” will involve a lot of testing
Steve Fisher, March 2002
WP3 Status and plans

12. Steps along the way
Currently working with WP7 (to publish network monitoring) – March (1.2)
Start work with WP2, 4 and 5 to get something going for – May (1.3)
Using existing info provider scripts initially
WP1 will initially use R-GMA info converted to MDS
Then the rest of the WPs can come in – July (1.4)
Steve Fisher, March 2002
WP3 Status and plans

13. WP8-10 Requirements
The applications will see an integrated system with GRM/PROVE
R-GMA will be there – but GRM/PROVE will not expose it
Steve Fisher, March 2002
WP3 Status and plans