Difference between revisions of "ToDo"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
 
m (Robot: Automated text replacement (-VE +container))
 
(7 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
 
* NFS issues
 
* NFS issues
 +
* Loopback device (/dev/lo*) support
 
* vzquota over other than ext2/ext3 filesystems
 
* vzquota over other than ext2/ext3 filesystems
 +
* Incorporate Zaptel/Asterisk modules [http://forum.openvz.org/index.php?t=msg&th=170&start=0& forum]?
 +
* patch profiling to support container's differentiation. [http://forum.openvz.org/index.php?t=tree&th=1455&mid=8098&&rev=&reveal=]
  
 
==Templates==
 
==Templates==
Line 8: Line 11:
 
* template metadata creation HOWTO
 
* template metadata creation HOWTO
 
* template metadata rpms build system, like we have for tools
 
* template metadata rpms build system, like we have for tools
* tool for auto creation rpm/deb packages from precreated templates tarballs for easy installation with yum/apt help.
+
* tool for auto creation rpm/deb packages from precreated templates tarballs for easy installation with yum/apt help
* page for precreated templates submission to contribs.
+
* page for precreated templates submission to contribs
 
* page with list of all available templates, like http://www.vmware.com/vmtn/appliances/
 
* page with list of all available templates, like http://www.vmware.com/vmtn/appliances/
* templates metadata should include "smart" package manager (yum to fc5, what else?)  
+
* templates metadata should include some high-level package manager (yum for FC5, what else?)
* add extra repo to fc5 template metadata
+
* add 'extras' repo to FC5 template metadata
  
==VPS package management==
+
==container package management==
  
 
* x86_64, ia64, ppc64 external package management (vzrpm, vzpkgenv?)
 
* x86_64, ia64, ppc64 external package management (vzrpm, vzpkgenv?)
 +
* support for application templates
 
* apt-based external package management
 
* apt-based external package management
 
* adoption for common build system
 
* adoption for common build system
 +
 +
==Tools==
 +
 +
vzctl:
 +
* add IPv6 configuration support
 +
* Debian-specific initscript
 +
* complete redesign
 +
* [http://bugzilla.openvz.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=OpenVZ&component=vzctl&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= List of opened vzctl bugs in Bugzilla]
 +
 +
==Testing suite==
 +
* should include base vzctl operation, published, easy to install and run on the node.

Latest revision as of 11:36, 11 March 2008

Kernel[edit]

  • NFS issues
  • Loopback device (/dev/lo*) support
  • vzquota over other than ext2/ext3 filesystems
  • Incorporate Zaptel/Asterisk modules forum?
  • patch profiling to support container's differentiation. [1]

Templates[edit]

  • template metadata creation HOWTO
  • template metadata rpms build system, like we have for tools
  • tool for auto creation rpm/deb packages from precreated templates tarballs for easy installation with yum/apt help
  • page for precreated templates submission to contribs
  • page with list of all available templates, like http://www.vmware.com/vmtn/appliances/
  • templates metadata should include some high-level package manager (yum for FC5, what else?)
  • add 'extras' repo to FC5 template metadata

container package management[edit]

  • x86_64, ia64, ppc64 external package management (vzrpm, vzpkgenv?)
  • support for application templates
  • apt-based external package management
  • adoption for common build system

Tools[edit]

vzctl:

Testing suite[edit]

  • should include base vzctl operation, published, easy to install and run on the node.