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
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

Publishing summarized records or single ones

Sites can send either. We would prefer sites with a lot of data to send summaries.

The frequency for sending aggregated/summary records to Apel database?

As far as I know it was 'monthly' but it is not clear if the package should contain 1 month or the frequency should be once a month with data for current month? Right now we support first option.

I 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.

XXXX

The EGI run a network of message brokers which aim to be more resilient than a single message broker could be. In order to get the list of hosts and ports, the client software must be able to run an ldap query on the bdii. I can provide details of this if you need. Otherwise, the less resilient approach is to specify a single message broker. The hosts for testing are, I believe:

test-msg01.afroditi.hellasgrid.hr:6163 test-msg02.afroditi.hellasgrid.hr:6163

You should not use ssl for testing.

For production: host msg.cro-ngi.hr, port 6162 host egi-2.msg.cern.ch, port 6162 host egi-1.msg.cern.ch, port 6162 broker.afroditi.hellasgrid.gr, port 6162

You should use ssl for production, using the host certificate (which is signed by a trusted CA from the ca_policy_core package). The certificate must not have the x509 extension: "Netscape Cert Type: SSL Server" because the message brokers will reject it.

The queue for testing is:

/queue/global.accounting.cputest.CENTRAL (case sensitive).

The queue for production is: /queue/global.accounting.cpu.central

Authorization and authentication

Authorization and authentication is made by host certificate which site admin should get from its CA. Certificate should be registered in GOC DB.

Testing procedure - sending trial records

To start sending accounting records:

  1. 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.
  2. create a ticket to Apel SU in GGUS with following information:
    • site name
    • host DN
    • middleware type
  3. the site sends us data via the test message brokers.
  4. when APEL team confirms that everything is OK, site can move to publishing records to production DB.

ARC

Multi-middleware site

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.

Desktop Grid

Multi-middleware site

EGI Federated Cloud

Multi-middleware site

Revision History

Version Authors Date Comments
1.0 First Draft