Gitiles
Code Review Sign In
gerrit.nordix.org / onap / dcaegen2 / platform / ves-openapi-manager / fe74c457e981e47f7a88d8039306b55baa1c1522
commitfe74c457e981e47f7a88d8039306b55baa1c1522[log] [tgz]
authorMichal Banka <michal.banka@nokia.com>Tue Feb 23 11:27:20 2021 +0100
committerMichal Banka <michal.banka@nokia.com>Tue Feb 23 11:41:37 2021 +0100
treede85b851f424ad8ecc7e6f108d7acaf7b97e99d8
parent7887d56ca97c0b2ffc534af1a1cbb5c1f28e46a5 [diff]
Add healthcheck controller

Healthcheck is required by Helm chart liveness.
Changes:
- Healthcheck added
- Minor updates in README
- .gitreview formatting update
- version update to 1.0.1

Change-Id: I4781ce0e896061ca8be52739f80ca02c294b8913
Signed-off-by: Michal Banka <michal.banka@nokia.com>
Issue-ID: DCAEGEN2-2574
6 files changed
tree: de85b851f424ad8ecc7e6f108d7acaf7b97e99d8
  1. releases/
  2. src/
  3. .gitignore
  4. .gitreview
  5. Changelog.md
  6. docker-compose.yml
  7. Dockerfile
  8. environment.config
  9. INFO.yaml
  10. Makefile
  11. pom.xml
  12. README.md
  13. version.properties
README.md

VES OpenApi Manager

Description

This application should partially validate incoming service distributions in SDC. It validates each artifact of type VES_EVENT. Its purpose is to check whether schemaReferences of stndDefined events included in VES_EVENT artifacts are matching the schemas which VES Collector contains.

Instructions

How to prepare environment for local ves-openapi-manager with lab connection

  1. Connect to lab and expose ports of message-router service by setting spec.type to NodePort.

  2. Add to /etc/hosts new entry:

<lab_worker_node_ip> sdc-be.onap

  1. Get exposed port of 3904 internal port of message-router.

    Set up connection configuration in environment.config file.

    • MESSAGE_ROUTER_PORT - exposed port of message-router.
    • RKE_IP - IP of lab RKE node.
    • WORKER_IP - IP of lab worker node.
    • SSH_LAB_KEY_PATH - path to lab SSH key.

  2. Local port forwarding is required to set up proper connection from local environment to message-router on the lab.

    Run this to enable port-forwarding (CTRL+C to end):

    make port-forwarding

How to locally start ves-openapi-manager

Currently, there are two common ways to run application, both described below.

Start in IntelliJ

Right click on Main class, then Run or Debug button.

Start as Docker container

Run (from other terminal than used for port-forwarding):

make all

Lab connection verification

Correctly connected to lab application should print logs:

distribution client initialized successfuly

and

distribution client started successfuly

How to use ves-openapi-manager

After preparing environment, starting ves-openapi-manager and successful connection to lab, application will listen for service distributions taking place in SDC.

  1. In SDC UI, create Service with Resource (e.g. PNF) containing VES_EVENT artifact.
  2. (Re)distribute created Service.

When distribution takes place, ves-openapi-manager downloads each VES_EVENT artifact to validate its stndDefined events.

Results of validation are visible in two places:

  • In SDC UI in Service -> Distributions view under specific distribution as component ves-openapi-manager. It might take few minutes to show results after service distribution.
  • In logs of ves-openapi-manager, right after validation takes place.

Docker image

Building

There are at least two ways to build docker image.

Using makefile:

make build docker

Direct creation with mvn:

mvn clean package docker:build

Image will be named: onap/org.onap.dcaegen2.platform.ves-openapi-manager