White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 74 of 144

Understanding OPNFV 74 Project Details Projects related to service assurance and availability are: Project Description Availability (HA for OPNFV) This project creates APIs and requirements for high availability (HA) in carrier-grade NFV scenarios. The project addresses HA at three different layers: hardware HA, virtual infrastructure HA and service HA. As an example of the project's success, during the Colorado release of OPNFV, this project identified a number of gaps that were successfully closed in OpenStack's Mitaka release, while some others were deferred to the Newton release. Barometer (Software fastpath service quality metrics) There is no shortage of open source data collection monitoring tools. Barometer takes an NFV-centric approach to this problem by capturing statistics and events from the NFVI layer in order to detect faults and enforce service level agreements (SLAs). Barometer passes this data on to higher level fault management systems. The project uses coll ect d for this purpose, and has an extensive set of plugins. These plugins range all the way from IPMI, BIOS, OVS, and DPDK to platform monitoring. Information gathered can be reported to higher level tools using a variety of interfaces, including standard telco interfaces such as SNMP. Doctor (Fault management) Doctor creates fault management and maintenance systems to ensure high availability for VNFs (see the next section) to match what operators are used to with physical network functions. VES (VNF Event Stream) While Barometer focuses on VNFI, VES gathers VNF event streams using a common model and format to enable the management of VNF health and life cycle. Currently end users have to deal with events and statistics from VNFs in a variety of different formats using different standards (for example, SNMP vs. 3GPP or CSV vs. XML) in order to implement service assurance. This increases engineering costs and delays the introduction of new VNFs. VES aims to streamline this by creating three components: an agent for mapping source telemetry to the VES event format, collector for receiving and displaying events, and a VES data schema to support these two activities.

Articles in this issue

view archives of White Papers - Understanding OPNFV