Difference: ApelDeployment (5 vs. 6)

Revision 62014-09-09 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 7 to 7
  Each resource centre needs to install a new node (the APEL Publisher) which receives the accounting information sent from the CE(s) by the APEL parser. Then the APEL publisher sends the data to the central database using the messaging infrastructure.
Changed:
<
<
We are testing two scenarios:
>
>
In the past months we tested two scenarios:
 
  • the accounting data are sent directly to the central databse (canonic installation)
  • the accounting data are sent to FAUST and to the central database
Added:
>
>
and we chose the second one
 

Registration

Changed:
<
<
you need to register the APEL publisher in the GOC-DB and ask the APEL team to authorize the publisher in sending the data. Follow the instructions here https://wiki.egi.eu/wiki/MAN09_Accounting_data_publishing
>
>
you need to register the APEL publisher in the GOC-DB and ask the APEL team to authorize the publisher in sending the data: do it by means of a GGUS ticket (see GGUS #106084 as example). Follow the instructions here https://wiki.egi.eu/wiki/MAN09_Accounting_data_publishing
 

APEL Publisher Installation and Configuration

Line: 23 to 26
  Don't start the apelclient and don't set it in the daily cron until you receive the OK by the APEL team.
Changed:
<
<
Remember to use the testing queue of the broker network during the first days
>
>
Remember to use the testing queue of the broker network during the first days (see again https://wiki.egi.eu/wiki/MAN09_Accounting_data_publishing): the APEL team will inform you when using the production queue.
 

Sending the data to FAUST

Changed:
<
<
in case of the second scenario, install and configure the APEL Publisher as explained in the section above, and then follow the instructions https://github.com/andreaguarise/ssm-dupl-send
>
>
In order to send the accounting data also to FAUST, after installing and configuring the APEL Publisher as explained in the section above, follow the instructions https://github.com/andreaguarise/ssm-dupl-send
  this mean that instead of apelclient script, you have to use the ssm-dupl-send.sh one
Line: 40 to 43
 destination: apel.test.input
Changed:
<
<
NOTA: per Tier1 e Tier2 verrą usata una coda dedicata, comunicata a ciascun sito. Ad esempio, nel caso di INFN-PISA, nel file faust-sender.cfg andrą impostata:
>
>
NOTA: per Tier1 e Tier2 verrą usata una coda dedicata:
destination: apel.<SITE-NAME>.input

Ad esempio, nel caso di INFN-PISA, nel file faust-sender.cfg andrą impostata:

 
destination: apel.INFN-PISA.input
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback