automatic migration for critical guest, router

[gowger]

I'd like to add a shutdown hook so to speak, in systemd to automate the migration of a guest upon intentional reboot of a host. The guest is a router and firewall so it must have low downtime and I like to keep my security patches up to date. My goal is simply saving time, instead of manually migrating hosts every time.

Can anyone tell me if there's any reasons this is a terrible idea?

The router is a pfsense instance and I haven't got it runnning in HA and CARP mode yet, so this would be a short term solution until that is working. I'd still consider keeping after that none the less.

 

[Alwin]

This will introduce more complexity and failure potential. To save time and repeat the same steps over-and-over, use a system/configuration automation tool (eg. ansible, puppet, salt, ...)

 

[adamb]

I agree, ive seen live migration fail enough that I wouldn't trust it in such a scenario.

 

[gowger]

very good, will be adding to ansible library in my case. Some minor bug in latest ansible proxmox lib that needs a patch merging in.