Home > readwriteweb > Choosing a Private Cloud Provider and Doing it All Wrong

Choosing a Private Cloud Provider and Doing it All Wrong

February 27th, 2011 02:00 admin Leave a comment Go to comments

snow patrol:make this go on foreverThere’s a right way to choose a cloud provider and there’s a wrong way. The right way is to do the research about your needs and requirements. The wrong way is to choose a provider by evaluating and comparing vendor offerings.

John Treadway writes on CloudBzz that IT leaders he speaks with are taking the latter approach. They’re evaluating the vendors and not doing their own analysis.

Instead, IT leaders should be going through a long list of questions before starting to evaluate vendors. His initial list gives a taste about how IT leaders should approach the task:

  1. What are the strategic objectives for my cloud program?
  2. How will my cloud be used?
  3. Who are my users and what are their expectations and requirements?
  4. How should/will a cloud model change my data center workflows, policies, processes and skills requirements?
  5. How will cloud users be given visibility into their usage, costs and possible chargebacks?
  6. How will cloud users be given visibility into operational issues such as server/zone/regional availability and performance?
  7. What is my approach to the service catalog? Is it prix fixe, a la carte, or more like value meals? Can users make their own catalogs?
  8. How will I handle policy around identity, access control, user permissions, etc?
  9. What are the operational tools that I will use for event management & correlation, performance management, service desk, configuration and change management, monitoring, logging, auditability, and more?
  10. What will my vCenter administrators do when they are no longer creating VMs for every request?
  11. What will the approvers in my process flows today do when the handling of 95% of all future requests are policy driven and automated?
  12. What levels of dynamism are required regarding elasticity, workload placement, data placement and QoS management across all stack layers?
  13. Beyond a VM, what other services will I expose to my users?
  14. How will I address each of the key components such as compute, networking, structured & object storage, virtualization, security, automation, self-service, lifecycle management, databases and more?
  15. What are the workloads I expect to see in my cloud, and what are the requirements for these workloads to run?

Treadway says IT leaders are letting the tail wag the dog. We can see how that can be the case. It seems logical to do the research first. But this may not be about the right choice as much as it is about the economical one for the business. That’s a problem. Vendors will offer all sorts of incentives to get your business. That can lead to trade offs that can really hurt down the road.

Source: Choosing a Private Cloud Provider and Doing it All Wrong

Related Articles:

  1. What Happens To Data When a Cloud Provider Dies?
  2. Your Cloud Provider (Probably) Isn’t Spying On You
  3. VMware Buys Cloud-Based IT Management Service Provider Shavlik Technologies
  4. Ask Slashdot: Which Encrypted Cloud Storage Provider?
  5. Cloud Database Provider MongoLab Raises $3 Million From Foundry, Baseline, And Others
blog comments powered by Disqus
YOYOYOOYOYOYO