The current large computing enterprise is complex and difficult to manage. Architecture can help ... Part 2 highlights the current situation.
Current Situation:
I suspect that many large IT shops are struggling with the same problems, which may include some/all of the following components in their enterprise.
- There are multiple hardware devices (rack servers, blade servers, switches, AP's, storage frames, NAS, SAN, appliances, desktops, workstations, laptops, small form factor devices, etc.) in the enterprise. All these devices run firmware/software that is not perfect and need to be managed.
- Applications are tightly coupled to the platforms. This dependency needs to be understood and managed. The idea of a CMDB is appealing, especially where relationships can be defined and used.
- There are hundreds of applications in the enterprise. Most of these applications were created, optimized and supported by specific teams or a Line of Business. Integrating these applications into the enterprise is difficult.
- There are confusing/mixed operations models (some centralized, some distributed, some vertical, some horizontal, some a combination, some changing).
- The desire for standard business processes in IT is high. ITIL appears to be a reasonable model to follow. Business processes (similar to applications) have historically been locally optimized and need substantial adjustment for the enterprise. This is complicated and difficult.
- Enterprises implement a combination of vendor manageability products, "frameworks" (not really), point solutions and a lot of home-grown and/or open-source code. IT is the integrator of last resort.
Introduction of the "Relevance of Manageability & Automation Architecture" topic: http://communities.intel.com/thread/1564
" Part 1 - Observations" is posted at: http://communities.intel.com/openport/blogs/proexpert/2008/05/14/relevance-of-architecture-part-1-observations


