1 .. This work is licensed under a Creative Commons Attribution 4.0
2 International License. http://creativecommons.org/licenses/by/4.0
4 Casablanca Release Notes
5 ^^^^^^^^^^^^^^^^^^^^^^^^
6 This page is the ONAP Casablanca Release Notes. The first release was labelled
7 Amsterdam, second release Beijing and subsequent major release will be named
10 Release notes are cumulative for the release, meaning this release note for Casablanca will have an entry for each Major, Minor, and Maintenance release, if applicable. Information that is applicable regardless of release is included in the `Getting Started With ONAP`_ section of this document.
12 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 releaese by each component is maintained in the component specific release notes.
17 The following releases are available for Casablanca:
18 - `Casablanca Maintenance Release 3.0.1`_
19 - `Casablanca Major Release 3.0.0`_
21 Casablanca Maintenance Release 3.0.1
22 ====================================
24 * Release Name: Casablanca
25 * Release Version: 3.0.1
26 * Release Date: Jan 31, 2019
28 The Casablanca Maintenance Release delivered a number of fixes and updates across the following projects:
47 Details on the specific Jira tickets addressed by each project can be found in the component specific Release Notes. Link can be found below in section `Project Specific Release Notes`_.
49 Casablanca Major Release 3.0.0
50 ==============================
52 * Release Name: Casablanca
53 * Release Version: 3.0.0
54 * Release Date: Nov 30, 2018
56 The Casablanca 3.0.0 is the first of Casablanca.
60 Getting Started With ONAP
61 =========================
65 ONAP provides a comprehensive platform for real-time, policy-driven
66 service orchestration and automation including virtual network functions and
67 applications instantiation and configuration, but also physical network
68 functions configuration.
69 ONAP will enable software, network, IT and cloud providers and developers
70 to rapidly automate new services and support complete life cycle management.
71 By unifying member resources, ONAP will accelerate the development of a
72 vibrant ecosystem around a globally shared architecture and implementation
73 for network automation-with an open standards focus-faster than any one
74 product could on its own.
78 **Portal** - a single, consistent user experience for both design time
79 and run time environments, based on the user’s role.
81 **Design Time Framework** - a comprehensive development environment with
82 tools, techniques, and repositories for defining/describing resources,
85 - Service Design and Creation (SDC) provides tools, techniques, and
86 repositories to define/simulate/certify system assets as well as their
87 associated processes and policies.
89 - A VNF Software Development Kit (VNFSDK) and VNF Validation Program (VVP)
90 with tools for VNF supplier packaging and validation.
92 - Policy Creation (POLICY) deals with conditions, requirements,
93 constraints, attributes, or needs that must be provided, maintained,
96 - Closed Loop Automation Management Platform (CLAMP) provides a method
97 for designing and managing control loops.
99 - Optimization Framework (OOF) provides a policy-driven and model-driven
100 framework for creating optimization applications.
102 **Runtime Framework** - The runtime execution framework executes the
103 rules and policies distributed by the design and creation environment
104 and Controllers that manage resources corresponding to their assigned
107 - Service Orchestrator (SO) executes the specified BPMN processes and
108 automates sequences of activities, tasks, rules and policies needed for
109 on-demand creation, modification or removal of network, application or
110 infrastructure services and resources. SO is especially able to drive
111 any OpenStack-based cloud platform.
113 - Software Defined Network Controller (SDNC) executes network configuration
114 for cloud computing resources and network.
116 - Application Controller (APPC) executes Virtual Network Functions (VNF)
117 configurations and lifecycle management operations.
119 - Virtual Function Controller (VF-C) is responsible for lifecycle management
120 of virtual network functions and network services based on VNF using
123 - Active and Available Inventory (A&AI) provides real-time views of a
124 system’s resources, services, products and their relationships with each
127 **Closed-Loop Automation** -- Design -> Create -> Collect -> Analyze >
128 Detect -> Publish -> Respond:
130 - Data Collection, Analytics and Events (DCAE) collects events, performance,
131 usage and publishes information to policy that executes the rules to perform
134 - Holmes provides alarm correlation and analysis for Telecom cloud
135 infrastructure and services, including servers, cloud infrastructure,
136 VNFs and Network Services.
138 - Common Services - operational services for all ONAP components including
139 activity logging, reporting, common data layer, access control, resiliency,
140 multisite state coordination, credential/secret management and
141 software lifecycle management.
143 **Microservices Support**
145 - ONAP Operation Manager (OOM) use Kubernetes and Helm to manage ONAP components.
146 - Microservices Bus (MSB) provides service registration/discovery,
147 external API gateway, internal API gateway, client software development kit
148 (SDK), and Swagger SDK.
150 Project Specific Release Notes
151 ==============================
152 ONAP releases are specified by a list of project artifact versions in a :ref:`manifest<doc-release-manifest>`.
159 Each project provides detailed :ref:`release notes<doc-releaserepos>`
160 and prepends to these if/when any updated versions the project team believes
161 are compatible with a major release are made available.
167 ONAP is installed using :ref:`ONAP Operations Manager (OOM) over Kubernetes<installing-onap>`
171 ONAP Casablanca Release provides multiple documents including the following:
173 * A high level :ref:`architecture view<doc-architecture>` of how components
174 relate to each other.
176 * A collection of documentation provided
177 by :ref:`each project <doc_onap-developer_guide_projects>`.
179 * Application Programming Interface
180 Reference :ref:`available here <doc-apiref>`.
182 * The `developer wiki <http://wiki.onap.org>`_ remains a good source of
183 information on meeting plans and notes from committees, project teams and
190 ONAP has adopted the `CII Best Practice Badge Program <https://bestpractices.coreinfrastructure.org/en>`_.
191 The goal of the Casablanca release is for all ONAP projects to be close to achieving a CII Passing badge.
193 - `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge#core-infrastructure-initiative-best-practices-badge>`_
194 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
196 Project specific details are in the :ref:`release notes<doc-releaserepos>` for each project.
200 ONAP Maturity Testing Notes
201 ===========================
202 For the Casablanca release, ONAP continues to improve in multiple areas of Scalability, Security, Stability and Performance (S3P) metrics.
204 The Integration team ran the 72 hours stability testing (100% passing rate) and full resilience testing (96.9% passing rate) at ONAP OpenLabs. More details in :ref:`ONAP Maturity Testing Notes <integration-s3p>`
208 ONAP Source Code is licensed under the `Apache Version 2 License <http://www.apache.org/licenses/LICENSE-2.0>`_.
209 ONAP Documentation is licensed under the `Creative Commons Attribution 4.0
210 International License <http://creativecommons.org/licenses/by/4.0>`_.
212 Known Issues and Limitations
213 ============================
214 Known Issues and limitations are documented in each :ref:`project Release Notes <doc-releaserepos>`.
216 .. index:: Reporting Bugs
220 There are 2 ways to report a bug in ONAP.
222 * In case you are familiar within ONAP, you can directly report a bug by
223 creating a Jira issue at `ONAP Jira <https://jira.onap.org>`_.
225 * If you don't know you are facing a bug or have a question, post your
226 question into the `Ask question <https://wiki.onap.org/display/DW/questions/all>`_.
227 You will need a Linux Foundation ID to login and post your question.
228 Get a Linux Foundation Identity using this `quick procedure <https://wiki.onap.org/display/DW/Joining+the+ONAP+Technical+Community#JoiningtheONAPTechnicalCommunity-WhereDoIStart?>`_.
230 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.
233 .. Include files referenced by link in the toctree as hidden