osc18

Starting with openSUSE Leap 42.2, a lot of cooperation has been done to bridge gaps between openSUSE and SUSE Linux Enterprise distributions. Things have been improving nicely with openSUSE Leap 42.3. We'll go into details on what this cooperation means for both openSUSE contributors and for SUSE and how we ensure it takes place. We will also discuss how we adjusted SLE15 development and how was done in harmony with openSUSE Tumbleweed (rolling release). Starting with openSUSE Leap 42.2, a lot of cooperation has been done to bridge gaps between openSUSE and SUSE Linux Enterprise distributions. Things have been improving nicely with openSUSE Leap 42.3. We'll go into details on what this cooperation means for both openSUSE contributors and for SUSE and how we ensure it takes place. We will also discuss how we adjusted SLE15 development and how was done in harmony with openSUSE Tumbleweed (rolling release). about this event: https://c3voc.de

Over the last year I have completed a large amount of work on the tools integral to the openSUSE release process and as such have become familiar with the scope, workflow, and general problems involved. After mulling over these general shortcomings it becomes clear that taking a step back and rethinking some core concepts such as the build service and the way the release tools interact with it is necessary. I have since explored and prototyped a new approach that should drastically reduce the maintenance burden on the openSUSE project while solving major pitfalls, improving transparency, solving a large number of open feature requests, and providing entirely new options. At this point it seems appropriate to present the concept and prototype to a wider audience before investing too much further. Hopefully, the openSUSE community will be as excited about this direction as I am. To start, some background on the type of work being done over the last year will be provided. Metrics will be provided to demonstrate the effect and importance of the work. After which details of pitfalls that force a cumbersome workflow will be provided in addition to covering some feature requests and general improvements desired for release work. The new approach will then be explained and how it resolves a large number of these problems while drastically reducing the overall code-base. With the reduction in the code-base along with adapting modern practices it should be easier to involve new contributors. Preferably key stake holders from OBS and release teams will be present and participate in a healthy discussion. Over the last year I have completed a large amount of work on the tools integral to the openSUSE release process and as such have become familiar with the scope, workflow, and general problems involved. After mulling over these general shortcomings it becomes clear that taking a step back and rethinking some core concepts such as the build service and the way the release tools interact with it is necessary. I have since explored and prototyped a new approach that should drastically reduce the maintenance burden on the openSUSE project while solving major pitfalls, improving transparency, solving a large number of open feature requests, and providing entirely new options. At this point it seems appropriate to present the concept and prototype to a wider audience before investing too much further. Hopefully, the openSUSE community will be as excited about this direction as I am. To start, some background on the type of work being done over the last year will be provided. Metrics will be provided to demonstrate the effect and importance of the work. After which details of pitfalls that force a cumbersome workflow will be provided in addition to covering some feature requests and general improvements desired for release work. The new approach will then be explained and how it resolves a large number of these problems while drastically reducing the overall code-base. With the reduction in the code-base along with adapting modern practices it should be easier to involve new contributors. Preferably key stake holders from OBS and release teams will be present and participate in a healthy discussion. about this event: https://c3voc.de

Open Build Service (OBS) development has increased in an exponential way. David will briefly explain the evolution of the OBS frontend in the last year, and also some of the awesome features that have been included recently. Kiwi Editor, Cloud Uploader features that are already available will not be the only ones we will talk about. Adrian will talk about the new OBS backend features as Docker build support, AppImage, Docker registry, etc. And last but not least, Marco will introduce us to OSC new features. We will also give some hints about the upcoming features we have in mind for the future of OBS. Sounds interesting, right? Don't miss this talk and take advantage of knowing all the improvements that can make your work easier using OBS. Open Build Service (OBS) development has increased in an exponential way. David will briefly explain the evolution of the OBS frontend in the last year, and also some of the awesome features that have been included recently. Kiwi Editor, Cloud Uploader features that are already available will not be the only ones we will talk about. Adrian will talk about the new OBS backend features as Docker build support, AppImage, Docker registry, etc. And last but not least, Marco will introduce us to OSC new features. We will also give some hints about the upcoming features we have in mind for the future of OBS. Sounds interesting, right? Don't miss this talk and take advantage of knowing all the improvements that can make your work easier using OBS. about this event: https://c3voc.de

