Editing Containers/Mini-summit 2008 notes
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 28: | Line 28: | ||
Amy Griffis, HP | Amy Griffis, HP | ||
Dhaval Giani, IBM | Dhaval Giani, IBM | ||
− | |||
− | (Later walk-ins) | + | (Later walk-ins) |
− | |||
== Namespaces and containers == | == Namespaces and containers == | ||
Why do various companies want containers? | Why do various companies want containers? | ||
− | + | ibm: workload management | |
EB: using containers as improved chroot | EB: using containers as improved chroot | ||
HP: wants similar to ibm, plus security | HP: wants similar to ibm, plus security | ||
Line 146: | Line 144: | ||
if we can do sys_hijack cleanly, | if we can do sys_hijack cleanly, | ||
we can use it to solve kthread problem | we can use it to solve kthread problem | ||
− | |||
− | |||
== Checkpoint/Restart [CR] == | == Checkpoint/Restart [CR] == | ||
Line 185: | Line 181: | ||
requires the kernel to expose a very fine-grained API. | requires the kernel to expose a very fine-grained API. | ||
− | Everyone | + | Everyone agreed to aim at a monolithic interface, such that nearly |
− | such that nearly all of the CR will be done in the kernel. The kernel | + | all of the CR will be done in the kernel. The kernel will return |
− | will return (checkpoint) or receive (restart) a blob with the image | + | (checkpoint) or receive (restart) a blob with the image of the state |
− | of the state of the container. | + | of the container. |
* '''Kernel-module ?''' | * '''Kernel-module ?''' |