Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Stratum: Next-Gen SDN (beyond OpenFlow)

256 views

Published on

Stratum is a next-generation network operating system (NOS) for white box switches. It is primarily focused on supporting machine interfaces (P4RT, gNMI and gNOI) to automate network operations and enable user defining network element behavior with P4. PLVision is a proud contributor to the Stratum Project.

As presented by PLVision's team at MPLS+SDN+NFV World Congress Paris 2019 at ONF Tutorials.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Stratum: Next-Gen SDN (beyond OpenFlow)

  1. 1. Stratum: Next-Gen SDN (beyond OpenFlow) Leonid Khedyk, CTO Iurii Odnorogov, BDM
  2. 2. Why PLVision is here • Silicon validation, BSP, Abstraction Layer (HAL/SAI) and SDK development; • Drivers, Libraries (Custom L2/L3 protocol stack or frameworks (e.g. Quagga) and API development; • North-bound protocols: OpenFlow, P4Runtime, NETCONF etc. • Switch silicons: Broadcom XGS & DNX, Mellanox SwitchX & Spectrum, Cavium Xpliant, Intel Fulcrum, Barefoot Tofino Full-Cycle NOS Development • Turnkey development of custom NOSes and commercial/open- source NOS porting and maintenance: OVS/FBOSS/SONiC/OPX/OPS; • Spirent & Ixia Testing, TAF development and adaptation; • Custom UI solutions: Web UI, CLI, CI/CD, SNMP Management.
  3. 3. Introduction: Legacy SDN
  4. 4. ONF’s History
  5. 5. ONF’s History
  6. 6. Challenges with Existing SDN Programmatic network interfaces are inconsistent and incomplete • OpenFlow provided no data plane pipeline specification; every vendor’s pipeline is different • Every vendor provides their own proprietary models for configuration or management Control planes are written and tested against specific hardware • Workaround with own abstractions to handle hardware differences: either least common denominator (e.g. SAI) or underspecified (e.g. FlowObjectives) • Exploited specific APIs that are essentially locked in to specific vendors, which slows innovation cycles Programmable forwarding chips are here • Control protocols are mostly fixed function • Extensibility is difficult or takes too long • Even “fixed-function” forwarding chips have some degree of programmability and may add new features
  7. 7. Challenge: Bringing SDN to production Need to define mutable contract between the hardware vendor and network operator • Different operators can have different contracts • Contract must be designed for programmability; APIs must be contract-independent Operators have hit limitations with existing protocols when introducing them into their networks at scale • e.g. OpenFlow, NETCONF • Interfaces and services must evolve to meet operational needs SDN at scale brings new requirements • Frequent updates to all layers of the stack (software AND state) • Monitoring, visibility and automation for rollout and operations
  8. 8. Next-Gen SDN Requirements New control interface with: • Abstraction for different types of switching chips • Well-defined interfaces and behavior • Extensibility Common interfaces for operations • Testing, Debugging, Certificate Management, Software upgrade Common platform abstraction (e.g. OCP’s ONLP) Open source switch stack
  9. 9. Stratum’s Answer: Next-Gen SDN Interfaces
  10. 10. P4/ P4Runtime Adapted from P4.org
  11. 11. Configuration Interfaces Adapted from Google • Configuration and management • Declarative configuration • Streaming telemetry • Model-driven management and operations o gNMI – network management interface o gNOI – network operations interface • Vendor-neutral data models
  12. 12. Code Releases Release 0.1 (May 2018) Release 0.2 (Oct. 2018) Release 0.3 (Dec. 2018) P4Runtime Support for pre-release Support for 1.0.0-rc1 Support for 1.0 and minor fixes gNMI Basic framework Stable support Stable support and bug fixes gNOI - Initial interfaces 4 service implementations (e.g. system, file) Switch support Google platforms; Partial Broadcom support Barefoot Tofino on 3 vendors; BMv2 software sw. Tofino platform integration; DummySwitch for testing Platform abstraction Basic interfaces Support for platform mapping and DB Add support for ONLP Conformance Testing - Test framework definitions Test framework definitions
  13. 13. Use Cases
  14. 14. The gNOI Story - Stratum
  15. 15. The gNOI Story - ONOS
  16. 16. The gNOI Story – ONOS Internals gNOI Protocol gNOI Driver PROTOCOLS DRIVERS Stratum gNOI CORE APPLICATIONS Applications Behavior Interfaces: SystemTime, SystemReboot, ... PROVIDERS Providers Managers System CLI
  17. 17. The gNOI Story – Update Application
  18. 18. Summary: The Next-Gen SDN View
  19. 19. Stratum Community
  20. 20. Why PLVision participates in Stratum • View it as a vendor-neutral SDK that enables o Quick porting to new platforms/silicones (well-defined APIs) o Easiness of adaptation to new use cases (P4 + P4Runtime) o Flexibility in applications (thin vs. thick models) interface • Less time to get from PoC to MVP and trials • Change behavior and add new functionality on the go
  21. 21. Iurii Odnorogov iurii.odnorogov@plvision.eu Leonid Khedyk leonid.khedyk@plvision.eu Thank you! opennetworking.org/stratum plvision.eu

×