| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| use-custom-uuid-fact.patch | Use custom UUID fact =================================================================== |
Thomas Goirand <zigo@debian.org> | no | 2021-02-15 | ||
| check-for-commented-out-drives-in-fstab.patch | Check for commented out drives in fstab This patch checks for commented out drives in /etc/fstab, in case Swift drive-audit process removed it. =================================================================== |
Thomas Goirand <zigo@debian.org> | yes | 2021-02-15 | ||
| fix-name-of-ceilometermiddleware-package.patch | Fix python-ceilometermiddleware -> python3-ceilometermiddleware There's a ::swift::params for it, but it's not in use. As a result, this breaks the install of ceilometermiddleware. Let's use it. =================================================================== |
Thomas Goirand <zigo@debian.org> | yes | 2022-10-21 | ||
| drive-full-checker.patch | [PATCH] drive-full-checker This implements swift_drive_full_checker_config to configure the drive-full-checker.conf from swift when this patch is merged: https://review.opendev.org/c/openstack/swift/+/907523 This also implements a new swift::storage::drive_full_checker class to set values in drive-full-checker.conf. This class also setups the cron job for drive-full-checker. Finally, a new option use_drive_full_checker is added to swift::storage, so that it writes to /etc/swift/rsyncd.conf instead of directly in /etc/rsyncd.conf, so that it lets the swift-drive-full-checker do the modification before writing to /etc/rsyncd.conf. Note that we need a new release of the puppetlabs-rsync module that includes the new conf_file parameter to write in /etc/swift/rsyncd.conf instead of /etc/rsyncd.conf directly. |
Thomas Goirand <zigo@debian.org> | no | 2024-02-14 | ||
| add-UUID-to-possible-device-def.patch | Add UUID to possible device def | Thomas Goirand <zigo@debian.org> | no | 2024-05-01 | ||
| Support-for-barbican_endpoint-in-kms_keymaster.patch | Support for barbican_endpoint in kms_keymaster This patch adds support for specifying barbican_endpoint, which is mandatory if doing a multi-region deployment with kms_keymaster. Indeed, without it, Castellan may use the wrong endpoint of the wrong cluster. diff --git a/manifests/keymaster.pp b/manifests/keymaster.pp index 683a26a..633b5b7 100644 |
Thomas Goirand <zigo@debian.org> | yes | 2024-06-13 |