White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 130 of 144

Understanding OPNFV 130 teams, and to coordinate these requirements? mechanisms to coordinate between projects. Impact to Process While OPNFV does not manage a production NFV cloud, the development, test and release processes are closer to those of Web 2.0 companies than a traditional telecom operator. Decision-making and coordination between projects in OPNFV is governed by light-weight processes. For example, a proposal to create a new project is as simple as creating a Wiki page and presenting the project to the technical community after two weeks of initial review. If there are no objections, the proposal moves to the TSC for approval. At a more concrete level, the CI/CD process employed by OPNFV provides a great opportunity for traditional telecoms to be exposed to DevOps methodologies that are sometimes thought to be inapplicable to the telecom community. Users can learn how to retool their processes for successful NFV transformation by getting involved with OPNFV. Let's revisit the process readiness questionnaire from Chapter 2 and see how OPNFV helps: Question Readiness: 1-5 (1 = Not ready, 5 = Completely ready) Why? Can you imagine an intern pushing a change to a production network on their first day at work? (Etsy requires their interns to do so) 4 OPNFV does not have a CD pipeline yet, but an intern could submit a patch for CI on their first day. 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.) N/A Not applicable.

Articles in this issue

view archives of White Papers - Understanding OPNFV