In this three-part series, we look at what to consider in the early phases of a private cloud project. We already talked about virtualization, automation, self-service, and chargeback. In this last part, we will see how important it is to keep in mind subjects such as monitoring, compliance, backup, and security too.
In the “Rapid deployments with IBM SmartCloud Provisioning” blog entry, we have shown that virtual machines or appliances can be started and configured in a matter of seconds. It has never been so easy to create a virtual machine (VM), install software, and configure middleware. However, with great power comes great responsibility…it is now possible to create a VM, but what is its lifecycle? Will it be destroyed after being used, is the starting image deprecated, or is there a better starting image given the needed configuration and software install requirements?
Finding new movies is a matter of thinking of new workloads that could take advantage of the cloud in the context of your business issues. To start with, good candidates are new services that are resource-consuming and that are used temporarily to support our production services.
I really liked the post “Rapid deployments with IBM SmartCloud Provisioning” that explains how simple and fast it is to deploy instances using SmartCloud Provisioning. But after the instances are deployed the next questions are: How can I "easily" manage them from a patch management point of view? How can I "ensure" that they satisfy my corporate and security standards?
For the past several years, there have been discussions on how to best reduce data center costs. A study in 2011 by Clabby Analytics, an IT research and analysis firm, showed that almost 50% of the data center costs can be attributed to management labor, followed by costs associated with equipment.
Many, many years ago I was sent some test code for a very basic web interface allowing self-service requests for virtual machines, developed by a single VMware employee in his spare time; looking back, this was the first time I actually "did cloud." And I liked it because it was exactly what I wanted at the time – a simple way to enable, control, and streamline resource requests.
One challenge in many cloud environments is having the correct platforms available to build solutions. Many times, cloud providers provide a subset either of infrastructure as a service (IaaS) or platform as a service (PaaS) solutions that might or might not meet the business requirements of a given application.
Three years ago, when everybody started talking about cloud computing, every application and system seemed to be a good candidate to be migrated to the cloud. It was a time when few really understood the implications of migrating business applications and data to the cloud… or maybe the hype of cloud computing eclipsed any possible drawback.
This is the second part of the IBM SmartCloud Enterprise+ blog entry with details about the service offering, features and functions, migration strategy to move workloads into the environment, and more interesting things that IBM is planning to add in the near future.