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.
LSO Hackathons are used to accelerate the evolution and development of OpenLSO.
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:-
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.
The architecture of OpenLSO is exactly that defined in MEF specifications within the following design constraints:-
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.
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: