Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

MAN09 Accounting data publishing

From EGIWiki
Jump to navigation Jump to search
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 08th October 2019
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status APPROVED
Approved Date 30.01.2014
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

Publishing with the APEL Client/SSM

To start sending accounting records:

  1. register 'gLite-APEL' endpoint in GOCDB with host DN information
    • this is usually corresponding to the service endpoint sending the accounting records to the central repository; in case you provide ARC-CEs, each of them need to be registered as gLite-APEL
    • it is needed to authorise the endpoint to use the ARGO Message Service (AMS)
    • Changes in GOCDB can take up to 4 hours to make it to AMS.
  2. install the APEL client and APEL SSM on your publisher host and edit client.cfg and sender.cfg
  3. install the APEL parser relevant to your batch system on each CE and edit parser.cfg
  4. The old ActiveMQ network was dismissed: have a look at the new settings to properly publish the accounting records via AMS: https://github.com/apel/ssm/blob/dev/migrating_to_ams.md
  5. configure the client to publish data from the start of the current month. 
  6. Run the parser(s) and client. 
  7. If there are no errors messages and the client says it has sent messages then wait a day and you should see summaries here: http://goc-accounting.grid-support.ac.uk/apel/summaries2.html
  8. If it doesn't open a GGUS ticket for the APEL Team.

Monitoring the accounting data publication

In order to monitor the regular publication of accounting data, it is enough registering only one CE with the "APEL" service type

See here the details about the related nagios probes: https://wiki.egi.eu/wiki/APEL/Tests

Publishing summarized records or single ones

Sites can send either but the preferred option is summaries. Larger sites are recommended 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.

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

See the NorduGrid ARC 6 documentation:

Revision History

Version Authors Date Comments
Alessandro Paolini 2021-08-06 updated the General Information and ARC sections; removed Globus, QCG, and Unicore sections
Alessandro Paolini 2019-10-08 added link to specific ARC 6 documentation
Alessandro Paolini 2019-09-13 updating the general information...
JC Gordon 17 Sept. 2014 Remove requirement to test APEL client
M. Krakowian 19 August 2014 Change contact group -> Operations support