Chaos Computer Club - archive feed

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

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

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

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

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

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

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

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

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

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