diff options
| author |   Rich Bennett <rb2745@att.com> | 2018-08-03 14:20:10 -0400 |
|---|---|---|
| committer | Rich Bennett <rb2745@att.com> | 2018-08-03 14:26:18 -0400 |
| commit | d6a93c8116a8c2ce7cb96896d9745406bfa2a5ec (patch) | |
| tree | ae24cbc6bd33b83ac3b1073c6eef98413f50ef09 /docs/release-notes.rst | |
| parent | 1ec476db8795ff868065a2e9d8e080afb15ab59b (diff) | |
Eliminate appx 350 Sphinx Warnings
Rename NSLCM_API as json file and use swaggerv2doc to display json swagger definition
Remove extra characters at the end of line reported by doc8
Use code-blocks to better highlight json objects and eliminate warnings
Remove duplicate offeredapis content
Change-Id: Iec699b8f7d4f4be5b9783b3c40f24c8c4a279d7b
Issue-ID: VFC-919
Signed-off-by: Rich Bennett <rb2745@att.com>
Diffstat (limited to 'docs/release-notes.rst')
| -rw-r--r-- | docs/release-notes.rst | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 3109ba9b..0334a488 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -5,15 +5,11 @@ VF-C Release Notes ================== -.. note:: -.. * This Release Notes must be updated each time the team decides to Release new artifacts. -.. * The scope of this Release Notes is for this particular component. In other words, each ONAP component has its Release Notes. -.. * This Release Notes is cumulative, the most recently Released artifact is made visible in the top of this Release Notes. -.. * Except the date and the version number, all the other sections are optional but there must be at least one section describing the purpose of this new release. -.. * This note must be removed after content has been added. - -VF-C includes two main components, NFV-O and GVNFM, to implement life cycle management and FCAPS of VNF and NS. VF-C takes part in end to end service orchestration and close loop automation by working with SO, DCAE and Policy. -VF-C also provides standard southbound interface to VNFMs and can integrate with multi vendor VNFMs via drivers. +VF-C includes two main components, NFV-O and GVNFM, to implement life cycle +management and FCAPS of VNF and NS. VF-C takes part in end to end service +orchestration and close loop automation by working with SO, DCAE and Policy. +VF-C also provides standard southbound interface to VNFMs and can integrate +with multi vendor VNFMs via drivers. Version: 1.1.0 -------------- @@ -25,7 +21,7 @@ Version: 1.1.0 - NS/VNF manual scaling supporting for VoLTE use case - VNF Integration, integration with VNF via GVNFM - S3P improvement - + Released components: NFVO @@ -61,7 +57,11 @@ This is the initial release **Security Notes** -VFC code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The VFC open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25437810>`_. +VFC code has been formally scanned during build time using NexusIQ and all Critical +vulnerabilities have been addressed, items that remain open have been assessed +for risk and determined to be false positive. The VFC open Critical security +vulnerabilities and their risk assessment have been documented as part +of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25437810>`_. Quick Links: @@ -90,7 +90,7 @@ Version: 1.0.0 - VNF FCAPS, collecting FCAPS data from vendor EMS - VNFM Integration, integration with specific VNFMs of vendors to deploy commercial VNFs - VNF Integration, integration with VNF via GVNFM - + Released components: NFVO |