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