From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>,
Lukas Straub <lukasstraub2@web.de>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Wen Congyang <wencongyang2@huawei.com>,
Xie Changlong <xiechanglong.d@gmail.com>,
qemu-block <qemu-block@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v7 0/4] colo: Add support for continuous replication
Date: Thu, 20 Feb 2020 09:38:43 +0800 [thread overview]
Message-ID: <f105e19b-6f1d-a539-459d-076a031b86b8@intel.com> (raw)
In-Reply-To: <9CFF81C0F6B98A43A459C9EDAD400D780630AB3E@shsmsx102.ccr.corp.intel.com>
Hi Jason,
I noticed this series can't be merged or queued, do you met some problem
about it?
Thanks
Zhang Chen
>>>> Max Reitz <mreitz@redhat.com>; qemu-block <qemu-block@nongnu.org>
>>>> Subject: Re: [PATCH v7 0/4] colo: Add support for continuous
>>>> replication
>>>>
>>>> On Fri, 25 Oct 2019 19:06:31 +0200
>>>> Lukas Straub <lukasstraub2@web.de> wrote:
>>>>
>>>>> Hello Everyone,
>>>>> These Patches add support for continuous replication to colo. This
>>>>> means that after the Primary fails and the Secondary did a failover,
>>>>> the Secondary can then become Primary and resume replication to a
>>>>> new
>>>> Secondary.
>>>>> Regards,
>>>>> Lukas Straub
>>>>>
>>>>> v7:
>>>>> - clarify meaning of ip's in documentation and note that active and
>> hidden
>>>>> images just need to be created once
>>>>> - reverted removal of bdrv_is_root_node(top_bs) in replication and
>>>> adjusted
>>>>> the top-id= parameter in documentation acordingly
>>>>>
>>>>> v6:
>>>>> - documented the position= and insert= options
>>>>> - renamed replication test
>>>>> - clarified documentation by using different ip's for primary and
>>>>> secondary
>>>>> - added Reviewed-by tags
>>>>>
>>>>> v5:
>>>>> - change syntax for the position= parameter
>>>>> - fix spelling mistake
>>>>>
>>>>> v4:
>>>>> - fix checkpatch.pl warnings
>>>>>
>>>>> v3:
>>>>> - add test for replication changes
>>>>> - check if the filter to be inserted before/behind belongs to the
>>>>> same interface
>>>>> - fix the error message for the position= parameter
>>>>> - rename term "after" -> "behind" and variable "insert_before" ->
>>>> "insert_before_flag"
>>>>> - document the quorum node on the secondary side
>>>>> - simplify quorum parameters in documentation
>>>>> - remove trailing spaces in documentation
>>>>> - clarify the testing procedure in documentation
>>>>>
>>>>> v2:
>>>>> - fix email formating
>>>>> - fix checkpatch.pl warnings
>>>>> - fix patchew error
>>>>> - clearer commit messages
>>>>>
>>>>>
>>>>> Lukas Straub (4):
>>>>> block/replication.c: Ignore requests after failover
>>>>> tests/test-replication.c: Add test for for secondary node continuing
>>>>> replication
>>>>> net/filter.c: Add Options to insert filters anywhere in the filter
>>>>> list
>>>>> colo: Update Documentation for continuous replication
>>>>>
>>>>> block/replication.c | 35 +++++-
>>>>> docs/COLO-FT.txt | 224 +++++++++++++++++++++++++++---------
>> -
>>>>> docs/block-replication.txt | 28 +++--
>>>>> include/net/filter.h | 2 +
>>>>> net/filter.c | 92 ++++++++++++++-
>>>>> qemu-options.hx | 31 ++++-
>>>>> tests/test-replication.c | 52 +++++++++
>>>>> 7 files changed, 389 insertions(+), 75 deletions(-)
>>>>>
>>>> Hello Everyone,
>>>> So I guess this is ready for merging or will that have to wait until
>>>> the 4.2 release is done?
>>> Due to Qemu 4.2 release schedule, after soft feature freeze(Oct29) the
>> master branch does not accept feature changes.
>>> But I don't know if sub-maintainer(block or net) can queue this series first
>> then merge it after 4.2 release?
>>> Thanks
>>> Zhang Chen
>>
>> Will try to queue this series.
> Thank you Jason~
>
> Thanks
> Zhang Chen
>
>> Thanks
>>
>>
>>>> Regards,
>>>> Lukas Straub
next prev parent reply other threads:[~2020-02-20 1:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 17:06 [PATCH v7 0/4] colo: Add support for continuous replication Lukas Straub
2019-10-24 14:25 ` [PATCH v7 1/4] block/replication.c: Ignore requests after failover Lukas Straub
2019-10-29 13:04 ` Max Reitz
2019-10-24 14:25 ` [PATCH v7 2/4] tests/test-replication.c: Add test for for secondary node continuing replication Lukas Straub
2019-10-24 14:25 ` [PATCH v7 3/4] net/filter.c: Add Options to insert filters anywhere in the filter list Lukas Straub
2019-10-24 14:25 ` [PATCH v7 4/4] colo: Update Documentation for continuous replication Lukas Straub
2019-10-30 8:58 ` Zhang, Chen
2019-11-13 16:35 ` [PATCH v7 0/4] colo: Add support " Lukas Straub
2019-11-19 12:28 ` Zhang, Chen
2019-11-19 15:03 ` Jason Wang
2019-11-20 1:31 ` Zhang, Chen
2020-02-20 1:38 ` Zhang, Chen [this message]
2020-02-20 6:52 ` Jason Wang
-- strict thread matches above, loose matches on Subject: below --
2019-10-25 17:04 Lukas Straub
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=f105e19b-6f1d-a539-459d-076a031b86b8@intel.com \
--to=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=lukasstraub2@web.de \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).