The OWSUB is a service for the TIP OpenWiFi CloudSDK (OWSDK). OWSUB provides a subscriber management service to the Subscriber App and interacts with the rest of the Cloud SDK. OWSUB, like all other OWSDK microservices, is defined using an OpenAPI definition and uses the ucentral communication protocol to interact with Access Points. To use the OWSUB, you either need to build it or use the Docker version.
You may get static page with OpenAPI docs generated from the definition on GitHub Page.
To build the microservice from source, please follow the instructions in here
To use the CLoudSDK deployment please follow here Also, you may use Swagger UI with OpenAPI definition file raw link (i.e. latest version file) to get interactive docs page.
From the directory where your cloned source is, you will need to create the certs
, logs
, and uploads
directories.
mkdir certs
mkdir certs/cas
mkdir logs
mkdir uploads
You should now have the following:
--+-- certs
| +--- cas
+-- cmake
+-- cmake-build
+-- logs
+-- src
+-- test_scripts
+-- openapi
+-- uploads
+-- owsub.properties
The OWSUB uses a certificate to provide security for the REST API Certificate to secure the Northbound API.
For all deployments, you will need the following certs
directory, populated with the proper files.
certs ---+--- restapi-ca.pem
+--- restapi-cert.pem
+--- restapi-key.pem
Port | Description | Configurable |
---|---|---|
16006 | Default port for REST API Access to the OWSUB | yes |
The following environment variables should be set from the root directory of the service. They tell the OWSUB process where to find the configuration and the root directory.
export OWSUB_ROOT=`pwd`
export OWSUB_CONFIG=`pwd`
You can run the shell script set_env.sh
from the microservice root.
The configuration is kept in a file called owsub.properties
. To understand the content of this file,
please look here
Toe read more about Kafka, follow the document
We need more contributors. Should you wish to contribute, please follow the contributions document.
Please create a branch with the Jira addressing the issue you are fixing or the feature you are implementing. Create a pull-request from the branch into master.
Here is a list of additional OWSDK microservices
Name | Description | Link | OpenAPI |
---|---|---|---|
OWSEC | Security Service | here | here |
OWGW | Controller Service | here | here |
OWFMS | Firmware Management Service | here | here |
OWPROV | Provisioning Service | here | here |
OWANALYTICS | Analytics Service | here | here |
OWSUB | Subscriber Service | here | here |