From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, "Denis V. Lunev" <den@openvz.org>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] Incremental backup call
Date: Mon, 22 Feb 2016 12:56:29 -0500 [thread overview]
Message-ID: <56CB4BCD.3010006@redhat.com> (raw)
In-Reply-To: <CAJSP0QW=s2PN4AgZZ=OrrNt=FHBngy7JeUt3_GQsmn3pOEFPLQ@mail.gmail.com>
On 02/16/2016 09:02 AM, Stefan Hajnoczi wrote:
> Hi,
> There are several ongoing efforts to implement incremental
> backup-related features.
>
> Let's have a voice/video conference to get everyone on the same page,
> avoid duplicated work, and get patches merged faster.
>
> Agenda:
>
> * External incremental backup API. Summarize requirements common to
> third-party backup appliances and agree on suitable API direction.
>
> * Persistent dirty bitmaps. Agree on how qcow2 and/or qbm will hold
> bitmaps in various use cases.
>
> * Anything else?
>
> Date: Tuesday, 23 February at 13:00 GMT
> URL: https://bluejeans.com/298720067
>
> If you are on the CC list and the time is inconvenient for you, please
> let me know so we can reschedule. The call is public and open to
> anyone.
>
> Stefan
>
Time works for me if it's suitable for everyone else.
--js
next prev parent reply other threads:[~2016-02-22 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:02 [Qemu-devel] Incremental backup call Stefan Hajnoczi
2016-02-22 17:56 ` John Snow [this message]
2016-02-23 14:25 ` Kashyap Chamarthy
2016-02-23 17:10 ` John Snow
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=56CB4BCD.3010006@redhat.com \
--to=jsnow@redhat.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=vsementsov@virtuozzo.com \
/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.