1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
..
This work is licensed under a Creative Commons Attribution 4.0
International License. http://creativecommons.org/licenses/by/4.0
.. _onap-release-notes:
'Montreal' Release Notes
========================
This page provides the release notes for the ONAP 'Montreal' release. This
includes details of software versions, known limitations, and outstanding
trouble reports.
Release notes are cumulative for the release, meaning this release note will
have an entry for each Major, Minor, and Maintenance release, if applicable.
Each component within the ONAP solution maintains their own component level
release notes and links to those release notes are provided below.
Details on the specific items delivered in each release by each component is
maintained in the component specific release notes.
'Montreal' Major Release 13.0.0
-------------------------------
+-----------------------------------+-----------------------------------------+
| **Project** | Open Network Automation Platform (ONAP) |
+-----------------------------------+-----------------------------------------+
| **Release name** | Montreal |
+-----------------------------------+-----------------------------------------+
| **Release version** | 13.0.0 |
+-----------------------------------+-----------------------------------------+
| **Release date** | 2023, December 14th |
+-----------------------------------+-----------------------------------------+
ONAP is evolving. We took efforts in streamlining processes and roles and
Montreal release is the first one with agreed simplified software development
life cycle governance.
OpenSSF Gold Standard
---------------------
We are proud to announce that first ONAP project achieved OpenSSF Gold
standard. It will give ONAP consumers great confidence in the quality,
security, and reliability of CPS.
Java 17
-------
First ONAP projects (CCSDK, CPS, UUI and Policy) completed their upgrades to
Java 17. Spring boot (uplift to v3.1.2) and OpenApi 3 upgrades were also
performed. These upgrades allow benefits of patched vulnerabilities and
software efficiencies in the latest versions.
CPS
---
ONAP CPS project continued efforts in improvement of read/write, query
operations, and huge reduction of memory consumption allowing for improved
query performance and improve stability.
Modeling
--------
Modeling project added provision of YANG modules automation tools, which helps
improve the YANG development efficiency and check the version update of the
YANG model.
OOM
---
OOM project team added support for Gateway-API in Ingress template (13.0.1) as
well as support for mariadb-operator (13.0.2). All ONAP MariaDB instances will
now be created with the latest version by default using the mariaDB-operator.
Added Galera clients (e.g. SO, SDNC) will use access to "primary" pod to avoid
"Deadlocks". Additionally added default role creation to ServiceAccount for
better access management.
SDC
---
SDC implemented-services update capability directly in yaml was added, more
comprehensive support for defining behavior of interface operations and
adaptability to define CSAR structure and content to suit the requirements of
individual models.
CCSDK
-----
CCSDK continued maintaining alignment with OpenDaylight release schedule by
upgrading to OpenDaylight Argon version, Service Release 2. This allows latest
ONAP user to make use of latest OpenDaylight software when they use latest
release of ONAP.
PortalNG
--------
We introduced new PortalNG as a maintained alternative to the unmaintained
Portal project. Allows ONAP user to make informed decisions on software use of
maintained and unmaintained projects.
Documentation Sources
---------------------
The formal ONAP 'Montreal' Release Documentation is available
in :ref:`ReadTheDocs<master_index>`.
The `Developer Wiki <http://wiki.onap.org>`_ remains a good source of
information on meeting plans and notes from committees, project teams and
community events.
OpenSSF Best Practice
---------------------
ONAP has adopted the `OpenSSF Best Practice Badge Program <https://bestpractices.coreinfrastructure.org/en>`_.
- `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge>`_
- `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
In the Montreal release,
- 100% projects passed 95% of the OpenSSF badge
- 94% passed the OpenSSF badge
- 24% projects passed the OpenSSF Silver badge
- 1 project passed the OpenSSF Gold badge
Project specific details are in the :ref:`release notes<component-release-notes>`
for each component.
.. index:: maturity
ONAP Maturity Testing Notes
---------------------------
For the 'Montreal' release, ONAP continues to improve in multiple areas of
Scalability, Security, Stability and Performance (S3P) metrics.
More details in :ref:`ONAP Integration Project<onap-integration:master_index>`
Known Issues and Limitations
----------------------------
Known Issues and limitations are documented in each
:ref:`project Release Notes <component-release-notes>`.
|
