Difference between revisions of "MAN09 Accounting data publishing"
Line 36: | Line 36: | ||
=== Publishing summarized records or single ones === | === Publishing summarized records or single ones === | ||
Sites can send either. | Sites can send either. Larger sites are preferred to send summaries. | ||
=== The frequency for sending aggregated/summary records to Apel database? === | === The frequency for sending aggregated/summary records to Apel database? === |
Revision as of 12:17, 27 January 2014
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Title | Accounting data publishing |
Document link | https://wiki.egi.eu/wiki/MAN09 |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | |
Document Status | |
Approved Date | |
Procedure Statement | This manual provides information on how to publish accounting information from different middlewares. |
Owner | Owner of procedure |
Introduction
In this manual we will show you how to publish accounting information from different middlewares.
General information
Testing procedure - sending trial records
To start sending accounting records:
- register 'gLite-APEL' endpoint in GOCDB with host DN information
- Changes in GOCDB can take up to 4 hours to make it to the message brokers.
- create a ticket to APEL Support Unit in [helpdesk.egi.eu GGUS] with following information:
- site name
- host DN
- middleware type
- the site sends data via the test message brokers.
- when APEL team confirms that everything is OK, site can move to publishing records to production DB.
Publishing summarized records or single ones
Sites can send either. Larger sites are preferred to send summaries.
The frequency for sending aggregated/summary records to Apel database?
We recommend sending data daily for all sites, whether sending summaries or individual records. I think this is in the interests of people who are using the portal so that what they see is accurate. The summaries are for a complete month or the current month so far.
Testing broker
The EGI run a network of message brokers which aim to be more resilient than a single message broker could be.
The broker hosts for testing are:
- test-msg01.afroditi.hellasgrid.hr:6163
- test-msg02.afroditi.hellasgrid.hr:6163
Site should not use SSL for testing. use_ssl:false
The queue for testing is:
- /queue/global.accounting.cputest.CENTRAL
- (case sensitive)
Authorization and authentication
Authorization and authentication is made by the host certificate (which is signed by a trusted CA from the ca_policy_core package). Certificate should be registered in GOC DB. The certificate must not have the x509 extension: "Netscape Cert Type: SSL Server" because the message brokers will reject it.
ARC
Instructions can be found here
Globus
The accounting system for the Globus Toolkit is called GridSAFE. There is an enhanced package provided by EGCF (formerly IGE). It is located in the EGCF repository for download/installation. There is a GridSAFE Service Reference Card as well.
The installation package contains information about how to parse your log-files to obtain the accounting information. Furthermore, there is a tool to create summary records in the APEL format which can be called using the ige-apel-client.sh script.
In order to publish your data to EGI, you need to install the APEL/SSM tool as well.
Multi-middleware site
No additional requirements.
QCG
For QCG Accounting installation and configuration please check The QCG-Accounting agent
Multi-middleware site
No additional requirements except: Services of each middlewere should be on separate machines.
Unicore
Publishing UNICORE jobs accounting data to EGI accounting system
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
1.0 | First Draft |