Skip to content

[booth] Add plugin for the Booth cluster ticket manager - #4424

Open
suraj-cmd wants to merge 1 commit into
sosreport:mainfrom
suraj-cmd:add-booth-plugin
Open

[booth] Add plugin for the Booth cluster ticket manager#4424
suraj-cmd wants to merge 1 commit into
sosreport:mainfrom
suraj-cmd:add-booth-plugin

Conversation

@suraj-cmd

Copy link
Copy Markdown
Contributor

Booth manages tickets across geographically separate Pacemaker clusters and is
packaged for Fedora, RHEL and SUSE. sos has a pacemaker plugin but nothing for
booth, and no other plugin references it, so an sosreport from a booth site or
arbitrator contains no configuration, ticket state or logs.

Paths and unit names are taken from upstream. src/booth.h defines the
configuration directory as /etc/booth, the run directory as /var/run/booth
and the log as /var/log/booth.log. conf/ ships booth-arbitrator.service
and the templated booth@.service, the latter keyed on /etc/booth/%i.conf.

booth list is the command the OCF resource agent itself uses to check ticket
state; peers and status are collected alongside it.

src/config.c parses an authfile option and src/main.c reads that file as
a shared secret used to authenticate ticket messages between sites. Key
material under the configuration directory is added to the forbidden paths so
it cannot be collected.

Confirmation of the packaged authfile default location would be welcome — I
have excluded *.key and authkey under /etc/booth, but the option accepts
an arbitrary path, so a reviewer with a real deployment may know of a
conventional location I have missed.


Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

  • Is the commit message split over multiple lines and hard-wrapped at 72 characters?
  • Is the subject and message clear and concise?
  • Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
  • Does the commit contain a Signed-off-by: First Lastname email@example.com?
  • Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
  • Are all passwords or private data gathered by this PR obfuscated?

Booth manages tickets across geographically separate Pacemaker
clusters and is packaged for Fedora, RHEL and SUSE. sos has a
pacemaker plugin but nothing for booth, and no other plugin
references it, so an sosreport from a booth site or arbitrator
contains no configuration, ticket state or logs.

Paths and unit names are taken from upstream. src/booth.h
defines the configuration directory as /etc/booth, the run
directory as /var/run/booth and the log as /var/log/booth.log.
conf/ ships booth-arbitrator.service and the templated
booth@.service, the latter keyed on /etc/booth/%i.conf.

"booth list" is the command the OCF resource agent itself uses
to check ticket state; peers and status are collected alongside
it.

src/config.c parses an "authfile" option and src/main.c reads
that file as a shared secret used to authenticate ticket
messages between sites. Key material under the configuration
directory is added to the forbidden paths so it cannot be
collected.

Signed-off-by: Suraj Patil <surajpatil522@gmail.com>
@packit-as-a-service

Copy link
Copy Markdown

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

  • sudo dnf install -y 'dnf*-command(copr)'
  • dnf copr enable packit/sosreport-sos-4424
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant