During his keynote speech, Kemp articulated one of the core visions held by OpenStack enthusiasts: It can be a ubiquitous platform used by both enterprises to deploy private clouds and service providers to launch public clouds. If both those sides use OpenStack to build their respective clouds, Kemp argues that allows for interoperability between the two that is not available in the market today in an open source framework. If OpenStack embraces that, he says the marketplace of users and vendors using the platform will be too big for even the market-leading cloud providers to ignore. "We can tell Amazon what to do, instead of the other way around," he says.
Not everyone is buying that vision. "It's not so straightforward," says Krishnan Subramanian, analyst at Rishidot Research and cloud blogger who's attending the event. "It's not a given," he says that two OpenStack vendors will inherently have interoperability between their systems. Vendors within the OpenStack community need to work together for their users to be able to migrate workloads across the disparate systems.
Kemp says that will come. The features and functionality around security and customized components of enterprises' private cloud needs to be replicated in a public cloud for enterprises to truly embrace the cloud. OpenStack, he says, is the way to do that.
The key, he says, is focusing on the users and the applications that will be run on OpenStack. Enterprises in the future will not run all of their applications on a single framework, they will instead use multiple infrastructures and platforms. OpenStack has to not only support those, but integrate features that users care about but aren't yet developed in the code. High availability, easier usability and cloud monitoring are some of the projects in the que for future development. If OpenStack is able to embrace this vision, Kemp says it has the opportunity to be the cloud architecture for the future.