Difference between revisions of "APEL/SSMConfiguration"

From EGIWiki
Jump to: navigation, search
(Cloud Accounting)
 
(5 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
= 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.''' 
  
'''The supplied configuration will send messages to the test server without any changes.'''  However, if you'd like to configure something differently, it should be simple.
+
However, if you need to configure something differently, here are the instructions:
  
== <code>ssm.cfg</code> ==
+
== CPU Accounting in Production ==
  
This is in the python ConfigParser format - see http://docs.python.org/library/configparser.html.
+
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
  
=== Things you might want to change ===
+
== Storage Accounting ==
  
===== Connection details =====
+
This is currently being tested, if you want to send StAR records to the test server you should make the following changes:
There are two ways the SSM can find details of a broker to connect to. One is using the EGI broker networks, the other is specifying host and port of a specific broker.
+
   
 +
Update the configuration file <code>ssm.cfg</code> default location is <code>/opt/apel/ssm/conf</code>
  
For the rest of testing and for production, we will use the broker networks.  To retrieve information about brokers in the network, we require two pieces of information:
+
In the [producer] section, instead of:
* the URL of a BDII
+
<code>topic: /topic/global.accounting.cpu.central</code>
* the name of a broker network
+
you need:
** currently available are 'PROD' and 'TEST-NWOB'
 
  
You can use SSL or username and password or both to connect to the brokers. If you are using SSL, it is important to get the port number right (it will be a different port to the non-SSL connection) - otherwise the connection may hang indefinitely.
+
<code>topic: /topic/global.accounting.storagetest.central</code>
  
We plan to use SSL for production, and for testing once the broker network have authorised the testing DNs.
+
== Cloud Accounting ==
  
===== Other =====
+
This is currently being tested, if you want to send Cloud Accounting records to the test server you should make the following changes:
# pidfile location - the pidfile is only created if the process is running continuously as a daemon
+
# Certificate location
+
Update the configuration file <code>ssm.cfg</code> default location is <code>/opt/apel/ssm/conf</code>
# messagedb location
 
  
=== Things you probably don't want to change ===
+
In the [producer] section, instead of:
# Consumer configuration - you probably don't want to receive messages
+
<code>topic: /topic/global.accounting.cpu.central</code>
# Producer configuration
+
you need:
## The default topic will be the one we're listening to
 
## The default consumer DN will be the one of our test server's certificate
 
## The ack topic can be anything, but needs to be unique to your SSM. The default is probably fine
 
  
== <code>ssm.log.cfg</code> ==
+
<code>topic: /topic/global.accounting.cloudtest.CENTRAL</code>
  
This is in the standard python logging module's format.
 
 
=== Things you might want to change ===
 
 
# 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 ===
 
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.
 
  
 
[[Category:Accounting]]
 
[[Category:Accounting]]

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