VDT 2.0.0 Release

On 21-May-2009, the VDT team announced the release of VDT 2.0.0. (Note: It was not widely announced on this date, because it first was sent to the OSG Validation Testbed for testing.)

Updates to VDT 2.0.0

Release Notes	Changes since 2.0.0	Release Date	Release highlights
2.0.0p11	Cumulative Changes	17 Nov 2009	Tomcat security update. GUMS, RSV, VOMS Admin, Xrootd* updates
2.0.0p10	Cumulative Changes	22 Sep 2009	Fixed lcg-utils version reporting. Updated Glexec and Java 5
2.0.0p9	Cumulative Changes	16 Sep 2009	Critical GIP and LCG-Utils updates. Fixed RSV zombie problem and more
2.0.0p8	Cumulative Changes	21 Aug 2009	Fixed RSV/pyOpenSSL issue, security fixes for Apache, Java, other bug fixes
2.0.0p7	Cumulative Changes	24 July 2009	Updated RSV
2.0.0p6	Cumulative Changes	17 July 2009	Fixed broken Gratia probes, updated RSV, minor Bestman update and more
2.0.0p5	Cumulative Changes	30 June 2009	Lots of updates: Gratia, UberFTP, XrootdFS, Bestman, Condor, OSG Matchmaker, GIP; Fetch CRL now runs every 6 hours
2.0.0p4	Cumulative Changes	23 June 2009	Critical RSV fix + Bestman install time fix
2.0.0p3	Cumulative Changes	15 June 2009	Critical RSV fix, updated Bestman, GIP, GUMS, minor bug fixes
2.0.0p2	Cumulative Changes	8 June 2009	Security update for Glexec
2.0.0p1	Cumulative Changes	3 June 2009	Improved MyProxy configuration, improved vdt-post-install logging, minor bug fixes
2.0.0		21 May 2009	Initial release

Compare differences between two VDT 2.0.0 point releases

Highlights of changes since 1.10.1

• We have added support for Debian 5, x86 and x86-64.
• We now build MyProxy against VOMS.
  • Note: MyProxy is not linked against VOMS on Mac OS
  • Note: The MyProxy executables and some flavors of the libraries are built against VOMS, but the following library flavors are not built against VOMS:
    • 32-bit: gcc32 and gcc32pthr
    • 64-bit: gcc64 and gcc64pthr
• We have removed MySQL 4. We have moved the software that was using MySQL 4 to MySQL 5.0: (VDT Ticket 5256)
  • Globus-RLS (VDT Ticket 3753)
  • Globus-RFT
  • GUMS
  • VOMRS
• We have added a new tool, vdt-ca-manage, to help simplify managing the CA certificates. This tool will be used to setup the certificates after installation. For more info, see the man page. Please note: Unlike VDT 1.10.1, you will not normally need to edit vdt-update-certs.conf or run vdt-setup-ca-certificates after you do an installation: you just run vdt-ca-manage.
• We now require the use of Pacman 3.28
• After you install the VDT with Pacman, you must finish the installation with the new vdt-post-install program, located in $VDT_LOCATION/bin/vdt-post-install. We are gradually moving some of the more complicated portions of the installation process out of the Pacman installation. This gives us two benefits:
  1. If the post-installation fails, it doesn't damage Pacman's database about the installation.
  2. It will simplify our transition to support native packages (RPMs and debs)
• Almost all of the questions that the VDT used to ask when doing an installation have been removed. Most of them were questions about whether or not a service should be enabled. Now the question isn't asked (it's often confusing at installation time), and all services are installed as "disabled", and can be enabled as desired with:

  vdt-control --enable SERVICE-NAME

  The VDT will now disregard pre-answered questions in the vdt-questions.sh file.
  This change was made because it significantly simplified the packaging of the VDT and, in some circumstances, will make it much easier for us to deliver updates to software.
  There is still one VDT question that asks you if you accept the licenses for the software in the VDT. How to pre-answer the licenses question.
