Troubleshooting blackbox SDN control software with minimal causal sequences

Colin Scott; Andreas Wundsam; Barath Raghavan; Aurojit Panda; Andrew Or; Jefferson Lai; Eugene Huang; Zhi Liu; Ahmed El-Hassany; Sam Whitlock; H. B. Acharya; Kyriakos Zarifis; Scott Shenker

doi:10.1145/2619239.2626304

Troubleshooting blackbox SDN control software with minimal causal sequences

Colin Scott, Andreas Wundsam, Barath Raghavan, Aurojit Panda, Andrew Or, Jefferson Lai, Eugene Huang, Zhi Liu, Ahmed El-Hassany, Sam Whitlock, H. B. Acharya, Kyriakos Zarifis, Scott Shenker

Computer Science

Research output: Contribution to journal › Conference article › peer-review

Abstract

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.

Original language	English (US)
Pages (from-to)	395-406
Number of pages	12
Journal	Computer Communication Review
Volume	44
Issue number	4
DOIs	https://doi.org/10.1145/2619239.2626304
State	Published - Feb 25 2015
Event	ACM SIGCOMM 2014 Conference - Chicago, United States Duration: Aug 17 2014 → Aug 22 2014

Keywords

SDN control software
Test case minimization
Troubleshooting

ASJC Scopus subject areas

Software
Computer Networks and Communications

Access to Document

10.1145/2619239.2626304

Cite this

@article{27abd0c2c5304aebac016381b9d81b05,

title = "Troubleshooting blackbox SDN control software with minimal causal sequences",

abstract = "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.",

keywords = "SDN control software, Test case minimization, Troubleshooting",

author = "Colin Scott and Andreas Wundsam and Barath Raghavan and Aurojit Panda and Andrew Or and Jefferson Lai and Eugene Huang and Zhi Liu and Ahmed El-Hassany and Sam Whitlock and Acharya, {H. B.} and Kyriakos Zarifis and Scott Shenker",

year = "2015",

month = feb,

day = "25",

doi = "10.1145/2619239.2626304",

language = "English (US)",

volume = "44",

pages = "395--406",

journal = "Computer Communication Review",

issn = "0146-4833",

publisher = "Association for Computing Machinery (ACM)",

number = "4",

note = "ACM SIGCOMM 2014 Conference ; Conference date: 17-08-2014 Through 22-08-2014",

}

TY - JOUR

T1 - Troubleshooting blackbox SDN control software with minimal causal sequences

AU - Scott, Colin

AU - Wundsam, Andreas

AU - Raghavan, Barath

AU - Panda, Aurojit

AU - Or, Andrew

AU - Lai, Jefferson

AU - Huang, Eugene

AU - Liu, Zhi

AU - El-Hassany, Ahmed

AU - Whitlock, Sam

AU - Acharya, H. B.

AU - Zarifis, Kyriakos

AU - Shenker, Scott

PY - 2015/2/25

Y1 - 2015/2/25

N2 - 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.

AB - 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.

KW - SDN control software

KW - Test case minimization

KW - Troubleshooting

UR - http://www.scopus.com/inward/record.url?scp=84924353655&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84924353655&partnerID=8YFLogxK

U2 - 10.1145/2619239.2626304

DO - 10.1145/2619239.2626304

M3 - Conference article

AN - SCOPUS:84924353655

SN - 0146-4833

VL - 44

SP - 395

EP - 406

JO - Computer Communication Review

JF - Computer Communication Review

IS - 4

T2 - ACM SIGCOMM 2014 Conference

Y2 - 17 August 2014 through 22 August 2014

ER -

Troubleshooting blackbox SDN control software with minimal causal sequences

Abstract

Keywords

ASJC Scopus subject areas

Access to Document

Other files and links

Fingerprint

Cite this