Model-Driven ONAP Operations Manager (OOM) On-boarding with TOSCA and Cloudify
Introduction ONAP Operations Manager (OOM) is an ONAP tool to efficiently deploy, manage and operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.). The OOM project takes a cloud-native approach to manage the OOM cluster and relies on Kubernetes as the main platform to manage ONAP services. In this post, we will
The Birth of an Edge Orchestrator – Cloudify Meets Edge Computing
Shay Naeh discusses the challenges of orchestrating at the edge and how Cloudify is the perfect orchestration platform for mobile edge devices.
An Open Source, Dynamic, and Integration-Based vCPE/SD-WAN Orchestration Service Built with Cloudify
This post explains how Cloudify’s integration-based approach to vCPE/SD-WAN orchestration offers a dynamic service for real-time VNF onboarding and service chaining.
Cloudify Orchestrates Service Function Chaining (SFC) at MEF
The MEF’s Goal and How Cloudify Fits the Bill The MEF is focused on enabling dynamic network services for the digital economy and the hyper-connected world by providing businesses an on-demand, cloud-connected, secure, and assured experience. It provides a practical evolution toward interconnected, orchestrated, and automated networks powered by Open LSO (lifecycle service orchestration),
How to Orchestrate VNFs in NFV and Deploy a Skype-like vIMS Application with Cloudify and Clearwater on a Multi-VIM Environment
What is a vIMS on boarding service? It is a virtual phone or even a mobile phone where users can connect to each other, similar to Skype. It is built on the following architecture. Bono, which receives the incoming connection, then sends it to Sprout which acts as the IP gateway with all of
NFV Orchestration on OpenStack, VMware, and More (Multi-VIM) with Cloudify and TOSCA
What is a VIM? A VIM, according to the MANO specification, is a virtual infrastructure manager. In a nutshell, a VIM is the same as IaaS in the cloud domain and Cloudify brings that IaaS concept to the telecom world. Intelligent NFV orchestration for any telecom environment. Download today. Go While, OpenStack has been
NFV Service Chaining Orchestration for Any Network Topology & Architecture
It’s a well-known pain point for Telecom companies that provisioning new services into their networks is a time and resource consuming process, as well as cost intensive. Until now, introducing new services would take months to years and was done with physical proprietary devices that took a long time just to procure – let alone
More Reference NFV Architecture Based on TOSCA + NetConf YANG
TOSCA is a very good descriptive language for VNF definition, nodes monitoring and active policies like healing and scaling, as it has the combination of declarative descriptions of the application topology with all its components – from the application and network components down to the compute resources, software and everything else – along
TOSCA and YANG for Application and Network Orchestration
We’ve been encountering quite a number of Telecoms and service providers mentioning TOSCA, YANG and modeling languages in general, for their NFV work.
NFV on OpenStack Cloud – Open Source Everything
As we get more heavily involved with NFV, I would like to share my experience taking a few VNFs (virtual network functions) and SFCs (service function chains) and implementing them on public and private clouds. I thought implementing an IMS system on a public cloud would take forever but I was surprised to