• By default CRLs are fetched every 6 hours instead of every 24 hours. (If you've enabled fetch-crl to automatically run.) If you have lots of computers at your site that fetch CRLs (such as all of your worker nodes) you may need to configure your site to be kinder to the CRL servers. Details

New Software Since 1.10.1

• One-Way Active Measurement Protocol (OWAMP, One-Way Ping) (VDT Ticket 4400)
• Bandwidth Test Controller (BWCTL) (VDT Ticket 4400)
• Network Diagnostic Tool (NDT)(VDT Ticket 4400)
• Network Path and Application Diagnosis (NPAD) Client (VDT Ticket 4400)

Upgraded Software Since 1.10.1

Software	1.10.1	2.0.0	Ticket (if applicable)
Apache HTTPD	2.2.9	2.2.13
Condor/Condor-G	7.0.5	7.2.4	(VDT Ticket 5318)
Condor Cron For OSG-RSV	7.0.5	7.2.4	(VDT Ticket 5318)
cURL	7.18.0	7.18.2
dCache	2.2.8 (Based on dCache 1.8.0-15p8)	2.3.1 (Based on dCache 1.9.2-5)
Generic Information Provider	1.1.3	1.1.5
Grid File Access Library (GFAL)	1.10.11-1	1.11.9-1
glexec-osg 0.6.7 (glexec 0.5.36.1, lcas 1.3.7.2 and lcmaps 1.4.3.1)	0.6.6	0.6.7
Gratia Condor Probe	1.02.1-5	1.04.4d-1
Gratia Glexec Probe	1.02.1-5	1.04.4d-1
Gratia GridFTP Probe	1.02.1-5	1.04.4d-1
Gratia LSF Probe	1.02.1-5	1.04.4d-1
Gratia Metric Probe	1.02.1-5	1.04.4d-1
Gratia PBS Probe	1.02.1-5	1.04.4d-1
Gratia SGE Probe	1.02.1-5	1.04.4d-1
GSI-Enabled OpenSSH	4.3	4.6	(VDT Ticket 5290)
GUMS	1.3.15	1.3.17
Java 5 SDK	1.5.0_20	1.5.0_21
LCG Utils	1.6.11-1p1	1.7.6-1
LCG File Catalog Client	1.6.11.4	1.7.2-4
LCG File Catalog Server	1.6.11.4	1.7.2-4
MySQL Connector/ODBC	3.51.12	3.51.27r695	(VDT Ticket 5303)
MyProxy Server	4.2	4.7
MySQL	5.0.67	5.0.81
MySQL Connector/J	5.0.6	5.0.8
Nmap Security Scanner	4.20-1	4.85BETA7-1
OpenLDAP	2.3.39	2.3.43
OSG Match Maker	0.5	0.7
OSG Resource and Service Validation (RSV)	2.4.2-3	3.1.1
Pegasus	2.1.0	2.3.0
Pegaus Worker Package	2.1.0	2.3.0
PHP	5.2.5	5.2.9
PRIMA Authorization Module	0.8.3	0.8.4
procd	0.2	0.3	(VDT Ticket 4969)
Python	2.3.7	2.4.6
Squid Web Proxy Cache	2.6.STABLE18	2.6.STABLE22
Stunnel	4.20	4.26
Syslog-ng	2.0.8	2.0.10
Tcl	8.4.18	8.4.19
Apache Tomcat	5.5.27	5.5.28
UberFTP	2.0p1	2.4
VOMRS	1.3.2	1.3.3a	(VDT Ticket 4473)
VOMRS-Client	1.3.2	1.3.3a
VOMS Admin	2.0.14-1	2.0.15-1
Xrootd	20080828-1632	20090721-0636
XrootdFS	2.0	2.2.1

Learning More

To learn more, you can view the main documentation page or documentation specific to VDT 2.0.0.

Known Problems

The VDT 2.0.0 cache is located at: http://vdt.cs.wisc.edu/vdt_200_cache