[CRIU] [PATCH v3 00/12] VZ shared ploops migration

[Nikita Spiridonov]

Acked-by: Nikita Spiridonov <nspiridonov at virtuozzo.com>

(unresolved minor comment from previous patchset)

I am not sure about prepare_shared_backups, restore_shared_backups and
cleanup_shared_backups names. Upper level migration logic call this
functions, maybe more generic names needed (something like
rollback_stop_migration, accept_stop_migration etc)? Xemul, what do you
think?

On Mon, 2016-04-11 at 19:28 +0300, Alexander Burluka wrote:
> This patch series introduces VZ migration on shared ploops
> I've described briefly algorithm in last patch.
> 
> Alexander Burluka (12):
>   p.haul: move get_ddxml_path
>   p.haul: move get_ploop_delta_abspath
>   p.haul: Implement class shared_ploop
>   p.haul: add parsing of shared disk string
>   p.haul: add vz specific parameter "--vz-shared-disks"
>   p.haul: modify p_haul_fs initialization
>   p.haul: add two common fs methods for shared backups
>   p.haul: add prepare_shared_backups function
>   p.haul: add prepare_src_data function
>   p.haul: add pre_final_setup function
>   p.haul: add --skipowner flag on every vzctl action
>   p.haul: implement vz migration with shared ploops
> 
>  phaul/fs_haul_ploop.py   | 90 ++++++++++++++++++++++++++++++++++++++++++++----
>  phaul/fs_haul_shared.py  |  9 +++++
>  phaul/fs_haul_subtree.py |  9 +++++
>  phaul/iters.py           | 32 +++++++++++------
>  phaul/p_haul_docker.py   |  3 ++
>  phaul/p_haul_lxc.py      |  3 ++
>  phaul/p_haul_pid.py      |  3 ++
>  phaul/p_haul_vz.py       | 33 +++++++-----------
>  phaul/service.py         |  3 ++
>  9 files changed, 148 insertions(+), 37 deletions(-)
>