Difference between revisions of "Main Page"
(change the intro) |
(rm audio. No links in headers. I said NO!) |
||
| Line 85: | Line 85: | ||
<br clear="both"> | <br clear="both"> | ||
<div style="float:left; width: 33%"> | <div style="float:left; width: 33%"> | ||
| − | == | + | == Under the hood == |
* [[Checkpoint/Restore]] | * [[Checkpoint/Restore]] | ||
| + | * [[:Category:Under the hood]] | ||
* [[:Category:Network]] | * [[:Category:Network]] | ||
* [[:Category:Files]] | * [[:Category:Files]] | ||
| Line 99: | Line 100: | ||
== External links == | == External links == | ||
{{:Articles}} | {{:Articles}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
<div style="float:right; width: 33%;"> | <div style="float:right; width: 33%;"> | ||
| − | == | + | == Misc == |
| + | * [[Podcasts]] and other audio/video interviews | ||
* Project [[history]] | * Project [[history]] | ||
* [[Logo]] description | * [[Logo]] description | ||
* [[Events]] | * [[Events]] | ||
| − | * | + | * [[CRIU acronym fun]] |
</div> | </div> | ||
Revision as of 21:48, 23 September 2016
|
Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.
Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it as a collection of files on disk. You can then use the files to restore the application and run it exactly as it was during the time of freeze. With this feature, application live migration, snapshots, remote debugging, and many other things are possible.
Using
- Getting packages for your distribution
- Or try manual installation to have CRIU on your system
- Usage scenarios
- Ideas how criu can be used (some are crazy indeed)
- Category:HOWTO
- Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a simple loop might be the best one to start with. Also a set of asciinema records for real-life examples.
- FAQ & When C/R fails
- A sort of troubleshooting guide
- What can change after C/R
- CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.
- What cannot be checkpointed
- What an application could do to make CRIU refuse to dump it.
- Contacts
- Ways to communicate with CRIU community
Developing
If you're interested in CRIU development, please subscribe to the criu mailing list: https://lists.openvz.org/mailman/listinfo/criu
- Images
- Description of image files format
- Plugins
- CRIU can call plugins provided by people
- Upstream kernel commits
- Mainline kernel commits tracker
- Recent commits
- CRIU tool repository commits
- Manpages
- Kernel's manpages commits tracker
- ZDTM Test Suite
- Zero downtime test suite
- TODO
- Current TODO list
- User namespace
- Implementing user namespace support
- Postulates
- What to keep in mind when writing new code
- Code coverage results
- Shows how zdtm run covers the criu code paths
|
Under the hood
External links
- 2024-04-22, Pronghorn: Effective Checkpoint Orchestration for Serverless Hot-Starts
- 2023-11-12, Checkpoint/Restart for CUDA Kernels
- 2023-10-23, Evicting for the greater good: The Case for Reactive Checkpointing in Serverless Computing
- 2023-04-20, A Dynamic Checkpoint Interval Decision Algorithm for Live Migration-Based Drone-Recovery System
- 2023-03-10, Forensic Container Analysis
- 2023-01-14, Async-fork: Mitigating Query Latency Spikes Incurred by the Fork-based Snapshot Mechanism from the OS Level
- 2022-12-05, Forensic container checkpointing in Kubernetes
- 2022-11-13, Out of hypervisor (OoH): efficient dirty page tracking in userspace using hardware virtualization feature
- 2022-08-07, iContainer: Consecutive Checkpointing with Rapid Resilience for Immortal Container-based Services
Misc
- Podcasts and other audio/video interviews
- Project history
- Logo description
- Events
- CRIU acronym fun