1 / 9

Updates on LRMS Grid Information Schema

Updates on LRMS Grid Information Schema. Massimo Sgaravatto INFN Padova. Introduction. The IS schema discussed within WP1 discussed during the WP1-WP4 meeting Few changes proposed during the discussion Hypothesis For the PM9 release a resource is a

cicily
Download Presentation

Updates on LRMS Grid Information 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. Updates on LRMS Grid Information Schema Massimo Sgaravatto INFN Padova

  2. Introduction • The IS schema discussed within WP1 discussed during the WP1-WP4 meeting • Few changes proposed during the discussion • Hypothesis • For the PM9 release a resource is a • Queue of an underlying LRMS, assuming that this queue represents a set of “homogeneous” resource • A “single” node

  3. Schema • ResourceId • GlobusResourceContactString • QueueName • ResourceManagementType • ResourceManagementVersion • GRAMVersion • Architecture • OpSys • PhysicalMemory

  4. Schema • LocalDisk • WP4 will investigate the technical machinery to grant that the advertised "local disk footprint" is actually available to a running job, even in case more than one process is running on a given "worker” node • TotalCPUs • FreeCPUs • NumSMPs • TotalJobs • RunningJobs • IdleJobs • MaxTotalJobs • MaxRunningJobs

  5. Schema • WorstTraversalTime • EstimatedTraversalTime • Scaled value of the last traversal time • Status • RunWindows • Priority • MaximumCPUTime • MaximumWallClockTime • MinSI00 • MaxSI00 • AvgSI00

  6. Schema • Authorization policies • WP1 needs to understand from WP6 whether gridmap file publishing will be OK for Testbed 1 • RunTimeEnvironments • WP4 will negotiate with the Application WPs what kind of information "tag(s)" they would like to use to identify an appropriate Testbed SW installation (e.g.: CMSVersion + CMSRoot, or just a list of RPM names/hashes, etc...) • WP1 will just transmit and match the tag requests through the JDL • AFSAvailable • OutboundIP • InboundIP

  7. Schema • StorageElements • List of SE URIs (format to be determined with interaction with WP5) that are "close enough" to the resource (e.g. on the same LAN) • Other SE information • Needs to be negotiated with WP5 • It is not true that a storage element can be directly accessed using a local protocol (NFS, AFS, …) from a computing resource “attached” to it !!!

  8. Supported LRMS’s • WP4 has to provide the missing information for all the supported LRMS’s • WP4 doesn’t know how to use MDS-2 • WP4 would prefer to update the new, improved Globus “GRAM reporter" rather than rewrite information providers for LRMS’s from scratch

  9. Actions • WP1 will provide an updated information schema, with the actual names of the attributes, identifying data types and formats • GOSP specification ? • WP4 checks with its partners what experience there are with different LRMS’s • WP1 starts the survey of existing information providers in MDS-2 for LSF and PBS (what is already in place ? What is not working ? What is missing) • PBS – Milano – M. Mezzadri • LSF – Padova – Z. Balaton • WP1 will provide a template for information providers or the necessary howto documentation • Checkpoint just before the PTB the 6th of June

More Related