The typical method to organize configuration settings in ControlTier is to associate them with components.
For example, there might be a component called Apache that represents an instance of an Apache web server. This apache object might have a few config settings like "httpPort", "docroot", and "installroot". These setting objects can be bound to the Apache object. A second component, say Tomcat, would have its own set of config settings like "ajpPort", "httpPort", and "catalinaBase". Finally, you can declare a composition hierarchy describing Apache's dependency on Tomcat.
These examples show two components belonging to the same level of abstraction, each with their own configuration settings. Settings can also be shared between components. For example, the Apache object might need to know the ajpPort value, and this can be accomplished by sharing the same configuration setting object between Apache and Tomcat. Note, this can also be accomplished by traversing the Tomcat dependency relationship to its ajpPort setting.
Global settings can also be established by introducing another abstraction layer. For example, we could introduce an object called ApacheTomcatStack, defined as an object that depends on Apache and Tomcat instances. Let us also say that ApacheTomcatStack has a setting called, "httpPort" (defining the standard listen port for any component that accepts HTTP requests). The Apache and Tomcat objects can inherit this setting via the composition hierarchy.
The ControlTier system itself isn't normally described in the application configuration model, though if the application configuration required it, that could be done. Perhaps you can help me answer this question with a bit more clarification.
Thanks, Alex (a ControlTier developer).
Daniel Hagerty wrote:> -Give the component a name (ex: LoadBalancer,Tomcat, Oracle, etc...)
> -Define the configuration settings that you need to manage (ex: various
> entries in a conf file)
Two complicating factors I find in doing this in larger and larger scales:
* Components contain components
* Saying concrete things about the variables with relation to a model
is important, but the more abstract your model, the more abstraction
support you need to speak of the static properties of configuration
variables in a useful way.
Have you reached the point yet where the component called
"ControlTier" and its variables appear in your system yet?
_______________________________________________
lssconf-discuss mailing list
lssconf-discuss@inf.ed.ac.uk
http://lists.inf.ed.ac.uk/mailman/listinfo/lssconf-discuss
Sent from the lssconf forum at Nabble.com.
_______________________________________________ lssconf-discuss mailing list lssconf-discuss@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/lssconf-discuss
