weaveworks
How to implement Firecracker Snapshotting in Ignite
This feature is not yet supported by firecracker, but they do have a roadmap issue for it: https://github.com/firecracker-microvm/firecracker/issues/1184
Ignite is dependent on firecracker for support of hardware/virt level features such as VM runtime snapshots.
I'm curious about your use-case here. Ignite makes it possible to bake properly pre-configured images and re-create fresh VM's quickly. How would you want to use snapshots or imagine how it would work?
I would like to be in control of being able to create a snapshot at runtime and be able to automate it from the backend as an alternative backup method.
@stealthybox for us FireCracker snapshot is needed to decrease the cold starts in serverless. This would be good not only to reduce VM start, but to remove Node.js startup time. This is especially important for applications with that use Java VM, like Lucene. I am curious as to what delays we will incur on restoring from the snapshop (I understand it is highly dependend on I/O in a particular setup)
This feature is available in dev preview now: https://github.com/firecracker-microvm/firecracker/blob/v0.23.0/docs/snapshotting/snapshot-support.md
Would be great to see Ignite add subcommands which support this, in particular which make resumed VMs work with newly allocated CNI addresses, and any other issues that come up.
Do you have any update on this? as firecracker now has snapshotting support (since 2020) do we have any ignite commands (existing or in-devlopment) to create snapshots for ignite VMs?
