1. W4: Grid Portals Building Web-enabled End-User Environments for accessing Grid Services By Michael Paul Russell russell@cs.uchicago.edu Dept Computer Science University of Chicago

2. Main Goals Evaluate GridSphere (developed by the ASC project, soon to be open-sourced) Extend/Adapt GridSphere to: Build/Support (Cactus) Simulation Portal Build/Support Grid Administrative Portal Build/Support (Generic) User Portal

3. Tasks Setup our development environnment. Determine where/how production environments will be supported. Determine Functional and User Interface Requirements for proposed Grid Portals. Work with W1-W3 in order to unify architectures, APIs, and so forth. Work with W5-W12 to develop plans for enabling access to the tools these teams are developing.

4. Tasks: Continued Coordinate development of GridSphere with Astrophysics Simulation Collaboratory and other portal groups. Stay on top of GGF standards. Develop relationships with Grid Computing Environments and other Grid Portal working groups.

5. Input to GAT Architecture Well, not exactly input to GAT… More likely to combine efforts with TGAT. Remember also, Grid Portals are “always-up”, multi-user environments for providing access to a variety of Grid Services, to coordinate and monitor user activity.

6. Relationships with other WPs Our relationship with W1-W3 is defined through our collaboration on GAT. We will work with W5-W11 through email correspondence, phone conferences, and onsite visits. It is important that we maintain communication with these groups, as they are building tools that we want to utilize in our Grid Portals!

7. Grid applications will be built with tools developed by these WPs. We must support applications compiled with these tools, particularly as a central or coordinating service. GridLab Portals should be able to utilize standing Grid Services developed by these WPs. GridLab Portal / Work Package Relationships W1W2W3W7 Transient Services that GridLab Portals must support Standing Services that will support GridSphere W5W7W8W11 W6 W6 will provide recommendations for how W4 should handle security.

8. Resources Oliver Wehrens of AEI-MPI: W4 Co-Project Manager and Developer. Michael Russell (soon) of AEI-MPI: W4 Co- Project Manager and Developer, coordinate activity with other Work Packages, augment GAT. Ian Kelley of AEI-MPI: W4 Developer. Jason Novotny, roaming Grid resource: W4 developer, provide development expertise to other projects, augment GAT.

9. Short Term Actions (Months 1-3) Setup our development environment and project pages. Determine where/how production environments should be supported. Establish contact with other Work Packages and develop summary plans for how to collaborate. Develop summary plan to coordinate development of GridSphere with ASC and other groups.

10. Mid Term Actions (Months 3- 12) Determine Functional and User Interface Requirements with other Work Packages (of course, these will change over time). Develop plans for incorporating tools developed by other Work Packages. Start developing!

11. Long Term Actions (3-36) Develop/maintain Grid Portals, i.e. production end-user environments. Develop tools for mobile access to Grid Portals, including email, SMS, and other end- user messaging services for notifying when tasks complete and so on. Promote our work to other communities, get others to use our Grid Portal technologies!

12. Future WP Meetings Meet with W10 (Information Services) Team. Meet with W5 (Testbed Management) Team. Meet with W9 (Resource Management) Team.