Upcoming maintenance: Thursday 21 August @ 12:00-14:00 CEST.

Skip to content
Snippets Groups Projects
  • Lluis Gifre Renom's avatar
    d4955a06
    MicroK8s deployment scripts: · d4955a06
    Lluis Gifre Renom authored
    - moved old deployment scripts to scripts/old
    - added NGINX-based ingress controller to expose http-based endpoints from a single connection point
    - adapted webui K8s manifest to be used with the ingress controller
    - improved install_requirements.sh (renamed from install_development_dependencies.sh) to prevent collision of package versions
    - adapted script to show deployment
    - created functional example settings script my_deploy.sh
    - created improved deploy.sh script
    - added first version of the deployment tutorial. Run Experiments and Development are work in progress.
    d4955a06
    History
    MicroK8s deployment scripts:
    Lluis Gifre Renom authored
    - moved old deployment scripts to scripts/old
    - added NGINX-based ingress controller to expose http-based endpoints from a single connection point
    - adapted webui K8s manifest to be used with the ingress controller
    - improved install_requirements.sh (renamed from install_development_dependencies.sh) to prevent collision of package versions
    - adapted script to show deployment
    - created functional example settings script my_deploy.sh
    - created improved deploy.sh script
    - added first version of the deployment tutorial. Run Experiments and Development are work in progress.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.

1.4. Access TeraFlowSDN WebUI and Grafana Dashboards

This section describes how to get access to the TeraFlowSDN controller WebUI and the monitoring Grafana dashboards.

1.4.1. Access the TeraFlowSDN WebUI

If you followed the installation steps based on MicroK8s, you got an ingress controller installed that exposes on TCP port 80. In the creation of the VM, a forward from local TCP port 8080 to VM's TCP port 80 is configured, so the WebUIs and REST APIs of TeraFlowSDN should be exposed on endpoint 127.0.0.1:8080. Besides, the ingress controller defines the following reverse proxy paths:

  • http://127.0.0.1:8080/webui: points to the WebUI of TeraFlowSDN.
  • http://127.0.0.1:8080/grafana: points to the Grafana dashboards. This endpoint brings access to the monitoring dashboards of TeraFlowSDN. The credentials for the adminuser are those defined in the my_deploy.sh script, in the TFS_GRAFANA_PASSWORD variable.
  • http://127.0.0.1:8080/context: points to the REST API exposed by the TeraFlowSDN Context component. This endpoint is mainly used for debugging purposes. Note that this endpoint is designed to be accessed from the WebUI.
  • http://127.0.0.1:8080/restconf: points to the Compute component NBI based on RestCONF. This endpoint enables connecting external software, such as ETSI OpenSourceMANO NFV Orchestrator, to TeraFlowSDN.