next up previous contents
Next: Technology Evaluation Report and Up: Sakai Evaluation including CHEF, Previous: Roadmap for a UK   Contents

Our Proposed Development Strategy

Sakai is currently the aggregation tool of choice for the ReDReSS project (https://e-science.lancs.ac.uk/redress) and the current instability is causing problems with tool development at the present time. What is proposed is a spreading of risk during the further development of the ReDReSS portal and Sakai VRE Demonstrator, using the following steps:

  1. Continue to run a stable version of Sakai RC1 or RC2 on the ReDReSS Web site. This will continue to supply collaboration facilities and a reasonably structured place to hold project material. The instructions for installing such a Sakai instance are contained in a separate document [73];
  2. Install GridSphere (http://www.gridsphere.org) with the aim of using this installation to test the JSR-168 compliance of any tools the projects produce;
  3. Write any tools in such a fashion that both JSR-168 and Sakai TPP versions are generated at compile time. The TPP versions get tested in an isolated Sakai instance (currently Adrian Fish's workstation) before live deployment. The JSR-168 version gets deployed into GridSphere and thus tested for compliance;
  4. When Sakai reaches the point of architectural stability, any tools deployed in GridSphere are moved to the latest Sakai version running on the Lancaster CeS Web server;
  5. A similar procedure is adopted at Daresbury on a separate Web server.

next up previous contents
Next: Technology Evaluation Report and Up: Sakai Evaluation including CHEF, Previous: Roadmap for a UK   Contents
Rob Allan 2005-05-09