Skip to content

Commit a424631

Browse files
committed
Update Blog “open-sourcing-workshops-on-demand-part-5-create-a-workshop”
1 parent b4e0489 commit a424631

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,47 @@ As the developer of the Workshops-on-demand content, Matt had to perform seve
113113
5. ###### Test the workshop using the staging registration portal.
114114
6. ###### When all tests are green, create a pull request to merge content with master repo.
115115

116+
As an admin, I need to check the pull request and accept it. Once done, the test/dev and staging environments will require an update.
117+
118+
1. ###### Log on to the backend server as wodadmin and update the notebook repository.
119+
2. ###### Run a wod-deliver to update the relevant backend server.
120+
121+
```
122+
git remote update
123+
git rebase
124+
wod-deliver
125+
```
126+
127+
The very same processes will apply to the move to production phase.
128+
129+
130+
116131
* Modifying the \[backend server installation yaml file ]
117132

133+
134+
135+
# Complex workshop example:
136+
137+
II will not repeat the steps I descirbed earlier for the simple workshop example. I will focus here on the specific aspects related to this new workshop. Are you familiar with High Performance Computing (HPC)? I am not. Even tough I am surrounded by some experts in that field in the HPE Grenoble Office. Let's consider that one of these colleagues is willing to build up a dedicated workshop on HPC Stax. As usual, we will start by a meeting each of us will explain to the other his goals, and how to achieve them. Once I get a clearer understanding of the technology involved, he and I can move on figure out the best platform to run his woorkshop on.
138+
139+
As an admin of the Workshops-on-demand infrastructure, I had to perform several tasks:
140+
141+
##### On the backend server:
142+
143+
the workshop will require:
144+
145+
* A dedicated server running docker to host the student containers in which the workshops' labs will take place.
146+
147+
* A set of Ansible playbooks to setup the dedicated server.
148+
149+
* A set of scripts to manage the workshop's lifecycle.
150+
151+
* A set of variables to be leveraged by the notebooks.
152+
153+
154+
155+
156+
118157
A set of notebooks that will be used by the student to follow instructions cells in markdown and run code cells leveraging the relevant kernel. If you are not familiar with Jupyter notebooks, a simple [101 workshop](https://developer.hpe.com/hackshack/workshop/25) is available in our Workshops-on-Demand 's catalog.
119158

120159
Optional:

0 commit comments

Comments
 (0)