Skip to contentSkip to conversation

CRIU @Plumbers

DISCUSSION Pavel Emelyanov 7 participants 10 messages Feb 2, 2015 – Feb 3, 2015 6 messages not in the archive

lore
Share & tools
lore
#0 lore raw

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.

Thanks,
Pavel

[1] http://wiki.linuxplumbersconf.org/2015:topics
[2] http://wiki.linuxplumbersconf.org/2015:containers
[3] http://wiki.linuxplumbersconf.org/2015:ckptrestart

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

I think it might be worthwhile - my main concern is that it not conflict timewise with the containers summit.

Quoted 20 lines · Pavel Emelyanov

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.

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 [email protected]
https://lists.openvz.org/mailman/listinfo/criu

#3 lore raw
Quoted 2 lines · Serge Hallyn

I think it might be worthwhile - my main concern is that it not conflict timewise with the containers summit.

You mean ContainerCon? That's running concurrently with LinuxCon, so it shouldn't conflict with either of the two plumbers days.

James

Quoted 26 lines · Pavel Emelyanov
Quoted 13 lines

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.

Thanks,
Pavel

Quoted 7 lines

[1] http://wiki.linuxplumbersconf.org/2015:topics
[2] http://wiki.linuxplumbersconf.org/2015:containers
[3] http://wiki.linuxplumbersconf.org/2015:ckptrestart
_______________________________________________
CRIU mailing list [email protected]
https://lists.openvz.org/mailman/listinfo/criu

_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

A message that is not in the archive (sent off-list or not yet received): 1422935454.2103.48.camel-d9PhHud1JfjCXq6kfMZ53/[email protected]

#5 lore raw
Quoted 6 lines · James Bottomley
Quoted 2 lines · Serge Hallyn

I think it might be worthwhile - my main concern is that it not conflict timewise with the containers summit.

You mean ContainerCon? That's running concurrently with LinuxCon, so it shouldn't conflict with either of the two plumbers days.

Sorry didn't mean "summit". I just mean the containers track at plumbers.

http://wiki.linuxplumbersconf.org/2015:containers

Quoted 35 lines

James

Quoted 21 lines · Pavel Emelyanov
Quoted 13 lines

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.

Thanks,
Pavel

Quoted 7 lines

[1] http://wiki.linuxplumbersconf.org/2015:topics
[2] http://wiki.linuxplumbersconf.org/2015:containers
[3] http://wiki.linuxplumbersconf.org/2015:ckptrestart
_______________________________________________
CRIU mailing list [email protected]
https://lists.openvz.org/mailman/listinfo/criu

Quoted 5 lines

_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw
Quoted 11 lines · Serge E. Hallyn
Quoted 6 lines · James Bottomley
Quoted 2 lines · Serge Hallyn

I think it might be worthwhile - my main concern is that it not conflict timewise with the containers summit.

You mean ContainerCon? That's running concurrently with LinuxCon, so it shouldn't conflict with either of the two plumbers days.

Sorry didn't mean "summit". I just mean the containers track at plumbers.

http://wiki.linuxplumbersconf.org/2015:containers

Yes, Plumbers can take care of the scheduling. Since we have a Seattle local team, we'll help running containers, which should make sure there's no overlap ...

James

#8 lore raw
In reply to a message not in the archive
Quoted 8 lines · Pavel Emelyanov

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

Quoted 11 lines

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 [email protected]
https://lists.openvz.org/mailman/listinfo/criu

#9 lore raw

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 <[email protected]

Quoted 33 lines

wrote:

Quoted 8 lines · Pavel Emelyanov

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

Quoted 11 lines

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 [email protected]
https://lists.openvz.org/mailman/listinfo/criu

_______________________________________________
CRIU mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/criu

A message that is not in the archive (sent off-list or not yet received): CA+Um-gj1ynTwOsQNV7482Lz2GsCX+Leuz=QdSfPL1MVaF1CRGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#11 lore raw
Quoted 6 lines · Saied Kazemi

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.

That's great :) I'll start filling the page with data soon then. Feel free to join and add the stuff you want.

Quoted 1 line

A minor nit: for consistency, can we call it checkpoint/restore instead of checkpoint/restart?

Google gives ~600k results for "checkpoint/restart" vs ~900k for "checkpoint/restore" so I don't mind :)

Quoted 37 lines

--Saied

On Mon, Feb 2, 2015 at 9:06 AM, Tycho Andersen <[email protected] <mailto:[email protected]>> 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
    > [email protected] <mailto:[email protected]>
    > https://lists.openvz.org/mailman/listinfo/criu
    _______________________________________________
    CRIU mailing list
    [email protected] <mailto:[email protected]>
    https://lists.openvz.org/mailman/listinfo/criu

A message that is not in the archive (sent off-list or not yet received): [email protected]

#13 lore raw
Quoted 8 lines · Pavel Emelyanov
Quoted 6 lines · Saied Kazemi

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.

Quoted 7 lines

That's great :) I'll start filling the page with data soon then. Feel free to join and add the stuff you want.

Quoted 1 line

A minor nit: for consistency, can we call it checkpoint/restore instead of checkpoint/restart?

Google gives ~600k results for "checkpoint/restart" vs ~900k for "checkpoint/restore" so I don't mind :)

I prefer "restore" (perhaps a more migration focused term) myself, but I think there is some history behind "restart" (perhaps a more fault tolerance focused term) from at least the Berkeley Lab's Checkpoint/Restart project, which has software releases from 2005 and papers from 2002.

http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/
http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/checkpoint-restart-publications/

Chris

Signature · 3 lines
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

A message that is not in the archive (sent off-list or not yet received): [email protected]

#15 lore raw

Since everyone is in agreement, let's call it checkpoint/restore then. Restart often implies stop + start and, in fact, Docker already has a restart command which does exactly that.

--Saied

Quoted 42 lines · Christopher Covington
Quoted 2 lines · Pavel Emelyanov
Quoted 1 line · Saied Kazemi

Given the wide spectrum of CRIU use cases, I am also in favor of

organizing a

Quoted 3 lines
Quoted 3 lines

separate track for it.

To that end, I can present and do a live demo of how CRIU was used to

provide

Quoted 1 line
Quoted 1 line

native Docker container checkpoint and restore. This can be a full

presentation

Quoted 3 lines
Quoted 1 line

by itself or combined with another presentation.

That's great :) I'll start filling the page with data soon then. Feel

free to

Quoted 3 lines

join and add the stuff you want.

Quoted 1 line

A minor nit: for consistency, can we call it checkpoint/restore instead

of checkpoint/restart?

Quoted 2 lines

Google gives ~600k results for "checkpoint/restart" vs ~900k for

"checkpoint/restore"

Quoted 1 line

so I don't mind :)

I prefer "restore" (perhaps a more migration focused term) myself, but I think
there is some history behind "restart" (perhaps a more fault tolerance focused
term) from at least the Berkeley Lab's Checkpoint/Restart project, which has
software releases from 2005 and papers from 2002.

http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/

http://crd.lbl.gov/departments/computer-science/CLaSS/research/BLCR/checkpoint-restart-publications/

Chris

--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project