Reconfiguration in Argus

Annotation: Defines a correctness condition for reconfiguration: ``continuation abstractions are preserved or invisibly extended by a replacement.'' That is, module (guardian) replacements must be backward (upward) compatible and must continue the behavior of the original module (e.g., by transferring the old module's state). Reconfiguration quiesces the modules to be replaced; client transactions on those modules abort. The authors describe two kinds of upgrading infrastructures: system-supported replacement (SSR) and application-level replacement (ALR). SSR requires hooks in the Argus system to allow replacement and an additional indirection on handler calls. ALR requires participation by designers of modules and clients of modules to support upgrades.

BibTeX entry:

@inproceedings{bloom92reconfiguration,
   author = {Toby Bloom and Mark Day},
   title = {Reconfiguration in {Argus}},
   booktitle = {Intl. Workshop on Configurable Dist. Systems},
   pages = {176--187},
   address = {London, England},
   month = mar,
   year = {1992},
   note = {Also in [swej93mar], pages 102--108}
}