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.
Difference between revisions of "APEL/Storage"
(Improving instructions and making formatting consistent) |
|||
| Line 3: | Line 3: | ||
EMI delivered StAR solutions for dcache and DPM in EMI-3. In both cases the storage service queries its database at a site and extracts data to populate StAR usage records. The site then uses SSM as a transport method to send the StAR records across the EGI Messaging Service to APEL's central accounting repository. | EMI delivered StAR solutions for dcache and DPM in EMI-3. In both cases the storage service queries its database at a site and extracts data to populate StAR usage records. The site then uses SSM as a transport method to send the StAR records across the EGI Messaging Service to APEL's central accounting repository. | ||
< | <br> | ||
Follow the link for your product. | == Deployment Instructions == | ||
=== Get the accounting script === | |||
Follow the link for your product. | |||
[[APEL/Dcache|dcache]] | [[APEL/Dcache|dcache]] | ||
[https://svnweb.cern.ch/trac/lcgdm/wiki/Dpm/Dev/Recipes/EGI_APEL_Accounting DPM] - you need to run 1.8.7 or higher. | [https://svnweb.cern.ch/trac/lcgdm/wiki/Dpm/Dev/Recipes/EGI_APEL_Accounting DPM] - you need to run 1.8.7 or higher. For earlier releases it can be found here http://svnweb.cern.ch/world/wsvn/lcgdm/lcg-dm/trunk/scripts/StAR-accounting/star-accounting.py | ||
For earlier releases it can be found here http://svnweb.cern.ch/world/wsvn/lcgdm/lcg-dm/trunk/scripts/StAR-accounting/star-accounting.py | |||
On the command line which runs the script, add --site="your-GOCDB-sitename" | On the command line which runs the script, add --site="your-GOCDB-sitename" | ||
=== Get the SSM software === | |||
The APEL SSM software can be installed from the yum repo or by downloading an rpm or tarball. See here for more information: [[APEL/SSM|SSM]] | |||
=== Get authorised === | |||
While storage accounting publishing is still in test mode please send the host certificate DN to [mailto:apel-admins@stfc.ac.uk] and ask them to authorise you for storage publishing. | |||
=== Configure SSM === | |||
To configure apel-ssm for sending acounting records we have to edit the file /etc/apel/sender.cfg, and modify some parameters: | |||
and | |||
network: TEST-NWOB | * In the '''[broker]''' section, you need: | ||
as for initial testing. Also set: | <code>network: PROD</code> | ||
and '''not''': | |||
<code>network: TEST-NWOB</code> | |||
as for initial testing. Also set: | |||
use_ssl: false | <code>use_ssl: false</code> | ||
* In the '''[certificates]''' section, you need to set the host certificate to be used by the sender: | |||
<code>certificate: /path/to/your/host/certificate | |||
key: /path/to/your/key</code> | |||
[ | * In the '''[messaging]''' section, you need: | ||
<code>destination: /queue/global.accounting.test.storage.central</code> - as described here: https://wiki.egi.eu/wiki/APEL/SSM2Configuration. | |||
dcache and dpm should send one StAR record per VO. Please set up a cron to run once per day. | dcache and dpm should send one StAR record per VO. Please set up a cron to run once per day. | ||
When storage accounting moves to the production message broker network then you will need to add a servicetype to GOCDB for the host which runs SSM. The servicetype | When storage accounting moves to the production message broker network then you will need to add a servicetype to GOCDB for the host which runs SSM. The servicetype has not yet been defined but it will require the host certificate DN. | ||
[http://goc-accounting.grid-support.ac.uk/storagetest/storagesitesystems.html Accounting Portal Prototype view] | |||
Revision as of 14:25, 5 November 2015
Storage accounting in APEL is based on the StAR (Storage Accounting Record) developed by EMI in conjuction with the OGF Usage Record Work Group (UR-WG). The format is documented here.
EMI delivered StAR solutions for dcache and DPM in EMI-3. In both cases the storage service queries its database at a site and extracts data to populate StAR usage records. The site then uses SSM as a transport method to send the StAR records across the EGI Messaging Service to APEL's central accounting repository.
Deployment Instructions
Get the accounting script
Follow the link for your product.
DPM - you need to run 1.8.7 or higher. For earlier releases it can be found here http://svnweb.cern.ch/world/wsvn/lcgdm/lcg-dm/trunk/scripts/StAR-accounting/star-accounting.py
On the command line which runs the script, add --site="your-GOCDB-sitename"
Get the SSM software
The APEL SSM software can be installed from the yum repo or by downloading an rpm or tarball. See here for more information: SSM
Get authorised
While storage accounting publishing is still in test mode please send the host certificate DN to [1] and ask them to authorise you for storage publishing.
Configure SSM
To configure apel-ssm for sending acounting records we have to edit the file /etc/apel/sender.cfg, and modify some parameters:
- In the [broker] section, you need:
network: PROD
and not:
network: TEST-NWOB
as for initial testing. Also set:
use_ssl: false
- In the [certificates] section, you need to set the host certificate to be used by the sender:
certificate: /path/to/your/host/certificate
key: /path/to/your/key
- In the [messaging] section, you need:
destination: /queue/global.accounting.test.storage.central - as described here: https://wiki.egi.eu/wiki/APEL/SSM2Configuration.
dcache and dpm should send one StAR record per VO. Please set up a cron to run once per day.
When storage accounting moves to the production message broker network then you will need to add a servicetype to GOCDB for the host which runs SSM. The servicetype has not yet been defined but it will require the host certificate DN.