Editing Networking/Summit-2017-03
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
= Agenda / Presentations = | = Agenda / Presentations = | ||
We had two full tracks of Networking presentations this year at Summit! Videos of presentations | We had two full tracks of Networking presentations this year at Summit! Videos of presentations will be available soon. | ||
=== 0900 - Welcome to OCP Networking === | === 0900 - Welcome to OCP Networking === | ||
* Omar Baldonado, Facebook | * Omar Baldonado, Facebook | ||
* Scott Emery, Cumulus Networks | * Scott Emery, Cumulus Networks | ||
== Track 1 (Times in PST) == | |||
=== 0930 - Facebook's Open Networking Hardware. === | === 0930 - Facebook's Open Networking Hardware. === | ||
This workshop will provide a technical overview of the latest networking devices coming from Facebook's hardware engineering teams: Backpack, their 128x100G modular chassis, and Wedge 100S, a new version of the original 32x100G Wedge 100 switch. The workshop will also include engineers from Cavium and Barefoot Networks, who will talk about the variations of Wedge 100 that they have developed to integrate their programmable ASICs into the platform, and the new use cases that are unlocked by their technologies. | This workshop will provide a technical overview of the latest networking devices coming from Facebook's hardware engineering teams: Backpack, their 128x100G modular chassis, and Wedge 100S, a new version of the original 32x100G Wedge 100 switch. The workshop will also include engineers from Cavium and Barefoot Networks, who will talk about the variations of Wedge 100 that they have developed to integrate their programmable ASICs into the platform, and the new use cases that are unlocked by their technologies. | ||
| Line 18: | Line 14: | ||
* Xu Wang, Facebook | * Xu Wang, Facebook | ||
* Zhiping Yao, Facebook | * Zhiping Yao, Facebook | ||
=== 1030 - Tales From the Field: L1 Issues === | === 1030 - Tales From the Field: L1 Issues === | ||
With the rise of Open Networking, where a user is able to switch out any piece of the stack without vendor lock in (switch, pluggable, NOS, etc…), we have only seen more issues arise when compared with vendor locked solutions. Most of these issues happen at L1 between the switch, the NOS, and the pluggable (cable or optic). Even companies that promote open networking solutions and provide internal testing fall victim to L1 issues. This talk is centered around common L1 issues observed from the field and how some vendors have banded together to eliminate them. | With the rise of Open Networking, where a user is able to switch out any piece of the stack without vendor lock in (switch, pluggable, NOS, etc…), we have only seen more issues arise when compared with vendor locked solutions. Most of these issues happen at L1 between the switch, the NOS, and the pluggable (cable or optic). Even companies that promote open networking solutions and provide internal testing fall victim to L1 issues. This talk is centered around common L1 issues observed from the field and how some vendors have banded together to eliminate them. | ||
* Carlos Cardenas, Cumulus Networks | * Carlos Cardenas, Cumulus Networks | ||
=== 1100 - Universal Connectivity and Interoperability in the Open Ecosystem === | === 1100 - Universal Connectivity and Interoperability in the Open Ecosystem === | ||
Interoperability is essential for customer confidence and wide adoption. This talk will address networking interop complexities inherent in an Open Eco system, including some problems that are unique to an Open Eco system, and that must be addressed for successful adoption. We'll examine specific types of Interop Problems found during plugfests and lab testing at UNH-IOL. Finally we'll examine what the community is doing to combat this and ensure interoperability. | Interoperability is essential for customer confidence and wide adoption. This talk will address networking interop complexities inherent in an Open Eco system, including some problems that are unique to an Open Eco system, and that must be addressed for successful adoption. We'll examine specific types of Interop Problems found during plugfests and lab testing at UNH-IOL. Finally we'll examine what the community is doing to combat this and ensure interoperability. | ||
* David Woolf, University of New Hampshire InterOperability Laboratory (UNH-IOL) | * David Woolf, University of New Hampshire InterOperability Laboratory (UNH-IOL) | ||
=== 1130 - ONIE with Secure Boot === | === 1130 - ONIE with Secure Boot === | ||
| Line 43: | Line 33: | ||
* Curt Brune, Cumulus Networks | * Curt Brune, Cumulus Networks | ||
=== 1300 - Linux Networking Greatness, episode 2 === | === 1300 - Linux Networking Greatness, episode 2 === | ||
| Line 56: | Line 44: | ||
* Roopa Prabhu, Cumulus Networks | * Roopa Prabhu, Cumulus Networks | ||
=== 1330 - Experience in Operating a Mixed OCP/Non-OCP Data Center Network === | === 1330 - Experience in Operating a Mixed OCP/Non-OCP Data Center Network === | ||
Facebook has been aggressively rolling out its Wedge, Wedge100, and now Backpack devices throughout its data centers. Yet, our data centers are (and will continue to be for quite a while) a mix of these OCP-accepted, disaggregated networking devices running FBOSS and traditional, non-OCP networking devices from traditional networking vendors. The Facebook Net Systems group writes the software on our switches (FBOSS) but also writes the software that provisions, automates, monitors, and controls these mixed data centers. This talk will cover learnings from how we had to adapt our existing systems to handle OCP networking devices such as Wedge/Wedge 100 alongside the traditional networking switches. It will also highlight patterns/conventions that we'd like to see all networking devices move toward to make operations of the network smoother. | Facebook has been aggressively rolling out its Wedge, Wedge100, and now Backpack devices throughout its data centers. Yet, our data centers are (and will continue to be for quite a while) a mix of these OCP-accepted, disaggregated networking devices running FBOSS and traditional, non-OCP networking devices from traditional networking vendors. The Facebook Net Systems group writes the software on our switches (FBOSS) but also writes the software that provisions, automates, monitors, and controls these mixed data centers. This talk will cover learnings from how we had to adapt our existing systems to handle OCP networking devices such as Wedge/Wedge 100 alongside the traditional networking switches. It will also highlight patterns/conventions that we'd like to see all networking devices move toward to make operations of the network smoother. | ||
* Starsky Wong, Facebook | * Starsky Wong, Facebook | ||
=== 1400 - Open Networking Advancing, Expanding, and Deploying === | === 1400 - Open Networking Advancing, Expanding, and Deploying === | ||
| Line 71: | Line 55: | ||
# Real word use cases and deployments – 1. Presentation from Major retailor utilizing Open Networking equipment and SW, and 2. Presentation from Major carrier deploying Open Networking equipment and SW | # Real word use cases and deployments – 1. Presentation from Major retailor utilizing Open Networking equipment and SW, and 2. Presentation from Major carrier deploying Open Networking equipment and SW | ||
* Jeff Catlin, Edgecore Networks | * Jeff Catlin, Edgecore Networks | ||
=== 1430 - Alpha 10G, 25G, and 100G switches for the DC and Telco Markets === | === 1430 - Alpha 10G, 25G, and 100G switches for the DC and Telco Markets === | ||
| Line 78: | Line 60: | ||
* Robert Chu, Alpha | * Robert Chu, Alpha | ||
== | == Track 2 == | ||
| Line 86: | Line 67: | ||
Switch Abstraction Interface (SAI) provides simple, consistent APIs for the upper network stack to consume the underlying complex, heterogeneous hardware easily and faster. Multiple popular NOS/network control stack are running on top of SAI, as a fundamental element of disaggregation. We are excited to announce SAI 1.0 release. Architects from major silicon companies will be on the stage to talk about advanced capabilities added/will be added to SAI and use cases lit up through these APIs. | Switch Abstraction Interface (SAI) provides simple, consistent APIs for the upper network stack to consume the underlying complex, heterogeneous hardware easily and faster. Multiple popular NOS/network control stack are running on top of SAI, as a fundamental element of disaggregation. We are excited to announce SAI 1.0 release. Architects from major silicon companies will be on the stage to talk about advanced capabilities added/will be added to SAI and use cases lit up through these APIs. | ||
* Xin Liu, Microsoft | * Xin Liu, Microsoft | ||
=== 1000 - Networking SAI Behavioral Model Implementation in P4 === | === 1000 - Networking SAI Behavioral Model Implementation in P4 === | ||
Providing standard interfaces for managing Ethernet switch device (SAI) is a great step towards HW agnostic NOS. Still, different underlying HW pipelines may result in HW specific product behavior. OCP SAI community has been defining a generic logical pipeline that can represent a common denominator of different Silicon implementation, named SAI behavioral model. Mellanox is implementing this model in P4 language to create a SW switch that is controlled by SAI interface. We would like to present the work, share the repository with the community, discuss obstacles we found along the way, and ask for other member's contributions. | Providing standard interfaces for managing Ethernet switch device (SAI) is a great step towards HW agnostic NOS. Still, different underlying HW pipelines may result in HW specific product behavior. OCP SAI community has been defining a generic logical pipeline that can represent a common denominator of different Silicon implementation, named SAI behavioral model. Mellanox is implementing this model in P4 language to create a SW switch that is controlled by SAI interface. We would like to present the work, share the repository with the community, discuss obstacles we found along the way, and ask for other member's contributions. | ||
* Aviad Raveh, Mellanox | * Aviad Raveh, Mellanox | ||
=== 1030 - Taking SAI Beyond the Data Center Fabric === | === 1030 - Taking SAI Beyond the Data Center Fabric === | ||
In this talk, we’ll examine the applicability of both SAI and SONiC to use cases which go beyond a typical DC fabric and argue that these use cases can drive the broader adoption of these technologies. We’ll look at the functional requirements these use cases place upon both SAI and SONiC; as well as the proof points in terms of scale, robustness and high-availability that both OCP-conformant hardware and software will need to be able to demonstrate to provide a compelling deployable solution for these cases. | In this talk, we’ll examine the applicability of both SAI and SONiC to use cases which go beyond a typical DC fabric and argue that these use cases can drive the broader adoption of these technologies. We’ll look at the functional requirements these use cases place upon both SAI and SONiC; as well as the proof points in terms of scale, robustness and high-availability that both OCP-conformant hardware and software will need to be able to demonstrate to provide a compelling deployable solution for these cases. | ||
* Alan Elder, Metaswitch | * Alan Elder, Metaswitch | ||
=== 1100 - SONIC: Enabling Fast Evolution in the Network === | === 1100 - SONIC: Enabling Fast Evolution in the Network === | ||
Running one of the largest clouds in the world, Microsoft has gained a lot of insight into building and managing a global, high performance, highly available and secure network. We built the these intelligence into Software for Open Networking in the Cloud (SONiC), which thrive for network switch operations and management. Dave Maltz, Distinguished Engineer from Microsoft, will deep dive into the design philosophy underneath SONiC, e.g. containerization, orchestration and how they enable the fast evolution of hyperscale networking. | Running one of the largest clouds in the world, Microsoft has gained a lot of insight into building and managing a global, high performance, highly available and secure network. We built the these intelligence into Software for Open Networking in the Cloud (SONiC), which thrive for network switch operations and management. Dave Maltz, Distinguished Engineer from Microsoft, will deep dive into the design philosophy underneath SONiC, e.g. containerization, orchestration and how they enable the fast evolution of hyperscale networking. | ||
* Dave Maltz, Microsoft | * Dave Maltz, Microsoft | ||
=== 1130 - Testing to Enable 100G Fabrics at Scale (TOR and Optics) === | === 1130 - Testing to Enable 100G Fabrics at Scale (TOR and Optics) === | ||
| Line 112: | Line 85: | ||
* Srinivasan Giridharan, Facebook | * Srinivasan Giridharan, Facebook | ||
* Ashwin Poojary, Facebook | * Ashwin Poojary, Facebook | ||
=== 1330 - OpenSwitch (OPX) Introduction === | === 1330 - OpenSwitch (OPX) Introduction === | ||
Open Switch is a project dedicated to making a solid Open Source option for a complete Network platform supporting the community and providing networking innovations. Open Switch has evolved recently to with new players Dell and Snaproute stepping in while HP has decided to exit the OpenSwitch project for now. With the changes there is a re-focus on making a completely open source NOS providing both a solid (Linux Based Package approach) allowing the installation of Open Switch on a Debian Jessie based platform. To the OPX project, Dell contributes the Open Source Base directly from their OS 10 Open Edition product while Snaproute has taken the role of providing the control plane software running on top. In this talk we will go through the architecture of the both of these components and describe to the community how and where they can help out. | Open Switch is a project dedicated to making a solid Open Source option for a complete Network platform supporting the community and providing networking innovations. Open Switch has evolved recently to with new players Dell and Snaproute stepping in while HP has decided to exit the OpenSwitch project for now. With the changes there is a re-focus on making a completely open source NOS providing both a solid (Linux Based Package approach) allowing the installation of Open Switch on a Debian Jessie based platform. To the OPX project, Dell contributes the Open Source Base directly from their OS 10 Open Edition product while Snaproute has taken the role of providing the control plane software running on top. In this talk we will go through the architecture of the both of these components and describe to the community how and where they can help out. | ||
* Cliff Wichmann, Dell | * Cliff Wichmann, Dell | ||
=== 1400 - Controlling the Network with APIs === | === 1400 - Controlling the Network with APIs === | ||
SnapRoute will demo the API-driven model that is used by the OCP project FlexSwitch. The showcase will be how using APIs as the control point of the network can allow for high-levels of automation and programability. Also, the integration of FlexSwitch APIs with other OCP projects such as Open Network Linux and ONIE will be demonstrated. | SnapRoute will demo the API-driven model that is used by the OCP project FlexSwitch. The showcase will be how using APIs as the control point of the network can allow for high-levels of automation and programability. Also, the integration of FlexSwitch APIs with other OCP projects such as Open Network Linux and ONIE will be demonstrated. | ||
* Glenn Sullivan, Snaproute | * Glenn Sullivan, Snaproute | ||
=== 1430 - 100G Optics Deployment in Facebook Data Centers === | === 1430 - 100G Optics Deployment in Facebook Data Centers === | ||
| Line 134: | Line 101: | ||
* Katharine Schmidtke, Facebook | * Katharine Schmidtke, Facebook | ||
* Vincent Zeng, Facebook | * Vincent Zeng, Facebook | ||