Exploiting Cloud Technologies in Networks: NFV and SDN. Andy Reid and Peter Willis BT Research and Innovation

Transcription

1 Exploiting Cloud Technologies in Networks: NFV and SDN Andy Reid and Peter Willis BT Research and Innovation

2 Clarifying what we mean by: SDN Separation of control plane logic/processing data plane header look up and forwarding Motivation Development of new control protocols without changing hardware Centralised control and optimisation of network capacity Improved scalability for datacentre networking NFV Separation of Software defining network function logic Generic processor based hardware Motivation Speed and operational efficiency in deploying new services Exploitation of commodity components from Cloud technologies Decoupling development/supply of network functions from development/supply of hardware

3 Issue 1: What is the operational model for a development to a network? Changing Engine Oil Hip Replacement Surgery The car and engine are stopped and idle during the operation. Context of operation can be broad full service, engine replacement Taking longer has little or no consequence for the car and engine Carried out as a matter of routine The patient must remain alive during the operation Scope of operation is precise and focussed Time is limited. Only attempted if really needed Upgrading a network is like changing the engine oil while driving along

4 Issue 2: Viability of network development by scale and scope Example Scope Dimensions Number services Range of legacy technologies Number of vendors Network interconnect OSS interworking Wide scope Complex but small Impractical too complex do not fit surgery model Narrow scope Not worthwhile Big but simple Small scale Large scale

5 Ground rules for introduction of SDN and NFV (or anything else) into a network 1. Select a (small) part of the network for initial upgrade Make use of new service introduction Make use of growth capacity increments 2. Interwork with existing parts of the network as necessary This includes OSS/BSS Selection in (1) which minimises (2) is good 3. Architect the development so that it fits with the longer term development roadmap Development only to meet initial need is normally bad Development with universal ambition is normally bad Business justification for the longer term fit is often not easy to quantify This is often the hardest step 4. It s a marathon made up from a large number of short sprints A continuous relay race

6 What is Network functions Virtualisation? Competitive & Innovative Ecosystem Message Router CDN Session Border Controller WAN Acceleration Network functions Virtualisation Approach Independent Software Vendors DPI Firewall Carrier Grade NAT Tester/QoE monitor Orchestrated, automatic & remote install. SGSN/GGSN PE Router BRAS Fragmented non-commodity hardware. Physical install per appliance per site. Hardware development large barrier to entry for new vendors constraining innovation & competition. Classical Network Appliance Approach Its a bit like... Radio Network Controller Standard High Volume x86 Servers Standard High Volume Storage Standard High Volume Ethernet Switches Adding Machine Typewriter Printing Press Fax Machine

7 The Story So Far: What happened last year... Standard high volume servers have sufficient packet processing performance to cost effectively virtualise network appliances. The hypervisor need not be a bottleneck. LINUX need not be a bottleneck. TCO advantages are scenario specific but expect significant benefits. Plus a significant reduction in energy consumption.

8 NfV traditional NFV Example: consolidation of customer premises equipment developer hardware & software bundle BT config & mgmt BT managed service IP697 Protects private network from Internet-based threats M-3050 Comprehensive IPS proactively detects/ prevents worms, data leaks & attacks Proxy SG 600 Checks web content for malware & controls insecure channels (e.g. IM) Sentry Steelhead nano engine Monitors network devices to collect/ analyse/ filter routine or false alerts Accelerates transfers by removing unnecessary or repeated data Prioritises apps and manages less important traffic over the Internet hypervisor 1 x 2 Unit rackmount server +

9 Orchestration and Relationship with SDN Orchestration and Infrastructure Network primary communications parameters are network addresses and services between addresses Orchestration only sees infrastructure network service not network detail Common model for any infrastructure network technology, not just SDN NVF Orchestration Hypervisor & Compute Domain Infrastructure Network Domain Infrastructure Network Service Hypervisor & Compute Domain

10 Inherent Provision for Evolutionary Interworking Interworking between software and hardware planes SDN NFV Interworking between vendors SDN NFV Interworking between networks SDN NFV Interworking with existing OSS SDN NFV

11 The scope of possible SDN development plans Plan A SDN only Plan B NFV+SDN Plan C?

12 THANK YOU