The Experts below are selected from a list of 29901 Experts worldwide ranked by ideXlab platform
Kyriakos Zarifis - One of the best experts on this subject based on the ideXlab platform.
-
troubleshooting blackbox sdn Control Software with minimal causal sequences
ACM Special Interest Group on Data Communication, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed Elhassany, Sam Whitlock, H B Acharya, Kyriakos ZarifisAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
Colin Scott - One of the best experts on this subject based on the ideXlab platform.
-
troubleshooting blackbox sdn Control Software with minimal causal sequences
ACM Special Interest Group on Data Communication, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed Elhassany, Sam Whitlock, H B Acharya, Kyriakos ZarifisAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
-
SIGCOMM - Troubleshooting blackbox SDN Control Software with minimal causal sequences
ACM SIGCOMM Computer Communication Review, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed El-hassany, Sam WhitlockAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
Sam Whitlock - One of the best experts on this subject based on the ideXlab platform.
-
troubleshooting blackbox sdn Control Software with minimal causal sequences
ACM Special Interest Group on Data Communication, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed Elhassany, Sam Whitlock, H B Acharya, Kyriakos ZarifisAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
-
SIGCOMM - Troubleshooting blackbox SDN Control Software with minimal causal sequences
ACM SIGCOMM Computer Communication Review, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed El-hassany, Sam WhitlockAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
Andreas Wundsam - One of the best experts on this subject based on the ideXlab platform.
-
troubleshooting blackbox sdn Control Software with minimal causal sequences
ACM Special Interest Group on Data Communication, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed Elhassany, Sam Whitlock, H B Acharya, Kyriakos ZarifisAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
-
SIGCOMM - Troubleshooting blackbox SDN Control Software with minimal causal sequences
ACM SIGCOMM Computer Communication Review, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed El-hassany, Sam WhitlockAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
Andrew Or - One of the best experts on this subject based on the ideXlab platform.
-
troubleshooting blackbox sdn Control Software with minimal causal sequences
ACM Special Interest Group on Data Communication, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed Elhassany, Sam Whitlock, H B Acharya, Kyriakos ZarifisAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.
-
SIGCOMM - Troubleshooting blackbox SDN Control Software with minimal causal sequences
ACM SIGCOMM Computer Communication Review, 2015Co-Authors: Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Eugene Huang, Ahmed El-hassany, Sam WhitlockAbstract:Software bugs are inevitable in Software-defined networking Control Software, and troubleshooting is a tedious, time-consuming task. In this paper we discuss how to improve Control Software troubleshooting by presenting a technique for automatically identifying a minimal sequence of inputs responsible for triggering a given bug, without making assumptions about the language or instrumentation of the Software under test. We apply our technique to five open source SDN Control platforms---Floodlight, NOX, POX, Pyretic, ONOS---and illustrate how the minimal causal sequences our system found aided the troubleshooting process.