diff options
Diffstat (limited to 'docs/release-notes.rst')
| -rw-r--r-- | docs/release-notes.rst | 39 |
1 files changed, 17 insertions, 22 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index ee323f9..d2c80f2 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -35,9 +35,9 @@ N/A HOLMES code has been formally scanned during build time using NexusCloud and all critical vulnerabilities have been addressed. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ **Upgrade Notes** @@ -78,9 +78,9 @@ N/A HOLMES code has been formally scanned during build time using NexusCloud and all critical vulnerabilities have been addressed. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ **Upgrade Notes** @@ -123,9 +123,9 @@ Version: 7.0.1 HOLMES code has been formally scanned during build time using NexusCloud and all critical vulnerabilities have been addressed. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ **Upgrade Notes** @@ -166,9 +166,9 @@ N/A HOLMES code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, some of the items that remain open have been assessed for risk and determined to be false positive and the rest are planned to be resolved in the next release. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ **Upgrade Notes** @@ -212,9 +212,9 @@ Added some tools to support the extended CCVPN use case: HOLMES code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, some of the items that remain open have been assessed for risk and determined to be false positive and the rest are planned to be resolved in the next release. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ **Upgrade Notes** @@ -259,14 +259,13 @@ Besides, Holmes has been enhanced to be CCVPN use case supportive. CCVPN related **Security Issues** -HOLMES 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 HOLMES open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=45298796>`_. +HOLMES 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 HOLMES open Critical security vulnerabilities and their risk assessment have been documented as part of the `project`_. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ - - - `Project Vulnerability Review Table for HOLMES <https://wiki.onap.org/pages/viewpage.action?pageId=45298796>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `Project Vulnerability Review Table for HOLMES`_ **Upgrade Notes** @@ -296,13 +295,11 @@ Version: 1.1.0 In the Beijing release, Holmes provides no more functionalites than the Amsterdam release. Its main features remains like follows: - `Rule Management <https://jira.onap.org/browse/HOLMES-4>`_ The feature provides interfaces for the users to create, query, update and delete rules. In this release, they are used along with the DCAE interfaces to accomplish the deployment (creation/update) of the control loop related rules. - - `Engine Management <https://jira.onap.org/browse/HOLMES-5>`_ The feature is not exposed to the end user directly. It's mainly used internally by Holmes as a container for the execution of rules. It provides interface for rule verification and deployment/un-deployment. Besides, Holmes has been enhanced to meet the platform maturity requirements. The enhancement mainly covers: - Scaling: Holmes supports horizontal scale-in/scale-out operations in case it is overloaded by too large amounts of data. - - Security: Holmes has updated all its APIs to support the HTTPS protocol. **Bug Fixes** @@ -319,11 +316,10 @@ N/A HOLMES 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 HOLMES open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28378012>`_. Quick Links: - - `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ - - `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ - - - `Project Vulnerability Review Table for HOLMES <https://wiki.onap.org/pages/viewpage.action?pageId=28378012>`_ +- `HOLMES project page <https://wiki.onap.org/display/DW/Holmes+Project>`_ +- `Passing Badge information for HOLMES <https://bestpractices.coreinfrastructure.org/en/projects/1602>`_ +- `Project Vulnerability Review Table for HOLMES <https://wiki.onap.org/pages/viewpage.action?pageId=28378012>`_ **Upgrade Notes** @@ -358,7 +354,6 @@ correlation analysis for the VoLTE scenario. To get us there, Holmes provides the following features: - `Rule Management <https://jira.onap.org/browse/HOLMES-4>`_ The feature provides interfaces for the users to create, query, update and delete rules. In this release, they are used along with the DCAE interfaces to accomplish the deployment (creation/update) of the control loop related rules. - - `Engine Management <https://jira.onap.org/browse/HOLMES-5>`_ The feature is not exposed to the end user directly. It's mainly used internally by Holmes as a container for the execution of rules. It provides interface for rule verification and deployment/un-deployment. **Bug Fixes** |