White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 41 of 144

Understanding OPNFV 41 ticket, or handoff that doesn't truly add value must be eliminated. To goal is to move away from processes organized around physical network functions to a cloud-based approach. Process readiness questionnaire: Question Readiness: 1-5 (1 = Not ready, 5 = Completely ready) Can you imagine an intern pushing an update to a service in production on their first day at work? (Another imperfect analogy, but in the web world Etsy requires their interns to push a change to their live site on their first day at work) Could you imagine an engineer experimenting with a new feature on the production network on 1% of your user-base without seeking any permission? (Twitter allows this.) Do you use Agile methodology? Is the methodology truly Agile or is it waterscrumfall (that is, a hybrid of waterfall and Agile)? Can your finance team approve hardware purchases not allocated to a specific cost center, but for an aggregate NFV cloud? Can your compliance, asset inventory, and security teams deal with a dynamic virtual infrastructure? Impact to Technology The impact of technology is perhaps the clearest. The organization must be able to absorb these new technologies and use them effectively. Technology readiness questionnaire: Question Readiness: 1-5 (1 = Not ready, 5 = Completely ready) Do you have a plan for what NFV software needs to be cloud

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV