{"id":635,"date":"2014-08-27T07:31:21","date_gmt":"2014-08-27T07:31:21","guid":{"rendered":"http:\/\/www.coffeescroll.com\/?p=635"},"modified":"2014-08-27T07:31:21","modified_gmt":"2014-08-27T07:31:21","slug":"how-fix-private-cloud-part-5","status":"publish","type":"post","link":"http:\/\/www.coffeescroll.com\/index.php\/how-fix-private-cloud-part-5\/","title":{"rendered":"How to fix your private cloud – Part 5"},"content":{"rendered":"

In parts 1-4 of this blog series<\/a> we explored some reasons why private clouds bombed. In this final blog, I’d like to discuss a better approach<\/p>\n

Finding examples of successful private clouds is difficult because many organisations claim to have a private cloud when in fact all they have done is install VMware. If a project manager has to organise a resource to install something it’s not a cloud. Cloud is not virtualisation.<\/strong><\/p>\n

If you were starting a private cloud environment build 3 years ago, it would look different to one you would begin building now. But I like to live in the here and now so let’s look at what we would do now.<\/p>\n

For starters, reverse these unspoken principles:<\/p>\n