SSM and Accounting Will Rogers STFC Introduction SSM

Introduction • • • SSM introduction SSM update Accounting status SSM 2. 0 Where

What is SSM? • Secure Stomp Messenger • Simple program to send and receive

SSM Status • Deployed in production for ~ 6 months • No operational difficulties

Accounting and SSM • SSM can transport any data • We use it for

Accounting Recipe • Produce some accounting records – APEL format – EMI CAR –

SSM 2. 0 • • SSM 1 works well But we are changing it

SSM 2. 0 • Interoperability issues: – Crypto not well defined – Synchronous messaging

EMI Messaging Protocol for Accounting (EMPA) • More logical, simpler • Use persistent queues

What now? • SSM is operational (version 1. 2) • Stable, reliable, hardened •

Some links • SSM: – https: //wiki. egi. eu/wiki/APEL/SSM • APEL message formats –

Slides: 12

Download presentation

SSM and Accounting Will Rogers, STFC

Introduction • • • SSM introduction SSM update Accounting status SSM 2. 0 Where next?

What is SSM? • Secure Stomp Messenger • Simple program to send and receive messages • Independent of message content • Uses STOMP (and EGI brokers) • ~1 k lines of python code

SSM Status • Deployed in production for ~ 6 months • No operational difficulties – (except for an LDAP query bug) • Robust, fast • Handles load easily • Allows separation of messaging and server: – filesystem buffer – but no message checking • Still improving usability (!)

Accounting and SSM • SSM can transport any data • We use it for accounting • Production: – APEL message format • Testing: – EMI Compute Accounting Record (CAR) – EMI Storage Accounting Record (St. AR)

Accounting Recipe • Produce some accounting records – APEL format – EMI CAR – EMI St. AR • Put them into a directory • Run SSM • This is pretty easy

SSM 2. 0 • • SSM 1 works well But we are changing it Why? It’s a bit over-complicated – Difficult to develop against – Could be simpler

SSM 2. 0 • Interoperability issues: – Crypto not well defined – Synchronous messaging – Unnecessary (? ) message sequence • EMI has different accounting systems which need to interoperate • One python program is not good enough.

EMI Messaging Protocol for Accounting (EMPA) • More logical, simpler • Use persistent queues – Not replies • Use SSL – Instead of encryption – (encryption still an option) • Use the infrastructure

What now? • SSM is operational (version 1. 2) • Stable, reliable, hardened • Don’t wait for version 2. 0 – It will be phased in gradually • Soon we will accept: – SSM 1, SSM 2 (EMPA) – APEL messages, CAR, St. AR

Some links • SSM: – https: //wiki. egi. eu/wiki/APEL/SSM • APEL message formats – https: //wiki. egi. eu/wiki/APEL/Message. Format • CAR: – https: //twiki. cern. ch/twiki/bin/view/EMI/Compute. Accounting • St. AR: – https: //twiki. cern. ch/twiki/bin/view/EMI/Storage. Accounting

Questions?