Chaos Computer Club - archive feed

Since last year’s talk i’ve been working on modernising conky’s default config system. There are a number of reasons for doing this from being able to provide a default configuration that better adapts to the system hardware to making it much easier to provide a modern look and feel. In this talk i’ll talk about the parts of this process that were easy because thanks to open source someone had already written something, the frustrating parts because someone had created something really nice but not licensed it. I’ll also talk about all the unexpected detours that I took which included some lua packaging, learning to write lua bindings and learning how to do proper font rendering on linux. I’ll also share the current progress and how you can give it a shot yourself along with what still needs to be done . Since last year’s talk i’ve been working on modernising conky’s default config system. There are a number of reasons for doing this from being able to provide a default configuration that better adapts to the system hardware to making it much easier to provide a modern look and feel. In this talk i’ll talk about the parts of this process that were easy because thanks to open source someone had already written something, the frustrating parts because someone had created something really nice but not licensed it. I’ll also talk about all the unexpected detours that I took which included some lua packaging, learning to write lua bindings and learning how to do proper font rendering on linux. I’ll also share the current progress and how you can give it a shot yourself along with what still needs to be done . about this event: https://c3voc.de

Another openSUSE conference, another MicroOS talk ;) I'm excited to share my MicroOS journey over the past three years. In this talk, I'll cover my reasons for switching my servers from Leap to MicroOS, how I overcame my initial apprehensions, the problems MicroOS solved for me, and how I adapted to the project sunsetting Kubic. Another openSUSE conference, another MicroOS talk ;) I'm excited to share my MicroOS journey over the past three years. In this talk, I'll cover my reasons for switching my servers from Leap to MicroOS, how I overcame my initial apprehensions, the problems MicroOS solved for me, and how I adapted to the project sunsetting Kubic. about this event: https://c3voc.de

In this talk, you are going to learn about the recent changes that we have done to improve the user experience for openSUSE especially in Brazil, but also for South America. There are many challenges when addressing issues in a country as big as Brazil or an entire continent, and we need your help to improve it further. In this talk, you are going to learn about the recent changes that we have done to improve the user experience for openSUSE especially in Brazil, but also for South America. There are many challenges when addressing issues in a country as big as Brazil or an entire continent, and we need your help to improve it further. about this event: https://c3voc.de

This talk will be about the creation of the openSUSE mirror in Open Labs Hackerspace. By having a local mirror, we are trying to reduce the time it takes to download updates and software packages and by making it publicly available, we hope to bring more enthusiasts in our openSUSE community, in Tirana. The mirror is being build and will be maintained by volunteers who are avid supporters of openSUSE distributions and are committed to helping others benefit from it. A technical breakdown of the openSUSE mirror on how we have designed the infrastructure to be secure, available and easily maintainable will be provided. Lastly, if you're curious about the openSUSE community in Albania, you'll definitely want to stick around! This talk will be about the creation of the openSUSE mirror in Open Labs Hackerspace. By having a local mirror, we are trying to reduce the time it takes to download updates and software packages and by making it publicly available, we hope to bring more enthusiasts in our openSUSE community, in Tirana. The mirror is being build and will be maintained by volunteers who are avid supporters of openSUSE distributions and are committed to helping others benefit from it. A technical breakdown of the openSUSE mirror on how we have designed the infrastructure to be secure, available and easily maintainable will be provided. Lastly, if you're curious about the openSUSE community in Albania, you'll definitely want to stick around! about this event: https://c3voc.de

This talk should be a collection of first experience with the life of a packager (in this case, one of the team maintaining Python packages in SLE and openSUSE) on MicroOS, with read/only root and using various containerized tools like podman, distrobox and flatpak. This talk should be a collection of first experience with the life of a packager (in this case, one of the team maintaining Python packages in SLE and openSUSE) on MicroOS, with read/only root and using various containerized tools like podman, distrobox and flatpak. about this event: https://c3voc.de

A quick glance at mirrors.opensuse.org gives an idea on the disparity between the African continent and the rest of the world in terms of infrastructure to support open source. It's not just openSUSE but every other Linux distribution has just one or two, or no mirror at all in Africa. A quick glance at mirrors.opensuse.org gives an idea on the disparity between the African continent and the rest of the world in terms of infrastructure to support open source. It's not just openSUSE but every other Linux distribution has just one or two, or no mirror at all in Africa. about this event: https://c3voc.de

The MicroOS Desktop started as a hairbrained, poorly thought out, "lets see what happens" concept at an openSUSE Conference not so long ago. It's since become perhaps the most stable, reliable, and exciting Desktop offering the openSUSE Project offers. This brief talk will provide a brief overview of the MicroOS Desktop project, advice for newcomers to the platform, and an open invitation as to how to contribute to help make openSUSE's latest and greatest Desktop OS even better. Africa's internet speed is below the global average and that gives us a stronger reason why we need more mirrors in the continent. In this presentation I'll explore how we built two additional openSUSE mirrors in Africa during the past year and what can be done to improve this picture, and reach out to more users in the continent. The MicroOS Desktop started as a hairbrained, poorly thought out, "lets see what happens" concept at an openSUSE Conference not so long ago. It's since become perhaps the most stable, reliable, and exciting Desktop offering the openSUSE Project offers. This brief talk will provide a brief overview of the MicroOS Desktop project, advice for newcomers to the platform, and an open invitation as to how to contribute to help make openSUSE's latest and greatest Desktop OS even better. Africa's internet speed is below the global average and that gives us a stronger reason why we need more mirrors in the continent. In this presentation I'll explore how we built two additional openSUSE mirrors in Africa during the past year and what can be done to improve this picture, and reach out to more users in the continent. about this event: https://c3voc.de

