2 This work is licensed under a Creative Commons Attribution 4.0
9 .. ===========================
10 .. * * * FRANKFURT * * *
11 .. ===========================
16 This document provides the release notes for the Frankfurt release.
26 +--------------------------------------+--------------------------------------+
29 +--------------------------------------+--------------------------------------+
30 | **Docker images** | optf-osdf 2.0.2 |
33 +--------------------------------------+--------------------------------------+
34 | **Release designation** | 6.0.0 frankfurt |
36 +--------------------------------------+--------------------------------------+
37 | **Release date** | 2020-05-07 (TBD) |
39 +--------------------------------------+--------------------------------------+
47 Known Limitations, Issues and Workarounds
48 =========================================
69 For more information on the ONAP Frankfurt release, please see:
72 #. `ONAP Documentation`_
73 #. `ONAP Release Downloads`_
77 .. _`ONAP Home Page`: https://www.onap.org
78 .. _`ONAP Wiki Page`: https://wiki.onap.org
79 .. _`ONAP Documentation`: https://docs.onap.org
80 .. _`ONAP Release Downloads`: https://git.onap.org
84 - `Passing Badge information for OOF`_
90 :Release Date: 2019-09-30 (El Alto Release)
92 The El Alto release is the fourth release for ONAP Optimization Framework (OOF).
102 While no new features were added in the release, the following Stories were delivered as enhancements.
104 * [OPTFRA-415] Automation on policy model uploading
105 * [OPTFRA-427] CMSO - Schedule a workflow in SO and track status to completion
107 * Platform Maturity Level 1
108 * ~65.1+ unit test coverage
113 The El Alto release for OOF fixed the following Bugs.
115 * [OPTFRA-579] Json error in homing solution
116 * [OPTFRA-521] oof-has-api exposes plain text HTTP endpoint using port 30275
117 * [OPTFRA-522] oof-osdf exposes plain text HTTP endpoint using port 30248
118 * [OPTFRA-577] Need for "ReadWriteMany" access on storage when deploying on Kubernetes?
119 * [OPTFRA-517] Clean up optf/cmso in integration/csit for Dublin
120 * [OPTFRA-486] Support "identifiers" field as a list of values
121 * [OPTFRA-403] OOF CMSO Service kubernetes resources allocation is not done
122 * [OPTFRA-526] OOF pods not running
123 * [OPTFRA-409] Template example : purpose to be explained
124 * [OPTFRA-593] OOF-CSMO healthcheck is failing in Master
129 * [OPTFRA-576] optf-has-master-csit-has is testing Dublin image
130 * [OPTFRA-596] CMSO - Sonar and CSIT jobs failing
131 * [OPTFRA-608] Error in Homing with multiple policies
135 *Fixed Security Issues*
137 * [OJSI-122] In default deployment OPTFRA (oof-osdf) exposes HTTP port 30248 outside of cluster.
138 * [OPTFRA-521] oof-has-api exposes plain text HTTP endpoint using port 30275
139 * [OPTFRA-522] oof-osdf exposes plain text HTTP endpoint using port 30248
140 * [OPTFRA-455] CMSO - Mitigate License Threat tomcat-embed-core
142 *Known Security Issues*
144 * [OPTFRA-481] Fix Vulnerability with spring-data-jpa package
145 * [OPTFRA-431] Fix Vulnerability with spring-security-web package
147 *Known Vulnerabilities in Used Modules*
152 **Deprecation Notes**
161 :Release Date: 2019-06-06 (Dublin Release)
165 The Dublin release is the third release for ONAP Optimization Framework (OOF).
167 A summary of features includes
169 * Support SON (PCI/ANR) optimization using OSDF
170 * Implement encryption for OSDF internal and external communication
172 * Platform Maturity Level 1
173 * ~65.1+ unit test coverage
175 The Dublin release for OOF delivered the following Epics.
177 * [OPTFRA-426] Track the changes to CMSO to support change management schedule optimization
178 * [OPTFRA-424] Extend OOF to support traffic distribution optimization
179 * [OPTFRA-422] Move OOF projects' CSIT to run on OOM
180 * [OPTFRA-276] Implementing a POC for 5G SON Optimization
181 * [OPTFRA-270] This epic captures stories related to maintaining current S3P levels of the project as new functional requirements are supported
186 * The full list of implemented user stories and epics is available on `DUBLIN RELEASE <https://jira.onap.org/projects/OPTFRA/versions/10463>`_
194 *Fixed Security Issues*
196 *Known Security Issues*
198 * [`OJSI-122 <https://jira.onap.org/browse/OJSI-122>`_] In default deployment OPTFRA (oof-osdf) exposes HTTP port 30248 outside of cluster.
200 *Known Vulnerabilities in Used Modules*
202 OPTFRA osdf code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.
203 The OPTF open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=64005463>`_.
206 - `OPTFRA project page <https://wiki.onap.org/display/DW/Optimization+Framework+Project>`_
207 - `Passing Badge information for OPTFRA <https://bestpractices.coreinfrastructure.org/en/projects/1720>`_
208 - `Project Vulnerability Review Table for OPTF <https://wiki.onap.org/pages/viewpage.action?pageId=64005463>`_
214 **Deprecation Notes**
225 :Release Date: 2019-01-31 (Casablanca Maintenance Release)
227 The following items were deployed with the Casablanca Maintenance Release:
236 * [OPTFRA-401] - Need flavor id while launching vm.
243 :Release Date: 2018-11-30 (Casablanca Release)
247 The Casablanca release is the second release for ONAP Optimization Framework (OOF).
249 A summary of features includes
251 * Homing enhancements for improving service deployability
252 * Discovering and reusing shared resources when processing multiple homing requests in parallel
253 * Considering Latency Reduction (in addition to geographical distances) for homing optimization
254 * Enhanced capacity checks during VNF homing
255 * Asynchronous communication between HAS components
256 * OOF Casablanca S3P Usability enhancement
257 * Adherence to ONAP API Common Versioning Strategy (CVS) Proposal
258 * Move all internal and external facing APIs to Swagger 2.0
259 * OOF Casablanca S3P Performance enhancements
260 * Creating a plan for performance improvements based on the baseline measured metrics
261 * OOF development platform hardening
263 * Fix Build Docker image script for supporting multiple versions
264 * Fix OOM, HEAT deployment scripts (versioning)
265 * CSIT functional tests for each repo
266 * CI Jobs for different streams (Beijing, master etc)
267 * Clean up nexus binaries and maven versioning
268 * Integrate OOF with Certificate and Secret Management Service (CSM)
269 * Support SON (PCI) optimization using OSDF
271 * Platform Maturity Level 1
272 * ~65.1+ unit test coverage
274 The Casablanca release for OOF delivered the following Epics.
276 * [OPTFRA-273] - Epic Name: OOF Casablanca S3P Manageability enhancement
277 * [OPTFRA-270] - Maintain current S3P levels
278 * [OPTFRA-271] - OOF Casablanca S3P Security enhancement
279 * [OPTFRA-267] - OOF - HPA Enhancements
280 * [OPTFRA-276] - Implementing a POC for 5G SON Optimization
285 * The full list of implemented user stories and epics is available on `CASABLANCA RELEASE <https://jira.onap.org/projects/OPTFRA/versions/10445>`_
289 * [OPTFRA-223] - On boarding and testing AAF certificates for OSDF.
290 * [OPTFRA-293] - Implement encryption for all OSDF internal and external communication
291 * [OPTFRA-329] - role based access control for OSDF-Policy interface
295 OPTFRA osdf code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.
296 The OPTF open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=43385924>`_.
299 - `OPTFRA project page <https://wiki.onap.org/display/DW/Optimization+Framework+Project>`_
300 - `Passing Badge information for OPTFRA <https://bestpractices.coreinfrastructure.org/en/projects/1720>`_
301 - `Project Vulnerability Review Table for OPTF <https://wiki.onap.org/pages/viewpage.action?pageId=43385924>`_
307 **Deprecation Notes**
318 :Release Date: 2018-06-07
323 The ONAP Optimization Framework (OOF) is new in Beijing. A summary of features includes:
325 * Baseline HAS functionality
326 * support for VCPE use case
327 * support for HPA (Hardware Platform Awareness)
328 * Integration with OOF OSDF, SO, Policy, AAI, and Multi-Cloud
329 * Platform Maturity Level 1
330 * ~50%+ unit test coverage
332 The Beijing release for OOF delivered the following Epics.
334 * [OPTFRA-2] - On-boarding and Stabilization of the OOF seed code
335 * [OPTFRA-6] - Integrate OOF with other ONAP components
336 * [OPTFRA-7] - Integration with R2 Use Cases [HPA, Change Management, Scaling]
337 * [OPTFRA-20] - OOF Adapters for Retrieving and Resolving Policies
338 * [OPTFRA-21] - OOF Packaging
339 * [OPTFRA-28] - OOF Adapters for Beijing Release (Policy, SDC, A&AI, Multi Cloud, etc.)
340 * [OPTFRA-29] - Policies and Specifications for Initial Applications [Change Management, HPA]
341 * [OPTFRA-32] - Platform Maturity Requirements for Beijing release
342 * [OPTFRA-33] - OOF Support for HPA
343 * [OPTFRA-105] - All Documentation Related User Stories and Tasks
348 None. Initial release R2 Beijing. No previous versions
356 OPTFRA code has been formally scanned during build time using NexusIQ and no Critical vulnerability was found.
359 - `OPTFRA project page <https://wiki.onap.org/display/DW/Optimization+Framework+Project>`_
360 - `Passing Badge information for OPTFRA <https://bestpractices.coreinfrastructure.org/en/projects/1720>`_
364 None. Initial release R2 Beijing. No previous versions
366 **Deprecation Notes**
368 None. Initial release R2 Beijing. No previous versions