The Future of Networks is Open...Source
8 likes1,941 views
1. The document discusses key trends impacting future networks including softwarization, cloudification, network functions virtualization, modularization, and open source. 2. It notes that over 80% of telco operators demand or prefer open systems for their networks and over 95% see open source as a positive attribute for NFV solutions. 3. The document outlines how open source is playing a role at each layer of future networks from the infrastructure to orchestration to the OSS/BSS and discusses the needs, facts, and status at each layer.
The Future of Networks is Open...Source
- 1. François Duthilleul EMEA Solution Architect, Telco Technology Office fduthill@redhat.com THE FUTURE OF NETWORKS IS OPEN...SOURCE !
- 2. TRENDS IMPACTING THE FUTURE NETWORK Softwarization & HW Commoditization Cloudification NFV as first step NFC* Modularization Microservices Open Source IT & Network Convergence Programmability SDx Agility (reuse, tools, process)Telco is not special * Network Functions Containerization / Cloudification
- 3. WHY OPEN SOURCE FOR FUTURE NETWORKS ? 83% Of Telco operators demand or prefer open systems for their networks 95% Of Telco operators see open source as a positive attribute for NFV solutions Faster innovation Choice of vendors Powerful think-tank
- 4. OPEN SOURCE IN THE FUTURE NETWORKS
- 5. OPEN SOURCE AT EACH LAYER Source: First reference NFV architecture - now replaced by the NFV-MANO architectural framework with reference points in ETSI GS NFV-MAN 001 V1.1.1 (2014-12) OPNFV works (a.o.) on a NFV reference implementation integrating open source components covering the NFVI and MANO layers ETSI and The Linux Foundation are working on Open Source implementation of MANO Vendors are modernizing their products (OSS, BSS, NF, EM) using open source technologies
- 6. 1. BUILDING A SOLID NFV FOUNDATION THE NEEDS - Provides a flexible and massively scalable IaaS foundation - Meets carrier expectations in terms of NFV readiness: performance, availability, security, manageability & lifecycle - Covers all use cases including most challenging like cRAN THE FACTS - OpenStack as de-facto standard for VIM - Making the foundation NFV ready has involved more open source communities than just OpenStack - the OS matters ! - Enhanced Platform Awareness (EPA) for performance - Open source projects for manageability, security, LCM,... THE STATUS - OpenStack is part in each NEP offering - Many commercial deployments on-going
- 7. 2. SOFTWARE DEFINED EVERYTHING (SDx) THE NEEDS - HW agnosticity, Use of commodity HW - Lower cost of ownership - Horizontal scalability of each components - Distributed storage, distributed network THE FACTS - Software Defined Storage (SDS) and Software Defined Network (SDN) are being more and more used THE STATUS - Ceph part of OpenStack-based deployments and default backend - Some SDN commercial solutions based on ODL - OpenDayLight part of OPNFV Danube release
- 8. 3. ORCHESTRATING THE NETWORK SERVICE LIFECYCLE THE NEEDS - Orchestrator is required to meet the NFV promise of full flexibility (resource optimization & meeting SLA) THE FACTS - Lots of Open Source projects to cover the MANO stack and first projects consolidation with ONAP - No convergence yet on the descriptors / APIs (WIP) THE STATUS - Too many open source projects - Further consolidation to happen - Orchestration stack provided by vendors are not fully open source but might use some
- 9. 4. TOWARDS CLOUD NATIVE NETWORK FUNCTIONS THE NEEDS - Independent scaling - Placement of workload / Footprint optimization (better usage) - Evolution to stateless NFs and to G-VNFM (vs S-VNFM) THE FACTS - Limited set of VNFs are containerized mostly related to Gi-LAN, CPE - Container will have to co-exist with VMs - Optimized OS for containers are available THE STATUS - On-going PoCs with first cloud native NFs - WIP in OPNFV, OpenStack, ETSI e.g. 3GPP service based architecture for 5G core network control plane
- 10. 5. DEVOPS-BASED SERVICE DELIVERY THE NEEDS - Automated service activation (DevOps style) - Customization through configuration - Tools independent of the products to be managed - Bridge the gap between Physical & Virtual THE FACTS - Powerful open source configuration management tools exist - Support of NETCONF makes possible to manage PNFs THE STATUS - Tools are used already for CI/CT/CD - IT is more used to this way of working than Telcos - Automation / remediation is used for security compliance
- 11. 6. MODERNIZING THE OSS/BSS THE NEEDS - Increase OSS/BSS automation to deal with dynamic network services - Manage the old and the new world - PNFs & VNFs - SW Modernization: cloud native, scalability, configuration management,... THE FACTS - Vendors are adopting open source technologies for modernizing their OSS/BSS products: API management, container platform, automation,... "For Digital Service Providers to realize the full benefits of virtualizing network functions a flexible modular micro-services approach that relies on the automation and deployment of cloud native services into hybrid IaaS environments is required. The innovation driven by Red Hat unlocks the value from the open source community which allows us to drive the future Telco Cloud assurance market." "The move to next generation cloud-deployed BSS/OSS is being driven by the innovations from the open source community - specifically open API management, container utilisation and automation of the PaaS layer. Partnering with companies such as Red Hat is key to the success of our SaaS billing and charging solution."
- 12. 7. THE INCREASING ROLE OF API THE NEEDS - Open up the network to create innovative network services - Monetizing the network by exposing APIs - Scaling, securing and managing the APIs will be key THE FACTS - Digital transformation is driving architecture towards API - TM Forum is a good example of this evolution - Network slicing is also driving towards exposing Network Functions e.g. 5G Network Exposure Function (NEF) THE STATUS - Many open source API management projects exist already or are in the process to be fully open sourced
- 13. 8. OPEN SOURCING THE USE CASE THE NEEDS - Build the future network maximizing the use of Open Source Software (and Hardware) - Revisiting the SW business models THE FACTS - NFV use cases can be built using open source software including for the NF itself - Example: Eclipse IoT foundation providing open source technology to build IoT devices, GW and cloud platforms ! THE STATUS - Increasing amount of collaborative projects some driven by web giants like FaceBook (TIP, OCP,...) - Still a long way to go but a clear direction... ...
- 14. FROM OPEN SOURCE TO PRODUCTION READY NETWORKS
- 15. FROM OPEN SOURCE TO ENTERPRISE INTEGRATE We participate in and create community powered upstream projects We integrate upstream projects, fostering open community platforms We commercialize these platforms together with a rich ecosystem of services and certifications INTEGRATE We integrate upstream projects, fostering open community platforms We commercialize these platforms together with a rich ecosystem of services and certifications STABILIZE STABILIZE
- 16. KEY TAKEAWAYS
- 17. KEY TAKEAWAYS Open Source is at the core of the Future Networks…. ….from the infrastructure to the OSS/BSS ! Vendors are already modernizing their products leveraging open source Open Source is a product development model and… ...new business models might emerge in future as a result Open Source driving NFV adoption is just the first step ! Don’t miss out the discussion...