For those who use Linux professionally in companies, proxy servers are a horror. Under Linux there is no central configuration of proxy servers and each major library / programming language implements its own implementation. If login data and so-called PAC proxies are added, which serve not only one but several proxy servers, it gets really complicated. This is where the library libproxy comes in and tries to solve this problem. By providing a simple and stable API it answers the question: Which way do I have to take to reach XYZ? In this talk we will present libproxy, its current state and future development. Together we can solve the problem and bring this solution into the enterprises, so that Linux becomes even more integrated and established in the professional environment and their complex processes. Translated with www.DeepL.com/Translator (free version) For those who use Linux professionally in companies, proxy servers are a horror. Under Linux there is no central configuration of proxy servers and each major library / programming language implements its own implementation. If login data and so-called PAC proxies are added, which serve not only one but several proxy servers, it gets really complicated. This is where the library libproxy comes in and tries to solve this problem. By providing a simple and stable API it answers the question: Which way do I have to take to reach XYZ? In this talk we will present libproxy, its current state and future development. Together we can solve the problem and bring this solution into the enterprises, so that Linux becomes even more integrated and established in the professional environment and their complex processes. Translated with www.DeepL.com/Translator (free version) about this event: https://c3voc.de

This presentation gives an overview of application design and development for Kubernetes, the de facto standard for container orchestration in enterprises of all sizes. Using a small web server code base as an example, the talk outlines the complete application lifecycle from the initial design to deployment, service-based access in addition to more advanced aspects such as scalability, resilience and high availability. The focus of this presentation is not so much on theory but rather practice using a live environment to demonstrate concepts and illustrate principles. Overview of the talk: - Application code base: The guinea pig - Packaging: Image building and registry management - Deployment: Populating the cluster - Services: Internal and external network access - High availability & resilience: Planning for the worst and beyond - Advanced concepts: Load balancers, Ingress and more - Spin your own: Kubernetes on a budget - Discussion & Q&A The presentation assumes a basic understanding of Docker and Kubernetes in addition to fundamental aspects of application design and programming. This presentation gives an overview of application design and development for Kubernetes, the de facto standard for container orchestration in enterprises of all sizes. Using a small web server code base as an example, the talk outlines the complete application lifecycle from the initial design to deployment, service-based access in addition to more advanced aspects such as scalability, resilience and high availability. The focus of this presentation is not so much on theory but rather practice using a live environment to demonstrate concepts and illustrate principles. Overview of the talk: - Application code base: The guinea pig - Packaging: Image building and registry management - Deployment: Populating the cluster - Services: Internal and external network access - High availability & resilience: Planning for the worst and beyond - Advanced concepts: Load balancers, Ingress and more - Spin your own: Kubernetes on a budget - Discussion & Q&A The presentation assumes a basic understanding of Docker and Kubernetes in addition to fundamental aspects of application design and programming. about this event: https://c3voc.de

In recent years the amount of vulnerabilities and also the amount of systems, installations or containers a single sysadmin has to oversee has grown beyond any human capable measures. The best help here is more automation in various places, which needs to be driven by automation consumable data. We will look at two primary areas, the automation data provided by SUSE for security fixes and also very fresh the inventory data, or "Software Bill of Materials (SBOM)". The talk will go over various formats, what SUSE offers and their purposes and also give some future look out on more improved or even more automation data formats. In recent years the amount of vulnerabilities and also the amount of systems, installations or containers a single sysadmin has to oversee has grown beyond any human capable measures. The best help here is more automation in various places, which needs to be driven by automation consumable data. We will look at two primary areas, the automation data provided by SUSE for security fixes and also very fresh the inventory data, or "Software Bill of Materials (SBOM)". The talk will go over various formats, what SUSE offers and their purposes and also give some future look out on more improved or even more automation data formats. about this event: https://c3voc.de

OpenSUSE MicroOS, SLE Micro and the SUSE Adaptable Linux Platform (ALP) have moved to using SELinux for Mandatory Access Control (MAC). There are some key differences between a traditional Linux system without MAC, and one with SELinux. Furthermore, using SELinux on transactional systems such as openSUSE MicroOS and ALP-based distributions has its own peculiarities. In this talk we will introduce SELinux, describe what it does, and show how to work with it. We will then see how it's used on a transactional immutable system such as an ALP-based distribution, where most workloads are run inside containers. This talk is for a beginner to intermediate-level audience. You should have a general understanding of both traditional and immutable Linux systems, but won't need specific SELinux expertise. OpenSUSE MicroOS, SLE Micro and the SUSE Adaptable Linux Platform (ALP) have moved to using SELinux for Mandatory Access Control (MAC). There are some key differences between a traditional Linux system without MAC, and one with SELinux. Furthermore, using SELinux on transactional systems such as openSUSE MicroOS and ALP-based distributions has its own peculiarities. In this talk we will introduce SELinux, describe what it does, and show how to work with it. We will then see how it's used on a transactional immutable system such as an ALP-based distribution, where most workloads are run inside containers. This talk is for a beginner to intermediate-level audience. You should have a general understanding of both traditional and immutable Linux systems, but won't need specific SELinux expertise. about this event: https://c3voc.de

