Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why NFV and Digital Transformation Projects Fail!

270 views

Published on

The whitepaper
https://cloudify.co/whitepapers/why-nfv-transformation-projects-fail-whitepaper

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Why NFV and Digital Transformation Projects Fail!

  1. 1. Cloudify: Why NFV and Digital Transformation Projects Fail!
  2. 2. “Transforming your decision making with technology - utilizing new sources of innovation and creativity to enhance experiences and improve financial performance”. Digital Transformation (DX) Defined IDC : Designing Tomorrow
  3. 3. 55%of network ops see agile and real time cross-business collaboration as a key priority "Enterprises are adopting new IT delivery models and applications that are imposing fundamental network changes from device access to core." Networking Plays Crucial Role in DX Source: Gartner's' 2017 "Strategic Roadmap for Networking"
  4. 4. CSP Approach to NFV and DX With both IT and networks embracing cloud, there is a strong case for merging IT and network functions. "IT transformation has proven difficult because most CSPs can’t afford to simply rip out and replace all their old systems. As such, they try to work with suppliers to improve existing systems, but there is little incentive for suppliers when their revenue streams are at stake" Source: TMForum Digital Transformation report, SDxCentral report
  5. 5. Key Technology Challenges
  6. 6. CSP Approach to NFV and DX How To Fix It?
  7. 7. Agile Transformation vs Big Bang
  8. 8. Telstra SEN Project / SD-Core • Dynamically deploy WAN and NFV components • Enables telcos to offer consumption based VNF value-added-services from edge compute via metro-Ethernet networks • Network and NFV service definitions defined in blueprints which are instantiated via orchestration • NFV-I networking, SFC and TOR options relative to specific vendors and design Utilization Stats Confidential
  9. 9. Open vCPE Open vCPE Demo Customer Case Study
  10. 10. A Pragmatic Approach to Standard Innovation VS Adoption Traditional Methods of driving Standards are not agile enough to meet the new speed of innovation <> adoption
  11. 11. TMForum: Open source and the future of OSS Open Source Drive New Standards The Only Constant Is change
  12. 12. TMForum: Open source and the future of OSS 2018-20 Cloud Native? Standard Led ? Open Source Led The Future of OSS - 2018-20?
  13. 13. Intent Based Network provisioning and configuration Domain / Edge Orchestrator VOLTHA Edge management Microservices Domain / Edge Orchestrator Central Orchestration / Management Physical Device Physical Device Bare-Metal Bare-Metal Cloud Native Edge Controller ● Virtualization of the control plane ● Kubernetes on Bare-Metal as Edge Platform ● ONAP as OSS/BSS ● VOLTHA management pod packaged microservices ● Generic architecture that can fit any access device management. A Pragmatic Approach to Standards Leveraging Cloud Native Stack to model and drive new network services Source: VOLTHA, SEBA, OSAM and ONAP with Cloudify for End-to-End Provisioning and Lifecycle Management of Access Devices
  14. 14. Top Down vs Bottom Up approach Simple Embeddable VNFM
  15. 15. A Mix of New & Traditional Vendors
  16. 16. Which approach gets you faster to the point where you see return from DX ? Cloud / NFV Transformation Approaches Agility and Cost Efficiency (Degree of Cloud Nativeness ) Time to Value (relative to transformation time) Fast Slow Serverless Cloud Native Platform (Kubernetes, OpenShift) Edge as Cloud Weeks Months Years Run on a Cloud Automate and Run on a Cloud MicroService Architecture vs. Monolithic Serverless Infrastructure as Code Automation-First Approach Lift & Shift Automation first approach put multiple transformation approaches together
  17. 17. Keith Rothschild Principal Engineer at Cox Communications ● Do you see virtualization & automation tightly coupled ? ● How does the move to cloud effect the current architecture ? ● What are the culture challenges ? ● How do you see the role of standards in driving the future of NFV? Q&A
  18. 18. The Future of Networking: SD-WAN Vision “it will be applications-on-demand (user) centric and NOT box (router) centric” Source: How SD-WAN will make the cloud much, much bigger
  19. 19. The Future of Networking: Intent Based Gartner: “the next big thing on the networking horizon promises to be …. wait for it … Intent-based Networking.” Composite Service Blueprint
  20. 20. The Future of Networking: Serverless Edge Reference: 5G To The Edge With AT&T: A Fully Orchestrated Open Source Stack
  21. 21. Summary: Lessons for successful NFV Transformation ● Agile transformation (Focus on time to value) vs “Big Bang” transformation (Focus on standard compliance) ● Pragmatic approach to standard - interoperability vs compliance ● Top Down vs Bottom Up approach ● A Mix new vendors alongside traditional vendors - Best of breed approach ● Smoothing the Cloud Native technology transformation
  22. 22. Thank You
  23. 23. ● Cloudify approach for supporting ETSI and other standards ● ETSI NFV MANO Components Mapping to Cloudify ● Why 70% of NFV and Digital Transformation Projects Fail?! ● Driving Open Standards in a Fragmented Networking Landscape ● What is the best NFV Orchestration platform? A review of OSM, Open-O, CORD, and Cloudify ● Is Networking becoming cool again ● Declarative networking ● VOLTHA, SEBA, OSAM and ONAP with Cloudify for End-to-End Provisioning and Lifecycle Management of Access Devices ● Telstra NFV/SDN Evolution Project ● Lumina SD-Core & NFV Service Chaining ● Linux Foundation Shifts Network Infrastructure to Kubernetes ● Cloudify Customers Use Cases References

×