1 / 22

WP5 – JRA1 Middleware Development, Evolution and Integration

WP5 – JRA1 Middleware Development, Evolution and Integration. Morris Riedel (JUELICH) JRA1 Leader EC Review Brussels, 22 June 2011. Content. Efforts JRA1 Year 1 Highlights Impacts on EMI 1 release New Functionality (Developments) Integration Standardization Quality Enforcements

awen
Télécharger la présentation

WP5 – JRA1 Middleware Development, Evolution and Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP5 – JRA1Middleware Development, Evolution and Integration Morris Riedel (JUELICH) JRA1 Leader EC Review Brussels, 22 June 2011

  2. Content • Efforts • JRA1 Year 1 • Highlights • Impacts on EMI 1 release • New Functionality (Developments) • Integration • Standardization • Quality Enforcements • Responding to DCI Evolutions • EMI Registry & Messaging • EMI Cloud approaches • Lessons Learned and Inter-WP Work EMI EC Review - Brussels

  3. JRA1 Contributions to EMI 1 Release EMI 1 Requirements PTB Software & Services 30/09/2010 SA1 JRA1 Alberto provides update of slide Now 31/10/2010 SA2 30/04/2011 28/02/2011 JRA1 SA1 EMI EC Review - Brussels

  4. JRA1 Y1 Highlights • All Y1 technical objectives from PTB achieved • 12/16 100% achieved, only 4 achieved with 50%-75% • Detailed Status in new area work plans as well as DNA1.3.2 • Product developments are part of the EMI 1 release • Within four different technologies in one integrated release • Important agreements established • Replacement of legacy GSI • EMI - Execution Services specification • Storage Accounting Record Specification • Common security attributes & several messaging use cases • Key Performance Indicator • Increased standardization adoption EMI EC Review - Brussels

  5. Technical Objectives DNA1.3.1 (1) EMI All-Hands Meeting - Lund

  6. Technical Objectives DNA1.3.1 (2) • … and a lot of preparatory work for technical objectives due in year 2 have been started (e.g. time-consuming agreements, detailed specifications, common APIs, etc.) EMI EC Review - Brussels

  7. JRA1 Y1 KPI-JRA1.1 at a glance EMI EC Review - Brussels

  8. New Functionality: GLUE2 Adoption Enable effective and efficient operations of the DCIs like EGI and PRACE by improving the existing middleware services with new required functionality focusing on usability, manageability and service operations… [DOW] • Consistent information ecosystem in EMI 1 • Avoids adapter-based transformations & semantic loss across EMI components; easier operations in EGI • Decision to use standard-based information model GLUE2 • LDAP and XML renderings • GLUE2 support in job management services • CREAM CE, ARC CE, and UNICORE • SEs publishing initial GLUE2 storage information • dCache, DPM, and StoRM • Production support for GLUE1.3 kept where available EMI EC Review - Brussels

  9. New Functionality: file:// Access Enable effective and efficient operations of the DCIs like EGI and PRACE by improving the existing middleware services with new required functionality focusing on usability,manageability and service operations… [DOW] • Storage elements providing file:// access in EMI 1 • POSIX IO compliant access pattern • NFS clients are able to use EMI SEs in an easy manner • Support for NFS4.1/pNFS makes SEs industry competitors • dCache supports NFS4.1/pNFS (production) • DPM supports NFS4.1/pNFS (experimental) • StoRM supports this functionality via the corresponding underlying file system if available • To be released with next EMI update EMI EC Review - Brussels

  10. New Functionality: HTTP & WebDAV SEs Enable effective and efficient operations of the DCIs like EGI and PRACE by improving the existing middleware services with new required functionality focusing on usability,manageability and service operations… [DOW] • EMI 1 Storage elements support HTTP(S) (+ WebDAV) • HTTP(S) as most widely used standards in the Web & DCIs • Adoption of WebDAV makes EMI SEs improves the usability • Increased competitiveness with business data solutions • dCache offers HTTP(S) (and additionally WebDAV) in EMI 1 • DPM offers HTTP(S) in EMI 1 • StoRM offers support very soon (next release) • Complete adoptions with WebDAV across storage elements planned for EMI 2 EMI EC Review - Brussels

  11. New Security Developments Enable effective and efficient operations of the DCIs like EGI and PRACE by improving the existing middleware services with new required functionality focusing on usability,manageability and service operations… [DOW] • VOMS 2.0 / VOMS-Admin • SAML-based access (VOMS-admin) • RESTful interface to obtain attributes • GSI dependency removal (kept for backward compatibility) • Good progress with VOMRS convergence • Argus 1.2 • CREAM CE works together Argus • UNICORE can work together with Argus • Argus PDP handler prototype for ARC service container • Blacklisting already used by DPM, dCache and LFC EMI EC Review - Brussels

  12. JRA1 Y1 Integration Integrate emerging components into the broader EMI component ecosystem in order to avoid incompatibilities as well as to ensure that the components can be used together … [DOW] • JRA1 delivered a consolidated and streamlined set of services and components from ARC, gLite, UNICORE, and dCache as integrated release for EMI 1 • Compliant to EMI 1 production release criteria • Including re-factoring of existing components to comply with OS guidelines (EPEL, etc.) and project policies • One Globus toolkit version avoids incompatibilities among the different EMI components • OS Integration: SL5/64bit as reference platform in collaboration with SA1 release management EMI EC Review - Brussels

  13. JRA1 Y1 Standardization (1) Guide and validate the open standard adoption process in EMI and participate in standardization bodies in order to promote and drive standards that are relevant to the EMI project … [DOW] • Wide adoption of GLUE2 within EMI products • Whole ‘EMI information ecosystem’ based on GLUE2 • Replacement of legacy (proprietary) GSI • https instead of httpg for the SRM protocol as prototype • Implemented in dCache server & client (w/o delegation yet) • Implemented with VOMS 2.0 • Security delegation group formed to evaluate solutions • Agreement on common profiles • Agreement on SAML profile for common attributes • Agreement on XACML profile for attribute-based policies EMI EC Review - Brussels

  14. JRA1 Y1 Standardization (2) Guide and validate the open standard adoption process in EMI and participate in standardization bodies in order to promote and drive standards that are relevant to the EMI project … [DOW] • Standardization pre-studies • Agreements within the EMI project on the path towards standardization • Ensure that EMI speaks with one voice to the community • Job execution and management • Agreement on EMI Execution Service Specification (ES) • [ https://twiki.cern.ch/twiki/bin/view/EMI/EmiExecutionService] • Storage accounting • Storage Accounting Record Specification (StAR) agreement • [http://cdsweb.cern.ch/record/1352472/files/StAR-EMI-tech-doc-final.doc ] CDSWEB Links (Florida) STAR: OK MISSING: EMI –ES (upload!) Information given EMI EC Review - Brussels

  15. JRA1 Y1 Standardization (3) Guide and validate the open standard adoption process in EMI and participate in standardization bodies in order to promote and drive standards that are relevant to the EMI project … [DOW] • Active contributions to OGF Working Groups • Grid Interoperation Now (GIN) CG • EMI chair position; EMI and international Grid interoperability • Production Grid Infrastructure (PGI) WG • EMI chair position; EMI input via EMI ES around job management • GLUE2 WG • EMI chair position; EMI implements specs & pushes XML rendering • Usage Record (UR) WG • EMI chair position; EMI input via storage accounting StAR spec. • Storage Resource Manager (SRM) WG • EMI provides implementation feedback & production experience EMI EC Review - Brussels

  16. JRA1 Y1 Quality Enforcements Continuously improve the quality of the grid services by implementing standard Quality Control activities with particular focus on standard compliance and conformance tests, unit and functional tests… [DOW] • JRA1 has followed the SA2 Software Quality Assurance Process (SQAP) • Product teams took established policies into account such as packaging, documentation, change management, etc. • Validation collaboratively by JRA1 and SA1 QC teams • Focus in year 1 on harmonization on release management • JRA1 and SA2 will work defining/monitoring metrics of the software engineering process in year 2 • E.g. metrics for Object Oriented Programs (Chidamber & Kemerer metrics suite) such as WMC, DIT, NOC, CBO, RFC EMI EC Review - Brussels

  17. EMI Registry and Messaging Follow and anticipate the needs of the growing infrastructure usage by investigating and adopting technologies to improve scalability, reliability and performance of the grid services… [DOW] • Provide DCIs with a common EMI registry • Provides functionality to obtain information about the existence of the grid service from the grid services itself • Design is available and early implementation plan exists • [https://twiki.cern.ch/twiki/pub/EMI/EMIRegistry/EMIRegistryDesign-v0.2.doc] • EMI take advantage of the messaging technologies • Early prototype for File Catalogues and SE synchronization • Use cases in the accounting area investigated: shipping usage records via a messaging system • Internal guidelines for messaging & EMI products • [https://twiki.cern.ch/twiki/bin/view/EMI/EMIMessagingGuidelines ] CDSWEB Links (Florida) EMI – Registry (upload) Information given EMI EC Review - Brussels

  18. EMI Cloud Approaches Increase the relevance and usability of the EMI grid middleware by actively managing user requirements in collaboration with infrastructure and community projects and initiatives… [DOW] • Clouds/virtualization • EMI Cloud Working group has been established • Goals: Integration scenarios with off-the-shelf computing cloud systems to be able to execute grid jobs on those (scaling out to clouds) evaluated, but also beyond that • EMI and cloud approaches have been researched and several documents are available (report, paper, etc.) • [https://twiki.cern.ch/twiki/pub/EMI/EmiJra1T5TaskForceCloudandVirtualization/EMIVirtCloudReport-v0.7.doc ] • Standardization approaches observed (OCCI, CDMI, etc.) • Existing work is baseline for setting up an EMI cloud strategy in the next months collaboratively with EGI CDSWEB Links (Florida) Cloud (upload!) Information given EMI EC Review - Brussels

  19. Lessons Learned • Quality Control Improvements • Alignment of JRA1 QC and SA1 QC makes sense • More time for testing towards EMI 2 release required • Write more unit tests, functional tests, etc. • Functional, conformance, compliance tests as part of development required • SA2 Policies • Plan together with SA2 when new policies will be released and enforced • Inter-product/-middleware work and strategies • Plan inter-product work and tests across middlewares/PTs EMI EC Review - Brussels

  20. Inter-WP Work • Initially challenging since EMI is a big project… • Gradually improving understanding of different technology backgrounds and a wide variety of ‘modus operandi’ • Collaboration with SA2 • JRA1 uses tools provided by SA2 (tracker, ETICS, testbeds,…) • Getting guidance with policies to improve software quality • Collaboration with SA1 • ETICS integration and received release process support • Delivered EMI 1 integrated releases • Collaboration with NA2 • Received training on tools like ETICS • Joint participation to important events (EGI UF, OGFs,…) EMI EC Review - Brussels

  21. Planned Major Year Two Activities • Developments • EMI – ES standardization pre-study Implementations • EMI Accounting Records agreement and CE support • Common Libraries for data access and Authentication • Argus Integration in Compute and Data • NAGIOS Probes for EMI Services • Important agreements established • Common EMI Delegation method • EMI Parallel Execution Framework & EMI Cloud strategies • Key Performance Indicator • Reduction of products and SLOCs • Increased standardization adoption (GLUE2, WebDAV,…) EMI All-Hands Meeting - Lund

  22. EMI is partially funded by the European Commission under Grant Agreement INFSO-RI-261611

More Related