Vox Pupuli Tasks Repositories About
Log in

GitHub puppet-corosync
44
44
21
Sets up and manages Corosync.

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Debian
No translation
Supports Latest Debian
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Synced
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Released
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

SLES support
enhancement
merge-conflicts
needs-rebase
tests-fail

Pull Request (PR) description

Adds support for SUSE Linux Enterprise Server to the puppetlabs-corosync module.
No special care is given to ensure only supported clusters are used, that's for either a profile or a separate module.

This Pull Request (PR) fixes the following issues

n/a

WIP: Fix acceptance tests
merge-conflicts
needs-rebase
tests-fail

The acceptance tests are failing in a not yet diagnosed fashion, this PR will solve that.

Add possibility to define watchdog_device resource
needs-rebase
tests-fail

This pull request allows to define a watchdog_device resource for corosync.

In early corosync versions, watchdog usage had to be explicitly turned off via the "off" keyword, while in recent versions its usage needs to be explicitly turned on via the device name e.g. "/dev/watchdog". Hence an Optional[String] seems a better choice than a Boolean.

Related to https://github.com/voxpupuli/puppet-corosync/pull/451

issue #485: remove score parameter from cs_order
tests-fail

I didn't spot an open PR on this, but there is open issue #485

It seems that the release of pacemaker 2.0.3 (in RHEL8) removes the option of supplying the superfluous score parameter.

Here is the documentation for pacemaker 2.0 which makes no mention of a score property:
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Explained/s-resource-ordering.html

Pull Request (PR) description

Removes the score parameter from cs_order type as it is no longer valid and causes errors.

This Pull Request (PR) fixes the following issues

Fixes #485

Support corosync v3 on RedHat8
merge-conflicts
needs-rebase
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Update the command used to check config file for corosync v3+

This Pull Request (PR) fixes the following issues

RedHat/CentOS 8 support