APEL Architecture Alison Packer Overview Grid jobs accounting

  • Slides: 13
Download presentation
APEL Architecture Alison Packer

APEL Architecture Alison Packer

Overview • Grid jobs accounting tool • APEL Client software - installed in sites

Overview • Grid jobs accounting tool • APEL Client software - installed in sites (CEs, g. Lite. APEL node) • APEL Server accepts data from APEL client plus external clients • Data is processed by APEL Server system and made available by the Accounting Portal: http: //www 3. egee. cesga. es/gridsite/accounting/CESGA/egee_view. php

Current Architecture CLIENT bash CLIENT BROKER Java My. SQL bash perl My. SQL CLIENT

Current Architecture CLIENT bash CLIENT BROKER Java My. SQL bash perl My. SQL CLIENT CONSUMER CLIENT python bash Java My. SQL Java CLIENT RGMA REGISTRY CLIENT Closed on 1 st March My. SQL FLEXIBLE ARCHIVER EXTERNAL CLIENTS PORTAL

Current System • R-GMA transport mechanism now replaced with Apache Active. MQ (broker) •

Current System • R-GMA transport mechanism now replaced with Apache Active. MQ (broker) • However: – Many machines and many databases – Many different languages/scripts – If the database is down clients can not publish – Some clients have direct access to the database, some publish via the APEL client

New System APEL CLIENT EXTERNAL CLIENTS SSM MESSAGE BROKERS – located across Europe (Active.

New System APEL CLIENT EXTERNAL CLIENTS SSM MESSAGE BROKERS – located across Europe (Active. MQ) CENTRAL SERVER (My. SQL, python) SSM RECORD LOADER SSM REGIONAL APEL SERVER SUMMARISER SSM PORTAL APEL Monitoring Job Records, Summary Job Records, Sync Records

New System features • Database improvements: o removed duplication of information (many date/time fields

New System features • Database improvements: o removed duplication of information (many date/time fields in same record) o added important fields (number of nodes, processors – for MPI jobs) o partitioning, indexing • All communication sent via Message Broker service using Secure Stomp Messenger (SSM) • SSM is available even if the database is not, so clients can still send messages • Regional APEL Server system

New System – showing Use Cases APEL CLIENT Job Records REGIONAL APEL SERVER Summaries

New System – showing Use Cases APEL CLIENT Job Records REGIONAL APEL SERVER Summaries EXTERNAL CLIENTS MESSAGE BROKERS – located across Europe (Active. MQ) Summaries & Job Records Summaries plus PORTAL CENTRAL APEL SERVER

Use Cases 1. APEL Client - publishes Job Records to central APEL server 2.

Use Cases 1. APEL Client - publishes Job Records to central APEL server 2. Regional APEL server – uses APEL Client and publishes Summaries to central APEL server 3. Site has own accounting system, publishes Summaries to central APEL server NOTE: All publishing is via Message Brokers

Messages • A message is one file which is sent and received by the

Messages • A message is one file which is sent and received by the SSM. A message will contain a number of records (e. g. 1000) • A record corresponds to one row in the database • The header in each message tells the server which type of records are in that message • Whole message is encrypted before it is sent and messages are signed so we know their origin

Message Types Currently 3 types of message defined: 1. Job Records – from APEL

Message Types Currently 3 types of message defined: 1. Job Records – from APEL client 2. Summary Records – from external clients and regional APEL server 3. Sync Records – for APEL monitoring Additional message types will be defined to accommodate new record types as required.

Summary Record message APEL-summary-job-message: v 0. 1 Site: RAL-LCG 2 Month: 3 Year: 2010

Summary Record message APEL-summary-job-message: v 0. 1 Site: RAL-LCG 2 Month: 3 Year: 2010 Global. User. Name: /C=whatever/D=some. DN VO: atlas Group: /atlas Role: Role=production Earliest. End. Time: 1267527463 Latest. End. Time: 1269773863 Wall. Duration: 23425 Cpu. Duration: 2345 Normalised. Wall. Duration: 244435 Normalised. Cpu. Duration: 2500 Number. Of. Jobs: 100 %%. . . another summary job record. . . %%

Deployment • External Clients (Dec, 2011) – External clients migrate to publishing their summaries

Deployment • External Clients (Dec, 2011) – External clients migrate to publishing their summaries to the new system although old system continues to receive Job Records, creates summaries and publishes to portal. • New System in Production (Feb, 2012) – The data from the old database is migrated to the new database; – Data is now summarised and published from the new system; – All external clients must have migrated to the new system at this point; – The old APEL client continues to publish as usual but the data is transferred to the new system using SSM and the message brokers. • New APEL client released (Apr, 2012) – New and old APEL clients both supported. APEL Regional server (Summer, 2012) •

Deployment External CLIENTS CONSUMER BROKER Current APEL CLIENT SSM New APEL CLIENT SSM Regional

Deployment External CLIENTS CONSUMER BROKER Current APEL CLIENT SSM New APEL CLIENT SSM Regional APEL SERVER MESSAGE BROKERS (Active. MQ) SSM PORTAL SSM CENTRAL SERVER (My. SQL, python) APEL Monitoring