From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block <qemu-block@nongnu.org>,
Wen Congyang <wencongyang2@huawei.com>,
Jason Wang <jasowang@redhat.com>, Max Reitz <mreitz@redhat.com>,
Zhang Chen <chen.zhang@intel.com>,
Xie Changlong <xiechanglong.d@gmail.com>
Subject: [PATCH v6 0/4] colo: Add support for continuous replication
Date: Sat, 5 Oct 2019 15:05:16 +0200 [thread overview]
Message-ID: <cover.1570280098.git.lukasstraub2@web.de> (raw)
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
v6:
- properly 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 | 38 ++++++-
docs/COLO-FT.txt | 213 +++++++++++++++++++++++++++----------
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, 380 insertions(+), 76 deletions(-)
--
2.20.1
next reply other threads:[~2019-10-05 13:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 13:05 Lukas Straub [this message]
2019-10-05 13:05 ` [PATCH v6 1/4] block/replication.c: Ignore requests after failover Lukas Straub
2019-10-18 18:46 ` Lukas Straub
2019-10-23 8:13 ` Zhang, Chen
2019-10-23 12:49 ` Max Reitz
2019-10-23 18:07 ` Lukas Straub
2019-10-05 13:05 ` [PATCH v6 2/4] tests/test-replication.c: Add test for for secondary node continuing replication Lukas Straub
2019-10-09 6:03 ` Zhang, Chen
2019-10-09 15:19 ` Lukas Straub
2019-10-05 13:05 ` [PATCH v6 3/4] net/filter.c: Add Options to insert filters anywhere in the filter list Lukas Straub
2019-10-05 13:05 ` [PATCH v6 4/4] colo: Update Documentation for continuous replication Lukas Straub
2019-10-09 8:36 ` Zhang, Chen
2019-10-09 15:16 ` Lukas Straub
2019-10-10 10:34 ` Zhang, Chen
2019-10-11 16:00 ` Lukas Straub
2019-10-11 17:39 ` Zhang, Chen
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=cover.1570280098.git.lukasstraub2@web.de \
--to=lukasstraub2@web.de \
--cc=chen.zhang@intel.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--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 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.