diff options
author | 2020-11-03 13:36:55 -0500 | |
---|---|---|
committer | 2020-11-03 13:37:03 -0500 | |
commit | c4d0593b5ec79333ebbbaa57f47ed08e929c56aa (patch) | |
tree | 17aeef922195df0bb974f66e4d3b31c235d5f2ce /docs/sections/architecture.rst | |
parent | 647eadec530a0353a08469df9220900843554bfe (diff) |
DCAE doc updates to remove pnda
Change-Id: I9e1ebd6f564103919fa9c5b9242711e751616cd8
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Issue-ID: DCAEGEN2-2505
Diffstat (limited to 'docs/sections/architecture.rst')
-rw-r--r-- | docs/sections/architecture.rst | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/sections/architecture.rst b/docs/sections/architecture.rst index 3bc3ceb6..8231f44d 100644 --- a/docs/sections/architecture.rst +++ b/docs/sections/architecture.rst @@ -82,7 +82,6 @@ ONAP supports deployment through OOM Helm Chart currently (Heat deployment suppo To keep the ONAP footprint minimal, only minimal set of MS (required for ONAP Integration usecases) are deployed via bootstrap pod. Rest of service blueprints are available for operator to deploy on-demand as required. -The PNDA platform service is an optional component that can be installed when using the OOM Helm Chart installation method on Openstack based Kubernetes infrastructure. More details of the DCAE deployment can be found under Installation section. @@ -94,7 +93,7 @@ For ONAP DCAE participates in the following use cases. - vDNS: VES collector, TCA analytics -- vFW: VES collector, TCA analytics, PNDA based analytics +- vFW: VES collector, TCA analytics - vCPE: VES collector, TCA analytics |