The new face of Cloud Foundry
The whirlwind of announcements presented at this week’s Cloud Foundry Summit Europe 2016 prompted many attendees to say that Cloud Foundry has changed greatly. As Abby Kearns, Cloud Foundry’s Vice President of Industry Strategy told JAXenter, the only thing Cloud Foundry took from founder Chris Richardson is the name.
Sam Ramji, CEO of Cloud Foundry took the stage in Frankfurt am Main, Germany and explained the role of Cloud Foundry. He also pointed out that “open source is a positive-sum game” and revealed that platforms drive network effects. Ramji concluded that Cloud Foundry is the place where users, developers, providers and operators can coexist and thrive.
Attendees had the chance to learn more about what’s under the hood of Cloud Foundry, but one topic that kept popping up is BOSH, an open source tool chain for release engineering, deployment and lifecycle management of large-scale distributed services. In short, its goal is to unify release engineering, deployment, and lifecycle management of small and large-scale cloud software. Although BOSH was developed to deploy Cloud Foundry PaaS, it can also be used to deploy almost any other software (including Hadoop).
Alexander Lomov, Cloud Foundry Engineer at Altoros, explained the idea behind BOSH and offered a sneak peek at BOSH 2.0, which will include availability zones, global networking (no more static IPs in manifest), cloud config and links.
BOSH allows individual developers and teams to easily version, package and deploy software in a reproducible manner. Developer/operator communities have come far in solving similar situations with tools like Chef, Puppet, and Docker. However, each organization solves these problems in a different way, which usually involves a variety of different, and not necessarily well-integrated, tools. While these tools exist to solve the individual parts of versioning, packaging, and deploying software reproducibly, BOSH was designed to do each of these as a whole.
“Companies should not worry about infrastructure”
JAXenter talked to Abby Kearns, Vice President of Industry Strategy at Cloud Foundry, about Cloud Foundry’s strategy, innovative aspects, and the purpose of the Cloud Foundry Foundation. She pointed out that Cloud Foundry solves a complex problem; it takes the features that you need and puts them on a single platform that you previously had to build yourself. Being able to integrate everything into a single solution which is easily managed is one thing that makes Cloud Foundry innovative.
“Automation is essential,” Cloud Foundry’s Vice President of Industry Strategy emphasized. It brings speed and infuses organizations with power simply because it doesn’t take 18 months to put the product into the customer’s hands anymore. The goal of Cloud Foundry is to make sure companies don’t have to worry about infrastructure anymore.
The Cloud Foundry Foundation is forever going to be open source
The Cloud Foundry Foundation aims to be the best platform for many years to come. One of its main benefits is the fact that “it is forever going to be open source” — it cannot be absorbed by a for-profit company, so “no one can take it and transform it into something that it’s not.”
Kearns also mentioned that platform certification (there are currently 11 certified providers) refers to the ability to run on any could, anywhere. Two of the perks that go hand in hand with platform certification are the lack of lock-in and plenty of flexibility. Cloud Foundry will continue to invest in that ecosystem.
Pair programming at its best
Pair programming represents a massive part of Pivotal’s identity so many keynotes and talks focused on the perks on this technique. Pivotal CEO Rob Mee emphasized that the No.1 skill he is looking for when hiring developers for pair programming is empathy.
In the How Cloud Foundry Dojo Experience talk, Michael Trestman, software engineer on the BOSH core team at Pivotal Cloud Foundry and Cornelius Schumacher, engineering manager in the cloud and systems management department at SUSE Linux, presented the benefits of pair programming such as getting to know every member of the team faster and learning new skills (including soft skills). The duo also pointed out that one needs to be open to like pair programming, but being humble and fearless are also a must.