Apache VCL logo Apache Software Foundation logo
Apache current event

VCL 2.2

Please make sure to download VCL from an mirror server. The following link will automatically select one for you that should be close to you. After downloading it make sure you verify it with MD5 or SHA1 sums AND the GPG signature (sums and signature files should be downloaded directly from Apache, not from mirrors).

Download ASF VCL 2.2
GPG Signature
MD5 Sum
SHA1 Sum

Run the following command to verify the MD5 sum. You should get the same number that is in apache-VCL-2.2-incubating.tar.bz2.md5:

md5sum apache-VCL-2.2-incubating.tar.bz2

Similarly, Run the following command to verify the SHA1 sum. You should get the same number that is in apache-VCL-2.2-incubating.tar.bz2.sha1:

sha1sum apache-VCL-2.2-incubating.tar.bz2

To verify the GPG signature (you’ll need to have GnuPG installed):

  1. download and import the VCL KEYS file:

    gpg –import KEYS

  2. download the GPG Signature to the same location as the release file

  3. from the directory containing both the release file and the GPG signature, run

    gpg –verify apache-VCL-2.2-incubating.tar.bz2.asc

For new installs, visit the on-line installation guide.

For upgrades from version 2.1, visit the on-line upgrade guide.

Release Notes

I. Intro and Description

VCL, Virtual Computing Lab. The VCL can be many things, first and foremost it is an open-source system used to dynamically provision and broker remote access to a dedicated compute environment for an end-user. The provisioned computers are typically housed in a data center and may be physical blade servers, traditional rack mounted servers, or virtual machines. VCL can also broker access to standalone machines such as a lab computers on a university campus.

One of the primary goals of VCL is to deliver a dedicated compute environment to a user for a limited time through a web interface. This compute environment can range from something as simple as a virtual machine running productivity software to a machine room blade running high end software (i.e. a CAD, GIS, statistical package or an Enterprise level application) to a cluster of interconnected physical (bare metal) compute nodes.

Also using the scheduling API it can be used to automate the provisioning of servers in a server farm or HPC cluster.

The release supports provisioning nodes using xCAT 1.3, xCAT 2.x, VMWare Server 1.x, VMWare Server 2.x, VMWare ESX 3.5, and VMWare ESXi with both purchased licenses and free licenses.

II. VCL Roadmap

VCL 2.2 (this release)

VCL 2.3

VCL 2.4

VCL 2.5

With each release, we’ll be working toward making VCL easier to install. As part of our move to development at the Apache Software Foundation, it is an obvious goal to create a community of users and more developers around VCL. Bringing in more developers should become easier as VCL becomes easier to install.

III. Getting Involved in the ASF VCL Community

There are five ways to become involved in the ASF VCL community.

IV. How to Submit Bugs and Feature Requests

If you find a bug, please submit a bug report to our JIRA bug tracking system at http://issues.apache.org/jira/browse/VCL (you will need to set up an account there if you haven’t already done so - it’s free to anyone). Also, we would appreciate it if you mentioned that you filed a bug on the dev list to make sure we don’t miss it.

If you would like to requrest a new feature, you can also submit that in the same way through JIRA (just select “New Feature” or “Improvement” as the Issue Type). Again, it would be helpful if you mentioned that you filed a feature request on the dev list.

After you have created a JIRA issue, you have the option to vote on it to help us know how to prioritize issues. You can also “watch” the issue to see when activity related to it is submitted.

Change Log

Release Notes - VCL - Version 2.2



New Feature