diff options
Diffstat (limited to 'docs/sections/services/tcagen2-docker')
4 files changed, 7 insertions, 5 deletions
diff --git a/docs/sections/services/tcagen2-docker/configuration.rst b/docs/sections/services/tcagen2-docker/configuration.rst index b0bc4820..817bddd5 100644 --- a/docs/sections/services/tcagen2-docker/configuration.rst +++ b/docs/sections/services/tcagen2-docker/configuration.rst @@ -39,4 +39,4 @@ Following is default configuration set for TCA during deployment. tca.enable_ecomp_logging: true -Complete configuration and input defaults can be found on blueprint here - https://git.onap.org/dcaegen2/platform/blueprints/plain/blueprints/k8s-tcagen2.yaml
\ No newline at end of file +Complete configuration and input defaults can be found on blueprint here - https://git.onap.org/dcaegen2/platform/blueprints/plain/blueprints/k8s-tcagen2.yaml diff --git a/docs/sections/services/tcagen2-docker/functionality.rst b/docs/sections/services/tcagen2-docker/functionality.rst index 8b729b1d..985c844e 100644 --- a/docs/sections/services/tcagen2-docker/functionality.rst +++ b/docs/sections/services/tcagen2-docker/functionality.rst @@ -1,7 +1,11 @@ +.. This work is licensed under a + Creative Commons Attribution 4.0 International License. + http://creativecommons.org/licenses/by/4.0 + Functionality ============= -TCA-gen2 is driven by the VES collector events published into Message Router. This Message Router topic is the source for the CDAP application which will read each incoming message. If a message meets the VES (CEF, v28.4) as specified by the VES 5.4 standard, it will be parsed and if it contains a message which matches the policy configuration for a given metric (denoted primarily by the "eventName" and the "fieldPath"), the value of the metric will be compared to the "thresholdValue". If that comparison indicates that a Control Loop Event Message should be generated, the application will output the alarm to the Message Router topic in a format that matches the interface spec defined for Control-Loop by ONAP-Policy +TCA-gen2 is driven by the VES collector events published into Message Router. This Message Router topic is the source for the CDAP application which will read each incoming message. If a message meets the VES (CEF, v28.4) as specified by the VES 5.4 standard, it will be parsed and if it contains a message which matches the policy configuration for a given metric (denoted primarily by the "eventName" and the "fieldPath"), the value of the metric will be compared to the "thresholdValue". If that comparison indicates that a Control Loop Event Message should be generated, the application will output the alarm to the Message Router topic in a format that matches the interface spec defined for Control-Loop by ONAP-Policy Assumptions: diff --git a/docs/sections/services/tcagen2-docker/index.rst b/docs/sections/services/tcagen2-docker/index.rst index c5fc85da..c22cf23b 100644 --- a/docs/sections/services/tcagen2-docker/index.rst +++ b/docs/sections/services/tcagen2-docker/index.rst @@ -15,8 +15,7 @@ The TCA-gen2 is docker based mS intended to replace TCA/cdap version, which was .. toctree:: :maxdepth: 1 - ./installation ./installation-helm.rst ./configuration ./functionality - ./delivery
\ No newline at end of file + ./delivery diff --git a/docs/sections/services/tcagen2-docker/installation-helm.rst b/docs/sections/services/tcagen2-docker/installation-helm.rst index e4a25d9b..9bc12336 100644 --- a/docs/sections/services/tcagen2-docker/installation-helm.rst +++ b/docs/sections/services/tcagen2-docker/installation-helm.rst @@ -92,4 +92,3 @@ Application Configurations +-------------------------------+------------------------------------------------+ |tca.enable_ecomp_logging | Enable ecomp logging | +-------------------------------+------------------------------------------------+ - |