No more HotDependencies: toward dependency-agnostic online upgrades in distributed systems

Authors:
Tudor Dumitras;Jiaqi Tan;Zhengheng Gho;Priya Narasimhan
Affiliations:
Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA
Venue:
HotDep'07 Proceedings of the 3rd workshop on on Hot Topics in System Dependability
Year:
2007

Citing 4
Cited 5

Dependence Management in Component-Based Distributed Systems

IEEE Concurrency
On-the-Fly Program Modification: Systems for Dynamic Updating

IEEE Software
How do APIs evolve? A story of refactoring: Research Articles

Journal of Software Maintenance and Evolution: Research and Practice - IEEE International Conference on Software Maintenance (ICSM2005)
Reducing downtime due to system maintenance and upgrades

LISA '05 Proceedings of the 19th conference on Large Installation System Administration Conference - Volume 19

Collateral evolution of applications and databases

Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
Why do upgrades fail and what can we do about it?: toward dependable, online upgrades in enterprise system

Proceedings of the 10th ACM/IFIP/USENIX International Conference on Middleware
Why do upgrades fail and what can we do about it?: toward dependable, online upgrades in enterprise system

Middleware'09 Proceedings of the ACM/IFIP/USENIX 10th international conference on Middleware
Safe and automatic live update for operating systems

Proceedings of the eighteenth international conference on Architectural support for programming languages and operating systems
Disnix: A toolset for distributed deployment

Science of Computer Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

Traditional approaches for online upgrades of distributed systems rely on dependency tracking to preserve system integrity during and after the upgrade. Because dependency reification can become intractable, we aim to enforce the isolation of the old and new versions during the upgrade. We achieve this by installing the new version in a "parallel universe" - a separate physical or virtual infrastructure that does not communicate directly with the old version. This allows our upgrading middleware to treat the complex IT infrastructure as a black box with unknown hidden-dependencies, and to validate the upgrade by cross-checking the outputs of the two universes.