499 Commits

Author SHA1 Message Date
aa6488854a Add forced upgrade of vhostmd 2023-12-26 01:08:53 -05:00
fc1556c16c Fix incorrect flag 2023-12-14 14:05:45 -05:00
fdf856c53d Add creation of PVC directory 2023-12-14 12:53:11 -05:00
9842f628a3 Use GO zkcli instead of trash BASH one
With Debian 12+ the interactive zkCli.sh is completely broken, failing
to load the JLine module regardless of what is done, and no one in the
project seems to care about that.

Instead let's swap this out for the (non-interactive) GO-based zkcli of
https://github.com/go-zkcli/zkcli instead, as this suits our needs
nicely.
2023-12-13 15:48:12 -05:00
b2a7eecf2c Only set exclude_perf_counts on Debian 12+ 2023-12-10 12:43:34 -05:00
09eba9de80 Add Prometheus Zookeeper exporter 2023-12-10 12:39:35 -05:00
1eb618e8f3 Fix typo 2023-12-10 03:15:02 -05:00
1f34427a0c Add user as well 2023-12-10 03:05:11 -05:00
c7d914696b Add configuration for Postgres Prom exporter 2023-12-10 02:53:11 -05:00
258b5792da Add Libvirt Prometheus exporter 2023-12-10 01:42:09 -05:00
7a2c16e2a5 Disable Zookeeper Prometheus export
This does not work as this functionality is built out of the Debian
packages. Hopefully it will be enabled one day...
2023-12-10 01:41:06 -05:00
23bb3cb4d9 Add JVM info to Zookepeer metric 2023-12-10 01:16:44 -05:00
54bf70d336 Enable Prometheus metrics in Zookeeper too 2023-12-10 00:32:37 -05:00
513313d60f Limit FRR Prom exporter to 12+
Package did not exist on Debian 10/11
2023-12-10 00:31:21 -05:00
35b375ab0e Fix incorrect variable name 2023-12-10 00:26:10 -05:00
bf10ede298 Add additional Prometheus exporters 2023-12-10 00:24:19 -05:00
8bf3bbdeb1 Enable Prometheus exporter on nodes by default 2023-12-10 00:18:44 -05:00
010ecefe16 Ensure pvchealthd is restarted as well 2023-12-10 00:13:42 -05:00
c07b835e33 Fix bad variable 2023-12-10 00:07:08 -05:00
54c9313668 Force all when updating PVC packages
Avoids the overwrite issue in <0.9.83 to 0.9.83.
2023-12-10 00:04:02 -05:00
c488b04939 Ensure new packages are installed as well 2023-12-09 23:59:42 -05:00
9e21aecf97 Ignore errors then check for PVC package
This helps work around apt issues when running from the oneshot
update-pvc-daemons playbook. On a new install, this will be OK. On an
upgrade, the apt tasks will fail OK but then the verification that
pvc-client-cli will ensure that things are actually sane before
proceeding.
2023-12-09 23:56:34 -05:00
865c7d0872 Add Ceph Prometheus configurations (0.9.84) 2023-12-09 23:51:29 -05:00
18054c01a0 Remove obsolete config templates 2023-12-09 23:05:16 -05:00
5111ae47c4 Lower default monitoring interval to 15s
Faults are also reported on the monitoring interval, so 60s seems like
too long. Lower this to 15 seconds by default instead.
2023-12-01 16:06:24 -05:00
82d2f13981 Add legacy config cleanup to playbook 2023-12-01 02:17:42 -05:00
73ad2a7751 Avoid removal of old versions at all
We simply shouldn't do this here. Let's leave them hanging around unless
removed in another way (e.g. in update-pvc-daemons)
2023-12-01 02:08:22 -05:00
97b1469a70 Set ownership of pvc.conf 2023-12-01 01:57:56 -05:00
d59c9ce1ea Add safety to removal of legacy configs
This conditional will ensure that, the first time pvc.conf is installed
(or, subsequent times, until it stabilizes), the legacy configs will not
be removed. Then, on the next run in which pvc.conf does not change,
they will be removed.

This should provide a safety valve during a 0.9.83 update with the
update-pvc-daemons playbook: if the update succeeds, on the next run,
the legacy configs will be purged; otherwise, they will still be present
and can be used for fallback just in case.

This probably isn't needed, but just in case I'd rather be safe.
2023-12-01 01:45:48 -05:00
1cfda69e5e Remove autobackup.yaml and fix quoting 2023-12-01 01:43:14 -05:00
9408bf709c Only install pvcapid on coordinators
There should be no reason for the API to be installed on non-coordinator
hosts, so separate it out.
2023-12-01 01:40:56 -05:00
15fc3261de Add PVC role tasks to update-pvc-daemons
Ensures that configurations are always updated whenever the daemons are.
This will be necessary for 0.9.83 with the fundamental change from
pvcXd.yaml to pvc.conf configuration formats, while also ensuring that
future daemon updates also include any configuration changes that may be
pending in the group_vars.
2023-12-01 01:37:39 -05:00
9d2af41d3f Install new packages and remove old confs 2023-11-30 03:29:24 -05:00
1e89a1440c Enable modelines by default 2023-11-28 16:13:49 -05:00
b1d6915cf4 Write new pvc.conf style configuration (0.9.82+) 2023-11-28 16:10:23 -05:00
7dbabf76c5 Remove pycache entries on update 2023-11-25 00:51:13 -05:00
fef97f0b04 Adjust name of pvcapid-worker to pvcworkerd 2023-11-15 20:32:23 -05:00
8ba0ca02b1 Add SSHFS auto_mount example to group_vars 2023-11-08 12:33:34 -05:00
c8764159f6 Readd queue configuration with updated options 2023-11-05 23:37:49 -05:00
523f7da71e Add KeyDB (Redis clone) to configuration
Replaces Redis for PVC >= 0.9.81
2023-11-05 19:24:30 -05:00
2f9603c82f Adjust pvcapid.yaml for 0.9.81 worker queue config 2023-11-04 12:52:21 -04:00
e15e2dfaab Remove erroneous netmask from floating IP defaults 2023-11-04 12:51:07 -04:00
103e9fe147 Add restart overrides for ceph-mgr
Needed because ceph-mgr seems to crash frequently under Debian 12 when
adding or removing OSDs. The default settings do not restart it
properly, so this override does.
2023-11-03 14:25:31 -04:00
15a5b581f1 Disable failing socket services 2023-11-03 12:10:19 -04:00
90417621d7 Add autobackup support to pvc-ansible 2023-10-27 02:08:20 -04:00
677287fd2e Add additional wait after stopping OSDs
Allows the Ceph cluster to properly reconcile first.
2023-10-24 10:42:15 -04:00
17f819ea3f Don't set "latest" for libvirt packages
Avoids errors during runs before upgrades.
2023-10-24 10:41:47 -04:00
d0bcbf123f Move kernel cleanup to after reboot
Otherwise, modules might fail etc. when the kernel package is purged
before reboot causing odd failures.
2023-10-24 10:41:47 -04:00
7fe682aa60 Handle freshness for all 3 types separately
If microcode was missing, checking the other two would be UNKN and thus
not restart. But, if microcode *is* present, we want to restart for
either of the other two as well.

So separate into 3 distinct checks and restart if any one is changed.
2023-10-24 10:41:47 -04:00
c11f896a60 Fix zk_status check target znode 2023-10-22 00:42:43 -04:00