White Papers

Understanding OPNFV

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

Contents of this Issue


Page 36 of 144

Understanding OPNFV 36 In short, every step below has to be software defined, with zero manual steps: Full Automation of NFV Software Lifecycle These three requirements necessitate re-architecting software applications around a set of core principles. The list below is not supposed to be complete; modern cloud native software is based on a principle called "twelve factor applications," but while you'd think that NFV was a shoo-in for "cloud native" computing, it turns out there are some differences. Twelve-factor apps, you see, are meant to stateless – they're all about separating processing and state management so that any part of a system is the same as any other part. However, networking applications are all about state management, so the normal cloud native assumptions need to be translated for NFV 2 : ● Microservices with API as contracts: A VNF needs to be split into small pieces or microservices that are loosely coupled and communicate through well-defined APIs. Both the code and the data model has to be split. This approach provides benefits to both operators and VNF vendors. Operators benefit by being able to scale VNFs in a very granular fashion, reduce the impact of faults (by limiting the blast radius to one microservice) and manage the lifecycle of VNFs using a DevOps mechanism. Vendors benefit by being to roll out new features faster and eliminate dead features. As we have discussed, VNFs are different from classic apps, in that they have a datapath that performs packet processing and a control-path that provides management, signaling etc. For this reason, microservices have to be used with care. The datapath is not an obvious candidate, as multiple microservices in the datapath could create inefficiencies due to multiple packet hops, each with switching and packet processing overhead. ● Decoupled from hardware: Most benefits from the DevOps section can only be 2 We mostly talk about VNFs, but the principles apply to other components of the NFV stack as well

Articles in this issue

view archives of White Papers - Understanding OPNFV