Continuous Integration and Continuous Deployment

From a Pipeline to a Government Cloud

How the UK government deploy a Platform-as-a-Service using Concourse, an open-source continuous thing-doer
UB4.136
Toby Lorne (tlwr)
Since 2016, the UK Government has been running an open-source, cross-government Platform-as-a-Service (PaaS) to make it easier and cheaper to build government services. The GOV.UK PaaS is built on BOSH and Cloud Foundry, and is deployed using Concourse. Concourse is "an open-source continuous thing-doer", with abstractions that help build pipelines quickly, and for extending the behaviour of the system. This presentation will provide an introduction to Concourse, and then describe how the GOV.UK PaaS team use Concourse to continuously deploy a whole PaaS whilst ensuring high-availability and minimal impact to services and users.
Toby Lorne is a site reliability engineer working at the UK Government Digital Service on the GOV.UK Platform-as-a-Service. This presentation is split into four parts: An overview of the architecture and implementation of GOV.UK PaaS: Terraform - a tool for managing infrastructure as code; BOSH - a tool for release engineering and software lifecycle management; Cloud Foundry - a set of components for Platform-as-a-Service; Prometheus & Grafana - monitoring and visualisation tools An introduction to Concourse: how it works; the abstractions; the design decisions, patterns, and anti-patterns A walkthrough of the pipelines used in deployment and development An examination of patterns used in the GOV.UK PaaS deployment pipeline, and how you could use these patterns in your pipelines.

Additional information

Type devroom

More sessions

2/2/20
Continuous Integration and Continuous Deployment
Kris Buytaert
UB4.136
Most organisations start their journey towards Continuous Delivery with their development teams, or often their web or mobile teams. I’ve seen many of these journeys fail because “ops” was not included in the picture. The organisation assumed DevOps didn’t need ops. So the team didn’t adapt, didn’t provide the right stacks, couldn’t support the tools. I’ve started a number of successful journeys with the ops teams doing Continuous Delivery of their infrastructure as code. They ...
2/2/20
Continuous Integration and Continuous Deployment
UB4.136
How can we listen to when new upstream software has been tested to the extent that we feel comfortable integrating it into our software? How can we communicate about new artifacts available for others to integrate? How can we see what has been integrated where? How can we achieve traceability across pipelines run on different tooling infrastructure? How can we visualize our pipelines to follow changes from source code to customer deployment? We will describe these challenges and show how we ...
2/2/20
Continuous Integration and Continuous Deployment
UB4.136
In this talk, the speakers will present their experiences about using Tekton - a cloud-native pipeline system - to test, release and continuously deploy itself.
2/2/20
Continuous Integration and Continuous Deployment
UB4.136
Modernizing the traveler information systems of an international railway and transportation company, including the modernization and renewal of traveler facing devices at the train stations. For a variety of devices ranging from 20-year-old x86 PC104 based embedded systems up to modern 64bit multi-core systems, a Buildroot based Linux system, and a custom application stack is being developed.
2/2/20
Continuous Integration and Continuous Deployment
Tracy Miranda
UB4.136
The Continuous Delivery Foundation was launched in 2019 as the new home to FOSS projects Jenkins, Jenkins, Spinnaker and Tekton. The foundation is also a community to advance adoption of CI/CD best practices and tools. This talk outlines the initiatives and ways to get involved so we can all work together to accelerate CI/CD adoption. Please note that this talk replaces one entitled "Infrastructure CICD with KubeVirt and Tekton" that was due to have been given by Tyler Auerbeck, who ...
2/2/20
Continuous Integration and Continuous Deployment
Viktor Farcic
UB4.136
Deployment strategies affect everyone, no matter whether we are focused only on a single aspect of the application lifecycle or we are in full control. The way we deploy affects the architecture, testing, monitoring, and many other aspects. And not only that, but we can say that architecture, testing, and monitoring affect the way we deploy. All those things are closely related and affect each other. We'll discuss different deployment strategies and answer a couple of questions. Is your ...
2/2/20
Continuous Integration and Continuous Deployment
Carlos Sanchez
UB4.136
Progressive Delivery makes it easier to adopt Continuous Delivery, by deploying new versions to a subset of users and evaluating their correctness and performance before rolling them to the totality of the users, and rolled back if not matching some key metrics. Canary deployments is one of the techniques in Progressive Delivery, used in companies like Facebook to roll out new versions gradually. But good news! you don't need to be Facebook to take advantage of it. We will demo how to create a ...