1 .. This work is licensed under a Creative Commons Attribution 4.0
2 International License. http://creativecommons.org/licenses/by/4.0
5 .. _dublinrelease-notes:
10 This page provides the release notes for the ONAP Dublin release. This includes
11 details of software versions used, known limitations, and outstanding trouble
14 Release notes are cumulative for the release, meaning this release note for the
15 Dublin release will have an entry for each Major, Minor, and Maintenance
16 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 releaese by each component is
21 maintained in the component specific release notes.
23 Dublin Major Release 4.0.0
24 ==========================
26 * Release Name: Dublin
27 * Release Version: 4.0.0
28 * Release Date: June 28th, 2019
30 The Dublin 4.0.0 is the fourth major ONAP release.
35 Dublin release introduces the following new features:
39 - Locale/Internationalization language support for Portal and UseCase UI
40 - A&AI UI integration in Portal
41 - Management GUI for Customer and Service Type in UseCase UI
42 - VID: Centralized Representation and Consistent ID of Cloud Regions
43 - VID: Change Management - Flexible Designer & Orchestrator
44 - CLI commands for end-to-end service creation
48 - Extended PNF requirements
49 - VTP (VNF Test Platform) is enabled with scenario and test case execution
51 - CSAR validation is enabled with PNF and VNF compliance check for SOL004,
53 - UI is available to execute VVP scripts.
54 - VVP is packaged as a Docker container including scripts covering all
55 mandatory, testable HOT requirements from VNFRQTS
56 - VNF SDK and VVP used for `OPNFV Verification Program (OVP) <https://vnf-verified.lfnetworking.org/#/>`_.
60 - PNF package onboarding aligned with ETSI SOL001
61 - Updating the VNFD type based on SOL001 v2.5.1
62 - Controller Design Studio integration
63 - VSP compliance check feature (SDC)
64 - K8S based Cloud Region Support (vFW, EdgeXFoundry)
65 - Model Driven Control Loop Design based on TOSCA
66 - New A&AI data types and schema service
70 - Hardening of HPA in SO and extension of HPA capabilities to existing
72 - Extended and enhance the SO generic building block to support pre and post
74 - SO to be made independent of Cloud technologies
75 - PNF Plug an play updates & improvements
77 - MultiCloud plugin for Kubernetes based cloud regions which supports
78 deployment via Helm Charts
79 - MultiCloud plugin for StarlingX
80 - MultiCloud plugin for ThinkCloud
81 - Additional LCM action for APPC : DistributeTrafficCheck
82 - Multiple standalone ansible servers support for APPC
83 - SDNC support for the PNF Use Case Network Assign for Plug and Play
85 - DCAE Collector : RESTConf collector
86 - DCAE Event Processors : VES Mapper, 3gpp PM-Mapper, BBS Event
88 - Analytics/RCA : SON-Handler, Heartbeat Micro Service
89 - Blueprint generator tool to simplify DCAE deployment artifact creation
90 - UI interface to manage Holmes rule management.
91 - Supports of Policy-model based Configuration Policy in CLAMP
92 - CLAMP supports new Policy Engine direct Rest API
93 - Support for Authenticated topics, Scaling support and multi-site
94 applications for DMAAP Message-Router
95 - Publication history for DMAAP Data-Router
96 - A new TOSCA parser common library
100 - ETSI: SO plugin to support SOL003 to connect to an external VNFM
101 - ETSI: SOL003 Alignment for GVNFM and Catalog in VFC
102 - TMF extension in External API with Service inventory notification and new
103 service specificationInputSchemas operation
107 - Default Storage Class Provisioner for improved Persistent Storage resiliency
108 - CNI reference integration for Multi-site support
109 - Platform Upgradability: Introduction of an Upgrade Framework supporting
110 automated rolling upgrades for applications and Release-to-release upgrade
111 for the following projects (A&AI, SDNC, SO)
115 - oParent Integration to fix vulnerabilities
116 - xNF communication security enhancements.
117 - Containers run as non-root
118 - More components integrated with AAF
119 - Some AAI services can be configured to leverage the ONAP Pluggable Security
120 Sidecar proof of concept
122 Footprint Optimization
123 ----------------------
124 - Optimized Docker images mainly using Alpine
125 - Shared MariaDB-Galera Cluster – used by : SO & SDNC
126 - Shared Cassandra Cluster – used by A&AI & SDC
127 - Optional deployment of independent clusters
131 Verified use cases are described in :ref:`verified Use Case <docs_usecases>`
133 - :ref:`vFirewall Use Case <docs_vfw>`
134 - :ref:`VF Module Scale Out Use Case (vLoadBalancer/vDNS) <docs_scaleout>`
135 - :ref:`vCPE Use Case <docs_vcpe>`
136 - :ref:`CCVPN (Cross Domain and Cross Layer VPN) Use Case <docs_ccvpn>`
137 - :ref:`vFirewall/vDNS with HPA Use Case <docs_vfw_hpa>`
138 - :ref:`vFirewall Traffic Distribution Use Case <docs_vfw_traffic>`
139 - :ref:`BBS (Broadband Service) Use Case <docs_bbs>`
140 - :ref:`vIPsec with HPA Use Case <docs_vipsec_hpa>`
141 - :ref:`vFirewall/edgex with K8S plugin <docs_vfw_edgex_multicloud_k8s>`
143 Project Specific Release Notes
144 ==============================
145 ONAP releases are specified by a list of project artifact versions in the
146 project repositories and docker container image versions listed in the OOM Helm
148 Each project provides detailed :ref:`release notes<doc-releaserepos>`
149 and prepends to these if/when any updated versions the project team believes
150 are compatible with a major release are made available.
154 ONAP Dublin Release provides multiple documents, see
155 :ref:`ONAP Home<master_index>`.
157 The `developer wiki <http://wiki.onap.org>`_ remains a good source of
158 information on meeting plans and notes from committees, project teams and
163 Details about discovered and mitigated vulnerabilities are in
164 :ref:`ONAP Security <onap-security>`
169 ../submodules/osa.git/docs/index.rst
171 ONAP has adopted the `CII Best Practice Badge Program <https://bestpractices.coreinfrastructure.org/en>`_.
173 - `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge#core-infrastructure-initiative-best-practices-badge>`_
174 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
176 Project specific details are in the
177 :ref:`release notes<doc-releaserepos>` for each project.
181 ONAP Maturity Testing Notes
182 ===========================
183 For Dublin release, ONAP continues to improve in multiple areas of Scalability,
184 Security, Stability and Performance (S3P) metrics.
186 The Integration team ran the 72 hours stability testing (100% passing rate) and
187 full resilience testing (99.4% passing rate) at ONAP OpenLabs. More details in
188 :ref:`ONAP Maturity Testing Notes <integration-s3p>`
190 Known Issues and Limitations
191 ============================
192 Known Issues and limitations are documented in each
193 :ref:`project Release Notes <doc-releaserepos>`.
195 .. index:: Reporting Bugs
199 There are 2 ways to report a bug in ONAP.
201 * In case you are familiar within ONAP, you can directly report a bug by
202 creating a Jira issue at `ONAP Jira <https://jira.onap.org>`_.
204 * If you don't know you are facing a bug or have a question, post your
205 question into the `Ask question <https://wiki.onap.org/display/DW/questions/all>`_.
206 You will need a Linux Foundation ID to login and post your question.
207 Get a Linux Foundation Identity using this `quick procedure <https://wiki.onap.org/display/DW/Joining+the+ONAP+Technical+Community#JoiningtheONAPTechnicalCommunity-WhereDoIStart?>`_.
209 To properly report a bug in Jira, you may want to consider these `recommendations <https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-RecommendationsforwrittingProperJIRAIssue>`_ to elaborate the issue you are facing.
212 .. Include files referenced by link in the toctree as hidden