Difference between revisions of "Wishlist"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(prlctl and libprlsdk packages)
(add features from community wishlist)
Line 20: Line 20:
 
=== Development ===
 
=== Development ===
  
* Perform [[static code analysis]]
+
* ZFS support (from community wishlist, see [http://openvz.livejournal.com/51718.html survey results])
 +
* Upstream kernel support and availability in Linux distributives (from community wishlist, see [http://openvz.livejournal.com/51718.html survey results])
 +
* Support of Debian 8.0 Jessie (from community wishlist, see [http://openvz.livejournal.com/51718.html survey results])
 +
* Setup regular [[static code analysis]] for OpenVZ components (Travis CI?)
 
* Integrate projects with [https://code.google.com/p/address-sanitizer/ Address Sanitizer]
 
* Integrate projects with [https://code.google.com/p/address-sanitizer/ Address Sanitizer]
  
Line 30: Line 33:
 
=== DevOps ===
 
=== DevOps ===
  
 +
* Create packages of [https://src.openvz.org/projects/OVZ/repos/libprlsdk/browse libprlsdk] and [https://src.openvz.org/projects/OVZ/repos/prlctl/browse prlctl] for different Linux distributions. See [[Packages]].
 
* Automate [[Virtuozzo Storage]] installation. Something like [https://github.com/ceph/ceph-ansible Ansible playbook for CEPH]
 
* Automate [[Virtuozzo Storage]] installation. Something like [https://github.com/ceph/ceph-ansible Ansible playbook for CEPH]
 
* [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.
+
* Automate [https://github.com/ligurio/openvz-playbooks OpenVZ infrastructure] (ask sergeyb@). [https://infrastructure.fedoraproject.org/cgit/ansible.git/ Something] like Fedora has.
* Create packages of [https://src.openvz.org/projects/OVZ/repos/libprlsdk/browse libprlsdk] and [https://src.openvz.org/projects/OVZ/repos/prlctl/browse prlctl] for different Linux distributions
 
  
 
[[Category:Contributions]]
 
[[Category:Contributions]]

Revision as of 13:33, 3 August 2015

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

Software testing

DevOps