Tester

Setting up a test environment

• setup Linux distributive (RPM based distro is preferred) on one of your test hardware node
• follow OpenVZ installation instructions
• install component which you want to test
• please consider to setup logging console. Especially you want to test new versions of OpenVZ kernel.
• add configuration of your hardware node to the wiki table

Exploratory testing

With an installed version of the development release up and running, you can perform exploratory testing against any packages of components you wish. Go wild! Try and break things! See if the new software can handle the unexpected, or even the normal use cases. If you find a bug, report it!

OpenVZ kernel

Sometimes new version of OpenVZ kernel contains new feature. Usually we provide howto described steps to enable feature and shortest steps how to use it.

Features are in testing below:

• Docker inside CT

Features are in released OpenVZ versions:

• IPsec inside container

OpenVZ OS template

We release OS templates as soon as new version of appropriate Linux distro is available. New OS templates announced on wiki. Follow these steps to validate new OS template:

• download new OS template
• create cache for it
• create container based on that OS template

Bug validation

In each release we do our best to fix as much bugs as possible. You can help us with validation of bugs fixed in latest version.

• open changelog of component in News (see as example ploop-1.12.2)
• find numbers of bugs fixed in that version
• try to reproduce each bug on your test environment and keep appropriate comment in OpenVZ bugzilla about results