Difference between revisions of "Tester"
(OS templates) |
|||
| Line 9: | Line 9: | ||
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, [[Reporting_OpenVZ_problem|report it]]! | 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, [[Reporting_OpenVZ_problem|report it]]! | ||
| − | Sometimes new version of | + | 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: | Features are in testing below: | ||
* [[Docker_inside_CT|Docker inside CT]] | * [[Docker_inside_CT|Docker inside CT]] | ||
| − | * | + | * |
Features are in released OpenVZ versions: | Features are in released OpenVZ versions: | ||
| + | |||
| + | * [[IPsec|IPsec]] inside container | ||
| + | * | ||
| + | |||
| + | We release OS templates as soon as new version of appropriate Linux distro is available. New OS templates announced on [https://openvz.org/News/updates#Templates_update_January_2015 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 == | == 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 (for example [https://openvz.org/Download/ploop/1.12.2 ploop-1.12.2]) | * open changelog (for example [https://openvz.org/Download/ploop/1.12.2 ploop-1.12.2]) | ||
Revision as of 14:24, 11 March 2015
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
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!
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:
Features are in released OpenVZ versions:
- IPsec inside container
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 (for example ploop-1.12.2)
- find bugs fixed in that version
- try to reproduce each bug on your test environment and keep appropriate comment in OpenVZ bugzilla
