From: "Zhang, Chen" <chen.zhang@intel.com>
To: Lukas Straub <lukasstraub2@web.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: Jason Wang <jasowang@redhat.com>,
Alberto Garcia <berto@igalia.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: RE: [PATCH 0/5] colo: Introduce resource agent and test suite/CI
Date: Mon, 18 May 2020 09:38:24 +0000 [thread overview]
Message-ID: <a1d3390036cd4007b53786cf6cb7b5a9@intel.com> (raw)
In-Reply-To: <cover.1589199922.git.lukasstraub2@web.de>
> -----Original Message-----
> From: Lukas Straub <lukasstraub2@web.de>
> Sent: Monday, May 11, 2020 8:27 PM
> To: qemu-devel <qemu-devel@nongnu.org>
> Cc: Alberto Garcia <berto@igalia.com>; Dr. David Alan Gilbert
> <dgilbert@redhat.com>; Zhang, Chen <chen.zhang@intel.com>
> Subject: [PATCH 0/5] colo: Introduce resource agent and test suite/CI
>
> Hello Everyone,
> These patches introduce a resource agent for fully automatic management of
> colo and a test suite building upon the resource agent to extensively test colo.
>
> Test suite features:
> -Tests failover with peer crashing and hanging and failover during checkpoint
> -Tests network using ssh and iperf3 -Quick test requires no special
> configuration -Network test for testing colo-compare -Stress test: failover all
> the time with network load
>
> Resource agent features:
> -Fully automatic management of colo
> -Handles many failures: hanging/crashing qemu, replication error, disk
> error, ...
> -Recovers from hanging qemu by using the "yank" oob command -Tracks
> which node has up-to-date data -Works well in clusters with more than 2
> nodes
>
> Run times on my laptop:
> Quick test: 200s
> Network test: 800s (tagged as slow)
> Stress test: 1300s (tagged as slow)
>
> The test suite needs access to a network bridge to properly test the network,
> so some parameters need to be given to the test run. See
> tests/acceptance/colo.py for more information.
>
> I wonder how this integrates in existing CI infrastructure. Is there a common
> CI for qemu where this can run or does every subsystem have to run their
> own CI?
Wow~ Very happy to see this series.
I have checked the "how to" in tests/acceptance/colo.py,
But it looks not enough for users, can you write an independent document for this series?
Include test Infrastructure ASC II diagram, test cases design , detailed how to and more information for
pacemaker cluster and resource agent..etc ?
Thanks
Zhang Chen
>
> Regards,
> Lukas Straub
>
>
> Lukas Straub (5):
> block/quorum.c: stable children names
> colo: Introduce resource agent
> colo: Introduce high-level test suite
> configure,Makefile: Install colo resource-agent
> MAINTAINERS: Add myself as maintainer for COLO resource agent
>
> MAINTAINERS | 6 +
> Makefile | 5 +
> block/quorum.c | 20 +-
> configure | 10 +
> scripts/colo-resource-agent/colo | 1429 ++++++++++++++++++++++
> scripts/colo-resource-agent/crm_master | 44 +
> scripts/colo-resource-agent/crm_resource | 12 +
> tests/acceptance/colo.py | 689 +++++++++++
> 8 files changed, 2209 insertions(+), 6 deletions(-) create mode 100755
> scripts/colo-resource-agent/colo create mode 100755 scripts/colo-resource-
> agent/crm_master
> create mode 100755 scripts/colo-resource-agent/crm_resource
> create mode 100644 tests/acceptance/colo.py
>
> --
> 2.20.1
next prev parent reply other threads:[~2020-05-18 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 12:26 [PATCH 0/5] colo: Introduce resource agent and test suite/CI Lukas Straub
2020-05-11 12:26 ` [PATCH 1/5] block/quorum.c: stable children names Lukas Straub
2020-06-02 1:01 ` Zhang, Chen
2020-06-02 11:07 ` Alberto Garcia
2020-05-11 12:26 ` [PATCH 2/5] colo: Introduce resource agent Lukas Straub
2020-05-11 12:27 ` [PATCH 3/5] colo: Introduce high-level test suite Lukas Straub
2020-06-02 12:19 ` Philippe Mathieu-Daudé
2020-06-04 10:55 ` Lukas Straub
2020-05-11 12:27 ` [PATCH 4/5] configure,Makefile: Install colo resource-agent Lukas Straub
2020-05-11 12:27 ` [PATCH 5/5] MAINTAINERS: Add myself as maintainer for COLO resource agent Lukas Straub
2020-05-18 9:38 ` Zhang, Chen [this message]
2020-06-06 18:59 ` [PATCH 0/5] colo: Introduce resource agent and test suite/CI Lukas Straub
2020-06-16 1:42 ` Zhang, Chen
2020-06-19 13:55 ` 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=a1d3390036cd4007b53786cf6cb7b5a9@intel.com \
--to=chen.zhang@intel.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=lukasstraub2@web.de \
--cc=qemu-devel@nongnu.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.