Given the wide spectrum of CRIU use cases, I am also in favor of organizing a separate track for it. To that end, I can present and do a live demo of how CRIU was used to provide native Docker container checkpoint and restore. This can be a full presentation by itself or combined with another presentation. A minor nit: for consistency, can we call it checkpoint/restore instead of checkpoint/restart? --Saied On Mon, Feb 2, 2015 at 9:06 AM, Tycho Andersen <tycho.andersen@xxxxxxxxxxxxx > wrote: > On Mon, Feb 02, 2015 at 01:05:51PM +0300, Pavel Emelyanov wrote: > > Hi, > > > > There's a call for micro-conferences now open at the upcoming Plumbers > > conference [1]. Before this one, CRIU was typically included into the > > containers MC [2], but this year we can try to organize a separate [3] > > track if there's enough topics and attendees. > > > > Suggestions and thoughts are welcome. > > I'm very interested, hopefully I can (I should) get back some time to > work on CRIU to have something to present. > > Tycho > > > Thanks, > > Pavel > > > > > > [1] http://wiki.linuxplumbersconf.org/2015:topics > > [2] http://wiki.linuxplumbersconf.org/2015:containers > > [3] http://wiki.linuxplumbersconf.org/2015:ckptrestart > > _______________________________________________ > > CRIU mailing list > > CRIU@xxxxxxxxxx > > https://lists.openvz.org/mailman/listinfo/criu > _______________________________________________ > CRIU mailing list > CRIU@xxxxxxxxxx > https://lists.openvz.org/mailman/listinfo/criu > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
