Published:
November 22 2010, 09:45 AM
|
5 Comment(s)
by
Marvin Waschke
What is the simplest, most common IaaS (Infrastructure as a Service) public cloud scenario? Will it be the same a year from now? Five years from now?
These are important questions because the infrastructure that will support these scenarios is being designed today. If we don't understand where computing is today, we won't be able to plan accurately for tomorrow. And our vision of tomorrow must be as accurate as we can make it in order to design infrastructure that does a good job of supporting cloud computing in the future.
There is a tremendous amount of thought about applications that automatically "cloud burst" from the on-premise data center to a public cloud, and folks are planning for the day when entire on-premise data centers are replaced by public clouds, but this is mainly long-range strategy, not what is happening in the data center today.
Today's Successful Public Cloud Projects
Today, we hear from IT departments that the cloud has tremendous potential, but many are still cautious about the idea of public clouds. They are wary of the security and regulatory issues arising from mission critical services implemented on public clouds, but IT shops still are striving to gain cloud IaaS computing experience. One method is to try out public cloud services like Amazon EC2 with lower risk projects.
For instance, the CA Service Desk Manager (SDM) product group recently conducted a successful beta test program using Amazon EC2 for IaaS. In the "BCE" (Before Cloud Era), beta software had to be installed on the customer's premises. That was not ideal because the beta tied up resources that the customer was often loath to give up.
For the SDM team's latest beta program, customers had the option of deploying the beta software on EC2. Since beta installations are expendable and are not subject to the privacy and security issues of a full production-level service desk, there was little resistance to using public cloud resources for testing. A substantial number of beta tests were performed on the public cloud and the program was quite successful because it was both economical and it effectively exercised and displayed the beta code.
IT pros are also trying lower risk projects that involve testing and development. The generally accepted best practice for transitioning IT services to production is to exercise all changed software in a test environment that mimics the production environment before transitioning software to production. This applies both to applications developed in-house and software obtained from software vendors. This kind of testing can involve vast computing resources for relatively short periods.
Instead of purchasing or leasing test equipment, using a public cloud for a few hours at a time can be quite attractive financially. Entire development projects can be developed and tested without purchasing equipment that may only be used temporarily. The security and governance risks during development and testing are much more easily managed than the risks involved in production.
Private Clouds as a Bridge to Public Clouds
Private clouds are another way in which IT departments are venturing into cloud computing. By setting up a private cloud, an enterprise can become familiar with cloud facilities with fewer worries about regulators and auditors.
All equipment and data remains on-premise and under control of the enterprise, but only the team assigned to administer the private cloud need be aware where processes run and data is stored. Resources in the private cloud can still be allocated and administered with many of the efficiencies of a public cloud, but security and governance issues remain similar to those in force before the private cloud was developed.
Many virtualization projects could be described as "private cloud building" and our colleagues from the virtualization team have covered this topic - virtualization as a path to the cloud -- at length on the CA Virtualization & Automation blog.
The Future
Eventually, the security and governance issues surrounding the public cloud will be tamed and IT departments will find that the experience they have gained with lower risk IaaS projects and private clouds will stand them in good stead. There are many signs that questions over cloud safety are being answered.
The Cloud Security Alliance (CSA) has published a second version of its document on security and governance, which has gained recognition as a careful study of the security and governance issues involved in using the cloud and is resulting in a growing body of cloud best practices.
ISO efforts, including ISO/IEC 27001 and ISO/IEC 27002 certification of cloud service providers, are also helping to build confidence in the cloud among auditors and security analysts.
These, and many more advances, point to a growing wave of acceptance of cloud computing. The more experience IT departments can obtain today, the better prepared they will be to implement more critical services taking full advantage of the cloud when the time is right for them.
*Photo used under Creative Commons License, courtesy of swisscan.