90 likes | 190 Vues
Coordinate grid project collaborations, organize mailing lists for progress updates, commit to 15 grid projects, identify leaders, deploy interoperation resources, enhance job submissions, and select applications for inter-grid operations. Utilize specific lists, engage in discussions, disseminate information, and interconnect islands for seamless grid operations. Follow monthly timelines and aim for substantial results by GGF17. Simplify authorization, manage job submissions, deploy GridFTP, and interoperate within and among grids effectively.
E N D
Further Steps • Mailing lists • General list: • Gridforge site will have the 4 specific lists (which will be announced at the gridforge site) • Tracker updates • Put your comments! • Incorporate the discussions into the plans • Timeframes, monthly granularity • 15 grid projects need commitment • Other grid projects can join! (as long as you could commit personnel resources) => get them on the mailing lists • Being aggressive is good
Next GGF (GGF17 Tokyo) • Need progress by then to have something done within this year • Should not repeat this workshop in May • Group and/or bilateral collaborations in the meantime are good • But it would be better to have beyond two • Information should be disseminated • Caveat: what happens if we don’t have a natural leader for groups? • Charlie and Satoshi (M) have put their neck on the line to have the groups will have a leader each
Identifying set of resources within each grid for interoperation (from PRAGMA-TeraGrid Experience) • Identification of interoperation resources • Identify area of early adoption for interoperation within the production resources to try out initial interoperation • along with the dedicated people • No major changes to the software stacks of the original production systems • Caveat: these need to be production to be significant • Avoid the little testbed being isolated and just dying down without impacting the production • Also, application should be identified for the interoperation to run on these resources
Area-Specific Summaries • Revise the plans with the feedback • Authorization and Identity Mgmt • Deployment of the IGTF CA credentials on all the grids • Also having institutional access to the CAs • Registration of new users to get access to the grids --- how to get authorized on remote grids • Will grid-specific GOCs coordinate to handle this on behalf of each Grid?
Job Submission • Get the islands working within the islands • Pre WS-GRAM (GT2 and GT4), WS-GRAM (GT4), Unicore 4 NJS • Bridge these islands • Looking at different JSDL implementations, and which islands are deploying which • Interoperation testing of JSDL • Need to know the exact state of compliance • OGSA-BES (need to be reviewed, GGF17) • Flavors of Condor as job submission
Information Service • In addition to what I had in my slides… • Define the use case and set minimum of attributes required • Then, work on how it can be represented in each information model (GLUE/CIM) • Initially look at the TeraGrid use case • (SC) Present data in a common fashion on each grid • WebMDS, NAREGI CIM Viewer, SCMSWeb, …
Data • GridFTP deployment and interoperability testing • Incl. acceptable inter-grid GridFTP performance • SRM vs. SRB islands identification and interoperability exercise • Interoperability within each island first
Selecting Applications • Small set of applications that demonstrate that it will “work” across grids • The entire set need to cover the 4 areas • The applications already need to have worked on multiple grids, or at least across a fairly diverse and heterogeneous environment within a grid • Need not run on all grids
THE MAILING LISTS • mgi@ggf.org (the main list) 4 areas • mgi-auth@ggf.org • mgi-jobs@ggf.org • mgi-info@ggf.org • mgi-data@ggf.org Send email to majordomo@ggf.org and in the body of the email say “subscribe listname”. Thanks everyone! Au revoir en Tokio.