You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/open-sourcing-workshops-on-demand-part-5-create-a-workshop.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,13 +184,13 @@ The workshop will require:
184
184
* reset-appliance (reset ssh keys and students credentials on appliance
185
185
* cleanup-\[WKSHP-NAME].sh (takes care of cleanup some workshop's specifics)
186
186
* 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
188
188
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.
190
190
191
-
* From the cli on the jupyterhub server:
191
+
Testing the workshop:
192
192
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.
194
194
195
195
```
196
196
dev@dev3:~$ wod-test-action.sh
@@ -199,7 +199,9 @@ Whenever all the scripts are functional and that the necessary actions have been
199
199
```
200
200
* The available trace under ~/.mail/from will detail the different steps of the action and allow you to troubelshoot any issue.
201
201
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.
0 commit comments