White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 32 of 144

Understanding OPNFV 32 of 3rd party solutions. DevOps The second area of technology change to required ensure a successful NFV transformation is DevOps. Every layer of the NFV stack (VNFs, NFVI, and MANO) is seeing innovation at a rate faster than anything witnessed in the prior era of physical network functions, and this pace is not going to slow down. To absorb this rate of innovation, organizations will have to fundamentally change their approach to technology components. Continuous Innovation Requires a New Approach The figure on the left shows, on a relative basis, slower innovation created by vendors at a predictable rate. In this case, users can upgrade every 6-18 months and perform routine operations in the interim. The right-hand side figure shows how that same safe and stable approach breaks down with rapid, continuous, and unpredictable rates of innovation coming from not just vendors but increasingly from open source communities. A 6-18-month upgrade is now going to create massive risk to an entire service or class of services. What's more, this window also keeps innovation away from the end users' hands for an unnecessary 6-18 months, just as it keeps valuable user feedback away from developers. What makes sense instead is small incremental changes, made regularly.

Articles in this issue

view archives of White Papers - Understanding OPNFV