tree: 7137f2619dca92bbc044208df9373e40a269b8c9 [path history] [tgz]
  1. Chart.yaml
  3. files/
  4. templates/
  5. tests/
  6. values.yaml

Aether ROC Umbrella chart

First add repos to your Helm client


Provides a Helm chart for deploying

  • aether-roc-gui (2 versions)
  • aether-roc-api
  • onos-topo
  • onos-config
  • sdcore-adapter (2 versions)
  • sdcore-test-dummy
  • grafana
  • prometheus

to Kubernetes.

See the documentation for more info.

Config models

The Aether ROC Umbrella chart controls the Config Model Plugins that are enabled in onos-config Currently 2 versions of the Aether model are loaded:

  • aether-2.0.x
  • aether-2.1.x

Configuring a default target

For the 2.1.x models, you may need to set a default target when configuring sdcore-adapter, as onos-config does not supply the target at this time. Override the setting "defaultTarget". Likely candidates include defaultent which should be available in all deployments, or acme or starbucks which are present in the 2.1 aether-roc-api mega-patch. For example,

  defaultTarget: defaultent

This setting is intentionally left unconfigured by default, to encourage the developer to choose a default target that matches their environment and workflow.

Deploy with Authentication enabled

  1. install the helm Repo
  2. deploy the dex-ldap-umbrella

Then run:

helm -n micro-onos install aether-roc-umbrella aether/aether-roc-umbrella \
--set onos-config.openidc.issuer=http://dex-ldap-umbrella:5556 \
--set aether-roc-gui.openidc.issuer=http://dex-ldap-umbrella:5556

Sample Data - MEGA Patch

Some sample data that works with the aether-3.0.0 models is available at

This creates 2 sample enterprises acme and starbucks with corresponding sites, applications, device-groups and vcs etc.


The chart includes the sdcore-test-dummy container for testing the sdcore-adapter

this may be disabled in the chart with --set import.sdcore-test-dummy.enabled=false

This runs in the cluster at http://aether-roc-umbrella-sdcore-test-dummy (port 80)

This is a simple nginx server that has been configured to accept POST requests and log their contents. Use kubectl -n <namespace> logs --follow <pod identifier> to see the POST request contents.

In a configuration of a connectivity-service for the 4G/5G model (aether-3.0.0) the following values should be set:

In a configuration of a connectivity-service for the 4G only model (aether-2.1.0) the following values should be set: