Introduc)on  to  OpenDaylight    

David  Meyer  

CTO  and  Chief  Scien)st,  Brocade    Director,  Advanced  Technology  Center,  University  of  Oregon  

NANOG  58  New  Orleans,  Louisiana  

Agenda  

•  OpenDaylight  intro  

•  OpenDaylight  architecture  overview  

•  GeFng  involved  in  the  OpenDaylight  Project  

What  is  OpenDaylight?  

•  OpenDaylight  is  an  open  source  project  under  the  Linux  Founda)on  with  the  mutual  goal  of  furthering  the  adop)on  and  evolu)on  of  SDN  through  the  crea)on  of  a  common  industry  supported  framework.    

•  Tiered  Membership  –  Pla)num,  Gold,  Silver  –  Pla)num:  Cisco,  Brocade,  Juniper,  Citrix,  Ericsson,  IBM,  MicrosoT,  redhat  

OpenDaylight  goals    Code:  To  create  a  robust,  extensible,  open  

source  code  base  that  covers  the  major  common  components  required  to  build  an  SDN  solu)on  

  Acceptance:  To  get  broad  industry  acceptance  amongst  vendors  and  users  

  Community:  To  have  a  thriving  and  growing  technical  community  contribu)ng  to  the  code  base,  using  the  code  in  commercial  products,    and  adding  value  above,  below  and  around  

  Key  Principles:    Open,  transparent,  fair  

  A  wide  array  of  technologies  contributed  by  leading  companies  and  developers  

  Open  Source:  Any  developer  can  contribute  code  as  an  individual  

  Robust  framework/plaXorm  for  new  apps  and  tools  

  Eclipse  Public  License  (EPL)  

  So  what  is  the  ODP  architecture?  

OpenDaylight  code  

OpenDaylight  SDN  plaXorm  Architectural    Framework  

integration network applications, orchestration, and services

OpenFlow other std. protocols (ONF, IETF, …)

base network service functions

GUI

controller platform

extensions / addn’l svcs

vendor-specific

interfaces

southbound interfaces & protocol plugins

OpenDaylight APIs (REST)

virtual network manager

data plane interfaces and enhancements

(virtual switches, physical device interfaces)

service abstraction layer (plug-in mgr., capability abstractions, …)

1.0 1.3 SAN

(SMI-S)

topology mgr

stats mgr

switch / device

mgr L4-L7 service

manager fwding

multi-tenant virtual

networks

L4-L7 service

abstractions

storage services

OpenStack Quantum CloudStack oVirt …  CLI

hw-independent interfaces and data models

virtual forwarding

enhancements

Open switch

API

inter-controller com

m

…  

GeFng  started  with  OpenDaylight  •  Developer  documenta)on:    wiki.opendaylight.org  

–  list  of  current  projects  in  various  states  –  links  to  documenta)on  on  current  projects,  e.g.,  how  to  get/build  code,  architecture,  etc.  

–  informa)on  on  proposing  new  projects  for  OpenDaylight  

7   OpenDaylight  |  ONS  Developer  Breakout  

GeFng  involved  in  OpenDaylight  

•  Open  mailing  lists:    lists.opendaylight.org    – discussion  groups  on  specific  projects  – cross-­‐project  discussions  – announcements  

8   OpenDaylight  |  ONS  Developer  Breakout  

OpenDaylight  governance  –  10K  view  

•  Bylaws:  hdp://www.opendaylight.org/project/bylaws  

•  ODP  Board  of  Directors  will  manage  business  leadership  for  OpenDaylight  including  governance,  marke)ng  and  opera)onal  decisions  –  Ini)al  BOD  populated  by  Pla)num  members  +  1  gold  +  1  silver  

•  ODP  Technical  Steering  Commi6ee  sets  technical  direc)on  –  TSC  provides  technical  leadership  for  OpenDaylight  –  TSC  members  are  elected  and  is  comprised  of  developers  and  project  leaders  

•  Ini)ally  seeded  with  Pla)num  member  representa)ves  –  TSC  chair  ex-­‐officio  member  of  the  Board  –  TSC  chair  elected  annually  with  no  term  limits  

•  Importantly:  OpenDaylight  is  open  to  anyone.    In  par)cular  –  Anyone  can  develop  and  contribute  code  –  Anyone  get  elected  to  the  Technical  Steering  Commidee  –  Anyone  can  get  elected  to  the  Board  –  Anyone  can    help  steer  a  project  forward  in  any  number  of  ways  

A  Lidle  More  on  the  TSC  

•  Technical  direc)on  set  by  the  Technical  Steering  Commidee  –  Responsible  for  maintaining  plaXorm  codebase  –  Sets  release  train  scope  and  schedule  

•  TSC  membership  –  Ini)alized  with  representa)ves  from  pla)num  member  companies  –  Will  evolve  to  be  comprised  of  core  project  leads  and  community  representa)ves  

•  TSC  mee)ngs  and  mailing  list  are  open  to  the  community  –  See  lists.opendaylight.org  to  subscribe  to  the  TSC  mailing  list  –  Mee)ngs  currently  Thursdays  at  1000  PDT  

•  Dial  in  informa)on:  hdps://wiki.opendaylight.org/view/TSC:Main  

–  Minutes  •  All  decisions  documented  and  recorded,  posted  on  public  web  site  

•  Technical  work  stream  calls  –  hdps://wiki.opendaylight.org/view/Tech_Work_Stream:Main  

Thanks!