Recap: Cloud Foundry Summit 2015, Day 1
Day 1 | Day 2 | Top 100 Quotes
This year, the Cloud Foundry Summit introduced a stronger focus on community diversity and closer collaboration between its ecosystem members. New partnerships, integrations, support for a broader technology stack, etc. Just like a year ago, we recap what was happening this Monday at the Santa Clara Convention Center, which was themed in the cyberpunk style.
Pre-game: CF Camp
For many of us, the Cloud Foundry Summit started a day earlier—on Sunday—at the CF Camp held by Dave Nielsen. A lot of legendary speakers could be met in the hall or during the unconference sessions.
This “warming” event was a good idea, it brought a lot of fun and useful debates at the same time. Browse through the #CFCamp hashtag, if you want to see its highlights.
Major announcements on Day 1
The conference itself kicked off with bringing some news and releases:
The CF Foundation has been joined by six new members: Apigee, Bloomberg, Cloudsoft, Huawei, Mirantis, and New Relic. Congrats, this brings the total number to 40+ companies!
HP Helion Development Platform has been enhanced with the .NET support. HP is also donating a sizable amount of code to the CF incubator (including Visual Studio Extension, MS Buildpack, .NET SDK for the Cloud Controller API, Windows-based DEAs, and a SQL Server service broker implementation).
ActiveState has released Stackato 3.6 with support for Docker images (called “Docker Apps”).
GE is launching an Industrial Dojo program (6–12 weeks) that allows developers to master Cloud Foundry by collaborating with other experienced CF engineers.
IBM established another independent CF Dojo at Raleigh (NC) and introduced new Bluemix services.
Pivotal and Mirantis announced a partnership aimed at delivering CF on OpenStack.
The opening talks of the summit focused on building a strong community and the cultural side of using Cloud Foundry. The first keynote was delivered by Sam Ramji, CEO of the CF Foundation. He spoke on how Cloud Foundry provides a choice of technologies and freedom to innovate.
According to Sam, we’re at “The Dawn of a New Era” and “continuous innovation.”
“Cloud Foundry can help organizations get off the ‘waterscrumfall’ syndrome” —Sam Ramji, CEO, CF Foundation
Angel Diaz (IBM) continued with a talk on the culture behind Cloud Foundry, covering the characteristics of a healthy corporate environment that promotes innovation.
According to him, a healthy CF culture is about:
- being aware of history without being beholden by it
- sharing information across all corporate levels
- asking the right questions with the right purpose
- changing results from client dialog
- fostering change, even if it means changing something considered “sacred”
“Combining code, community, culture in a single platform is key. No app can be an island” —Angel Diaz, IBM
Christine McKinley, a mechanical engineer, musician, and author, amused everyone with funny pics and brilliant geek humor. According to her, open source communities get right what governments and hippie communes have strived for.
“Day after the biggest drinking day of the year…Mothers Day” —Christine McKinley
Siki Giunta (Verizon) spoke about the maths of how Cloud Foundry impacts resource allocation in a large enterprise.
She noted that most cloud systems fail because of one of these three reasons:
- they become hard/impossible to operate
- they cannot run, embed, and build services
- they stop making money
A PaaS system adds a level of automation on top of IaaS, balancing many of its downsides. This helps to economize and/or find resources for more growth and transformation.
At the evening keynotes, Mark Interrante (HP) officially announced the deep Windows and .NET support added to HP Helion Dev Platform 1.2. According to Mark, 40-45% of enterprise customers are running on .NET.
After that, Andy Zitney (Allstate) shared why the company he works at—which is nearly a hundred years old—chose Cloud Foundry as the platform for change.
“We must be able conceive an app Monday and deliver it Friday…Innovate to avoid disruption.” —Andy Zitney
“CF delivers on what they say it does. You need a team of people around it to [make it hum].” —Andy Zitney
The keynote section continued with a panel discussion moderated by Sam Ramji. Andreas Wesselmann (SAP) and Jeroen van Rotterdam (EMC) discussed how Cloud Foundry helps ISVs to reduce costs and improve agility. Jeroen van Rotterdam noted that “when you reduce the marginal cost of new customers to zero, you’ve won over the business team.”
“The concept of a release is outdated.” —Jeroen van Rotterdam (EMC)
The final keynote by author Andy Weir told a story of how his bestselling book, The Martian, was open-sourced for the good of the community. Surprisingly, although it was out for free, people still wanted to pay money for it on Amazon.
“You can be an open source hippy and a money grubbing capitalist at the same time” —Andy Weir
It would be impossible to attend and cover all of the sessions presented at the CF summit. Still, here’s our pick of talks that our team liked and was able to attend.
Running Cloud Foundry at Comcast
Media giant Comcast shared their experience with running Cloud Foundry. According to Comcast’s engineers, a PaaS gives them the freedom to use their backend services. The first two services they created were Logger and Outbound Proxy. The main challenge they had was with custom URLs.
Comcast also provided some advice for would-be CF adopters. They suggest that when extending the platform, one should follow three principles:
- avoiding major dev efforts
- taking into account service life cycles (you need to maintain and support managed services)
Comcast’s cloud platform is based on three building blocks: OpenStack, CF, and Docker. As many other companies, they chose Docker because it provides portability and the right level of isolation.
The talk also touched upon the cultural side of Comcast’s transformation. Their major goals were to change the mentality of their teams and lower barriers for product development. Thanks to Cloud Foundry, a self-service model was introduced; so Comcast’s developers, engineers, and architects now work closer together.
Neville George, Sam Guerrero, Tim Leong, and Sergey Matochkin listed some of the tools that Comcast uses for managing CF, e.g. for proactive monitoring (see the slides).
Finally, the speakers explained how Comcast trained their developers to use Cloud Foundry.
Data Science on Cloud Foundry
Ian Huston and Alexander Kagoshima (Pivotal) spoke on how data scientists can employ Cloud Foundry to work with big data.
Alex Kagoshima suggests: “What you can do is to keep using your big data platform for analytics, Spark, etc. and use CF as visualization.”
Here’s the architecture of the prediction API:
How to deploy models to Cloud Foundry:
This session by Colin Humphreys (CloudCredo) and Marco Hochstrasser (Swisscom) was about the current issues with pushing services and data to Cloud Foundry.
According to Colin and Marco, many services—such as monolithic databases—are simply not made to work in the PaaS world.
This creates a number of challenges for service providers. For instance, there are concerns related to:
- PaaS readiness of existing service landscapes and their inability to scale horizontally
- operability and compatibility of existing and new services
- delivering new state-as-a-service(s) in a fast and dependable way
‘We need to address automation, scaling and durability to develop a cloud native data services framework in CF’ —@hatofmonkeys
Diego should be out of beta within Q3…Probably
Question from the audience: “We all know that all simple things tend to get complicated. How does Lattice not become a new CF?”
Onsi Fakhouri: “I don’t know. Let’s see where it goes.” (Smiling)
For the summit, Onsi even wrote a haiku about ‘cf push’:
“Here is my source code
Run it on the cloud for me
I do not care how”
Managing multiple clouds with a single BOSH deployment
Currently, one BOSH deployment can only work with a single cloud, but some companies need multiple, geographically distributed data centers and use different cloud providers. This means they have to install BOSH in each data center and use additional computing resources/team efforts to provide fault tolerance. This session by Alan Moran and Alex Lomov of Altoros elaborated on an architectural solution for extending the functionality of BOSH director and building BOSH plug-ins to automate deployments to multiple clouds.
Alan expained why one may want to use BOSH with many clouds, how BOSH works with an IaaS, and how to make BOSH work with multiple clouds.
The solution involves replicating a CF deployment, distributing workload through a GeoDNS, and deploying apps on both CF clusters—all with BOSH!
Service discovery on Lattice with Consul
Another session by Juan Pablo Genovese and Aleksei Zalesov of Altoros featured an overview of Consul, a fast and simple HA service discovery tool shipped with Lattice.
The second part was a demo where Juan Pablo used Consul to discover and bind a MariaDB service to a microservices app running on a Lattice cluster.
How to deploy your first app on Cloud Foundry
At the summit, there was also a hands-on demo of Cloud Foundry delivered by Dave Nielsen. He briefly showcased how to run “Hello, world!” on Cloud Foundry just in 30 minutes. During the session, Dave explained how to deploy a Web app to Pivotal Web Services or IBM Bluemix and then bind it to a database.
Dave is giving a deeper Cloud Foundry training on May 13, right after the CF Summit. As a sponsor of this training, Altoros can provide discounts to the summit attendees. To get one, visit us at booth #113 and ask for 25-50% off!
Ready for Day 2?
Other sessions were also amazing. Dr.Nic talked about version probs with CF, how OpenStack doesn’t work, spiff trouble, etc. James Bayer elaborated on how their team is working to get Lattice to work with droplets, not only Docker images. I wish we could attend everything!
That’s it for day one. Day two is already in progress and is also a blast. See you there!
Read all recaps: Day 1 | Day 2 | Top 100 Quotes
*All photos are courtesy of Altoros.