Add first version of VES agent and vesmgr

Vesmgr starts VES agent with a hard-coded measurement
configuration.

The following parameters can be defined as environment variables:
VESMGR_HB_INTERVAL
VESMGR_MEAS_INTERVAL
VESMGR_PRICOLLECTOR_ADDR
VESMGR_PRICOLLECTOR_PORT
VESMGR_PROMETHEUS_ADDR

Change-Id: I2faf07fca10864d331d81c2c15b94b9f263402b5
Signed-off-by: Katri Turunen <katri.turunen@nokia.com>
21 files changed
tree: fea85301c9982fe182135c833b5892c67f06e2a4
  1. cmd/
  2. ves-agent-chart/
  3. .gitreview
  4. container-tag.yaml
  5. Dockerfile
  6. go.mod
  7. go.sum
  8. LICENSES.txt
  9. README.md
README.md

RIC VESPA manager

The VESPA manager uses the VES Agent (https://github.com/nokia/ONAP-VESPA) to adapt near-RT RIC internal statistics' collection using Prometheus (xApps and platform containers) to ONAP's VES (VNF event streaming).

The VESPA manager starts and configures the VES Agent.

Environment variables

The VESPA manager container requires the following environment variables:

  • VESMGR_HB_INTERVAL - VES heartbeat interval. For example: 30s.
  • VESMGR_MEAS_INTERVAL - Measurement interval. For example: 60s.
  • VESMGR_PRICOLLECTOR_ADDR - Primary collector IP address. For example: 127.0.0.1.
  • VESMGR_PRICOLLECTOR_PORT - Primary collector port id as an integer. For example: 1234.
  • VESMGR_PROMETHEUS_ADDR - Prometheus address. For example: http://127.0.0.1:123

Unit Tests

In order to run the VESPA manager unit tests, give the following command:

go test ./... -v

License

See LICENSES.txt file.