Telecominfraproject/wlan-cloud-ucentral-deploy
1
0
Fork 0
mirror of https://github.com/Telecominfraproject/wlan-cloud-ucentral-deploy.git synced 2026-01-27 10:23:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adjust owls image tags as new ones don't work

Browse Source 
Signed-off-by: Carsten Schafer <Carsten.Schafer@kinarasystems.com>
This commit is contained in:
Carsten Schafer
2024-07-29 14:02:03 -04:00
parent 0185aece01
commit f8dcdf64f3
4 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
chart/environment-values/values.openwifi-qa.owls-external.yaml
View File

@@ -45,3 +45,7 @@ owprov:
# controller:
# persistence:
# size: 80Gi
# extraConfig: |-
# # consider tuning this as otherwise kafka storage may be exceeeded quickly
# # the default is 1 week!
# logRetentionHours = 24

1
docker-compose/README.md
View File

@@ -235,6 +235,7 @@ For the Let's Encrypt challenge to work you need a public IP address. The hostna
| `SYSTEM_URI_PUBLIC` | Set this to your OWSub URL, for example `https://openwifi.example.com:16006`. |
| `SYSTEM_URI_UI` | Set this to your OWGW-UI URL, for example `https://openwifi.example.com`. |
### traefik.env
| Variable | Description |
| --------------------------------------------------- | ----------------------------------------- |

10
docker-compose/owls/.env
View File

@@ -1,9 +1,13 @@
COMPOSE_PROJECT_NAME=owls
# Image tags
OWSEC_TAG=main
OWLS_TAG=main
OWLSUI_TAG=master
# Currently main branches don't work - owlsui is not compatible with owls.
#OWSEC_TAG=main
#OWLS_TAG=main
#OWLSUI_TAG=master
OWSEC_TAG=v2.9.0
OWLS_TAG=v2.9.0
OWLSUI_TAG=v2.9.0
KAFKA_TAG=3.7-debian-12
# Microservice root/config directories

2
docker-compose/owls/README.md
View File

@@ -1,6 +1,6 @@
# OpenWifi OWLS Docker Compose
## Deployment with self-signed certificates
To run a load simulation you need to generate a specific Digicert-signed AP certificate which will be used to connect to the gateway. The certificate serial number has to start with the digits `53494d` since otherwise the gateway won't allow a load simulation. The rest of the serial number and the specified redirector URL can be chosen randomly. You only need to generate one AP certificate for your simulations.
To run a load simulation you need to generate a specific Digicert-signed AP certificate which will be used to connect to the gateway. The certificate serial number has to start with the digits `53494d` since otherwise the gateway won't allow a load simulation. The rest of the serial number and the specified redirector URL can be chosen randomly. You only need to generate one AP certificate for your simulations.
Be aware that since the OWLS deployment partly exposes the same ports on the host as the OpenWifi deployment, it is not intended that both run on the same host.
1. Copy or move your AP load simulation certificate into the `docker-compose/certs` directory. Don't forget to name the files `device-cert.pem` and `device-key.pem` or adapt the path names in the OWLS configuration if you're using different file names.
2. To be able to run load simulation tests against your OpenWifi SDK deployment, you'll have to [add the serial number of your generated AP certificate to the gateway configuration](https://github.com/Telecominfraproject/wlan-cloud-owls#prepare-your-openwifi-gateway). You can do that by either editing [owgw.env](../owgw.env) or doing the changes directly in your OWGW configuration file if it is exposed on your Docker host.