Install And Configure RSV

Included topic: Install And Configure RSV


RSV configuration steps


Configuring RSV using configure-osg

IMPORTANT: Ensure you have gone through the RSV prerequisites section of the Preparing Compute Element document already.

The recommended and simplest way to configure RSV (for simple RSV setups) on an OSG CE is by using configure-osg.

  • Edit the [RSV] section in config.ini; The section is self-explanatory -- each option is commented upon in detail. You can also refer to the RSV section of the ConfigureFileHelp twiki page for extensive documentation.

Alternative Method: If you would rather do the RSV configuration on the command line using configure_osg_rsv, then refer to the advanced RSV configuration twiki page.

Start RSV and related services

Start Condor-cron and RSV services

NOTE: If any of the services have already been started as a result of previous CE configuration steps, etc., then you should stop them and then start them again.

vdt-control --enable condor-cron osg-rsv
vdt-control --on condor-cron osg-rsv

NOTE: If you are using Apache to monitor the local RSV status, you will need to enable and [re]start that service as well.

Validating RSV configuration

  • Condor_cron jobs: You can check that your RSV monitoring jobs are running in the Condor-Cron infrastructure with the following command:

    You should see a handful of jobs, and a couple of other jobs (html-consumer, gratia-script-consumer, rotate_html_files), with output similar to this:
    Submitter: : <156.56.m.n:nnn> :
    ID      OWNER   SUBMITTED     RUN_TIME ST PRI SIZE CMD               
    21.0   rsvuser    5/9  16:36   0+00:00:00 I  0   0.0 /
       . . .
    36.0   rsvuser    5/9  16:36   0+00:00:00 I  0   0.0 /
    37.0   rsvuser    5/9  16:36   0+00:00:04 R 0   0.0  html-consumer     
    38.0   rsvuser    5/9  16:36   0+00:00:00 I  0   0.0 /
    39.0   rsvuser    5/9  16:36   0+00:00:04 R 0   0.0  gratia-script-cons
    40.0   rsvuser    5/9  16:36   0+00:00:00 I  0   0.0  rotate_html_files.

    If you do not see these jobs in Condor-Cron, then RSV jobs are not running on your system.

  • Service cert proxy (if applicable): If you setup RSV to use a service certificate (use_service_cert setting in your config.ini file), then you should see the proxy for it in /tmp/rsvproxy (or whatever path you specified in rsv_proxy_out_file in your config.ini file). This page explains how to authorize the certificate to allow RSV to run globus jobs.

  • Local RSV status page : After the first probe has run (usually ~15 minutes), you can see the results on the local status web page that is created. This page is created at $VDT_LOCATION/osg-rsv/output/html/index.html. You can either view the local status pages directly on the monitoring host ; or you can view these pages on the web at https://<FQDN_of_monitoring_host>:8443/rsv, as long as the setup_for_apache value in your config.ini file is enabled.

    Note: In order to view this page, you'll need to have a certificate loaded in your web browser that is accepted by one of the Certificate Authorities on your CE.

  • RSV status on MyOSG: After the first probe has run (usually ~15 minutes), check MyOSG's RSV resource status page - metric results for your resource, as well as resource status, should be displayed, assuming your resource is registered with the appropriate FQDN, and is active in OIM.
    • RSV output record upload to central collector (using Gratia transport): if the MyOSG URL above does not display metrics then you can start debugging by first looking at the Gratia consumer log file: $VDT_LOCATION/osg-rsv/logs/consumers/gratia-script-consumer.out to see if probe results were uploaded successfully to the GOC maintained RSV database. You should see entries similar to this:

         08-20-2007 16:35:26 - Executing script '/usr/local/grid/ . . .'

Complete: 2
Responsible:-- ArvindGopu - 09 May 2008
Reviewer - date:

Topic revision: r42 - 23 May 2008 - 19:57:07 - ArvindGopu?

TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..