Difference between revisions of "Wishlist"
(added design tasks) |
m (→Software testing) |
||
| Line 29: | Line 29: | ||
* See things to test in [[QA TODO list]] | * See things to test in [[QA TODO list]] | ||
| − | * Add tests to [https://src.openvz.org/projects/OVZ/repos/prl-disp-service/browse/Tests Parallels Dispatcher] code | + | * Add more unit tests to [https://src.openvz.org/projects/OVZ/repos/prl-disp-service/browse/Tests Parallels Dispatcher] code |
=== DevOps === | === DevOps === | ||
Revision as of 05:45, 7 August 2015
This article is a stub. You can help OpenVZ Wiki by expanding it. If you have ideas and suggestions on new features and improvements that you would like to see and help bring to OpenVZ, you can:
Write a specification - a short description what feature or improvement you would like to implement and why and how it should be implemented. Writing a good specification is an art, the finer points of which are discussed here. Once you have written your specification, you will need to discuss it with OpenVZ developers for inclusion in OpenVZ.
List below contains our current plans and TODO:
Per project
Per activity
Development
- ZFS support (from community wishlist, see survey results)
- Upstream kernel support and availability in Linux distributives (from community wishlist, see survey results)
- Support of Debian 8.0 Jessie (from community wishlist, see survey results)
- Setup regular static code analysis for OpenVZ components (Travis CI?)
- Integrate projects with Address Sanitizer
Software testing
- See things to test in QA TODO list
- Add more unit tests to Parallels Dispatcher code
DevOps
- Create packages of libprlsdk and prlctl for different Linux distributions. See Packages.
- Automate Virtuozzo Storage installation. Something like Ansible playbook for CEPH
- Automate CRIU development environment
- Automate CRIU code coverage measuring process
- Automate OpenVZ infrastructure (ask sergeyb@). Something like Fedora has.