kanku is designed to give you a better integration of your kiwi images built in Open Build Service (OBS) into your development and testing workflow. It provides a framework for simple automation of complex setups, e.g. to prepare your development environment or run simple tests. This talk will give an overview of the motivation/goals and basic concepts/architecture of kanku. Links: * Presentation - https://m0ses.github.io/kanku-presentation/overview.html#/cover-page * Github Pages - https://m0ses.github.io/kanku/ * Github Code - https://github.com/M0ses/kanku/ kanku is designed to give you a better integration of your kiwi images built in Open Build Service (OBS) into your development and testing workflow. It provides a framework for simple automation of complex setups, e.g. to prepare your development environment or run simple tests. This talk will give an overview of the motivation/goals and basic concepts/architecture of kanku. Links: * Presentation - https://m0ses.github.io/kanku-presentation/overview.html#/cover-page * Github Pages - https://m0ses.github.io/kanku/ * Github Code - https://github.com/M0ses/kanku/ about this event: https://c3voc.de

The openSUSE Board (Richard Brown, Gertjan Lettink, Christian Boltz, Sarah Julia Kriesch, Ana María Martínez Gómez and Simon Lees) will present the outcome of their last F2F meeting, where they started driving its collective agenda for the next year. After that, everybody is welcome to ask questions, give feedback, make suggestions and present ideas. The openSUSE Board (Richard Brown, Gertjan Lettink, Christian Boltz, Sarah Julia Kriesch, Ana María Martínez Gómez and Simon Lees) will present the outcome of their last F2F meeting, where they started driving its collective agenda for the next year. After that, everybody is welcome to ask questions, give feedback, make suggestions and present ideas. about this event: https://c3voc.de

Creating development setups can be tedious, error-prone and quite horrifying to novice contributors of Open Source projects. You would set up a virtual machine, install the required software and spend quite some time configuring it. On top of this, your setup would require maintenance and updates. A more modern approach is featured in this talk: Create a reproducible environment, have automatic updates to new package versions just by using OBS to build your Docker container image from RPMs and a kiwi XML file. No more fiddling with VMs, no more manual install and configuration marathons - just download and run your ready-to-use Docker image from OBS. Creating development setups can be tedious, error-prone and quite horrifying to novice contributors of Open Source projects. You would set up a virtual machine, install the required software and spend quite some time configuring it. On top of this, your setup would require maintenance and updates. A more modern approach is featured in this talk: Create a reproducible environment, have automatic updates to new package versions just by using OBS to build your Docker container image from RPMs and a kiwi XML file. No more fiddling with VMs, no more manual install and configuration marathons - just download and run your ready-to-use Docker image from OBS. about this event: https://c3voc.de

Starting with openSUSE Leap 42.2, a lot of cooperation has been done to bridge gaps between openSUSE and SUSE Linux Enterprise distributions. Things have been improving nicely with openSUSE Leap 42.3. We'll go into details on what this cooperation means for both openSUSE contributors and for SUSE and how we ensure it takes place. We will also discuss how we adjusted SLE15 development and how was done in harmony with openSUSE Tumbleweed (rolling release). Starting with openSUSE Leap 42.2, a lot of cooperation has been done to bridge gaps between openSUSE and SUSE Linux Enterprise distributions. Things have been improving nicely with openSUSE Leap 42.3. We'll go into details on what this cooperation means for both openSUSE contributors and for SUSE and how we ensure it takes place. We will also discuss how we adjusted SLE15 development and how was done in harmony with openSUSE Tumbleweed (rolling release). about this event: https://c3voc.de

