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.

Summit 16: Keynote: HPE Presentation- Transforming Communication Service Provider Networks via Open Source and Open Ecosystems

1,859 views

Published on

If Communications Service Providers are to achieve the Nirvana of networks composed of interoperable, “best-of-breed” components, and if they want the journey to get there to be a relatively short one, then engaging vendors who can use open source effectively is crucial. HPE is using open source and leveraging its partner ecosystem of 80+ companies, to build its NFV and SDN platforms and solutions. This talk will describe what HPE is doing with open source, open ecosystems and CSPs to accelerate the successful transformation of service provider networks.

Prodip Sen, HPE, CTO of the Network Functions Virtualization (NFV)

Published in: Technology
  • Be the first to comment

Summit 16: Keynote: HPE Presentation- Transforming Communication Service Provider Networks via Open Source and Open Ecosystems

  1. 1. Open Transformation Transforming Service Provider Networks via Open Source and Open Ecosystems Prodip Sen CTO, NFV HPE June 22, 2016
  2. 2. Convergence of initiatives is accelerating transformation 2013 2016 Open innovation Software-defined networking Network functions virtualization Open innovation Software-defined networking Network functions virtualization 2
  3. 3. Open Development Open Source 3
  4. 4. Why Open Source 4 Interoperable software components Needs Challenges Choose from “best-of-breed” Shorten the journey Avoid duplication of efforts Produce usable code Interoperability and standardization Encourage diversity and innovation Changing mindsets
  5. 5. Myths and realities of Open Source 5 Open source code is unreliable Myths Realities Long development times Hijacked by special interests Large community of developers Faster bug-fixing Practical and innovative ideas Stable code after few iterations Automatic interoperability
  6. 6. Open Source projects driving NFV implementations OSS / BSS Open Source VNFs NFV ISG Standards Open Source 6
  7. 7. Open Resource Dilemma Tacker Astara Blazer Congress Mistral Senlin Monasca Stadium Neutron Doctor Promise Multisite ONOS CopperParser Functest SFC SDN-VPN OpenSAF DIDM Infra Utilities Lisp Flow Mapping Discovery Copper Network Intent Composition Affinity Metadata Svc SNMP UNI Mgr Plugin 7 NFV Developers/ Solution Builders − Too many (sub) projects − Limited ecosystem resources − Where should I start? − Is there duplication? Issues
  8. 8. However, there is harmony in the chaos Multisite Neutron Heat Infrastructure compute storagenetwork KVMCeph Virtual compute Virtual storage Virtual network VNF1 VNF2 VNF3 OVS TOSCA NFV profile Kingbird HA SDN VPN Promise (Resource Mgmt) Blazar Parser NetReady Models Functest Doctor VIM SFC Monitoring NetVirt OVS DB NFVI MANO Network DC, DCI ODL controller VNFs OPNFV OPENSTACK ODL Senlin Federation Clustering Pharos 8 Tacker NFVO Domino Parser Nova Ceilo meter Monasca Others …..
  9. 9. Open Development Open Ecosystems 9
  10. 10. Open Source to deployable solutions à There are chasms to cross 10 Open StackOpen Helion OpenStack Carrier Grade Stack Carrier Grade Features Stable OS Projects Deployable NFV Systems + Solutions are not born multi-vendor. They require integration of components and systems Solutions cannot be built solely on Open Source NFV Solutions
  11. 11. And expectations to meet ... 11 Open Source Vendor HW/SW Vendor HW/SW Open Source Service Providers Vendors CSP Expectations Vendor View ?
  12. 12. Open ecosystems emerging to bridge the gap… 12 Intel® Network Builders program AT&T Domain 2.0 …. to build solutions and meet requirements. However, the learnings have mostly been one way: Open Source à Ecosystem
  13. 13. HPE OpenNFV Program Providing an open, proven, and innovative environment for NFV transformation
  14. 14. HPE OpenNFV Partner ecosystem Apps, CPE, OTT, Security vEPC, vIMS, LTE, RAN Signaling, Testing, Management Technology Partners 14
  15. 15. HPE NFV Partnership Ecosystem Foundation Architecture OpenNFV Partner Program OpenNFV Labs Proof Of Concepts Technology Partners – Technology integration and support for HPE OpenNFV Stack – Long-term partnership focused on integration testing of NFV architecture within OpenNFV labs Application Partners – Validation and characterization testing on ETSI-compliant HPE OpenNFV Reference Architecture – Catalog of tested partner VNFs/applications Services Partners – Leverages and supports the HPE OpenNFV reference architecture and product portfolio as a platform to align their industry strengths and offerings 9 70+ 15 +
  16. 16. Bridging the Gap
  17. 17. Bringing Ecosystem Learnings back to the Community 17 Onboarding Common onboarding OPNFV and OpenNFV SolutionValidation Beyond pure onboarding Detailed VNF feature validation Expanding Functest Publishing ……… DevtoDeploy ……… • HPE is announcing that our OpenNFV Labs to participate in the OPNFV Pharos project • The Houston location of our HPE OpenNFV Lab is now part of Pharos • HPE will institute automated processes allowing HPE OpenNFV partners to verify that they can run on the OPNFV platform. June 2016
  18. 18. Bridging the gap .. 18 OpenNFV onboarding tool OPNFV Workflow (ETSI Standard à Parser à Hot à Functest) OpenNFV Workflow (ETSI Adapted à OBTool à Hot à Test) Tested on Pharos Infrastructure Tested on OpenNFV infrastructure ready ready … Demo at HPE booth
  19. 19. HPE’s approach to NFV Bridge IT & CSP Networks Accelerate NFV deployments With a rich partner ecosystem, reference architecture and global network of labs Bridge current to the new With innovative hybrid orchestration solutions to manage and operate current and new networks 19 With expertise in virtualization and open source cloud solutions and long Telco heritage Creating Open Solutions in an Open Ecosystem Delivering Business Outcomes
  20. 20. Join us to bridge the chasms ü Address the needs of solutions in addition to components ü Bridge the gap between open source and ecosystems üEnsure consistency and interoperability 20
  21. 21. Thank you 21
  22. 22. Thank you 22

×