NFV Management & Orchestration with TOSCA
NFV, (network function virtualization), is the growing need by Telcos and enterprises to deploy, manage and scale their network functions and services on standardized hardware. Cloudify, provides the full end-to-end lifecycle of NFV orchestration, from installation, provisioning, configuration and deployment through management and monitoring of your application or service in order for the system to take proactive actions, such as healing and scaling based on custom triggers, i.e. Day 0 through Day 2 support, all through a simple TOSCA-based YAML blueprint.
Cloudify participates in and sponsors diverse NFV projects and standards organizations, to help contribute to open source NFV MANO adoption.
GigaSpaces is an active participant in the TOSCA Technical Committee (TC) with 10 current members, while co-chairing the Instance Model workgroup, tasked with providing a complete representation of the state of a TOSCA service template deployment, as well as the Technical Marketing and Education ad-hoc, which promotes TOSCA's message and capabilities, and is building a community around the standard.
GigaSpaces is a member of the MEF Forum, and a leading member of the OpenLSO Service Function Chaining team. This team introduced service function chaining to the MEF's CE 2.0 services for the first time at the Euro16 LSO Hackathon, and is hard at work with introducing added functionality to the L3 layer to support complex SFC use cases.
Cloudify has decided to release its core capabilities to the Apache Foundation through the ARIA project. ARIA is an open governance and source orchestration engine, providing an actual code base and library built on TOSCA, to strengthen TOSCA's adoption and enable simple incorporation to orchestration projects.
The Open-O project is a Linux Foundation-backed project to develop an open-source NFV orchestrator that is also trying to standardize the way the orchestrator interfaces with other software elements in NFV. Cloudify are premier and founding members, joining immediately when launched in February 2016. The Open-O Mini Summit took place during the OPNFV Summit in Berlin, where the Cloudify team led a panel and a session on TOSCA/YANG interoperability. The Cloudify team serves in diverse roles in Open-O, Board Members and Treasurer, as well as on the Technical Steering Committee and Marketing Committee.
Cloudify & ETSI's MANO
ETSI, the European Telecommunications Standards Institute, defined a standard reference architecture to achieve NFV, where an integral part of this architecture is the MANO - the NFV management and orchestration layer.
MANO based on TOSCA
MANO is the layer defined by ETSI that manages and orchestrates the cloud infrastructure and resources, and it is comprised of the following elements:
- The VIM (Virtual Infrastructure Manager), essentially controls the interaction of the VNF with the compute, networking and storage resources of the chosen NFVI (i.e. cloud or virtualization layer).
- The VNFM (Virtual Network Function Manager), is responsible for the VNF lifecycle management - e.g. it takes action on instantiation, termination, failover, scaling in and out, and more. Cloudify serves as a generic VNF manager (G-VNFM) and enables full automation of all lifecycle stages for any network function. See this video example of vIMS management.
- The NFVO (NFV Orchestrator), as its name implies, basically serves the purposes of orchestrating and managing end to end network services, through the complex NFV architecture, including integration with SDN controllers, OSS/BSS systems, and more. Cloudify provides a fully open NFVO, learn more about NFV & SDN, and more.
ETSI's MANO is intended to provide the full end-to-end lifecycle of NFV orchestration and management – from installation and deployment through post-deployment, or in the telco industry terminology - Day 0 through Day 2 support.
As MANO is currently just a guideline all implementations of MANO are proprietary, aside from the TOSCA-based agnostic implementation that also enables the plugging in of additional standards like YANG/Netconf for service chaining.
The telco industry is known to be very standard driven, therefore, the alignment with MANO is an important element for NFV adoption, where many Telcos and Enterprises these days are searching for modeling languages to help achieve the goal of application and network orchestration, and are betting on OpenStack and the nature of standards-driven open source cloud to help deliver this in the real world. This is where the importance and adoption of a standard like TOSCA becoming an important criterion in the choice of an orchestration platform.
TOSCA has the combination of declarative descriptions of the application topology with all its components - including the load balancer, network, the compute resources, software and everything else, along with an imperative set of workflows to describe the logic of any process we need to automate. What this means from an NFV perspective, is that TOSCA is very good when it comes to defining virtual application topologies, VNF dependencies and relationships, actions to be performed as part of a lifecycle. This significantly simplifies the complexities involved with exposing networking elements and end-to-end lifecycle management for NFV, by abstracting the networking piece of the deployment into an application blueprint.
You can learn more about the TOSCA spec in our docs.