Refactor VM snapshot management #802
Assignees
Labels
enhancement
New feature or request
Comments
CuriousGeorgiy
added a commit
to CuriousGeorgiy/vHive
that referenced
this issue
Sep 6, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With vhive-serverless#794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes vhive-serverless#802 Part of vhive-serverless#794 Signed-off-by: Georgiy Lebedev <[email protected]>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/vHive
that referenced
this issue
Sep 6, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With vhive-serverless#794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes vhive-serverless#802 Part of vhive-serverless#794 Signed-off-by: Georgiy Lebedev <[email protected]>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/vHive
that referenced
this issue
Sep 8, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With vhive-serverless#794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes vhive-serverless#802 Part of vhive-serverless#794 Signed-off-by: Georgiy Lebedev <[email protected]>
leokondrashov
pushed a commit
to CuriousGeorgiy/vHive
that referenced
this issue
Sep 11, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With vhive-serverless#794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes vhive-serverless#802 Part of vhive-serverless#794 Signed-off-by: Georgiy Lebedev <[email protected]>
leokondrashov
pushed a commit
to CuriousGeorgiy/vHive
that referenced
this issue
Sep 11, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With vhive-serverless#794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes vhive-serverless#802 Part of vhive-serverless#794 Signed-off-by: Georgiy Lebedev <[email protected]>
leokondrashov
pushed a commit
that referenced
this issue
Sep 11, 2023
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With #794 snapshot management will become more complicated, and thus it requires refactoring into a separate component. Closes #802 Part of #794 Signed-off-by: Georgiy Lebedev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, VM snapshots are managed by the orchestrator via a table of idle function instances. With #794 snapshot management will become more complicated and thus it requires refactoring into a separate component.
The text was updated successfully, but these errors were encountered: