From: hp1256 Date: Wed, 11 Oct 2017 18:32:11 +0000 (-0700) Subject: VNFRQTS -Requirements Remove trademark from Ch7 X-Git-Tag: 2.0.0-ONAP~105^2 X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=99e1560a199c00599d60b7a37b3620d949acb705;p=vnfrqts%2Frequirements.git VNFRQTS -Requirements Remove trademark from Ch7 VNFRQTS -Requirements removed att trademark from chapter 7 Change-Id: I66abb3bb6f13e10751a327eb0fe44420f81e8607 Issue-ID:VNFRQTS-56 Signed-off-by: hp1256 --- diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst index f6061b0..1a09ad2 100644 --- a/docs/Chapter7.rst +++ b/docs/Chapter7.rst @@ -145,6 +145,8 @@ services. The Adapters employ a model driven approach along with standardized APIs provided by the VNF developers to configure resources and manage their runtime lifecycle. +Additional details can be found in the `ONAP Application Controller (APPC) API Guide `_. + NETCONF Standards and Capabilities ---------------------------------- @@ -622,6 +624,8 @@ points in the network. The VNF vendors must be able to provide the aforementioned set of required data directly to the ONAP collection layer using standardized interfaces. +Additional details can be found in the `Data Collection, Analytics, and Events (DCAE) `_ project documentation. + Transports and Protocols Supporting Resource Interfaces ------------------------------------------------------- @@ -883,11 +887,6 @@ For additional information on the event record formats of the data structures mentioned above, please refer to `VES Event Listener `__. -.. [1] - ECOMP (Enhanced Control Orchestration, Management & Policy) - Architecture White Paper - (http://about.att.com/content/dam/snrdocs/ecomp.pdf) - .. [2] https://github.com/mbj4668/pyang