Скачать презентацию EGI-In SPIRE GLUE 2 0 migration plan Stephen Скачать презентацию EGI-In SPIRE GLUE 2 0 migration plan Stephen

a48fd225cf372659cc2288e97216641a.ppt

  • Количество слайдов: 24

EGI-In. SPIRE GLUE 2. 0 migration plan Stephen Burke egi. eu EGI OMB July EGI-In. SPIRE GLUE 2. 0 migration plan Stephen Burke egi. eu EGI OMB July 17 th 2012 EGI-In. SPIRE RI-261323 www. egi. eu

Overview • Why we needed a new schema • GLUE 2 timeline • Implementation Overview • Why we needed a new schema • GLUE 2 timeline • Implementation and deployment – – Schema design BDII infrastructure Service publication Clients • Migration GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 2 www. egi. eu

GLUE history • The European Data. Grid project (predecessor of EGEE) initially had its GLUE history • The European Data. Grid project (predecessor of EGEE) initially had its own schema (2001) • The GLUE (Grid Laboratory for a Uniform Environment) project was a collaboration between EDG, EU Data. TAG, i. VDGL (predecessor of OSG) and Globus to promote interoperability – The GLUE schema 1. 0 was defined in September 2002 after several months of discussion – Version 1. 1 was released with some minor improvements in April 2003, and deployed by EDG and then LCG and EGEE in 2003/4 – Version 1. 2 was agreed in February 2005, finalised in May 2005 and deployed (fairly gradually) by LCG/EGEE in 2006 – Version 1. 3 was agreed in October 2006, finalised in December 2006 and deployed from 2007 onwards GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 3 www. egi. eu

Problems with GLUE 1. x • The schema has worked, but we have many Problems with GLUE 1. x • The schema has worked, but we have many accumulated issues • Initial schema definitions were based on limited experience – Only for CE and SE • No SRM for storage in 2002, just “classic SE” – Embedded assumptions which turned out to be too restrictive • Not easily extendable • Definitions not always clear, documentation somewhat limited – Case sensitivity, optional attributes, units, special values – Ambiguities (CPUs/job slots) – Too specific (only two CPU benchmarks) – Many things effectively defined by LCG/EGEE practice • We always required changes to be backward-compatible to make upgrading easier – 1. x schema had limited scope for additions, so changes often “shoe-horned” into the available structure – 1. 2 schema introduced a generic Glue. Service object, but it had no connection to the existing CE and SE objects GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 4 www. egi. eu

Upgrading the schema Schema migration is a complex process: 1) Define the abstract schema Upgrading the schema Schema migration is a complex process: 1) Define the abstract schema 2) Define the LDAP rendering 3) Implement the schema in the BDII and roll out 4) Write and deploy information providers 5) Update client tools to understand GLUE 2 • You are here! 6) ((Retire GLUE 1)) • The schema interacts with everything, so the rollout must be a gradual process without breaking anything GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 5 www. egi. eu

GLUE 2 timeline • • • October 2006: First discussion, decision to move into GLUE 2 timeline • • • October 2006: First discussion, decision to move into the OGF January 2007 (OGF 19): First working group meeting June 2008 (OGF 23): Draft specification opened to public comment August 2008: Public comment period ended January 2009: Final specification ready March 2009 (OGF 25): GLUE 2. 0 becomes an official OGF standard – http: //www. ogf. org/documents/GFD. 147. pdf • LDAP rendering defined in May/June 2009 – Resource BDII in production since September 2009 – Site BDII in production since August 2010 – Top-level BDII in production since October 2010 • Information providers gradually rolled out (2010/11) • EMI 2 has full GLUE 2 support (May 2012) GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 6 www. egi. eu

Ground rules • Complete redesign, not backwardcompatible • OGF working group – Real Grid Ground rules • Complete redesign, not backwardcompatible • OGF working group – Real Grid standard – Buy-in from other projects, especially Nordugrid • Incorporates many years of experience – Supports existing uses in GLUE 1. x • Designed to be easy to extend GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 7 www. egi. eu

Key concepts User Domain Negotiates Share with Admin Domain Provides Contacts Has End Point Key concepts User Domain Negotiates Share with Admin Domain Provides Contacts Has End Point Service Maps User to Has Share Manager Defined on Resource Has Runs Has Access Policy Mapping Policy Activity GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 8 www. egi. eu

Computing Service Has Computing End Point Maps User to Has Computing Share Computing Manager Computing Service Has Computing End Point Maps User to Has Computing Share Computing Manager Defined on Manages Application Environment Execution Environment Can use Runs Computing Activity GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 9 www. egi. eu

Storage Service Storage Access Protocol Storage Capacity Has Offers Storage Service Has Storage Manager Storage Service Storage Access Protocol Storage Capacity Has Offers Storage Service Has Storage Manager Manages Offers Storage End Point Maps User to Storage Share Defined on Data Store Has Storage Share Capacity GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 10 www. egi. eu

