From f47631075122c9f9dd2d4e461b1c529890267517 Mon Sep 17 00:00:00 2001 From: "Lovett, Trevor" Date: Wed, 1 Apr 2020 13:54:08 -0500 Subject: Clarify VES listener accepts all domains A concern was raised based on the prior wording that it left it open that there may be multiple listeners each handling different domains. The wording was updated to remove any ambiguity. Issue-ID: VNFRQTS-871 Signed-off-by: Lovett, Trevor Change-Id: Id06ac6181a9cda086e9ada8a1880703cdd282788 --- docs/Chapter8/ves7_1spec.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/Chapter8') diff --git a/docs/Chapter8/ves7_1spec.rst b/docs/Chapter8/ves7_1spec.rst index e63628a..2c8b933 100644 --- a/docs/Chapter8/ves7_1spec.rst +++ b/docs/Chapter8/ves7_1spec.rst @@ -362,9 +362,8 @@ an ONAP controller action, or provided manually. VES Events. The events shall only be sent to one VES Event Listener at a time. Please note: If a FQDN is used, the DNS query would return a single IP address. -* A single VES Event Listener may handle more than one type of VES event - (different domains); i.e. same VES Event Listener can receive and process - heartbeat, fault, measurement, syslog, etc. events. +* The active VES Event Listener (either the primary or secondary) will handle + all VES events regardless of domain. * **VES Credentials**: If the NF is using Basic Authentication, then the NF must support the provisioning of security and authentication parameters (HTTP username and password) in order to be able to authenticate with the -- cgit 1.2.3-korg