On Wed, Feb 20, 2019 at 10:22:47AM +0100, Jan Kasprzak wrote: > If I read the parallel thread about pool migration in ceph-users@ > correctly, the ability to migrate to v2 would still require to stop the client > before the "rbd migration prepare" can be executed.
Note, if even rbd supported live (without any downtime) migration you would still need to restart the client after the upgrate to a new librbd with migration support. So actually you can combine the upgrade with migration: upgrade client library stop client rbd migration prepare start client and eventually: rbd migration execute rbd migration commit And it would be interesting to investigate a possibility to replace "stop/start client" steps with "migrating the VM to another (upgraded) host" to avoid stopping the VM at all. The trick would be to execute somehow "rbd migration prepare" after the the sourse VM closes the image, but before the destination VM opens it. -- Mykola Golub _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
