Page tree
Skip to end of metadata
Go to start of metadata

Project Name:

ONAP

Project description:

From: ONAP ReadTheDocs

The Open Network Automation Platform (ONAP) project addresses the rising need for a common automation platform for telecommunication, cable, and cloud service providers—and their solution providers— that enables the automation of different lifecycle processes, to deliver differentiated network services on demand, profitably and competitively, while leveraging existing investments.

Prior to ONAP, telecommunication network operators had to keep up with the scale and cost of manual changes required to implement new service offerings, from installing new data center equipment to, in some cases, upgrading customer equipment on-premises. Many operators are seeking to exploit Software Defined Network (SDN) and Network Function Virtualization (NFV) to improve service velocity, simplify equipment interoperability and integration, and reduce overall CapEx and OpEx costs. In addition, the current, highly fragmented management landscape makes it difficult to monitor and guarantee service-level agreements (SLAs).

ONAP is addressing these challenges by developing global and massive scale (multi-site and multi-Virtual Infrastructure Manager (VIM)) automation capabilities for both physical and virtual network elements. It facilitates service agility by supporting data models for rapid service and resource deployment, by providing a common set of Northbound REST APIs that are open and interoperable, and by supporting model driven interfaces to the networks. ONAP’s modular and layered nature improves interoperability and simplifies integration, allowing it to support multiple VNF environments by integrating with multiple VIMs, virtualized network function managers (VNFMs), SDN Controllers, and even legacy equipment. ONAP’s consolidated VNF requirements enable commercial development of ONAP-compliant VNFs. This approach allows network and cloud operators to optimize their physical and virtual infrastructure for cost and performance; at the same time, ONAP’s use of standard models reduces integration and deployment costs of heterogeneous equipment, while minimizing management fragmentation.

Scope:

Describe the are that project is addressing (for instance cloud infrastructure)

The Open Network Automation Platform (ONAP) project addresses the rising need for a common automation platform for telecommunication, cable, and cloud service providers—and their solution providers— that enables the automation of different lifecycle processes, to deliver differentiated network services on demand, profitably and competitively, while leveraging existing investments.

Describe the planned areas of focus and development (for instance keystone federation for distributed clouds)

ONAP enables product- or service-independent capabilities for design, deployment and operation, in accordance with the following foundational principles:

  1. Ability to dynamically introduce full service lifecycle orchestration (design, provisioning and operation) and service API for new services and technologies without the need for new platform software releases or without affecting operations for the existing services
  2. Carrier-grade scalability including horizontal scaling (linear scale-out) and distribution to support large number of services and large networks
  3. Metadata-driven and policy-driven architecture to ensure flexible and automated ways in which capabilities are used and delivered
  4. The architecture shall enable sourcing best-in-class components
  5. Common capabilities are ‘developed’ once and ‘used’ many times
  6. Core capabilities shall support many diverse services and infrastructures
  7. The architecture shall support elastic scaling as needs grow or shrink
Specify any upstream sources or projects the team will be working with (for instance OpenStack/keystone)

N/A       

Specify and local testing and integration needs (outline intent here, infra needs are listed later)

Cloud space is required for spinning up components to test their interoperability. 

Describe how the project is extensible in the future or how others might participate

ONAP is a Linux Foundation hosted project and is open to anyone with a Linux Foundation ID to participate in. More details are available here.

The future extensibility of the project is driven by the Technical Steering Committee. 

Infrastructure needs:

We request forks created from existing ONAP projects (https://gerrit.onap.org/r/#/admin/projects/) into the Nordix namespace, and the requisite job/workflows to mirror those repos and upstream contributions.

For testing purposes there is a requirement for cloud access to create live environments. The amount required will expand and contract based on the stage of the release and requirements of the individual teams.

Dependencies:

N/A

Project members and contributors:

Committers:

Henrik Andersson

Fiachra Corcoran

Sofia Wallin

Liam Fallon

Byung-Woo Jun

Ram Krishna Verma 

Contributors:

Ram Krishna Verma

Waqas Ikram

Fiachra Corcoran

Liam Fallon

Gerard Nugent

Ajith Sreekumar

Andr�� Schmid

Eliezio Oliveira

Byung-Woo Jun

David Farrelly

Eoin Hanan

Joseph O'Leary

Rajendra Jaiswal

Gerard Hickey

Helena Lydon

Vasyl Razinkov

Henrik Andersson

Maxime Bonneau

Ning Xi

Tim Huang

Bilal Iqbal

Tamas Bakai

Yongchao Wu

Michael Morris

Bowen Sun

John Keeney

Lathishbabu Ganesan

Gareth Roper

Anderson Ribiero

Andrew Lamb

Björn Magnusson

Ephraim Martin

rahul.tyagi@ericsson.com

Sofia Wallin

Xuefeng Xie

Dermot Melia

James Cuddy

Muhammad Rehan Raza

Patrik Buhr

Ronan Kenny

Robert Tomczyk


  • No labels