While ETSI has been instrumental in defining MANO product architecture, and a majority of telecoms vendors have contributed to this architecture in terms of both open-source and commercial implementations. Below is an attempt to normalize our understanding of implementation architectures from the ETSI NFV MANO Architecture perspective. We have used well-known public examples (generally open-source examples that include some of the earlier described projects) of different ways of implementing MANO to showcase both the diversity and commonality between implementations.
ETSI Standard MANO Architecture
OpenMANO/RIFT.io Architecture (OSM)
RIFT.io has taken the approach of commercializing the OpenMANO open-source implementation provided by ETSI with full product support. As a part of the implementation, RIFT provides the NFVO and partners with Telefonica, 6Wind, Metaswitch Networks, Intel and Canonical to provide a complete stack. As we described earlier, Telefonica contributed its original implementations of OpenMano to ETSI, RIFT.io provided an open-source component for orchestration and Canonical providing Juju as a generic VNFM in this implementation.
OpenBaton enables virtual Network Services deployments on top of heterogeneous NFV Infrastructures and integrates with OpenStack, and provides a plugin mechanism for supporting additional VIM types. It supports Network Service management either using a generic VNFM or interoperating with VNF-specific VNFM. It uses different mechanisms (REST or PUB/SUB) for interoperating with the VNFMs, and also integrates with additional components for the runtime management of a Network Service. For instance, it provides auto-scaling and fault management based on monitoring information coming from the NFVI.