Configuration management in the Nexus distributed operating system

A. Tripathi, N. M. Karnik, S. P. Koneru, C. Nock, R. Tewari, K. Day, T. Noonan

Research output: Contribution to journalArticle

Abstract

The paper describes the approach taken for configuration management in the Nexus distributed operating system. Nexus uses kernel‐level support for monitoring the failure or termination status of distributed components of an application. Periodic user‐level messages are not required for status monitoring. Group and dependency relationships between such components can be defined by the programmer for the purpose of configuration monitoring and management. An object belonging to a distributed application can be monitored by its host kernel for system‐defined exception conditions. When any of these conditions arise, other objects are notified through signals or messages, as specified by the programmer.

Original languageEnglish
Pages (from-to)325-338
Number of pages14
JournalConcurrency: Practice and Experience
Volume6
Issue number4
DOIs
Publication statusPublished - 1994

Fingerprint

Operating Systems
Distributed Systems
Monitoring
Configuration
Distributed Applications
Termination
Exception
kernel
Object

ASJC Scopus subject areas

  • Engineering(all)

Cite this

Tripathi, A., Karnik, N. M., Koneru, S. P., Nock, C., Tewari, R., Day, K., & Noonan, T. (1994). Configuration management in the Nexus distributed operating system. Concurrency: Practice and Experience, 6(4), 325-338. https://doi.org/10.1002/cpe.4330060407

Configuration management in the Nexus distributed operating system. / Tripathi, A.; Karnik, N. M.; Koneru, S. P.; Nock, C.; Tewari, R.; Day, K.; Noonan, T.

In: Concurrency: Practice and Experience, Vol. 6, No. 4, 1994, p. 325-338.

Research output: Contribution to journalArticle

Tripathi, A, Karnik, NM, Koneru, SP, Nock, C, Tewari, R, Day, K & Noonan, T 1994, 'Configuration management in the Nexus distributed operating system', Concurrency: Practice and Experience, vol. 6, no. 4, pp. 325-338. https://doi.org/10.1002/cpe.4330060407
Tripathi, A. ; Karnik, N. M. ; Koneru, S. P. ; Nock, C. ; Tewari, R. ; Day, K. ; Noonan, T. / Configuration management in the Nexus distributed operating system. In: Concurrency: Practice and Experience. 1994 ; Vol. 6, No. 4. pp. 325-338.
@article{b3bbe410b48d4deaa590881ac713e3ae,
title = "Configuration management in the Nexus distributed operating system",
abstract = "The paper describes the approach taken for configuration management in the Nexus distributed operating system. Nexus uses kernel‐level support for monitoring the failure or termination status of distributed components of an application. Periodic user‐level messages are not required for status monitoring. Group and dependency relationships between such components can be defined by the programmer for the purpose of configuration monitoring and management. An object belonging to a distributed application can be monitored by its host kernel for system‐defined exception conditions. When any of these conditions arise, other objects are notified through signals or messages, as specified by the programmer.",
author = "A. Tripathi and Karnik, {N. M.} and Koneru, {S. P.} and C. Nock and R. Tewari and K. Day and T. Noonan",
year = "1994",
doi = "10.1002/cpe.4330060407",
language = "English",
volume = "6",
pages = "325--338",
journal = "Concurrency Computation Practice and Experience",
issn = "1532-0626",
publisher = "John Wiley and Sons Ltd",
number = "4",

}

TY - JOUR

T1 - Configuration management in the Nexus distributed operating system

AU - Tripathi, A.

AU - Karnik, N. M.

AU - Koneru, S. P.

AU - Nock, C.

AU - Tewari, R.

AU - Day, K.

AU - Noonan, T.

PY - 1994

Y1 - 1994

N2 - The paper describes the approach taken for configuration management in the Nexus distributed operating system. Nexus uses kernel‐level support for monitoring the failure or termination status of distributed components of an application. Periodic user‐level messages are not required for status monitoring. Group and dependency relationships between such components can be defined by the programmer for the purpose of configuration monitoring and management. An object belonging to a distributed application can be monitored by its host kernel for system‐defined exception conditions. When any of these conditions arise, other objects are notified through signals or messages, as specified by the programmer.

AB - The paper describes the approach taken for configuration management in the Nexus distributed operating system. Nexus uses kernel‐level support for monitoring the failure or termination status of distributed components of an application. Periodic user‐level messages are not required for status monitoring. Group and dependency relationships between such components can be defined by the programmer for the purpose of configuration monitoring and management. An object belonging to a distributed application can be monitored by its host kernel for system‐defined exception conditions. When any of these conditions arise, other objects are notified through signals or messages, as specified by the programmer.

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

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

U2 - 10.1002/cpe.4330060407

DO - 10.1002/cpe.4330060407

M3 - Article

VL - 6

SP - 325

EP - 338

JO - Concurrency Computation Practice and Experience

JF - Concurrency Computation Practice and Experience

SN - 1532-0626

IS - 4

ER -