The heart of the NFVTime is an open source, thin and robust NFVi-OS that turns any x86-device, low or high resources, to a fully operational uCPE. With a very low system footprint and design optimized to extract superior performance from Intel™ processors, it is the perfect solution for operators seeking to rapidly deploy end-to-end, carrier-class networking solution for business or metro environment.
NFVTime-OS allows complete decoupling between hardware, software and VNF, enabling mix and match to optimize the service provider flexibility, Cap-Ex, Op-Ex and most importantly, utilize the community innovation and quickly adopt new hardware, services and architecture versions. It can run any VNF service out of the box and requires zero setup thanks to the NFVTime-Central provisioning and control server.
NFVTime-OS is tested and certified on many hardware types, obtained from any vendor or directly from Telco Systems.
NFVTime-OS support out of the box broad hardware from leading HW vendors and broad VNF library. With the backup of NFVTime-central, it automate and allow swift deployment of NFV services in mettar of weeks from decision to service luanch.
NFVTime-OS architecture is based on open source and community projects optimized to achieve carrier class uCPE. NFVTime uses RT Kernel to optimize and improve performance of the overall uCPE and VNFs performance.
The major NFVTime-OS building blocks include:
Open vSwitch (OVS) is used as the virtual networking component. It connects VNFs’ virtual ports between themselves and to the external ports. It also separates management and data traffic on the same WAN uplink port. Telco Systems solution support both VirtIP and DPDK and SRIOV to improved packet processing performance.
Selected OpenStack components – NFVTime-OS is based on various Openstack components to allow support uCPE lifecycle, security and manageability of the uCPE.
Control Plane Apps provide enhancements for routing and forwarding of management traffic within the uCPE, as well as monitoring and testing for all traffic.
uCPE Lifecycle Management Apps provide functions not available in OpenStack such as:
– HW level – temperature, fans, PSUs, CPU/RAM/Disk usage, etc.
– OS level – critical Linux processes & services, OVS, KVM, etc.
– OpenStack level – OpenStack agents (Nova, Neutron, etc.)
– Virtual Network level – virtual network traffic statistics (per VLAN, per flow, per virtual port)
– VM level – aliveness of VM processes, and possibly their vCPU/vRAM usage. This doesn’t include monitoring of the VNF itself (e.g. vFW internal statistics). Also, the Health Monitoring agent will never attempt VM self-healing as this must be controlled by the Orchestrator or VNFM.
Build for easy integration, Unified Management Layer
All management & control functions built in addition to OpenStack components can be controlled via unified CLI or through Telco Systems REST API.
The Unified Management Layer provides the northbound REST APIs (both Telco & OpenStack) to any Orchestrator or Controller and also connects to the Provisioning Server. In any addition, NFVTime-OS provides a unified CLI built on top of the REST API layer so it can easily support any function provided by the REST APIs (Telco or OpenStack).
In addition, OpenStack Horizon GUI can be enabled on the uCPE if it runs with a local OpenStack Controller.
Use of the SDxCentral service directory is governed by our Terms of Service, including without limitation those sections under the headings "CONTENT", "LICENSING AND OTHER TERMS APPLYING TO CONTENT POSTED ON THE SDXCENTRAL SITES", "INDEMNITY; DISCLAIMER; LIMITATION OF LIABILITY" AND "COPYRIGHTS". Under no circumstances will SDxCentral be liable in any way for any Content, including, but not limited to, liability for any errors or omissions in any Content or for any loss or damage of any kind incurred as a result of the use of any Content posted, emailed or otherwise transmitted via the Sites.