Release Overview

• Release Name: Mercury
• Release Version: 2.0.0
• Release Date: April 27, 2017
• Release Type: Generally Available
• Former Release: OPEN-O Sun Release
• Next Release: OPEN-O Mercury Release is the latest OPEN-O Release. OPEN-O has merged with Open Source ECOMP to become ONAP

Release Summary

OPEN-O is developing a solution to allow ''Any Service on Any Network". OPEN-O delivers to the community a micro services based architecture providing operators an incremental path to transform their networks (including OSS/BSS), through the adoption of SDN and NFV orchestration platform.

The Sun Release is built to support our Virtual CPE use case. This use case has two components:

• Through a coordinated cloud and network approach, OPEN-O Enterprise Use Case provides automated end-to-end ''cloud + enterprise private network'' service to enterprise users. Enterprise users benefit from high-quality and cheap cloud service without deploying any complex infrastructure by themselves.
• OPEN-O Residential Use Case allows operators to provide off the shelf residential vCPE services, such as parental control and firewall, within minutes. Open-O orchestrates the VNFs for vCPE to be deployed to the nearest TIC Edge to the requesting subscriber’s home.

The Mercury Release is built to support VoLTE (Voice Over LTE) where OPEN-O automatically triggers action, scales up and down to add and remove more virtual resource on data plane to cope with traffic.

Functionality

OPEN-O Sun Release is built around 5 main projects providing the following functionalities:

• GS-O project implements the Global Service Orchestrator. GS-O is responsible for providing end-to-end services.
• SDN-O project implements the Software Defined Network Orchestrator. SDN-O provides connectivity services across SDN and legacy networks.
• NFV-O projects implements the Network Function Virtualization Orchestrator. NFV-O provides an ETSI MANO-aligned NFV orchestrator.
• Common Services project provides the common services for all the other OPEN-O components, including our Microservice bus, HA, Driver Manager, Log, Authentication and Protocol Stack.
• Common Tosca project provides the TOSCA Parser and Execution Engine and Model Designer.

OPEN-O Mercury Release add the following functionalities:

• VNF-SDK project delivers VNF packaging tool, VNF Marketplace and VNF Testing Framework to enable VNF suppliers to participate in the OPEN-O platform. It works with NFV-O to facilitate VNF Onboarding.
• Modelling project documents API and Data Models used in OPEN-O.
• GVNFM project provides a generic VNF manager as defined in ETSI NFV standard.
• Client project provides an unified GUI and CLI for the OPEN-O functionalities provided over RESTful API. In addition, Client provides Java & JS SDK for OPEN-O services.
• Multi VIM project offers support for multiple versions of OpenStack and VMWare VIMs.
• SDN Hub Driver provides drivers for SDN Controllers.
• SDN-O provides catalogue driven orchestration and management engine (SDN-O LCM), TOSCA based.
• Holmes project provides an alarm correlation and analysis framework.
• Policy project provides a policy framework for OPEN-O.

Supported Platform

OPEN-O Mercury Release has been tested on CentOS version 7 and is the only OS supported.

Required Software

Depending on the way you are installing OPEN-O (through the Tarball or Docker) the following software may be installed, configured and running prior to execute any OPEN-O Service.
Consult the Tarball or Docker installation instructions for further details.

Integration and compatibility Matrix

This section is to document the third party software and their version OPEN-O is supporting.

Stack

Telecom

Third Party Dependencies: Controller view

Third Party Dependencies: Services View

Downloads

Download Binaries

Mercury Release deliverables are available in 2 format: Tarball and Docker. The are both accessible from the OPEN-O Releases download page.

Download Source Code

Source code is available to the public in Gerrit.
Clone each project from Gerrit by using the command:

git clone https://gerrit.open-o.org/r/'project'

To find the complete list of OPEN-O projects, see https://gerrit.open-o.org/r/#/admin/projects/

Example: git clone https://gerrit.open-o.org/r/gso

Other Systems

Access to OPEN-O Continuous Integration System.

Documentation

Installation

There are 2 main ways to install OPEN-O:

1. From the Tarball: procedures to install OPEN-O from A to Z using the OPEN-O Tarball.
2. Using Docker: procedures to install OPEN-O using Docker.

Architecture

To understand the overall OPEN-O architecture, functional components and microservice refer to the OPEN-O Architecture and more particularly for OPEN-O Mercury Release Architecture.

GUI Documentation

To understand the OPEN-O GUI Operations refer to the OPEN-O GUI Operations.

CLI Documentation

Refer Open-O CLI wiki for developer guide and admin guide.

API Documentation

Each OPEN-O functional component has its set of API Documentation.

License

OPEN-O is an Apache Version 2 license type of Open Source project.

More info

OPEN-O Wiki
Link toward OPEN-O Portal