Note: This web site is only kept up to date for OSG Software
1.2 (VDT 2.0.0). If you are looking for information for the most recent
release, the RPM-based OSG Software 3.0, please see
the OSG documentation web site
VDT 2.0.0p24 Update
On 2011-02-07, the VDT team announced the release of VDT 2.0.0p24.
The Gratia probes have been updated to properly account for HTPC jobs
(VDT ticket 8361)
Bestman and SRM-Client-LBNL have been updated to 22.214.171.124.18
Bestman2, Bestman-Client, and SRM-Tester3-LBNL have been updated to 2.0.5
SRM-Client-Fermi has been updated to 1.9.5-23
Updated Pegasus and Pegasus-Worker from 2.4.1 to 3.0.1.
(VDT ticket 8111). This incidentally addressed Pacman update
problems from (VDT ticket 7500).
Updated the GIP from 1.1.12 to 1.1.14. (VDT ticket 8147),
(VDT ticket 8175) . Changes in this release:
- Bugfix: fix the ACBRs to VOLocalViews
- Bugfix: enable allowed_vos to also work properly on the storage element
- LSF: better parsing of waiting jobs, free slots, host groups
- LSF: bugfix: don't include queues that are not in the RVF
- PBS: better chance to include PBS binaries in the path
- SGE: fix missing includes
- Enable publication of WLCG site attributes (admins must set wlcg_tier, wlcg_parent, wlcg_name in the [site] section of config.ini)
- Better reporting of commands with non-zero exit status
- Remove duplicates from PATH
- Updated unit tests
Updated the OSG Matchmaker from 0.8 to 0.9. (VDT ticket 8166)
Updated MyProxy from 5.2 to 5.3. This addresses
a security fix.
The directory VDT_LOCATION/openldap/bin has been added to PATH. This change did not include an
update to the version of OpenLDAP.
RSV has been updated to a new major version.
RSV documentation on the twiki
Notes about the update from RSV pre-3.2.x to RSV 3.3.0 or later
- Existing config.ini files will continue to work (if you have any problems please report them). Some options have been deprecated and an appropriate message will print if you have those options included.
- We do not preserve spec files. You will need to manually
- The state of your html-consumer will be lost. You can now run all probes immediately using "rsv-control --run --all-enabled" (do this after all services are running)
- The addition of the rsv-control tool. rsv-control will:
- Show you what metrics and consumers are enabled and running in Condor-Cron
- Enable or disable metrics
- Easily run a one-off test of any metric against any host
(without changing users, cd'ing to a specific directory, etc, etc)
- Easier configuration:
- The [RSV] section in the ce.ini file has been improved and comments have been
clarified. Additionally it is now much easier to monitor multiple SEs. If you
are using an existing config.ini you can copy the [RSV] section from the ce.ini
template if desired.
- configure-osg can now be used for standalone RSV installations. A new rsv.ini
file is provided as a template.
- Much improved underlying configuration - this is mostly invisible to the admin
but helped us make the high level configuration simpler. If you have any
suggestions for configuration that cannot be done at the config.ini level let us
- New metrics: none of these will be enabled by default (yet), but feel feel to
try them out. You can enable them using the "rsv-control --enable" option.
- Information services metrics by Brian Bockelman
- ReSS metrics by Parag Mhashilkar
- Storage Element metrics by Doug Strain
- Pigeon tools from Doug Strain
- A much easier format for new probe developers to write metrics:
Note: existing probes have not been modified and probe owners do
not need to do any work at this time - the old probes will still work fine
- For details on writing probes in the new style
- For a comparison of the old and new probes
- "rsv-control --on" must be run as root and cannot be run as the rsvuser
- The ReSS metrics can only query the production server currently.
- In config.ini you cannot specify different Gratia metrics if you are
monitoring more than one CE.
If you installed VDT 2.0.0 after VDT 2.0.0p24 was released on
2011-02-07, you do not need to do any of these update operations
because you will have 2.0.0p24.
Recommended method: VDT Updater
We strongly encourage users to update the VDT using the VDT updater
VDT Updater Instructions
Not recommended: Pacman update
If you really want to do it the hard way,
instructions for updating by using
Pacman directly are available on another page. This method is
hard to follow and error prone.