doc: keep instances running during update/upgrade #609
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Minae Lee <[email protected]>
roosterfish
approved these changes
Feb 5, 2025
| To ensure that the update or upgrade does not affect workloads on running instances at all, use the following live-migration approach: | ||
|
|
||
| - Use virtual machines (VMs) instead of system containers for crucial workloads; in general, containers cannot be live-migrated. | ||
| - Each VM must be pre-configured for live migration. See: {ref}`lxd:live-migration-vms` for information on the required configurations. |
There was a problem hiding this comment.
We have fixed this already in v2-edge and it should be configured by default starting with the next MicroCloud release if you create a new cluster.
But for now I think it makes sense to explicitly document this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a section in the How to update and upgrade docs page to explain that instances can be left running during and update/upgrade but the storage/network services might briefly be affected. It also explains how to use cluster evacuate to migrate instances away before an update/upgrade, including live migration for pre-configured VMs, and how to use cluster restore to migrate them back afterward.