Changes

** Summary of existing cDocumentation*** Zap : http://www.ncl.cs.columbia.edu/publications/usenix2007_fordist.pdf*** Metacluster : http://lxc.sourceforge.net/doc/ols2006/lxc-ols2006.pdf*** OpenVZ : http://wiki.openvz.org/Checkpointing_and_live_migration*** Checkpoint/Restart technology : http://en.wikipedia.org/wiki/Application_checkpointing*** Virtual Servers and Checkpoint/Restart in Mainstream Linux : Sigops document*** Remote fork: http://www.cse.nd.edu/~dthain/courses/classconf/wowsys2004/talks/rfork.pd*** Vmadump : http://bproc.sourceforge.net/c268.html*** Posix CR : http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/0650/bks/SGI_Admin/CPR_OG/sgi_html/ch03.html*** An OS services overview : http://sw-eng.falls-church.va.us/r patchsetsitsg/designsP08V31.htm** Goals and expectations of this 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 ?** How Determining the userspace API - Posix 1003.1m ?** 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:)