THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
Why Testing of a Release Artifact Matters
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.
Test with source code 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. |
Setup environment
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. |
...
Clean up your environment (and DevCloud)
| 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 '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 SSHType the password "password" during the ssh promote.
Download the source build
Download the artifacts:
| 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 Blockcode |
|---|
mkdir /tmp/cloudstack; cd /tmp/cloudstack wget httphttps://peopledist.apache.org/~chipchildersrepos/dist/release/cloudstack/KEYS wget http://people.apache.org/~jzb/~chipchilderscloudstack/dist/cloudstack/releases/4.0.0-incubatingVERSION/apache-cloudstack-4.0.0-incubatingVERSION-src.tar.bz2 wget http://people.apache.org/~jzb/~chipchilderscloudstack/dist/cloudstack/releases/4.0.0-incubatingVERSION/apache-cloudstack-4.0.0-incubatingVERSION-src.tar.bz2.asc wget http://people.apache.org/~jzb/~chipchilderscloudstack/dist/cloudstack/releases/4.0.0-incubatingVERSION/apache-cloudstack-4.0.0-incubating-src.VERSION-src.tar.bz2.md5 wget http://people.apache.org/~jzb/~chipchilderscloudstack/dist/cloudstack/releases/4.0.0-incubatingVERSION/apache-cloudstack-4.0.0-incubatingVERSION-src.tar.bz2.sha |
Replace VERSION with the version you are testing.
Install gpg (if needed): sudo apt-get install gpg
...
| Code Block |
|---|
gpg --verify apache-cloudstack-4.0.0-incubating*-src.tar.bz2.asc |
This command should return "Good Signature".
| Code Block |
|---|
gpg --print-md MD5 apache-cloudstack-4.0.0-incubating*-src.tar.bz2 | diff - apache-cloudstack-4*-src.0.0-incubating-src.tar.bz2tar.bz2.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 |
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 /tmp/cloudstack/tree |
...
| 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.
Compile
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 |
| Code Block |
mvn -P deps
ant clean-all build-all
|
...
Wait for secondary storage VM coming up.
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"This may take a bit...
Add a new instance
- In the first step of "Add instance " wizard , select template,
- In step 2, select "tiny Linux"
- In step 3, select "tinyOffering"
- In step 4, select "No thanks"
- Skip step 5 and 6.
- Launch VM
...
Overview
Content Tools
Apps