Software-defined networking separates the part of a network that decides where traffic goes from the part that moves it. A central or logically central controller computes policy in ordinary software; simple switches follow the rules it installs. The result is a network you program, test and change like any other system.
Key concepts
- Control plane and data plane: the first decides and the second forwards, and SDN splits them.
- Match-action tables: a switch matches header fields and applies an action, such as forward, drop or rewrite.
- Southbound and northbound interfaces: the controller speaks to devices with a protocol such as OpenFlow, and to applications through an API.
- Programmable data planes: languages such as P4 describe how a switch parses and forwards packets.
- Virtual networks: overlays that give tenants private networks on shared hardware.
Vocabulary
- Controller: the software that holds the network's global view and installs rules.
- Flow: a stream of packets sharing header values, the unit rules act on.
- Overlay: a virtual network tunnelled over a physical one, as with VXLAN.
- Open vSwitch: a widely used software switch for virtualised hosts.
- Intent: a high-level statement of what the network should do, left to software to realise.
What to study, in order
- Classic switching and routing, so you know what is being separated.
- Run Open vSwitch and a network emulator such as Mininet on one machine.
- Write a small controller that learns MAC addresses and installs flows.
- Add a policy, such as blocking one host pair, and verify it with captured traffic.
- Read about failure: what happens to forwarding when the controller is unreachable, and how to scale it out.