On 25/12/19 10:30 pm, Sriram Narayanan wrote: > On Wed, 25 Dec 2019 at 7:41 PM, Stuart Longland <stua...@longlandclan.id.au> > wrote: > >> Both VMs should probably be re-built from scratch as a matter of sanity, >> but I can do that at leisure now, what I have, works. > > > What hypervisor are you using? Does it support an API to create VM from ISO > images and to launch VMs from templates?
I'm using OpenNebula atop Linux KVM with a Ceph storage back-end. https://hackaday.io/project/10529-solar-powered-cloud-computing It does have templates, but only one of the VMs concerned are actually being managed by OpenNebula (my own; sjl-router). The other (corerouter) is actually a bare KVM virtual machine managed outside OpenNebula as the plan was to set up corosync to auto-migrate it and the VM that runs the OpenNebula front-end between the two compute nodes. Since it is the route by which the OpenNebula VM reaches the host nodes, it can't be managed by OpenNebula. So templates are not a solution. … > This would help you to cut over when needed, cut back in case of issues, > and have the ability to recover thanks to your automation. It would, and if I were managing dozens of them all with a largely identical pattern, I'd definitely look into it. My VMs tend to be pets, not cattle¹. They're all highly specialised to the task they're performing and none of them are really alike, so templating really doesn't work in that context. Regards, -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. 1. http://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/ (In truth, my hosts are also pet-like, because I only have a small number of them.)