Changes in terminology • GLUE 2 looks a bit different to GLUE 1, but Changes in terminology • GLUE 2 looks a bit different to GLUE 1, but most of the concepts are there under different names – Site -> Admin. Domain – (VO) -> User. Domain – Element -> Service – Service -> Endpoint – Access. Control. Base. Rule -> Access. Policy, Mapping. Policy – CE, VOView -> Computing. Manager, Computing. Share • Remove duplication/double counting • – Cluster/Sub. Cluster -> Execution. Environment – (Job) -> Activity – SA/VOInfo -> Storage. Share Existing attributes should all map to something – Unless they were unused – All existing use cases should be met GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 11 www. egi. eu

Major changes • Generic concept of a Service as a coherent grouping of Endpoints, Major changes • Generic concept of a Service as a coherent grouping of Endpoints, Managers and Resources – Computing. Service and Storage. Service are specialisations, sharing a common structure as far as possible – Generic concepts for Manager (software) and Resource (Hardware) • All objects are extensible – Multivalued string “Other. Info” and/or Key-Value pairs • All objects have a globally unique ID • Many objects allow many-to-many relations – More flexible, but more complex • Some concepts made more generic/flexible by making them separate objects rather than attributes – Location, Contact, Policy, Benchmark, Capacity • More complete/rigorous definitions – Many more enumerated types – but not fully defined yet – Placeholder values, case sensitivity, optional vs mandatory GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 12 www. egi. eu

Main benefits • General structure for any service – CE, SE, WMS, VOMS, My. Main benefits • General structure for any service – CE, SE, WMS, VOMS, My. Proxy, LFC, FTS, … – Generic service discovery tool • Much more expandable – All objects can be extended – We always find new cases we didn’t anticipate – Schema upgrades can take a long time • Fixes many long-standing problems – Storage. Service designed for SRM! – Computing. Service has a better separation of Grid endpoint, LRMS and queue/fairshare • Interoperability and standardisation – EMI adopted GLUE 2 as a unified standard GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 13 www. egi. eu

BDII implementation • Merged LDAP schema, GLUE 1. 3 + GLUE 2 • Generally BDII implementation • Merged LDAP schema, GLUE 1. 3 + GLUE 2 • Generally follows GLUE 1 practice, but some changes – Attribute names like GLUE 2 Computing. Share. Running. Jobs – Case sensitivity – Some attributes are mandatory – The naming and usage of foreign keys are somewhat different • Single LDAP server, on port 2170 as usual • Separate root DNs – o=glue vs o=grid – Should be no crosstalk other than data volume • Resource BDII: GLUE 2 Group. ID=resource, o=glue • Site BDII: GLUE 2 Domain. ID=, o=glue • Top BDII: GLUE 2 Domain. ID=, GLUE 2 Group. ID=grid, o=glue GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 14 www. egi. eu

Service publisher • Generic service publisher to publish the GLUE 1 Glue. Service object Service publisher • Generic service publisher to publish the GLUE 1 Glue. Service object in production for several years – FTS and LFC have their own dedicated providers • Upgraded to publish the GLUE 2 Service, Endpoint and Access. Policy – Backward compatible with the GLUE 1 publisher – Supports all relevant GLUE 2 attributes, and Services with multiple Endpoints • Progressively rolled out as new versions of services are released – Already have WMS, LB, My. Proxy, bdii_site, bdii_top, msg. broker. *, VOMS and VOBOX in production – In EMI 2 for AMGA, Argus – In work for Hydra, Nagios, Frontier/squid, … • Easy to add publication for any service (APEL? ) • FTS and LFC have upgraded their own providers GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 15 www. egi. eu

CREAM • For GLUE 1 we introduced the glite-CLUSTER node type to allow the CREAM • For GLUE 1 we introduced the glite-CLUSTER node type to allow the Glue. Cluster and Glue. Subcluster objects to be published from a different node – Supports sites with multiple CEs submitting to the same cluster – Also publishes the Glue. Service object for the “RTEPublisher” – a Grid. FTP server used to allow VOs to publish Run. Time. Environment tags in the Sub. Cluster – No-CLUSTER mode continues to publish everything from the CREAM node for small sites • For GLUE 2, use the CLUSTER node to publish all objects except the CREAM and CEMon Endpoints (and associated Access. Policy) – Objects are merged in the site BDII – The detailed plan is described in a wiki page: https: //wiki. italiangrid. it/twiki/bin/view/CREAM/Cream. Glue 2 – EMI 2 has complete publication – Batch system integration for PBS, LSF and SGE is done GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 16 www. egi. eu

