Difference between revisions of "MAN09 Accounting data publishing"
Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | ||
{{Template:Doc_menubar}} | |||
{{TOC_right}} | |||
{{Ops_procedures | {{Ops_procedures | ||
Line 14: | Line 11: | ||
|Approval_date = | |Approval_date = | ||
|Procedure_statement = This manual provides information on how to publish accounting information from different middlewares. | |Procedure_statement = This manual provides information on how to publish accounting information from different middlewares. | ||
}} | }} | ||
== Introduction == | == Introduction == | ||
In this manual we will show you how to publish accounting information from different middlewares. | In this manual we will show you how to publish accounting information from different middlewares. | ||
==General information== | == General information == | ||
=== Testing procedure - sending trial records === | === Testing procedure - sending trial records === | ||
To start sending accounting 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 SU in GGUS with following information: | |||
#*site name | |||
#*host DN | |||
#*middleware type | |||
#the site sends us data via the test message brokers. | |||
#when APEL team confirms that everything is OK, site can move to publishing records to production DB. | |||
<br> | |||
=== 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. | |||
The | 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. | ||
=== Testing broker === | |||
The EGI run a network of message brokers which aim to be more resilient than a single message broker could be. | |||
The queue for testing is: | The broker hosts for testing are: | ||
* /queue/global.accounting.cputest.CENTRAL | |||
*test-msg01.afroditi.hellasgrid.hr:6163 | |||
*test-msg02.afroditi.hellasgrid.hr:6163 | |||
Site should not use SSL for testing. | |||
The queue for testing is: | |||
*/queue/global.accounting.cputest.CENTRAL | |||
**(case sensitive) | **(case sensitive) | ||
=== Authorization and authentication === | === 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. | |||
<br> | |||
== ARC == | |||
tbd | |||
=== Multi-middleware site === | === Multi-middleware site === | ||
tbd<br> | |||
== Globus == | == Globus == | ||
The accounting system for the Globus Toolkit is called [http://gridsafe.sourceforge.net/ GridSAFE]. There is an enhanced package provided by EGCF (formerly IGE). It is located in the EGCF [http://www.ige-project.eu/downloads/software/releases/downloads repository for download/installation]. | The accounting system for the Globus Toolkit is called [http://gridsafe.sourceforge.net/ GridSAFE]. There is an enhanced package provided by EGCF (formerly IGE). It is located in the EGCF [http://www.ige-project.eu/downloads/software/releases/downloads repository for download/installation]. There is a [http://www.ige-project.eu/downloads/documents/service-reference-cards/gridsafe GridSAFE Service Reference Card] as well. | ||
There is a [http://www.ige-project.eu/downloads/documents/service-reference-cards/gridsafe 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. | 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. | In order to publish your data to EGI, you need to install the [[APEL/SSM]] tool as well. | ||
=== Multi-middleware site === | === Multi-middleware site === | ||
No additional requirements. | No additional requirements. | ||
== QCG == | == QCG == | ||
For QCG Accounting installation and configuration please check [http://apps.man.poznan.pl/trac/qcg-computing/wiki/QCG-Accounting The QCG-Accounting agent] | For QCG Accounting installation and configuration please check [http://apps.man.poznan.pl/trac/qcg-computing/wiki/QCG-Accounting The QCG-Accounting agent] | ||
=== Multi-middleware site === | === Multi-middleware site === | ||
No additional requirements except: Services of each middlewere should be on separate machines. | No additional requirements except: Services of each middlewere should be on separate machines. | ||
== Desktop Grid == | == Desktop Grid == | ||
tbd<br> | |||
=== Multi-middleware site === | |||
tbd<br> | |||
== EGI Federated Cloud == | == EGI Federated Cloud == | ||
tbd<br> | |||
=== Multi-middleware site === | |||
== Revision History == | tbd<br> | ||
== Revision History == | |||
{| border="3" | {| border="3" | ||
|- | |- | ||
! 1.0 | ! Version | ||
! Authors | |||
! Date | |||
! Comments | |||
|- | |||
! 1.0 | |||
| | | | ||
| | | | ||
| First Draft | | First Draft | ||
| | |} | ||
[[Category:Operations_Manuals]] |
Revision as of 17:15, 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
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 SU in GGUS with following information:
- site name
- host DN
- middleware type
- the site sends us 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. 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.
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.
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
tbd
Multi-middleware site
tbd
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
tbd
Multi-middleware site
tbd
EGI Federated Cloud
tbd
Multi-middleware site
tbd
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
1.0 | First Draft |