1 / 6

Glue schema

Glue schema. Massimo Sgaravatto INFN Padova. EU – US Grids interoperability. Problem: address interoperability between EU and US HEP Grid projects  Datatag, iVDLG, HJTB, Glue First issue to address: have common schemas to describe Grid resources

chakra
Télécharger la présentation

Glue schema

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 schema Massimo Sgaravatto INFN Padova

  2. EU – US Grids interoperability • Problem: address interoperability between EU and US HEP Grid projects •  Datatag, iVDLG, HJTB, Glue • First issue to address: have common schemas to describe Grid resources • Goal: to have common schemas for CE, SE, and SE defined, deployed, and tested in a short time (for the DataGrid Testbed 2 release) • Long term discussions in GGF DAMED WG

  3. Tasks • Refine and agree on terminology (April 1-15) • CE: The interface to computing power provided in a fabric for user job execution on batch and interactive CPU services. It handles job submission requests coming from the Grid and their execution. It also provides to the Grid information on itself and the jobs it is managing • Decided to consider a logical view (service), and not a physical description of the resource • SE: Any data storage resource that is registered in a Grid Information service, contains files registered in a Replica Location Service, and provides access to remote sites via a Grid interface (e.g.: GSI authenticated) • NE: a network path or a set of network hops. This includes both end-to-end and hop-by-hop path information.

  4. Tasks • Define common schema for a CE using GOS (April 7-30) • So far (changes wrt EDG Schema): • Min, Max, Average for SI, SF, MHz (9 attributes) • IdleJobs  QueueLenghth • Long discussions on FreeCPus • Use it only when it make sense • Discussions on CEId • Still to be decided … • Totaljobs, Maxtotaljobs, Maxrunningjobs removed • Other attributes expected to be renamed, removed, added

  5. Tasks • Identify GLUE testbed hosts (April 15-May 15) • Add new CE schemas to Globus and EDG “information provider” package. Write unit tests to test modifications (May 1-30) • Modify and use “Grid Searcher” tool for testing new schemas (May 1-30) • Modify EDG WP1 RB and other middleware to use the new schemas, and test. (May 1 - June 30) • Define a schema versioning mechanism to allow easy changes/additions to the schemas in the future. (May 1-30)

  6. Tasks • Install R-GMA on GLUE testbed, and test. Configure EDG CE with R-GMA information providers, write new information providers if necessary(July 1-31) • Modify R-GMA equivalent to “Grid Searcher” to work with new schemas (July 1-31) • Define common schema for SE, and repeat step 4 and 5 (July 1-31) • Define common schema for NE, and repeat step 4 and 5 (July 1-31) • More testing (August) • Deploy on EDG testbed 2 (September)

More Related