by kishi on April 06, 2007 04:14pm
In my last blog called “Why Manageability Matters” I talked about why we chose to work on “Systems Manageability” as a whole and get a grassroots understanding of it within the context of Linux and Open Source space. In this blog, I’m going to address the Methodology and Ontology of the Systems Manageability project. This will shed immediate light on how we approach, design and implement projects in the OSSL. Let’s start with the main goals and purpose behind the project.
I. Systems Manageability Project Goals:
Once we defined what we needed to get into, yet another realization dawned on us, which was the sheer size and volume of the data and information that was staring at us in the face. Let’s just say “overwhelmed” was a mild word compared to what we were looking at. My colleague, Steve Zarkos and I immediately realized that it was time to trim the scope of what we were doing and limit ourselves to what’s achievable in three months and with two people J. This called for drawing up what we considered to be “out-of-scope”, which was:
III. Systems Manageability Project Methodology:
The approach taken for the project was simple and scientific. The project was divided into three stages:
IV. Systems Manageability Project Ontology (classification):
The hardest and most challenging aspect of the project was to develop some sort ontology, characterization or classification of the manageability technologies prevalent in the IT environments today. The diagram below represents the overall "buckets" defined as part of this exercise. Each section of the diagram is broken down to provide a detailed breakdown of each of these Systems Manageability classifications represented:
In the next blog to follow, I will break down the first segment of ontology i.e. “Provisioning and Deployment” and discuss our research with all of you. Meanwhile, we always look forward to hearing from you, our audience and urge you for any feedback you may have about the topic. Thank You for tuning into Port25.