This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
For an apache project, a VOTE on a release candidate is a very important process. By voting (particularly for PMC members and committers), you are saying to the world that "yes, I have download, verified and tested using the project's procedure for testing". Your +1, 0 or -1 vote is an indication of the success of the steps listed. The more time that each individual spends reviewing the artifacts, the higher confidence we can have in the release.
To setup an environment for CloudStack, usually it will take a while, e.g install a hypervisor host, install Mysql server etc. Here we'll use DevCloud2 to simplify the test procedure.
Unless specified specifically, instruction steps should be assumed to be run from your local machine, not from within the DevCloud VM. The DevCloud VM is the target runtime environment of the tests, but the instructions will push the code to that VM at the right time.
Install the DevCloud VM image via the instructions on the DevCloud wiki page.
Install your required development tools (if not already available)
These pre-requisite development tools are not part of the release validation itself. The instructions are being provided for those testers that may not normally have these tools installed on their test system, and want to perform the expected tests. The pre-requisites listed may not be 100% complete (for example, we assume you have git, tar, etc... installed). If you run into any issues, please ask on the firstname.lastname@example.org mailing list.
Install Boto (assumes you have Python and Setup Tools installed):
OSX users should be able to use their default JVM for this testing.
OSX users need to have Apache Ant and Maven 3 installed.
Ant may already be on your system. Run
which ant to see. If not, Ant can be installed via MacPorts or from source.
Maven 3 can be installed with Homebrew, or can be downloaded and installed from the Maven homepage.
Next, you will need to install OS X tools:
Then you will need cdrtools, which is available as package in both Homebrew and MacPorts.
If after the above steps, for any reason,
mkisofs is still not installed, download it from the net. One good link to get mkisofs for Mac OS X is from Helios. Follow the instructions in the section "Download HELIOS 'mkisofs' tested binary versions". Use the
macosx86 binary if you're running mac os x on an intel platform. After downloading the
mkisofs binary, copy it over to
Next, you will need to install JSch.
First download the binary distribution of Ant.
Unpack the archive, and run:
Install Boto (assumes you have Python and Python Setup Tools already installed):
Download the artifacts:
Install gpg (if needed): sudo apt-get install gpg
This can be done by importing the keys stored in the source distribution's KEYS file: gpg --import KEYS
Alternatively, you could download the signing keys (ID's found in the KEYS file) individually via a keyserver. Ex: gpg --recv-keys CC56CEA8
Verify signatures and hash files:
This command should return "Good Signature".
Each of these commands should return no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server.
Get the commit hash from the VOTE email (ex: 4cd60f3d1683a3445c3248f48ae064fb573db2a1). The value will change between releases.
Create two new temporary directories:
Pull down the git repo:
Unpack the release artifact:
Compare the contents of the release artifact with the contents pulled from the repo:
Nothing should be different.
The build should FAIL if there are any non-compliant files that are not specifically excluded from the ASF license header requirement. You can optionally review the target/rat.txt file after the run completes. If the build passes, RAT is saying that we are compliant and this test passes.
Note: If you're on Ubuntu and using the PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3 instead of mvn, so mvn3 -P deps
Once the management server starts on your local machine, execute the following commands to bring up a basic zone using the devcloud2 VM:
Deploy DevCloud (make sure mysql-connector-python is installed and that the management server is running)
Or, if the above does not work, maybe you're running mvn in debug mode using some MAVEN_OPTS, try marvin:
The above will deploy a zone with settings defined in tools/devcloud/devcloud.cfg which sets some global settings and will take some time. After this, you should restart management server and destroy any system vms which may have started for the global settings to take effect.
Access web UI: http://localhost:8080/client, and login with admin/password. You can tell if the SSVM has been started by navigating to the Infrastructure page, and clicking on System VMs. There should be 2 listed, and their status needs to be displayed as "Started".
Add a new instance:
Test other functionality, to suite your tastes (and perhaps using non-DevCloud infrastructure.
In a separate terminal run:
Via the UI:
1. Destroy any running instances
2. Rename the tinyoffering compute offering 'm1.small'
Then using the access key and secret key of your admin user run the following python script:
If the keys have changed, using the above script verbatim won't work. Make sure to update the keys.
If we made it this far, the release has at least been reasonably "smoke tested".