The controller placement problem
The controller placement problem
复制标题
DOI：
10.1145/2342441.2342444
复制
发表时间：
2012
期刊：
影响因子：
--
通讯作者：
Brandon Heller;Rob Sherwood;N. McKeown
中科院分区：
文献类型：
--
作者：
Brandon Heller;Rob Sherwood;N. McKeown
诸如软件定义网络（SDN）之类的网络架构将控制逻辑从分组处理设备转移到外部控制器上。与更传统的纯分布式系统相比，这些具有解耦控制平面的网络架构在可靠性、可扩展性和性能方面提出了许多未回答的问题。本文打开调查集中在两个具体的问题：给定的拓扑结构，需要多少控制器，他们应该去哪里？为了回答这些问题，我们研究了即将到来的Internet 2生产部署中控制平面传播延迟的基本限制，然后将我们的范围扩展到100多种公开可用的WAN拓扑。正如预期的那样，答案取决于拓扑。更令人惊讶的是，一个控制器位置通常足以满足现有的反应时间要求（尽管肯定不是容错要求）。
Network architectures such as Software-Defined Networks (SDNs) move the control logic off packet processing devices and onto external controllers. These network architectures with decoupled control planes open many unanswered questions regarding reliability, scalability, and performance when compared to more traditional purely distributed systems. This paper opens the investigation by focusing on two specific questions: given a topology, how many controllers are needed, and where should they go? To answer these questions, we examine fundamental limits to control plane propagation latency on an upcoming Internet2 production deployment, then expand our scope to over 100 publicly available WAN topologies. As expected, the answers depend on the topology. More surprisingly, one controller location is often sufficient to meet existing reaction-time requirements (though certainly not fault tolerance requirements).