In this hands-on workshop attendees will learn the basics of how to use Argo Rollouts to progressively roll out apps. In this lab you will learn how to: Review the Rollouts specification, Use Rollouts to perform a blue-green deployment, Review the blue-green Rollout that were pre-deployed as part of the workshop, Update the image with continuous integration and observe the blue-green progressive delivery in action, Enhance the blue-green rollout with integrated testing by applying an AnalysisTemplate, Update the image again and review how the AnalysisTemplate works, Use Rollouts to perform a canary deployment, Review the canary Rollout that was pre-deployed as part of the workshop, Update the image with continuous integration and observe the canary progressive delivery in action, Observe that the canary is configured for a manual step, approve the promotion, Observe the remainder of the deployment until completion, Perform a rollback of the canary of the canary deployment.

In this session we'll go over the history of the OpenStack project before diving deeper into how it all works and how you can contribute. We will look at the landscape of the project as it is today, while diving deeper into what some of the projects are and the services they provide and how they interact together. We will finish with a call to action on how you can get involved in the project. After this session, you should walk away with a better understanding of OpenStack as a project and an infrastructure-as-a-service, and how you can get involved and contriibute to the project.

Amy Marrich,

Principal Technical Marketing Manager, Red Hat

Running OpenStack on Kubernetes is a great idea - users can leverage their Kubernetes platform expertise and run the OpenStack clouds and services that they need while also adding in additional cloud native workloads that enhance their OpenStack experience. On the other hand, running OpenStack on Kubernetes adds a huge additional layer of complexity for Day 2 operators. When something goes wrong (as it always will), how can you find and resolve it quickly in all the operational layers? One big advantage with OpenStack on Kubernetes is the potential to augment the Observability stack. Rather than relying on just the OpenStack Observability services, users can also leverage Cloud Native Observability in order to get a more comprehensive view of their systems, and help reduce that Mean Time to Remediation and Resolution. In this talk, we will discuss ways to use several Open Source technologies to get end to end Observability for OpenStack on Kubernetes.

Jamie Parker,

Product Manager, Red Hat

Learn about the ecosystems in the Fedora and CentOS projects, and how you can package software for both. Fedora Linux is the leading edge, community built operating system. CentOS is the open source, community operating system derived from Fedora. Although separate projects, Fedora and CentOS have a lot in common, such as packaging and build infrastructure. Both projects also have a wide ecosystem of special interest groups that develop on top of the core operating systems. We will present an overview of the Fedora project followed by an overview CentOS ecosystem. We'll show how both systems are developed and what the various special interest groups are doing. We will then provide a packaging workshop where you can learn how to package your favorite software, whether you want it in Fedora, EPEL, a CentOS SIG, or just for your own personal use. No prior packaging experience is necessary, but we will assume a basic familiarity with Linux and the command line.

As OpenStack emerged in 2010 the community infrastructure needed to authenticate community members. As many of those community members already used Ubuntu and Canonical, provided Ubuntu One as and Identity Provider, it was a natural fit. Fast forward 15(ish) years. OpenStack becomes OpenInfra and the tools to support a single project, now need to support several aligned technologies on a single platform, OpenDev. It just makes sense to broaden the pool of Identity providers to best align with each project, and as a bonus avoid a single point of failure. To that end the OpenDev sysadmins have begun integrating Keycloak as an Identity broker, and authorisation provider. This is a great success for "green fields" tools but the catch? Well there are several; Keycloak doesn't support OpenID (which is the protocol provided by Ubuntu One); there is no trivial tool for establishing the pre-existing mappings needed to ensure developers can keep ... developing and last but by no means least Keycloak is written in Java (you may not know this but Java isn't Python!)

Tony Breeds,

Software Engineer, Red Hat

