While implementing Open Baton we have
followed as much as possible the ETSI NFV MANO specification keeping in mind as first
requirement the extensibility of the framework. For this reason, Open Baton
provides several mechanisms for being extended at every level in order to interoperate with
heterogeneous network functions and cloud infrastructures.
VNFM Interoperability Mechanisms
Open Baton supports several VNFM and VIM solutions. It provides a generic Virtual Network Function
Manager (combined with its own Generic Element Management System) which can be used for
managing VNF Packages. Furthermore, it supports additional mechanisms for integrating
external VNFMs: either over a message bus using the pub/sub mechanism or using a RESTFul
API. For both scenarios a SDK is provided for easily building new VNFMs.
Integration with a Multi-site NFV Infrastructure
Open Baton fully integrates with OpenStack as first Point of Presence (PoP). The VIM Driver
mechanism allow to integrate external heterogeneous PoPs without modification to the
orchestration logic. The provided OpenStack driver uses the OpenStack APIs for requesting
virtual compute and networking resources. Following the ETSI NFV specification the OpenStack
API is just one of the VIM interfaces implementation.
Virtual IMS to Get Started Immediately
Open Baton supports several VNFs. In order to get started immediately,
you can play with the OpenIMSCore and Clearwater IMS VNFs already provided via the Marketplace.
With few steps you should be able to deploy a complete IMS Network Service on top of OpenStack.
Please check also our tutorial
section on the documentation website for additional use cases.