All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: drbd-reactor v1.5.0-rc.1
Date: Thu, 19 Sep 2024 14:08:24 +0200	[thread overview]
Message-ID: <ZuwUOOQZS3SROVGm@arm64> (raw)

Dear DRBD users,

this is the first RC of the upcoming drbd-reactor version 1.5.0. There
are smaller fixes and improvements all over the place, the important
changes happened in startup of the daemon and the promoter plugin:

We have customers that have hundreds of promoter resources managed by
drbd-reactor. So far every instance on startup wrote their systemd
target units and then called `systemctl daemon-reload`. That takes some
time and in sum systemd might kill the drbd-reactor service because it
did not start in time. We now call daemon-reload only once, and we
improved sd_notify(3) communication between reactor and systemd. Startup
with lots of plugins should now be faster and timeouts should no longer
be a problem.

Please test, if we don't find any bugs I will do the final release in
about a week from now.

Regards, rck

GIT: https://github.com/LINBIT/drbd-reactor/commit/49a7b49b1a3278356a75e7409f374c3b61e6660c
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-reactor-1.5.0-rc.1.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack

Changelog:
[ Lars Ellenberg ]
* promoter: fix Description override to use %N not %p

[ Roland Kammerer ]
* doc: fix start-until procedure
* promoter: check for '/' in service names
* ctl: improve evict error message
* build: add sbom files to tarballs
* build: rm packaging targets
* promoter: add trace logging around adjust
* promoter: systemctl daemon-reload only once
* promoter: use EXTEND_TIMEOUT_USEC in sd_notify
* promoter: use Stdio::null() for systemctl commands
* all: stop using plugin::system and use Command
* daemon: use Stdio::null() for stdin
* systemd: improve notify

                 reply	other threads:[~2024-09-19 12:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZuwUOOQZS3SROVGm@arm64 \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.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 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.