BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Pentabarf//Schedule 0.3//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALDESC;VALUE=TEXT:Continuous Integration and Continuous Deployment devroom X-WR-CALNAME;VALUE=TEXT:Continuous Integration and Continuous Deployment devroom X-WR-TIMEZONE;VALUE=TEXT:Europe/Brussels BEGIN:VEVENT METHOD:PUBLISH UID:9246@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T090000 DTEND:20200202T094000 SUMMARY:Continuous Delivery starts with Continuous Infrastructure DESCRIPTION:
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 changed their mindset, allowing them to understand, support and onboard the development teams. This talk will document that approach with some supporting cases and examples.
Taking one step further we'll showcase a on how to do Continuous Delivery of your Infrastructure as Code, obviously with Open Source tools
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/continuous_delivery_starts_with_continuous_infrastructure/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Kris Buytaert":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10369@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T094500 DTEND:20200202T102500 SUMMARY:An event based approach for CI/CD pipelines DESCRIPTION: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 tackled them using self-documenting integration pipelines providing traceability and visualization to benefit multiple needs in the organization. We will present based on our experience from large-scale software development.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/an_event_based_approach_for_cicd_pipelines/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Emelie Pettersson":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Fredrik Fristedt":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9133@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T103000 DTEND:20200202T111000 SUMMARY:Mario’s adventures in Tekton land DESCRIPTION:In this talk, the speakers will present their experiences about using Tekton - a cloud-native pipeline system - to test, release and continuously deploy itself.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/marios_adventures_in_tekton_land/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Andrea Frittoli":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Vincent Demeester":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10366@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T111500 DTEND:20200202T115500 SUMMARY:Test Software On Emulated Hardware In Containers... In The Cloud DESCRIPTION: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.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/test_software_on_emulated_hardware_in_containers_in_the_cloud/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Sean A. Parker":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Paul Schroeder":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10806@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T120000 DTEND:20200202T121500 SUMMARY:AMENDMENT Advancing the Future of CI/CD Together DESCRIPTION: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 unfortunately wasn't able to travel to FOSDEM.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/continuous_delivery_foundry/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Tracy Miranda":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9243@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T122000 DTEND:20200202T130000 SUMMARY:Choosing The Right Deployment Strategy DESCRIPTION: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 application stateful or stateless? Does its architecture permit scaling? How do you roll back? How do you scale up and down? Do you need your application to run always? Should you use Kubernetes Deployments instead of, let's say, StatefulSets? Answers to those questions will not serve much unless we are familiar with some of the most commonly used deployment strategies. Not only that knowledge will help us choose which one to pick, but they might even influence the architecture of our applications.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/choosing_the_right_deployment_strategy/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Viktor Farcic":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9341@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T130500 DTEND:20200202T134500 SUMMARY:Progressive Delivery DESCRIPTION: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 fully automated Progressive Delivery pipeline with Canary deployments and rollbacks in Kubernetes using Jenkins X, an open source platform for cloud native CI/CD in Kubernetes, and Flagger, a project that uses Istio and Prometheus to automate Canary rollouts and rollbacks.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/progressive_delivery/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Carlos Sanchez":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9753@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T135000 DTEND:20200202T140500 SUMMARY:A Practical CI/CD Framework for Machine Learning at Massive Scale DESCRIPTION:Managing production machine learning systems at scale has uncovered new challenges that have required fundamentally different approaches to that of traditional software engineering and data science. In this talk, we'll provide key insights on MLOps, which often encompasses the concepts around monitoring, deployment, orchestration and continuous delivery for machine learning. We will be covering a hands on an example where we will be training, deploying and monitoring ML at scale. We'll be using Jenkins X (+ Prow & Tekton) to deploy/promote these models across multiple environments. We will use KIND (Kubernetes in Docker) to run integration tests in our development environment. Finally, we'll be using Seldon to orchestrate & monitor these models leveraging advanced ML techniques.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/a_practical_cicd_framework_for_machine_learning_at_massive_scale/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Alejandro Saucedo":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10263@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T141000 DTEND:20200202T145000 SUMMARY:Our road to a k8s/GKE based Closed Build Environment DESCRIPTION:My team build a new Closed Build Environment for building Release Packages on Google Cloud Platform(gcp) with Google Kubernetes Engine (GKE).
I like to take you on a small journey through a variety of topics we came across (open for change):
How we bootstrap and how we use ArgoCD
Autoscaling to 100 Build nodes for building
Why we are using Prometheus-Operator
SRE or how we maintain our stack
Product aspect
Base Image building & scanning
Network setup with Shared VPC
Google Cloud Platform IAM Permissions vs. RBAC
Specific GKE Features like Workload Identity
And others
Simple real live example how my team is doing it. Looking forward to inspire and to get feedback from others!
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/our_road_to_a_k8sgke_based_closed_build_environment/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Siegfried Kiermayer":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9493@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T145500 DTEND:20200202T153500 SUMMARY:From a Pipeline to a Government Cloud DESCRIPTION: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.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/from_a_pipeline_to_a_government_cloud/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Toby Lorne (tlwr)":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10412@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T154000 DTEND:20200202T162000 SUMMARY:Deployment to hardware DESCRIPTION:Our project takes a fun, road-following app which leverages a basic neural network and deploys it to real hardware with an OStree update system. This has meant managing a variety of different CI-runners; GPU, aarch64 and x86_64. These have variety of different dependencies, drivers and have interfaces with a number of services and caches.
I will focus on how we constructed and developed our CI pipelines to build, test and integrate a number of disparate components to produce images and push updates into an OStree server to be deployed over the air onto our hardware.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/deployment_to_hardware/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="William Salmon":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10666@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T162500 DTEND:20200202T170000 SUMMARY:AMENDMENT How secure is your build/server? DESCRIPTION:We have learned that we need to trust others, but as our parents used to say - don’t trust strangers. So we secure our production server more than ever.
Yet, there is this no-man's land: “the build server”. We think it’s time to take a closer look at some of the good practices around securing builds & artifacts to improve our day to day level of trust.
Please note that this talk replaces one entitled "Safe, gated and integrated GitOps for Kubernetes" that was due to have been given by Mohammed Naser, who unfortunately is now unable to present. We wish him a speedy recovery.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Continuous Integration and Continuous Deployment URL:https:/fosdem.org/2020/schedule/2020/schedule/event/kubernetes_gitops/ LOCATION:UB4.136 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Patrick Debois":invalid:nomail END:VEVENT END:VCALENDAR