X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Frelease%2Findex.rst;h=453d7c1aacadb37977a3ad2724c942cb05c3f65c;hb=6dee0826a47d1b1468207b28fc10ac7c7760b661;hp=bc4ee56745cfb7de6377737982c134d7c475c8c1;hpb=b921b99f27d55e46db2b72b5987ffacb1f781857;p=doc.git diff --git a/docs/release/index.rst b/docs/release/index.rst index bc4ee5674..453d7c1aa 100644 --- a/docs/release/index.rst +++ b/docs/release/index.rst @@ -1,196 +1,99 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. http://creativecommons.org/licenses/by/4.0 -.. index:: Release Notes -Releases -======== -This page is the ONAP Amsterdam Release Notes. The first release is -Amsterdam and subsequent major release will be named using city names. +.. _release-notes: -* Release Name: Amsterdam -* Release Version: 1.0.0 -* Release Date: November 16, 2017 +El Alto Release Notes +^^^^^^^^^^^^^^^^^^^^^ +This page provides the release notes for the ONAP El Alto release. This +includes details of software versions used, known limitations, and outstanding +trouble reports. -Amsterdam Release ------------------ +Release notes are cumulative for the release, meaning this release note for the +El Alto release will have an entry for each Major, Minor, and +Maintenance release, if applicable. -Summary -+++++++ -ONAP provides a comprehensive platform for real-time, policy-driven -orchestration and automation of physical and virtual network functions -that will enable software, network, IT and cloud providers and developers -to rapidly automate new services and support complete life cycle management. -By unifying member resources, ONAP will accelerate the development of a -vibrant ecosystem around a globally shared architecture and implementation -for network automation–with an open standards focus–faster than any one -product could on its own. +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. -Functionality -+++++++++++++ -**Portal** - a single, consistent user experience for both design timer -and run time environments, based on the user’s role. +El Alto Major Release 5.0.1 +=========================== -**Design Time Framework** - a comprehensive development environment with -tools, techniques, and repositories for defining/describing resources, -services, and products: - - - Service Design and Creation (SDC) provides tools, techniques, and - repositories to define/simulate/certify system assets as well as their - associated processes and policies. - - - A VNF Software Development Kit (VNFSDK) with tools for VNF supplier - packaging and validation. - - - Policy Creation (POLICY) deals with conditions, requirements, - constraints, attributes, or needs that must be provided, maintained, - and/or enforced. - - - Closed Loop Automation Management Platform (CLAMP) provides a method - for designing and managing control loops. - -**Runtime Framework** - The runtime execution framework executes the -rules and policies distributed by the design and creation environment -and Controllers that manage resources corresponding to their assigned -controlled domain: - - - Service Orchestrator (SO) executes the specified processes and automates - sequences of activities, tasks, rules and policies needed for on-demand - creation, modification or removal of network, application or infrastructure - services and resources. - - - Software Defined Network Controller (SDNC) network configuration of - cloud computing resources. - - - Application Controller (APPC) Application resources. - - - Virtual Function Controller (VF-C) provides an ETSI NFV compliant NFV-O - functions, and is responsible for life cycle management of virtual services - and the associated physical COTS server infrastructure. - - - Active and Available Inventory (A&AI) provides real-time views of a - system’s resources, services, products and their relationships with each - other. - -**Closed-Loop Automation** -- Design -> Create -> Collect -> Analyze > -Detect -> Publish -> Respond: - - - Data Collection, Analytics and Events (DCAE) collects performance, - usage, and configuration data and publishes information to policy, - orchestration, and the data lake. - - - “Holmes” provides alarm correlation and analysis for Telecom cloud - infrastructure and services, including hosts, vims, VNFs and NSs - - - Common Services - operational services for all ONAP components including - activity logging, reporting, common data layer, access control, resiliency, - and software lifecycle management. +* Release Name: El Alto +* Release Version: 5.0.1 +* Release Date: October 24 2019 Project Specific Release Notes -++++++++++++++++++++++++++++++ -ONAP releases are specified by a list of project artifact -versions in a :ref:`manifest`. +============================== +ONAP releases are specified by a list of project artifact versions in the +project repositories and docker container image versions listed in the OOM +Helm charts. Each project provides detailed :ref:`release notes` and prepends to these if/when any updated versions the project team believes are compatible with a major release are made available. - -Supported Platforms -+++++++++++++++++++ -ONAP Amsterdam Release has been tested on Ubuntu 16.04 and thus is -the only OS supported. - Documentation -+++++++++++++ -ONAP Amsterdam Release documentation is available :ref:`here `. -For Amsterdam this includes: +============= +ONAP El Alto Release provides a set selection of documents, +see :ref:`ONAP Home`. - * A high level :ref:`architecture view` of how components - relate to each other. +The `developer wiki `_ remains a good source of +information on meeting plans and notes from committees, project teams and +community events. - * A collection of documentation provided - by :ref:`each project `. +Security Notes +============== +Details about discovered and mitigated vulnerabilities are in +:ref:`ONAP Security ` - * Application Programming Interface - Reference :ref:`available here `. +.. toctree:: + :hidden: - * The `developer wiki `_ remains a good source of - information on meeting plans and notes from committees, project teams and - community events. + ../submodules/osa.git/docs/index.rst +ONAP has adopted the `CII Best Practice Badge Program `_. -Known Issues and Limitations -++++++++++++++++++++++++++++ -Known Issues and limitations are documented in each project Release Notes. +- `Badging Requirements `_ +- `Badging Status for all ONAP projects `_ -Refer to :ref:`release notes ` for each project. +Project specific details are in the :ref:`release notes` for +each project. +.. index:: maturity -.. index:: Licensing +ONAP Maturity Testing Notes +=========================== +For El Alto release, ONAP continues to improve in multiple areas of +Scalability, Security, Stability and Performance (S3P) metrics. -Licenses -++++++++ -ONAP Amsterdam Source Code is licensed under the `Apache Version 2 License `_. -ONAP Amsterdam Documentation is licensed under the `Creative Commons Attribution 4.0 International License `_. +The Integration team ran the 72 hours stability testing (100% passing rate) +and full resilience testing (99.4% passing rate) at ONAP OpenLabs. More details +in :ref:`ONAP Maturity Testing Notes ` + +Known Issues and Limitations +============================ +Known Issues and limitations are documented in each +:ref:`project Release Notes `. .. index:: Reporting Bugs How to Report a Bug -+++++++++++++++++++ +=================== There are 2 ways to report a bug in ONAP. - * In case you are familiar within ONAP, you can directly - report a bug by creating a Jira issue - at `ONAP Jira `_. - - * If you don't know you are facing a bug or have a question, email - the ONAP Discuss mailing list at onap-discuss@lists.onap.org . - -You may consider these `recommendations `_ to elaborate the issue you are facing and this `guideline `_ to register into the ONAP Discuss mailing list. - -.. index:: Download - -Download -++++++++ - -* ONAP Source Code is available through Gerrit at https://gerrit.onap.org or Git at https://git.onap.org/ . - -* ONAP is packaged within Docker and can be dowloaded from Docker Hub at https://hub.docker.com/r/onap . - + * In case you are familiar within ONAP, you can directly report a bug by + creating a Jira issue at `ONAP Jira `_. -.. index:: Installation + * If you don't know you are facing a bug or have a question, post your + question into the `Ask question `_. + You will need a Linux Foundation ID to login and post your question. + Get a Linux Foundation Identity using this `quick procedure `_. - -Install -+++++++ -There are 2 approaches to install ONAP. - -* From a complete demo solution perspective. This installs the whole ONAP, - refer to :ref:`Setting Up ONAP `. - -* From a developer perspective. ONAP is installed component per component. - Each - component :ref:`installation is listed in`. - The list of ports used by default within ONAP is documented - in `ONAP Service List `_. - -Usage -+++++ -This section is intended to provide users on the usage of ONAP components. - -Instructions on using the ONAP deployment including Robot, Portal, SDC and VID -in the context of running (Onboarding, service creation, service deployment, -VNF creation, VNF preload, VF Module creation and closed loop operations) -the vFirewall sanity use case is documented -in `Running the ONAP Demos `_. +To properly report a bug in Jira, you may want to consider these `recommendations `_ to elaborate the issue you are facing. .. Include files referenced by link in the toctree as hidden - -.. toctree:: - :hidden: - - release-manifest.rst - releaserepos.rst - repolist.rst