Cockpit (https://cockpit-project.org) and its builtin set of UIs for system services has become an integral part of Fedora Server, RHEL, and is included in all major distributions.
It has always been very simple to create your own interfaces using Cockpit's API. But it is a big step from some quick HMTL+JS proof of concept towards maintaining a production-grade project with proper integration testing/gating and fully automatic delivery. This talk introduces the tools and services that the Cockpit team offers for developing your Cockpit extensions, which gets you there right from scratch.
Program and project management of Red Hat Enterprise Linux (RHEL) is daunting task which provides tons of learning opportunities. RHEL is unique because we use Open Source as the way how to develop and maintain it.
I work for more than 10 years in program management team responsible for planning and delivering RHEL releases. I would like to share what the team learned what worked and what did not work as the product was getting more complex over time.
This session will give an introduction to a new way of doing system upgrades on Fedora, RHEL and CentOS using the Leapp framework to give more options to the users.
We will introduce the Framework, how it works and what it can do for making a difference during the upgrade of Fedora.
The talk will introduce Tuned and its features. Tuned is application for system tuning. It can help system administrators to optimize their systems for various workloads (e.g. SAP, Oracle DB, MS SQL, ...) or to optimize systems for general goals like high throughput, low latency, or low power consumption. Instead of having configuration on multiple places and in custom scripts, Tuned stores all its configuration cleanly in one place - in the Tuned profile. It can do do rollback of settings, supports hot plugging of devices and can be controlled from the command line or through the D-Bus, thus it can be easily integrated into existing administering solutions like e.g. Cockpit. Project web page: https://tuned-project.org/
Introducing Cockpit Composer, a new tool that lets you create, edit, and manage customized OS images over time. Create blueprints with custom selections of packages and modules from different source repositories. Then generate images from those blueprints for physical, virtual, and cloud environments. Learn about what features are currently available in the web UI, including how to select the content you need and how to create images. As part of this session, we want to take some time to get feedback from the audience on the flow of features presented and their image building needs.
If you're interested in package management and DNF stack in particular, join us to learn more about what we have done over the past year and what we plan for the next years. Among other topics, we'll touch Modularity support, new unified API and integration testing.
Worked for 10 years in Red Hat's Release Engineering team, leading RHEL 7 release among other activities. Joined the Software Management team 2 years ago as a team leader. Currently focused mainly on DNF.
Recently, the co-presenters have used surveys and direct interviews to collect people’s work methods and habits while maintaining upstream software, RPM packages, modules and container images for Fedora and Red Hat. Unsurprisingly, despite a roughly unified set of tools, people have very different methods for their day to day tasks.
During this talk we will present the results of our research, including the wide-variety of tools, processes, and mechanisms we found. Our focus has been on collecting information on the current state and ideas for improvement. As a result, we will not be presenting solutions but are very interested in your experience and ideas for improvement.
subtitle: The G.K. Chesterton Approach to Software Development
The early-20th century author G.K. Chesterton wrote one of the most insightful things I've ever read about politics, which also happens to apply perfectly to software development. The spirit of it is: changing things is fine, but understand what you're changing before you do it. I will present the full quotation, then dig into how it applies to software development, and some simple tools and techniques you can use to apply this in real life.
