Skip to content

Commit 00ce00a

Browse files
authored
Merge pull request #3080 from hpe-dev-incubator/cms/blog/open-sourcing-workshops-on-demand-part2-deploying-the-backend
Update Blog “open-sourcing-workshops-on-demand-part2-deploying-the-backend”
2 parents 930cdff + b7dfaab commit 00ce00a

File tree

2 files changed

+19
-9
lines changed

2 files changed

+19
-9
lines changed

content/blog/open-sourcing-workshops-on-demand-part2-deploying-the-backend.md

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,10 @@ Here's a quick look at what can be found in each:
3636

3737
* You can test them live at <https://hackshack.hpedev.io/workshops>
3838

39+
**[wod-install](https://github.com/Workshops-on-Demand/wod-install):** Installer part of the Workshops-on-Demand project.
40+
41+
**[wod-backend](https://github.com/Workshops-on-Demand/wod-backend):** Back-end part of our Workshops-on-Demand setup.
42+
3943
**[wod-frontend](https://github.com/Workshops-on-Demand/wod-frontend):** Frontend part of the Workshops-on-Demand project.
4044

4145
* Based on NGINX and NodeJS technologies, it provides the participtants' Registration Portal used to enable booking of the workshops.
@@ -46,18 +50,19 @@ Here's a quick look at what can be found in each:
4650

4751
**[wod-private](https://github.com/Workshops-on-Demand/wod-private):** Example Private configuration for Workshops-on-Demand (WoD).
4852

49-
* This provide an example for creating your own cutomization layer on top of the public standard WoD Backend / wod Notebooks content. Do not put any confidential data here as this is a public repository!
50-
51-
**[wod-backend](https://github.com/Workshops-on-Demand/wod-backend):** Back-end part of our Workshops-on-Demand setup.
53+
**[wod-frontend-private](https://github.com/Workshops-on-Demand/wod-frontend-private):** Private Frontend part of the Workshops-on-Demand project.
5254

53-
**Note**: There are only 3 repositories available for now. The missing 2 will show up later.
55+
**[wod-api-db-private](https://github.com/Workshops-on-Demand/wod-api-db-private):** Workshops-on-Demand registration portal application
5456

57+
* This provide examples for creating your own cutomization layer on top of the public standard WoD Backend / wod Notebooks content. Do not put any confidential data here as this is a public repository!
5558

59+
**Note**: There are now 7 repositories available for now.
5660

57-
![](/img/wod-blogserie2repos.png "Workshops-on-Demand repositories")
61+
![](/img/wod-blogserie2-2repos.png "Workshops-on-Demand repositories")
5862

5963
It provides:
6064

65+
* An Installer allowing you to install either Backend, Api-DB server, or Frontend using a single line of command.
6166
* A complete JupyterHub server with some addons (additional Jupyterhub kernels, Ansible galaxies, and PowerShell libraries) on your system, ready to host Workshops-on-Demand that you can find here.
6267
* A postfix server used for the procmail API
6368
* An Ansible engine to allow automation
@@ -78,7 +83,7 @@ Before cloning the backend repository, you will need to prepare the server th
7883

7984
In order to setup the backend server, you will need:
8085

81-
* A fresh OS install on physical / virtualized server running Ubuntu 20.04 or Centos 7.9 leveraging any deployment mechanism of your choice.(e.g. iLO, vagrant, etc.). You may even use this vagrant file to automatically generate a complete setup leveraging vagrant, libvirt and QEMU/KVM.
86+
* A fresh OS install on physical / virtualized server running Ubuntu 24.04 or Centos 7.9 leveraging any deployment mechanism of your choice.(e.g. iLO, vagrant, etc.). You may even use this vagrant file to automatically generate a complete setup leveraging vagrant, libvirt and QEMU/KVM.
8287
* A Linux account with sudo priviledges on your Linux distro. Name it `install`
8388

8489
**Note**: In order to support 100 concurrent users, you need:
@@ -91,11 +96,11 @@ We are currently using an HPE ProLiant DL360 Gen10 server on our different produ
9196

9297
When done with OS installation and preparation
9398

94-
* From the WoD-backend server (aka JupyterHub server), as the install user, you will need to clone the repo first.
99+
* From the WoD-backend server (aka JupyterHub server), as the install user, you will need to clone the wod-install repo first.
95100

96101
```shellsession
97-
install$ git clone https://github.com/Workshops-on-Demand/wod-backend.git
98-
install$ cd wod-backend/
102+
install$ git clone https://github.com/Workshops-on-Demand/wod-install.git
103+
install$ cd wod-install/
99104
```
100105

101106
* Examine default installation parameters and adapt when necessary accordingly. Files are self-documented.
@@ -270,6 +275,11 @@ WODFEAPIPWD: MotDePasseCompliquéAussi125!!!##
270275

271276
### Backend installation process:
272277

278+
The installation process is handled by a dedicated repo : wod-install. This repo needs to be cloned on every single machine constituting the wod architecture.
279+
280+
The wod installer allows through a single command to install either a backend, an api-db server, or a frontend.
281+
282+
273283
[](https://github.com/Workshops-on-Demand/wod-backend/blob/main/INSTALL.md#for-private-based-workshops-on-demand-private-backend--private-workshops-or-if-you-need-to-modify-defaults)Once you are done with the files, you can can proceed with the installation itself. The installation is based on a common install script [install.sh ](https://github.com/Workshops-on-Demand/wod-backend/blob/main/install/install.sh)that allows the deployment of the different parts of the solution. It can be called as follows:
274284

275285
`install.sh [-h][-t type][-g groupname][-b backend][-f frontend][-a api-db][-e external][-u user][-s sender]`

static/img/wod-blogserie2-2repos.png

403 KB
Loading

0 commit comments

Comments
 (0)