Hi Conrad,
On Thu, Apr 18, 2024 at 11:50:59AM +0100, Conrad Wood via BitFolk Users wrote:
My usecase would be something like this:
1) trigger image via http/wget/curl/API
2) poll for it be completed
3) download image
4) delete image (via some api)
Okay so this is a slightly different set of concerns for us, because
snapshots are at the moment full LVM snapshots which consume disk
space and negatively affect IO performance, which means they need to
be fairly short-lived.
In the solution I am proposing for the one customer who asked,
BitFolk is going to be in control of how long the LVM snapshot stays
around for, so we can keep that burden acceptable. We archive it off
and delete the snapshot quite quickly.
There is always interest in disk snapshots, so possibly it is worth
looking into moving to some other snapshot technology. There is no
getting away from the fact that snapshots use storage though, so
either the storage used will have to be paid for or the lifetime of
the snapshots will have to be limited in some way.
To restore an image, some sort of upload would need to
be
available
Yes it is already possible to overwrite your VM's disk with your own
image from the Rescue VM. Of course if there was some disk imaging
or snapshots feature then it wouldn't be very hard to have some
button in the Panel that restores to it also.
Unless using one of the more advanced filesystems, taking a coherent
snapshot is something that is not easy for a customer to do
themselves, whereas restoring one is, so possibly it is worth
focusing on making just the former a feature, rather than the whole
bit about storing multiple incrementals.
with qemu/kvm. the "live migration" feature
essentially gives you
a consistent view of disk+memory+devicestate that one can store.
There is a save state command but before looking into this I wanted
to see what people's thoughts were.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting