modifying live migration section, updating database service

rhpds · Sep 16, 2024 · c2138d8 · c2138d8
1 parent 4f0e9f0
commit c2138d8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/content/modules/ROOT/pages/module-01-intro.adoc b/content/modules/ROOT/pages/module-01-intro.adoc
@@ -188,13 +188,13 @@ Only cluster administrators can see the Node - the screenshot is an example of w
 +
 image::module-01-intro/21_VM_Dialog_Migrate.png[link=self, window=blank, width=100%]
 
-. After a few seconds, the VM will change the status to *Migrating*. A few seconds later, it will return to the *Running* status, but on a new node. The VM has been successfully live migrated!
+. After a few seconds, the VM will change the status to *Migrating*, and you can follow it's progress. When it is complete it will return to the *Running* status, but on a new node. 
 +
-image::module-01-intro/22_Migrated.png[link=self, window=blank, width=100%]
 
-. You can see the VM moving between nodes if you look at the Pod that is running the VM. Blink and you'll miss it though!
-+
 image::module-01-intro/23_PodLink.png[link=self, window=blank, width=100%]
+
+. If you would like to see the guest switch nodes, you can do so on the *Pod Details* screen by clicking on the pod name on the right. You can see the node the VM lives on, and it's new node when it changes. The cutover is fairly quick, blink and you may miss it!
++
 image::module-01-intro/24_Pod.png[link=self, window=blank, width=100%]
 
 == Summary

diff --git a/content/modules/ROOT/pages/module-08-workingvms.adoc b/content/modules/ROOT/pages/module-08-workingvms.adoc
@@ -127,14 +127,14 @@ metadata:
   namespace: vmexamples-{user}
 spec:
   selector:
-    vm.kubevirt.io/name: database
+    vm.kubevirt.io/name: {DATABASE_VM_NAME}
   ports:
   - protocol: TCP
     port: 3306
     targetPort: 3306
 ----
 +
-NOTE: This time we used the name of the virtual machine to attach it to the service we are creating, since there is only one VM named *database* in the namespace with this name it is safe to do so without having to customize the YAML of the VM or rebooting the guest.
+NOTE: This time we used the name of the virtual machine to attach it to the service we are creating, make sure that you update the YAML when you copy/paste it to ensure that you are using the correct name for the database instance in your lab environment.
 +
 image::module-08-workingvms/21_Database_YAML.png[link=self, window=blank, width=100%]