Skip to content
Snippets Groups Projects
Commit c5477f6f authored by Jan David Mol's avatar Jan David Mol
Browse files

L2SS-391: Better split of bootstrap and startup

parent 3fc93b10
No related branches found
No related tags found
1 merge request!144L2SS-391: Add boot device
......@@ -22,20 +22,15 @@ You will also need:
* python3.7+
* pip
## Bootstrap
## Bootstra
First we build all docker containers, and load the initial configuration. This may take a while:
The bootstrap procedure is needed only once. First we build all docker containers, and load the initial configuration. This may take a while:
```
cd docker-compose
make bootstrap
```
Once per reboot, the host kernel needs to be configured. This is already included in `make bootstrap`:
```
make start elk-configure-host
```
If you lack access to LOFAR station hardware, configure the devices to use their simulators instead:
```
......@@ -44,8 +39,6 @@ for sim in ../CDB/*-sim-config.json; do
done
```
## Start up
Now we can start all containers, and make sure everything is up:
```
......@@ -53,9 +46,17 @@ make start
make status
```
If not, you can inspect why with `docker logs <container>`.
If not, you can inspect why with `docker logs <container>`. The containers will automatically be restarted on reboot or failure. Stop them explicitly to bring them down (`make stop <container>`).
## Start up
The start-up procedure is needed both after bootstrapping and after a system reboot. Once per reboot, the host kernel needs to be configured:
```
make start elk-configure-host
```
The software devices start in an OFF state. To boot the devices, go to Jupyter (port 8888), start a new notebook, and run:
The software devices start in an OFF state, after bootstrap or reboot. To boot the devices, go to Jupyter (port 8888), start a new notebook, and run:
```
# start boot device
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment