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"
(Updates in preparation for move to production) |
|||
| Line 1: | Line 1: | ||
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 [http://cds.cern.ch/record/1452920/files/GFD.201.pdf here]. | 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 [http://cds.cern.ch/record/1452920/files/GFD.201.pdf here]. | ||
EMI delivered StAR solutions for | 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 == | == Deployment Instructions == | ||
| Line 9: | Line 7: | ||
=== Get the accounting script === | === Get the accounting script === | ||
Follow the link for your product | Follow the link for your product: | ||
[[APEL/Dcache| | [[APEL/Dcache|dCache]] | ||
[https://svnweb.cern.ch/trac/lcgdm/wiki/Dpm/Dev/Recipes/EGI_APEL_Accounting DPM] | [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 | ||
On the command line which runs the script, add --site="your-GOCDB-sitename" | On the command line which runs the script, add: <code>--site="your-GOCDB-sitename"</code> | ||
=== Get the SSM software === | === Get the SSM software === | ||
The APEL SSM software can be installed from the yum repo or by downloading an | 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 === | === Get authorised === | ||
While storage accounting publishing is still in test mode please send the host certificate DN to [mailto:apel-admins@stfc.ac.uk apel-admins@stfc.ac.uk] and ask them to authorise you for storage publishing. | <strike>While storage accounting publishing is still in test mode please send the host certificate DN to </strike>[mailto:apel-admins@stfc.ac.uk <strike>apel-admins@stfc.ac.uk</strike>]<strike>and ask them to authorise you for storage publishing.</strike> | ||
To authorise your host to publish storage accounting see the section on configuring GOCDB. | |||
=== Configure GOCDB === | |||
<strike>When storage accounting moves to the production message broker network then you will need to add a service type to GOCDB for the host which runs SSM. The servicetype has not yet been defined but it will require the host certificate DN.</strike> | |||
You need to add a service endpoint for that host to GOCDB with the service type "eu.egi.storage.accounting" and the correct host certificate DN. | |||
=== Configure SSM === | === Configure SSM === | ||
To configure apel-ssm for sending | To configure apel-ssm for sending accounting records edit the file /etc/apel/sender.cfg, and modify some parameters: | ||
*In the '''<code>[broker]</code>''' section, you need: | |||
<code>network: PROD</code> | <code>network: PROD</code> | ||
<code> | (Not this: <strike> <code>network: TEST-NWOB</code></strike>) | ||
Also set: | |||
<code>use_ssl: false</code> | |||
<code> | |||
*In the '''<code>[certificates]</code>''' section, you need to set the host certificate to be used by the sender: | |||
<code>certificate: /path/to/your/host/certificate</code><br> <code>key: /path/to/your/key</code> | |||
*In the '''<code>[messaging]</code>''' section, you need: | |||
Create a cron job to run your accounting script followed by the SSM sender. We recommend that you send storage accounting data once per day. There will be a delay of up to | <code>destination: /queue/global.accounting.test.storage.central</code> - as described here: https://wiki.egi.eu/wiki/APEL/SSM2Configuration.<br> <code>path:</code> set to the directory to which the StAR records are written by your storage software. | ||
dCache and DPM should send one StAR record per VO. Please set up a cron to run once per day. | |||
== Running the Accounting Software == | |||
Create a cron job to run your accounting script followed by the SSM sender. We recommend that you send storage accounting data once per day. There will be a delay of up to 12 hours before you see the data you have sent reflected in the Accounting Portal. | |||
== Storage Data at the EGI Accounting Portal == | == Storage Data at the EGI Accounting Portal == | ||
[http://accounting-devel.egi.eu/storage.php | |||
[http://accounting-devel.egi.eu/storage.php Accounting Portal Prototype view] | |||
Revision as of 15:45, 5 July 2017
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 apel-admins@stfc.ac.ukand ask them to authorise you for storage publishing.
To authorise your host to publish storage accounting see the section on configuring GOCDB.
Configure GOCDB
When storage accounting moves to the production message broker network then you will need to add a service type to GOCDB for the host which runs SSM. The servicetype has not yet been defined but it will require the host certificate DN.
You need to add a service endpoint for that host to GOCDB with the service type "eu.egi.storage.accounting" and the correct host certificate DN.
Configure SSM
To configure apel-ssm for sending accounting records edit the file /etc/apel/sender.cfg, and modify some parameters:
- In the
[broker]section, you need:
network: PROD
(Not this: )
network: TEST-NWOB
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.
path: set to the directory to which the StAR records are written by your storage software.
dCache and DPM should send one StAR record per VO. Please set up a cron to run once per day.
Running the Accounting Software
Create a cron job to run your accounting script followed by the SSM sender. We recommend that you send storage accounting data once per day. There will be a delay of up to 12 hours before you see the data you have sent reflected in the Accounting Portal.