White Papers

Understanding OPNFV

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

Contents of this Issue

Navigation

Page 131 of 144

Understanding OPNFV 131 Do you use Agile methodology? Is the methodology truly Agile or is it waterscrumfall (that is, a hybrid of waterfall and Agile)? 5 OPNFV methodology is fully agile, driven by epics and user stories in JIRA. Can your finance team deal with hardware purchases not allocated to a specific cost center, but for an aggregate NFV cloud? N/A Not applicable. Can your compliance, asset inventory, and security teams deal with a dynamic virtual infrastructure? N/A Not applicable. Impact to Technology The primary objective of the OPNFV project is to give users open source technology they can use and tailor for their purposes. Over and above the benefits from the Tangible Benefits section above, by getting involved, users can also gain valuable experience with technologies required for a successful NFV transformation. Let's revisit the technology readiness questionnaire from Chapter 2 and see how OPNFV helps: Question Readiness: 1-5 (1 = Not ready, 5 = Completely ready) Why? Are you ready for cloud native applications and microservices? 5 OPNFV uses OpenStack as a VIM, which is perfectly suited for cloud native applications. Would your organization be receptive to the principles of Chaos Engineering? 4 While there isn't a formal Chaos Engineering project in OPNFV, the technical community culture is

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV