White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 46 of 144

Understanding OPNFV 46 Journey #2 Compute virtualization + SDN controller NFVI + SDN controller + VIM + MANO Journey #3 NFVI + SDN controller + VIM + MANO This above table does not talk about VNFs; even with VNFs, users could go with cloud hosted, cloud optimized, or cloud native VNFs. Similarly, users could use DevOps practices only for the development environment first, or jump into DevOps for all stages – dev/test/staging/production. And so, there are many routes to your destination. 5. Find use case: It is too tempting to build out a 20-50 node NFVI/MANO POC and then wait for VNF workloads. But this approach does not work – it results in orphan clouds. What does work is to find a real production workload – ideally non-mission-critical – and then create an NFVI/MANO infrastructure around it. It is perfectly fine if this is a small use case to begin with, you need some real time gains today! To use a non-telco example, in the case of Volkswagen, they picked a car configurator application for their customers in Spain and built an OpenStack cloud around it. 6. Find executive sponsor: It is important for a key transformation such as NFV to have top-down support. Without an executive sponsor, an initiative such as NFV is likely to wither away. Executives such as André Beijen, head of network innovation for KPN, and Deutsche Telekom Vice President Axel Clauberg have been vocal about their implementation approach to NFV. 7. Use dedicated teams: Rather than add another task to existing teams' burden, starting with a new dedicated team seems to be more successful. The new team can also embrace a new culture, processes and tools, as opposed to reusing existing ones. KPN, for example, assembled a new team for virtualization projects, recruiting key talent by asking for volunteers rather than assigning people. 8. Spread the knowledge: The initial team needs to act like a catalyst that transfers its newly acquired skills, knowledge, thinking, culture and processes to the rest of the organization. Going back to the Volkswagen example, they actively organize ongoing workshops and technology days to disseminate the knowledge across the company. In addition, the above best practices, OPNFV is an open source community that can help you with your NFV journey. In the next chapter, we will look at what OPNFV is.

Articles in this issue

view archives of White Papers - Understanding OPNFV