Accounting

There are two different processes handling the accounting integration:

• cASO, which connects to the OpenStack services to get the usage information, and,
• ssmsend, which sends that usage information to the central EGI accounting repository.

Installation

You can get cASO from the releases page, alternatively a container image is available in the fedcloud-caso repository.

SSM is also available in the releases or as a container in the ssm repository

Configuration

cASO configuration is stored at /etc/caso/caso.conf. Most default values should be OK, but you must set:

• site_name (line 12), with the name of your site as defined in GOCDB.

• credentials to access the OpenStack services to extract accounting data. Check cASO documentation for the expected permissions of the user configured here.

• cASO will discover the projects from OpenStack using tags and properties. You can set specific tags and properties as needed as described in the Documentation.

cASO will write records to /var/spool/apel from where ssmsend will take them.

SSM configuration is available at /etc/apel. Set the destination to eu-egi-cloud-accounting:

[messaging]
# If using AMS this is the project that SSM will connect to. Ignored for STOMP.
ams_project: accounting

# Queue to which SSM will send messages
destination: eu-egi-cloud-accounting

Other default values available in the configuration file should be ok for your site. SSM expects /etc/grid-security to contain the host certificate (/etc/grid-security/hostcert.pem), private key (/etc/grid-security/hostkey.pem) and CAs (/etc/grid-security/certificates).

Running the services

Both caso and ssmsend should run periodically, e.g. with a cron job, at least once a day. We recommend running them every 4 hours.