...
| Expand | ||
|---|---|---|
| ||
OSM follows a container based implementation approach but not strictly microservices based approach. This is based on the key architectural principle of maintaining simplicity. OSM components are built in to LXD containers and each of these containers can be a monolith in its own sense. Inter-Component interactions are implemented through REST APIs. OSM follows a model driven architecture principles – but primarily use this concept for the NS and VNF models and not for internal components.
Opendaylight follows the microservice architecture principle and uses OSGi runtime enabled through Apache Karaf. Opendaylight also supports a model drive approach for defining the micro services, where in each micro service is modelled using YANG DML. Opendaylight supports numerous tool sets to process the YANG models – for parsing, code generation, RESTCONF etc. The MD-SAL framework available in Opendaylight functions as a common platform layer which enables interaction between microservices and also manages the configuration and operational state of micro services. MD-SAL also supports scalable deployments enabled through clusters implemented using akka framework. MD-SAL supports an event sourcing approach wherein the object state changes are stored as series of event logs which can be replayed for recovery of state. Following Yang model for micro services Opendaylight can manage three facets of microservice – data/state, rpc/actions, notification/events.
ONOS follows microservice architecture and uses OSGi runtime enabled through Apache Karaf. Unlike Opendaylight ONOS does not have a common framework like MD-SAL or does not follow a model driven approach. But ONOS supports some of the interesting concepts like cluster based deployments, efficient entropy management, state consistency, data sharding etc. ONOS variant supported by Ciena BluePlanet is also available as Docker container, to leverage container based microservice use cases in a wider scope.
OpenBaton uses a ‘microservice-like’ approach but not strictly leverage on any microservice framework. The modules are based on Spring Framework and interaction between microservices is enabled through RabbitMQ message bus and REST API.
Based on last OPEN CORD conference, It appears that ONOS and XOS transforming itself to Cloud-Native. They seems to be moving ahead with cloud-native technologies such as
|