Well… being a ProxMox users for my clients, I’d be hesitant to use Debops against ProxMox
for anything other than /etc/hosts (be carefull with the name/etc. of the cluster
nodes),local user accounts and root’s password changes, /etc/network/interfaces (and then
be very very very careful as ProxMox edits that file whenever you touch the networking
stack) that is not VM/cluster related but only things for bootstrap reasons, and then
Debops is doing lots of things that you could expect to break ProxMox is strange ways, so
the acronym H.B.D. and the latin caveat emptor applies fully ;(
YEs, I do use Debops against my ProxMox, but that is just the things like user/root
password additions/changes, and then to do things like debops-task to fetch information…
having that in the same “bundle”/playbooks as my jumphosts and other “controllers”
On 22 Aug 2020, at 14:33 , Stuart Mumford <stuart(a)cadair.com>
I have been using debops for a while for my homelab, and it's been a
great way to learn ansible for me.
I am currently building myself a new proxmox server, and I am wondering
if people have advice or experience they could share with running
debops against a proxmox host.
I have tried this in the past and things like the DNS configuration and
other things have ended up a little broken, so I am hesitatant to just
run the full common playbook against it again.
The main things I am interested in running on the proxmox host from
debops are the pki role, and any other core roles which might make
things better without interfering with the existing quirks of a proxmox
install. I was thinking at least unattended upgrades, sshd and then