Difference between revisions of "LibCT"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
m (add mail list)
(moved tasks to table)
Line 7: Line 7:
 
[https://github.com/xemul/libct https://github.com/xemul/libct]
 
[https://github.com/xemul/libct https://github.com/xemul/libct]
  
== Requirements ==
+
== Development status ==
* '''DONE''' C/C++ bindings (for Parallels SDK)
+
 
* '''DONE''' Python bindings (for OpenStack)
+
 
** Might make sence to write Python code that just goes via RPC
+
{| class="wikitable sortable"
* '''DONE''' Fine grained support for namespaces and cgroups
+
|-
* +/- Extendable support for different private FS
+
! Status
* +/- Extendable support for different NICs
+
! Feature
* '''DONE''' Support for external bind mounts
+
|-
* '''DONE''' Ability to enter a CT
+
| DONE || C/C++ bindings (for Parallels SDK)
* +/- Ability to configure running CT
+
|-
* - Integration with CRIU for checkpointing
+
| DONE || Python bindings (for OpenStack)
* - Integration with CRIU for migration
+
|-
* - Ability to operate on remote host
+
| DONE || Fine grained support for namespaces and cgroups
* - Ability to be used by non-root App
+
|-
* - Ability to resurrect after sudden App crash
+
| +/- || Extendable support for different private FS
* - Ability to work on OpenVZ kernel (backend)
+
|-
* - Ability to run libct supporting tools on older (OpenVZ) kernels (depends on above)
+
| +/- || Extendable support for different NICs
* +/- Integration with Docker libcontainer to give any container system implementing the ability to deploy docker packages
+
|-
* - Backend for Solaris Zones and probably Virtuozzo Windows Containers
+
| DONE || Support for external bind mounts
 +
|-
 +
| DONE || Ability to enter a CT
 +
|-
 +
| +/- || Ability to configure running CT
 +
|-
 +
| - || Integration with CRIU for checkpointing
 +
|-
 +
| - || Integration with CRIU for migration
 +
|-
 +
| - || Ability to operate on remote host
 +
|-
 +
| - || Ability to be used by non-root App
 +
|-
 +
| - || Ability to resurrect after sudden App crash
 +
|-
 +
| - || Ability to work on OpenVZ kernel (backend)
 +
|-
 +
| - || Ability to run libct supporting tools on older (OpenVZ) kernels (depends on above)
 +
|-
 +
| +/- || Integration with Docker libcontainer to give any container system implementing the ability to deploy docker packages
 +
|-
 +
| - || Backend for Solaris Zones and probably Virtuozzo Windows Containers
 +
|-
 +
|}
 +
 
 +
 
  
 
== See also ==
 
== See also ==
 +
* LibCT [[packages]] in various Linux distributions.
 
* [https://lists.openvz.org/mailman/listinfo/libct LibCT mailing list]
 
* [https://lists.openvz.org/mailman/listinfo/libct LibCT mailing list]
 
* [https://github.com/docker/libcontainer/pull/434 Initial integration of libct into libcontainer]
 
* [https://github.com/docker/libcontainer/pull/434 Initial integration of libct into libcontainer]
 +
 +
[[Category:Development]]

Revision as of 14:08, 6 August 2015

Description

LibCT is a containers management library which provides convenient API for frontend programs to rule a container during its whole lifetime.

Source code

https://github.com/xemul/libct

Development status

Status Feature
DONE C/C++ bindings (for Parallels SDK)
DONE Python bindings (for OpenStack)
DONE Fine grained support for namespaces and cgroups
+/- Extendable support for different private FS
+/- Extendable support for different NICs
DONE Support for external bind mounts
DONE Ability to enter a CT
+/- Ability to configure running CT
- Integration with CRIU for checkpointing
- Integration with CRIU for migration
- Ability to operate on remote host
- Ability to be used by non-root App
- Ability to resurrect after sudden App crash
- Ability to work on OpenVZ kernel (backend)
- Ability to run libct supporting tools on older (OpenVZ) kernels (depends on above)
+/- Integration with Docker libcontainer to give any container system implementing the ability to deploy docker packages
- Backend for Solaris Zones and probably Virtuozzo Windows Containers


See also