Biggest Private Cloud Deployment Threat: Your IT Staff
Your technologist-heavy IT staff won't help you find success with a private-cloud deployment. Here's why shifting to an IT service catalog approach may ease your transition to the cloud.
People are the No. 1 reason why private clouds fail. The traditional IT staff is a tactically driven, deeply technical group of hardware and software problem solvers who aren't familiar with strategic IT thinking and don't have time for it. They aren't accustomed to aligning IT processes with business drivers. They're more comfortable with explaining why something can't be done than finding a way to make it happen. And they will be the downfall of your private cloud deployment.
This isn't their fault. They're working in a world with enough fires to put out that they don't have time to be forward thinking. They're IT MacGyvers, keeping your disparate systems and technology silos running with minimal budgets. They're trying to keep enough abreast of the next big IT wave so they can try and surf it when it's dropped on them unexpectedly and without their input. They're an impressive bunch, but as it stands right now they will fail you.
Expertise, automation, and silo busting are all required, say early adopters of private clouds. Also in the new, all-digital Private Clouds: Vision Vs. Reality issue of InformationWeek: How to choose between OpenStack and CloudStack for your private cloud. (Free with registration.)
Multicloud Infrastructure & Application ManagementEnterprise cloud adoption has evolved to the point where hybrid public/private cloud designs and use of multiple providers is common. Who among us has mastered provisioning resources in different clouds; allocating the right resources to each application; assigning applications to the "best" cloud provider based on performance or reliability requirements.
InformationWeek Tech Digest August 03, 2015The networking industry agrees that software-defined networking is the way of the future. So where are all the deployments? We take a look at where SDN is being deployed and what's getting in the way of deployments.