How can a network be "virtual"?
summary
Explains why clouds need networks that look local while running on shared hardware and details Linux tools that make that happen including 802.1Q VLANs and encapsulation tunnels like VXLAN over UDP and GRE that carry Ethernet across IP, how Open vSwitch implements SDN/OpenFlow and can encapsulate and select traffic, how OVN provides the high level API for orchestrating rules and migrations, how containers use network namespaces and veth pairs, and why overlays and reconfiguration are required for live migration.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:42Traditional Networking
- 5:31Vlan
- 12:24Generic Road Encapsulation
- 14:31Routing
- 16:07Switching
- 21:29Open V-Switch
- 26:19Overlay Network
- 29:06Containers
- 34:22What's the Cost of Having Multiple Q and Q in Vlan Solution for Network Virtualization Is It Resource Intensive for Switches
related talks
45mPanel: What's Next in Network Virtualization
22mConnecting virtual machines in the cloud age
51mSoftware Defined Networking Using the VXLAN Standard
29mLiving on the Edge with DCN Networking
51mOVN: Integrating an Off-the-Shelf SDN into a Virtualization Platform
47mVirtualized highload NFV
43mPanel Discussion: Containers and Networking: A Symbiotic Relationship
19mAdvanced Network management with oVirt and OVN