And that’s a wrap!
This week flew by — almost as quickly as the direct flight from San Francisco to Frankfurt. We had the opportunity to interface with so many members of the Cloud Foundry community in a spectacular event space and left Summit with a renewed appreciation for our unique culture, dedicated developers, inclusive attitude and visionary ambition. Speaking of which, what was the buzz word on everybody’s tongues today?
Atos’ Ursula Morgenstern gave a thought-provoking keynote speech on the need for diversity across all industries, asking the audience to consider whether cloud as a sector will be the catalyst for greater diversity in IT.
…or Tuesday morning, if you’re reading this in North America.
The last two days have been a flurry of announcements, fascinating talks and countless opportunities to engage with other members of the Cloud Foundry community. Let’s take a look back at Summit so far:
Memberships & Certifications
We announced that five new members have joined the Foundation, including:
Yesterday we posted the first half of a Q+A with this year’s Unconference emcees, Sara Lenz of anynines and Paula Kennedy of Pivotal. Don’t forget to join the Unconference on Monday, September 26 at the Cloud Foundry Summit in Frankfurt, starting at 5:00 pm. If you can’t make it to Frankfurt this year, follow along here to stay up to date on Summit news! Don’t forget to join the live conversation the entire week using the hashtag #CloudFoundry.
In addition to emcees Paula and Sara, Director of Product Marketing at HPE Cloud Amy Frampton will emcee Cloud Foundry Summit Frankfurt on Tuesday and Wednesday.
We’re counting the hours to Cloud Foundry Summit in Frankfurt, kicking off with the Unconference on Monday, September 26 at 5:00 pm. This year’s Unconference will be hosted by two exceptional women, Sara Lenz of anynines and Paula Kennedy of Pivotal. We sat down with both of them to learn about their relationship to Cloud Foundry and the community, their experiences as women in a male-dominated industry and what they’re looking forward to at Summit!
Left: Sara Lenz, anynines; Right: Paula Kennedy, Pivotal
Based in Berlin and an active member of the Cloud Foundry community, Sara is project manager of the anynines team, responsible for customer relations, and all organizational project processes concerning anynines.
When it comes to private cloud deployments of Cloud Foundry, OpenStack is often the infrastructure of choice. The OpenStack ecosystem is vibrant and growing, and for an installation, there is a huge number of projects to choose from. Each project comes with its own set of configurations. That’s why OpenStack validation for Cloud Foundry is something that has to be done on each installation. A certification of distributions would not be enough. Many people who wish to install Cloud Foundry on their OpenStack installation ask the same question: “Will it run on *my* OpenStack?”
Read more →
Does Cloud Foundry work with containers? According to this video from the Cloud Foundry Foundation, containers are “part of the platform’s DNA.”
For those just getting started with Cloud Foundry and containers, we’ve put together an overview on different types of container implementations and how they might be used.
Until recently, Warden was the main container implementation used in Cloud Foundry. Docker is another option to easily and efficiently manage containers. That’s why a lot of effort has been put into enabling support for Docker in the Cloud Foundry Diego runtime.
Here, we briefly compare Warden and Docker, as well as explore the internals of Garden—the current container back end in Cloud Foundry.
In our earlier blogs, we had described how to build and deploy BOSH and how to build and deploy cf-release on OpenPOWER systems, an alternative processor architecture based on IBM POWER systems. In this blog, we will describe how to build and deploy the Concourse continuous integration service as a BOSH release to OpenStack on OpenPOWER systems. Concourse installation steps with BOSH documented here need just OpenPOWER specific releases and resources to deploy on OpenPOWER. We are providing a base Concourse release which contains four resources – git-resource, time-resource, archive-resource and docker-image-resource as Docker images. The list of supported resources and additional custom resource types can be built using Concourse pipelines.
Interest in containers reached a broad audience nearly two years ago. My, how time flies! Since then, adoption has been, well, up and to the left.
Today, Cloud Foundry is announcing it’s retiring its legacy DEA backend in favor of Diego, which is rapidly approaching the scale of 250,000 containers in a single cluster.
Why should you care?
Consider the iPhone. When you first purchased one, it was likely an 8gb phone. Chances are, you thought you’d never use all the space on that phone. Chances are you were dead wrong. Fast forward to last week’s iPhone 7 announcement. Max size for those devices was 256gb. If you’re anything like me, you probably plan to order the largest capacity device available, just to be safe.
Cloud Foundry’s next generation runtime, Diego, is production ready and has been running production workloads since October 2015. Work to increase its scalability substantially past that of the DEAs is nearing completion. After this work completes we will be phasing out support for the DEA, Warden, HM9k, DEA Logging Agent, and Collector components. In this document, “DEAs” will be used to stand for all these components.
Though the specific date is subject to change, we expect Diego to meet its scaling targets of 250,000 containers spanning 1000 Cells during Q3 of 2016. This is being accomplished primarily by transitioning Diego from etcd to a relational database (Cloud Foundry’s HA MySQL database by default, though postgres is also supported).
As the world grows evermore connected with IoT devices, the demand for developers in the industrial space is poised to skyrocket. Cloud Foundry Foundation CEO Sam Ramji sat down with OZY reporter Renee Morad to discuss the potential for a devastating “cloud skills gap” that comes as a result of a predicted 50 billion connected device — just four years from today.