TY - GEN
T1 - HotSwap
T2 - 2013 2nd ACM SIGCOMM Workshop on Hot Topics in Software Defined Networking, HotSDN 2013
AU - Vanbever, Laurent
AU - Reich, Joshua
AU - Benson, Theophilus
AU - Foster, Nate
AU - Rexford, Jennifer L.
PY - 2013
Y1 - 2013
N2 - Like any complex software, SDN programs must be updated periodically, whether to migrate to a new controller platform, repair bugs, or address performance issues. Nowadays, SDN operators typically perform such upgrades by stopping the old controller and starting the new one - an approach that wipes out all installed flow table entries and causes substantial disruption including losing packets, increasing latency, and even compromising correctness. This paper presents HOTSWAP, a system for upgrading SDN controllers in a disruption-free and correct manner. HOTSWAP is a hypervisor (sitting between the switches and the controller) that maintains a history of network events. To upgrade from an old controller to a new one, HOTSWAP bootstraps the new controller (by replaying the history) and monitors its output (to determine which parts of the network state may be reused with the new controller). To ensure good performance, HOTSWAP filters the history using queries specified by programmers. We describe our design and preliminary implementation of HOTSWAP, and present experimental results demonstrating its effectiveness for managing upgrades to third-party controller programs.
AB - Like any complex software, SDN programs must be updated periodically, whether to migrate to a new controller platform, repair bugs, or address performance issues. Nowadays, SDN operators typically perform such upgrades by stopping the old controller and starting the new one - an approach that wipes out all installed flow table entries and causes substantial disruption including losing packets, increasing latency, and even compromising correctness. This paper presents HOTSWAP, a system for upgrading SDN controllers in a disruption-free and correct manner. HOTSWAP is a hypervisor (sitting between the switches and the controller) that maintains a history of network events. To upgrade from an old controller to a new one, HOTSWAP bootstraps the new controller (by replaying the history) and monitors its output (to determine which parts of the network state may be reused with the new controller). To ensure good performance, HOTSWAP filters the history using queries specified by programmers. We describe our design and preliminary implementation of HOTSWAP, and present experimental results demonstrating its effectiveness for managing upgrades to third-party controller programs.
KW - Controller upgrade
KW - Dynamic software updating
KW - Software-defined network
UR - http://www.scopus.com/inward/record.url?scp=84883717281&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84883717281&partnerID=8YFLogxK
U2 - 10.1145/2491185.2491194
DO - 10.1145/2491185.2491194
M3 - Conference contribution
AN - SCOPUS:84883717281
SN - 9781450320566
T3 - HotSDN 2013 - Proceedings of the 2013 ACM SIGCOMM Workshop on Hot Topics in Software Defined Networking
SP - 133
EP - 138
BT - HotSDN 2013 - Proceedings of the 2013 ACM SIGCOMM Workshop on Hot Topics in Software Defined Networking
Y2 - 16 August 2013 through 16 August 2013
ER -