Ceph is an open source distributed object store, network block device, and file system designed for reliability, performance, and scalability. It runs on commodity hardware, has no single point of failure, and is supported in the Linux kernel. This tutorial will describe the Ceph architecture, share its design principles, and discuss how it can be part of a cost-effective, reliable cloud stack. The de-facto standard for OpenStack storage, Ceph is leading the rising tide of Software-defined-Storage and a top contender in the Kubernetes and S3 storage use cases.

These days we all spend a lot of time developing for Kubernetes. Wouldn't it be great if you could develop and test your containerized application from an easy-to-use desktop application, and not need to touch Kubernetes clusters until you're ready for staging? With Podman Desktop and Bluefin Linux, you can! In this demo-heavy presentation, we will go over the workflow of a containerized application developer working on a simple application (the open source project Elekto), making changes, running local tests, and finally deploying to a Kubernetes cluster. We'll then demostrate some of the other capabilities of Podman Desktop, including developing system images using BootC. No previous knowledge of Kubernetes is required. If you regularly work on applications targeting Kubernetes, or if you want to, you'll learn about a set of tools designed to make your life easier and your development speedier.

Josh Berkus,

Kubernetes Community Manager, Red Hat

In this session, attendees will have the opportunity to meet with leaders of the OpenInfra Foundation, as well as members of the Board of Directors and technical leaders from Kata, OpenStack, StarlingX, and Zuul. This is a great opportunity to learn more about the Foundation and it's projects, as well as put faces to names and get answers to your questions.

If you have ever wondered what it takes to develop OpenStack, look no further. This workshop is designed for attendees with any level of OpenStack experience. In this workshop, we will provide attendees a walkthrough of making a code change into OpenStack. Attendees will understand how developers identify bugs/features to work on, create contributor accounts, develop the code change, test it against an OpenStack deployment and submit it for community code review. As seasoned core maintainers of OpenStack, we can share strategies we have learned to engage with the community and get these code changes merged. We hope this session will serve as a quickstart to in-person audiences who get to follow along hands-on.

The Universal Blue project builds custom Fedora Atomic images via OCI/Docker containers. This is a feature that is not yet in mainline Fedora. One of the reasons the project was started was to test and validate this method of distribution and modification as a way to experiment with this new model to see if it is viable.

Noel Miller,

Technical Account Manager, Red Hat

Bazzite is an open source custom operating system image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. It is built with Cloud Native Technology through the use of OCI containers and GitHub Runners. It is built for Linux newcomers and enthusiasts to provide the best user friendly experience for playing your favorite video games.

In this session, you will learn the importance of joining and giving back to a community. We will discuss the different roles within an Open Source Community and why they are all important and most importantly how everyone's work is important and has value.

Amy Marrich,

Principal Technical Marketing Manager, Red Hat

Backstage Software Templates provide a consistent way for platform engineers to enable self-service delivery of cloud-native software components. Templates ease onboarding and daily development work by establishing the tools, services, documentation, and best practices as “golden paths” for users to navigate. Attendees will learn how to use CNCF products and technologies together to construct flexible foundations for cloud-native development using Backstage Software Templates, Helm Charts, Tekton, Kubernetes, ArgoCD, and more, and will review common workflows for delivering and updating these offerings via the Backstage Software Catalog. Learn how to enable your teams to get to work immediately using your prescribed tools and technologies with Software Templates for Backstage.

Ryan Jarvinen,

Developer Advocate, Red Hat

The RamaLama project's goal is to make working with AI boring through the use of OCI containers. RamaLama tool facilitates local management and serving of AI Models. On first run RamaLama inspects your system for GPU support, falling back to CPU support if no GPUs are present. RamaLama uses container engines like Podman or Docker to pull the appropriate OCI image with all of the software necessary to run an AI Model for your systems setup. Running in containers eliminates the need for users to configure the host system for AI. After the initialization, RamaLama runs the AI Models within a container based on the OCI image. RamaLama then pulls AI Models from model registires. Starting a chatbot or a rest API service from a simple single command. Models are treated similarly to how Podman and Docker treat container images.

James Huang,

Senior Product Manager, Red Hat