Completed exercise 6. Polished earlier exercises.

data/workshop/scenario1.mdx

@@ -67,3 +67,12 @@ If your team have secured an environment and are ready to start the challenge pl
 > [team name] have logged into an environment and are starting the challenge!
 
 The event team will reply in slack to confirm your team has been recorded and start you with a base score of `10` points.
+
+
+## 1.5 - Hints!
+
+If you get stuck on a question, fear not, perhaps try a different approach. If you have tried everything you can think of and are still stuck you can unlock a hint for `3` points by posting a message in the `#event-anz-ocp-virt-hackathon` channel with the message:
+
+> [team name] are stuck on [exercise] and are unlocking a hint.
+
+A hackathon organiser will join your breakout room to share the hint with you 🤫.

data/workshop/scenario2.mdx

@@ -19,6 +19,8 @@ For this task, your team are required to use this [`CentOS-5.11-x86_64-netinstal
 
 No command line is required. Your challenge is to create and boot a virtual machine on your cluster using the name `crusty-corp-fun-financial-appliance`, within the namespace `crusty-corp`.
 
+**Note: You don't need to complete the CentOS 5 install, you just need to get the machine to boot into the installer.**
+
 Documentation you may find helpful is:
 - https://docs.openshift.com/container-platform/4.15/virt/virtual_machines/creating_vms_custom/virt-creating-vms-from-custom-images-overview.html
 

data/workshop/scenario5.mdx

@@ -53,10 +53,11 @@ While you're on the Skype for Business™ video call with Chad fixing the `crypt
 
 This is a straightforward table stakes procedure for any virtualisation platform so you offer to step Chad through it then and there and get it out of the way.
 
-Your task is to add an additional `20GiB` disk labelled `wannacry` to the virtual machine. No command line is required.
+Your task is to add an additional `20GiB` disk labelled `wannacry` to the virtual machine. No command line is required, however you may have to get creative and manually create the volume and update the virtual machine spec if your OpenShift console "Configure --> Add Disk" functionality isn't working.
 
 Documentation you may find helpful is:
 - https://docs.openshift.com/container-platform/4.15/virt/virtual_machines/virtual_disks/virt-hot-plugging-virtual-disks.html
+- https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html/managing_and_allocating_storage_resources/managing-persistent-volume-claims_rhodf#configuring-application-pods-to-use-openshift-data-foundation_rhodf
 
 
 ## 5.3 - Check your work

data/workshop/scenario6.mdx

@@ -10,7 +10,7 @@ summary: "How do we make a virtual machine accessible over the OpenShift SDN"
 
 Time flies when you're having fun, after 17 months the "quick" proof of concept for OpenShift Virtualisation has now completed at Acme Financial Services and the CTO has asked for a final presentation from the local Red Hat pre sales team.
 
-The Acme team have kept talking about modernisation throughout the proof of concept so for the final demo your local Red Hat team agree to showcase how container workloads can be run alongside virtual machines and even balance traffic across containers and virtual machines.
+The Acme team have talked about modernisation throughout the proof of concept so for the final demo your local Red Hat team agree to again showcase how container workloads can be run alongside virtual machines and even balance traffic across containers and virtual machines.
 
 This is it. No pressure but we need to nail this!
 
@@ -25,13 +25,30 @@ This is it. No pressure but we need to nail this!
 
 Your first challenge for this exercise is to deploy two workloads within the `acme-bank` namespace on your cluster:
 
-1. The container image `quay.io/jmhbnz/acme-bank:latest`.
-2. A virtual machine running that same workload (in podman for simplicity).
+1. The container image `quay.io/redhattraining/hello-world-nginx` running as a standard `deployment` named `acme-pod`, listening on port `8080`.
 
+2. A linux virtual machine named `acme-vm` running that same workload on port `8080` in podman for simplicity.
+
+Documentation you may find helpful is:
+- https://docs.openshift.com/container-platform/4.15/applications/creating_applications/odc-creating-applications-using-developer-perspective.html#odc-deploying-container-image_odc-creating-applications-using-developer-perspective
+- https://podman.io/docs/installation#installing-on-linux
+- https://developers.redhat.com/cheat-sheets/podman-cheat-sheet
 
 ## 6.2 - Establish networking
 
-Once the workloads are deployed your challenge is to create one service that will load balance traffic across the virtual machine and regular container.
+Once the workloads are deployed your challenge is to create one service named `acme-balancer` that will load balance traffic across the virtual machine and regular container.
+
+You'll know if this is working correctly when you can see two pods appearing in your service pod listing:
+
+<Zoom>
+|![workshop](/workshops/static/images/hackathon/vm-pod-service.png)             | 
+|:-----------------------------------------------------------------------------:|
+| *"The best of both worlds!"*                                                  |
+</Zoom>
+
+Documentation you may find helpful is:
+- https://docs.openshift.com/container-platform/4.15/virt/vm_networking/virt-exposing-vm-with-service.html
+- https://kubernetes.io/docs/concepts/services-networking/service
 
 
 ## 6.2 - Check your work