[CRIU] Image cache/proxy TODO

Radostin Stoyanov rstoyanov1 at gmail.com
Fri Sep 14 10:06:18 MSK 2018


On 10/09/18 23:26, Rodrigo Bruno wrote:
> Hi,
>
> last time I touched this code we had some zdtm tests failing.
>
> Have you checked how many tests/issues still need to be fixed?
Hi Rodrigo,

Thank you for the pointer!
I will start with fixing the zdtm tests.

Radostin
>
> cheers,
> rodrigo
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Sat, 8 Sep 2018 10:18:27 +0100
>     From: Radostin Stoyanov <rstoyanov1 at gmail.com
>     <mailto:rstoyanov1 at gmail.com>>
>     To: CRIU <criu at openvz.org <mailto:criu at openvz.org>>
>     Subject: [CRIU] Image cache/proxy TODO
>     Message-ID: <3ddf274f-54a7-b947-fa25-a9c3d60b9fb4 at gmail.com
>     <mailto:3ddf274f-54a7-b947-fa25-a9c3d60b9fb4 at gmail.com>>
>     Content-Type: text/plain; charset="utf-8"
>
>     Hi all,
>
>     I would like to work towards merging the remote option and image
>     cache/proxy into
>     the master branch of CRIU and I was wondering what needs to be done?
>
>     Below is a brief summary of the tasks from [1] and the commit
>     comment in
>     [2].
>
>     1. Add articles for newly introduced actions and options.
>     - I assume that this task is to add more information to the
>     following pages
>     * https://criu.org/CLI/opt/--remote
>     * https://criu.org/CLI/cmd/image-cache
>     * https://criu.org/CLI/cmd/image-proxy
>
>     2. Make the UNIX sockets reside in work-dir.
>     - The option -D|--images-dir should become optional. When --remote
>     is used,
>     CRIU should work purely on the work-dir and not generate anything
>     in the
>     images-dir.
>
>     3. Tune up the image_cache and image_proxy commands to accept the
>     --status-fd
>     and --pidfile options.
>
>     4. Fix local connections not to generate per-image threads.
>     - I believe that this one is already done.
>
>     5. No strings in protocol. Now the hard-coded "RESTORE_FINISH" string
>     (and DUMP_FINISHED one) is used to terminate the communication.
>     Need to tune up the protobuf objects to send boolean (or integer) EOF
>     sign rather that the string.
>
>     6. Check how proxy/cache works with incremental dumps.
>
>     7. Add support for cache/proxy into go-phaul code.
>
>     Is there anything else?
>
>     [1] https://criu.org/Image_cache/proxy_TODO
>     [2]
>     https://github.com/checkpoint-restore/criu/commit/a14f0d0effc92985a79a9a9da86e338b968c26d6
>
>     Thanks,
>     Radostin
>
>
>     ------------------------------
>



More information about the CRIU mailing list