Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Su Yue <glass.su@suse.com>
To: drbd-dev@lists.linbit.com
Cc: lars.ellenberg@linbit.com
Subject: [RFC PATCH 0/3] drbd.ocf support for OCF 1.1 standard
Date: Mon, 29 Jul 2024 21:34:07 +0800	[thread overview]
Message-ID: <20240729133410.8332-1-glass.su@suse.com> (raw)

Hi, drbd maintainers
Here is a patchset which adds supports of drbd.ocf for OCF 1.1 standard.
The motivation is that SUSE's SLE16 will bring corosync3 and pacemaker
built without option '--enable-compat-2.0'. So drbd.ocf needs some
adaptations.

The first two patches are compatible with pacemaker even without option
"--enable-compat-2.0".
NOTE: The third patch changes roles "Master" "Slave" to "Promoted" "Unpromoted".
It breaks the compatibility of Pacemaker < 2.1.0.

The patchset was tested in my testbox only, non SUSE QE. I want to get your
suggestions first so make it RFC. Many thanks.


Su Yue (3):
  drbd.ocf: replace crm_master with ocf_promotion_score
  drbd.ocf: update regex of sed for new output from crm_resource
  drbd.ocf: update for OCF 1.1

 scripts/drbd.ocf | 38 +++++++++++++++++++++++++-------------
 1 file changed, 25 insertions(+), 13 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-07-29 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 13:34 Su Yue [this message]
2024-07-29 13:34 ` [RFC PATCH 1/3] drbd.ocf: replace crm_master with ocf_promotion_score Su Yue
2024-07-29 13:34 ` [RFC PATCH 2/3] drbd.ocf: update regex of sed for new output from crm_resource Su Yue
2024-07-29 13:34 ` [RFC PATCH 3/3] drbd.ocf: update for OCF 1.1 Su Yue

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=20240729133410.8332-1-glass.su@suse.com \
    --to=glass.su@suse.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.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