by kishi on March 21, 2007 06:09pm
Impetus: This is the 19th year I have spent in the Information Technology business, out of which more than 15 were spent designing and implementing IT environments of various scopes, platforms and sizes. Among several similarities and differences between each implementation, a few constants always emerged, and my favorite of all:
Systems Manageability. This question always got asked during every high-profile design review meeting. You know the meeting I’m talking about, the one with the CIO and the IT Director are sitting across the table and asking how we’re planning on managing the environment. The main concern you could see in everyone’s expression was “what sort of manageability needs to be built around for operations and support ?”. So why does manageability matter ? Let’s start with what people imagine, when they think of Systems Manageability. It means different things to people in different roles: the Infrastructure folks imagine uptime and redundancy, the Developers imagine reliability, the Business Managers imagine efficiency. But the answer is so overwhelmingly obvious. Had it not been for systems management toolsets, apps and frameworks, ITPro’s and Admins would be worried sick about everything from uptime to reliability to scalability. So yes, manageability matters, a lot, because it’s the knowledge that “all’s well and running smoothly” that matters to everyone from a CIO to a Developer to a IT Admin.
Importance: Now that we have established the impetus behind why Systems Manageability matters, we should now address the importance tied to it, such as:
In the next seven blogs or so to follow, you will get a detailed breakdown on the Systems Manageability project that we have completed in the lab. We will be covering the Project Methodology and Project Ontology in my next blog. As always, send us your comments and feedback and THANK YOU for tuning into Port25.