aboutsummaryrefslogtreecommitdiffstats
path: root/sources/hv-collector-xnf-simulator
AgeCommit message (Collapse)AuthorFilesLines
2019-03-20Remove environment variables and program argumentsJakub Dudycz2-10/+6
- Move all command line program arguments to json file. - Reorganize configuration classes and the way they are passed through application - Implement HV VES configuration stream - Create concrete configuration from partial one - Modify main HV-VES server starting pipeline Change-Id: I6cf874b6904ed768e4820b8132f5f760299c929e Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1340
2019-03-15Use Netty HttpServer in XnfApiServerIzabela Zawadzka3-46/+51
Change-Id: I86e06bd540c961098ee11af99735a5b35ce760fd Issue-ID: DCAEGEN2-1325 Signed-off-by: Izabela Zawadzka <izabela.zawadzka@nokia.com>
2019-03-14Extract HV-VES configuration moduleFilip Krzywka3-9/+9
To avoid cyclic dependency between "modules trio" configuration-core-ssl some classes from core.model were also extracted. Change-Id: Ie11029ae3500964f67f4d72279ddd68cdb2a1f0c Issue-ID: DCAEGEN2-1332 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-03-11Assure coverage is checked for all modulesPiotr Jaszczyk1-4/+0
Change-Id: Ia9bb6cef9154d64cfa45455e38c9fe7603a64c74 Issue-ID: DCAEGEN2-1328 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-03-07Remove Guava 19 dependency via protobuf-java-utilJakub Dudycz1-1/+6
Change-Id: Ic11cab5bce064817a954a462b3d2eea463198bd8 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1311
2019-03-05Extract module for ArgBasedConfigurationJakub Dudycz3-21/+15
Change-Id: Ib11700650583378eb347451950a24c5f238382e4 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1292
2019-03-05Fix ssl related bug in xnf simulatorJakub Dudycz9-60/+78
Fix bug when xnf simnulator was using same SecurityKeys object instance for every new VesClient, which resulted in fault while trying to connect to collector. With new implementation simulator reuses same HvVesProdcuer from SDK for every VesEvent request received and creates new Producer for every WireFrameEvent request. This allows to continue testing cases in which there is need to assert if connection was dropped from malicious client. Change-Id: I5f51a58de85cccf7de6ab2392f86259502be31dd Issue-ID: DCAEGEN2-1291 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-02-27Fix bug when xnf simulator was not sending eventsJakub Dudycz1-1/+1
Change-Id: I53cdf572d2df66d6021651424931a67108c482d3 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1291
2019-02-21Use sdk/hvves-producer in hvves/xnf-simulatorJakub Dudycz9-156/+279
Change-Id: I8f493b0edd2cbaef136a22d914ad24198bb63a7f Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1253
2019-02-19Use SDK/SSL in HV-VESPiotr Jaszczyk2-3/+18
Issue-ID: DCAEGEN2-1226 Change-Id: I7cfc09001f7315c1b6f4fcf150ad631630c810ef Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-02-18Merge "Generate VesEvents in hv-ves/message-generator"Piotr Jaszczyk3-42/+60
2019-02-15Generate VesEvents in hv-ves/message-generatorJakub Dudycz3-42/+60
- Split message generator on two specialized generators for VesEvent and WireFrame related message types - Refactor whole message-generator module Change-Id: I1266b549a9a4d27213d03e8921298deab2dacb59 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1162
2019-02-05Add sdk to dependencies of XNF simulatorkjaniak1-0/+8
Change-Id: Ib1e96c71dcddcd5228f8d186a66c924a25e32dec Issue-ID: DCAEGEN2-1163 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2019-01-25Mitigation of unexpected hv-ves shutdownkjaniak1-1/+1
Change-Id: I96183e2358ac10457568d223f37d69c61dfd252d Issue-ID: DCAEGEN2-1117 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2019-01-10Update development scriptsFilip Krzywka1-1/+1
This changeset is mostly follow-up after merges in DCAEGEN2-1063 - new options for hv-ves hostname and port in xnf simulations scripts - new option for disabling SSL in xnf simulations scripts - fail start-simulation script on not completing all simulations - use docker-healthchecks to determine xNF simulator readiness in development scripts - fix logging in xNF simulator on closing connection - minor corrections in logs and usage for development scripts Change-Id: Ic939a139fdaf86ad487e0b31d6abcfc6c8a28885 Issue-ID: DCAEGEN2-1063 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-01-08Merge "Align XNF simulator batch with Netty's queue size"Piotr Jaszczyk1-2/+2
2019-01-08Align XNF simulator batch with Netty's queue sizeJakub Dudycz1-2/+2
This change will lessen the probability of out of memory errors Change-Id: I96c735f4d7f5cedf3fddd66830e6557ea35ad1ea Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1062
2019-01-08Merge Healthcheck descriptionsFilip Krzywka9-86/+126
- start new API server for healthchecks in xNF simulator on port 6063 - changed DCAE App default port to 6064 - switched to InetSocketAddresses usage in components configurations Change-Id: I398f9ea6e887f78d88286ed717d310d3297b1571 Issue-ID: DCAEGEN2-1063 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-01-03Add script for sending messages from multiple xNFsFilip Krzywka4-14/+95
Change-Id: I9acd3278929c30a3036f97f403a31a8817723d27 Issue-ID: DCAEGEN2-1027 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-13Align logback configurationFilip Krzywka1-25/+84
- followed current logging guidelines in regard of format - in simulators currently very simple (minimalistic) pattern will be used as they do not contain any MDCs or Markers - in main logbacks included three patterns varying on verbosity and human-readability (for production full logging, ie. ONAP_LOG_PATTERN, should be used) - removed logback-test from domain module as it was not enabled anyway (no dependency on logback) and we should never have need for logging in this module - made logback-tests consistent (using simple pattern) except in component-tests, where it might be useful to have more verbose output (including MDCs etc.) Change-Id: Ifd851d12a77d5303b836a25c0e168e18a3a804e9 Issue-ID: DCAEGEN2-1026 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-10Add log diagnostic contextPiotr Jaszczyk4-14/+16
As it's not trivial to use MDC directly from logging framework in reactive application, we need to do some work manually. The approach proposed is an explicit MDC handling, which means that context is kept as an object created after establishing client connection. Next, new instance of HvVesCollector (and its dependencies) is created. Every object is propagated with ClientContext so it can use it when calling logger methods. In the future ClientContext might be used to support other use-cases, ie. per-topic access control. As a by-product I had to refactor our Logger wrapper, too. It already had too many functions and after adding MDC number would be doubled. Change-Id: I9c5d3f5e1d1be1db66d28d292eb0e1c38d8d0ffe Issue-ID: DCAEGEN2-671 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-05Enhance of logging in test partkjaniak1-1/+9
Change-Id: Ibdec0ac5cead7e46ada4c32983b9ccf962df703b Issue-ID: DCAEGEN2-1004 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2018-11-29Custom detekt rule for logger usage checkPiotr Jaszczyk12-0/+930
Check if logger invocations don't use unoptimal invocations, eg. concatenation `debug("a=" + a)` instead of lambda use `debug {"a=" + a}` Unfortunately to avoid defining dependencies in many places and having circural dependencies it was necessarry to reorganize the maven module structure. The goal was to have `sources` module with production code and `build` module with build-time tooling (detekt rules among them). Issue-ID: DCAEGEN2-1002 Change-Id: I36e677b98972aaae6905d722597cbce5e863d201 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>