diff options
author | 2018-07-27 19:16:26 +0000 | |
---|---|---|
committer | 2018-07-27 19:17:54 +0000 | |
commit | a4e0df11ff98a3a1b821f619e040506e3c3a33ed (patch) | |
tree | 7067f23488ac920f880c9d005321baab281ebd6a /docs/Chapter1 | |
parent | 5ecdcdb81911072feb73e092c0f4d11c8356f3ca (diff) |
VNFRQTS - Correcting initial release info
Removing references to initial release of ONAP from Open-O and OpenECOMP.
Change-Id: I749cfdf449d243720d47314525dd94a9fded16e1
Issue-ID: VNFRQTS-280
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Diffstat (limited to 'docs/Chapter1')
-rw-r--r-- | docs/Chapter1/index.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/Chapter1/index.rst b/docs/Chapter1/index.rst index a0b917e..f738542 100644 --- a/docs/Chapter1/index.rst +++ b/docs/Chapter1/index.rst @@ -9,10 +9,9 @@ Purpose practices which will increase innovation, minimize customization needed to onboard xNFs as well as reduce implementation complexity, time and cost for all impacted stakeholders. -- This initial release consolidates the requirements from Open-O and OpenECOMP - to provide common xNF requirements across the industry in order to drive - interoperability, simplify management, and reduce cost to build, deploy and - manage xNFs. +- The consolidated requirements provide common xNF requirements across + the industry in order to drive interoperability, simplify management, and + reduce cost to build, deploy and manage xNFs. - These requirements serve multiple purposes: - Primarily it provides a detailed list of requirements for xNF providers to meet to be compatible with ONAP; xNF providers will use |