Skip to content

Commit f5673ff

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

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

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

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -184,13 +184,13 @@ The workshop will require:
184184
* reset-appliance (reset ssh keys and students credentials on appliance
185185
* cleanup-\[WKSHP-NAME].sh (takes care of cleanup some workshop's specifics)
186186
* reset-\[WKSHP-NAME].sh (reset of the workshop's appliance, docker compose down of a container for instance)
187-
* A set of variables to be leveraged by the notebooks. These variables are to be set in yml format. They will be parsed at deployment times to set student ids, appliance IP addresses, and other relevant parameters like ports, simulated hardware information for instance.
187+
* A set of variables to be leveraged by the notebooks. These variables are to be set in yml format. They will be parsed at deployment time to set student ids, appliance IP addresses, and other relevant parameters like ports, or simulated hardware information
188188

189-
Whenever all the scripts are functional and that the necessary actions have been performed both on backend and frontend servers, some functional tests can conducted using cli and later webui as described earlier for the simple workshop example.
189+
Whenever all the scripts are functional and that the necessary actions have been performed both on backend and frontend servers, some functional tests can be conducted using cli and later webui as described earlier for the simple workshop example.
190190

191-
* From the cli on the jupyterhub server:
191+
Testing the workshop:
192192

193-
* one can leverage the wod-test-action.sh script to test a workshop lifecycle action from deployment (CREATE) to cleanup, rest or purge.
193+
* one can leverage the wod-test-action.sh script to test a workshop lifecycle action from deployment (CREATE) to CLEANUP, RESET, or PURGE.
194194

195195
```
196196
dev@dev3:~$ wod-test-action.sh
@@ -199,7 +199,9 @@ Whenever all the scripts are functional and that the necessary actions have been
199199
```
200200
* The available trace under ~/.mail/from will detail the different steps of the action and allow you to troubelshoot any issue.
201201
202-
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.
202+
* A set of notebooks that will be used by the student:
203+
204+
* Containing 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.
203205
204206
A workshop should come up with at least :
205207

0 commit comments

Comments
 (0)