Difference between revisions of "CRIT"
(fix examples) |
(use {{status}} template) |
||
| Line 23: | Line 23: | ||
=== Convert images to JSON and back === | === Convert images to JSON and back === | ||
| + | |||
| + | {{Status|ready}} | ||
| + | |||
This is the replacement for (rather nasty) criu show code. Also this is the way to edit the images before restoring from them. | This is the replacement for (rather nasty) criu show code. Also this is the way to edit the images before restoring from them. | ||
| − | |||
| − | |||
It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages. | It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages. | ||
| Line 56: | Line 57: | ||
=== Generate core files out of task images === | === Generate core files out of task images === | ||
| + | |||
| + | {{Status|not ready}} | ||
All the needed information is in core-$pid.img and pagemap-$pid.img | All the needed information is in core-$pid.img and pagemap-$pid.img | ||
| − | + | === On-the-fly conversion === | |
| − | + | {{Status|not ready}} | |
There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications | There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications | ||
| − | + | === Convert between different image versions === | |
| − | + | {{Status|not ready}} | |
Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images. | Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images. | ||
| − | + | === Show images statistics === | |
| − | + | {{Status|not ready}} | |
E.g. -- total number of processes, files, memory, sockets, etc. | E.g. -- total number of processes, files, memory, sockets, etc. | ||
| − | + | === Check/validate images === | |
| − | + | {{Status|not ready}} | |
Check that | Check that | ||
* all images are present | * all images are present | ||
* the inter-images IDs are in consistent state | * the inter-images IDs are in consistent state | ||
| − | |||
| − | |||
[[Category:Images]] | [[Category:Images]] | ||
[[Category:API]] | [[Category:API]] | ||
Revision as of 19:23, 14 January 2015
This page describes the CRiu Image Tool.
Usage
usage: crit [-h] [-i IN] [-o OUT] [-f {raw,nice}] {decode,encode}
CRiu Image Tool
positional arguments:
{decode,encode} decode/encode - convert criu image from/to binary type
to/from json
optional arguments:
-h, --help show this help message and exit
-i IN, --in IN input file (stdin by default)
-o OUT, --out OUT output file (stdout by default)
-f {raw,nice}, --format {raw,nice}
well-formated output (by default: raw for files and
nice for stdout)
Functionality
Convert images to JSON and back
Status: ready
This is the replacement for (rather nasty) criu show code. Also this is the way to edit the images before restoring from them.
It uses text_format as a human-readable format for protobuf messages.
The output file is structured in the following way.
With "--format raw":
{ "magic" : "FOO", "entries" : [{"foo": "bar", "bar": "foo", "extra": "abc"}, {"foo": "bar", "bar" : "foo", "extra" : "abc"} ]}
With "--format nice"(default for stdout):
{
"magic" : "FOO",
"entries" : [
{
"foo" : "bar",
"bar" : "foo",
"extra" : "abc"
},
{
"foo" : "bar",
"bar" : "foo",
"extra" : "abc"
}
]
}
Generate core files out of task images
Status: not ready
All the needed information is in core-$pid.img and pagemap-$pid.img
On-the-fly conversion
Status: not ready
There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications
Convert between different image versions
Status: not ready
Right now we store the images version in inventory.img and collect info about what's bad with V1 images. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images.
Show images statistics
Status: not ready
E.g. -- total number of processes, files, memory, sockets, etc.
Check/validate images
Status: not ready
Check that
- all images are present
- the inter-images IDs are in consistent state