Download Job Repository

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Extensible Storage Engine wikipedia , lookup

Relational algebra wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Oracle Database wikipedia , lookup

IMDb wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Ingres (database) wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Concurrency control wikipedia , lookup

Functional Database Model wikipedia , lookup

Database wikipedia , lookup

Clusterpoint wikipedia , lookup

Versant Object Database wikipedia , lookup

Database model wikipedia , lookup

Relational model wikipedia , lookup

ContactPoint wikipedia , lookup

Transcript
Enabling Grids for E-sciencE
Job Repository
Oscar Koeroo
JRA3
www.eu-egee.org
INFSO-RI-508833
Content
Enabling Grids for E-sciencE
•
•
•
•
Where does it do what
Goal of Job Repository and what are the advantages
How does it work
Planning
INFSO-RI-508833
2
Where does it do what?
Enabling Grids for E-sciencE
• On a CE the LCMAPS framework is used for its
enhanced usermapping capabilities
– The LCMAPS framework provides usermapping from DN (+
VOMS attributes) to Unix UIDs and GIDs
• Job Repository is implemented primarily as a LCMAPS
plug-in
# LCMAPS Policies:
voms:
localaccount -> posix_enf | vomsextract
vomsextract -> vomslocalgroup
vomslocalgroup -> vomspoolgroup
vomspoolgroup -> vomspoolaccount
vomspoolaccount -> jobrep
jobrep -> posix_enf
standaard:
localaccount -> jobrep | poolaccount
poolaccount -> jobrep
jobrep -> posix_enf | posix_enf
INFSO-RI-508833
3
Goals of Job Repository
Enabling Grids for E-sciencE
• Its goal is to log all the mapping information into a
relational database
– Which user (identified with a DN) submitted what kind of job
(based on the RSL or executable name)
– Which certificate chain has been used per job (linked to this
user)
– Which set of VOMS Attributes did the user use this time and
which jobs has been executed with them
– Which VOMS attribute mapped into which primary GID
– Which VOMS attributes mapped into which secondary GIDs
– Keep hold of the job status through the batch system’s unique
identifier (batch system independent)
• Using any kind of database with the same code
– Done though ‘iodbc’ (starting with a MySQL db back-end)
INFSO-RI-508833
4
And what are the advantages
Enabling Grids for E-sciencE
• Relational database
– An admin can query the db himself with normal DB tools or with use of
provided tools/scripts that extract useful info.
• Traceability
– In a high detail you can follow the mapping mechanism without
grepping and awking log files
• Upgradeability
– With a database schema upgrade (into the active database, extending
the existing schema) you can include other services to provide
information
– Information of other services can be linked through the ‘generic part’
of the database schema
 The ‘generic part’ consists of the user credentials that initiated a service
action
• DB is local to a site because of the sensitivity of the data that it
stores
INFSO-RI-508833
5
How does it work (database schema)
Enabling Grids for E-sciencE
INFSO-RI-508833
6
To be done…
Enabling Grids for E-sciencE
Short Term:
• Using ‘iodbc 3.52’ (but perhaps stick to 3.51 ….)
• Finishing code reorganization
• Releasing it
Long Term:
• Designing new interfaces to the Job Repository
database
– APEL / DGAS seem to be interested in the JR info
– Making it easier for other services to connect and log to the JR
extending the traceability of users and their activities on a site
INFSO-RI-508833
8