Difference between revisions of "LibCT"
(+ two more backends) |
(add status of implementation according to mail from jejb https://lists.linux-foundation.org/pipermail/containers/2014-June/034669.html) |
||
| Line 1: | Line 1: | ||
== Requirements == | == Requirements == | ||
| − | * C/C++ bindings (for Parallels SDK) | + | * '''DONE''' C/C++ bindings (for Parallels SDK) |
| − | * Python bindings (for OpenStack) | + | * '''DONE''' Python bindings (for OpenStack) |
** Might make sence to write Python code that just goes via RPC | ** Might make sence to write Python code that just goes via RPC | ||
| − | * Fine grained support for namespaces and cgroups | + | * '''DONE''' Fine grained support for namespaces and cgroups |
| − | * Extendable support for different private FS | + | * +/- Extendable support for different private FS |
| − | * Extendable support for different NICs | + | * +/- Extendable support for different NICs |
| − | * Support for external bind mounts | + | * '''DONE''' Support for external bind mounts |
| − | * Ability to enter a CT | + | * '''DONE''' Ability to enter a CT |
| − | * Ability to configure running CT | + | * +/- Ability to configure running CT |
| − | * Integration with CRIU for checkpointing | + | * - Integration with CRIU for checkpointing |
| − | * Integration with CRIU for migration | + | * - Integration with CRIU for migration |
| − | * Ability to operate on remote host | + | * - Ability to operate on remote host |
| − | * Ability to be used by non-root App | + | * - Ability to be used by non-root App |
| − | * Ability to resurrect after sudden App crash | + | * - Ability to resurrect after sudden App crash |
| − | * Ability to work on OpenVZ kernel (backend) | + | * - Ability to work on OpenVZ kernel (backend) |
| − | * Ability to run libct supporting tools on older (OpenVZ) kernels (depends on above) | + | * - 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 | + | * +/- 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 | + | * - Backend for Solaris Zones and probably Virtuozzo Windows Containers |
Revision as of 15:27, 30 April 2015
Requirements
- DONE C/C++ bindings (for Parallels SDK)
- DONE Python bindings (for OpenStack)
- Might make sence to write Python code that just goes via RPC
- 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
