White Papers

Understanding OPNFV

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

Contents of this Issue


Page 33 of 144

Understanding OPNFV 33 What does that kind of environment look like? Let's take Netflix as an example. Netflix isn't strictly an NFV architecture, but it does exemplify this type of development; Netflix makes thousands of small changes to their production environment every single day. Using the old method of "forklift upgrades", that kind of pace would have been not just unheard of – it would be suicide. This process of making continuous incremental changes results from a practice called DevOps. The term "DevOps" has become slightly overused lately, leading to some argument over what it actually means (solid Wikipedia definition notwithstanding). Some view it as a mindset where development and ops teams work in tight collaboration. Others view it as a set of activities. In reality it is perhaps a bit of both. Using the former viewpoint, DevOps is about two groups with different goals coming together. Development's 1 goal is to increase software velocity. Clearly, development is incentivized to create change. Operations, on the other hand, is measured in terms of network availability, Mean Time Between Failures (MTBF), Mean Time to Repair (MTTR) and other operational metrics. So, while Operations, isn't necessarily trying to prevent change, they are obligated to operationalize change and make sure that it happens without disruptions. DevOps is a way to encourage collaboration by breaking down the walls between these two teams and helping them embrace change without jeopardizing stability. If we view DevOps from the second lens of "activities", it involves these following steps: continuous integration, continuous testing, continuous delivery, continuous monitoring. 1 In the case of NFV, the development of the NFV software stack and VNFs is typically not done in- house. For that reason, "Dev" in DevOps for NFV may be loosely considered external vendors and open source communities. This is different from web giants, where most of the development is in-house.

Articles in this issue

view archives of White Papers - Understanding OPNFV