GovOps Installation

Installing GovOps

There is an active GovOps instance running at TODO. This can be used to check out how the framework works and to quickly test its capabilities. In case a support for more complex usecases is needed, you can easily customize, build and deploy a local instance of GovOps(see the next section).

Building and deploying GovOps locally

Building GovOps

GovOps is a Maven project so building it is easy. Just go to the GovOps-Controller directory and run

mvn clean install -DskipTests=true

Please note that it is advised to skip test in case of local build, since they require a WebDAV repository and PostgreSQL test database. If you really want to run tests, install these dependencies and provide test data.

Deploying GovOps

GovOps is a web-based, highly modular framework and deploying it requires deploying the following services:

• APIManager
• SDGBuilder (capabilities builder)
• SDGManager (device manager)
• SDGBalancer (load balancer)

It is advised to used a Tomcat 7 for the deployment.

GovOps is based on Sring Boot and enables easy custom configurations via .properties files (defined in each of the above services). Default configuration assumes all the services are deployed on a single machine (127.0.0.1). In addition by default it is configured to run with hsql inmemory database. However, if the services are not deployed locally or if permanent/different storage is needed, they can easily be configured via .properties files exposed by each of the above services.

After successful deployment, by default GovOps can be accessed at:

http://127.0.0.1:8080/APIManager/

For more details about the exposed APIs, please see the API page.