If you ever wondered how the OBS gets developed, this talk will provide some insights into how the OBS development works including tools we use (e.g. depfu, hakiri, codecov) and workflows we follow (e.g. Scrum). OBS developers have also changed a lot in the last time. The OBS frontend team has doubled its size within the last 2 years. We will explain how we brought everyone up to speed with techniques and methodologies such as Scrum and mob / pair programming. The reference installation build.opensuse.org is now also OBS frontend team responsibility. We changed the deployment process by introducing a demolition squad role. Beside build.opensuse.org, we also release OBS regularly and are in charge of quality assurance using e.g. openQA and Kanku. Last but not least, we will cover how you can participate in OBS development, both as a developer and suggesting changes and features. If you ever wondered how the OBS gets developed, this talk will provide some insights into how the OBS development works including tools we use (e.g. depfu, hakiri, codecov) and workflows we follow (e.g. Scrum). OBS developers have also changed a lot in the last time. The OBS frontend team has doubled its size within the last 2 years. We will explain how we brought everyone up to speed with techniques and methodologies such as Scrum and mob / pair programming. The reference installation build.opensuse.org is now also OBS frontend team responsibility. We changed the deployment process by introducing a demolition squad role. Beside build.opensuse.org, we also release OBS regularly and are in charge of quality assurance using e.g. openQA and Kanku. Last but not least, we will cover how you can participate in OBS development, both as a developer and suggesting changes and features. about this event: https://c3voc.de

At CZ.NIC, we are making open source routers. Those come with automatic updates, plenty of software available in repositories, root ssh account and other nice features. What challenges does it bring? How do we cope with them? Why would you want open source router anyway? What open source project are we building on top? And what actually spinned off out of our router? At CZ.NIC, we are making open source routers. Those come with automatic updates, plenty of software available in repositories, root ssh account and other nice features. What challenges does it bring? How do we cope with them? Why would you want open source router anyway? What open source project are we building on top? And what actually spinned off out of our router? about this event: https://c3voc.de

Creating development setups can be tedious, error-prone and quite horrifying to novice contributors of Open Source projects. You would set up a virtual machine, install the required software and spend quite some time configuring it. On top of this, your setup would require maintenance and updates. A more modern approach is featured in this talk: Create a reproducible environment, have automatic updates to new package versions just by using OBS to build your Docker container image from RPMs and a kiwi XML file. No more fiddling with VMs, no more manual install and configuration marathons - just download and run your ready-to-use Docker image from OBS. Creating development setups can be tedious, error-prone and quite horrifying to novice contributors of Open Source projects. You would set up a virtual machine, install the required software and spend quite some time configuring it. On top of this, your setup would require maintenance and updates. A more modern approach is featured in this talk: Create a reproducible environment, have automatic updates to new package versions just by using OBS to build your Docker container image from RPMs and a kiwi XML file. No more fiddling with VMs, no more manual install and configuration marathons - just download and run your ready-to-use Docker image from OBS. about this event: https://c3voc.de

Curious about openSUSE Kubic and using it for running your containers workloads ? I will introduce the various way to deploy openSUSE Kubic and explain how to get started with systems operations and containers management. From scratch to fully running containers in 45 minutes :) Curious about openSUSE Kubic and using it for running your containers workloads ? I will introduce the various way to deploy openSUSE Kubic and explain how to get started with systems operations and containers management. From scratch to fully running containers in 45 minutes :) about this event: https://c3voc.de

