https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Cdelcano&feedformat=atomEGIWiki - User contributions [en]2024-03-28T14:38:19ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=APEL/Server&diff=18833APEL/Server2011-06-09T10:34:46Z<p>Cdelcano: </p>
<hr />
<div>'''This page is under construction and is not yet complete.'''<br />
<br />
== APEL STOMP Testing ==<br />
[[APEL/APELSSMExternalTesting|APEL SSM Testing]]: If you are interested in testing the new STOMP interface or want to develop your own client.<br />
<br />
== APEL Server Design ==<br />
The new APEL server is written in Python. Its design is described in [[APEL/ServerDesign|APEL Server Design]]. It has four components:<br />
* SSM<br />
* Record loader<br />
* Record publisher<br />
* Authentication<br />
<br />
== APEL Message Format ==<br />
* [[APEL/MessageFormat|APEL Message Format]]<br />
<br />
== SSM ==<br />
The SSM is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.<br />
<br />
* [[APEL/SSMOverview|SSM Overview]]<br />
* [[APEL/SSMInstallation|SSM installation instructions]]<br />
<br />
== Record loader ==<br />
This has the fairly simple job of taking the received messages and putting them in the database.<br />
<br />
== Record publisher ==<br />
This takes the information from a database and produces messages.<br />
<br />
== Authentication ==<br />
This verifies that the senders of the messages via the SSM are known to APEL.<br />
<br />
* [[APEL/UsingAuth]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17768APEL/SSMInstallation2011-05-20T14:00:23Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
<br />
=== Prerequisites ===<br />
* python:<br />
** we use 2.4.3, the standard version with SL5<br />
* stomppy: the python STOMP library<br />
** the version in the epel repository (3.0.3) conflicts with python 2.4<br />
** We have been using 2.0.2; the version in the EGEE SA1 repository is 2.0.4 and this works as well<br />
* openssl:<br />
** we use 0.9.8, the standard version with SL5<br />
* lcg-CA<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
* Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
<br />
Your SSM '''encrypts''' using our certificate. Before it does this, it tries to verify it against the CA certificates in <code>/etc/grid-security/certificates</code>. To ensure this works fine, install the lcg-CA package using yum.<br />
<br />
Your SSM uses your host certificate to '''sign''' the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17767APEL/SSMInstallation2011-05-20T13:35:13Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
<br />
=== Prerequisites ===<br />
* python:<br />
** we use 2.4.3, the standard version with SL5<br />
* stomppy: the python STOMP library<br />
** the version in the epel repository (3.0.3) conflicts with python 2.4<br />
** We have been using 2.0.2; the version in the EGI jra1 repository is 2.0.4 and this works as well<br />
* openssl:<br />
** we use 0.9.8, the standard version with SL5<br />
* lcg-CA<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
* Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
<br />
Your SSM '''encrypts''' using our certificate. Before it does this, it tries to verify it against the CA certificates in <code>/etc/grid-security/certificates</code>. To ensure this works fine, install the lcg-CA package using yum.<br />
<br />
Your SSM uses your host certificate to '''sign''' the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17766APEL/SSMInstallation2011-05-20T13:34:49Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
<br />
=== Prerequisites ===<br />
* python:<br />
** we use 2.4.3, the standard version with SL5<br />
* stomppy: the python STOMP library<br />
** the version in the epel repository (3.0.3) conflicts with python 2.4<br />
** We have been using 2.0.2; the version in the EGI jra1 repository is 2.0.4 and this works as well<br />
* openssl:<br />
** we use 0.9.8, the standard version with SL5<br />
* lcg-CA<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
* Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
<br />
Your SSM '''encrypts''' using our certificate. Before it does this, it tries to verify it against the CA certificates in <code>/etc/grid-security/certificates</code>. To ensure this works fine, install the lcg-CA package using yum.<br />
<br />
The SSM uses your host certificate to sign the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17765APEL/SSMInstallation2011-05-20T13:21:39Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
<br />
=== Prerequisites ===<br />
* python:<br />
** we use 2.4.3, the standard version with SL5<br />
* stomppy: the python STOMP library<br />
** the version in the epel repository (3.0.3) conflicts with python 2.4<br />
** We have been using 2.0.2; the version in the EGI jra1 repository is 2.0.4 and this works as well<br />
* openssl:<br />
** we use 0.9.8, the standard version with SL5<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
* Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
The SSM uses your host certificate to sign the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17764APEL/SSMInstallation2011-05-20T13:21:16Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
<br />
=== Prerequisites ===<br />
* python:<br />
** we use 2.4.3, the standard version with SL5<br />
* stomppy: the python STOMP library<br />
** the version in the epel repository conflicts with python 2.4<br />
** We have been using 2.0.2; the version in the EGI jra1 repository is 2.0.4 and this works as well<br />
* openssl:<br />
** we use 0.9.8, the standard version with SL5<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
* Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
The SSM uses your host certificate to sign the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17760APEL/SSMInstallation2011-05-20T13:13:56Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Certificates ===<br />
The SSM uses your host certificate to sign the messages it sends. When our version of the SSM receives a message, it retrieves your certificate and attempts to verify it against the CA certificates in the lcg-CA rpm.<br />
<br />
If your host certificate is not signed by one of these CAs, discuss this with apel-admins@mailtalk.ac.uk.<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/SSMInstallation&diff=17759APEL/SSMInstallation2011-05-20T13:09:02Z<p>Cdelcano: </p>
<hr />
<div>The Secure Stomp Messenger (SSM) is used to transmit arbitrary messages using the STOMP protocol. For a description, see [[APEL/SSMOverview|SSM Overview]]. <br />
<br />
'''PLEASE NOTE THIS IS NOT PRODUCTION-LEVEL SOFTWARE''' '''This software is distributed as an example and for testing'''. Expect bugs, and if you find any please let us know about them: apel-admins@mailtalk.ac.uk.<br />
<br />
== ssm-0.2 ==<br />
<br />
=== Installation ===<br />
<br />
You can't currently download a version of the code, but if you would like a zip file please email apel-admins@mailtalk.ac.uk and we will send you a version. <br />
<br />
Unzip the file into a directory, which is denoted as $SSM_HOME below.<br />
<br />
=== Configuration ===<br />
The environment variable SSM_HOME must be set appropriately:<br />
* <code>export SSM_HOME=<directory></code><br />
<br />
There are two other configuration files.<br />
<br />
==== <code>$SSM_HOME/conf/ssm.cfg</code> ====<br />
'''The default values should suffice to send messages to the APEL test system''', but there are notes about the file below.<br />
<br />
This SSM will be a producer, so the consumer section can be left out or given dummy values - it doesn't hurt. The file is well commented, it should be straightforward. In this file configure:<br />
<br />
* the broker to use (host: dev.msg.cern.ch port: 6163 for testing purposes)<br />
* the message store (suggest: $SSM_HOME/messages)<br />
* the certificate/key settings and CA directory<br />
* the topic to send to (/topic/grid.accounting.cpuTest.CENTRAL is being used for testing)<br />
* The DN of the consumer that messages are sent to(<code>consumerDN: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=rap.esc.rl.ac.uk/emailAddress=sct certificates@rl.ac.uk</code>)<br />
<br />
* The acknowledgment topic; a sensible default is already used.<br />
==== <code>$SSM_HOME/conf/ssm.log.cfg</code> ====<br />
This is the configuration for the logging. ''''You need to change one thing:'''<br />
* In the section [handler_fileHander], specify the path to a log file. The directory must exist. You need a full path - you can't use $SSM_HOME.<br />
* Example: <code>args=('/home/apel/ssm/ssm.log', 'a')</code><br />
<br />
=== Running the SSM ===<br />
<br />
* <code>cd $HOME/bin</code><br />
* <code>./run-ssm</code><br />
<br />
Once the SSM is running, it will send messages from the directory <code>$SSM_HOME/messages/outgoing</code> automatically. All you need to do is to put the messages in this directory. If they don't disappear, check the log file to see what it says, check your configuration, then send us an email.</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16707APEL/MessageFormat2011-05-03T12:52:28Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<pre>APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
| Key <br />
| Value <br />
| Description <br />
| Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month of summary <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year of summary <br />
| Yes<br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| VO <br />
| String <br />
| User's VO <br />
| <br />
|-<br />
| Group <br />
| String <br />
| User's VOMS group <br />
| <br />
|-<br />
| Role <br />
| String <br />
| User's VOMS&nbsp;role <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wall clock time for the job <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedCpuDuration <br />
| int <br />
| Normalised CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedWallDuration <br />
| int <br />
| Normalised Wall clock time for the job <br />
| Yes<br />
|-<br />
| NumberOfJobs <br />
| int <br />
| Total number of jobs <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
&nbsp; <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'. <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.<br />
<br />
=== Example Message ===<br />
<pre>APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB&nbsp;sitename <br />
| Yes<br />
|-<br />
| NJobs <br />
| int <br />
| Total number of jobs for that month <br />
| Yes<br />
|-<br />
| NDays <br />
| int <br />
| Number of days between earliest and latest job in month <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test.<br />
<br />
=== Example Message ===<br />
<pre>APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
</pre></div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16702APEL/MessageFormat2011-05-03T12:38:51Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<pre>APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
| Key <br />
| Value <br />
| Description <br />
| Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month of summary <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year of summary <br />
| Yes<br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| VO <br />
| String <br />
| User's VO <br />
| <br />
|-<br />
| Group <br />
| String <br />
| User's VOMS group <br />
| <br />
|-<br />
| Role <br />
| String <br />
| User's VOMS&nbsp;role <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wall clock time for the job <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedCpuDuration <br />
| int <br />
| Normalised CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedWallDuration <br />
| int <br />
| Normalised Wall clock time for the job <br />
| Yes<br />
|-<br />
| NumberOfJobs <br />
| int <br />
| Total number of jobs <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
&nbsp; <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'. <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.<br />
<br />
=== Example Message ===<br />
<pre>APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB&nbsp;sitename <br />
| Yes<br />
|-<br />
| NJobs <br />
| int <br />
| Total number of jobs for that month <br />
| Yes<br />
|-<br />
| NDays <br />
| int <br />
| Number of days between earliest and latest job in month <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test.<br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16699APEL/MessageFormat2011-05-03T12:21:56Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<pre>APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
| Key <br />
| Value <br />
| Description <br />
| Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month of summary <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year of summary <br />
| Yes<br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| VO <br />
| String <br />
| User's VO <br />
| <br />
|-<br />
| Group <br />
| String <br />
| User's VOMS group <br />
| <br />
|-<br />
| Role <br />
| String <br />
| User's VOMS&nbsp;role <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wall clock time for the job <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedCpuDuration <br />
| int <br />
| Normalised CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedWallDuration <br />
| int <br />
| Normalised Wall clock time for the job <br />
| Yes<br />
|-<br />
| NumberOfJobs <br />
| int <br />
| Total number of jobs <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
&nbsp; <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'. <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.<br />
<br />
=== Example Message ===<br />
<pre>APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16698APEL/MessageFormat2011-05-03T12:19:44Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<pre>APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
| Key <br />
| Value <br />
| Description <br />
| Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| Month <br />
| int <br />
| Month of summary <br />
| Yes<br />
|-<br />
| Year <br />
| int <br />
| Year of summary <br />
| Yes<br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| VO <br />
| String <br />
| User's VO <br />
| <br />
|-<br />
| Group <br />
| String <br />
| User's VOMS group <br />
| <br />
|-<br />
| Role <br />
| String <br />
| User's VOMS&nbsp;role <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wall clock time for the job <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedCpuDuration <br />
| int <br />
| Normalised CPU&nbsp;time for the job <br />
| Yes<br />
|-<br />
| NormalisedWallDuration <br />
| int <br />
| Normalised Wall clock time for the job <br />
| Yes<br />
|-<br />
| NumberOfJobs <br />
| int <br />
| Total number of jobs <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
&nbsp; <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:''' <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'. <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.<br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16697APEL/MessageFormat2011-05-03T12:09:21Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<pre>APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
</pre><br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || Month || int || Month of summary || Yes || || Year || int || Year of summary || Yes || ||&nbsp;!GlobalUserName || String || User's X.509 DN || || || VO || String || User's VO || || || Group || String || User's VOMS Group || || || Role || String ||User's VOMS Role || || ||&nbsp;!WallDuration || int || clock time for the job || Yes || ||&nbsp;!CpuDuration || int || CPU time for the job || || ||&nbsp;!NormalisedCpuDuration || int || Normalised CPU time for the job || Yes || ||&nbsp;!NormalisedWallDuration || int || Normalised Wall clock time || Yes || ||&nbsp;!NumberOfJobs || int || Total number of jobs || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'.[[BR]] <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.[[BR]] <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16696APEL/MessageFormat2011-05-03T12:06:43Z<p>Cdelcano: </p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> <br />
<br />
<br> '''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
}}}<br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || Month || int || Month of summary || Yes || || Year || int || Year of summary || Yes || ||&nbsp;!GlobalUserName || String || User's X.509 DN || || || VO || String || User's VO || || || Group || String || User's VOMS Group || || || Role || String ||User's VOMS Role || || ||&nbsp;!WallDuration || int || clock time for the job || Yes || ||&nbsp;!CpuDuration || int || CPU time for the job || || ||&nbsp;!NormalisedCpuDuration || int || Normalised CPU time for the job || Yes || ||&nbsp;!NormalisedWallDuration || int || Normalised Wall clock time || Yes || ||&nbsp;!NumberOfJobs || int || Total number of jobs || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'.[[BR]] <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.[[BR]] <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16695APEL/MessageFormat2011-05-03T12:05:31Z<p>Cdelcano: /* Description */</p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="600"<br />
|-<br />
! scope="col" | Key <br />
! scope="col" | Value <br />
! scope="col" | Description <br />
! scope="col" | Mandatory<br />
|-<br />
| Site <br />
| String <br />
| GOCDB sitename <br />
| Yes<br />
|-<br />
| SubmitHost <br />
| String <br />
| Head node where the job was submitted <br />
| Yes<br />
|-<br />
| LocalJobID <br />
| String <br />
| Batch System Job ID <br />
| Yes<br />
|-<br />
| LocalUserID <br />
| String <br />
| Local username <br />
| <br />
|-<br />
| GlobalUserName <br />
| String <br />
| User's X509 DN <br />
| <br />
|-<br />
| UserFQAN <br />
| String <br />
| User's VOMS&nbsp;attributes <br />
| <br />
|-<br />
| WallDuration <br />
| int <br />
| Wallclock time for the job (seconds) <br />
| Yes<br />
|-<br />
| CpuDuration <br />
| int <br />
| CPU&nbsp;time for the job (seconds) <br />
| Yes<br />
|-<br />
| Processors <br />
| int <br />
| Number of processors <br />
| <br />
<br> <br />
<br />
|-<br />
| NodeCount <br />
| int <br />
| Number of nodes <br />
| <br />
|-<br />
| StartTime <br />
| int <br />
| Start time of the job (epoch) <br />
| Yes<br />
|-<br />
| EndTime <br />
| int <br />
| Stop time of the job (epoch) <br />
| <br />
|-<br />
| MemoryReal <br />
| int <br />
| Memory consumed by job (kbytes) <br />
| <br />
|-<br />
| MemoryVirtual <br />
| int <br />
| Virtual memory consumed by job&nbsp;(kbytes) <br />
| <br />
|-<br />
| ScalingFactorUnit <br />
| String <br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom <br />
| Yes<br />
|-<br />
| ScalingFactor <br />
| double <br />
| Value of either HepSpec, SpecInt or custom <br />
| Yes<br />
|}<br />
<br />
<br />
<br />
<br />
'''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'.<br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || Month || int || Month of summary || Yes || || Year || int || Year of summary || Yes || ||&nbsp;!GlobalUserName || String || User's X.509 DN || || || VO || String || User's VO || || || Group || String || User's VOMS Group || || || Role || String ||User's VOMS Role || || ||&nbsp;!WallDuration || int || clock time for the job || Yes || ||&nbsp;!CpuDuration || int || CPU time for the job || || ||&nbsp;!NormalisedCpuDuration || int || Normalised CPU time for the job || Yes || ||&nbsp;!NormalisedWallDuration || int || Normalised Wall clock time || Yes || ||&nbsp;!NumberOfJobs || int || Total number of jobs || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'.[[BR]] <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.[[BR]] <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16694APEL/MessageFormat2011-05-03T12:04:33Z<p>Cdelcano: /* New Message Format */</p>
<hr />
<div>= APEL Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="200"<br />
|-<br />
! scope="col" | Key<br />
! scope="col" | Value<br />
! scope="col" | Description<br />
! scope="col" | Mandatory<br />
|-<br />
| Site<br />
| String<br />
| GOCDB sitename<br />
| Yes<br />
|-<br />
| SubmitHost<br />
| String<br />
| Head node where the job was submitted<br />
| Yes<br />
|-<br />
| LocalJobID<br />
| String<br />
| Batch System Job ID<br />
| Yes<br />
|-<br />
| LocalUserID<br />
| String<br />
| Local username<br />
| <br />
|-<br />
| GlobalUserName<br />
| String<br />
| User's X509 DN<br />
| <br />
|-<br />
| UserFQAN<br />
| String<br />
| User's VOMS&nbsp;attributes<br />
| <br />
|-<br />
| WallDuration<br />
| int<br />
| Wallclock time for the job (seconds)<br />
| Yes<br />
|-<br />
| CpuDuration<br />
| int<br />
| CPU&nbsp;time for the job (seconds)<br />
| Yes<br />
|-<br />
| Processors<br />
| int<br />
| Number of processors<br />
| <br />
<br />
<br />
|-<br />
| NodeCount<br />
| int<br />
| Number of nodes<br />
| <br />
|-<br />
| StartTime<br />
| int<br />
| Start time of the job (epoch)<br />
| Yes<br />
|-<br />
| EndTime<br />
| int<br />
| Stop time of the job (epoch)<br />
| <br />
|-<br />
| MemoryReal<br />
| int<br />
| Memory consumed by job (kbytes)<br />
| <br />
|-<br />
| MemoryVirtual<br />
| int<br />
| Virtual memory consumed by job&nbsp;(kbytes)<br />
| <br />
|-<br />
| ScalingFactorUnit<br />
| String<br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom<br />
| Yes<br />
|-<br />
| ScalingFactor<br />
| double<br />
| Value of either HepSpec, SpecInt or custom<br />
| Yes<br />
|}<br />
<br />
'''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || Month || int || Month of summary || Yes || || Year || int || Year of summary || Yes || ||&nbsp;!GlobalUserName || String || User's X.509 DN || || || VO || String || User's VO || || || Group || String || User's VOMS Group || || || Role || String ||User's VOMS Role || || ||&nbsp;!WallDuration || int || clock time for the job || Yes || ||&nbsp;!CpuDuration || int || CPU time for the job || || ||&nbsp;!NormalisedCpuDuration || int || Normalised CPU time for the job || Yes || ||&nbsp;!NormalisedWallDuration || int || Normalised Wall clock time || Yes || ||&nbsp;!NumberOfJobs || int || Total number of jobs || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'.[[BR]] <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.[[BR]] <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/MessageFormat&diff=16693APEL/MessageFormat2011-05-03T12:03:46Z<p>Cdelcano: Created page with '= New Message Format = This describes a new message format for getting data between the APEL clients and the server. == Job Records == A message can contain multiple record…'</p>
<hr />
<div>= New Message Format =<br />
<br />
This describes a new message format for getting data between the APEL clients and the server. <br />
<br />
== Job Records ==<br />
<br />
A message can contain multiple records. Different records must be separated by the end of record marker (%%). <br />
<br />
=== Description ===<br />
<br />
'''Header''' APEL-individual-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" align="left" width="200"<br />
|-<br />
! scope="col" | Key<br />
! scope="col" | Value<br />
! scope="col" | Description<br />
! scope="col" | Mandatory<br />
|-<br />
| Site<br />
| String<br />
| GOCDB sitename<br />
| Yes<br />
|-<br />
| SubmitHost<br />
| String<br />
| Head node where the job was submitted<br />
| Yes<br />
|-<br />
| LocalJobID<br />
| String<br />
| Batch System Job ID<br />
| Yes<br />
|-<br />
| LocalUserID<br />
| String<br />
| Local username<br />
| <br />
|-<br />
| GlobalUserName<br />
| String<br />
| User's X509 DN<br />
| <br />
|-<br />
| UserFQAN<br />
| String<br />
| User's VOMS&nbsp;attributes<br />
| <br />
|-<br />
| WallDuration<br />
| int<br />
| Wallclock time for the job (seconds)<br />
| Yes<br />
|-<br />
| CpuDuration<br />
| int<br />
| CPU&nbsp;time for the job (seconds)<br />
| Yes<br />
|-<br />
| Processors<br />
| int<br />
| Number of processors<br />
| <br />
<br />
<br />
|-<br />
| NodeCount<br />
| int<br />
| Number of nodes<br />
| <br />
|-<br />
| StartTime<br />
| int<br />
| Start time of the job (epoch)<br />
| Yes<br />
|-<br />
| EndTime<br />
| int<br />
| Stop time of the job (epoch)<br />
| <br />
|-<br />
| MemoryReal<br />
| int<br />
| Memory consumed by job (kbytes)<br />
| <br />
|-<br />
| MemoryVirtual<br />
| int<br />
| Virtual memory consumed by job&nbsp;(kbytes)<br />
| <br />
|-<br />
| ScalingFactorUnit<br />
| String<br />
| HepSpec &#124;&nbsp;SpecInt &#124; custom<br />
| Yes<br />
|-<br />
| ScalingFactor<br />
| double<br />
| Value of either HepSpec, SpecInt or custom<br />
| Yes<br />
|}<br />
<br />
<br />
<br />
<br><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''End of record:''' &nbsp;%% <br />
<br />
'''Notes:''' If&nbsp;!ScalingFactorUnit/Value is not available it should be set to: <br />
<br />
ScalingFactorUnit = 'custom'<br />
ScalingFactor = 1<br />
<br />
If&nbsp;!GlobalUserName or&nbsp;!UserFQAN is not published, the value for these fields on the server will be set to 'None'. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-individual-job-message: v0.1<br />
Site: RAL-LCG2<br />
SubmitHost: ce01.ncg.ingrid.pt:2119/jobmanager-lcgsge-atlasgrid<br />
LocalJobID: 31564872<br />
LocalUserID: atlasprd019<br />
GlobalUserName: /C=whatever/D=someDN<br />
UserFQAN: /voname/Role=NULL/Capability=NULL<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
Processors: 2<br />
NodeCount: 2<br />
StartTime: 1234567890<br />
EndTime: 1234567899<br />
MemoryReal: 1000<br />
MemoryVirtual: 2000<br />
ScalingFactorUnit: SpecInt2000<br />
ScalingFactor: 1000<br />
%%<br />
...another job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Job Records ==<br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-summary-job-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || Month || int || Month of summary || Yes || || Year || int || Year of summary || Yes || ||&nbsp;!GlobalUserName || String || User's X.509 DN || || || VO || String || User's VO || || || Group || String || User's VOMS Group || || || Role || String ||User's VOMS Role || || ||&nbsp;!WallDuration || int || clock time for the job || Yes || ||&nbsp;!CpuDuration || int || CPU time for the job || || ||&nbsp;!NormalisedCpuDuration || int || Normalised CPU time for the job || Yes || ||&nbsp;!NormalisedWallDuration || int || Normalised Wall clock time || Yes || ||&nbsp;!NumberOfJobs || int || Total number of jobs || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
If&nbsp;!GlobalUserName, VO, Role or Group are not published, the value for these fields on the server will be set to 'None'.[[BR]] <br />
<br />
A single job record must only be included in one summary record to avoid duplication of data.[[BR]] <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-summary-job-message: v0.1<br />
Site: RAL-LCG2<br />
Month: 3<br />
Year: 2010<br />
GlobalUserName: /C=whatever/D=someDN<br />
VO: atlas<br />
Group: /atlas<br />
Role: Role=production<br />
WallDuration: 234256<br />
CpuDuration: 2345<br />
NormalisedCpuDuration: 2500<br />
NormalisedWallDuration: 244435<br />
NumberOfJobs: 100<br />
%%<br />
...another summary job record...<br />
%%<br />
...<br />
%%<br />
}}} <br />
<br />
== Summary Sync Records ==<br />
<br />
The summary Sync records are used for the creation of the apel-sync Nagios test. It is a mechanism for the central APEL server to know the number of records that each site is storing locally. <br />
<br />
=== Description ===<br />
<br />
'''Header''': APEL-sync-message: v0.1 <br />
<br />
The header only appears once at the top of each message. It defines the type of record and the schema version. || '''Key''' || '''Value''' || '''Description''' || '''Mandatory''' || || Site || String || GOCDB/official name of the site where the job run || Yes || || NJobs || int || Total number of jobs for that month || Yes || || NDays || int || Number of days between earliest and latest job in month || Yes || ||Month || int || Month || Yes || ||Year || int ||Year || Yes || <br />
<br />
<br> '''End of record:'''&nbsp;%% <br />
<br />
'''Notes:'''[[BR]] <br />
<br />
Each record indicates the number of jobs run on the site per month. This data is used to create the Nagios apel-sync test. <br />
<br />
=== Example Message ===<br />
<br />
{{{<br />
APEL-sync-message: v0.1<br />
Site: RAL-LCG2<br />
NJobs: 3479<br />
NDays: 29<br />
Month: 1<br />
Year: 2010<br />
%%<br />
...another sync record...<br />
%%<br />
...<br />
%%<br />
}}}</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/Server&diff=16680APEL/Server2011-05-03T10:20:34Z<p>Cdelcano: </p>
<hr />
<div>'''This page is under construction and is not yet complete.'''<br />
<br />
== APEL Server Design ==<br />
The new APEL server is written in Python. Its design is described in [[APEL/ServerDesign|APEL Server Design]]. It has four components:<br />
* SSM<br />
* Record loader<br />
* Record publisher<br />
* Authentication<br />
<br />
== APEL Message Format ==<br />
* [[APEL/MessageFormat|APEL Message Format]]<br />
<br />
== SSM ==<br />
The SSM is the messaging system used by APEL to transmit messages. It is written in Python and uses the STOMP protocol.<br />
<br />
* [[APEL/SSMOverview|SSM Overview]]<br />
* [[APEL/SSMInstallation|SSM installation instructions]]<br />
<br />
== Record loader ==<br />
This has the fairly simple job of taking the received messages and putting them in the database.<br />
<br />
== Record publisher ==<br />
This takes the information from a database and produces messages.<br />
<br />
== Authentication ==<br />
This verifies that the senders of the messages via the SSM are known to APEL.<br />
<br />
* [[APEL/UsingAuth]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15530APEL2011-04-13T10:51:19Z<p>Cdelcano: /* Links */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Tests|APEL Nagios Monitoring]]<br />
* [https://edms.cern.ch/document/726137 Operational Accounting Portal Description]<br />
<br />
== Support ==<br />
* Please use [https://gus.fzk.de/pages/home.php GGUS] to report any problems and provide the following information:<br />
** Your Site Name<br />
** A description of the problem<br />
** Any relevant log file<br />
** The versions of the APEL software installed<br />
* Other questions/comments about the APEL system can be sent to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* For APEL Client issues check the [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient#Documentation documentation]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15529APEL2011-04-13T10:51:03Z<p>Cdelcano: /* Links */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Encryption|Apel Encryption]]<br />
* [[APEL/Tests|APEL Nagios Monitoring]]<br />
* [https://edms.cern.ch/document/726137 Operational Accounting Portal Description]<br />
<br />
== Support ==<br />
* Please use [https://gus.fzk.de/pages/home.php GGUS] to report any problems and provide the following information:<br />
** Your Site Name<br />
** A description of the problem<br />
** Any relevant log file<br />
** The versions of the APEL software installed<br />
* Other questions/comments about the APEL system can be sent to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* For APEL Client issues check the [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient#Documentation documentation]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/Tests&diff=15528APEL/Tests2011-04-13T10:49:46Z<p>Cdelcano: /* APEL Nagios Monitoring */</p>
<hr />
<div>== APEL Nagios Monitoring ==<br />
<br />
Two APEL accounting tests are provided, APEL-Pub and APEL-Sync. Both tests run centrally in the APEL server and query the central APEL database for publishing details of every production/certified site registered in GOCDB with at least one CE defined as an "APEL" service type.<br />
<br />
These results are then sent as Nagios metrics via the network of ActiveMQ brokers to be consumed by the ROC Nagios instances.<br />
<br />
=== APEL-Pub ===<br />
<br />
The APEL-Pub test checks for the latest successfull published date for each site. The test can return the following values:<br />
<br />
* OK: The most recent record published by the site is 7 or less days old.<br />
* WARNING: The most recent record published by the site is between 8 and 31 days old.<br />
* ERROR: The site hasn't published any records for more than 31 days.<br />
<br />
=== APEL-Sync ===<br />
<br />
The APEL-Sync test compares the number of records in the site's local database with the number of records published to the central APEL database by month. The test can return the following values:<br />
<br />
* OK: The difference between local and central number of records is less than 10.<br />
* WARNING: The difference between local and central number of records is between 10 and 100.<br />
* ERROR: The difference between local and central number of records is greater than 100.<br />
<br />
The results of the tests are also published to the following webpages: http://goc-accounting.grid-support.ac.uk/rss/SITENAME_Pub.html and http://goc-accounting.grid-support.ac.uk/rss/SITENAME_Sync.html</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL/Tests&diff=15526APEL/Tests2011-04-13T10:47:07Z<p>Cdelcano: /* APEL Nagios Monitoring */</p>
<hr />
<div>== APEL Nagios Monitoring ==</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15521APEL2011-04-13T10:35:09Z<p>Cdelcano: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Encryption|Apel Encryption]]<br />
* [[APEL/Tests|APEL Nagios Monitoring]]<br />
<br />
== Support ==<br />
* Please use [https://gus.fzk.de/pages/home.php GGUS] to report any problems and provide the following information:<br />
** Your Site Name<br />
** A description of the problem<br />
** Any relevant log file<br />
** The versions of the APEL software installed<br />
* Other questions/comments about the APEL system can be sent to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* For APEL Client issues check the [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient#Documentation documentation]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15520APEL2011-04-13T10:34:49Z<p>Cdelcano: /* Support */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Encryption|Apel Encryption]]<br />
* [[APEL/Tests|APEL Nagios Monitoring]]<br />
<br />
== Support ==<br />
* Please use [https://gus.fzk.de/pages/home.php GGUS] to report any problems and provide the following information:<br />
** Your Site Name<br />
** A description of the problem<br />
** Any relevant log file<br />
** The versions of the APEL software installed<br />
* Other questions/comments about the APEL system can be sent to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* For APEL Client issues check the [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient#Documentation documentation]<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15518APEL2011-04-13T10:31:30Z<p>Cdelcano: /* Links */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Encryption|Apel Encryption]]<br />
* [[APEL/Tests|APEL Nagios Monitoring]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15517APEL2011-04-13T10:27:52Z<p>Cdelcano: /* APEL Information */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== Links ==<br />
* [http://accounting.egi.eu/ EGI Accounting Portal]<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELFAQ APEL FAQ and Troubleshooting]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15516APEL2011-04-13T10:25:44Z<p>Cdelcano: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== APEL Information ==<br />
* [[APEL/FAQ|Frequently Asked Questions]]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [http://accounting.egi.eu/ View Data on Portal]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15513APEL2011-04-13T10:17:30Z<p>Cdelcano: /* Components */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [https://twiki.cern.ch/twiki/bin/view/EMI/APELClient APEL Client]<br />
* APEL Server<br />
<br />
== APEL Information ==<br />
* [[APEL/FAQ|Frequently Asked Questions]]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [http://accounting.egi.eu/ View Data on Portal]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]<br />
<br />
== Benchmarking ==<br />
<br />
* [[HEP_SPEC06 | see this link for more information]]<br />
<br />
<br />
* The old CPU_Benchmarking_HowTo on the GOCWIKI is obsolete.<br />
----------</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15512APEL2011-04-13T10:17:01Z<p>Cdelcano: /* Components */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [APEL Client:https://twiki.cern.ch/twiki/bin/view/EMI/APELClient]<br />
* APEL Server<br />
<br />
== APEL Information ==<br />
* [[APEL/FAQ|Frequently Asked Questions]]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [http://accounting.egi.eu/ View Data on Portal]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]<br />
<br />
== Benchmarking ==<br />
<br />
* [[HEP_SPEC06 | see this link for more information]]<br />
<br />
<br />
* The old CPU_Benchmarking_HowTo on the GOCWIKI is obsolete.<br />
----------</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15511APEL2011-04-13T10:16:00Z<p>Cdelcano: /* Components */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Components ==<br />
<br />
* [[https://twiki.cern.ch/twiki/bin/view/EMI/APELClient][APEL Client]]<br />
* APEL Server<br />
<br />
== APEL Information ==<br />
* [[APEL/FAQ|Frequently Asked Questions]]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [http://accounting.egi.eu/ View Data on Portal]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]<br />
<br />
== Benchmarking ==<br />
<br />
* [[HEP_SPEC06 | see this link for more information]]<br />
<br />
<br />
* The old CPU_Benchmarking_HowTo on the GOCWIKI is obsolete.<br />
----------</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=APEL&diff=15510APEL2011-04-13T10:14:49Z<p>Cdelcano: /* Description*/</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
== Description ==<br />
<br />
APEL is an accounting tool that collects accounting data from sites participating in the EGI and WLCG infrastructures as well as from sites belonging to other Grid organisations that are collaborating with EGI, including OSG, NorduGrid and INFN.<br />
<br />
The accounting information is gathered from different sensors into to a central accounting database where it is processed to generate statistical summaries that are available through the EGI/WLCG Accounting Portal. <br />
<br />
Statistics are available for view in different detail by Users, VO Managers, Site Administrators and anonymous users according to well defined access rights.<br />
<br />
== Future Plans ==<br />
* [[APEL/Dev|APEL Development]]<br />
<br />
== APEL Information ==<br />
* [[APEL/FAQ|Frequently Asked Questions]]<br />
* [[APEL/Tests|APEL Nagios Tests]]<br />
* [http://accounting.egi.eu/ View Data on Portal]<br />
* [[APEL/Encryption|Apels Encryption Algorithm]]<br />
* [[APEL/Misc|Miscellaneous]]<br />
<br />
== Support ==<br />
* Installing a glite-APEL node on [[APEL/glite-APEL|glite-APEL]]<br />
* Check APEL server status on the [[APEL/Status|Status page]]<br />
* Please use the [https://gus.fzk.de/pages/home.php GGUS ticketing system] and provide the following information<br />
** Your siteName<br />
** A description of the problem<br />
** Any relevant log file<br />
* Any questions/comments about APEL / EGI CPU Accounting can be forwarded to [mailto:APEL-SUPPORT_AT_JISCMAIL.AC.UK APEL-SUPPORT_AT_JISCMAIL.AC.UK]<br />
* BetaTesting<br />
<br />
== Development ==<br />
* [[APEL/gliteAPELTestPlan|glite-APEL test plan]]<br />
* [[APEL/APELParserTestPlan|APEL parser test plan]]<br />
<br />
== Benchmarking ==<br />
<br />
* [[HEP_SPEC06 | see this link for more information]]<br />
<br />
<br />
* The old CPU_Benchmarking_HowTo on the GOCWIKI is obsolete.<br />
----------</div>Cdelcanohttps://wiki.egi.eu/w/index.php?title=GGUS:APEL_client_%26_Accounting_Repository_FAQ&diff=14621GGUS:APEL client & Accounting Repository FAQ2011-03-29T07:52:54Z<p>Cdelcano: </p>
<hr />
<div>{{GGUS-FAQ<br />
|Unit= APEL<br />
|Interface= H<br />
|Updated= 2011-02-11 <!-- 18500_FAQ_for_apel.docx --><br />
|purpose=To deal with operational and deployment issues with the APEL accounting software.<br />
|components=Glite-APEL, apel-parsers, and the central APEL repository.<br />
|assigned by=TPM or others, no special permissions. <br />
|solved by=Operational and deployment issues are solved in this SU. Suspected software bugs in glite-APEL will be assigned to [[GGUS:APEL-EMI FAQ|APEL-EMI SU]].<br />
|responsible=The developer team based at RAL (UK).<br />
|documentation=Development, FAQ and APEL encryption information is available in<br />
https://wiki.egi.eu/wiki/APEL<br />
|sortname=Apel<br />
}}</div>Cdelcano