Mubashir Anwar
ABSTRACT
The future of static verification in networking may be obscured by two clouds: the complexity of distributed systems with highly concurrent events, and the decision-making on infrastructures growing without a premeditated plan. This poster discusses a possible solution to these issues, in which the huge space of analyzing distributed systems and the macro-questions of system evolution are addressed by a common structure, a logical implication problem which we call indirect troubleshooting. The usefulness and feasibility of indirect troubleshooting is illustrated by a preliminary realization with the chase, a remarkable process for mechanically deciding implications.
- Serge Abiteboul, Richard Hull, and Victor Vianu (Eds.). 1995. Foundations of Databases: The Logical Level (1st ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.Google Scholar
- Mike Y. Chen, Anthony Accardi, and Dave Patterson. 2004. Path-Based Failure and Evolution Management. In First Symposium on Networked Systems Design and Implementation (NSDI 04). USENIX Association, San Francisco, CA.Google Scholar
- Ari Fogel, Stanley Fung, Luis Pedrosa, Meg Walraed-Sullivan, Ramesh Govindan, Ratul Mahajan, and Todd Millstein. 2015. A General Approach to Network Configuration Analysis. In Proceedings of the 12th USENIX Conference on Networked Systems Design and Implementation (Oakland, CA) (NSDI’15). USENIX Association, USA, 469–483.Google ScholarDigital Library
Index Terms
- Indirect Network Troubleshooting with The Chase
Index terms have been assigned to the content through auto-classification.
Comments