Start writing virt hackathon exercise 3.
This commit is contained in:
@ -8,7 +8,7 @@ authors: ['default']
|
|||||||
summary: "Will OpenShift Virtualisation run Acme virtual machines?"
|
summary: "Will OpenShift Virtualisation run Acme virtual machines?"
|
||||||
---
|
---
|
||||||
|
|
||||||
As a sales team you've got an upcoming demo with the Acme Financial Services linux team. They are concerned a modern cloud native virtualisation platform like OpenShift Virtualistion won't support running their **Crusty Corp Financial Appliance™** vm appliances which run Red Hat Enterprise Linux 5.0 and cannot be updated or altered in any way.
|
As a sales team you've got an upcoming demo with the Acme Financial Services linux team. They are concerned a modern cloud native virtualisation platform like OpenShift Virtualistion won't support running their **Crusty Corp Financial Appliance™** vm appliances which run Red Hat Enterprise Linux 5.0 and cannot be updated or altered in any way 🤯.
|
||||||
|
|
||||||
The deal rests on your teams ability to prove that an old operating system will boot successfully within OpenShift Virtualisation.
|
The deal rests on your teams ability to prove that an old operating system will boot successfully within OpenShift Virtualisation.
|
||||||
|
|
||||||
@ -25,6 +25,6 @@ The deal rests on your teams ability to prove that an old operating system will
|
|||||||
|
|
||||||
If your **Crusty Corp Financial Appliance** has booted please post a message in `#rh-hackathon-ocp-virt` with the message:
|
If your **Crusty Corp Financial Appliance** has booted please post a message in `#rh-hackathon-ocp-virt` with the message:
|
||||||
|
|
||||||
> Please review team <name> solution for exercise 2.
|
> Please review team [name] solution for exercise 2.
|
||||||
|
|
||||||
This exercise is worth 25 points. The event team will reply in slack to confirm your updated team total score.
|
This exercise is worth 25 points. The event team will reply in slack to confirm your updated team total score.
|
||||||
|
|||||||
36
data/workshop/scenario3.mdx
Normal file
36
data/workshop/scenario3.mdx
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
---
|
||||||
|
title: But can it do live migration?
|
||||||
|
exercise: 3
|
||||||
|
date: '2024-04-05'
|
||||||
|
tags: ['openshift','virtualisation','kubernetes','kubevirt']
|
||||||
|
draft: false
|
||||||
|
authors: ['default']
|
||||||
|
summary: "Will OpenShift Virtualisation live migrate a virtual machine?"
|
||||||
|
---
|
||||||
|
|
||||||
|
During the demo with the Acme Financial Services team one of their traditional hypervisor team asked if you can show them a live migration for a running virtual machine.
|
||||||
|
|
||||||
|
Thinking on your feet you remember the Fedora virtual machine you've were tinkering with last night in the `demotestblah17` namespace on the cluster.
|
||||||
|
|
||||||
|
The Acme Financial Services team have put you on the spot, can you quickly pull off a virtual machine live migration? 😅
|
||||||
|
|
||||||
|
|
||||||
|
## 2.1 - Confirm the machine current state
|
||||||
|
|
||||||
|
...
|
||||||
|
|
||||||
|
## 2.2 - Initiate the live migration
|
||||||
|
|
||||||
|
...
|
||||||
|
|
||||||
|
## 2.3 - Confirm the workload is uninterrupted
|
||||||
|
|
||||||
|
...
|
||||||
|
|
||||||
|
## 2.4 - Check your work
|
||||||
|
|
||||||
|
If the virtual machine in your **demotestblah17** namespace has been live migrated successfully please post a message in `#rh-hackathon-ocp-virt` with the message:
|
||||||
|
|
||||||
|
> Please review team [name] solution for exercise 3.
|
||||||
|
|
||||||
|
This exercise is worth 25 points. The event team will reply in slack to confirm your updated team total score.
|
||||||
@ -3,21 +3,41 @@
|
|||||||
<channel>
|
<channel>
|
||||||
<title>Red Hat OpenShift Virtualisation Hackathon</title>
|
<title>Red Hat OpenShift Virtualisation Hackathon</title>
|
||||||
<link>https://jmhbnz.github.io/workshops/workshop</link>
|
<link>https://jmhbnz.github.io/workshops/workshop</link>
|
||||||
<description>Red Hat OpenShift Workshops</description>
|
<description>Red Hat OpenShift Virtualisation Hackathon</description>
|
||||||
<language>en-us</language>
|
<language>en-us</language>
|
||||||
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
|
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
|
||||||
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
|
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
|
||||||
<lastBuildDate>Mon, 18 Dec 2023 00:00:00 GMT</lastBuildDate>
|
<lastBuildDate>Fri, 05 Apr 2024 00:00:00 GMT</lastBuildDate>
|
||||||
<atom:link href="https://jmhbnz.github.io/workshops/feed.xml" rel="self" type="application/rss+xml"/>
|
<atom:link href="https://jmhbnz.github.io/workshops/feed.xml" rel="self" type="application/rss+xml"/>
|
||||||
|
|
||||||
<item>
|
<item>
|
||||||
<guid>https://jmhbnz.github.io/workshops/workshop/scenario1</guid>
|
<guid>https://jmhbnz.github.io/workshops/workshop/scenario1</guid>
|
||||||
<title>Understanding our lab environment</title>
|
<title>Understanding the hackathon environment</title>
|
||||||
<link>https://jmhbnz.github.io/workshops/workshop/scenario1</link>
|
<link>https://jmhbnz.github.io/workshops/workshop/scenario1</link>
|
||||||
<description>Let's get familiar with our lab setup.</description>
|
<description>Let's get underway with the hackathon.</description>
|
||||||
<pubDate>Mon, 18 Dec 2023 00:00:00 GMT</pubDate>
|
<pubDate>Fri, 05 Apr 2024 00:00:00 GMT</pubDate>
|
||||||
<author>jablair@redhat.com (Red Hat)</author>
|
<author>jablair@redhat.com (Red Hat)</author>
|
||||||
<category>openshift</category><category>containers</category><category>kubernetes</category><category>disconnected</category>
|
<category>openshift</category><category>virtualisation</category><category>kubernetes</category><category>kubevirt</category>
|
||||||
|
</item>
|
||||||
|
|
||||||
|
<item>
|
||||||
|
<guid>https://jmhbnz.github.io/workshops/workshop/scenario2</guid>
|
||||||
|
<title>How old is too old?</title>
|
||||||
|
<link>https://jmhbnz.github.io/workshops/workshop/scenario2</link>
|
||||||
|
<description>Will OpenShift Virtualisation run Acme virtual machines?</description>
|
||||||
|
<pubDate>Fri, 05 Apr 2024 00:00:00 GMT</pubDate>
|
||||||
|
<author>jablair@redhat.com (Red Hat)</author>
|
||||||
|
<category>openshift</category><category>virtualisation</category><category>kubernetes</category><category>kubevirt</category>
|
||||||
|
</item>
|
||||||
|
|
||||||
|
<item>
|
||||||
|
<guid>https://jmhbnz.github.io/workshops/workshop/scenario3</guid>
|
||||||
|
<title>But can it do live migration?</title>
|
||||||
|
<link>https://jmhbnz.github.io/workshops/workshop/scenario3</link>
|
||||||
|
<description>Will OpenShift Virtualisation live migrate a virtual machine?</description>
|
||||||
|
<pubDate>Fri, 05 Apr 2024 00:00:00 GMT</pubDate>
|
||||||
|
<author>jablair@redhat.com (Red Hat)</author>
|
||||||
|
<category>openshift</category><category>virtualisation</category><category>kubernetes</category><category>kubevirt</category>
|
||||||
</item>
|
</item>
|
||||||
|
|
||||||
</channel>
|
</channel>
|
||||||
|
|||||||
Reference in New Issue
Block a user