Home > IT Blogs > Adventures in Data Center Automation > Next pass on Data Center Automation “Blueprint”
>>VIEW ALL POSTS  

Adventures in Data Center Automation

«
»
Dec 17 2007   5:59PM GMT

Next pass on Data Center Automation “Blueprint”



Posted by: Ryan Shopp
Application monitoring, CMDB, DataCenter, eTOM, FCAPS, IT Process Automation, ITIL, Network monitoring, Performance management, RBA, Run Book Automation, Security, Storage, Systems monitoring, Systemschannel, Virtualization, WAN optimization

Thanks for the feedback, I’ve incorporated some points that have been made into an updated version of the Data Center Automation Blueprint (DCAB).

data-center-automation-blueprint2.jpg

As mentioned previous this is a work in progress and I love getting feedback, ideas, concerns etc. with the model. As mentioned previously I’m trying to build a functional model (at the 30,000 foot level) that represents key software functionality to automate the data center towards someday becoming “lights out.”

Also, with that said, it needs to be comprehensive but not overwhelming. I want to keep the yellow DCA functional areas limited in number…if this grows to be much more then the current six I feel it becomes too complex. So to add any new areas I need to assess how do they compare to the current areas and could I combine any areas.

One I’m struggling with right now is I’ve received feedback that analytics itself is an area. The interesting thing is analytics currently fits to some degree within each of the 4 horizontal functional areas (e.g., Configuration/Change, Security/Protection) as each of those products offer advanced reporting and as that progresses they do predictive reporting and analytics around that functional area.

Analytics would also show up at the dashboard level (currently beyond the scope of what I’m defining as the functional areas of the Data Center Automation Blueprint) where you would correlate business intelligence, patterns etc. across not just Data Center Automation functional categories but also across manual task orchestration (e.g., service/help desk) details.

Thoughts?

One more thing to clear up, I know some (many) of these functional categories and their products extend beyond the Data Center. The lens this blog looks through is exclusively focused on the challenges posed by large, complex data centers. For example, I know performance products are also useful in all sized companies (big & small) and also beyond the data center (e.g., headquarters, remote offices, partner networks, etc).

  Bookmark and Share     Comment     RSS Feed     Email a friend

Comment on this Post

Leave a comment:

RStreu  |   Dec 19, 2007  5:02 AM (GMT)

Hi Ryan,

You’ve been busy! Good information – keep up the good work.

Since this is a continuation of the another post on the categories, I’ll respond here.

Virtualization is disruptive. It is important to recognize complete shifts in paradigms. I think Virtualization is a game changing event in IT that simplifies many tasks (which isn’t all good by the way) and complicates others (ex: troubleshooting). It’s your model, so, I’ll leave it to you…it is more of a theme or thread that runs through and impacts everything.

In terms of the skill set required, I agree there is a difference skillset (and thus level of skill/individual) required to perform the tasks you mention. However, I was trying to convey the relationship of Configuration to the other aspects. There is only one reason something is available, performant, secure, etc. — you are serving up a configuration that results in those things. The complexity of the configurations is increasing in many ways which complicates many of the other functions. What “part” of the stack is unavailable? It isn’t the simple “ping” it used to be….

Help Desks are evolving as is the role and skill of the people responsible. I’m an ex IT guy. The help desk people used to have very little value and skill to an oranization. That is NOT the case today. When moving to a Service Desk model and adopting process models like ITIL, these groups are getting very senior and skilled IT folks that understand the broader Service Delivery model. The game is changing…

Okay, now my view on Analytics. In terms of where it should and could be applied, it most definitely spans both the functional ares as well as the Infrastructure categories. That is the whole idea. Take data that would traditionally be in a silo and put it together in a way that begins to see how they ***relate*** to each other. How does my CM change/process impact security, performance, availability…and how did that impact my ability to respond (service desk, etc). True analytics looks for how people respond to technology including how the process responds…very, very cool and compelling stuff.

Yeah, I’m a bit passionate and opinionated about this! :-)

Merry Christmas and Happy New Year.

Randy


 

RStreu  |   Dec 19, 2007  5:07 AM (GMT)

Okay a few more thoughts: first, I should use a spell checker!

Analytics holds a promise of so much more. It should be able to pinpoint the most important “things” (config, people, process) that are the difference in how effective IT really is (cost, availability, security, etc). What is the determining factor…across all this big mess that is my IT infrastructure…that is most important in determining which service is more available? Etc… Very cool space with mature technology that has never been applied to understanding IT complexity…


 

Ryan Shopp  |   Dec 19, 2007  7:52 PM (GMT)

Again, great feedback! Thanks for you thoughts and passion. Virtualization is disruptive and many more threads and pondering will be going into how/if their is a better way to showcase in the blueprint. Same goes with Analytics. I need to do some more research and reading but fundamentally agree their is something to be said about leveraging patterns/trends/details across technology & functionality silo’s to help enterprise architects, director level executives and up more efficiently solve problems and make decision that are more in line with strategic/business objectives. Keep the feedback rolling. Anyone else out their with an opinion?