Cloud Foundry Summit Europe 2016

In this tutorial, Sufyaan Kazi and David Pinto will walk attendees through the architecture of a Stock Trading application which has been built as 5 distinct Spring Boot Microservices. They will also give attendees a walk through of how to deploy these Microservices to Cloud Foundry to create a highly available resilient application and how to utilise features such as binding apps to a database, using a Configuration Server to store config external to an application, using Service Discovery to avoid hard-coding application urls.

The tutorial is hands on and attendees are invited to take part and try the classes or just follow the instructors.

When it comes to setting up a Cloud Foundry environment, one of the first questions is which services should be provided. Therefore, Service Brokers are the core components to implement. Based on their experience on the development of several Service Brokers for use cases in DevOps and production infrastructures the speakers present how to avoid common pitfalls and risks. Together with the audience the speakers implement an exemplary Service Broker based on an Open Source framework[1]. After the tutorial, participants are able to implement their own Service Brokers more efficiently with the gained insights and knowledge. The speaker team helps the audience to benefit from their rich experience from small and highly complex projects and the improving of their own DevOps infrastructure with customized Service Brokers to accelerate Development.[1] https://github.com/evoila/cf-service-broker

Bluemix is the largest CF environment by far. It is also arguably the one with the most usage and users. Come to this talk to hear from the World Wide DevOps and development team who answers the call when things go wrong and who also help keep Bluemix up to date and running.

We plan to share what we have learned in the past year as we grew and encountered unexpected failures and how we dealt with them.

The Dojo is Cloud Foundry's unique way of ramping up new contributors. Participants join existing core teams on site for six to ten weeks, and get introduced to technology, culture, and community by working as part of the team, pair programming all day.

The Dojo experience immerses participants in the extreme programming culture practiced at Pivotal, as well as a wide range of tools and technologies. The Dojo embodies the values of transparency and openness, prevents siloing of project expertise within Pivotal, and ensures that Cloud Foundry development is accessible to the greater community.

This presentation will give a first hand experience report about the Dojo from the perspectives of a new participant joining the BOSH core team and a full-time member of the project, and situate this in the broader context of Cloud Foundry software development.

So you’ve found a bug in Diego, and you’re excited to make a contribution to the project. Great! Now how do you get your fix accepted into the Diego codebase?

This talk will walk through the process of implementing a small change, writing and running the tests, and following the Diego team’s best practices for Golang development. It will cover common reasons for pull requests to be rejected and peel back the curtains on how the Diego team handles code contributions from developers outside the core team.

We will use the Diego project as a concrete example, but many of the steps discussed will apply to the other Cloud Foundry projects as well.

Cloud Foundry development is driven by several tenants, agile development, test-driven development and of course pair programming. Pair programming is seen as working best when the pairs are right next to each other working on the same computer in the same room, but what do you do when your pair is hundreds and perhaps thousands of miles away? The Diego team has several members who are not located in San Francisco, so remote pairing is part of our daily workflow. This talk will touch on the tools we use, the process we follow, and how we get the most out of a remote pairing situation. Andrew and Jennifer will also look at the drawbacks most often faced with remote teams and discuss a few strategies the we use to combat issues and to keep the remote team members engaged and productive and have a truly distributed agile development team.

Do you want to get started with Cloud Foundry - but think that setting it up takes too long? Do you want to know to get started with using services but don’t have a BOSH director setup?

Join us while we give you a quick intro to the fundamentals and then take you through the whole process of writing, deploying, updating apps on CF.

In this session, we will iterate on an application, demonstrating how you can get started on a Cloud Foundry without even leaving your workstation - and push to a remote Cloud Foundry when ready. You will also learn how to use services from your CF application.