1 / 5

NFV Service Verification: Challenges & Solutions

This document addresses the verification challenges in NFV services, including configuration inconsistencies, VNF dependency issues, load balancing, policy and state consistency, performance, and security. It also discusses open-source related issues and proposes a next step for ongoing validation and contribution to a project in Open Daylight.

swyckoff
Download Presentation

NFV Service Verification: Challenges & Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Verification of NFV Services : Problem Statement and Challengesdraft-shin-nfvrg-service-verification-03 M-K. Shin, ETRI, K. Nam, Friesty S. Pack, KU, S. Lee, ETRI R. Krishnan, Dell, T. Kim, LG U+ NFVRG Meeting@IETF93, Prague

  2. Motivation • NFV relocates network functions from dedicated hardware appliances to generic servers, so they can run in software. However, incomplete and/or inconsistent configuration of VNF and FGs (aka, service chain) may lead to verification issues. • Properties to be checked on NFV services • Dependencies of network service components in NFV • Invariant and error check in VNF FGs (e.g., infinite loop, confliction of properties or interference between VNFs, consistent ordering of FGs, etc.) • Load balancing among VNF instances • Policy and state consistency on NFV services • Performance • Security

  3. Changes since IETF92 • Address most of the comments from last meeting • Mainly related to the scope (e.g., static vs. dynamic changes) and verification framework options/issues • -02 and -03 • Verification framework section removed • Many variations and too early to fix architectural aspects • Properties section revised • Adding some additional text explaining examples (thanks Ramki) • Open source related issues (e.g., consistency of distributed state, Intent and compiling, etc.) • A new co-author added • Ramki Krishnan • And many editorial updates

  4. Open source related issues • Consistency of distributed state (management) • Open Daylight, ONOS • RAFT algorithm is used for distribution and replication • No "one-size-fits-all" solution for control plane data consistency • Intent or policy-based languages and compiling • Intent allows for a descriptive way to get what is desired from the infrastructure • A Intent compiler translates and compiles it into low level instructions (e.g., SDN controller/OpenStack primitives) for network service components. • Error checking or debugging are critical for reliable Intent-based service composition.

  5. Next step • Deal with the ongoing validation of the life cycle, composition of VNF, etc. • Contribute to a project related to verification or correctness/ consistency checker in Open Daylight

More Related