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

ONOS Summit: ONOS Roadmap 2015

12ab1f737f33bf4ea2f59b0c5191b789?s=47 ONOS Project
December 09, 2014

ONOS Summit: ONOS Roadmap 2015

ONOS Roadmap at ONOS Summit 2015
Presented by: Prajakta Joshi, Director of Product, ONOS

12ab1f737f33bf4ea2f59b0c5191b789?s=128

ONOS Project

December 09, 2014
Tweet

More Decks by ONOS Project

Other Decks in Technology

Transcript

  1. Prajakta Joshi Director of Product, ONOS What’s  next  for  ONOS?

      [ROADMAP  2015]  
  2. “Avocet”  released  on  Dec  5th,  2014   Welcome  to  open

     source  ONOS!  
  3. Blackbird  release   May  Release   August  Release   November

     release   Nov   Sep   Aug   Jul   Jun   May   Mar   Feb   Jan’15   Dec’14   Apr   Oct   ONOS  Releases   •  Regular 3 month release cadence •  Named after birds in alphabetical order (Avocet, Blackbird…) •  Community release planning event at the start of the release cycle •  Everything tracked in JIRA (jira.onosproject.org) •  Agile development at ON.Lab + freedom to choose whatever process works for you UPCOMING  ONOS  RELEASES  
  4. 1 2 3 Blackbird  Release  (28th  Feb  2015)   • 

    RAFT  for  distributed  core   •  Define  metrics,  create  test  set-­‐up   •  Performance  assessment/op_miza_on   •  High  Availability   •  Fix  bugs  found  in  Avocet   •  Tes_ng  framework  improvements   •  Tes_ng  with  hardware   •  Avocet  Use  Cases-­‐  next  phase   •  Internet2  deployment   •  Iden_fy  requirements  for  new  use  cases,   POCs,  deployments   STABILITY   PERFORMANCE   USE  CASES/DEPLOYMENTS  
  5. COMMUNITY   POCs,   DEPLOYMENTS   USE  CASES   CORE

        PLATFORM   COMMUNITY   ROADMAP  -­‐  2015  
  6. ONOS  Distributed  Core   •  Scalable  strongly  consistent  data  store

      –  Move  from  Hazelcast  to  RAFT     •  Mastership   –  Move  from  Hazelcast  to  RAFT     •  Clustering                  -­‐  Migrate  out  of  Hazelcast.  Add  support  for  an  Accrual  failure                              detector  (such  as  Phi  Accrual  failure  detector)   •  Distributed  data  structures   -­‐  Distributed  queue  on  RAFT  –used  by  Intent  framework     for  distributed  execu_on  of    intents.   •  Metrics  and  monitoring   •  Overall  stability/performance  improvements   •  Geo-­‐distributed  ONOS  cluster(s)   Detailed  Roadmap  at:   h1ps://wiki.onosproject.org/display/ONOS/Roadmap+2015%3A+Distributed+Core  
  7. ONOS  Applica_on  Intent  Framework     •  Support  for  new

     types  of  Intents   •  Conflict  detec_on   •  Security   •  Batching   •  Introduce  a  more  generic/powerful                language  for  expressing  Intents                (Frene_c/Pyre_c)   •  Mechanism  to  compose  intents  within  or  across  applica_ons              (With  Jen  Rexford’s  team  +  Josh  Reich  from  AT&T)     Detailed  Roadmap  at:   h1ps://wiki.onosproject.org/display/ONOS/Roadmap+2015%3A+Intent+Framework  
  8. ONOS  Southbound   •  Null  Providers  (for  performance  benchmarks)  

    •  OVS-­‐DB  /  OF-­‐CONFIG  provider   •  Addi_ons  to  API   •  Addi_onal  OF  1.3  support  (driven  by  segment                  rou_ng  por_ng  to  ONOS  main)                -­‐  Group  table,  TTPs   •  Enable  vendors  to  write  southbound  providers   •  OpenVirtex  integra_on?         Detailed  2015  Roadmap  at:   h1ps://wiki.onosproject.org/display/ONOS/Roadmap+2015%3A+Southbound  
  9. Interes_ng  areas  on  the  agenda  for  2015   •  Geographically

     distributed  ONOS  cluster(s)   •  Mul_-­‐tenancy   –  Mul_ple  ways  of  suppor_ng  it   –  MT  aware  code  or  with  OpenVirtex  Layered  on  ONOS  Core  or  something  else?   –  MT  at  scale  for  Service  Provider  networks  =  how  many  tenants?   •  Openstack  Integra_on   •  IPv6  support   –  Not  just  IPv6-­‐aware  but  IPv6-­‐based  (  e.g.  look  closely  at  IPv6  flow  labels  for  SDN  use  cases)   •  Security   •  Mobility   •  Running  another  SDN  controller  and/or  another  controller’s  apps  on  ONOS.       DefiniMon  of  these  features  to  be  done  in  conjuncMon  with  service  providers  and  vendors.     Build  these  features  to  be  relevant  to  real  world  deployments.  
  10. COMMUNITY   POCs,   DEPLOYMENTS   USE  CASES   CORE

        PLATFORM   ROADMAP  -­‐  2015  
  11. ONOS-­‐  Avocet  Service  Provider  Use  Cases-­‐  Phase  2   Mobile

     customer Residen_al  customer Enterprise  customer Developed  with  ONF   Mul_layer  SDN  Control   SDN-­‐IP   Segment  Rou_ng   NFaaS  
  12. New  Use  Cases  under  explora_on   •  AT&T   • 

    Network  Func_ons  as  a  service  in  central  office  –  phase  2   •  SDN  in  Access  Networks-­‐  virtual  CPE,  white  boxes     •  Mul_layer  SDN  control  of  packet  and  op_cal  networks  –phase  2   •  Provisioning  automa_on  layer  (PAL)   •  Meta-­‐Tagging  and  Data  Temperature  PoC  (Cloud  Innova_on  Lab,  Dallas)   •  Adap_ve  Virtual  Probing   •  SDN-­‐IP  enhancements  for  service  provider  deployability   •  NTT     •  Packet  op_cal  (with  NEC)   •  Huawei   •  IP  RAN  use  case   •  OSS/BSS     * Statements here are forward looking and subject to change
  13. COMMUNITY   POCs,   DEPLOYMENTS   USE  CASES   CORE

        PLATFORM   ROADMAP  -­‐  2015  
  14. ONOS  POCs  under  explora_on/implementa_on   •  AT&T   •  Use

     Case  POCs   •  AT&T  Labs   •  Cloud  Innova_on  Lab  (  Dallas)     •  NTT  +  NEC   •  Packet  op_cal  use  case  POC     •  Huawei   •  IP  RAN  use  case  POC   •  Others  under  discussion   •  ONOS  Community  Lab(s)     •  Under  discussion  with  several  vendor  partners     * Statements here are forward looking and subject to change
  15. Internet2  deployment:  SDN-­‐IP   •  Provide  L3  connec_vity  between  6

     universi_es  around  US   o  SDN  switches  in  the  core   o  ONOS  and  SDN-­‐IP  will  control  the  network     Seamless  peering  of  SDN  islands  with  exis_ng  networks  =  Migra_on  strategy  for  real  networks  
  16. COMMUNITY   POCs,   DEPLOYMENTS   USE  CASES   CORE

        PLATFORM   ROADMAP  -­‐  2015  
  17. GOAL  1:  BUILDING  THE  ONOS  DEVELOPER  COMMUNITY   GOALS • 

    Expand  the  developer  community   •  Create  sense  of  belonging  and  ownership   •  Generate  significant,  sustained                contribu_ons     Jono  Bacon:  Community  Strategy  for  ONOS   •  Transparency   •  Good  code,  good  architecture,  good   documenta_on   •  New  developer  ques_ons  answered  right   away   •  Events-­‐  hackathons,  meetups,  engage  with   other  project  community  managers   •  Don’t  throw  marke_ng  stuff  at              developers  J   •  Encourage  and  celebrate  contribu_ons   •  Solicit  feedback  on  regular  basis  to  know   what’s  going  on  well  and  specially  what  isn’t.   Tweet reproduced with permission of Steven Noble HOW?  
  18. ONF   OPNFV   OTHER  OS  PROJECTS   You  tell

     us…   You  help  us…   Network  VirtualizaEon   Neutron  APIs   Network  FuncEons  as  a  Service   Reference  deployments   Northbound  (Intent  Framework)   Southbound  (OpenFlow,  OVS)   GOAL  2:  INFLUENCING  STANDARDS,  WORKING  WITH  OTHER     OPEN  SOURCE  PROJECTS   OPENSTACK  
  19. OPEN  SOURCE  ONOS  PROJECT   Success  Metrics  -­‐  2015  

    Delivering  quality  code,  Emely  releases,  value   Service  Provider  and  Vendor  Sponsorship,   ParEcipaEon,  Diversity   Community  support  and  contribuEons     Open-­‐ness,  transparency,  meritocracy   Industry  and  end  user  buy-­‐in,  trials,  adopEon  
  20. All  of  this  and  more  is  possible..   Because  we

     hope  to  have  each  one  of  you  on-­‐board!   Exci_ng  _mes  ahead!   Join the journey @ onosproject.org