From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: "Zhang, Chen" <chen.zhang@intel.com>,
Jason Wang <jasowang@redhat.com>,
Alberto Garcia <berto@igalia.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 0/4] colo: Introduce resource agent and high-level test
Date: Fri, 22 Nov 2019 09:46:46 +0000 [thread overview]
Message-ID: <20191122094646.GA2785@work-vm> (raw)
In-Reply-To: <cover.1574356137.git.lukasstraub2@web.de>
* Lukas Straub (lukasstraub2@web.de) wrote:
> Hello Everyone,
> These patches introduce a resource agent for use with the Pacemaker CRM and a
> high-level test utilizing it for testing qemu COLO.
>
> The resource agent manages qemu COLO including continuous replication.
>
> Currently the second test case (where the peer qemu is frozen) fails on primary
> failover, because qemu hangs while removing the replication related block nodes.
> Note that this also happens in real world test when cutting power to the peer
> host, so this needs to be fixed.
Do you understand why that happens? Is this it's trying to finish a
read/write to the dead partner?
Dave
> Based-on: <cover.1571925699.git.lukasstraub2@web.de>
> ([PATCH v7 0/4] colo: Add support for continuous replication)
>
> Lukas Straub (4):
> block/quorum.c: stable children names
> colo: Introduce resource agent
> colo: Introduce high-level test
> MAINTAINERS: Add myself as maintainer for COLO resource agent
>
> MAINTAINERS | 6 +
> block/quorum.c | 6 +
> scripts/colo-resource-agent/colo | 1026 ++++++++++++++++++++++++
> scripts/colo-resource-agent/crm_master | 44 +
> tests/acceptance/colo.py | 444 ++++++++++
> 5 files changed, 1526 insertions(+)
> create mode 100755 scripts/colo-resource-agent/colo
> create mode 100755 scripts/colo-resource-agent/crm_master
> create mode 100644 tests/acceptance/colo.py
>
> --
> 2.20.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-11-22 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 17:49 [PATCH 0/4] colo: Introduce resource agent and high-level test Lukas Straub
2019-11-21 17:49 ` [PATCH 1/4] block/quorum.c: stable children names Lukas Straub
2019-11-21 18:04 ` Eric Blake
2019-11-21 18:34 ` Lukas Straub
2019-11-26 14:21 ` Alberto Garcia
2019-11-27 21:20 ` Lukas Straub
2019-11-21 17:49 ` [PATCH 2/4] colo: Introduce resource agent Lukas Straub
2019-11-21 17:49 ` [PATCH 3/4] colo: Introduce high-level test Lukas Straub
2019-11-21 17:49 ` [PATCH 4/4] MAINTAINERS: Add myself as maintainer for COLO resource agent Lukas Straub
2019-11-22 9:46 ` Dr. David Alan Gilbert [this message]
2019-11-27 21:11 ` [PATCH 0/4] colo: Introduce resource agent and high-level test Lukas Straub
2019-12-18 9:27 ` Lukas Straub
2019-12-18 19:46 ` Dr. David Alan Gilbert
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=20191122094646.GA2785@work-vm \
--to=dgilbert@redhat.com \
--cc=berto@igalia.com \
--cc=chen.zhang@intel.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.