-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #32 from acend/feat/livemigration
Initial Live Migration lab
- Loading branch information
Showing
3 changed files
with
443 additions
and
1 deletion.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
title: "Live Migration" | ||
weight: 7 | ||
labfoldernumber: "07" | ||
sectionnumber: 7 | ||
description: > | ||
Migrate running VMs to other Nodes for maintenance or other reasons | ||
--- | ||
|
||
In this section we will get familiar with the concept of the Live Migration capabilities in KubeVirt. | ||
|
||
The idea of live migration is a familiar one in virtualization platforms, allowing administrators to keep workloads operational while servers are taken offline for various reasons, such as: | ||
|
||
* Hardware maintenance (e.g., physical repairs, firmware updates) | ||
* Power management by consolidating workloads onto fewer hypervisors during off-peak times | ||
* And more | ||
|
||
Similarly, KubeVirt offers the ability to migrate virtual machines within Kubernetes when this feature is enabled. | ||
|
||
|
||
## Lab Goals | ||
|
||
* Know what the Concept of Live Migration is | ||
* Understand when workload can be live migrated and when not | ||
* Execute a live migration |
Oops, something went wrong.