Summer’s almost over – time for less sun and more clouds!
I’ve gotten a lot of client questions recently about how to get started building their private clouds. Their vendors are at their doorstep hawking private cloud computing. Clients are asking about what technologies to use, which vendors to choose, how to build one, etc. I say, “Whoa!”
We’ve got to get our IT people to stop thinking about products and technologies and even architectures first, and instead to focus on understanding their service requirements first.
Start by understanding your service catalog (most organizations don’t have one), understand the SLAs and costs for each service (most don’t know that, either), build strategic plans for each of those services (does anyone have this?), determine which ones might go to the cloud in the future and when that cloud service will be “ready” (OK, this takes some work), make your ROI decision about building a private cloud service, and then you can start looking at architectures and products and technologies.
There has been an awful lot of definitional talk about cloud computing and private clouds for the past year. Time to move on. My cloud research at Gartner is focusing on case studies, roadmaps, and best practices for private cloud computing – and debunking the incredible amount of vendor hype that is hiding some real value in this trend.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.