From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>,
Amit Shah <amit.shah@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
"eddie . dong" <eddie.dong@intel.com>
Subject: Re: [Qemu-devel] [PATCH] docs: fix COLO architecture diagram
Date: Tue, 1 Nov 2016 14:25:24 +0800 [thread overview]
Message-ID: <58183554.8070101@huawei.com> (raw)
In-Reply-To: <1477971492-10766-1-git-send-email-zhangchen.fnst@cn.fujitsu.com>
Hmm, there are other contents in this file need to be updated,
for example, we support blockdev-add command for nbd now,
so we can convert the related hmp command to qmp command way.
But since we didn't integrate COLO frame with block replication
and proxy, It is OK to fix them later.
For COLO, the basic capability is still incomplete,
but now we got into 'Soft feature freeze' stage,
I'm wondering if it is possible at this point to combine
COLO frame with proxy and block replication which only needs
three or four patches that only touch colo related files ...
Or uses still can't test COLO feature in qemu 2.8.
Any ideas ? Thanks.
On 2016/11/1 11:38, Zhang Chen wrote:
> Fix COLO-Proxy part of COLO architecture diagram
>
> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Reviewed-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
All such patches can go through trivial branch.
Cc: qemu-trivial@nongnu.org
> ---
> docs/COLO-FT.txt | 72 +++++++++++++++++++++++++++++---------------------------
> 1 file changed, 37 insertions(+), 35 deletions(-)
>
> diff --git a/docs/COLO-FT.txt b/docs/COLO-FT.txt
> index 6282938..e289be2 100644
> --- a/docs/COLO-FT.txt
> +++ b/docs/COLO-FT.txt
> @@ -41,41 +41,43 @@ identical responses to all client requests. Once the differences in the outputs
> are detected between the PVM and SVM, COLO withholds transmission of the
> outbound packets until it has successfully synchronized the PVM state to the SVM.
>
> - Primary Node Secondary Node
> - +------------+ +-----------------------+ +------------------------+ +------------+
> - | | | HeartBeat |<----->| HeartBeat | | |
> - | Primary VM | +-----------|-----------+ +-----------|------------+ |Secondary VM|
> - | | | | | |
> - | | +-----------|-----------+ +-----------|------------+ | |
> - | | |QEMU +---v----+ | |QEMU +----v---+ | | |
> - | | | |Failover| | | |Failover| | | |
> - | | | +--------+ | | +--------+ | | |
> - | | | +---------------+ | | +---------------+ | | |
> - | | | | VM Checkpoint |-------------->| VM Checkpoint | | | |
> - | | | +---------------+ | | +---------------+ | | |
> - | | | | | | | |
> - |Requests<---------------------------^------------------------------------------>Requests|
> - |Responses----------------------\ /--|--------------\ /------------------------Responses|
> - | | | | | | | | | | | | |
> - | | | +-----------+ | | | | | | | +------------+ | | |
> - | | | | COLO disk | | | | | | | | | COLO disk | | | |
> - | | | | Manager |-|-|--|--------------|--|->| Manager | | | |
> - | | | +|----------+ | | | | | | | +-----------|+ | | |
> - | | | | | | | | | | | | | | |
> - +------------+ +--|------------|-|--|--+ +---|--|--------------|--+ +------------+
> - | | | | | | |
> - +-------------+ | +----------v-v--|--+ +---|--v-----------+ | +-------------+
> - | VM Monitor | | | COLO Proxy | | COLO Proxy | | | VM Monitor |
> - | | | |(compare packet) | | (adjust sequence)| | | |
> - +-------------+ | +----------|----^--+ +------------------+ | +-------------+
> - | | | |
> - +------------------|------------|----|--+ +---------------------|------------------+
> - | Kernel | | | | | Kernel | |
> - +------------------|------------|----|--+ +---------------------|------------------+
> - | | | |
> - +--------------v+ +--------v----|--+ +------------------+ +v-------------+
> - | Storage | |External Network| | External Network | | Storage |
> - +---------------+ +----------------+ +------------------+ +--------------+
> + Primary Node Secondary Node
> ++------------+ +-----------------------+ +------------------------+ +------------+
> +| | | HeartBeat +<----->+ HeartBeat | | |
> +| Primary VM | +-----------+-----------+ +-----------+------------+ |Secondary VM|
> +| | | | | |
> +| | +-----------|-----------+ +-----------|------------+ | |
> +| | |QEMU +---v----+ | |QEMU +----v---+ | | |
> +| | | |Failover| | | |Failover| | | |
> +| | | +--------+ | | +--------+ | | |
> +| | | +---------------+ | | +---------------+ | | |
> +| | | | VM Checkpoint +-------------->+ VM Checkpoint | | | |
> +| | | +---------------+ | | +---------------+ | | |
> +|Requests<--------------------------\ /-----------------\ /--------------------->Requests|
> +| | | ^ ^ | | | | | | |
> +|Responses+---------------------\ /-|-|------------\ /-------------------------+Responses|
> +| | | | | | | | | | | | | | | |
> +| | | +-----------+ | | | | | | | | | | +----------+ | | |
> +| | | | COLO disk | | | | | | | | | | | | COLO disk| | | |
> +| | | | Manager +---------------------------->| Manager | | | |
> +| | | ++----------+ v v | | | | | v v | +---------++ | | |
> +| | | |+-----------+-+-+-++| | ++-+--+-+---------+ | | | |
> +| | | || COLO Proxy || | | COLO Proxy | | | | |
> +| | | || (compare packet || | |(adjust sequence | | | | |
> +| | | ||and mirror packet)|| | | and ACK) | | | | |
> +| | | |+------------+---+-+| | +-----------------+ | | | |
> ++------------+ +-----------------------+ +------------------------+ +------------+
> ++------------+ | | | | +------------+
> +| VM Monitor | | | | | | VM Monitor |
> ++------------+ | | | | +------------+
> ++---------------------------------------+ +----------------------------------------+
> +| Kernel | | | | | Kernel | |
> ++---------------------------------------+ +----------------------------------------+
> + | | | |
> + +--------------v+ +---------v---+--+ +------------------+ +v-------------+
> + | Storage | |External Network| | External Network | | Storage |
> + +---------------+ +----------------+ +------------------+ +--------------+
> +
>
> == Components introduction ==
>
>
next prev parent reply other threads:[~2016-11-01 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 3:38 [Qemu-devel] [PATCH] docs: fix COLO architecture diagram Zhang Chen
2016-11-01 6:25 ` Hailiang Zhang [this message]
2016-11-01 7:06 ` Zhang Chen
2016-11-09 4:01 ` Zhang Chen
2016-11-15 7:31 ` Jason Wang
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=58183554.8070101@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=eddie.dong@intel.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=zhangchen.fnst@cn.fujitsu.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).