Tags:
, view all tags

APEL Deployment

We are changing the accounting system used in our infrastructure, from DGAS to APEL and the procedure is quite simple.

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.

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

and we chose the second one

Registration

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

Follow the EMI3 generic installation guide and the APEL one https://twiki.cern.ch/twiki/pub/EMI/EMI3APELClient/APEL_Publisher_System_Administrator_Guide.pdf

Don't start the apelclient and don't set it in the daily cron until you receive the OK by the APEL team.

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

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

Among the important paramaters to set in the faust-sender.cfg there are the following ones:

host: dgas-broker.to.infn.it
port: 61613

use_ssl: false

destination: apel.input

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

  • Example of the cron:
cat /etc/cron.d/ssm-dupl-send 
# Run APEL client once daily
05 01 * * * root /root/bin/ssm-dupl-send.sh

APEL Parser Installation and Configuration

Install and configure the APEL parser on each computing element of your resource centre.

Follow the EMI3 generic installation guide and the APEL one https://twiki.cern.ch/twiki/pub/EMI/EMI3APELClient/APEL_Parsers_System_Administrator_Guide.pdf

Don't make parse the blah and batch server logs older than one month before to the current one.

you can launch the apelparser script after the setting-up of the apelclient database

an example of the cron:

cat /etc/cron.d/apelparser 
# Run APEL parser once daily
04 22 * * * root /usr/bin/apelparser

Bug in APEL 1.2.1 - Upgrade

The latest version of the APEL software (version 1.2.1*) contains a bug in the parser which prevents it from working in the most common cases: it is unable to open uncompressed accounting logs for parsing.

Sites with this problem will have version 1.2.1 installed and see many log messages like this:

2014-08-11 12:54:11,819 - parser - ERROR - Cannot open file 
blahp.log-20140811: Not a gzipped file
in their parser log file - usually at /var/log/apel/parser.log.

Sites who have installed version 1.2.1 should upgrade to 1.2.2 immediately.

- SL5:

https://github.com/apel/apel/releases/download/1.2.2-1/apel-lib-1.2.2-1.el5.noarch.rpm

https://github.com/apel/apel/releases/download/1.2.2-1/apel-parsers-1.2.2-1.el5.noarch.rpm

- SL6:

https://github.com/apel/apel/releases/download/1.2.2-1/apel-lib-1.2.2-1.el6.noarch.rpm

https://github.com/apel/apel/releases/download/1.2.2-1/apel-parsers-1.2.2-1.el6.noarch.rpm

What about DGAS sensors?

you may leave active the dgas sensors: just request to NGI_IT to disable the data sending from DGAS to APEL for your site

STATUS

SITE NAME TICKET STATUSSorted ascending INFO
BIOCOMP 17459 IN PROGRESS
CNR-ILC-PISA 17461 IN PROGRESS
INFN-NAPOLI-ATLAS 17453 IN PROGRESS
INFN-PADOVA 17480 IN PROGRESS
INFN-PERUGIA 17483 IN PROGRESS
INFN-PISA 17454 IN PROGRESS
CIRMMP 17460 OPEN
CRS4 17462 OPEN
FBF-Brescia-IT 17463 OPEN
GARR-01-DIR 17464 OPEN
GRISU-COMETA-INFN-CT 17465 OPEN
GRISU-UNINA 17466 OPEN
INAF-TS 17467 OPEN
INFN-BARI 17448 OPEN
INFN-BOLOGNA 17468 OPEN
INFN-BOLOGNA-T3 17469 OPEN
INFN-CATANIA 17449 OPEN
INFN-CNAF-LHCB 17470 OPEN
INFN-COSENZA 17471 OPEN
INFN-FERRARA 17472 OPEN
INFN-FRASCATI 17452 OPEN
INFN-GENOVA 17473 OPEN
INFN-LECCE 17474 OPEN
INFN-LNL-2 17450 OPEN
INFN-MILANO-ATLASC 17448 OPEN
INFN-NAPOLI-ARGO 17477 OPEN
INFN-NAPOLI-CMS 17478 OPEN
INFN-NAPOLI-PAMELA 17479 OPEN
INFN-PARMA 17481 OPEN
INFN-PAVIA 17482 OPEN
INFN-ROMA1 17455 OPEN
INFN-ROMA1-CMS 17456 OPEN
INFN-ROMA1-VIRGO 17484 OPEN
INFN-ROMA2 17485 OPEN
INFN-ROMA3 17486 OPEN
INFN-T1 17457 OPEN
INFN-TORINO 17458 OPEN
INFN-TRIESTE 17487 OPEN
RECAS-NAPOLI 17488 OPEN
SNS-PISA 17489 OPEN
TRIGRID-INFN-CATANIA 17490 OPEN
UNI-PERUGIA 17491 OPEN
UNINA-EGEE 17492 OPEN

-- AlessandroPaolini - 2014-06-13

Edit | Attach | PDF | History: r59 | r15 < r14 < r13 < r12 | Backlinks | Raw View | More topic actions...
Topic revision: r13 - 2014-09-11 - AlessandroPaolini
 
  • Edit
  • Attach
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