One big complexity to note would be working the Ceph health messages into this, but luckily their levels are fairly consistent (WARN and ERR being roughly -10 and -50 respectively) and they output…
This actually wouldn't work as well as-is as would be obvious. Probably better to make our own "plugin" system that allows arbitrary things to monitor then build a coherent check framework around…
I definitely think leveraging part of the check_mk_agent system for this might be worthwhile. At regular intervals (say every minute so every ~12 keepalives), the plugins can run and save output…
I think this could be done in a crude way by doing:
virsh pauseon the VM- Quickly snapshotting all volumes
virsh unpauseon the VM
It should be quick enough to be impreceptable…
From some quick testing, the consolecallback script does not work properly - it prints no output and immediately exits on any input. This is also the only example I can find so far which does not…
It looks like there is a python-native implementation of virsh console here:
https://github.com/libvirt/libvirt-python/blob/master/examples/consolecallback.py
And because of how we configure…
After another solid year of use, I've found very few situations where these commands would be particularly useful, though they still might be nice to have.
Implementing them shouldn't be…
I think from a backend perspective, the best solution is the simplest solution.
API keys should remain, and we can define at least 3 discrete roles that any given API key can be given.
First…
After many more months of thinking, Vue.js (and possibly Nuxt.js) still seems like the "right" choice in terms of frontend frameworks. However implementation must be done properly which my attemps…
Moving this to the v2 project as a nice-to-have. The current manual SQL works more than well enough.
The implementation of the create() aspect of VM provisioner scripts in #148 effectively completes this: since the configuration of new VMs in the provisioner is handled by…