180 likes | 199 Vues
JRA1 progress. PSC05 Meeting, Dubrovnik, 8-11 September 2009. Deliverables. Three JRA1 deliverables produced DJRA1.1 - Grid application requirements and commonalities assessment M06, 7 PM, UoB-RCUB , Editor: B.M. DJRA1.2 - Application-specific monitoring and control tools design
E N D
JRA1 progress PSC05 Meeting, Dubrovnik, 8-11 September 2009 The SEE-GRID-SCI initiative is co-funded by the European Commission under the FP7 Research Infrastructures contract no. 211338
Deliverables Three JRA1 deliverables produced DJRA1.1 - Grid application requirements and commonalities assessment M06, 7 PM, UoB-RCUB, Editor: B.M. DJRA1.2 - Application-specific monitoring and control tools design M08, 12 PM, IPP, Editor: E.A. DJRA1.3 - Application services design report M12, 10 PM, UoB-RCUB, Editor: B.M. DJRA1.4 - Application services implementation and deployment report M22, 30 PM, UoB-RCUB, Editor: B.M. DJRA1.5 - Assessment of operational tools developed M23, JRA1 28,5 PM, ICI, Editor: A.S. PSC05 meeting, Dubrovnik, 8-11.09.09 2
Milestones MJRA1.1 - Baseline analysis of operational tools M03, IPP: wiki, informal report MJRA1.2 - Application commonalities assessed and areas of development identified M06, UoB-RCUB: DJRA1.1 MJRA1.3 - Operational tools implemented and running M16, IPP: wiki, informal report 5 in production, Logwatch-G and AMS in beta MJRA1.4 - Selected application services implemented and deployed M24, UoB: DJRA1.3, demonstration at review PSC05 meeting, Dubrovnik, 8-11.09.09 3
Ongoing Developments and Metrics (Y1->PSC05) 11 AS (7 major, 3 pre-existing as prototypes, 1 small effort with some initial interest) Described in DJRA1.1 and DJRA1.3 7 OT Described in DJRA1.2 Black: As in DoW Green: Achieved PSC05 meeting, Dubrovnik, 8-11.09.09 4
Application Services (Y1->PSC05) PSC05 meeting, Dubrovnik, 8-11.09.09 5
Operational Tools (Y1->PSC05) PSC05 meeting, Dubrovnik, 8-11.09.09 6
Access to JRA1 Developments http://wiki.egee-see.org/index.php/JRA1_Commonalities PSC05 meeting, Dubrovnik, 8-11.09.09 7
Y1 review recommendations The reviewers make the following recommendations: DJRA1.5 due in M23, Assessment of Operational Tools Developed, should include a description of: which tools have come from previous projects; which tools have been enhanced in this project; which tools are new; how the tools compare with what has been developed elsewhere which tools have been picked up and exploited by other communities/projects. In the second year of the project, the partners will need to place more emphasis on dissemination of the scientific outputs from the project. PSC05 meeting, Dubrovnik, 8-11.09.09 8
Internal JRA1 MetricsMeasure and compare the progress of AS & OT Current status (only one of offered values, maximum is 8 points): 1 - Planning - Conceptual description, possibly with initial functional specification, or architectural description 3 - Development - in progress, no working version available 5 - Alpha - working version exists, available only to developers 6 - Beta - working version exists, available to users 7 - Production/live - released, open to adding new features and bug-fixes 8 - Production/stable - released, developers still work on bug-fixes but it is closed for new features 7 - Production/closed - final version released, development closed NaN - Abandoned/Inactive - project abandoned before being released to production Usage (additive for each named usage, but up to maximally 6 points): 2 – per each application currently using an application service (AS only) 1 - per each site having tool deployed (if applicable, OT only) or 1 - per each user (e.g. grid site administrator) using it in last 3 months (for OT only) Presentation (only one of offered values, maximum is 6 points): 0 - No presentation or outdated presentation 2 - Up-to-date brief presentation (based on JRA1 presentation template) available (not more than 3 months old) 4 - Up-to-date detailed presentation available (not more than 3 months old) 6 - Detailed presentation available with usage or performance analysis and live or recorded demo Visibility towards wider community (additive for each fulfilled indicator, but up to maximally 8 points) 1 - Software license defined and declared 1 - Introductory web site or Wiki with basic data and functional overview 2 - Architectural description available, online or within the corresponding JRA1-related project deliverable 2 – User documentation available (preferably online) fully covering typical usage, including deployment, if applicable 1 - Source code available publicly or to all eligible users (in accordance with license), e.g. via download. 1 - Source code repository with version control available publicly or to eligible users PSC05 meeting, Dubrovnik, 8-11.09.09 9
Metrics issues PSC05 metrics Transitive (indirect) usage by applications should be included as well as external Usage limit moved to 8 (SDSAS, GSSVA and JTS were over 6) Some missed to provide links Future Should publications be added? Automated installation? Fair to centralized OT – clients? PSC05 meeting, Dubrovnik, 8-11.09.09 10
General ranking and status(OT + AS) PSC05 meeting, Dubrovnik, 8-11.09.09 11
Usage (OT + AS) ULMON and AMS must integrate with users quickly BBmSAMeX BBmSAMeX, NMTT, Logwatch should start using AMS PSC05 meeting, Dubrovnik, 8-11.09.09 12
Presentation and end-user visibility (OT + AS) To many rely on standard brief presentations User documentation Only three publish data in a source repository PSC05 meeting, Dubrovnik, 8-11.09.09 13
Dissemination and Plans Achieved so far Early start through presentation of 3 VOs at EGEE’08 conference in Istanbul 4 developments present at EGEE UF4: ESIP Platform, SDSAS, Work Binder, ULMON Dozen of published papers Initial publishing of details and documentation of JRA1 developments Focus on Improvement of existing documentation, installation and user documentation Making both code and packaged (installable) software available Start promotion of developments when they reach adequate level of maturity Possible external verification: should advertise our software and collaborate with other related projects and user communities PSC05 meeting, Dubrovnik, 8-11.09.09 14
Actions to be Taken 1 Source repos whenever possible Developers are encouraged to use the EGEE-SEE/SEE-GRID-SCI SVN-Trac Repository Cleared pending licensing issues (compatibility with used components) Usage by applications – commitment defined in DJRA1.1! New recommendations and guidelines RPM based deployment, installers Use of other development and maintenance support tools (build and publishing of build artefacts - Maven, continuous integration?) Installation packaging Architectural, installation and user documentation PSC05 meeting, Dubrovnik, 8-11.09.09 15
Actions to be taken 2 Promotion, publication, dissemination! Target external communities! Attempt to get additional users and stakeholders from outside the project involved SEE-GRID-SCI UF iSGTW - along with applications Domain-related journals – e.g. Lizza-PAKP/Work Binder in Journal of Hydrology EGEE’09 Conference in Barcelona Earth Science Application Development Methodology by ESIP and gProcess Platforms A Service for Turning Alerts into Messages (AMS) WatG Browser - Grid Information System Browser - non-JRA1 WMSMon - gLite WMS/LB Monitoring Tool - non-JRA1 We had 4 application services (SDSAS, Work Binder, ULMON, ESIP Platform) at 4th EGEE User Forum! Grid observatory (ULMON, GSSVA) Select 2-3 SEE-GRID-SCI generic AS candidates with good metrics, hopefully two would end up endorsed? EGI equivalent of EGEE-II RESPECT program within EGI User Community Services (UCS). Info on UCS contacts and timeframe? To be exploited after the project! Select 2-3 SEE-GRID-SCI generic AS candidates with good metrics, hopefully two would end up endorsed? PSC05 meeting, Dubrovnik, 8-11.09.09 16
Existing APs PSC05 meeting, Dubrovnik, 8-11.09.09 17
New APs JRA1 wiki – add overview, publications, relationships with existing products (BMa, all) Update JRA1 wiki with new information already provided in metrics (not everybody did so) (all) Investigate possible collaborations with Grid Observatory (ULMON, GSSVA) Check possibilities for inclusion of 2-3 AS into RESPECT (ILi) Making the shared source repository available to the public (without certificates) with R/O access (ILi) Prepare abstracts for SEE-GRID-SCI UF (all) Add publications (scientific papers and articles) into metrics (BMa) Review alignment with DJRA1.1 commitments (BMa) PSC06 JRA1 metrics (All) NA4 AP on description of AS in detailed application descriptions PSC05 meeting, Dubrovnik, 8-11.09.09 18