* Release Date: November 16, 2017
-Amsterdam Release
------------------
+Getting Started With Amsterdam
+------------------------------
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
+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
+for network automation-with an open standards focus-faster than any one
product could on its own.
Functionality
and Controllers that manage resources corresponding to their assigned
controlled domain:
- - Service Orchestrator (SO) executes the specified processes and automates
+ - 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.
+ services and resources. SO is especially able to drive any OpenStack-based cloud platform.
- - Software Defined Network Controller (SDNC) network configuration of
- cloud computing resources.
+ - Software Defined Network Controller (SDNC) executes network configuration for
+ cloud computing resources and network.
- - Application Controller (APPC) Application resources.
+ - Application Controller (APPC) executes Virtual Network Functions (VNF) configurations and lifecycle
+ management operations.
- - 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.
+ - 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
**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.
+ - 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 hosts, vims, VNFs and NSs
+ - 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 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.
+Platforms Requirements
+++++++++++++++++++++++
+ONAP Amsterdam Release has been tested on Linux OSs. Details are :ref:`available here <demo-installing-running-onap-requirements>`.
+
.. index:: Download
Full ONAP installation using Heat template
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-From a complete demo solution perspective. This installs the whole ONAP,
- refer to :ref:`Setting Up ONAP <demo-installing-running-onap>`.
+From a complete demo solution perspective. This installs the whole ONAP, refer to :ref:`Setting Up ONAP <demo-installing-running-onap>`.
Advanced installation to install individual components
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-From a developer perspective. ONAP can be installed component per component:
- :ref:`installation is listed in <doc_onap-developer_guide_projects>`.
+From a developer perspective, ONAP can be installed component per component. For details, refer to :ref:`the installation procedure available for each component<doc_onap-developer_guide_projects>`.
+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 <https://wiki.onap.org/display/DW/ONAP+Services+List>`_.
* The ONAP Source Code is available through Gerrit at https://gerrit.onap.org or Git at https://git.onap.org/.
Experimental installation using Kubernetes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-From a complete demo solution perspective using Kubernetes. This installs the whole ONAP, refer to `ONAP Operations Manager - Quick Start Guide <http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/OOM%20Project%20Description/oom_project_description.html#quick-start-guide>`_.
+From a complete demo solution perspective using Kubernetes. This installs the whole ONAP, refer to :ref:`ONAP Operations Manager - Quick Start Guide <onap-operations-manager-project>`.
Documentation
+++++++++++++
Known Issues and Limitations
++++++++++++++++++++++++++++
-Known Issues and limitations are documented in each project Release Notes.
-
-Refer to :ref:`release notes <doc-releaserepos>` for each project.
+Known Issues and limitations are documented in each :ref:`project Release Notes <doc-releaserepos>`.
.. index:: Reporting Bugs
+++++++++++++++++++
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 <https://jira.onap.org>`_.
+ * In case you are familiar within ONAP, you can directly report a bug by creating a Jira issue at `ONAP Jira <https://jira.onap.org>`_.
- * 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 .
+ * If you don't know you are facing a bug or have a question, post your question into the `Ask question <https://wiki.onap.org/display/DW/questions/all>`_.
+ You will need a Linux Foundation ID to login and post your question. Get a Linux Foundation Identity using this `quick procedure <https://wiki.onap.org/display/DW/Joining+the+Community>`_.
-You may consider these `recommendations <https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-RecommendationsforwrittingProperJIRAIssue>`_ to elaborate the issue you are facing and this `guideline <https://wiki.onap.org/display/DW/Mailing+Lists>`_ to register into the ONAP Discuss mailing list.
+You may consider these `recommendations <https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-RecommendationsforwrittingProperJIRAIssue>`_ to elaborate the issue you are facing.
.. Include files referenced by link in the toctree as hidden
Code Review / doc.git / blobdiff