Hi
Earlier in the thread I promised to send a link for the cobbler code I
wrote... so here it is.
https://github.com/gjngeldenhuis/stuff
please ignore the very imaginative git repository name... :D
It should be lightly documented.
Regards
On 31 January 2012 16:46, Michael DeHaan <michael.dehaan(a)gmail.com> wrote:
My view is basically that you have three entities:
OS setup -> Config Setup -> Monitoring
The thing that owns OS setup also owns the way that control is transferred
to the next, similar to the way that many configuration tools can also help
you set up monitoring. They don't own monitoring, but they own the setup
of the next tool in the chain
( cobbler: OS setup -> ) (config tool: Config Setup -> ) Monitoring
Each tool owns the arrow that sets up the next.
But to do the thing with each tool, you go to tweak the tool that can best
tweak itself, rather than working through a little tiny porthole and making
it harder.
Bad analogy -- suppose you have a car. You can either drive the car or
you can tell someone else how to drive the car, but it will never be as
immediate as driving the actual car. My first analogy would have been
with analog synthesizer knobs vs MIDI commands in a Digital Audio
Workstation but that might not work for everyone :)
--
Gerhardus Geldenhuis