Gitiles
Code Review Sign In
gerrit.nordix.org / onap / dcaegen2 / platform / ves-openapi-manager / c5c005a74157d8436bffd714c316ce257d2700ca
commitc5c005a74157d8436bffd714c316ce257d2700ca[log] [tgz]
authorMichal Banka <michal.banka@nokia.com>Fri Feb 12 09:36:30 2021 +0100
committerMichal Banka <michal.banka@nokia.com>Fri Feb 12 09:36:53 2021 +0100
treee4e57db9ba8d8d3bf4aca7f5d7acb7978ff17a15
parent7f7704977116ead5bc3ae8cba4afdf698d08bce7 [diff]
Remove Sonar code smells

- Reorganized test classes to match source code structure
- Removed Sonar code smells
- Removed unused test dependency from pom.xml

Change-Id: If8fda0caf01fe9d91aa7c784a3875a856d87f63d
Signed-off-by: Michal Banka <michal.banka@nokia.com>
Issue-ID: DCAEGEN2-2575
6 files changed
tree: e4e57db9ba8d8d3bf4aca7f5d7acb7978ff17a15
  1. src/
  2. .gitignore
  3. .gitreview
  4. Changelog.md
  5. docker-compose.yml
  6. Dockerfile
  7. environment.config
  8. INFO.yaml
  9. Makefile
  10. pom.xml
  11. README.md
  12. 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:

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.