Many techniques were proposed for detecting soft- ware misconfigurations and diagnosing unintended behavior caused by misconfigurations in cloud systems. Detection and diagnosis are steps in the right direction: misconfigurations cause many costly failures and severe performance issues. But we argue that continued focus on detection and diagnosis is symptomatic of a more serious problem: configuration design and implementation are not first-class software engineering endeavors in cloud systems. Little is known about how and why developers of these systems evolve software configuration design and implementation, and the challenges that they face in doing so.

We present a source-code level study of the evolution of software configuration design and implementation in cloud systems. Our goal is to understand the rationale and developer practices for revising initial software configuration design and implementation decisions, especially in response to consequences of misconfigurations. To this end, we studied 1178 configuration-related commits from a recent 2.5 year version-control history of four large-scale, mature, and actively-maintained open-source cloud systems (HDFS, HBase, Spark, and Cassandra). We derive several new insights into the software configuration engineering process. Our results motivate new techniques for proactively reducing misconfigurations by improving the configuration design and implementation process in cloud systems. We highlight a number of future research directions.