Changes

There will be was a containers mini-summit at the [http://www.linuxsymposium.org/2008/ OLS'08]. This page is served for organizing this mini-summit. Feel free to editevent.

'''When''': 22nd of July 2008, 8:30-16:30<br/>'''Where''': Ottawa, ON, Canada, Novotel Hotel (Albion A). == Notes == For the notes from the mini-summit, '''see [[Containers/Mini-summit 2008 notes]].'''

The mini-summit proposal sent to OLS organizers. ; '''See see [[/Proposal|proposal]]'''.

* Namespaces/Containers (8am-108:30am-11am)

*** Swap (separate subsystem or merge with memory?)*** Disk I/O (several proposed designs)*** Network traffic classification*** Freezer*** Signaller*** OOM Handler** libcg - userspace explotation of control groups/resource management** Resource management* Overview so far*** Is kernel-based reclassification needed?*** Real use-cases*** Future directions  

** Summary Documentation : Look at "See Also" section below** Goals and expectations of existing c/r patchsets/designsthis summit*** identify, discuss and (if possible) agree on the general design** How to initiate * identify, discuss and synchronize (if possible) agree on the technical points*** decide on priorities for different components (eg. high, medium, low) such that the final outcome is a practical road-map that would keep us busy for (at least) until the next OLS (though the "O" may change ;)** What are the problems that the linux community can solve with the checkpoint/restart?** (state of freezer subsystemPreparing the kernel internals*** How we implement it without affecting long term maintainability ?)** Memory state dump* What are the kernel subsystems, process resources and framework for CR ?** How * Which pieces to dumptarget first ? The following technical points can be discussed during the mini-summit if we have time or later at the OLS. ** Checkpointing /fetch data for Restarting*** Reaching a quescient point - network, processes, aio, avoiding side effects of quiesce/revive*** Checkpoint - signal handler ? syscall ? crfs ? process hierarchy, resource dependencies, system and process resources*** Restarting - New binary format handler ? converting between formats (filefrom older kernel to newer)*** Notification to processes which explicitly wish to be notified about quiesce, ipc) checkpointand restart - container state ? new signals ?** Determining the userspace API - Posix 1003.1m ?** How Passing the kernel internal state to do restart/from userspace - coredump like file ? swap per container ? netlinks, CR filesystem ? army of different call for the CR (proc, existing syscalls, ...)** Hopefully we can make decisions here, continue to discuss in the next days and get a bit of a hackfest going during OLS:)