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
RAFT for distributed core • Deﬁne 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
– 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
types of Intents • Conﬂict 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
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 ﬂow labels for SDN use cases) • Security • Mobility • Running another SDN controller and/or another controller’s apps on ONOS. DeﬁniMon of these features to be done in conjuncMon with service providers and vendors. Build these features to be relevant to real world deployments.
Network Func_ons as a service in central oﬃce – 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
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
Expand the developer community • Create sense of belonging and ownership • Generate signiﬁcant, 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 stuﬀ 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?
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
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