Fix HV-VES readiness probe 03/75803/3
authorFilip Krzywka <filip.krzywka@nokia.com>
Tue, 15 Jan 2019 08:13:33 +0000 (09:13 +0100)
committerFilip Krzywka <filip.krzywka@nokia.com>
Tue, 15 Jan 2019 12:14:36 +0000 (13:14 +0100)
commit034a2e03801977dad689082e388abd010937d39c
tree8baf80a32f2fd744654ec4e4d469697a9ceb9317
parentd2a565cf3f17ecc3d065f8b406b7320ae9305f93
Fix HV-VES readiness probe

In related commits from DCAEGEN2-1025 location of healthcheck script
was changed.

- changed log_directory property in blueprint - current
location of log directory is  `/var/log/ONAP/dcae-hv-ves-collector`
according to logging specification v1.2 [Casablanca]
- also to be more compatible with logging spec: added default logback
configuration filepath to allow mounting different configuration.
HV-VES will fallback to jar-defined configuration in case of not finding
it on filesystem
- used hv_ves_name property for dns_name as hardcoded value was same

Change-Id: I8877ca774109ef293f3daaf057d5bcf666fa5305
Issue-ID: DCAEGEN2-1025
Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
blueprints/k8s-hv-ves.yaml-template