Monday, May 7, 2007

Configuration management requirements

I seem to be working on several configuration management projects at once. Everyone uses a different set of scripts, or tools. No one has any documented information about what they are solving with the systems, and what they want to do. They seem to have started with the "backup the configuration of x" requirement, and evolved into:

  1. Monitoring (Error detection, service outages, checking for known problematic conditions)
  2. Capacity management
  3. Reporting

The issue without having any documentation of what the systems intended uses are, as well as current uses would make standardizing on software much easier. I'm battling trying to accomplish this, and it's very slow and painful. I think authority will help force changes, which should start to happen here.

No comments: