1 / 7

Job Repository

Job Repository. Oscar Koeroo JRA3. Content. Where does it do what Goal of Job Repository and what are the advantages How does it work Planning. Where does it do what?. On a CE the LCMAPS framework is used for its enhanced usermapping capabilities

rafael
Download Presentation

Job Repository

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. Job Repository Oscar Koeroo JRA3

  2. Content • Where does it do what • Goal of Job Repository and what are the advantages • How does it work • Planning

  3. Where does it do what? • 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

  4. Goals of Job Repository • 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 database)

  5. And what are the advantages • 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

  6. How does it work (database schema)

  7. To be done… • Performance upgrade • Still needs index tuning (this enhances query times significantly) • Using ‘iodbc 3.52’ (but perhaps stick to 3.51 ….) • Finishing code reorganization • Releasing it • Designing interfaces to the Job Repository database • APEL / DGAS seem to be interested in the JR info • Making it easy for other services to connect and log to the JR extending the traceability of users and their activities on a site

More Related