X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Frelease%2Findex.rst;h=ff81038fb45d1cf84229c92e0fb45b0c67fc6303;hb=c10c7c97bb0aefd6f1b46645ac029d6dab87235b;hp=aad7d757eddb8352d7c4f7206168a9058382e980;hpb=1bf0d36bcb82b159fdc8087c51d3454832051f46;p=doc.git diff --git a/docs/release/index.rst b/docs/release/index.rst index aad7d757e..ff81038fb 100644 --- a/docs/release/index.rst +++ b/docs/release/index.rst @@ -1,32 +1,193 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. This work is licensed under a Creative Commons Attribution 4.0 + International License. http://creativecommons.org/licenses/by/4.0 +.. index:: Release Notes Releases ======== -ONAP is developed and released around 6 month cycles. After an initial major release, additional -stable point releases may be created. +This page is the ONAP Amsterdam Release Notes. The first release is +Amsterdam and subsequent major release will be named using city names. -Named Releases --------------- +* Release Name: Amsterdam +* Release Version: 1.0.0 +* Release Date: November 16, 2017 -.. csv-table:: - :align: left - :header-rows: 0 - :header: "Release", "Status", "Initial Release Date", "Next Phase", "EOL Date" - :widths: 15, 10, 10, 15, 10 - "Amsterdam", "Under Development", "TBD", "", "" - "OpenECOMP R1.0.0 Seed Code", "EOL", "2017-04-XX", "", "" +Getting Started With Amsterdam +------------------------------ -Amsterdam Projects ------------------- -The following projects repositories have been approved by the TSC to be part of -the Amsterdam Release and provide detailed release notes at the links below. +Summary ++++++++ +ONAP provides a comprehensive platform for real-time, policy-driven +service orchestration and automation including virtual network functions and applications +instantiation and configuration, but also physical network functions configuration. +ONAP 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. -.. include:: releaserepos.rst +Functionality ++++++++++++++ +**Portal** - a single, consistent user experience for both design timer +and run time environments, based on the user’s role. +**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. -The complete list of projects providing documentation for current and future releases -has been moved to the onap-developer guide :ref:`doc_onap-developer_guide_projects`. + - 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 BPMN 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. SO is especially able to drive any OpenStack-based cloud platform. + + - Software Defined Network Controller (SDNC) executes network configuration for + cloud computing resources and network. + + - Application Controller (APPC) executes Virtual Network Functions (VNF) configurations and lifecycle + management operations. + + - Virtual Function Controller (VF-C) is responsible for lifecycle management of virtual network functions + and network services based on VNF using VNF Manager. + + - 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 events, performance, + usage and publishes information to policy that executes the rules to perform + closed loop actions. + + - Holmes provides alarm correlation and analysis for Telecom cloud + infrastructure and services, including servers, cloud infrastructure, + VNFs and Network Services. + + - Common Services - operational services for all ONAP components including + activity logging, reporting, common data layer, access control, resiliency, + and software lifecycle management. + +Project Specific Release Notes +++++++++++++++++++++++++++++++ +ONAP releases are specified by a list of project artifact +versions in a :ref:`manifest`. +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. + +Platforms Requirements +++++++++++++++++++++++ +ONAP Amsterdam Release has been tested on Linux OSs. Details are :ref:`available here `. + + +.. index:: Download + +Download & Install +++++++++++++++++++ +There are 3 approaches to install ONAP: + +* Full ONAP installation using Heat template +* Advanced installation to install individual components +* Experimental installation using Kubernetes + +Full ONAP installation using Heat template +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +From a complete demo solution perspective. This installs the whole ONAP, refer to :ref:`Setting Up ONAP `. + +Advanced installation to install individual components +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +From a developer perspective, ONAP can be installed component per component. For details, refer to :ref:`the installation procedure available for each component`. +The advanced installation procedure is recommended only for experienced developers who desire to focus their attention on a few components and who have a deep understanding of dependencies between components. +This type of installation is not recommended to fully install ONAP. + +* The list of ports used by default within ONAP is documented in `ONAP Service List `_. +* The 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. + +Experimental installation using Kubernetes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +From a complete demo solution perspective using Kubernetes. This installs the whole ONAP, refer to :ref:`ONAP Operations Manager - Quick Start Guide `. + +Documentation ++++++++++++++ +ONAP Amsterdam Release documentation is available :ref:`here `. +For Amsterdam this includes: + + * A high level :ref:`architecture view` of how components + relate to each other. + + * A collection of documentation provided + by :ref:`each project `. + + * Application Programming Interface + Reference :ref:`available here `. + + * The `developer wiki `_ remains a good source of + information on meeting plans and notes from committees, project teams and + community events. + +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 `_. + +.. index:: Licensing + +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 `_. + +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, 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 `_. + +You may 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