Unconference Session: Checkpoint/Restore BoF
summary
Working group prototypes an API that supports three concrete cases: suspend/resume, live migration, and warm start (prewarmed JVM/GPU images). Implementations target CRIU and gVisor; checkpoints are file archives possibly stored via CSI or a registry artifact and include kernel + GPU memory. Design uses a separate Checkpoint object and controller plus a pod-side restoreFrom field, plans core API (not CRD), and raises practical issues: storage transport, device plugins, node compatibility checks, security/permission boundaries, and coordinated group checkpoints.
AI-written summary · about
chapters (6)
- 0:00Checkpoint/Restore BoF intro
- 1:48Use cases and scenarios
- 3:16Open questions in SIGs
- 6:45API design approach
- 9:14Community discussion
- 34:06Closing remarks
related talks
15mUniversal Checkpointing: A Flexible and Efficient Distributed Checkpointing...
15mDistributed Checkpoint
10mLightning Talk: In-Cluster Distributed Checkpointing: Optimizing Training...
17mCheckmate: Zero Performance Overhead Model Checkpointing via Network Gradient Replication
28mRundown of Flink's Checkpoints
39mProcess Migration in the Orchestration World
55mGoing Resilient
19mProtocol-Aware Recovery for Consensus-Based Storage
