Difference between revisions of "LibCT"
(Created and filled Parallels reqs) |
(Idea how to do python) |
||
| Line 2: | Line 2: | ||
* C/C++ bindings (for Parallels SDK) | * C/C++ bindings (for Parallels SDK) | ||
* Python bindings (for OpenStack) | * Python bindings (for OpenStack) | ||
| + | ** Might make sence to write Python code that just goes via RPC | ||
* Fine grained support for namespaces and cgroups | * Fine grained support for namespaces and cgroups | ||
* Extendable support for different private FS | * Extendable support for different private FS | ||
Revision as of 21:08, 14 May 2014
Requirements
- C/C++ bindings (for Parallels SDK)
- Python bindings (for OpenStack)
- Might make sence to write Python code that just goes via RPC
- Fine grained support for namespaces and cgroups
- Extendable support for different private FS
- Extendable support for different NICs
- Support for external bind mounts
- 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
