Difference between revisions of "MAN09 Accounting data publishing"
(→=) |
|||
Line 33: | Line 33: | ||
The summaries are for a complete month or the current month so far. | 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. | The EGI run a network of message brokers which aim to be more resilient than a single message broker could be. |
Revision as of 17:00, 2 October 2013
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 process - introducing new sites
To send to the test server, sites will need to let us know their DN. We prefer a GGUS ticket because it allows us to coordinate better between members of the team. Sites will also need to have their DN in GOCDB under a 'gLite-APEL' endpoint. Changes to GOCDB can take up to 4 hours to make it to the message brokers.
Is there a test procedure to start publishing data? Like contact apel team and first send trial records?
Yes. Please open a GGUS ticket. We will need to know the site name and the certificate DN. We can then authorize the site for the test system. The site sends us data via the test message brokers. Once we have confirmed that everything is OK, we can move to production.
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 |