Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote firecracker snapshots #823

Open
CuriousGeorgiy opened this issue Sep 18, 2023 · 0 comments
Open

Remote firecracker snapshots #823

CuriousGeorgiy opened this issue Sep 18, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@CuriousGeorgiy
Copy link
Member

CuriousGeorgiy commented Sep 18, 2023

Describe the enhancement
Rather than only using the snapshots available locally on a node, snapshots can also be transferred between nodes to potentially accelerate cold start times and reduce memory utilization, given that proper mechanisms are in place to minimize the snapshot network transfer latency. This could be done by storing snapshots in a global storage solution
such as MinIO S3, or directly distributing snapshots between compute nodes.

Problem
Currently, the blocker for using remote snapshots is container disk state restoration. Containers restored on a clean node seem to be healthy, and respond to requests, but their disk state gets corrupted after a request is received.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant