If you believe enterprise adoption is the next wave of cloud adoption, then these organizations have huge salesforce’s with deep customer relationships and services organizations capable of assisting enterprises with the transition to cloud. They have knowledge on the workload profiles that are the essential first step in determining what in the enterprise is suited to cloud deployment.
Many of the workloads running on the infrastructure of these vendors would require significant re-architecting to take advantage of the cloud. These workloads would most likely be the trailing adopters with the more urgent being redeveloped on a new infrastructure platform. If my previous employer (Sun Microsystems) grew up as the platform of choice for the Internet, then Redhat grew up in the era of the commodity architectures made famous by google and the social networking phenoms. Redhat technology (Linux, JBoss, etc..) supports a large number of the more modern application workload that are suitable for cloud deployment. They are not to be underestimated.
What I am looking forward to is some good discussion on the Aeolus Project, “delta cloud” and cloud engine. Its the clouds best kept secret, and you can find a good overview at the Redhat Cloud Blog. Its the vision of “many clouds” and its importance to the future of cloud computing. Redhats API approach is trying to solve the problem by trying to gather a community around the interoperability API vs. building portability into a product or development of standards. I think this is a valuable approach.
Why is “many clouds” important ?The events of April 21st had me thinking about this more over the last few days.A multi-vendor solution as assurance against failures like the one at Amazon Web Services is one use case, but its certainly not the most interesting. The seamless movement of workloads across many clouds will shape the future of cloud services.
- Portability/Lock-in – reduce the barriers to adoption associated with fear of lock-in to a single vendor. Portability also reduces switching costs which creates greater price/function competitiveness, reducing overall customer costs.
- Unification – for enterprise, its quite possible you have already deployed multiple flavors of virtualization technology. Some KVM, RHEV, some Hyper-V, Xen and some VMware. You will want to consolidate these into a single automation framework to preserve your investment in OS images and software stacks.
- Federation - if you look at global infrastructure providers or even service organizations, you will often see different providers having different strengths in different regions. Just the regulatory, cost, political, language, cultural differences alone ensure this is inevitable. Companies might adopt different providers in different regions to leverage those strengths. Creating a federated solution of different providers in different regions is a essential solution for these companies.
- Hybrids – private clouds often have some limitations is workload elasticity and resource pooling. The ability to leverage hybrid cloud solutions will be a useful solution to minimize these limitations.
- Disaster Recovery - related to hybrids and Multi-Provider availability, it provides a practically implementable solution. A bridge between private and public clouds to enable hot even better rapid scaling “warm” disaster solutions.
- Multi-Provider Availability – finally we reach the “Amazon Effect”. A push to eliminate single vendor point of failure through the use of multiple clouds in your solution. For me, the complexity this type of architecture far outweighs the benefits that can be obtained (sort of like having a two node cluster with one linux and one solaris node).
If you are @RedhatSummit and want to talk cloud, virtualization & smart infrastructure. Come visit at booth #211 in the exhibit hall.
Contributed by: Brad Vaughan