Upgrade to Pro — share decks privately, control downloads, hide ads and more …

ONOS Summit: NTT (Service Provider Perspective)

ONOS Project
December 09, 2014

ONOS Summit: NTT (Service Provider Perspective)

Talk by NTT at ONOS Summit on Dec 9th, 2014
Presented by: Dai Kashiwa

ONOS Project

December 09, 2014
Tweet

More Decks by ONOS Project

Other Decks in Technology

Transcript

  1. Evolution of SDN services in NTT Communications and Our Activities

    on Transport SDN 2014.12.9   NTT  Communica2ons ONOS  summit  2014
  2. 3 Step1: Enterprise Cloud Services First private cloud in the

    world adopting virtualized network technologies launched in June 2012 ü  Automatic configuration using SDN technologies ü  On-demand provisioning through customer portal ü  Direct connection to VPN SDN  tech.  deployed  to   inside  of  DC Germany  (Mar.  2014)   UK  (Feb.  2013)   Australia (May.  2013)   India (2015)   China     [Hong  Kong]   (Jun.  2012)   Spain (Mar.  2015)   France (Mar.  2015)   US     [2  locaJons]   (Feb.  2013)   China    [Shanghai]   (2015)    Japan     [2  locaJons]   (Jun.  2012)   Singapore  (Feb.  2013)   Malaysia  (Mar.  2013)   Thailand  (Mar.  2013)   +[1  locaJon]           (Dec.  2014)  
  3. 4 Step2: Between Enterprise Clouds Dynamic virtualized network between DCs

    ü  Customers can control network resources ü  Typical Use Case: On demand global data backup OFSW* OFSW* Country A Virtualized Network between Data Centers Enterprise Cloud Enterprise Cloud Customer Portal * OFSW : OpenFlow Switch Data center in Data center in Country B Network Controller SDN  tech.  deployed  to   b/w  DCs
  4. VLAN-MPLS gateway eBGP Open Flow VLAN MPLS API SDN Controller

    ü  Configurations of DC and VPN are exchanged and mapped each other at the gateway automatically (VLAN<->MPLS) ü  Delivery time: Several days -> hours 5 Data centre Network MPLS-VPN Step3: Cloud-VPN inter-conn automation   Flow  tables SDN  tech.  deployed  to   b/w  DC  and  WAN
  5. ADP ADP SW ü  Realize flexible connections without changing the

    current physical network In-house Locations Overlay Function Newly-launched Overseas Locations Internet Company A’s System : Connection Route : Software Virtualize Network Customer Portal Network Controller ADP SW : Adaptor 6 (Company B) Locations acquired by M&A Arcstar Universal One Other VPN Step4: Virtualized Overlay Network SDN  tech.  deployed  to   overlay  NW  on  WAN
  6. 7 Network Internet : Connection route Customer Portal Realize functions

    of WA and FW over network Network Controller Customer’s system Step5: Network Functions Virtualization ü  Virtualize network appliances on LAN with software over Arcstar Universal One. After NFV service SDN  tech.  deployed  to   NFV
  7. 8 Step6: Transport SDN Cloud Connectivity  Domain  -‐‑‒  Physical Core

     Domain  -‐‑‒  OTN Aggregation  Domain  -‐‑‒  MPLS DC  Domain  -‐‑‒  VLAN •  SDN technology deployment to carrier core networks. •  Aims to realization of “Carrier cloud”: high quality integrated cloud/network services under •  Multi-Domain (Access, Aggregation, Core,…) •  Multi-Layer (Fiber, WDM, OTN, MPLS,…) •  Multi-Vendor ɹ network environment Integrated  control  of  multi-‐‑‒domain/layer/ vendor  transport  networks SDN  tech.  deployed  to   core  NW  of  WAN
  8. Cloud  controller   System   Collabora2on   API BSS  /OSS

    Service  NW   Controller OpenFlow     Controller NFV  Controler Compute  Recource   Controller   Customer/   Product   management Automated   resources   mashup Virtual   resources   control SDN  controller AP  controller Management Framework for SDN Services To  develop  services  rapidly  and  expansively,  integrated  management   framework  is  needed.   <Goals>   ü  Rapid  service  development  using  mul2vendor  S/W  and  H/W   ü  Lean  S/W  development  avoiding  redundant  development   Orchestrator 9 Next   Slide should  be     Open  APIs Various  Ctrler  will   be  deployed  as   technology   progresses Strage    Recource   Controller   Transport  NW   Controller
  9. 11 Use Case1: Integrated Network Visualization •  Multi-layer/Multi-domain/Multi-vender NWs are

    managed integrated through one-view. •  Operators can easily grasp whole network situations by virtualization and abstraction of network resources. Ether  domain Operator MPLS  domain Operator WDM  domain Operator Per  layer/domain/vendor  view Integrated  “one-‐‑‒view” Traditional  Operation ToBe  Operation
  10. 12 Use Case 2: Multi-layer/domain Optimal Path Allocation Use Case

    3: Multi-domain Auto Recovery •  Optimal end-to-end path allocation among multi-layer/domain networks. •  Discover candidate paths automatically •  Select a path based on operator’s policy •  Auto recovery of all end-to-end paths beyond domains Traditional  Operation ToBe  Operation Per  layer/domain/vendor   Operation Overall  Optimization  Operation Optimal  paths   per  domain End-‐‑‒to-‐‑‒end   optimal  path   allocation Failures   between   domains  must   be  recovered   manually Auto  recovery   beyond   domains  on   end-‐‑‒to-‐‑‒end   basis
  11. 13 Transport SDN Controller Architecture Cloud Connectivity  Domain  -‐‑‒  Physical

    Admin & Management Network  Orchestrator Visualization Resource Slicing Path Computation Failure Handling MPLS-‐‑‒TP Adaptor OpenFlow Adaptor Optical  SW Adaptor GMPLS Adaptor Core  Domain  -‐‑‒  OTN Aggregation  Domain  -‐‑‒  MPLS DC  Domain  -‐‑‒  VLAN Cloud  controller   BSS  /OSS Service  NW   Controller OpenFlow     Controller NFV  Controler Compute   Recource   Controller   SDN  controller AP  controller Orchestrator Next   Slide Strage     Recource   Controller   Transport  NW   Controller Applications  of   operation   automation   Management   functions Network  OS  to   control   transport   networks Adaptors  to   various   protocols
  12. Our Expectations for ONOS 14 n  Technology  development •  “Carrier-‐‑‒grade”

     functions  such  as… ü  High  Availability ü  Scalability ü  High  performance n  Implementation •  Production  level  (?)  codes  (not  just  a  prototype)   written  by  worldwide  software  developers n  Open  Innovation •  Excellent  ideas  for  Transport  SDN •  Other  cutting  edge  use  cases  
  13. 16 ü  Automatic configuration ü  Quick delivery ü  On-demand provisioning

    through customer portal Effectiveness of SDN technologies Servers Data Centre VPN, etc. Manual Configuration FW LB L2SW L2SW <Before> Virtual Servers VPN, etc. Data Centre Network Controller enables immediate changes Automatic Configuration Virtualized Network OFSW OFSW FW LB * * Network Controller * OFSW: OpenFlow Switch <After> Customer Portal
  14. 17 OFS OpenFlow   Controller OFS Network   Controller Plug-­‐in

      Agent OpenFlow   Controller OFS OFS NW  APP1 Open  API   (Neutron  etc) Com   App1 【As  Is】 Plugin 【To  Be】 Orchestrator NW  APP2 Open  API   (Neutron  etc) Com   App2 Standard  Open   API   Integrated  plaXorm   to  modify/  add   func2ons Network   Controller OFS   Service  1 Service  2 Service  3 SDN Controller Architecture Controller1       Controller2       Controller3       API API SDN  Controller  PlaQorm   We  started  stepping  forward  to  deploying  integrated  SDN  controller  plaXorm   from  current  “product  lock-­‐in”  controllers.   ü  Standard  and  open  northband  I/Fs  (e.g.  neutron  APIs)   ü  Easy  plug-­‐in  of  emerging  service/  opera2on  func2ons