White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 35 of 144

Understanding OPNFV 35 isolate failures to just one component at a time. So, you are unlikely to have an entire service or set of services fail, which is a distinct possibility with a forklift upgrade. ● Continuous monitoring: The final piece of the puzzle is to monitor NFV services continuously. Every log, metric, and alert has to be processed by automated big data systems, because lifecycle management decisions for any NFV software component must be made automatically based on policies. It is simply not possible to have a human being monitor all individual components. That's why you should never see CLI access to an individual VNF. The concept no longer makes sense in NFV! To achieve DevOps successfully, organizations require automated tooling. CI (including continuous testing), and CD are often automated as a pipeline. In chapter 6, we will look at the OPNFV CI pipeline in more detail. In general, a CI/CD pipeline, followed by continuous monitoring, could be generalized as follows: Representative CI/CD Pipeline and Ongoing Monitoring Again, don't worry if this topic feels completely futuristic, we don't anticipate a full DevOps for NFV approach to take hold for at least a few years. Cloud Native Software The third area of technology change to ensure a successful NFV transformation is cloud native software. The entire NFV stack needs to, over time, migrate to a cloud native software architecture. Analogous to DevOps, cloud native NFV is similar to, but not the same as cloud native apps for consumer and enterprise use. Simply put, cloud native NFV software architecture requires the following: ● Ability to scale out (to multiple nodes), scale in, and self-heal in an automated fashion. ● Ability to withstand, even thrive in an environment where hardware failures are commonplace. ● Support the DevOps for NFV approach (see above section) to fully automate the entire lifecycle of every component of the NFV software stack.

Articles in this issue

view archives of White Papers - Understanding OPNFV