1 .. This work is licensed under a Creative Commons Attribution 4.0
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) ONAP Project and its contributors
5 .. _release_notes_frankfurt:
9 *************************************
10 ONAP Operations Manager Release Notes
11 *************************************
13 Previous Release Notes
14 ======================
16 - :ref:`El Alto <release_notes_elalto>`
17 - :ref:`Dublin <release_notes_dublin>`
18 - :ref:`Casablanca <release_notes_casablanca>`
19 - :ref:`Beijing <release_notes_beijing>`
20 - :ref:`Amsterdam <release_notes_amsterdam>`
25 This document provides the release notes for the Frankfurt release.
30 The focus of this release is to strengthen the foundation of OOM installer.
35 +--------------------------------------+--------------------------------------+
38 +--------------------------------------+--------------------------------------+
39 | **Docker images** | N/A |
41 +--------------------------------------+--------------------------------------+
42 | **Release designation** | Frankfurt |
44 +--------------------------------------+--------------------------------------+
45 | **Release date** | 2020/06/15 |
47 +--------------------------------------+--------------------------------------+
52 * Ingress deployment is getting more and more usable
53 * Use of dynamic Persistent Volume is available
57 A list of issues resolved in this release can be found here:
58 https://jira.onap.org/projects/OOM/versions/10826
62 - `OOM-1237 <https://jira.onap.org/browse/OOM-1237>`_ Source Helm Charts from
63 ONAP Repo. Having helm charts repo is not possible for Frankfurt release.
64 - `OOM-1720 <https://jira.onap.org/browse/OOM-1237>`_ galera container is
65 outdated. containers used for mariadb are outdated and not supported anymore.
66 - `OOM-1817 <https://jira.onap.org/browse/OOM-1817>`_ Use of global.repository
67 inconsistent across Helm Charts. it's then may be hard to retrieve some
68 containers when deploying in constrained environment.
69 - `OOM-2075 <https://jira.onap.org/browse/OOM-2075>`_ Invalid MTU for Canal CNI
71 - `OOM-2227 <https://jira.onap.org/browse/OOM-2227>`_ Cassandra Backup Mechanism
72 works only on "static PV" mode.
73 - `OOM-2230 <https://jira.onap.org/browse/OOM-2230>`_ Missing requests/limits
74 for some PODS. This can lead to "memory bombing" so cautious monitoring of
75 Kubernetes resources usage must be set up.
76 - `OOM-2279 <https://jira.onap.org/browse/OOM-2279>`_ OOM El Alto and master
77 clamp mariadb resources doesn't match chart.
78 - `OOM-2285 <https://jira.onap.org/browse/OOM-2285>`_ deploy.sh does not work
79 for mariadb-galera. deploy script doesn't behave well with "-" in the
81 - `OOM-2369 <https://jira.onap.org/browse/OOM-2369>`_ DMAAP Helm install takes
82 too long and often fails.
83 - `OOM-2418 <https://jira.onap.org/browse/OOM-2418>`_ Readiness-check 2.0.2 not
84 working properly for stateful set.
85 - `OOM-2421 <https://jira.onap.org/browse/OOM-2421>`_ OOM NBI chart deployment
86 error. In some case, NBI deployment fails.
87 - `OOM-2422 <https://jira.onap.org/browse/OOM-2422>`_ Portal App is unreachable
88 when deploying without HTTPs
98 Documentation Deliverables
99 ~~~~~~~~~~~~~~~~~~~~~~~~~~
101 Known Limitations, Issues and Workarounds
102 =========================================
104 Known Vulnerabilities
105 ---------------------
110 - `OOM-1237 <https://jira.onap.org/browse/OOM-1237>`_ Workaround is to generate
111 them as explained in documentation.
112 - `OOM-1817 <https://jira.onap.org/browse/OOM-1817>`_ Workaround is to use
113 offline installer if needed.
114 - `OOM-2227 <https://jira.onap.org/browse/OOM-2227>`_ Workaround is to stick to
115 "static PV" (so, not using storage class) if backup is needed.
116 - `OOM-2285 <https://jira.onap.org/browse/OOM-2285>`_ Workaround is to use
117 directly helm upgrade if needed.
118 - `OOM-2369 <https://jira.onap.org/browse/OOM-2369>`_ Workaround is to play
119 postinstall jobs by hand.
120 - `OOM-2418 <https://jira.onap.org/browse/OOM-2418>`_ Workaround is to use
121 version 2.2.2 in global part of override file if the new check is needed.
122 - `OOM-2421 <https://jira.onap.org/browse/OOM-2421>`_ Workaround is to
123 undeploy/redeploy NBI.
124 - `OOM-2422 <https://jira.onap.org/browse/OOM-2422>`_ Workaround is to create
125 first portal app service with service type Cluster IP then changing it to
126 NodePort or LoadBalancer so all the port are available.
131 **Fixed Security Issues**
133 - In default deployment OOM (consul-server-ui) exposes HTTP port 30270 outside
134 of cluster. [`OJSI-134 <https://jira.onap.org/browse/OJSI-134>`_]
135 - CVE-2019-12127 - OOM exposes unprotected API/UI on port 30270
136 [`OJSI-202 <https://jira.onap.org/browse/OJSI-202>`_]
141 For more information on the ONAP Frankfurt release, please see:
144 #. `ONAP Documentation`_
145 #. `ONAP Release Downloads`_
149 .. _`ONAP Home Page`: https://www.onap.org
150 .. _`ONAP Wiki Page`: https://wiki.onap.org
151 .. _`ONAP Documentation`: https://docs.onap.org
152 .. _`ONAP Release Downloads`: https://git.onap.org