From: Mykola Golub <to.my.trociny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: koukou73gr <koukou73gr-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RBD image format v1 EOL ...
Date: Fri, 22 Feb 2019 16:38:36 +0200 [thread overview]
Message-ID: <20190222143835.GA20829@gmail.com> (raw)
In-Reply-To: <48f860e6-f9d4-ef39-53a2-465380596429-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
On Fri, Feb 22, 2019 at 02:43:36PM +0200, koukou73gr wrote:
> On 2019-02-20 17:38, Mykola Golub wrote:
>
> > 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.
> >
> >
> You could probably get away with executing the client with a new librbd
> version by live migrating the VM to an updated hypervisor.
>
> At least, this is what I have been doing so far when updating Ceph client
> libraries having zero downtime.
Yes, and this is what I meant when I was writing about investigating a
possiblilty to migrate to the new format with zero downtime by using
VM live migration. If there were a way to execute "rbd migration
prepare $pool/$image" during live VM migration, exactly after the
source VM closes the rbd image but before the destination VM opens it,
it would do the trick (the destination VM would start using the new
format).
Right now I don't know if it is possible at all, because I am not
familiar with VM migration, e.g. I don't know if it opens the image on
the destination before or after it closes it on the source.
--
Mykola Golub
prev parent reply other threads:[~2019-02-22 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:36 RBD image format v1 EOL Jason Dillaman
[not found] ` <CA+aFP1Dod_hwug_omfegFTERyiYmwa+3KDcBZsXcjR+B87YykQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-13 19:14 ` Gregory Farnum
2019-02-20 9:22 ` Jan Kasprzak
[not found] ` <20190220092247.GZ92783-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
2019-02-20 15:38 ` Mykola Golub
[not found] ` <48f860e6-f9d4-ef39-53a2-465380596429@yahoo.com>
[not found] ` <48f860e6-f9d4-ef39-53a2-465380596429-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2019-02-22 14:38 ` Mykola Golub [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190222143835.GA20829@gmail.com \
--to=to.my.trociny-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
--cc=koukou73gr-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.