Storage • In EMI 2 we should have full GLUE 2 publication for DPM, Storage • In EMI 2 we should have full GLUE 2 publication for DPM, d. Cache and Sto. RM • First versions so will need testing • Need to verify interoperability – Different implementations may have made different choices • CASTOR and Be. St. Man missing – What about classic SE (standalone gridftp)? GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 17 www. egi. eu

Profile • The schema is intentionally very flexible • Many ways to use it, Profile • The schema is intentionally very flexible • Many ways to use it, not necessarily interoperable • Need a profile to specify how it should be used – Detailed semantics of each attribute, what should and should not be published – Monitoring tools should enforce the usage • Currently in work – Will need agreement with EMI, LCG etc • Hope to finalise a document by the TF – May need updates in the light of experience GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 18 www. egi. eu

Deployment status • 389 sites published in GLUE 1 in the CERN top BDII Deployment status • 389 sites published in GLUE 1 in the CERN top BDII (as of 16/7/12) • 221 sites publishing a GLUE 2 Admin. Domain • Missing sites mainly still have a g. Lite 3. 1 site BDII – GLUE 2 support since g. Lite 3. 2 update 16 (4/8/10) • Case-sensitivity in site name in the GOC DB – Sites we noticed were ticketed and fixed • May be other problems at some sites? • No explicit steps needed to configure for GLUE 2, just clones the GLUE 1 configuration – Sites may not have realised that they’re publishing! GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 19 www. egi. eu

Published Endpoints 413 156 82 35 1 83 129 3 5 11 8 2 Published Endpoints 413 156 82 35 1 83 129 3 5 11 8 2 2 bdii_site bdii_top dcap emi. storm file gsidcap gsiftp https lcg-file-catalog lcg-local-file-catalog msg. broker. openwire-ssl msg. broker. stomp-ssl CERN services currently missing - GGUS ticket submitted - CERN seem very slow to respond 33 12 493 337 9 9 9 178 14 217 95 178 1 1 106 50 66 My. Proxy org. glite. ce. Application. Publisher org. glite. ce. CREAM org. glite. ce. Monitor org. glite. Channel. Management org. glite. Delegation org. glite. File. Transfer org. glite. lb. Server org. glite. RTEPublisher org. glite. voms-admin org. glite. wms. WMProxy org. globus. gram org. nordugridftpjob org. nordugrid. ldapglue 1 org. nordugrid. ldapglue 2 org. nordugrid. ldapng SRM VOBOX xroot GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 20 www. egi. eu

Clients • All clients need to become GLUE 2 -aware – Must be backward-compatible Clients • All clients need to become GLUE 2 -aware – Must be backward-compatible – Can happen gradually • WMS: JDL – first version in EMI 2 (next update) • Storage: GFAL/lcg-utils – first version in EMI 2 • Service discovery: lcg-info(sites), glite-sd-query – First version of OGF/SAGA service discovery tool available – CERN has possible replacement for lcg-info(sites) • Monitoring, resource accounting: gstat – in progress (Taiwan) • User tools - ? ? ? GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 21 www. egi. eu

Next steps • Start ticketing sites not publishing in GLUE 2 – Early September? Next steps • Start ticketing sites not publishing in GLUE 2 – Early September? – Now have a push to upgrade for other reasons • Every cloud has a silver lining! • Start pushing EMI 2 deployment – ~ 1 year? – May get help from LCG, e. g. for multicore support • Get new clients into UI/WN distributions • Aim for late 2013 for a full beta-test system? GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 22 www. egi. eu

Summary • Define LDAP schema and deploy in BDIIs – 1. 3 and 2. Summary • Define LDAP schema and deploy in BDIIs – 1. 3 and 2. 0 together in parallel – Now deployed in production • But sites are slow to upgrade! • Write and deploy information providers to populate the new objects – Generic Service publisher available • Being rolled out progressively – Computing. Service publication (for CREAM) developed incrementally • Full version with EMI 2 • Including support for main batch systems – Storage. Service for DPM, d. Cache and Sto. RM in EMI-2 • Update clients to look at the new information – Workload management, data management, service discovery, monitoring, accounting, user, … – Upgrades need to be backward-compatible • Need to start validating the published information • Eventually want to make GLUE 2 the default – Maybe start in 2013? ? ? – GLUE 1 still available as a fallback GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 23 www. egi. eu

References • OGF GLUE working group home page – http: //forge. ogf. org/sf/projects/glue-wg • References • OGF GLUE working group home page – http: //forge. ogf. org/sf/projects/glue-wg • GLUE 2. 0 specification – http: //www. ogf. org/documents/GFD. 147. pdf • LDAP rendering specification (draft) – http: //forge. ogf. org/sf/go/doc 15518? nav=1 GLUE 2. 0 migration - EGI OMB EGI-In. SPIRE RI-261323 24 www. egi. eu