diff options
| author |   yangyan <yangyanyj@chinamobile.com> | 2018-06-07 14:05:18 +0800 |
|---|---|---|
| committer |   Gildas Lanilis <gildas.lanilis@huawei.com> | 2018-06-11 15:15:17 +0000 |
| commit | 01237eb956ad93de7f39075da829ac8aee388442 (patch) | |
| tree | c10f73bf20dc15dc9038555d834f5aa1792921af | |
| parent | fcbd6fe69e8da067b7eb11202cb5797a2659245c (diff) | |
Fix format issue on RNbeijing
Issue-ID: DOC-271
Change-Id: Ic98be75196f8f07d13a2bdab9c7ee1a14e032291
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
(cherry picked from commit fa5ce71293ba07ee8f0978fa81ab97c6bf26dfc2)
| -rw-r--r-- | docs/release-notes.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index c2202018..3109ba9b 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -57,13 +57,14 @@ This is the initial release - VFC-896 vim-id in AAI is handled as a mandatory parameter - VFC-890 The hard coded SDC user and password in catalog & LCM is not present in SDC - - VFC-891 The AAI credentials is hard coded in LCM + - VFC-891 The AAI credentials is hard coded in LCM **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>`_. Quick Links: + - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_ - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_ - `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=25437810>`_ |