If you ever wondered how the OBS gets developed, this talk will provide some insights into how the OBS development works including tools we use (e.g. depfu, hakiri, codecov) and workflows we follow (e.g. Scrum). OBS developers have also changed a lot in the last time. The OBS frontend team has doubled its size within the last 2 years. We will explain how we brought everyone up to speed with techniques and methodologies such as Scrum and mob / pair programming. The reference installation build.opensuse.org is now also OBS frontend team responsibility. We changed the deployment process by introducing a demolition squad role. Beside build.opensuse.org, we also release OBS regularly and are in charge of quality assurance using e.g. openQA and Kanku. Last but not least, we will cover how you can participate in OBS development, both as a developer and suggesting changes and features. If you ever wondered how the OBS gets developed, this talk will provide some insights into how the OBS development works including tools we use (e.g. depfu, hakiri, codecov) and workflows we follow (e.g. Scrum). OBS developers have also changed a lot in the last time. The OBS frontend team has doubled its size within the last 2 years. We will explain how we brought everyone up to speed with techniques and methodologies such as Scrum and mob / pair programming. The reference installation build.opensuse.org is now also OBS frontend team responsibility. We changed the deployment process by introducing a demolition squad role. Beside build.opensuse.org, we also release OBS regularly and are in charge of quality assurance using e.g. openQA and Kanku. Last but not least, we will cover how you can participate in OBS development, both as a developer and suggesting changes and features. about this event: https://c3voc.de

