Difference between revisions of "Wishlist"
m |
m |
||
| Line 33: | Line 33: | ||
* [https://github.com/ligurio/ansible-criu-environment Automate] CRIU development [http://criu.org/Installation environment] | * [https://github.com/ligurio/ansible-criu-environment Automate] CRIU development [http://criu.org/Installation environment] | ||
* Automate CRIU [http://criu.org/cov/ code coverage] measuring process | * Automate CRIU [http://criu.org/cov/ code coverage] measuring process | ||
| + | * Automate OpenVZ infrastructure (ask sergeyb@). [https://infrastructure.fedoraproject.org/cgit/ansible.git/ Something like] Fedora has. | ||
Revision as of 17:13, 6 June 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
- Perform static code analysis
- Integrate projects with Address Sanitizer
Software testing
- See things to test in QA TODO list
- Add tests to Parallels Dispatcher code
DevOps
- 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.
