Posted by: Mark Szynaka
Amazon EC2, Amazon Web Services, cloud computing
I attended the NYC OpenStack Meetup this week, which focused on understanding what place Amazon EC2 APIs should hold for OpenStack design and implementation. It was billed as the third round of the AWS API debate, with the first two rounds held on the West Coast. And this event did not disappoint.
The audience seemed more focused on enterprise applicability versus a theoretical discussion of AWS APIs. I suppose this was because these enterprise clients and IT bosses want to know if they can make OpenStack work with some of the rogue AWS implementations their companies already own.
Randy Bias, founding CEO, CTO and co-founder of Cloudscaling, was quick to point out the OpenStack community uses an OpenStack version of the Amazon Web Services (AWS) Elastic Compute Cloud (EC2) API already.
Attendee concerns centered on whether developers could depend on AWS to keep the APIs intact, so that if an OpenStack private cloud developer were to make a call to the API, they’re sure it will work. IT pros know that how much you rely on each of the public cloud APIs affects the portability of clouds. So, it was encouraging to hear AWS APIs are not being deprecated and, therefore, are reliable for multi-cloud architectures for the foreseeable future.
Randy Bias, Nati Shalom, CTO and founder of GigaSpaces, and Alex Freedland, CFO of Mirantis, all provided a healthy divergence of how they see OpenStack evolving and what is needed to strengthen the industry.
Freedland postulated that Moore’s Law applies to cloud computing; the acceleration of innovation and the financial impact to companies will drive cloud adoption, he added. Bias and Shalom took a more technology-focused, ‘If you build it, they will come’ view.
But all three speakers agreed there are two things driving the adoption of, or at least investigation into, the use of OpenStack in a private cloud: an IT manager’s desire to stay independent of any single cloud provider and the ability to interface any private cloud for resources they don’t want to build in-house.