OpenLSO is a MEF-facilitated service orchestration ecosystem within which MEF member companies collaborate to maximize the alignment of market implementations - both Open Source and proprietary - with MEF-defined LSO specifications. The objective of OpenLSO is to accelerate market adoption of LSO as defined by MEF in order to achieve fully-featured end to end service orchestration of MEF-defined service lifecycles. The output of OpenLSO includes pointers to upstream Open Source projects that contain LSO-based software code contributions, as well as providing use cases and reference implementations on how to use that upstream code.

OpenLSO is run by the MEF membership in close collaboration with market leaders in Open Source service orchestration solutions, and Open Source projects such as OPEN-O.

OpenLSO interacts with OpenCS via the LSO Reference Point LSO Presto.

LSO Hackathons are used to accelerate the evolution and development of OpenLSO.

 

OpenLSO Stakeholders

The primary stakeholders of OpenLSO are the service providers that implement service orchestration as per the MEF LSO specifications across multiple networks and domains.

OpenLSO enables service providers to improve:-

  • Interoperability
  • Scalability
  • Testability
  • Reusability
  • Security

of their LSO service orchestration solutions.

Secondary stakeholders of OpenLSO include equipment manufacturers, SDOs, Open Source communities and MEF projects that are impacted by LSO specifications. In the case of equipment manufacturers, they can use OpenLSO to repackage their solutions and bring them to market with support for their value add features.


OpenLSO Architecture

The architecture of OpenLSO is exactly that defined in MEF specifications within the following design constraints:-

  • Implements the MEF's LSO Reference Architecture (currently in draft form and available only to MEF members)
  • Adheres to a component-based and layered architecture paradigm
  • Implement a client-service (including REST) approach

A consequence of these design constraints is that OpenLSO contain clearly defined and separate functional layers where upper layers send commands to lower layers, and may react to events in these layers, allowing data to flow both up and down between the layers.

Component View

openlso-component-view

Figure 1 OpenLSO Component View

LSO Management Interface Reference Points

As shown in Figure 1, OpenLSO focuses on three of the LSO Reference Architecture's Management Interface Reference Points:

OpenLSO implements LSO Legato and LSO Interlude and consumes LSO Presto.  

OpenLSO Components

OpenLSO components implement LSO functionalities as specified by the LSO Reference Architecture.

 

Management RequirementComponent TypeOpen Source Project
Order Fulfillment OrchestrationTBDTBD
Service Configuration and Activation OrchestrationTBDTBD
Service Control OrchestrationTBDTBD
Service Delivery OrchestrationTBDTBD
Service Testing OrchestrationTBDTBD
Service Quality ManagementTBDTBD
Service Problem ManagementTBDTBD
AnalyticsTBDTBD
Policy-based ManagementTBDTBD

Relationship to OpenCS

OpenCS exposes the SDN and NFV resources and interfaces OpenLSO will use in order to orchestrate the service lifecycle of a connectivity project.

OpenLSO consume the standard APIs exposed by OpenCS via LSO Presto.

Deployment View

OpenLSO is deployed on MEFnet servers.

openlso-deployment-view

 

Software Components

The goal of OpenLSO is to target open source components that align with, exercise and validate LSO Reference Architecture's functional blocks and interface points.

 

Cloud/Virtualization

Component

Open Source Project
 

DC Orchestration
 

OpenStack
CloudStack
Cloudify
OpenNebula
Helion
Eucalyptus
XOS
 
Platform as a Service
 
Cloud Foundry
OpenShift 
Provisioning and Management Tool
 
Puppet
Ansible
Salt Stack
JuJu
Chef 
Virtual Network Functions
 
CloudRouter
XORP
CPqD RouteFlow,
NetFilter
Snort
OpenWRT
Clearwater
VMs and Containers
 
Kernel Virtual Machine (KVM)
Xen
Docker
Example(s)

openlso-component-example

Related and Further Reading

OpenCS |

Categories

 

Status

DRAFT

Source(s) and Reference(s)
Contributor(s)
Reviewer(s)