Difference between revisions of "APEL/SSMConfiguration"

From EGIWiki
Jump to: navigation, search
(Cloud Accounting)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
* Back to [[APEL/SSM]]
 +
 
= Configuring the SSM =
 
= Configuring the SSM =
  
The SSM has two configuration files, located in <code>$SSM_HOME/conf</code>.
+
'''The supplied configuration will send messages to the test server CPU accounting SSM.''' 
 +
 
 +
However, if you need to configure something differently, here are the instructions:
  
'''We try to make the supplied configuration work without any changes.'''  However, if you'd like to configure something differently, it should be simple.
+
== CPU Accounting in Production ==
  
== <code>ssm.cfg</code> ==
+
This should only be done, once successful testing on the test server has been done. Please contact the APEL team for the setup instructions: APEL-SUPPORT@JISCMAIL.CO.UK
  
This is in the python ConfigParser format - see http://docs.python.org/library/configparser.html.
+
== Storage Accounting ==
  
==== Things you might want to change ====
+
This is currently being tested, if you want to send StAR records to the test server you should make the following changes:
 +
 +
Update the configuration file <code>ssm.cfg</code> default location is <code>/opt/apel/ssm/conf</code>
  
 +
In the [producer] section, instead of:
 +
<code>topic: /topic/global.accounting.cpu.central</code>
 +
you need:
  
==== Things you probably don't want to change ====
+
<code>topic: /topic/global.accounting.storagetest.central</code>
  
 +
== Cloud Accounting ==
  
== <code>ssm.log.cfg</code> ==
+
This is currently being tested, if you want to send Cloud Accounting records to the test server you should make the following changes:
 +
 +
Update the configuration file <code>ssm.cfg</code> default location is <code>/opt/apel/ssm/conf</code>
  
This is in the standard python logging module's format.
+
In the [producer] section, instead of:
 +
<code>topic: /topic/global.accounting.cpu.central</code>
 +
you need:
  
==== Things you might want to change ====
+
<code>topic: /topic/global.accounting.cloudtest.CENTRAL</code>
  
# log file location:
 
## under the [handler_fileHandler] heading, change the line beginning 'args'. 
 
## The 'a' argument means that the log file is appended to.
 
## '''Beware!''' - the logging module won't expand environment variables, so you must use a full path
 
# logging levels for stomppy or SSM:
 
## under the [logger_*] headings, change the line beginning 'level'. 
 
## The possible values are DEBUG, INFO, WARN, ERROR, CRIITICAL.
 
  
==== Things you probably don't want to change ====
+
[[Category:Accounting]]
Everything else.  If you know the python logging system, you can configure the logging as you like - see http://docs.python.org/library/logging.config.html.
 

Latest revision as of 16:33, 30 October 2012

Configuring the SSM

The supplied configuration will send messages to the test server CPU accounting SSM.

However, if you need to configure something differently, here are the instructions:

CPU Accounting in Production

This should only be done, once successful testing on the test server has been done. Please contact the APEL team for the setup instructions: APEL-SUPPORT@JISCMAIL.CO.UK

Storage Accounting

This is currently being tested, if you want to send StAR records to the test server you should make the following changes:

Update the configuration file ssm.cfg default location is /opt/apel/ssm/conf

In the [producer] section, instead of: topic: /topic/global.accounting.cpu.central you need:

topic: /topic/global.accounting.storagetest.central

Cloud Accounting

This is currently being tested, if you want to send Cloud Accounting records to the test server you should make the following changes:

Update the configuration file ssm.cfg default location is /opt/apel/ssm/conf

In the [producer] section, instead of: topic: /topic/global.accounting.cpu.central you need:

topic: /topic/global.accounting.cloudtest.CENTRAL