For the administrator of many Linux machines, [Uyuni](https://www.uyuni-project.org) is a very important tool. It currently runs on premise in a virtual machine or on bare metal. Could it be running in the kubernetes cluster of the lab? Would it be more scalable? Would I finally get high availability or resilience for it? This session will address these questions by explaining how we got Uyuni running in [K3S](https://k3s.io/) on ALP. We will also see which of the container-ready applications benefits would apply and what could be the next steps towards a more modern application. For the administrator of many Linux machines, [Uyuni](https://www.uyuni-project.org) is a very important tool. It currently runs on premise in a virtual machine or on bare metal. Could it be running in the kubernetes cluster of the lab? Would it be more scalable? Would I finally get high availability or resilience for it? This session will address these questions by explaining how we got Uyuni running in [K3S](https://k3s.io/) on ALP. We will also see which of the container-ready applications benefits would apply and what could be the next steps towards a more modern application. about this event: https://c3voc.de

Showing cross building our new code base, based on openSUSE Factory. This includes: * Cross architecture package builds * Cross architecture image builds * Cross OS Container builds All covered by Open Build Service or plain git and pbuild tooling locally using the same sources. Showing cross building our new code base, based on openSUSE Factory. This includes: * Cross architecture package builds * Cross architecture image builds * Cross OS Container builds All covered by Open Build Service or plain git and pbuild tooling locally using the same sources. about this event: https://c3voc.de

Let's talk about the current state and ongoing plans with openSUSE Leap 16.0 which is based on SUSE's Adaptable Linux Platform. Let's talk about the current state and ongoing plans with openSUSE Leap 16.0 which is based on SUSE's Adaptable Linux Platform. about this event: https://c3voc.de

After 13 years, a new major release of the syslog-ng logging application is available. Syslog-ng 4.0 brings type support and many additional enhancements. This presentation also gives you an overview of some of the larger features since the previous major release, and then proves why type support is a major enhancement, improving both operations and security. In version 3 and earlier, syslog-ng handled all data as text. Syslog-ng 4 can associate the proper type information with data parsed from log messages using the JSON or PatternDB parsers. You can use type information for comparisons within syslog-ng, and storing data to various destinations, like Elasticsearch or MongoDB. Type support enables more precise filtering and thus real-time security alerting in syslog-ng, and easier searching and reporting in databases. I give a quick overview of the major new syslog-ng features during the version 3 series, including disk-buffer, message parsing, Python support, HTTP destination, Kubernetes support and how these combined with 4.0 features improve both operations and security. After 13 years, a new major release of the syslog-ng logging application is available. Syslog-ng 4.0 brings type support and many additional enhancements. This presentation also gives you an overview of some of the larger features since the previous major release, and then proves why type support is a major enhancement, improving both operations and security. In version 3 and earlier, syslog-ng handled all data as text. Syslog-ng 4 can associate the proper type information with data parsed from log messages using the JSON or PatternDB parsers. You can use type information for comparisons within syslog-ng, and storing data to various destinations, like Elasticsearch or MongoDB. Type support enables more precise filtering and thus real-time security alerting in syslog-ng, and easier searching and reporting in databases. I give a quick overview of the major new syslog-ng features during the version 3 series, including disk-buffer, message parsing, Python support, HTTP destination, Kubernetes support and how these combined with 4.0 features improve both operations and security. about this event: https://c3voc.de

A quick overview of the upcoming RPM 4.19 release and the plans beyond that. A quick overview of the upcoming RPM 4.19 release and the plans beyond that. about this event: https://c3voc.de

Is the IBM mainframe really an old legacy system? If all people are speaking about Cloud Native, Edge Computing and Industry 4.0, IBM has released a new mainframe exactly for the combination with that all. You can integrate the new "small" mainframe as a "Thing" or IoT device into manufacturing facilities or use it in for smaller company requirements for processing a lot of tasks/instructions in parallel. Then you can combine it with the Public Cloud or Embedded Systems. You will receive an overview, what is possible today with mainframes by IBM. Is the IBM mainframe really an old legacy system? If all people are speaking about Cloud Native, Edge Computing and Industry 4.0, IBM has released a new mainframe exactly for the combination with that all. You can integrate the new "small" mainframe as a "Thing" or IoT device into manufacturing facilities or use it in for smaller company requirements for processing a lot of tasks/instructions in parallel. Then you can combine it with the Public Cloud or Embedded Systems. You will receive an overview, what is possible today with mainframes by IBM. about this event: https://c3voc.de

This talk will introduce the new zypper-keys plugin. It provides an easy way to manage rpm repo signing keys on your local system. [https://github.com/asdil12/zyppkeys](https://github.com/asdil12/zyppkeys) This talk will introduce the new zypper-keys plugin. It provides an easy way to manage rpm repo signing keys on your local system. [https://github.com/asdil12/zyppkeys](https://github.com/asdil12/zyppkeys) about this event: https://c3voc.de

This should consist of nine short 4-minute talks by users with 1 minute for handover. Users do not need their own laptop, but instead link their resources on https://etherpad.opensuse.org/p/lightning-talks-osc2023 Topics can be - a project the presenter made or uses that might be useful to other Geekos - a relevant topic where you look for others to join a discussion - etc This should consist of nine short 4-minute talks by users with 1 minute for handover. Users do not need their own laptop, but instead link their resources on https://etherpad.opensuse.org/p/lightning-talks-osc2023 Topics can be - a project the presenter made or uses that might be useful to other Geekos - a relevant topic where you look for others to join a discussion - etc about this event: https://c3voc.de

When using **Xorg**, in order to have a headless remote session we could use **Xvnc**, and it worked great. You can start with it a headless **Xorg** display, on top of it use any desktop environment or just run a **Xorg** client and access it using **VNC** protocol. Now with **Wayland**, the display server is also the windows manager/compositor so there isn't just one single display server to use any desktop environment but each desktop environment has its own **Wayland** compositor implementation. In this talk, I will explain my quest to have a **Wayland** headless remote desktop using the **RDP** protocol in the **GNOME** environment. Most of the work I'm doing is on this [MR](https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/139). When using **Xorg**, in order to have a headless remote session we could use **Xvnc**, and it worked great. You can start with it a headless **Xorg** display, on top of it use any desktop environment or just run a **Xorg** client and access it using **VNC** protocol. Now with **Wayland**, the display server is also the windows manager/compositor so there isn't just one single display server to use any desktop environment but each desktop environment has its own **Wayland** compositor implementation. In this talk, I will explain my quest to have a **Wayland** headless remote desktop using the **RDP** protocol in the **GNOME** environment. Most of the work I'm doing is on this [MR](https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/139). about this event: https://c3voc.de

Everybody of us have got a laptop. Then there are some Embedded enthusiasts with arm hardware. Did you hear already about the architecture s390x for mainframes, which includes IBM zSystems and LinuxONE? You will learn, where such hardware is used and that you can also still use it with openSUSE. Hints will be given, how to receive mainframe access for free for open source development. Finally, there is a short introduction, how you can be included for better s390x support (with feedback) within the Linux Distributions Working Group at the Open Mainframe Project. Everybody of us have got a laptop. Then there are some Embedded enthusiasts with arm hardware. Did you hear already about the architecture s390x for mainframes, which includes IBM zSystems and LinuxONE? You will learn, where such hardware is used and that you can also still use it with openSUSE. Hints will be given, how to receive mainframe access for free for open source development. Finally, there is a short introduction, how you can be included for better s390x support (with feedback) within the Linux Distributions Working Group at the Open Mainframe Project. about this event: https://c3voc.de

systemd-boot is a rather simple UEFI boot manager. Using it instead of grub might be desirable in the future. The combination with btrfs snapshots makes things more complicated though. This talk gives an introduction to systemd-boot and the challenges to fully integrate it into openSUSE. systemd-boot is a rather simple UEFI boot manager. Using it instead of grub might be desirable in the future. The combination with btrfs snapshots makes things more complicated though. This talk gives an introduction to systemd-boot and the challenges to fully integrate it into openSUSE. about this event: https://c3voc.de

BCI (Base Container Images) is a set of open-source container images that developers and operators can use as a foundation for containerizing applications. BCIs cover a wide range of use cases and scenarios compared to traditional enterprise distribution images. We had to take a different approach to testing and delivery to cover all these new use cases. In this session we briefly cover the history of the Base Container Images and the tooling that we created in the process. This includes our [Dockerfile generator](https://github.com/SUSE/BCI-dockerfile-generator), the [BCI test suite](https://github.com/SUSE/BCI-tests/), and the [`pytest_container`](https://github.com/dcermak/pytest_container) plugin. We also take a look how we moved the development from our internal build service to the [public Open Build Service](https://build.opensuse.org/project/subprojects/devel:BCI) and then to [Github](https://github.com/SUSE/BCI-dockerfile-generator). BCI (Base Container Images) is a set of open-source container images that developers and operators can use as a foundation for containerizing applications. BCIs cover a wide range of use cases and scenarios compared to traditional enterprise distribution images. We had to take a different approach to testing and delivery to cover all these new use cases. In this session we briefly cover the history of the Base Container Images and the tooling that we created in the process. This includes our [Dockerfile generator](https://github.com/SUSE/BCI-dockerfile-generator), the [BCI test suite](https://github.com/SUSE/BCI-tests/), and the [`pytest_container`](https://github.com/dcermak/pytest_container) plugin. We also take a look how we moved the development from our internal build service to the [public Open Build Service](https://build.opensuse.org/project/subprojects/devel:BCI) and then to [Github](https://github.com/SUSE/BCI-dockerfile-generator). about this event: https://c3voc.de

Rancher can deploy and manage your Kubernetes clusters on AWS EKS and EC2. But what about things like Authentication, Logging, Monitoring or Backup? I will give an overview of AWS services for these four pillars and talk about what’s already possible, which challenges some integrations might have and an outlook what’s planned. Learn more about how the integrations are working under the hood and which technologies and open-sources solutions are involved. Rancher can deploy and manage your Kubernetes clusters on AWS EKS and EC2. But what about things like Authentication, Logging, Monitoring or Backup? I will give an overview of AWS services for these four pillars and talk about what’s already possible, which challenges some integrations might have and an outlook what’s planned. Learn more about how the integrations are working under the hood and which technologies and open-sources solutions are involved. about this event: https://c3voc.de

We are using SALT to deploy SUSE Systems for production. The included modules work well for usual problems. But what needs to be done if you want to integrate a software system (or part thereof) where there are no modules available? Calling out to shell commands won't work to well for complex tasks. You'll find the slides at https://www.jochen.org/vortraege/implementing-salt-modules.pdf We've implemented - as part of a bigger automation effort - some SALT modules to configure our SAP HANA applications for better integration into the automation machinery. I'll present our motivation for implementing execution and state modules, how you can start implementing and testing them. In my experience the function signatures of the modules are the key to useful state modules, so I'll take a look at our modules and discuss the experiences gained in using them. Is the effort worth the gain? My answer is "yes". Some basic programming skills and Python will be helpful for understanding, but not required. We are using SALT to deploy SUSE Systems for production. The included modules work well for usual problems. But what needs to be done if you want to integrate a software system (or part thereof) where there are no modules available? Calling out to shell commands won't work to well for complex tasks. You'll find the slides at https://www.jochen.org/vortraege/implementing-salt-modules.pdf We've implemented - as part of a bigger automation effort - some SALT modules to configure our SAP HANA applications for better integration into the automation machinery. I'll present our motivation for implementing execution and state modules, how you can start implementing and testing them. In my experience the function signatures of the modules are the key to useful state modules, so I'll take a look at our modules and discuss the experiences gained in using them. Is the effort worth the gain? My answer is "yes". Some basic programming skills and Python will be helpful for understanding, but not required. about this event: https://c3voc.de

This talk will cover the development of an openSUSE based external-dns solution that can be used within a k3s environment. The current upstream solution for external-dns is based on Alpine Linux. In order to create containers based on openSUSE, powerdns and external-dns containers were developed and published to registry.opensuse.org. During this session, the different design decisions and hurdles that were overcome will be covered. In addition, the presentation will provide tools, tips, and troubleshooting techniques that were used during the development cycle. This talk will cover the development of an openSUSE based external-dns solution that can be used within a k3s environment. The current upstream solution for external-dns is based on Alpine Linux. In order to create containers based on openSUSE, powerdns and external-dns containers were developed and published to registry.opensuse.org. During this session, the different design decisions and hurdles that were overcome will be covered. In addition, the presentation will provide tools, tips, and troubleshooting techniques that were used during the development cycle. about this event: https://c3voc.de

WASM affords portability when coupled with Content Addressable Tar Files, we can utilize Peer.2 Peer distribution to enhance and reduce the size and vitality of images. This talk explores how the next evolution of containers might take place, and what key technologies are driving solutions in place today. WASM affords portability when coupled with Content Addressable Tar Files, we can utilize Peer.2 Peer distribution to enhance and reduce the size and vitality of images. This talk explores how the next evolution of containers might take place, and what key technologies are driving solutions in place today. about this event: https://c3voc.de

With SUSE's ALP stirring up discussions how Linux distribution may look like, we decided to try different approach how installer may work. Part of these installer try-outs is **Iguana** - installation initramfs where all heavy lifting is done in containers. Moving installers to the containers and by leveraging container infrastructure, we are trying to solve ever changing requirements or need to have security and other fixes in installer, which was always a bit of challenge for relatively static things like OS installers. With SUSE's ALP stirring up discussions how Linux distribution may look like, we decided to try different approach how installer may work. Part of these installer try-outs is **Iguana** - installation initramfs where all heavy lifting is done in containers. Moving installers to the containers and by leveraging container infrastructure, we are trying to solve ever changing requirements or need to have security and other fixes in installer, which was always a bit of challenge for relatively static things like OS installers. about this event: https://c3voc.de

Packaging for a distribution means taking sources from upstream projects, applying fixes and modifications, adding some configuration and then build the result by calling some commands. RPM formalized the process following a "pristine sources" model. The approach is basically to take the unmodified sources as released by upstream and store required changes in the form of patches as well as a build description next to them. Times have changed. The distributed version control system git dominates the free software world. Juggling tarballs and manually applying patches is no longer a natural workflow. Packager life could be much easier if downstream changes could be applied by means of git too, skipping tarballs. This talks presents a way how to apply the pristine source idea to a git based world, without history rewriting in the distro repo. Packaging for a distribution means taking sources from upstream projects, applying fixes and modifications, adding some configuration and then build the result by calling some commands. RPM formalized the process following a "pristine sources" model. The approach is basically to take the unmodified sources as released by upstream and store required changes in the form of patches as well as a build description next to them. Times have changed. The distributed version control system git dominates the free software world. Juggling tarballs and manually applying patches is no longer a natural workflow. Packager life could be much easier if downstream changes could be applied by means of git too, skipping tarballs. This talks presents a way how to apply the pristine source idea to a git based world, without history rewriting in the distro repo. about this event: https://c3voc.de

Both the ISO 27001 and ISO 27002 standards have been updated in 2022. What does this mean for open source communities and companies leveraging open source? What are the most significant changes to the standards? The new ISO27001 standard requires companies to identify and meet the needs of interested parties, such as customers and suppliers. That way, organizations can ensure that their information security management system is designed to meet their stakeholders needs. It also requires that organizations include processes for managing information security objectives in their ISMS, so that those objectives can be monitored and evaluated over time. It is essential for organizations to be able to demonstrate that their data-protection and security risk mitigation measures will be maintained and continuously improved. The new ISO27001 standard also makes it clear that changes to an organization's ISMS must be planned, with a specific process for communicating those changes to interested parties. This process should establish how communication should occur (rather than just who should communicate). Organizations now have to control processes, products, or services that are outside of the ISMS (as well as those that are inside of it), which means that they have to take a more holistic approach to managing both internal and outsourced operations. ISO 27002 has been updated, firstly the phrase 'code of practice' has been dropped from the title of the updated ISO 27002 standard. This approach better reflects the set's intended purpose as a reference of information security controls. The 27002 Standard itself is considerably longer than the previous version, and the controls have been reordered and updated. The new controls are identifiable by attribute, which makes it easier to focus on relevant categorical selections, which could reduce the compliance burden or help better integrate information security processes, making the ISMS easier to implement and manage. What is a reasonable for IT vendors and open source communities to update their cybersecurity approach to reflect the new requirements from the new norms? Both the ISO 27001 and ISO 27002 standards have been updated in 2022. What does this mean for open source communities and companies leveraging open source? What are the most significant changes to the standards? The new ISO27001 standard requires companies to identify and meet the needs of interested parties, such as customers and suppliers. That way, organizations can ensure that their information security management system is designed to meet their stakeholders needs. It also requires that organizations include processes for managing information security objectives in their ISMS, so that those objectives can be monitored and evaluated over time. It is essential for organizations to be able to demonstrate that their data-protection and security risk mitigation measures will be maintained and continuously improved. The new ISO27001 standard also makes it clear that changes to an organization's ISMS must be planned, with a specific process for communicating those changes to interested parties. This process should establish how communication should occur (rather than just who should communicate). Organizations now have to control processes, products, or services that are outside of the ISMS (as well as those that are inside of it), which means that they have to take a more holistic approach to managing both internal and outsourced operations. ISO 27002 has been updated, firstly the phrase 'code of practice' has been dropped from the title of the updated ISO 27002 standard. This approach better reflects the set's intended purpose as a reference of information security controls. The 27002 Standard itself is considerably longer than the previous version, and the controls have been reordered and updated. The new controls are identifiable by attribute, which makes it easier to focus on relevant categorical selections, which could reduce the compliance burden or help better integrate information security processes, making the ISMS easier to implement and manage. What is a reasonable for IT vendors and open source communities to update their cybersecurity approach to reflect the new requirements from the new norms? about this event: https://c3voc.de

After some years from first openSUSE image for a mobile phone, i think it is time to let people know about status of project for this topic. In other hand the talk will check features already working and some not fixed, of course at the end there will be a resume about future of the project. This talk will show to everyone wich devices can be considered to be used in a daily drive devices and wich ones are having improvements and will be usable in future. After some years from first openSUSE image for a mobile phone, i think it is time to let people know about status of project for this topic. In other hand the talk will check features already working and some not fixed, of course at the end there will be a resume about future of the project. This talk will show to everyone wich devices can be considered to be used in a daily drive devices and wich ones are having improvements and will be usable in future. about this event: https://c3voc.de

Ask your questions about the new Adaptable Linux Platform. This will be a discussion format with ALP Architects. Get all the answers about the next generation product line in this open format discussion. Ask your questions about the new Adaptable Linux Platform. This will be a discussion format with ALP Architects. Get all the answers about the next generation product line in this open format discussion. about this event: https://c3voc.de

The famous inventor Zangemann lives in a huge villa high above the city. Adults and children alike love his inventions and are desperate to have them. But then something happens: when Zangemann wants to take another close-up look at his inventions during a walk through the city, a child hits him in the shin with the skateboard. That hurts! Enraged, the inventor makes a momentous decision... The clever girl Ada sees through what is going on. Together with her friends, she forges a plan. This illustrated children's book (licensed under Creative Commons BY-SA) tells the story of the famous inventor Zangemann and the girl Ada, a curious tinkerer. Ada begins to experiment with hardware and software, and in the process realizes how crucial it is for her and others to control technology. Ada & Zangemann will inspire children's interest in tinkering and encourages shaping technology. > "A rousing tale of self-reliance, community, and standing up to bullies." —Cory Doctorow, Sci-Fi Author > "Ada & Zangemann proves that the argument for software and hardware freedom is simple: We should be able to do what we want with our stuff. . . . Electronics freedom means more learning and less waste, as Ada shows. Kids and adults alike will be entertained by this book, charmed by its illustrations, and inspired by Ada’s engineering spirit and impassioned activism." —Elizabeth Chamberlain, Director of Sustainability, iFixit > "What a fun read! I recognize myself in Ada at many moments." —Isabela Fernandes, Executive Director, The Tor project > "Even as a non-child, I was captivated by the story from the first page to the last. Kudos to the author for packaging difficult topics such as monopolies, lobbyism, digital divide, software freedom, digital autonomy, IoT, consumer control, e-waste and much more in a child-friendly form in an easily understandable and exciting storyline." —Jörg Luther, chief editor of the German Linux-Magazin, LinuxUser [Download the slides of the talk here](https://download.fsfe.org/presentations/20230526-mk-opensuse-ada-zangemann-reading.en.pdf) and you generic slides for doing your own readings with the book are available [in the FSFE's book repository](https://git.fsfe.org/FSFE/ada-zangemann). The famous inventor Zangemann lives in a huge villa high above the city. Adults and children alike love his inventions and are desperate to have them. But then something happens: when Zangemann wants to take another close-up look at his inventions during a walk through the city, a child hits him in the shin with the skateboard. That hurts! Enraged, the inventor makes a momentous decision... The clever girl Ada sees through what is going on. Together with her friends, she forges a plan. This illustrated children's book (licensed under Creative Commons BY-SA) tells the story of the famous inventor Zangemann and the girl Ada, a curious tinkerer. Ada begins to experiment with hardware and software, and in the process realizes how crucial it is for her and others to control technology. Ada & Zangemann will inspire children's interest in tinkering and encourages shaping technology. > "A rousing tale of self-reliance, community, and standing up to bullies." —Cory Doctorow, Sci-Fi Author > "Ada & Zangemann proves that the argument for software and hardware freedom is simple: We should be able to do what we want with our stuff. . . . Electronics freedom means more learning and less waste, as Ada shows. Kids and adults alike will be entertained by this book, charmed by its illustrations, and inspired by Ada’s engineering spirit and impassioned activism." —Elizabeth Chamberlain, Director of Sustainability, iFixit > "What a fun read! I recognize myself in Ada at many moments." —Isabela Fernandes, Executive Director, The Tor project > "Even as a non-child, I was captivated by the story from the first page to the last. Kudos to the author for packaging difficult topics such as monopolies, lobbyism, digital divide, software freedom, digital autonomy, IoT, consumer control, e-waste and much more in a child-friendly form in an easily understandable and exciting storyline." —Jörg Luther, chief editor of the German Linux-Magazin, LinuxUser [Download the slides of the talk here](https://download.fsfe.org/presentations/20230526-mk-opensuse-ada-zangemann-reading.en.pdf) and you generic slides for doing your own readings with the book are available [in the FSFE's book repository](https://git.fsfe.org/FSFE/ada-zangemann). about this event: https://c3voc.de

The Open Build Service can build just about everything from any source imaginable, including container images from a `Dockerfile` or a kiwi build description. But as usual, the devil lies in the details, and just pushing a `Dockerfile` to OBS would often lead to odd errors that do not occur in a local build. This talk covers the basics of building container images, best practices to follow as well as certain corner cases that you never wanted to know about, but might run into anyway. Come join this talk, so that you can start deploying and stop worrying about your container images ever getting out of date! The Open Build Service can build just about everything from any source imaginable, including container images from a `Dockerfile` or a kiwi build description. But as usual, the devil lies in the details, and just pushing a `Dockerfile` to OBS would often lead to odd errors that do not occur in a local build. This talk covers the basics of building container images, best practices to follow as well as certain corner cases that you never wanted to know about, but might run into anyway. Come join this talk, so that you can start deploying and stop worrying about your container images ever getting out of date! about this event: https://c3voc.de

How does the latest prototype of the Adaptable Linux Platform behave on AWS? What is required to build a EC2 compatible image via OBS? How does the workflow look like to go from OBS to an available and deployable AMI? What is the state of integration with AWS compared to openSUSE Leap? And what has SUSE NeuVector todo with all that? Let me take you on my journey and share my experiences, thoughts and results with you. How does the latest prototype of the Adaptable Linux Platform behave on AWS? What is required to build a EC2 compatible image via OBS? How does the workflow look like to go from OBS to an available and deployable AMI? What is the state of integration with AWS compared to openSUSE Leap? And what has SUSE NeuVector todo with all that? Let me take you on my journey and share my experiences, thoughts and results with you. about this event: https://c3voc.de

This session will present the latest news from the development of the next-gen SUSE Adaptable Linux Platform. We will cover both technical aspects of the platform as well as discuss implication for the Leap successor product. This session is recommended to attend before joining the panel discussion about ALP. This session will present the latest news from the development of the next-gen SUSE Adaptable Linux Platform. We will cover both technical aspects of the platform as well as discuss implication for the Leap successor product. This session is recommended to attend before joining the panel discussion about ALP. about this event: https://c3voc.de

There are multiple Source code management systems online today, systems like GitHub, GitLab, etc. They are widely used to manage your package sources. With the help of SCM/CI workflows, you can integrate an SCM with OBS and run different workflows. For example, on creating a new pull request, build a package on OBS and report back to SCM. The focus of the talk will be introducing SCM/CI integration. We'll present an implementation of a simple workflow and explain its limitations. There are multiple Source code management systems online today, systems like GitHub, GitLab, etc. They are widely used to manage your package sources. With the help of SCM/CI workflows, you can integrate an SCM with OBS and run different workflows. For example, on creating a new pull request, build a package on OBS and report back to SCM. The focus of the talk will be introducing SCM/CI integration. We'll present an implementation of a simple workflow and explain its limitations. about this event: https://c3voc.de

Scientific research relies heavily on software to analyze the vast amounts of data that are generated every day. But unfortunately, software development is not supposed to be part of a scientific career. Funding is usually granted for developing new algorithms rather than providing user-friendly features or maintaining software. In this talk, I will share our story of how scientific software can benefit from spinning out a software company. Our software identifies molecules in biological samples and enables researchers to detect toxic compounds, find molecules indicating diseases or discover the next drug candidate. For many years we have been developing the underlying algorithms based on combinatorial optimization, statistics and machine learning, in an academic context. We started as PhD students and postdocs at the University of Jena, and in 2019, we founded a spin-off company, Bright Giant GmbH, to provide services based on this software. This allows us to provide better support and implement features that are highly valuable to users but not of scientific novelty. A big part of the software is open-source and free to use for everybody. Furthermore, our SaaS is offered to the academic community free of charge by the University of Jena. With the right balance between free and commercial software, as well as open- and closed-source software, spin-off companies can accelerate scientific research. Scientific research relies heavily on software to analyze the vast amounts of data that are generated every day. But unfortunately, software development is not supposed to be part of a scientific career. Funding is usually granted for developing new algorithms rather than providing user-friendly features or maintaining software. In this talk, I will share our story of how scientific software can benefit from spinning out a software company. Our software identifies molecules in biological samples and enables researchers to detect toxic compounds, find molecules indicating diseases or discover the next drug candidate. For many years we have been developing the underlying algorithms based on combinatorial optimization, statistics and machine learning, in an academic context. We started as PhD students and postdocs at the University of Jena, and in 2019, we founded a spin-off company, Bright Giant GmbH, to provide services based on this software. This allows us to provide better support and implement features that are highly valuable to users but not of scientific novelty. A big part of the software is open-source and free to use for everybody. Furthermore, our SaaS is offered to the academic community free of charge by the University of Jena. With the right balance between free and commercial software, as well as open- and closed-source software, spin-off companies can accelerate scientific research. about this event: https://c3voc.de

Podman is a wonderful tool to work with containers. Podman containers can easily be managed as a systemd service. Podman can generate the systemd unit, so the user does not have to. In case you are managing your infrastructure and configuration with Ansible, you can also create the Podman container configuration with Ansible, thanks to the containers.podman collection. This talk gives a short introduction in both Podman containers and Ansible. Podman is a wonderful tool to work with containers. Podman containers can easily be managed as a systemd service. Podman can generate the systemd unit, so the user does not have to. In case you are managing your infrastructure and configuration with Ansible, you can also create the Podman container configuration with Ansible, thanks to the containers.podman collection. This talk gives a short introduction in both Podman containers and Ansible. about this event: https://c3voc.de

The RISC-V ISA is highly modular with cpu vendors being able to pick from a number of standardized extensions and even invent their own. Yet we want a unified kernel Image and userspace that does not have to care about which extensions are available but still is able to use them. So after showing where this matters, I want to introduce some techniques the kernel has in its lower levels that allows us to do this performantly. The RISC-V ISA is highly modular with cpu vendors being able to pick from a number of standardized extensions and even invent their own. Yet we want a unified kernel Image and userspace that does not have to care about which extensions are available but still is able to use them. So after showing where this matters, I want to introduce some techniques the kernel has in its lower levels that allows us to do this performantly. about this event: https://c3voc.de

The DNF package manager has been available in openSUSE for some time now, providing all kinds of useful functionality and enabling a consistent software management experience across RPM distributions. With DNF version 5 coming later this year, what does this look like from the perspective of an openSUSE user? Is this finally the version that brings us to a unified package manager for RPM distributions? This talk will discuss how DNF version 5 in openSUSE looks and provide a demonstration of an openSUSE system with it in place. The DNF package manager has been available in openSUSE for some time now, providing all kinds of useful functionality and enabling a consistent software management experience across RPM distributions. With DNF version 5 coming later this year, what does this look like from the perspective of an openSUSE user? Is this finally the version that brings us to a unified package manager for RPM distributions? This talk will discuss how DNF version 5 in openSUSE looks and provide a demonstration of an openSUSE system with it in place. about this event: https://c3voc.de

If your household has several Linux systems (of various distros/ flavors) running, updating them all can be time consuming not just as a mental load (even if automated) but can take up a lot of WAN bandwidth! Wouldn't it be nice if you could download repositores locally and update from a machine on your own LAN? Benefits include much faster updates, more control over local updates, and less cluttered WAN traffic. In this talk, I will go over the setup and benefits of running a local Repository Mirroring Tool (RMT) instance on openSUSE Leap, that can serve all your other systems' update needs. This aims to be a comprehensive guide, covering all the specifics of RMT setup locally: hardware requirements; downloading the pattern to allocating disk space; setting up systemd unit files and timers; subscribing your other systems to the RMT server; and some simple troubleshooting for commonly observed issues. RMT is an opensource tool available from SUSE written in Ruby. The setup for RMT is currently lacking in documentation for openSUSE specifically. Consider this a first step in making a more specifically open version of RMT (i.e. at present the "client subscription script" fails when it calls proprietary SUSE URLs). If your household has several Linux systems (of various distros/ flavors) running, updating them all can be time consuming not just as a mental load (even if automated) but can take up a lot of WAN bandwidth! Wouldn't it be nice if you could download repositores locally and update from a machine on your own LAN? Benefits include much faster updates, more control over local updates, and less cluttered WAN traffic. In this talk, I will go over the setup and benefits of running a local Repository Mirroring Tool (RMT) instance on openSUSE Leap, that can serve all your other systems' update needs. This aims to be a comprehensive guide, covering all the specifics of RMT setup locally: hardware requirements; downloading the pattern to allocating disk space; setting up systemd unit files and timers; subscribing your other systems to the RMT server; and some simple troubleshooting for commonly observed issues. RMT is an opensource tool available from SUSE written in Ruby. The setup for RMT is currently lacking in documentation for openSUSE specifically. Consider this a first step in making a more specifically open version of RMT (i.e. at present the "client subscription script" fails when it calls proprietary SUSE URLs). about this event: https://c3voc.de

Agama, the artist previously known as D-Installer, is the result of a love story between YaST and Cockpit. Although it's still in its infancy, Agama is already able to install openSUSE Tumbleweed and several ALP-based distributions both in virtual machines and all kind of bare metal systems. Even in unattended fashion! Join this session to learn more about the present and future possibilities, the technical architecture, the relationship with other projects like YaST and the opportunities to contribute. Agama, the artist previously known as D-Installer, is the result of a love story between YaST and Cockpit. Although it's still in its infancy, Agama is already able to install openSUSE Tumbleweed and several ALP-based distributions both in virtual machines and all kind of bare metal systems. Even in unattended fashion! Join this session to learn more about the present and future possibilities, the technical architecture, the relationship with other projects like YaST and the opportunities to contribute. about this event: https://c3voc.de

This talk gives a short introduction to Ansible and shows how it is being packaged in openSUSE. It touches on roles and collections that allow users to easily re-use existing Ansible code for their own needs. To make sure that the Ansible code has valid syntax and matches the guidelines defined by the Ansible community, it can be checked with ansible-lint. ansible-lint is also available for Tumbleweed. This talk gives a short introduction to Ansible and shows how it is being packaged in openSUSE. It touches on roles and collections that allow users to easily re-use existing Ansible code for their own needs. To make sure that the Ansible code has valid syntax and matches the guidelines defined by the Ansible community, it can be checked with ansible-lint. ansible-lint is also available for Tumbleweed. about this event: https://c3voc.de

While Podman started out as a replacement for Docker, it has now become a well-established container runtime. With containerd as the backend and nerdctl as the frontend there is now a new contender in the container runtime ecosystem challenging both Podman and Docker. In this talk, we will introduce containerd, a lightweight and flexible open-source container runtime, and nerdctl, a command-line interface for containerd. We will then take a look at these two tools together as an alternative to both Docker and Podman, especially taking a look at new and exciting features implemented in nerdctl. Be sure to join this session to find out how nerdctl can accelerate rootless container networking, encrypt your images and much, much more! While Podman started out as a replacement for Docker, it has now become a well-established container runtime. With containerd as the backend and nerdctl as the frontend there is now a new contender in the container runtime ecosystem challenging both Podman and Docker. In this talk, we will introduce containerd, a lightweight and flexible open-source container runtime, and nerdctl, a command-line interface for containerd. We will then take a look at these two tools together as an alternative to both Docker and Podman, especially taking a look at new and exciting features implemented in nerdctl. Be sure to join this session to find out how nerdctl can accelerate rootless container networking, encrypt your images and much, much more! about this event: https://c3voc.de

Introducing the [Geeko Foundation](https://geekos.org/). Find out all you want to know during this sessions. Introducing the [Geeko Foundation](https://geekos.org/). Find out all you want to know during this sessions. about this event: https://c3voc.de

Do you want to test Kubernetes end-to-end on your cloud? Also curious to know how other projects in the Kubernetes ecosystem do this? If so, you will love this Kubetest2 session. Kubetest2 is a testing framework maintained by Kubernetes SIG Testing that allows you to test Kubernetes code changes both locally and on the cloud. It manages cluster configuration, e2e testing, log collection, and test environment disposal. Kubetest2 natively supports GCP, GKE & KinD deployers, but also enables writing custom deployers out-of-tree. A custom Kubetest2 deployer is possible, but it needs some prior context & knowledge of Kubetest2 internals. To that end, this talk will provide attendees with the following takeaways: * What is Kubetest2, overview of its architecture, and its evolution from its predecessor Kubetest * Benefits of using Kubetest2 as a testing tool for your project * Reasons to use a bespoke Kubetest2 deployer * And, a step-by-step demo for constructing a custom kubetest2 deployer for your own cloud provider Slides available at https://psaggu.com/assets/osc2023/k2p.pdf Do you want to test Kubernetes end-to-end on your cloud? Also curious to know how other projects in the Kubernetes ecosystem do this? If so, you will love this Kubetest2 session. Kubetest2 is a testing framework maintained by Kubernetes SIG Testing that allows you to test Kubernetes code changes both locally and on the cloud. It manages cluster configuration, e2e testing, log collection, and test environment disposal. Kubetest2 natively supports GCP, GKE & KinD deployers, but also enables writing custom deployers out-of-tree. A custom Kubetest2 deployer is possible, but it needs some prior context & knowledge of Kubetest2 internals. To that end, this talk will provide attendees with the following takeaways: * What is Kubetest2, overview of its architecture, and its evolution from its predecessor Kubetest * Benefits of using Kubetest2 as a testing tool for your project * Reasons to use a bespoke Kubetest2 deployer * And, a step-by-step demo for constructing a custom kubetest2 deployer for your own cloud provider Slides available at https://psaggu.com/assets/osc2023/k2p.pdf about this event: https://c3voc.de

Nach dem gescheiterten Mediengesetz suchen die Verlage neue Einnahmequellen. So ist das «Leistungsschutzrecht», auch bekannt als «Linksteuer», nun wieder auf dem politischen Parkett. Bereits in der Debatte zum Urheberrecht 2019 wurde überraschend ein solches beschlossen – und nach breiten Protesten wieder verworfen. Wir betrachten die Mechanismen des Leistungsschutzrechts kritisch und schauen, wo der politische Prozess bei diesem neuen Gesetz aktuell steht (ein Entwurf wurde in diesen Tagen veröffentlicht). Andreas von Gunten ist Unternehmer und Verleger, unter anderem von dnip.ch und beschäftigt sich seit mehr als zehn Jahren mit dem Leistungsschutzrecht. about this event: https://www.digitale-gesellschaft.ch/event/netzpolitischer-abend-zum-thema-leistungsschutzrecht/

In den letzten Monaten hat sich Lukas an einer Frage festgebissen: Wie entwickelt sich der Baumbestand in deutschen Städten? Eigentlich, so dachte er, sei das leicht herauszufinden. Nach Tagen auf kommunalen Websites, über 100 „Frag den Staat“-Anfragen und einer riesigen Tabelle ist er nun nicht nur schlauer, was den Stadtbaum-Bestand angeht, sondern auch, was die fehlende Digitalisierung und das (un)verständnis für Open-Data auf kommunaler Ebene angeht. Quellen und Referenzen: https://tvluke.de/baumbilanzen-befreien-freitalk-1.html#baumbilanzen-befreien-freitalk-1 This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License (CC BY NC ND 4.0). https://creativecommons.org/licenses/by-nc-nd/4.0/ about this event: https://chaotikum.org/blog/2023/05/07/freitalk-baumbilanzen/