DROS Configuration Maintained by: David Austin

• 1.0 Introduction

1.0 Introduction

This web page describes how configurations should be managed for DROS. First, we define what is meant by a configuration. We will use the term configuration space. A configuration space is the data needed by programs that the user starts. It is expected that every configuration space contain at least the data that StateManager will use to start the processes that the user wants. In addition to this, the configuration space will contain the configuration for each of the programs that are started. Ideally, all configurable items for each program will be loaded from the configuration space. However, this is not required.

Each user therefore, has a configuration space (or multiple configuration spaces). The configuration spaces are stored in the global database maintained by the DBManager.

One overriding design idea for the configuration spaces is that one should be able to re-use existing configurations, just re-defining the parts that need to be changed for the latest application. Hopefully, this will make configuration of the system a whole lot easier for the users (though a little harder to implement).

Copyright 2001 David Austin