For an apache project, a VOTE on a release candidate is a very important process. By voting (particularly for PPMC 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 both the release itself and our ability to pass an IPMC vote later on. Remember, we, as a podling, are going to be held to a higher standard for our releases! The IPMC (and our mentors) are looking for us to show that we understand what it means to have a high quality release.
...
Note |
---|
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. |
Note |
---|
You can follow the following screencast to watch the entire procedure. |
Install the devcloud VM image.
...
Warning |
---|
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 be not be 100% complete (for example, we assume you have git, tar, etc... installed). If you run into any issues, please ask on the cloudstack-dev@incubatordev@cloudstack.apache.org mailing list. |
...
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 should can be installed with Homebrew, or can be downloaded and installed from http://maven.apache.org/download.htmlthe Maven homepage.
Next, you will need to install OS X tools:Install mkisofs
Then you will need cdrtools, which is available as package in both Homebrew and MacPorts.
Note |
---|
If after the above steps, for any reason, |
Next, you will need to install JSch.
First download the binary distribution of Ant.
Unpack the archive, and runInstall JSch:
Code Block |
---|
wget http://downloads.sourceforge.net/project/jsch/jsch.jar/0.1.48/jsch-0.1.48.jar sudo cp jsch-0.1.48.jar /usr/sudo cp lib/ant-jsch.jar /usr/share/ant/lib/ |
Install Boto (assumes you have Python and Python Setup Tools already installed):
...
Note |
---|
Since we have graduated from the incubator, the git remote URL thats embedded in the original DevCloud image is incorrect. Before following the step below, ssh into the devcloud image (run "ssh root@localhost -p 2222" and password is "password") and edit |
Code Block |
rm -Rf /tmp/cloudstack
rm -Rf ~/.m2
ssh root@localhost -p 2222 'cd /opt/cloudstack/ ; rm -rf apache-tomcat-6.0.32; unzip apache-tomcat-6.0.32.zip; cd incubator-cloudstack; git clean -f; git reset --hard; git pull --rebase; git clean -f; git checkout origin/4.0 -b 4.0 -f ' |
Type password during the ssh promote.
Download the artifacts:
Code Block |
---|
mkdir /tmp/cloudstack; cd /tmp/cloudstack
wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
|
Install gpg (if needed): sudo apt-get install gpg
Import keys:
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:
Code Block |
---|
gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
gpg --verify apache-cloudstack-4.0.0-incubating-src.zip.asc
|
Both of these commands should return "Good Signature".
incubator-cloudstack/.git/config to modify the URL from https://git-wip-us.apache.org/repos/asf/*incubator-*cloudstack.git (https://git-wip-us.apache.org/repos/asf/*incubator\-*cloudstack.git) to https://git-wip-us.apache.org/repos/asf/cloudstack.git Once that's done, exit from your ssh session back to your local system. |
Code Block |
---|
rm -Rf /tmp/cloudstack
rm -Rf ~/.m2
ssh root@localhost -p 2222 'cd /opt/cloudstack/; rm -rf apache-tomcat-6.0.32; unzip apache-tomcat-6.0.32.zip; cd incubator-cloudstack; git clean -f; git reset --hard; git pull --rebase; git clean -f; git checkout origin/4.0 -b 4.0 -f ' |
Type the password "password" when prompted to by SSH.
Note |
---|
Some versions of wget will require that you add the --no-check-certificate param to the commands below. You need this, if you get an error stating "ERROR: The certificate of `dist.apache.org' is not trusted.". |
Download the artifacts:
Code Block |
---|
mkdir /tmp/cloudstack; cd /tmp/cloudstack
wget https://dist.apache.org/repos/dist/release/cloudstack/KEYS
wget http://people.apache.org/~jzb/cloudstack/dist/releases/VERSION/apache-cloudstack-VERSION-src.tar.bz2
wget http://people.apache.org/~jzb/cloudstack/dist/releases/VERSION/apache-cloudstack-VERSION-src.tar.bz2.asc
wget http://people.apache.org/~jzb/cloudstack/dist/releases/VERSION/apache-cloudstack-VERSION-src.tar.bz2.md5
wget http://people.apache.org/~jzb/cloudstack/dist/releases/VERSION/apache-cloudstack-VERSION-src.tar.bz2.sha
|
Replace VERSION
with the version you are testing.
Install gpg (if needed): sudo apt-get install gpg
Import keys:
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:
Code Block |
---|
gpg --verify apache-cloudstack-*-src.tar.bz2.asc
|
This command should return "Good Signature".
Code Block |
---|
Code Block |
gpg --print-md MD5 apache-cloudstack-4.0.0-incubating-src.tar.bz2 | diff - apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5 gpg --print-md MD5 apache-cloudstack-*-4src.0.0-incubating-src.ziptar.bz2 | diff - apache-cloudstack-4.0.0-incubating*-src.tar.zipbz2.md5 gpg --print-md SHA512 apache-cloudstack-4.0.0-incubating*-src.tar.bz2 | diff - apache-cloudstack-4.0.0-incubating*-src.tar.bz2.sha gpg --print-md SHA512 apache-cloudstack-4.0.0-incubating-src.zip | diff - apache-cloudstack-4.0.0-incubating-src.zip.sha |
Each of these commands should return no output. If 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.
...
Code Block |
---|
git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git /tmp/cloudstack/git
cd /tmp/cloudstack/git
git archive --prefix=/tmp/cloudstack/tree/ <commit-hash> | tar Pxf -
|
...
Code Block |
---|
cd /tmp/cloudstack tar xvfj apache-cloudstack-4.0.0-incubating*-src.tar.bz2 |
Compare the contents of the release artifact with the contents pulled from the repo:
Code Block |
---|
diff -r /tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src*-src /tmp/cloudstack/tree |
Nothing should be different.
Code Block |
---|
cd /tmp/cloudstack/apache-cloudstack-4.0.0-incubating*-src mvn --projects='org.apache.cloudstack:cloudstack' org.apache.rat:apache-rat-plugin:0.8:check |
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
Code Block |
---|
mvn -P deps ant clean-all build-all |
...
This may take a bit...
Depending on your local system configuration, and available RAM / Disk IO / Net IO, this step will take varied amounts of time. It's reasonable to expect 30 minutes (or more), but it could be less.
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".
...
Code Block |
---|
python cloudstack-aws-api-register --apikey=JdTxDI2rOZ0RDZdgF1O_ZxfISxNuema9gQ3NyE4z5psX4sgSxE4ueEBohG3bfqWHr7BYP6_sAghXTIvm3noqkw --secretkey=fVT0r5lETIJThRGyec-Eg4WFm9_IN5tNIut7Ac5BJW0VExFGdRZEqA_JFvxdTFDH2ZeRcbO25xPQcyxt0VRWKg --cert=/tmp/cert.pem --url=http://localhost:7080/awsapi
|
In case you don't have a X509 ssl certificate, this is how you can generate one:
Code Block |
---|
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /path/to/private_key.pem -out /path/to/cert.pem |
Code Block |
python cloudstack-aws-api-register --apikey=JdTxDI2rOZ0RDZdgF1O_ZxfISxNuema9gQ3NyE4z5psX4sgSxE4ueEBohG3bfqWHr7BYP6_sAghXTIvm3noqkw --secretkey=fVT0r5lETIJThRGyec-Eg4WFm9_IN5tNIut7Ac5BJW0VExFGdRZEqA_JFvxdTFDH2ZeRcbO25xPQcyxt0VRWKg --cert=/tmp/cert.pem --url=http://localhost:7080/awsapi
|
Note |
---|
You can specify an empty file as cert but use the keys generated in the GUI (ex: touch /tmp/cert.pem). Executing this with an empty cert file will result in an error that can be ignored for this test. Regardless of this error, if the registration works you should see the credentials in the cloudbridge database in the usercredentials table. Within the DevCloud VM (as root): You should see your account as the only row in that table. |
...