Last Thursday, Piston Cloud (Piston) and Pivotal announced a partnership whereby Piston will deliver the community OpenStack infrastructure for Cloud Foundry. The partnership enables Pivotal to continue refining the integration of Cloud Foundry with OpenStack that Piston achieved last year. Thursday’s announcement means that Cloud Foundry’s developer ecosystem will be tightly integrated with Piston’s OpenStack distribution in order to ensure the resulting IaaS-PaaS, OpenStack-Cloud Foundry infrastructure successfully negotiates challenges related to continuous integration, rapid release cycles and scalability considerations. Piston’s co-founder and CTO, Joshua McKenty, will serve on the Cloud Foundry Advisory Board and Piston will continue to function as a partner for rapid deployments of Cloud Foundry.
James Watters, the head of product, marketing, and ecosystem for Cloud Foundry, remarked on the work specific to the integration in an interview with The Register by noting, “there’s a fair amount of work to make sure an IaaS and a PaaS like Cloud Foundry that automates itself through APIs all flows together very well” and that “every hour of every day Cloud Foundry gets tested on Piston.” Meanwhile, Joshua McKenty identified some of the integration issues that the partnership proposes to examine as follows:
We actually did most of the work to make sure Cloud Foundry could run on OpenStack last year. It’s not a tremendously complicated API, but it is important that it’s consistent and reliable. One of the things we’ve really focused on with Piston OpenStack is making sure the services are highly available, so as you scale up the scope of the Cloud Foundry environment on top, the IaaS environment can handle it.
Here, McKenty singles out the consistency and reliability of the Cloud Foundry API and the scalability of the OpenStack infrastructure in relation to the Cloud Foundry platform as topics for investigation. In a guest blog post for Cloud Foundry, McKenty further noted that Piston’s aim is to “to keep up with and continue to support the growing Cloud Foundry ecosystem” given that the fundamental goal of cloud computing is “really just about providing the computing resources to keep up with the fast-paced DevOps and Agile lifecycle.” In other words, Piston intends to “keep up with” Cloud Foundry not only from a scalability perspective, but also in the context of its rapidly evolving, agile-driven code base and enhancements.
Overall, the partnership represents a huge coup for Piston given that it was hand-picked from the cottage industry of OpenStack vendors and distributions. More importantly, however, the announcement underscores the weight of the market momentum in favor of open-source based cloud computing platforms. Moreover, Thursday’s partnership increases the commercial viability of Cloud Foundry insofar as it was motivated in part by customer requests and interest. The industry should expect McKenty to bring his expertise in OpenStack governance to Cloud Foundry’s emerging governance structure and help drive a rapid expansion in Pivotal’s partnering companies and organizations with respect to Cloud Foundry. As the integration between OpenStack and Cloud Foundry matures courtesy of the Pivotal-Piston partnership, we may even see the evolution of a formal collaboration beween OpenStack’s governance structure and Cloud Foundry’s emerging model of governance and open source software leadership.