Changes between Version 9 and Version 10 of Documentation/Manuals/ARCNativeAPELClients


Ignore:
Timestamp:
Jul 3, 2013 8:12:23 PM (11 years ago)
Author:
Andrii Salnikov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/Manuals/ARCNativeAPELClients

    v9 v10  
    22== Installation ==
    33
    4 Install ARC BLAHP-logger:
     4Install ARC CE plugin to write logs for APEL BLAH parser:
    55{{{
    6 svn co http://trac.grid.org.ua/repos/workarea/arc-misc/arc-blahp-logger /usr/libexec/arc/
     6yum -y localinstall http://blackjack.grid.org.ua/pub/linux/rhel/6x/base/x86_64/nordugrid-arc-blahp-logger-1-1.noarch.rpm
    77mkdir /var/log/arc/accounting/
    88}}}
    … …  
    1919}}}
    2020
    21 Install MySQL backend for APEL clients. MySQL can be installed on any host, running it on ARC host is not mandatory.
     21Install MySQL backend for APEL clients. MySQL can be installed on any host, running it on ARC CE host is not mandatory.
    2222{{{
    2323yum -y install mysql-server mysql
    … …  
    3838== Configuration ==
    3939
    40 Configure ARC to call logger to write BLAHP log. In the {{{/etc/arc.conf}}} add following configuration and restart A-REX:
     40Configure ARC CE to call installed BLAH logger. In the {{{/etc/arc.conf}}} add the following configuration and restart A-REX:
    4141{{{
    4242authplugin="FINISHED timeout=10,onfailure=pass /usr/libexec/arc/arc-blahp-logger /var/log/arc/accounting/blahp.log- %W %C %I %u ce.fqdn:2811/nordugrid-torque-"
    4343}}}
    4444
    45 Edit APEL parser configuration file ({{{/etc/apel/parser.cfg}}}) and specify DB access settings, batch system _accounting_ logs path, and ARC BLAH plugin logs path:
     45Edit APEL parser configuration file ({{{/etc/apel/parser.cfg}}}) and specify DB access settings, batch system ''accounting'' logs path, and ARC CE BLAH plugin logs path:
    4646{{{
    4747[db]
    … …  
    7676}}}
    7777
    78 Run {{{apelparser}}} and make sure records are parsed successfully looking into parser.log and of cause the database content :-)
     78Run {{{apelparser}}} and make sure records are parsed successfully looking into {{{parser.log}}} and of course the database content :-)
    7979
    8080If everything is OK, it's time to configure APEL client and broker network to use.
    … …  
    120120[broker]
    121121# production
    122 #bdii: ldap://bdii.ha.grid.org.ua:2170
    123 #network: PROD
    124 #use_ssl: true
     122bdii: ldap://bdii.ha.grid.org.ua:2170
     123network: PROD
     124use_ssl: true
    125125# testing
    126 host: test-msg02.afroditi.hellasgrid.gr
    127 port: 6163
    128 use_ssl: false
     126#host: test-msg02.afroditi.hellasgrid.gr
     127#port: 6163
     128#use_ssl: false
    129129
    130130[certificates]
    … …  
    135135[messaging]
    136136# production
    137 # destination: /queue/global.accounting.cpu.central
     137destination: /queue/global.accounting.cpu.central
    138138# testing
    139 destination: /queue/global.accounting.cputest.CENTRAL
     139#destination: /queue/global.accounting.cputest.CENTRAL
    140140path: /var/spool/apel/outgoing
    141141
    … …  
    146146}}}
    147147
    148 You can start with "testing" APEL server and open a GGUS ticket to verify is everything is OK. But once the solution will be verified for one site, another sites can go to production using the standard operations procedure:
     148You can start with "testing" APEL server and open a GGUS ticket to verify if everything is OK. But once the solution will be verified for one site, another sites can go to production using the standard operations procedure:
    149149 - declare "gLite-APEL" endpoing in GOCDB for grid-site
    150150 - use PROD brockers from BDII