1 / 13

GLUE 2: Deployment and Validation

GLUE 2: Deployment and Validation. Stephen Burke egi.eu EGI OMB March 26 th 2013. Overview. Current state of GLUE 2 deployment GLUE 2 support by services Current and expected GLUE 2 profile document Validation glue-validator Nagios Next steps. Deployment status.

smarkowski
Télécharger la présentation

GLUE 2: Deployment and Validation

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. GLUE 2: Deployment and Validation Stephen Burke egi.eu EGI OMB March 26th 2013

  2. Overview • Current state of GLUE 2 deployment • GLUE 2 support by services • Current and expected • GLUE 2 profile document • Validation • glue-validator • Nagios • Next steps GLUE 2 Deployment - EGI OMB

  3. Deployment status • All EGI sites now publish GLUE 2 • Helped by the gLite 3 retirement campaign • Remaining configuration problems all fixed • Should pay attention to new sites – part of certification? • OSG currently has no plans for GLUE 2 • Currently have 325 sites, 4306 endpoints, 51 endpoint types GLUE 2 Deployment - EGI OMB

  4. Service publication • All gLite services (+dCache) publish from EMI 2 • Deployment will advance as EMI 1 is retired • Argus only publishes in GLUE 2 • ARC integration is part of the EMI 3 top BDII • Also has performance improvements, e.g. cache size and indexing • Unicore publishing should come with EMI 3 • Not documented? • IGE (GridFTP, gsissh, gram) publishes from the 3.1 release GLUE 2 Deployment - EGI OMB

  5. EMIR • New service from EMI – service registry • http://eu-emi.github.com/emiregistry/documentation/registry-1.2.1/emir-manual.html • In EMI 3 all services can be configured to register with it • Has been under test for a while – feedback is positive • http://www.isgtw.org/announcement/european-middleware-initiative-registry-solution-federated-online-services • Need to consider how to deploy and use it in EGI GLUE 2 Deployment - EGI OMB

  6. Client support • WMS now has support for matchmaking with GLUE 2 attributes • Data matching not yet supported, but less important • https://wiki.italiangrid.it/twiki/bin/view/WMS/WMS34ExtendedReleaseNotes • GFAL 2 has support for data management tools • No documentation? • ginfo tool in development as a replacement for lcg-info(sites) • http://cern.ch/lfield/ginfo-1.0.0-1.noarch.rpm • Will release to EPEL after feedback from WLCG GLUE 2 Deployment - EGI OMB

  7. EGI Profile • The draft profile document was presented at the August OMB • Defines detailed semantics, extends the schema definitions • Classifies attributes by use case and importance • Service Discovery, Service Selection, Monitoring, Oversight, Diagnostic • Mandatory, Recommended, Desirable, Optional, Undesirable • Various implications: need for accuracy, update rate, latency, caching ... • Detailed validation criteria • FATAL, ERROR, WARNING, INFO GLUE 2 Deployment - EGI OMB

  8. Profile status • Detailed comments received from four people, plus more minor comments from several others • Comments mainly asking for better/more detailed explanations • Detailed comments and replies uploaded to DocDB page • https://documents.egi.eu/document/1324 • Updated document with changes tracked: version 0.9 • Fairly small changes in substance • Will do one final review myself, update and create version 1.0 • Hopefully within a couple of weeks GLUE 2 Deployment - EGI OMB

  9. glue-validator • Existing python tool which just checked the basic schema structure • Enhanced by Maria Alandes Pradillo • BDII developer and WLCG Information Officer • Now implements essentially all validation checks in the profile document • Currently 129 separate tests • Easy to add more • Standalone tool, but can output in Nagios format • Flexible configuration GLUE 2 Deployment - EGI OMB

  10. Middleware validation • Started by looking for middleware bugs • Initially using the EMI 3 certification testbed • Bugs already submitted for several gLite services • Many services were OK! • Continue with ARC and Unicore • Also need to look at IGE • Record progress on a wiki page • https://twiki.cern.ch/twiki/bin/view/EGEE/ISproviders#GLUE_2_0_Validation GLUE 2 Deployment - EGI OMB

  11. Nagios • A previous version of glue-validator is already running on midmon.egi.eu as a test • Some initial problems fixed • Central deployment makes it easier to update • Known middleware bugs will be masked in Nagios • Sites should only get bugs for things they can fix • Need to move the latest version to midmon and check that the output looks sane • Can then consider raising alarms – in a few weeks? GLUE 2 Deployment - EGI OMB

  12. Next steps - deployment • Continue to deploy EMI 2 services • Consider pushing deployment of EMI 3 top BDII • Should be an easy upgrade • ARC integration, several performance improvements • Test EMIR and consider deployment strategy • Test WMS, GFAL and ginfo • Test gstat 3 when available • GLUE2 extensions for GPGPU • NB: GOC DB is also moving to use the GLUE 2 info model • XML rendering but similar to LDAP GLUE 2 Deployment - EGI OMB

  13. Next steps - validation • Review profile document and release “final” version • May well need updates after experience • Document is versioned • Compliance with a given version should be published • Release new version of glue-validator and integrate in Nagios • Submit bugs to developers and sites as necessary • Document known bugs/features GLUE 2 Deployment - EGI OMB

More Related