| commit | 4229afc64d82cbd1ea1e43c92fcd6c9bed9e5137 | [log] [tgz] |
|---|---|---|
| author | PatrikBuhr <patrik.buhr@est.tech> | Wed May 29 09:39:53 2019 +0000 |
| committer | PatrikBuhr <patrik.buhr@est.tech> | Wed May 29 09:39:53 2019 +0000 |
| tree | 6c5c6efecb383a439f27cd163b20edfa364b6ce2 | |
| parent | 2187fc6e6b4b4783389289fb87bd6a3676ad2c72 [diff] |
Generalizing Data File Collection to handle any type of file Extension of the DFC to be able to handle any file types types, which are published on different DR feeds. This association between file type and DR feed is defined by configuration. The file type is defined by the changeIdentifier in the fileReady VES message reported from the PNF. The creation of DR feeds and configuration will be done by the DMAAP plugin, but that is not tested yet. Change-Id: I13b36acd926a6941ee733e6b37922049fb54a5d9 Issue-ID: DCAEGEN2-1532 Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
Datafile Collector is responsible for collecting PM counter files from PNF (Physical Network Function) and then publish these files to Dmaap DataRouter.
DFC is delivered as one Docker container which hosts application server and can be started by docker-compose.
Whole project (top level of DFC directory) and each module (sub module directory) can be compiled using mvn clean install command.
Running with dev-mode of DFC
Heartbeat: http://<container_address>:8100/heartbeat or https://<container_address>:8443/heartbeat
Start DFC: http://<container_address>:8100/start or https://<container_address>:8433/start
Stop DFC: http://<container_address>:8100/stopDatafile or https://<container_address>:8433/stopDatafile
org.onap.dcaegen2.collectors
dcae-services
Copyright (C) 2018-2019 NOKIA Intellectual Property, 2018-2019 Nordix Foundation. All rights reserved. License