jmhbnz/workshops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add captions for remaining images.

Browse Source
This commit is contained in:
James Blair
2023-12-05 22:33:47 +13:00
parent e8fe498612
commit 91d7b21673
2 changed files with 29 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
data/workshop/exercise1.mdx
View File

@ -23,7 +23,9 @@ An OpenShift `4.14` cluster has already been provisioned for you to complete the
Once the page loads you can login with the details provided by your workshop facilitator.
<Zoom>
![workshop](/ocp-app-delivery-workshop/static/images/workshop.png)
|![workshop](/ocp-app-delivery-workshop/static/images/workshop.png) |
|:-----------------------------------------------------------------------------:|
| *Workshop login page* |
</Zoom>
@ -34,7 +36,9 @@ Once you're logged into the lab environnment we can open up the OpenShift web co
When first logging in you will be prompted to take a tour of the **Developer** console view, let's do that now.
<Zoom>
![tour](/ocp-app-delivery-workshop/static/images/tour.gif)
| ![tour](/ocp-app-delivery-workshop/static/images/tour.gif) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective web console tour* |
</Zoom>
@ -48,10 +52,12 @@ Projects act as a "wrapper" around all the application services you (or your tea
In this lab environment, you already have access to single project: `userX` (Where X is the number of your user allocted for the workshop.)
Let's click into our `Project` from the left hand panel of the "Developer" web console view. We should be able to see that our project has no `Deployments` and there are no compute cpu or memory resources currently being consumed.
Let's click into our `Project` from the left hand panel of the **Developer** web console perspective. We should be able to see that our project has no `Deployments` and there are no compute cpu or memory resources currently being consumed.
<Zoom>
![project](/ocp-app-delivery-workshop/static/images/project.png)
|![project](/ocp-app-delivery-workshop/static/images/project.png) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective project view* |
</Zoom>
@ -68,10 +74,13 @@ Switch back to the **Developer** perspective. Once the Developer perspective loa
Right now, there are no applications or components to view in your `userX` project, but once you begin working on the lab, you’ll be able to visualize and interact with the components in your application here.
<Zoom>
![perspectives](/ocp-app-delivery-workshop/static/images/perspectives.gif)
|![perspectives](/ocp-app-delivery-workshop/static/images/perspectives.gif) |
|:-----------------------------------------------------------------------------:|
| *Switching web console perspectives* |
</Zoom>
## 1.5 - Launching a web terminal
While web interfaces are comfortable and easy to use, sometimes we want to quickly run commands to get things done. That is where the `oc` command line utility comes in.
@ -81,7 +90,9 @@ One handy feature of the OpenShift web console is we can launch a web terminal t
Let's launch a web terminal now by clicking the terminal button in the top right hand corner and then clicking **Start** with our `userX` project selected.
<Zoom>
![web-terminal](/ocp-app-delivery-workshop/static/images/web-terminal.gif)
|![web-terminal](/ocp-app-delivery-workshop/static/images/web-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Launching your web terminal* |
</Zoom>
@ -172,5 +183,8 @@ DESCRIPTION:
That's a quick introduction to the `oc` command line utility. Let's close our web terminal now so we can move on to the next excercise.
<Zoom>
![close-terminal](/ocp-app-delivery-workshop/static/images/close-terminal.gif)
|![close-terminal](/ocp-app-delivery-workshop/static/images/close-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Closing your web terminal* |
</Zoom>

8
data/workshop/exercise2.mdx
View File

@ -39,3 +39,11 @@ OpenShift will pull this container image if it does not exist already on the clu
|:-------------------------------------------------------------------:|
| *Deploying the container image* |
</Zoom>
## 2.2 - Observing our deployed application
If you click on the **parksmap** entry in the **Topology** view, you will see some information about that deployed application.
The Resources tab may be displayed by default. If so, click on the Details tab. On that panel, you will see that there is a single Pod that was created by your actions.