Christoph Maser wrote:
>
>>>> But will the tool do these changes for me?
>>> The tool will do anything you tell it to, it's a generic tool.
>> OK, but if I have to write the script, why wouldn't I just write the
>> script my way and automate it over ssh which already works instead of
>> learning some new language and having to install some new agent
>> everywhere to run it?
>
> Just a small real life example. Every now and then we find that some
> webservers on our farm do not have a specific sysctl config set (tcp fin
> timeout). If you fix that with an ssh loop or mussh you have it fixed
> now, just until you add a new server to the farm month later. If you use
> a management tool it will find that this particular server belongs to
> the farm and should have it set, does it for you and activates it. How
> do you do that with manual interaction?
If I wrote the script I would either have set it up to run regularly
with a list of targets where it is needed and add new members to the
list as appropriate or I'd add the setup to our stock images so it
wouldn't be needed as a special case. But in my experience, the kinds
of things that need time consuming configuration aren't that predictable
ahead of time. What do you do when they relate to the switch where
something is connected or something other than the group you've put the
server in?
--
Les Mikesell
lesmikesell at gmail.com