Following up on last year's talk (https://events.opensuse.org/conference/oSC17/program/proposal/1246) I intend to give an update on hardware support in openSUSE and software support for new boards. This will include an update on Meltdown/Spectre mitigations and what users need to take care of. Following up on last year's talk (https://events.opensuse.org/conference/oSC17/program/proposal/1246) I intend to give an update on hardware support in openSUSE and software support for new boards. This will include an update on Meltdown/Spectre mitigations and what users need to take care of. about this event: https://c3voc.de

The openSUSE Board (Richard Brown, Gertjan Lettink, Christian Boltz, Sarah Julia Kriesch, Ana María Martínez Gómez and Simon Lees) will present the outcome of their last F2F meeting, where they started driving its collective agenda for the next year. After that, everybody is welcome to ask questions, give feedback, make suggestions and present ideas. The openSUSE Board (Richard Brown, Gertjan Lettink, Christian Boltz, Sarah Julia Kriesch, Ana María Martínez Gómez and Simon Lees) will present the outcome of their last F2F meeting, where they started driving its collective agenda for the next year. After that, everybody is welcome to ask questions, give feedback, make suggestions and present ideas. about this event: https://c3voc.de

Over the last year I have completed a large amount of work on the tools integral to the openSUSE release process and as such have become familiar with the scope, workflow, and general problems involved. After mulling over these general shortcomings it becomes clear that taking a step back and rethinking some core concepts such as the build service and the way the release tools interact with it is necessary. I have since explored and prototyped a new approach that should drastically reduce the maintenance burden on the openSUSE project while solving major pitfalls, improving transparency, solving a large number of open feature requests, and providing entirely new options. At this point it seems appropriate to present the concept and prototype to a wider audience before investing too much further. Hopefully, the openSUSE community will be as excited about this direction as I am. To start, some background on the type of work being done over the last year will be provided. Metrics will be provided to demonstrate the effect and importance of the work. After which details of pitfalls that force a cumbersome workflow will be provided in addition to covering some feature requests and general improvements desired for release work. The new approach will then be explained and how it resolves a large number of these problems while drastically reducing the overall code-base. With the reduction in the code-base along with adapting modern practices it should be easier to involve new contributors. Preferably key stake holders from OBS and release teams will be present and participate in a healthy discussion. Over the last year I have completed a large amount of work on the tools integral to the openSUSE release process and as such have become familiar with the scope, workflow, and general problems involved. After mulling over these general shortcomings it becomes clear that taking a step back and rethinking some core concepts such as the build service and the way the release tools interact with it is necessary. I have since explored and prototyped a new approach that should drastically reduce the maintenance burden on the openSUSE project while solving major pitfalls, improving transparency, solving a large number of open feature requests, and providing entirely new options. At this point it seems appropriate to present the concept and prototype to a wider audience before investing too much further. Hopefully, the openSUSE community will be as excited about this direction as I am. To start, some background on the type of work being done over the last year will be provided. Metrics will be provided to demonstrate the effect and importance of the work. After which details of pitfalls that force a cumbersome workflow will be provided in addition to covering some feature requests and general improvements desired for release work. The new approach will then be explained and how it resolves a large number of these problems while drastically reducing the overall code-base. With the reduction in the code-base along with adapting modern practices it should be easier to involve new contributors. Preferably key stake holders from OBS and release teams will be present and participate in a healthy discussion. about this event: https://c3voc.de

kanku is designed to give you a better integration of your kiwi images built in Open Build Service (OBS) into your development and testing workflow. It provides a framework for simple automation of complex setups, e.g. to prepare your development environment or run simple tests. This talk will give an overview of the motivation/goals and basic concepts/architecture of kanku. Links: * Presentation - https://m0ses.github.io/kanku-presentation/overview.html#/cover-page * Github Pages - https://m0ses.github.io/kanku/ * Github Code - https://github.com/M0ses/kanku/ kanku is designed to give you a better integration of your kiwi images built in Open Build Service (OBS) into your development and testing workflow. It provides a framework for simple automation of complex setups, e.g. to prepare your development environment or run simple tests. This talk will give an overview of the motivation/goals and basic concepts/architecture of kanku. Links: * Presentation - https://m0ses.github.io/kanku-presentation/overview.html#/cover-page * Github Pages - https://m0ses.github.io/kanku/ * Github Code - https://github.com/M0ses/kanku/ about this event: https://c3voc.de

A few years ago we started adding cross-compiler packages to Tumbleweed, based on our maintained GCC packages. There have been two recent toolchain additions, more are still in the works, and several challenges remain - such as on our end Leap and PackageHub. A few years ago we started adding cross-compiler packages to Tumbleweed, based on our maintained GCC packages. There have been two recent toolchain additions, more are still in the works, and several challenges remain - such as on our end Leap and PackageHub. about this event: https://c3voc.de

At CZ.NIC, we are making open source routers. Those come with automatic updates, plenty of software available in repositories, root ssh account and other nice features. What challenges does it bring? How do we cope with them? Why would you want open source router anyway? What open source project are we building on top? And what actually spinned off out of our router? At CZ.NIC, we are making open source routers. Those come with automatic updates, plenty of software available in repositories, root ssh account and other nice features. What challenges does it bring? How do we cope with them? Why would you want open source router anyway? What open source project are we building on top? And what actually spinned off out of our router? about this event: https://c3voc.de

Open Build Service (OBS) development has increased in an exponential way. David will briefly explain the evolution of the OBS frontend in the last year, and also some of the awesome features that have been included recently. Kiwi Editor, Cloud Uploader features that are already available will not be the only ones we will talk about. Adrian will talk about the new OBS backend features as Docker build support, AppImage, Docker registry, etc. And last but not least, Marco will introduce us to OSC new features. We will also give some hints about the upcoming features we have in mind for the future of OBS. Sounds interesting, right? Don't miss this talk and take advantage of knowing all the improvements that can make your work easier using OBS. Open Build Service (OBS) development has increased in an exponential way. David will briefly explain the evolution of the OBS frontend in the last year, and also some of the awesome features that have been included recently. Kiwi Editor, Cloud Uploader features that are already available will not be the only ones we will talk about. Adrian will talk about the new OBS backend features as Docker build support, AppImage, Docker registry, etc. And last but not least, Marco will introduce us to OSC new features. We will also give some hints about the upcoming features we have in mind for the future of OBS. Sounds interesting, right? Don't miss this talk and take advantage of knowing all the improvements that can make your work easier using OBS. about this event: https://c3voc.de

Curious about openSUSE Kubic and using it for running your containers workloads ? I will introduce the various way to deploy openSUSE Kubic and explain how to get started with systems operations and containers management. From scratch to fully running containers in 45 minutes :) Curious about openSUSE Kubic and using it for running your containers workloads ? I will introduce the various way to deploy openSUSE Kubic and explain how to get started with systems operations and containers management. From scratch to fully running containers in 45 minutes :) about this event: https://c3voc.de