https://media.ccc.de/c/osc19 This feed contains all events from osc19 as opus see video outro Thu, 23 Jan 2025 18:42:58 -0000 https://static.media.ccc.de/media/events/osc/2019/osc19_logo.png https://media.ccc.de/c/osc19 https://media.ccc.de/v/2525-identity-in-openstack-the-challenge-of-multitenancy Keystone is the OpenStack component responsible for identity management and user authentication and authorization, which has unique challenges in cloud-like environments where secure sharing of resources is an essential requirement and yet is fundamental to the core idea of collaborative computing. This introductory talk will give an overview of the keystone project, including: * The many ways users and applications can securely authenticate with keystone, including SAML2.0, OpenID Connect, X.509 and Kerberos * The implications for authorization in a multitenant environment and how role-based access control is designed in keystone * How keystone relates to projects outside of the OpenStack ecosystem such as Kubernetes Keystone is the OpenStack component responsible for identity management and user authentication and authorization, which has unique challenges in cloud-like environments where secure sharing of resources is an essential requirement and yet is fundamental to the core idea of collaborative computing. This introductory talk will give an overview of the keystone project, including: * The many ways users and applications can securely authenticate with keystone, including SAML2.0, OpenID Connect, X.509 and Kerberos * The implications for authorization in a multitenant environment and how role-based access control is designed in keystone * How keystone relates to projects outside of the OpenStack ecosystem such as Kubernetes about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2525-eng-Identity_in_OpenStack_the_Challenge_of_Multitenancy_opus.opus?1558878424 -CVvXbWXJE9qM7F5NaSGGQ 2019-05-26T00:00:00+02:00 Colleen Murphy No osc19, 2525, Cloud and Containers Keystone is the OpenStack component responsible for identity management and user authentication and authorization, which has unique challenges in cloud-like environments where secure sharing of resources is an essential requirement and yet is fundamental to the core idea of collaborative computing. This introductory talk will give an overview of the keystone project, including: * The many ways users and applications can securely authenticate with keystone, including SAML2.0, OpenID Connect, X.509 and Kerberos * The implications for authorization in a multitenant environment and how role-based access control is designed in keystone * How keystone relates to projects outside of the OpenStack ecosystem such as Kubernetes Keystone is the OpenStack component responsible for identity management and user authentication and authorization, which has unique challenges in cloud-like environments where secure sharing of resources is an essential requirement and yet is fundamental to the core idea of collaborative computing. This introductory talk will give an overview of the keystone project, including: * The many ways users and applications can securely authenticate with keystone, including SAML2.0, OpenID Connect, X.509 and Kerberos * The implications for authorization in a multitenant environment and how role-based access control is designed in keystone * How keystone relates to projects outside of the OpenStack ecosystem such as Kubernetes about this event: https://c3voc.de 00:26:25 https://media.ccc.de/v/2240-ae-dir-authorized-entitites-directory This talk will present a concept and real-world implementation of an identity and access management system (IAM) purely based on OpenLDAP. The main goal of Æ-DIR (besides challenging Unicode handling in various software with its name) is to follow the delegation, need-to-know and least-privilege principles as strictly as possible. The visibility of user, group, sudoers, etc. is limited by OpenLDAP’s set-based ACLs. All systems and services, no exception(!), have to individually authenticate to be authorized to access Æ-DIR. The talk will give some additional information about the secure base configuration of OpenLDAP and a special NSS/PAM caching demon developed for lower resource usage. This talk will present a concept and real-world implementation of an identity and access management system (IAM) purely based on OpenLDAP. The main goal of Æ-DIR (besides challenging Unicode handling in various software with its name) is to follow the delegation, need-to-know and least-privilege principles as strictly as possible. The visibility of user, group, sudoers, etc. is limited by OpenLDAP’s set-based ACLs. All systems and services, no exception(!), have to individually authenticate to be authorized to access Æ-DIR. The talk will give some additional information about the secure base configuration of OpenLDAP and a special NSS/PAM caching demon developed for lower resource usage. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2240-eng-AE-DIR_--_Authorized_Entitites_Directory_opus.opus?1558878294 dVYz0GFKsKPfIUQDmTJmqQ 2019-05-26T00:00:00+02:00 stroeder No osc19, 2240, Open Source Identity and Access Management with OpenLDAP This talk will present a concept and real-world implementation of an identity and access management system (IAM) purely based on OpenLDAP. The main goal of Æ-DIR (besides challenging Unicode handling in various software with its name) is to follow the delegation, need-to-know and least-privilege principles as strictly as possible. The visibility of user, group, sudoers, etc. is limited by OpenLDAP’s set-based ACLs. All systems and services, no exception(!), have to individually authenticate to be authorized to access Æ-DIR. The talk will give some additional information about the secure base configuration of OpenLDAP and a special NSS/PAM caching demon developed for lower resource usage. This talk will present a concept and real-world implementation of an identity and access management system (IAM) purely based on OpenLDAP. The main goal of Æ-DIR (besides challenging Unicode handling in various software with its name) is to follow the delegation, need-to-know and least-privilege principles as strictly as possible. The visibility of user, group, sudoers, etc. is limited by OpenLDAP’s set-based ACLs. All systems and services, no exception(!), have to individually authenticate to be authorized to access Æ-DIR. The talk will give some additional information about the secure base configuration of OpenLDAP and a special NSS/PAM caching demon developed for lower resource usage. about this event: https://c3voc.de 00:44:28 https://media.ccc.de/v/2282-business-applications-as-free-software-demystifying-fud Everyone knows that Free Software such as Linux, Apache or PostgreSQL are the backbone of many data centers (DC) and cloud offerings. The Internet as we know it today would not exist without Free & OpenSource Software (FOSS) But the more Free Software leaves the DC and gets closer to the 'Enduser', the more myth are build around FOSS. Linux on a Desktop? GIMP Instead of Photoshop? Running your business on a Free ERP-System? Fear, Uncertainty and Doubts (FUD) are spread to protect market share for proprietary solutions. In this talk I will take a look at some FUD, and share some thoughts about answers to the myths. Everyone knows that Free Software such as Linux, Apache or PostgreSQL are the backbone of many data centers (DC) and cloud offerings. The Internet as we know it today would not exist without Free & OpenSource Software (FOSS) But the more Free Software leaves the DC and gets closer to the 'Enduser', the more myth are build around FOSS. Linux on a Desktop? GIMP Instead of Photoshop? Running your business on a Free ERP-System? Fear, Uncertainty and Doubts (FUD) are spread to protect market share for proprietary solutions. In this talk I will take a look at some FUD, and share some thoughts about answers to the myths. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2282-eng-Business_Applications_as_Free_Software_-_Demystifying_FUD_opus.opus?1558878034 lzk3pJgMkSKPXG8vHMiwjg 2019-05-26T00:00:00+02:00 Axel Braun No osc19, 2282, Open Source You should not believe everything that Big Money tells you..... Everyone knows that Free Software such as Linux, Apache or PostgreSQL are the backbone of many data centers (DC) and cloud offerings. The Internet as we know it today would not exist without Free & OpenSource Software (FOSS) But the more Free Software leaves the DC and gets closer to the 'Enduser', the more myth are build around FOSS. Linux on a Desktop? GIMP Instead of Photoshop? Running your business on a Free ERP-System? Fear, Uncertainty and Doubts (FUD) are spread to protect market share for proprietary solutions. In this talk I will take a look at some FUD, and share some thoughts about answers to the myths. Everyone knows that Free Software such as Linux, Apache or PostgreSQL are the backbone of many data centers (DC) and cloud offerings. The Internet as we know it today would not exist without Free & OpenSource Software (FOSS) But the more Free Software leaves the DC and gets closer to the 'Enduser', the more myth are build around FOSS. Linux on a Desktop? GIMP Instead of Photoshop? Running your business on a Free ERP-System? Fear, Uncertainty and Doubts (FUD) are spread to protect market share for proprietary solutions. In this talk I will take a look at some FUD, and share some thoughts about answers to the myths. about this event: https://c3voc.de 00:41:42 https://media.ccc.de/v/2378-annual-discussion-with-opensuse-board The openSUSE Board 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 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 Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2378-eng-Annual_Discussion_with_openSUSE_Board_opus.opus?1558877584 Fr3C_NhVihzg-YFJoESUxw 2019-05-26T00:00:00+02:00 Douglas DeMaio No osc19, 2378, openSUSE The openSUSE Board 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 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 00:46:14 https://media.ccc.de/v/2405-the-art-of-advocacy-with-linux Through this Lighting Talk I'd like to share some thoughts on the importance of Advocacy for the use of Linux distributions by various actors, starting with students or home users, to continue with Universities, Public Institutions and Governments. Educating the new generation to use Linux is something that should be seen of high importance. As there is a lot of progress done today with different Linux distros being massively used, a lot of improvements made in terms of the interface, security etc more efforts can be put in Advocacy. If today, as experienced users of Free Software, we understand our potential in getting more people to use Linux and we invest a little bit of our time in advocating it, we will definitely bring new users, some of which will definitely become new contributors. Awareness of Linux, and FOSS is spread largely by word of mouth, using grass roots movements and social media. You can teach others how to use it, run a workshop in a school, teach a student how to install Linux, show different environments and tools. Another step, which requires more efforts and planning, can be to bring Linux in the Government as well. This is something we cannot do alone, but you can try to support organizations and communities who do a lot of work in this direction. We keep hearing on migrations to various FLOSS projects by different governments, yours can be the next one, and you can be part of that great change. Through this Lighting Talk I'd like to share some thoughts on the importance of Advocacy for the use of Linux distributions by various actors, starting with students or home users, to continue with Universities, Public Institutions and Governments. Educating the new generation to use Linux is something that should be seen of high importance. As there is a lot of progress done today with different Linux distros being massively used, a lot of improvements made in terms of the interface, security etc more efforts can be put in Advocacy. If today, as experienced users of Free Software, we understand our potential in getting more people to use Linux and we invest a little bit of our time in advocating it, we will definitely bring new users, some of which will definitely become new contributors. Awareness of Linux, and FOSS is spread largely by word of mouth, using grass roots movements and social media. You can teach others how to use it, run a workshop in a school, teach a student how to install Linux, show different environments and tools. Another step, which requires more efforts and planning, can be to bring Linux in the Government as well. This is something we cannot do alone, but you can try to support organizations and communities who do a lot of work in this direction. We keep hearing on migrations to various FLOSS projects by different governments, yours can be the next one, and you can be part of that great change. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2405-eng-The_Art_of_Advocacy_with_Linux_opus.opus?1558871074 tcqG0x1tb0cojdtR4-QsFw 2019-05-26T00:00:00+02:00 Redon Skikuli No osc19, 2405, Open Source Advocacy tricks Through this Lighting Talk I'd like to share some thoughts on the importance of Advocacy for the use of Linux distributions by various actors, starting with students or home users, to continue with Universities, Public Institutions and Governments. Educating the new generation to use Linux is something that should be seen of high importance. As there is a lot of progress done today with different Linux distros being massively used, a lot of improvements made in terms of the interface, security etc more efforts can be put in Advocacy. If today, as experienced users of Free Software, we understand our potential in getting more people to use Linux and we invest a little bit of our time in advocating it, we will definitely bring new users, some of which will definitely become new contributors. Awareness of Linux, and FOSS is spread largely by word of mouth, using grass roots movements and social media. You can teach others how to use it, run a workshop in a school, teach a student how to install Linux, show different environments and tools. Another step, which requires more efforts and planning, can be to bring Linux in the Government as well. This is something we cannot do alone, but you can try to support organizations and communities who do a lot of work in this direction. We keep hearing on migrations to various FLOSS projects by different governments, yours can be the next one, and you can be part of that great change. Through this Lighting Talk I'd like to share some thoughts on the importance of Advocacy for the use of Linux distributions by various actors, starting with students or home users, to continue with Universities, Public Institutions and Governments. Educating the new generation to use Linux is something that should be seen of high importance. As there is a lot of progress done today with different Linux distros being massively used, a lot of improvements made in terms of the interface, security etc more efforts can be put in Advocacy. If today, as experienced users of Free Software, we understand our potential in getting more people to use Linux and we invest a little bit of our time in advocating it, we will definitely bring new users, some of which will definitely become new contributors. Awareness of Linux, and FOSS is spread largely by word of mouth, using grass roots movements and social media. You can teach others how to use it, run a workshop in a school, teach a student how to install Linux, show different environments and tools. Another step, which requires more efforts and planning, can be to bring Linux in the Government as well. This is something we cannot do alone, but you can try to support organizations and communities who do a lot of work in this direction. We keep hearing on migrations to various FLOSS projects by different governments, yours can be the next one, and you can be part of that great change. about this event: https://c3voc.de 00:22:48 https://media.ccc.de/v/2219-what-can-you-do-with-a-self-hosted-alternative-to-office365-google-apps-and-others Nextcloud is by far the easiest way to get a complete, 100% open source, fully self-hosted solution that can replace Office 365 or Google Apps. From file sync and collaborative document editing to chat & video calls, mail, calendar and password management, you can do almost anything with the apps on our expansive app store. In this lightning talk I'll quickly present #nextcloud and what it can do for you! One example: create a document, share it with your team, discuss it in the comments, add it to a video chat session & edit it together during a call. And did you know you can create a poll with Nextcloud? That there's a Kanban app? GPX tracker? Sensor logger? Radio player? Join the talk to hear more! Nextcloud is by far the easiest way to get a complete, 100% open source, fully self-hosted solution that can replace Office 365 or Google Apps. From file sync and collaborative document editing to chat & video calls, mail, calendar and password management, you can do almost anything with the apps on our expansive app store. In this lightning talk I'll quickly present #nextcloud and what it can do for you! One example: create a document, share it with your team, discuss it in the comments, add it to a video chat session & edit it together during a call. And did you know you can create a poll with Nextcloud? That there's a Kanban app? GPX tracker? Sensor logger? Radio player? Join the talk to hear more! about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2219-eng-What_can_you_do_with_a_self-hosted_alternative_to_Office365_Google_Apps_and_others_opus.opus?1558870980 xEWoNyjCI4ExTDHTer-QWw 2019-05-26T00:00:00+02:00 Frank Karlitschek No osc19, 2219, Desktop and Applications A small selection of the nearly 200 apps for Nextcloud Nextcloud is by far the easiest way to get a complete, 100% open source, fully self-hosted solution that can replace Office 365 or Google Apps. From file sync and collaborative document editing to chat & video calls, mail, calendar and password management, you can do almost anything with the apps on our expansive app store. In this lightning talk I'll quickly present #nextcloud and what it can do for you! One example: create a document, share it with your team, discuss it in the comments, add it to a video chat session & edit it together during a call. And did you know you can create a poll with Nextcloud? That there's a Kanban app? GPX tracker? Sensor logger? Radio player? Join the talk to hear more! Nextcloud is by far the easiest way to get a complete, 100% open source, fully self-hosted solution that can replace Office 365 or Google Apps. From file sync and collaborative document editing to chat & video calls, mail, calendar and password management, you can do almost anything with the apps on our expansive app store. In this lightning talk I'll quickly present #nextcloud and what it can do for you! One example: create a document, share it with your team, discuss it in the comments, add it to a video chat session & edit it together during a call. And did you know you can create a poll with Nextcloud? That there's a Kanban app? GPX tracker? Sensor logger? Radio player? Join the talk to hear more! about this event: https://c3voc.de 00:16:36 https://media.ccc.de/v/2237-state-of-ceph What's new in Nautilus and what's coming next? This talk focuses on the new features and implementations of Ceph Nautilus and also includes an outlook about what's planned and coming next. If you want to learn what's new in Nautilus and also learn about new features within Ceph, this is the right talk for you. What's new in Nautilus and what's coming next? This talk focuses on the new features and implementations of Ceph Nautilus and also includes an outlook about what's planned and coming next. If you want to learn what's new in Nautilus and also learn about new features within Ceph, this is the right talk for you. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2237-eng-State_of_Ceph_opus.opus?1558870686 xeLK3Ot8S1TKYGID6y2eIQ 2019-05-26T00:00:00+02:00 Kai Wagner No osc19, 2237, Open Source What's new in Nautilus and what's coming next? What's new in Nautilus and what's coming next? This talk focuses on the new features and implementations of Ceph Nautilus and also includes an outlook about what's planned and coming next. If you want to learn what's new in Nautilus and also learn about new features within Ceph, this is the right talk for you. What's new in Nautilus and what's coming next? This talk focuses on the new features and implementations of Ceph Nautilus and also includes an outlook about what's planned and coming next. If you want to learn what's new in Nautilus and also learn about new features within Ceph, this is the right talk for you. about this event: https://c3voc.de 00:41:36 https://media.ccc.de/v/2336-opensuse-artwork-branding-ui-and-ux openSUSE's brand image and software have been evolving for a long time, and in that time a lot of stuff was defined. There is YaST, there is geeko, both are industry standard, both function as a way to differentiate the distribution. However not everything that is openSUSE is great, in many cases, there are some serious omissions in terms of how openSUSE is sold through the eyes of potential users. This talk would function as a way to highlight some of the issues that will require further development in upcoming years, to support future devices, use cases for the distribution, ease of use, as well what we should improve in terms of presentation of the brand itself. openSUSE's brand image and software have been evolving for a long time, and in that time a lot of stuff was defined. There is YaST, there is geeko, both are industry standard, both function as a way to differentiate the distribution. However not everything that is openSUSE is great, in many cases, there are some serious omissions in terms of how openSUSE is sold through the eyes of potential users. This talk would function as a way to highlight some of the issues that will require further development in upcoming years, to support future devices, use cases for the distribution, ease of use, as well what we should improve in terms of presentation of the brand itself. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2336-eng-openSUSE_Artwork_Branding_UI_and_UX_opus.opus?1558870431 OB5O-mYv6r9yEGLa77x8nw 2019-05-26T00:00:00+02:00 Stasiek Michalski No osc19, 2336, openSUSE What's wrong and what could be better openSUSE's brand image and software have been evolving for a long time, and in that time a lot of stuff was defined. There is YaST, there is geeko, both are industry standard, both function as a way to differentiate the distribution. However not everything that is openSUSE is great, in many cases, there are some serious omissions in terms of how openSUSE is sold through the eyes of potential users. This talk would function as a way to highlight some of the issues that will require further development in upcoming years, to support future devices, use cases for the distribution, ease of use, as well what we should improve in terms of presentation of the brand itself. openSUSE's brand image and software have been evolving for a long time, and in that time a lot of stuff was defined. There is YaST, there is geeko, both are industry standard, both function as a way to differentiate the distribution. However not everything that is openSUSE is great, in many cases, there are some serious omissions in terms of how openSUSE is sold through the eyes of potential users. This talk would function as a way to highlight some of the issues that will require further development in upcoming years, to support future devices, use cases for the distribution, ease of use, as well what we should improve in terms of presentation of the brand itself. about this event: https://c3voc.de 00:35:41 https://media.ccc.de/v/2486-opensuse-leap-15-x-kernels-status-quo The saga continues: after the legendary Leap 42.3 trilogy, we entered a new era of Leap 15.x. This talk will look over the past Leap 15.0 kernel and the ongoing Leap 15.1 kernel development, which new feature are armed, how they are managed and how they are processed. The saga continues: after the legendary Leap 42.3 trilogy, we entered a new era of Leap 15.x. This talk will look over the past Leap 15.0 kernel and the ongoing Leap 15.1 kernel development, which new feature are armed, how they are managed and how they are processed. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2486-eng-openSUSE_Leap_15x_Kernels_Status_Quo_opus.opus?1558864923 N7AvGCS9c4IOGEHCNEGeqA 2019-05-25T00:00:00+02:00 Takashi Iwai No osc19, 2486 The saga continues: after the legendary Leap 42.3 trilogy, we entered a new era of Leap 15.x. This talk will look over the past Leap 15.0 kernel and the ongoing Leap 15.1 kernel development, which new feature are armed, how they are managed and how they are processed. The saga continues: after the legendary Leap 42.3 trilogy, we entered a new era of Leap 15.x. This talk will look over the past Leap 15.0 kernel and the ongoing Leap 15.1 kernel development, which new feature are armed, how they are managed and how they are processed. about this event: https://c3voc.de 00:28:13 https://media.ccc.de/v/2489-rust-packaging-cross-distro-collaboration-done-right When you are looking on the distribution and how they package things, they do it in so much different way. Even between RPM-based distributions, there are different macro, different package names and so on. People inside distributions tend to just write something what suit their needs and start using it. With Rust we've taken different approach: we've designed prototype in Fedora and then before officially using it, showed to other people (openSUSE, Mageia, Debian), asked for feedback, worked with them to suit their needs and only after that went and started using it in Fedora. It didn't work out fully with Debian because the ecosystem is too different, but even there we've made agreement on the filesystem paths and basic principles. When you are looking on the distribution and how they package things, they do it in so much different way. Even between RPM-based distributions, there are different macro, different package names and so on. People inside distributions tend to just write something what suit their needs and start using it. With Rust we've taken different approach: we've designed prototype in Fedora and then before officially using it, showed to other people (openSUSE, Mageia, Debian), asked for feedback, worked with them to suit their needs and only after that went and started using it in Fedora. It didn't work out fully with Debian because the ecosystem is too different, but even there we've made agreement on the filesystem paths and basic principles. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2489-eng-Rust_packaging_Cross-distro_collaboration_done_right_opus.opus?1558864795 XiMGzrAdPuzVluYhoPCNzA 2019-05-26T00:00:00+02:00 Igor Gnatenko No osc19, 2489, openSUSE Yes, distros can work together! When you are looking on the distribution and how they package things, they do it in so much different way. Even between RPM-based distributions, there are different macro, different package names and so on. People inside distributions tend to just write something what suit their needs and start using it. With Rust we've taken different approach: we've designed prototype in Fedora and then before officially using it, showed to other people (openSUSE, Mageia, Debian), asked for feedback, worked with them to suit their needs and only after that went and started using it in Fedora. It didn't work out fully with Debian because the ecosystem is too different, but even there we've made agreement on the filesystem paths and basic principles. When you are looking on the distribution and how they package things, they do it in so much different way. Even between RPM-based distributions, there are different macro, different package names and so on. People inside distributions tend to just write something what suit their needs and start using it. With Rust we've taken different approach: we've designed prototype in Fedora and then before officially using it, showed to other people (openSUSE, Mageia, Debian), asked for feedback, worked with them to suit their needs and only after that went and started using it in Fedora. It didn't work out fully with Debian because the ecosystem is too different, but even there we've made agreement on the filesystem paths and basic principles. about this event: https://c3voc.de 00:21:54 https://media.ccc.de/v/2372-atomic-updates-and-etc The great thing on atomic updates as used e.g. with transactional-update is, that your system is always in a defined state. But what happens with changes in /etc? With normal updates, changes are done immediately to /etc during the updates. With atomic updates, they are only visible with the next reboot. Which means, changes between update and reboot to /etc can create a conflict. There are several strategies by other distributions, like three-way-diff and patching, symlinks, ignoring the problem, etc. In this talk I will mention the biggest challenges we see, which solutions do exist, what are the advantages and what the disadvantages and which impact this will have on normal distributions like openSUSE Tumbleweed. This talk is to create awareness for the problem and as base for discussions, it will not provide a solution for every problem. It's targeting application developers and distribution developers, as this are the areas were changes would be necessary. The great thing on atomic updates as used e.g. with transactional-update is, that your system is always in a defined state. But what happens with changes in /etc? With normal updates, changes are done immediately to /etc during the updates. With atomic updates, they are only visible with the next reboot. Which means, changes between update and reboot to /etc can create a conflict. There are several strategies by other distributions, like three-way-diff and patching, symlinks, ignoring the problem, etc. In this talk I will mention the biggest challenges we see, which solutions do exist, what are the advantages and what the disadvantages and which impact this will have on normal distributions like openSUSE Tumbleweed. This talk is to create awareness for the problem and as base for discussions, it will not provide a solution for every problem. It's targeting application developers and distribution developers, as this are the areas were changes would be necessary. about this event: https://c3voc.de Sun, 26 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2372-eng-Atomic_Updates_-_and_etc_opus.opus?1558864864 a7hHbtzQv9BpGrrF0B_HGQ 2019-05-26T00:00:00+02:00 Thorsten Kukuk No osc19, 2372, openSUSE How to handle updates of config files in /etc The great thing on atomic updates as used e.g. with transactional-update is, that your system is always in a defined state. But what happens with changes in /etc? With normal updates, changes are done immediately to /etc during the updates. With atomic updates, they are only visible with the next reboot. Which means, changes between update and reboot to /etc can create a conflict. There are several strategies by other distributions, like three-way-diff and patching, symlinks, ignoring the problem, etc. In this talk I will mention the biggest challenges we see, which solutions do exist, what are the advantages and what the disadvantages and which impact this will have on normal distributions like openSUSE Tumbleweed. This talk is to create awareness for the problem and as base for discussions, it will not provide a solution for every problem. It's targeting application developers and distribution developers, as this are the areas were changes would be necessary. The great thing on atomic updates as used e.g. with transactional-update is, that your system is always in a defined state. But what happens with changes in /etc? With normal updates, changes are done immediately to /etc during the updates. With atomic updates, they are only visible with the next reboot. Which means, changes between update and reboot to /etc can create a conflict. There are several strategies by other distributions, like three-way-diff and patching, symlinks, ignoring the problem, etc. In this talk I will mention the biggest challenges we see, which solutions do exist, what are the advantages and what the disadvantages and which impact this will have on normal distributions like openSUSE Tumbleweed. This talk is to create awareness for the problem and as base for discussions, it will not provide a solution for every problem. It's targeting application developers and distribution developers, as this are the areas were changes would be necessary. about this event: https://c3voc.de 00:29:58 https://media.ccc.de/v/2519-open-build-service-obs-development-has-increased-exponentially OBS Team will briefly explain the evolution of the OBS in the last year, and also some of the impressive features that have been included recently. We will introduce the advances of OBS, not only the Frontend but also those related with the Backend and OSC (command line tool). 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. OBS Team will briefly explain the evolution of the OBS in the last year, and also some of the impressive features that have been included recently. We will introduce the advances of OBS, not only the Frontend but also those related with the Backend and OSC (command line tool). 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 Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2519-eng-Open_Build_Service_OBS_development_has_increased_exponentially_opus.opus?1558807714 B7oXBmGX9R-A-86GuvS6YQ 2019-05-25T00:00:00+02:00 David Kang No osc19, 2519 OBS Team will briefly explain the evolution of the OBS in the last year, and also some of the impressive features that have been included recently. We will introduce the advances of OBS, not only the Frontend but also those related with the Backend and OSC (command line tool). 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. OBS Team will briefly explain the evolution of the OBS in the last year, and also some of the impressive features that have been included recently. We will introduce the advances of OBS, not only the Frontend but also those related with the Backend and OSC (command line tool). 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 00:26:05 https://media.ccc.de/v/2507-suse-security-retrospective-for-last-year Another year - another security retrospective. The talk will introduce the SUSE security team and its members, our areas of work and responsibilities. The talk will show some statistics and interesting details of last year security issues, and go in detail on some of the specific codenamed ones. A special focus will be on updated classification and overview of last years Meltdown and Spectre like CPU issues, describing them and the mitigations that SUSE has been deployed. As the SUSE security team has grown in the last year, we also increased our work in both proactive security and related areas, which the talk will briefly highlight Another year - another security retrospective. The talk will introduce the SUSE security team and its members, our areas of work and responsibilities. The talk will show some statistics and interesting details of last year security issues, and go in detail on some of the specific codenamed ones. A special focus will be on updated classification and overview of last years Meltdown and Spectre like CPU issues, describing them and the mitigations that SUSE has been deployed. As the SUSE security team has grown in the last year, we also increased our work in both proactive security and related areas, which the talk will briefly highlight about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2507-eng-SUSE_Security_retrospective_for_last_year_opus.opus?1558807683 jot9JzhThXaI-bg4lHKeIQ 2019-05-25T00:00:00+02:00 Marcus Meissner No osc19, 2507, openSUSE Situation normal - all fine Another year - another security retrospective. The talk will introduce the SUSE security team and its members, our areas of work and responsibilities. The talk will show some statistics and interesting details of last year security issues, and go in detail on some of the specific codenamed ones. A special focus will be on updated classification and overview of last years Meltdown and Spectre like CPU issues, describing them and the mitigations that SUSE has been deployed. As the SUSE security team has grown in the last year, we also increased our work in both proactive security and related areas, which the talk will briefly highlight Another year - another security retrospective. The talk will introduce the SUSE security team and its members, our areas of work and responsibilities. The talk will show some statistics and interesting details of last year security issues, and go in detail on some of the specific codenamed ones. A special focus will be on updated classification and overview of last years Meltdown and Spectre like CPU issues, describing them and the mitigations that SUSE has been deployed. As the SUSE security team has grown in the last year, we also increased our work in both proactive security and related areas, which the talk will briefly highlight about this event: https://c3voc.de 00:41:56 https://media.ccc.de/v/2396-opensuse-testing-an-overview How is software within the openSUSE ecosystem tested? What kind of tests exist? Who is doing what? This talk will try to present an overview of how "testing" is done for software developed in the openSUSE ecosystem. The workflow of software contributions to the openSUSE distributions will be shown from testing perspective from upstream source code repos to feedback from users in the released products. Used tools will be mentioned, the testing approaches as well as the people involved. The relation to SLE testing will be described. As this "overview" will not be able to cover all approaches used by the community feedback by the audience in the Q&A part of the talk will be appreciated. Of course, openQA will be included but it is certainly not the only solution to be mentioned ;) How is software within the openSUSE ecosystem tested? What kind of tests exist? Who is doing what? This talk will try to present an overview of how "testing" is done for software developed in the openSUSE ecosystem. The workflow of software contributions to the openSUSE distributions will be shown from testing perspective from upstream source code repos to feedback from users in the released products. Used tools will be mentioned, the testing approaches as well as the people involved. The relation to SLE testing will be described. As this "overview" will not be able to cover all approaches used by the community feedback by the audience in the Q&A part of the talk will be appreciated. Of course, openQA will be included but it is certainly not the only solution to be mentioned ;) about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2396-eng-openSUSE_testing_-_an_overview_opus.opus?1558807323 V5TLukgwdAbRwzDYdJDPMg 2019-05-25T00:00:00+02:00 Oliver Kurz No osc19, 2396, openSUSE How is software within the openSUSE ecosystem tested? What kind of tests exist? Who is doing what? This talk will try to present an overview of how "testing" is done for software developed in the openSUSE ecosystem. The workflow of software contributions to the openSUSE distributions will be shown from testing perspective from upstream source code repos to feedback from users in the released products. Used tools will be mentioned, the testing approaches as well as the people involved. The relation to SLE testing will be described. As this "overview" will not be able to cover all approaches used by the community feedback by the audience in the Q&A part of the talk will be appreciated. Of course, openQA will be included but it is certainly not the only solution to be mentioned ;) How is software within the openSUSE ecosystem tested? What kind of tests exist? Who is doing what? This talk will try to present an overview of how "testing" is done for software developed in the openSUSE ecosystem. The workflow of software contributions to the openSUSE distributions will be shown from testing perspective from upstream source code repos to feedback from users in the released products. Used tools will be mentioned, the testing approaches as well as the people involved. The relation to SLE testing will be described. As this "overview" will not be able to cover all approaches used by the community feedback by the audience in the Q&A part of the talk will be appreciated. Of course, openQA will be included but it is certainly not the only solution to be mentioned ;) about this event: https://c3voc.de 00:31:50 https://media.ccc.de/v/2357-installing-opensuse-only-with-saltstack When we want to install openSUSE in out laptop we will use YaST. It will take care of all the details required for a correct partitioning, bootloader installation, time zone selection, network configuration, software selection, etc, etc. But when we want to install 100 nodes in our cloud, each one with a different hardware profile and a different role in our infrastructure, we need something different. AutoYaST can help with this, but there are some limitations, as we need to provide XMLs adjusted for those hardware profiles and roles, and we need a different tool to orchestrate those multiple installations. Can be done, but we can do better. SaltStack is a tool used to manage configuration and provisioning of machines, and we propose use this tool to drive the installation of openSUSE for big deployments. I want to show a WIP installer based on Salt, that can be naturally integrated in any other Salt-based solution, and I would like to talk about the ways that we can improve it in the future. When we want to install openSUSE in out laptop we will use YaST. It will take care of all the details required for a correct partitioning, bootloader installation, time zone selection, network configuration, software selection, etc, etc. But when we want to install 100 nodes in our cloud, each one with a different hardware profile and a different role in our infrastructure, we need something different. AutoYaST can help with this, but there are some limitations, as we need to provide XMLs adjusted for those hardware profiles and roles, and we need a different tool to orchestrate those multiple installations. Can be done, but we can do better. SaltStack is a tool used to manage configuration and provisioning of machines, and we propose use this tool to drive the installation of openSUSE for big deployments. I want to show a WIP installer based on Salt, that can be naturally integrated in any other Salt-based solution, and I would like to talk about the ways that we can improve it in the future. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2357-eng-Installing_openSUSE_only_with_SaltStack_opus.opus?1558806934 G-fbiDSrJ6ifAOEPW1PmZA 2019-05-25T00:00:00+02:00 Alberto Planas No osc19, 2357, openSUSE Using Salt as an alternative to AutoYaST When we want to install openSUSE in out laptop we will use YaST. It will take care of all the details required for a correct partitioning, bootloader installation, time zone selection, network configuration, software selection, etc, etc. But when we want to install 100 nodes in our cloud, each one with a different hardware profile and a different role in our infrastructure, we need something different. AutoYaST can help with this, but there are some limitations, as we need to provide XMLs adjusted for those hardware profiles and roles, and we need a different tool to orchestrate those multiple installations. Can be done, but we can do better. SaltStack is a tool used to manage configuration and provisioning of machines, and we propose use this tool to drive the installation of openSUSE for big deployments. I want to show a WIP installer based on Salt, that can be naturally integrated in any other Salt-based solution, and I would like to talk about the ways that we can improve it in the future. When we want to install openSUSE in out laptop we will use YaST. It will take care of all the details required for a correct partitioning, bootloader installation, time zone selection, network configuration, software selection, etc, etc. But when we want to install 100 nodes in our cloud, each one with a different hardware profile and a different role in our infrastructure, we need something different. AutoYaST can help with this, but there are some limitations, as we need to provide XMLs adjusted for those hardware profiles and roles, and we need a different tool to orchestrate those multiple installations. Can be done, but we can do better. SaltStack is a tool used to manage configuration and provisioning of machines, and we propose use this tool to drive the installation of openSUSE for big deployments. I want to show a WIP installer based on Salt, that can be naturally integrated in any other Salt-based solution, and I would like to talk about the ways that we can improve it in the future. about this event: https://c3voc.de 00:58:12 https://media.ccc.de/v/2432-introducing-pagure Pagure is a new, full-featured Git repository service for the web, written in Python. It is similar to other popular Git-based forges, allowing developers and contributors to share and collaborate on code and content. It also has some unique features not found in any other Git forge providing the basis for decentralized, federated software code hosting and development. It's fully free and open source software, and it's included in openSUSE Leap 15.1 and openSUSE Tumbleweed! The agenda of the presentation: - What is Pagure - History of Pagure - Current state and features of Pagure - Current ecosystem around Pagure - Plans for the future of Pagure - Demo of Pagure on openSUSE Pagure is a new, full-featured Git repository service for the web, written in Python. It is similar to other popular Git-based forges, allowing developers and contributors to share and collaborate on code and content. It also has some unique features not found in any other Git forge providing the basis for decentralized, federated software code hosting and development. It's fully free and open source software, and it's included in openSUSE Leap 15.1 and openSUSE Tumbleweed! The agenda of the presentation: - What is Pagure - History of Pagure - Current state and features of Pagure - Current ecosystem around Pagure - Plans for the future of Pagure - Demo of Pagure on openSUSE about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2432-eng-Introducing_Pagure_opus.opus?1558801324 UXkaWhL6nt_30m-UEalVMQ 2019-05-25T00:00:00+02:00 pingou No osc19, 2432, Open Source A new lightweight and powerful Git-centered forge, now in openSUSE! Pagure is a new, full-featured Git repository service for the web, written in Python. It is similar to other popular Git-based forges, allowing developers and contributors to share and collaborate on code and content. It also has some unique features not found in any other Git forge providing the basis for decentralized, federated software code hosting and development. It's fully free and open source software, and it's included in openSUSE Leap 15.1 and openSUSE Tumbleweed! The agenda of the presentation: - What is Pagure - History of Pagure - Current state and features of Pagure - Current ecosystem around Pagure - Plans for the future of Pagure - Demo of Pagure on openSUSE Pagure is a new, full-featured Git repository service for the web, written in Python. It is similar to other popular Git-based forges, allowing developers and contributors to share and collaborate on code and content. It also has some unique features not found in any other Git forge providing the basis for decentralized, federated software code hosting and development. It's fully free and open source software, and it's included in openSUSE Leap 15.1 and openSUSE Tumbleweed! The agenda of the presentation: - What is Pagure - History of Pagure - Current state and features of Pagure - Current ecosystem around Pagure - Plans for the future of Pagure - Demo of Pagure on openSUSE about this event: https://c3voc.de 00:38:51 https://media.ccc.de/v/2450-open-source-firmware Firmware is found in all computing devices, including PCs, laptops, networking equipment, printers, embedded devices such as IoT and industrial controllers, mobile phones, tablets, and more. The community around open source firmware has grown over the last years, allowing for more exchange in the development and granting freedom to end users. Prominent projects like U-Boot, Tianocore, coreboot and others teach how firmware works and welcome contributions. This talk provides a brief introduction into firmware, an overview of the general build process, a perception of the current state of development on two platforms, an end user report, and a summary of the first Open Source Firmware Conference, which was supported by the openSUSE project. Firmware is found in all computing devices, including PCs, laptops, networking equipment, printers, embedded devices such as IoT and industrial controllers, mobile phones, tablets, and more. The community around open source firmware has grown over the last years, allowing for more exchange in the development and granting freedom to end users. Prominent projects like U-Boot, Tianocore, coreboot and others teach how firmware works and welcome contributions. This talk provides a brief introduction into firmware, an overview of the general build process, a perception of the current state of development on two platforms, an end user report, and a summary of the first Open Source Firmware Conference, which was supported by the openSUSE project. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2450-eng-Open_Source_Firmware_opus.opus?1558800843 -TfWXwLFMvJx2yy1UQ6iTg 2019-05-25T00:00:00+02:00 Daniel Maslowski No osc19, 2450, Open Source ... and I finally had my personal bootsplash screen :) Firmware is found in all computing devices, including PCs, laptops, networking equipment, printers, embedded devices such as IoT and industrial controllers, mobile phones, tablets, and more. The community around open source firmware has grown over the last years, allowing for more exchange in the development and granting freedom to end users. Prominent projects like U-Boot, Tianocore, coreboot and others teach how firmware works and welcome contributions. This talk provides a brief introduction into firmware, an overview of the general build process, a perception of the current state of development on two platforms, an end user report, and a summary of the first Open Source Firmware Conference, which was supported by the openSUSE project. Firmware is found in all computing devices, including PCs, laptops, networking equipment, printers, embedded devices such as IoT and industrial controllers, mobile phones, tablets, and more. The community around open source firmware has grown over the last years, allowing for more exchange in the development and granting freedom to end users. Prominent projects like U-Boot, Tianocore, coreboot and others teach how firmware works and welcome contributions. This talk provides a brief introduction into firmware, an overview of the general build process, a perception of the current state of development on two platforms, an end user report, and a summary of the first Open Source Firmware Conference, which was supported by the openSUSE project. about this event: https://c3voc.de 00:45:07 https://media.ccc.de/v/2390-iot-programming-with-opensuse Small networked devices, commonly named Internet of Things (IoT), lead the next revolution in information technology. This talk will present the software and tools available on openSUSE to participate in this revolution. We will especially look at the 'Arduino' IDE to program Arduino, ESP8266, Wemos, ESP32, and similar devices. Small networked devices, commonly named Internet of Things (IoT), lead the next revolution in information technology. This talk will present the software and tools available on openSUSE to participate in this revolution. We will especially look at the 'Arduino' IDE to program Arduino, ESP8266, Wemos, ESP32, and similar devices. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2390-eng-IoT_programming_with_openSUSE_opus.opus?1558792234 caBUDXeLXE4J3RhUXoULhQ 2019-05-25T00:00:00+02:00 Klaus Kämpf No osc19, 2390 . Small networked devices, commonly named Internet of Things (IoT), lead the next revolution in information technology. This talk will present the software and tools available on openSUSE to participate in this revolution. We will especially look at the 'Arduino' IDE to program Arduino, ESP8266, Wemos, ESP32, and similar devices. Small networked devices, commonly named Internet of Things (IoT), lead the next revolution in information technology. This talk will present the software and tools available on openSUSE to participate in this revolution. We will especially look at the 'Arduino' IDE to program Arduino, ESP8266, Wemos, ESP32, and similar devices. about this event: https://c3voc.de 00:39:37 https://media.ccc.de/v/2570-suse-developer-program LEARN WHAT SUSE IS DOING TO HELP THE DEVELOPERS COMMUNITY CREATING APPLICATIONS AND SOLUTIONS IN AN EASIER AND QUICKER WAY AND HOW YOU CAN CONTRIBUTE TO THAT EFFORT! LEARN WHAT SUSE IS DOING TO HELP THE DEVELOPERS COMMUNITY CREATING APPLICATIONS AND SOLUTIONS IN AN EASIER AND QUICKER WAY AND HOW YOU CAN CONTRIBUTE TO THAT EFFORT! about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2570-eng-SUSE_DEVELOPER_PROGRAM_opus.opus?1558789744 3cC2qVMvq6bZ76LgeVzM-A 2019-05-25T00:00:00+02:00 Marco Varlese, FSzekely, timirnich No osc19, 2570, Open Source LEARN WHAT SUSE IS DOING TO HELP THE DEVELOPERS COMMUNITY CREATING APPLICATIONS AND SOLUTIONS IN AN EASIER AND QUICKER WAY AND HOW YOU CAN CONTRIBUTE TO THAT EFFORT! LEARN WHAT SUSE IS DOING TO HELP THE DEVELOPERS COMMUNITY CREATING APPLICATIONS AND SOLUTIONS IN AN EASIER AND QUICKER WAY AND HOW YOU CAN CONTRIBUTE TO THAT EFFORT! about this event: https://c3voc.de 00:18:47 https://media.ccc.de/v/2345-lora-for-the-kernel At ELCE 2018 I presented a project to implement Linux kernel drivers for LoRa Low-Power Wide Area Network (LPWAN) wireless technology. The project is since evolving to cover more chipsets and other technologies. This is a brief overview of what is being worked on and how to participate. It will also explain how openSUSE Tumbleweed aarch64 has been used as base for most of the kernel development. At ELCE 2018 I presented a project to implement Linux kernel drivers for LoRa Low-Power Wide Area Network (LPWAN) wireless technology. The project is since evolving to cover more chipsets and other technologies. This is a brief overview of what is being worked on and how to participate. It will also explain how openSUSE Tumbleweed aarch64 has been used as base for most of the kernel development. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2345-eng-LoRa_for_the_kernel_opus.opus?1558789654 xO0S5vz0kq5ATcAd2Y-0aw 2019-05-25T00:00:00+02:00 Andreas Färber No osc19, 2345, Open Source Adding support for LPWA wireless technologies At ELCE 2018 I presented a project to implement Linux kernel drivers for LoRa Low-Power Wide Area Network (LPWAN) wireless technology. The project is since evolving to cover more chipsets and other technologies. This is a brief overview of what is being worked on and how to participate. It will also explain how openSUSE Tumbleweed aarch64 has been used as base for most of the kernel development. At ELCE 2018 I presented a project to implement Linux kernel drivers for LoRa Low-Power Wide Area Network (LPWAN) wireless technology. The project is since evolving to cover more chipsets and other technologies. This is a brief overview of what is being worked on and how to participate. It will also explain how openSUSE Tumbleweed aarch64 has been used as base for most of the kernel development. about this event: https://c3voc.de 00:42:43 https://media.ccc.de/v/2537-state-of-transactional-update You may have heard about transactional updates already - that thing that will force you to reboot your system just like on Windows. Well, it still does, but it also provides a huge benefit compared to your regular updates: It won't break your currently running system. transactional-update is the default update mechanism on openSUSE Kubic and when using the "Transactional Server" role in openSUSE Leap or Tumbleweed. This talk is intended for both existing users and newcomers and will feature the following contents: - Give an overview of the design - Highlight the most important changes since last year, including the all-new _/etc_ handling - Give a general overview of the file system layout You may have heard about transactional updates already - that thing that will force you to reboot your system just like on Windows. Well, it still does, but it also provides a huge benefit compared to your regular updates: It won't break your currently running system. transactional-update is the default update mechanism on openSUSE Kubic and when using the "Transactional Server" role in openSUSE Leap or Tumbleweed. This talk is intended for both existing users and newcomers and will feature the following contents: - Give an overview of the design - Highlight the most important changes since last year, including the all-new _/etc_ handling - Give a general overview of the file system layout about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2537-eng-State_of_transactional-update_opus.opus?1558787932 8xulM32JRt4IMza2mCbdtQ 2019-05-25T00:00:00+02:00 Ignaz Forster No osc19, 2537, openSUSE News & file system layout anatomy You may have heard about transactional updates already - that thing that will force you to reboot your system just like on Windows. Well, it still does, but it also provides a huge benefit compared to your regular updates: It won't break your currently running system. transactional-update is the default update mechanism on openSUSE Kubic and when using the "Transactional Server" role in openSUSE Leap or Tumbleweed. This talk is intended for both existing users and newcomers and will feature the following contents: - Give an overview of the design - Highlight the most important changes since last year, including the all-new _/etc_ handling - Give a general overview of the file system layout You may have heard about transactional updates already - that thing that will force you to reboot your system just like on Windows. Well, it still does, but it also provides a huge benefit compared to your regular updates: It won't break your currently running system. transactional-update is the default update mechanism on openSUSE Kubic and when using the "Transactional Server" role in openSUSE Leap or Tumbleweed. This talk is intended for both existing users and newcomers and will feature the following contents: - Give an overview of the design - Highlight the most important changes since last year, including the all-new _/etc_ handling - Give a general overview of the file system layout about this event: https://c3voc.de 00:16:48 https://media.ccc.de/v/2351-opensuse-on-arm This talk will give an overview of what happens since about a year for openSUSE on ARM. What is the current status and what is on the TODO list. This talk will give an overview of what happens since about a year for openSUSE on ARM. What is the current status and what is on the TODO list. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2351-eng-openSUSE_on_ARM_opus.opus?1558787373 W1PdrH0zlNpL1dKwmW1KLg 2019-05-25T00:00:00+02:00 Guillaume Gardet No osc19, 2351, openSUSE What happened since a year This talk will give an overview of what happens since about a year for openSUSE on ARM. What is the current status and what is on the TODO list. This talk will give an overview of what happens since about a year for openSUSE on ARM. What is the current status and what is on the TODO list. about this event: https://c3voc.de 00:26:43 https://media.ccc.de/v/2498-why-you-should-choose-opensuse-kubic In the past few years, the development of container application technology has advanced by leaps and bounds. But for people who want to enter a containers word still hard for them. Most of people stop at the first step that use Kubernetes to setup environment. As a opsnSUSE user I’m glad we have openSUSE Kubic. I would like to share people who frustrated to build container. All they should do are use openSUSE Kubic. They need new tools that make them easy to set up cluster and maintain. OpenSUSE Kubic is great platform to run containers and to learn how to containerize. Hope through my experience of use Kubic can share it for people who want to join open source and containers word. There always have a best way to help you management your IT infrastructure and work smart. In the past few years, the development of container application technology has advanced by leaps and bounds. But for people who want to enter a containers word still hard for them. Most of people stop at the first step that use Kubernetes to setup environment. As a opsnSUSE user I’m glad we have openSUSE Kubic. I would like to share people who frustrated to build container. All they should do are use openSUSE Kubic. They need new tools that make them easy to set up cluster and maintain. OpenSUSE Kubic is great platform to run containers and to learn how to containerize. Hope through my experience of use Kubic can share it for people who want to join open source and containers word. There always have a best way to help you management your IT infrastructure and work smart. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2498-eng-Why_you_should_choose_openSUSE_Kubic_opus.opus?1558786923 mWKUN7nGXvyiGK9jC3zBVw 2019-05-25T00:00:00+02:00 kimlin No osc19, 2498, Cloud and Containers openSUSE Kubic is really fun! In the past few years, the development of container application technology has advanced by leaps and bounds. But for people who want to enter a containers word still hard for them. Most of people stop at the first step that use Kubernetes to setup environment. As a opsnSUSE user I’m glad we have openSUSE Kubic. I would like to share people who frustrated to build container. All they should do are use openSUSE Kubic. They need new tools that make them easy to set up cluster and maintain. OpenSUSE Kubic is great platform to run containers and to learn how to containerize. Hope through my experience of use Kubic can share it for people who want to join open source and containers word. There always have a best way to help you management your IT infrastructure and work smart. In the past few years, the development of container application technology has advanced by leaps and bounds. But for people who want to enter a containers word still hard for them. Most of people stop at the first step that use Kubernetes to setup environment. As a opsnSUSE user I’m glad we have openSUSE Kubic. I would like to share people who frustrated to build container. All they should do are use openSUSE Kubic. They need new tools that make them easy to set up cluster and maintain. OpenSUSE Kubic is great platform to run containers and to learn how to containerize. Hope through my experience of use Kubic can share it for people who want to join open source and containers word. There always have a best way to help you management your IT infrastructure and work smart. about this event: https://c3voc.de 00:08:32 https://media.ccc.de/v/2555-cilium-bpf-the-future-of-linux-networking-and-security-keynote-thomas-graf-cilium Linux is the dominant platform to run microservices using cloud-native architectures. These modern architectures impose new challenges on the platform serving the applications. We'll take a peek at BPF and Cilium and how it revolutionizes both networking and security to enable platforms built on top of it to fully utilize the benefits of cloud-native architectures. Thomas Graf is Co-Founder & CTO at Isovalent and creator of the Cilium project. Before this, Thomas has been a Linux kernel developer at RedHat for many years. Linux is the dominant platform to run microservices using cloud-native architectures. These modern architectures impose new challenges on the platform serving the applications. We'll take a peek at BPF and Cilium and how it revolutionizes both networking and security to enable platforms built on top of it to fully utilize the benefits of cloud-native architectures. Thomas Graf is Co-Founder & CTO at Isovalent and creator of the Cilium project. Before this, Thomas has been a Linux kernel developer at RedHat for many years. about this event: https://c3voc.de Sat, 25 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2555-eng-Cilium_BPF_-_The_Future_of_Linux_Networking_and_Security_Keynote_Thomas_Graf_Cilium_opus.opus?1558786834 csrcGQ7hEYgCTrb3f58vSQ 2019-05-25T00:00:00+02:00 Thomas Graf No osc19, 2555, Keynote Linux is the dominant platform to run microservices using cloud-native architectures. These modern architectures impose new challenges on the platform serving the applications. We'll take a peek at BPF and Cilium and how it revolutionizes both networking and security to enable platforms built on top of it to fully utilize the benefits of cloud-native architectures. Thomas Graf is Co-Founder & CTO at Isovalent and creator of the Cilium project. Before this, Thomas has been a Linux kernel developer at RedHat for many years. Linux is the dominant platform to run microservices using cloud-native architectures. These modern architectures impose new challenges on the platform serving the applications. We'll take a peek at BPF and Cilium and how it revolutionizes both networking and security to enable platforms built on top of it to fully utilize the benefits of cloud-native architectures. Thomas Graf is Co-Founder & CTO at Isovalent and creator of the Cilium project. Before this, Thomas has been a Linux kernel developer at RedHat for many years. about this event: https://c3voc.de 00:29:08 https://media.ccc.de/v/2501-re-thinking-spec-files Right now many RPM spec files contain large parts of boiler plate code. In the current development cycle of RPM we try to help reducing this clutter. We hope we can make packaging easier by providing means to have pre-arranged building blocks and offer more control over larger sets of packages. This will also change the relation between RPM as a multipurpose tool and the single package/packager by adding a layer in between take will take care of common tasks. This talk will give a overview of the changes already done and still planned and will allow for discussion and feed back. Right now many RPM spec files contain large parts of boiler plate code. In the current development cycle of RPM we try to help reducing this clutter. We hope we can make packaging easier by providing means to have pre-arranged building blocks and offer more control over larger sets of packages. This will also change the relation between RPM as a multipurpose tool and the single package/packager by adding a layer in between take will take care of common tasks. This talk will give a overview of the changes already done and still planned and will allow for discussion and feed back. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2501-eng-Re-Thinking_Spec_Files_opus.opus?1558722634 IEyjOV2OETpd153wvMALIA 2019-05-24T00:00:00+02:00 Florian Festi No osc19, 2501, openSUSE New features for rpmbuild Right now many RPM spec files contain large parts of boiler plate code. In the current development cycle of RPM we try to help reducing this clutter. We hope we can make packaging easier by providing means to have pre-arranged building blocks and offer more control over larger sets of packages. This will also change the relation between RPM as a multipurpose tool and the single package/packager by adding a layer in between take will take care of common tasks. This talk will give a overview of the changes already done and still planned and will allow for discussion and feed back. Right now many RPM spec files contain large parts of boiler plate code. In the current development cycle of RPM we try to help reducing this clutter. We hope we can make packaging easier by providing means to have pre-arranged building blocks and offer more control over larger sets of packages. This will also change the relation between RPM as a multipurpose tool and the single package/packager by adding a layer in between take will take care of common tasks. This talk will give a overview of the changes already done and still planned and will allow for discussion and feed back. about this event: https://c3voc.de 00:45:57 https://media.ccc.de/v/2513-building-large-health-networks-gnu-health-federation-and-opensuse GNU Health is the Free/Libre Health and Hospital Information System that is included in openSUSE. GNU Health combines the socioeconomic determinants of health with state-of-the-art technology in bioinformatics and clinical genetics. It provides holistic picture of the person, from the biological and molecular basis of disease to the environmental determinants of health. In addition, it manages the internal processes of a health institution, such as financial management, billing, stock management, pharmacies or labs (LIMS) The GNU Health Federation introduced in 3.4 series allows to build nationwide federated networks with thousands of heterogeneous nodes. The GNU Health federation is revolutionary, and will allow the community, the health practitioners, the research institutions and the ministries of health to have much better perspective and precise information on the individuals and their context. Having the GNU Health Federation in openSUSE (available both for Tumbleweed and Leap) not only provides the development environment, but the server stability to deploy it in hospitals and large heterogeneous health networks across a country. GNU Health is the Free/Libre Health and Hospital Information System that is included in openSUSE. GNU Health combines the socioeconomic determinants of health with state-of-the-art technology in bioinformatics and clinical genetics. It provides holistic picture of the person, from the biological and molecular basis of disease to the environmental determinants of health. In addition, it manages the internal processes of a health institution, such as financial management, billing, stock management, pharmacies or labs (LIMS) The GNU Health Federation introduced in 3.4 series allows to build nationwide federated networks with thousands of heterogeneous nodes. The GNU Health federation is revolutionary, and will allow the community, the health practitioners, the research institutions and the ministries of health to have much better perspective and precise information on the individuals and their context. Having the GNU Health Federation in openSUSE (available both for Tumbleweed and Leap) not only provides the development environment, but the server stability to deploy it in hospitals and large heterogeneous health networks across a country. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2513-eng-Building_large_health_networks_GNU_Health_Federation_and_openSUSE_opus.opus?1558722476 cp8jUfTm9BjicPO2BYu7ZQ 2019-05-24T00:00:00+02:00 Luis Falcon No osc19, 2513, openSUSE 10 years of Freedom and Equity in Healthcare GNU Health is the Free/Libre Health and Hospital Information System that is included in openSUSE. GNU Health combines the socioeconomic determinants of health with state-of-the-art technology in bioinformatics and clinical genetics. It provides holistic picture of the person, from the biological and molecular basis of disease to the environmental determinants of health. In addition, it manages the internal processes of a health institution, such as financial management, billing, stock management, pharmacies or labs (LIMS) The GNU Health Federation introduced in 3.4 series allows to build nationwide federated networks with thousands of heterogeneous nodes. The GNU Health federation is revolutionary, and will allow the community, the health practitioners, the research institutions and the ministries of health to have much better perspective and precise information on the individuals and their context. Having the GNU Health Federation in openSUSE (available both for Tumbleweed and Leap) not only provides the development environment, but the server stability to deploy it in hospitals and large heterogeneous health networks across a country. GNU Health is the Free/Libre Health and Hospital Information System that is included in openSUSE. GNU Health combines the socioeconomic determinants of health with state-of-the-art technology in bioinformatics and clinical genetics. It provides holistic picture of the person, from the biological and molecular basis of disease to the environmental determinants of health. In addition, it manages the internal processes of a health institution, such as financial management, billing, stock management, pharmacies or labs (LIMS) The GNU Health Federation introduced in 3.4 series allows to build nationwide federated networks with thousands of heterogeneous nodes. The GNU Health federation is revolutionary, and will allow the community, the health practitioners, the research institutions and the ministries of health to have much better perspective and precise information on the individuals and their context. Having the GNU Health Federation in openSUSE (available both for Tumbleweed and Leap) not only provides the development environment, but the server stability to deploy it in hospitals and large heterogeneous health networks across a country. about this event: https://c3voc.de 00:42:55 https://media.ccc.de/v/2465-geeko-magazine-a-technical-magazine-on-opensuse-edited-on-opensuse Japan openSUSE User Group publishes a technical magazine every half year. The title of the magazine is Geeko Magazine. It consists of technical articles on openSUSE and applications running on openSUSE. For example, the latest issue of the magazine contains articles like "Launching Kubernetes Cluster with Kubic in 10 minutes", "Accessing to Google Drive from openSUSE", and "How to enable HTTPS with Let's Encrypt." Since 2014, we have published 9 issues of Geeko Magazine. In this talk, after explaining the culture of self-publishing in Japan, I will talk about the process from calling articles from the user group until distributing Geeko Magazine. Another topic is our challenge: editing the magazine on openSUSE. Thereby, we cannot use popular desktop publishing (DTP) applications like Adobe InDesign. Instead of such applications, we have been using Scribus, an OSS DTP application to edit Geeko Magazine. It supports CMYK color and DTP data such as trim marks and bleed areas, required by print shops. However, in 2014, Scribus was not adequate for writing a Japanese document. This is because typesetting rules are much different from English etc. To publish Geeko Magazine, we went OSS way; we have improved Scribus one by one at every issue of the magazine in cooperation with the upstream community. I will talk about a brief summary of those problems we have resolved. Japan openSUSE User Group publishes a technical magazine every half year. The title of the magazine is Geeko Magazine. It consists of technical articles on openSUSE and applications running on openSUSE. For example, the latest issue of the magazine contains articles like "Launching Kubernetes Cluster with Kubic in 10 minutes", "Accessing to Google Drive from openSUSE", and "How to enable HTTPS with Let's Encrypt." Since 2014, we have published 9 issues of Geeko Magazine. In this talk, after explaining the culture of self-publishing in Japan, I will talk about the process from calling articles from the user group until distributing Geeko Magazine. Another topic is our challenge: editing the magazine on openSUSE. Thereby, we cannot use popular desktop publishing (DTP) applications like Adobe InDesign. Instead of such applications, we have been using Scribus, an OSS DTP application to edit Geeko Magazine. It supports CMYK color and DTP data such as trim marks and bleed areas, required by print shops. However, in 2014, Scribus was not adequate for writing a Japanese document. This is because typesetting rules are much different from English etc. To publish Geeko Magazine, we went OSS way; we have improved Scribus one by one at every issue of the magazine in cooperation with the upstream community. I will talk about a brief summary of those problems we have resolved. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2465-eng-Geeko_Magazine_A_Technical_Magazine_on_openSUSE_edited_on_openSUSE_opus.opus?1558720985 VYFvdxaeH_SfczvkUMPjMw 2019-05-24T00:00:00+02:00 Fuminobu Takeyama No osc19, 2465, openSUSE Japan openSUSE User Group publishes a technical magazine every half year. The title of the magazine is Geeko Magazine. It consists of technical articles on openSUSE and applications running on openSUSE. For example, the latest issue of the magazine contains articles like "Launching Kubernetes Cluster with Kubic in 10 minutes", "Accessing to Google Drive from openSUSE", and "How to enable HTTPS with Let's Encrypt." Since 2014, we have published 9 issues of Geeko Magazine. In this talk, after explaining the culture of self-publishing in Japan, I will talk about the process from calling articles from the user group until distributing Geeko Magazine. Another topic is our challenge: editing the magazine on openSUSE. Thereby, we cannot use popular desktop publishing (DTP) applications like Adobe InDesign. Instead of such applications, we have been using Scribus, an OSS DTP application to edit Geeko Magazine. It supports CMYK color and DTP data such as trim marks and bleed areas, required by print shops. However, in 2014, Scribus was not adequate for writing a Japanese document. This is because typesetting rules are much different from English etc. To publish Geeko Magazine, we went OSS way; we have improved Scribus one by one at every issue of the magazine in cooperation with the upstream community. I will talk about a brief summary of those problems we have resolved. Japan openSUSE User Group publishes a technical magazine every half year. The title of the magazine is Geeko Magazine. It consists of technical articles on openSUSE and applications running on openSUSE. For example, the latest issue of the magazine contains articles like "Launching Kubernetes Cluster with Kubic in 10 minutes", "Accessing to Google Drive from openSUSE", and "How to enable HTTPS with Let's Encrypt." Since 2014, we have published 9 issues of Geeko Magazine. In this talk, after explaining the culture of self-publishing in Japan, I will talk about the process from calling articles from the user group until distributing Geeko Magazine. Another topic is our challenge: editing the magazine on openSUSE. Thereby, we cannot use popular desktop publishing (DTP) applications like Adobe InDesign. Instead of such applications, we have been using Scribus, an OSS DTP application to edit Geeko Magazine. It supports CMYK color and DTP data such as trim marks and bleed areas, required by print shops. However, in 2014, Scribus was not adequate for writing a Japanese document. This is because typesetting rules are much different from English etc. To publish Geeko Magazine, we went OSS way; we have improved Scribus one by one at every issue of the magazine in cooperation with the upstream community. I will talk about a brief summary of those problems we have resolved. about this event: https://c3voc.de 00:43:28 https://media.ccc.de/v/2492-suse-package-hub-from-community-to-enterprise SUSE Package Hub provides open source packages from the Community to SUSE Linux Enterprise Users. This talk shows the current state, explains how to contribute and also gives some insights in the live of Package Hub. SUSE Package Hub provides open source packages from the Community to SUSE Linux Enterprise Users. This talk shows the current state, explains how to contribute and also gives some insights in the live of Package Hub. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2492-eng-SUSE_Package_Hub_-_From_Community_to_Enterprise_opus.opus?1558719094 bmP7L6IcODD0pR1J8n-A-A 2019-05-24T00:00:00+02:00 Wolfgang Engel No osc19, 2492, openSUSE SUSE Package Hub provides open source packages from the Community to SUSE Linux Enterprise Users. This talk shows the current state, explains how to contribute and also gives some insights in the live of Package Hub. SUSE Package Hub provides open source packages from the Community to SUSE Linux Enterprise Users. This talk shows the current state, explains how to contribute and also gives some insights in the live of Package Hub. about this event: https://c3voc.de 00:18:53 https://media.ccc.de/v/2435-introduction-to-yubikeys-in-opensuse YubiKeys are handy little USB tokens that allow for hardware-based cryptography, which are becoming ever more prevalent. They provide support for a great variety of cryptographic protocols and standards, and offer several modes of operations. While this makes them very versatile, it can also be somewhat confusing, especially when you are only getting in touch with them for the first time. This talk is an introduction to YubiKeys. It will explain what multifactor authentication is about, what kind of problems the YubiKey is addressing, and how the different modes of operation can be used to improve computer security. In this talk two new emerging authentication standards will also be touched upon, namely WebAuthn and FIDO2. These are related to the YubiKey and in combination will make authentication throughout the Internet substantially more secure. More importantly, however, it is very easy to use - even by non-technical people! A live demonstration will show you how a typical workflow looks like. Some advice and good practice, along with a Q&A session will conclude the talk. Recently some effort has been put into packaging and updating the software stack for YubiKeys within openSUSE, so that everything (including the latest generation of YubiKeys) are supported out-of-the box. For this talk no prior knowledge about the topic is required and/or expected. Any cryptographic concepts that are needed for explanation will be introduced on a high-level during the talk. Having basic cryptographic knowledge will definitely make it easier to follow along on some details, though. YubiKeys are handy little USB tokens that allow for hardware-based cryptography, which are becoming ever more prevalent. They provide support for a great variety of cryptographic protocols and standards, and offer several modes of operations. While this makes them very versatile, it can also be somewhat confusing, especially when you are only getting in touch with them for the first time. This talk is an introduction to YubiKeys. It will explain what multifactor authentication is about, what kind of problems the YubiKey is addressing, and how the different modes of operation can be used to improve computer security. In this talk two new emerging authentication standards will also be touched upon, namely WebAuthn and FIDO2. These are related to the YubiKey and in combination will make authentication throughout the Internet substantially more secure. More importantly, however, it is very easy to use - even by non-technical people! A live demonstration will show you how a typical workflow looks like. Some advice and good practice, along with a Q&A session will conclude the talk. Recently some effort has been put into packaging and updating the software stack for YubiKeys within openSUSE, so that everything (including the latest generation of YubiKeys) are supported out-of-the box. For this talk no prior knowledge about the topic is required and/or expected. Any cryptographic concepts that are needed for explanation will be introduced on a high-level during the talk. Having basic cryptographic knowledge will definitely make it easier to follow along on some details, though. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2435-eng-Introduction_to_YubiKeys_in_openSUSE_opus.opus?1558718554 B7CBSq7u1UrdIoJSOaMcUQ 2019-05-24T00:00:00+02:00 kbabioch No osc19, 2435, Desktop and Applications Everything you should know about YubiKey YubiKeys are handy little USB tokens that allow for hardware-based cryptography, which are becoming ever more prevalent. They provide support for a great variety of cryptographic protocols and standards, and offer several modes of operations. While this makes them very versatile, it can also be somewhat confusing, especially when you are only getting in touch with them for the first time. This talk is an introduction to YubiKeys. It will explain what multifactor authentication is about, what kind of problems the YubiKey is addressing, and how the different modes of operation can be used to improve computer security. In this talk two new emerging authentication standards will also be touched upon, namely WebAuthn and FIDO2. These are related to the YubiKey and in combination will make authentication throughout the Internet substantially more secure. More importantly, however, it is very easy to use - even by non-technical people! A live demonstration will show you how a typical workflow looks like. Some advice and good practice, along with a Q&A session will conclude the talk. Recently some effort has been put into packaging and updating the software stack for YubiKeys within openSUSE, so that everything (including the latest generation of YubiKeys) are supported out-of-the box. For this talk no prior knowledge about the topic is required and/or expected. Any cryptographic concepts that are needed for explanation will be introduced on a high-level during the talk. Having basic cryptographic knowledge will definitely make it easier to follow along on some details, though. YubiKeys are handy little USB tokens that allow for hardware-based cryptography, which are becoming ever more prevalent. They provide support for a great variety of cryptographic protocols and standards, and offer several modes of operations. While this makes them very versatile, it can also be somewhat confusing, especially when you are only getting in touch with them for the first time. This talk is an introduction to YubiKeys. It will explain what multifactor authentication is about, what kind of problems the YubiKey is addressing, and how the different modes of operation can be used to improve computer security. In this talk two new emerging authentication standards will also be touched upon, namely WebAuthn and FIDO2. These are related to the YubiKey and in combination will make authentication throughout the Internet substantially more secure. More importantly, however, it is very easy to use - even by non-technical people! A live demonstration will show you how a typical workflow looks like. Some advice and good practice, along with a Q&A session will conclude the talk. Recently some effort has been put into packaging and updating the software stack for YubiKeys within openSUSE, so that everything (including the latest generation of YubiKeys) are supported out-of-the box. For this talk no prior knowledge about the topic is required and/or expected. Any cryptographic concepts that are needed for explanation will be introduced on a high-level during the talk. Having basic cryptographic knowledge will definitely make it easier to follow along on some details, though. about this event: https://c3voc.de 00:46:22 https://media.ccc.de/v/2393-kubic-with-opensds I introduce OpenSDS that is an open source community working to address storage integration challenges. I remark technology. OpenSDS can manage LVM, Ceph, Cinder, and more as a software defined storage. and We can use OpenSDS in Kubernetes through CSI, Flexvolume, and Service Catalog. therefore, Kubernetes can use software defined storage by OpenSDS. I draw overview of Kubernetes - OpenSDS - storage relationship and explain one case of to build on Kubic. This strategy bring us these benefits: - If Administrator create PodPreset at SDS, Application developer don't need to prepare storage. - If Administrator create storage pool, He don't need to create volume each request. And I explain potential of replication with DRBD. Participant can learn SDS strategy on Kubernetes with OpenSDS. and How to build on Kubic. I introduce OpenSDS that is an open source community working to address storage integration challenges. I remark technology. OpenSDS can manage LVM, Ceph, Cinder, and more as a software defined storage. and We can use OpenSDS in Kubernetes through CSI, Flexvolume, and Service Catalog. therefore, Kubernetes can use software defined storage by OpenSDS. I draw overview of Kubernetes - OpenSDS - storage relationship and explain one case of to build on Kubic. This strategy bring us these benefits: - If Administrator create PodPreset at SDS, Application developer don't need to prepare storage. - If Administrator create storage pool, He don't need to create volume each request. And I explain potential of replication with DRBD. Participant can learn SDS strategy on Kubernetes with OpenSDS. and How to build on Kubic. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2393-eng-Kubic_with_OpenSDS_opus.opus?1558716568 gdfI-Glbwx3op1MmYFwC9A 2019-05-24T00:00:00+02:00 hashimotosyuta No osc19, 2393, Cloud and Containers Flexible software defined storage management I introduce OpenSDS that is an open source community working to address storage integration challenges. I remark technology. OpenSDS can manage LVM, Ceph, Cinder, and more as a software defined storage. and We can use OpenSDS in Kubernetes through CSI, Flexvolume, and Service Catalog. therefore, Kubernetes can use software defined storage by OpenSDS. I draw overview of Kubernetes - OpenSDS - storage relationship and explain one case of to build on Kubic. This strategy bring us these benefits: - If Administrator create PodPreset at SDS, Application developer don't need to prepare storage. - If Administrator create storage pool, He don't need to create volume each request. And I explain potential of replication with DRBD. Participant can learn SDS strategy on Kubernetes with OpenSDS. and How to build on Kubic. I introduce OpenSDS that is an open source community working to address storage integration challenges. I remark technology. OpenSDS can manage LVM, Ceph, Cinder, and more as a software defined storage. and We can use OpenSDS in Kubernetes through CSI, Flexvolume, and Service Catalog. therefore, Kubernetes can use software defined storage by OpenSDS. I draw overview of Kubernetes - OpenSDS - storage relationship and explain one case of to build on Kubic. This strategy bring us these benefits: - If Administrator create PodPreset at SDS, Application developer don't need to prepare storage. - If Administrator create storage pool, He don't need to create volume each request. And I explain potential of replication with DRBD. Participant can learn SDS strategy on Kubernetes with OpenSDS. and How to build on Kubic. about this event: https://c3voc.de 00:27:38 https://media.ccc.de/v/2468-deploying-ceph-with-rook-on-kubic-k8s-cluster In this talk we could see how easy it is to deploy and configure Ceph ready k8s cluster on top of Kubic. And setup Ceph on top of it with Rook (rook.io). We would see couple of examples for Openstack and Vagrant to run such clusters for your CI and development environments. In this talk we could see how easy it is to deploy and configure Ceph ready k8s cluster on top of Kubic. And setup Ceph on top of it with Rook (rook.io). We would see couple of examples for Openstack and Vagrant to run such clusters for your CI and development environments. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2468-eng-Deploying_Ceph_with_Rook_on_Kubic_k8s_cluster_opus.opus?1558714623 XUovULBhNMilNEB3Jj5YuA 2019-05-24T00:00:00+02:00 Denis Kondratenko No osc19, 2468, Cloud and Containers In this talk we could see how easy it is to deploy and configure Ceph ready k8s cluster on top of Kubic. And setup Ceph on top of it with Rook (rook.io). We would see couple of examples for Openstack and Vagrant to run such clusters for your CI and development environments. In this talk we could see how easy it is to deploy and configure Ceph ready k8s cluster on top of Kubic. And setup Ceph on top of it with Rook (rook.io). We would see couple of examples for Openstack and Vagrant to run such clusters for your CI and development environments. about this event: https://c3voc.de 00:30:15 https://media.ccc.de/v/2495-thinking-about-opensuse-hcl I have been a part of the Taiwan openSUSE community for almost a year. During this time, I was a volunteer at the openSUSE Asia Summit 2018, and I attended monthly openSUSE meet-ups. It feels great to have a group of people with whom to study and share knowledge. In the new year, I am curious about how I can contribute to the community with my expertise as an OS certification technical manager in the server hardware industry. My job is to ensure the hardware product we make is compatible with as many operating systems as possible. Therefore, the first option I have looked into is the Hardware Compatibility List (HCL). Why does the HCL matter? There are four reasons: 1. For some users, an HCL is mandatory before ordering can be started. 2. It increases the user base; by having an updated HCL, people can easily start to use it. 3. Providing a hardware compatibility process to hardware vendors so they can display openSUSE as a compatible OS to their customers could be a chance to increase visibility to users. 4. Establishing an easy-to-follow hardware testing policy may increase the number of hardware vendors and users available to do the test and to report more bugs, and it will make openSUSE more reliable. The good news is that openSUSE already has an HCL on its wiki page, but we are still facing some challenges. Here, I listed four major problems: 1. The data are entirely outdated. 2. There is much inconsistent information. 3. There is a lack of real data from the real system. 4. Anyone can edit the existing HCL, which could make the data unreliable. To solve the problems, I herein propose three approaches to improve the HCL: 1. Develop a simple test kit to record the hardware information from the testing hardware system and provide the result to the HCL by submitting logs. 2. Leverage the SUSE Yes Certification Program’s result, listing the SUSE-certified servers in the openSUSE HCL. 3. Expand the HCL source from users to hardware vendors to collect HCL data from the source that are more reliable. Ultimately, the HCL could develop into a hardware certification program, which can create more value. Adding more test cases can provide more compatibility between the hardware and openSUSE. In addition, we can create more policies to guide the hardware vendor, and we can even design a logo to prove compatibility in the market. In the end, I will talk about the call to action. If the audiences are interested in the idea, the HCL needs more people to become involved to: 1. Develop a test suite to collect the HW data; it must be expandable for adding more test cases in the future. 2. Create a basic guideline for the people who want to test their hardware and submit the logs to the openSUSE HCL. 3. Form a team/committee to oversee the process of submitting the HCL. I have been a part of the Taiwan openSUSE community for almost a year. During this time, I was a volunteer at the openSUSE Asia Summit 2018, and I attended monthly openSUSE meet-ups. It feels great to have a group of people with whom to study and share knowledge. In the new year, I am curious about how I can contribute to the community with my expertise as an OS certification technical manager in the server hardware industry. My job is to ensure the hardware product we make is compatible with as many operating systems as possible. Therefore, the first option I have looked into is the Hardware Compatibility List (HCL). Why does the HCL matter? There are four reasons: 1. For some users, an HCL is mandatory before ordering can be started. 2. It increases the user base; by having an updated HCL, people can easily start to use it. 3. Providing a hardware compatibility process to hardware vendors so they can display openSUSE as a compatible OS to their customers could be a chance to increase visibility to users. 4. Establishing an easy-to-follow hardware testing policy may increase the number of hardware vendors and users available to do the test and to report more bugs, and it will make openSUSE more reliable. The good news is that openSUSE already has an HCL on its wiki page, but we are still facing some challenges. Here, I listed four major problems: 1. The data are entirely outdated. 2. There is much inconsistent information. 3. There is a lack of real data from the real system. 4. Anyone can edit the existing HCL, which could make the data unreliable. To solve the problems, I herein propose three approaches to improve the HCL: 1. Develop a simple test kit to record the hardware information from the testing hardware system and provide the result to the HCL by submitting logs. 2. Leverage the SUSE Yes Certification Program’s result, listing the SUSE-certified servers in the openSUSE HCL. 3. Expand the HCL source from users to hardware vendors to collect HCL data from the source that are more reliable. Ultimately, the HCL could develop into a hardware certification program, which can create more value. Adding more test cases can provide more compatibility between the hardware and openSUSE. In addition, we can create more policies to guide the hardware vendor, and we can even design a logo to prove compatibility in the market. In the end, I will talk about the call to action. If the audiences are interested in the idea, the HCL needs more people to become involved to: 1. Develop a test suite to collect the HW data; it must be expandable for adding more test cases in the future. 2. Create a basic guideline for the people who want to test their hardware and submit the logs to the openSUSE HCL. 3. Form a team/committee to oversee the process of submitting the HCL. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2495-eng-Thinking_About_openSUSE_HCL_opus.opus?1558714564 R_xgbDbjKckw1D_7uNzUVQ 2019-05-24T00:00:00+02:00 Joshsi No osc19, 2495, openSUSE Let's Keep HCL Updated I have been a part of the Taiwan openSUSE community for almost a year. During this time, I was a volunteer at the openSUSE Asia Summit 2018, and I attended monthly openSUSE meet-ups. It feels great to have a group of people with whom to study and share knowledge. In the new year, I am curious about how I can contribute to the community with my expertise as an OS certification technical manager in the server hardware industry. My job is to ensure the hardware product we make is compatible with as many operating systems as possible. Therefore, the first option I have looked into is the Hardware Compatibility List (HCL). Why does the HCL matter? There are four reasons: 1. For some users, an HCL is mandatory before ordering can be started. 2. It increases the user base; by having an updated HCL, people can easily start to use it. 3. Providing a hardware compatibility process to hardware vendors so they can display openSUSE as a compatible OS to their customers could be a chance to increase visibility to users. 4. Establishing an easy-to-follow hardware testing policy may increase the number of hardware vendors and users available to do the test and to report more bugs, and it will make openSUSE more reliable. The good news is that openSUSE already has an HCL on its wiki page, but we are still facing some challenges. Here, I listed four major problems: 1. The data are entirely outdated. 2. There is much inconsistent information. 3. There is a lack of real data from the real system. 4. Anyone can edit the existing HCL, which could make the data unreliable. To solve the problems, I herein propose three approaches to improve the HCL: 1. Develop a simple test kit to record the hardware information from the testing hardware system and provide the result to the HCL by submitting logs. 2. Leverage the SUSE Yes Certification Program’s result, listing the SUSE-certified servers in the openSUSE HCL. 3. Expand the HCL source from users to hardware vendors to collect HCL data from the source that are more reliable. Ultimately, the HCL could develop into a hardware certification program, which can create more value. Adding more test cases can provide more compatibility between the hardware and openSUSE. In addition, we can create more policies to guide the hardware vendor, and we can even design a logo to prove compatibility in the market. In the end, I will talk about the call to action. If the audiences are interested in the idea, the HCL needs more people to become involved to: 1. Develop a test suite to collect the HW data; it must be expandable for adding more test cases in the future. 2. Create a basic guideline for the people who want to test their hardware and submit the logs to the openSUSE HCL. 3. Form a team/committee to oversee the process of submitting the HCL. I have been a part of the Taiwan openSUSE community for almost a year. During this time, I was a volunteer at the openSUSE Asia Summit 2018, and I attended monthly openSUSE meet-ups. It feels great to have a group of people with whom to study and share knowledge. In the new year, I am curious about how I can contribute to the community with my expertise as an OS certification technical manager in the server hardware industry. My job is to ensure the hardware product we make is compatible with as many operating systems as possible. Therefore, the first option I have looked into is the Hardware Compatibility List (HCL). Why does the HCL matter? There are four reasons: 1. For some users, an HCL is mandatory before ordering can be started. 2. It increases the user base; by having an updated HCL, people can easily start to use it. 3. Providing a hardware compatibility process to hardware vendors so they can display openSUSE as a compatible OS to their customers could be a chance to increase visibility to users. 4. Establishing an easy-to-follow hardware testing policy may increase the number of hardware vendors and users available to do the test and to report more bugs, and it will make openSUSE more reliable. The good news is that openSUSE already has an HCL on its wiki page, but we are still facing some challenges. Here, I listed four major problems: 1. The data are entirely outdated. 2. There is much inconsistent information. 3. There is a lack of real data from the real system. 4. Anyone can edit the existing HCL, which could make the data unreliable. To solve the problems, I herein propose three approaches to improve the HCL: 1. Develop a simple test kit to record the hardware information from the testing hardware system and provide the result to the HCL by submitting logs. 2. Leverage the SUSE Yes Certification Program’s result, listing the SUSE-certified servers in the openSUSE HCL. 3. Expand the HCL source from users to hardware vendors to collect HCL data from the source that are more reliable. Ultimately, the HCL could develop into a hardware certification program, which can create more value. Adding more test cases can provide more compatibility between the hardware and openSUSE. In addition, we can create more policies to guide the hardware vendor, and we can even design a logo to prove compatibility in the market. In the end, I will talk about the call to action. If the audiences are interested in the idea, the HCL needs more people to become involved to: 1. Develop a test suite to collect the HW data; it must be expandable for adding more test cases in the future. 2. Create a basic guideline for the people who want to test their hardware and submit the logs to the openSUSE HCL. 3. Form a team/committee to oversee the process of submitting the HCL. about this event: https://c3voc.de 00:29:22 https://media.ccc.de/v/2531-opensuse-microos-desktop Kubic with its MicroOS core is an exciting distribution that takes much of the cool stuff we're doing in Tumbleweed, adds solutions to the problems of updating a running system, and is becoming the perfect base system for running containers. But in openSUSE, running server stuff is only half the fun. Why should servers be the only platform enjoying automatic, atomic, "auto-rollbackable" system updates? Surely desktop users want to be lazy like server admins also? Can the tools and approaches implemented in MicroOS help create the desktop distribution of the future? Let's find out! This talk will introduce the concept of 'openSUSE MicroOS Desktop', a desktop focused variant of MicroOS based on Tumbleweed. Various ideas will be discussed, prototypes will be shown, and feedback will be expected from the audience to help shape this potentially exciting take on the future of openSUSE on Desktops. Kubic with its MicroOS core is an exciting distribution that takes much of the cool stuff we're doing in Tumbleweed, adds solutions to the problems of updating a running system, and is becoming the perfect base system for running containers. But in openSUSE, running server stuff is only half the fun. Why should servers be the only platform enjoying automatic, atomic, "auto-rollbackable" system updates? Surely desktop users want to be lazy like server admins also? Can the tools and approaches implemented in MicroOS help create the desktop distribution of the future? Let's find out! This talk will introduce the concept of 'openSUSE MicroOS Desktop', a desktop focused variant of MicroOS based on Tumbleweed. Various ideas will be discussed, prototypes will be shown, and feedback will be expected from the audience to help shape this potentially exciting take on the future of openSUSE on Desktops. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2531-eng-openSUSE_MicroOS_Desktop_opus.opus?1558712643 FYZNn_oSKwNj28O6WUViuw 2019-05-24T00:00:00+02:00 Richard Brown No osc19, 2531, Desktop and Applications A New openSUSE Desktop Distribution? Kubic with its MicroOS core is an exciting distribution that takes much of the cool stuff we're doing in Tumbleweed, adds solutions to the problems of updating a running system, and is becoming the perfect base system for running containers. But in openSUSE, running server stuff is only half the fun. Why should servers be the only platform enjoying automatic, atomic, "auto-rollbackable" system updates? Surely desktop users want to be lazy like server admins also? Can the tools and approaches implemented in MicroOS help create the desktop distribution of the future? Let's find out! This talk will introduce the concept of 'openSUSE MicroOS Desktop', a desktop focused variant of MicroOS based on Tumbleweed. Various ideas will be discussed, prototypes will be shown, and feedback will be expected from the audience to help shape this potentially exciting take on the future of openSUSE on Desktops. Kubic with its MicroOS core is an exciting distribution that takes much of the cool stuff we're doing in Tumbleweed, adds solutions to the problems of updating a running system, and is becoming the perfect base system for running containers. But in openSUSE, running server stuff is only half the fun. Why should servers be the only platform enjoying automatic, atomic, "auto-rollbackable" system updates? Surely desktop users want to be lazy like server admins also? Can the tools and approaches implemented in MicroOS help create the desktop distribution of the future? Let's find out! This talk will introduce the concept of 'openSUSE MicroOS Desktop', a desktop focused variant of MicroOS based on Tumbleweed. Various ideas will be discussed, prototypes will be shown, and feedback will be expected from the audience to help shape this potentially exciting take on the future of openSUSE on Desktops. about this event: https://c3voc.de 00:41:39 https://media.ccc.de/v/2444-opensuse-microos-in-production This talk will be about deploying comment business applications on openSUSE MicroOS It will have a 15 mins presentation about the challenges that we face at our company La Sentinelle, Mauritius (https://www.lasentinelle.mu) and how we used openSUSE MicroOS to address those. The presentation will follow by a 30 mins technical demo deploying a business application on MicroOSp. Finally, there will be 15 mins to address questions pertaining to the technical demo and any other business. This talk will be about deploying comment business applications on openSUSE MicroOS It will have a 15 mins presentation about the challenges that we face at our company La Sentinelle, Mauritius (https://www.lasentinelle.mu) and how we used openSUSE MicroOS to address those. The presentation will follow by a 30 mins technical demo deploying a business application on MicroOSp. Finally, there will be 15 mins to address questions pertaining to the technical demo and any other business. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2444-eng-openSUSE_MicroOS_in_Production_opus.opus?1558712524 JT01r0-bwd2t4iKNoCLBVg 2019-05-24T00:00:00+02:00 Ish Sookun No osc19, 2444, Cloud and Containers Deploying apps using Podman This talk will be about deploying comment business applications on openSUSE MicroOS It will have a 15 mins presentation about the challenges that we face at our company La Sentinelle, Mauritius (https://www.lasentinelle.mu) and how we used openSUSE MicroOS to address those. The presentation will follow by a 30 mins technical demo deploying a business application on MicroOSp. Finally, there will be 15 mins to address questions pertaining to the technical demo and any other business. This talk will be about deploying comment business applications on openSUSE MicroOS It will have a 15 mins presentation about the challenges that we face at our company La Sentinelle, Mauritius (https://www.lasentinelle.mu) and how we used openSUSE MicroOS to address those. The presentation will follow by a 30 mins technical demo deploying a business application on MicroOSp. Finally, there will be 15 mins to address questions pertaining to the technical demo and any other business. about this event: https://c3voc.de 00:16:22 https://media.ccc.de/v/2456-kubernetes-the-hard-way-on-opensuse-cloud-environment "Kubernetes" is one of the most popular and famous container orchestration open source software. And now, there are so many Kubernetes environments and deployment tools such as SUSE CaaS Platform, minikube, kubeadm, Rancher, GKE/AKS/EKS, etc. So, we can use or build a Kubernetes cluster with them very easily. However, it also prevents opportunities to understand Kubernetes technologies themselves from people who want to know the architecture itself. Therefore, if a Kubernetes cluster gets something wrong, it would be tough challenge to resolve it without such knowledge. For such a situation, here is a very good exercise document - "Kubernetes The Hard Way[0]" which is a tutorial for setting up Kubernetes the hard way on Google Cloud Platform(GCP). People can learn internal architecture of Kubernetes from that. In this session, attendees will get an opportunity to know how to set up a Kubernetes cluster on not only GCP but also an openSUSE OpenStack cloud based on the tutorial, and, will get to know its technology deeply. "Kubernetes The Hard Way"[0] has 14 chapters right now. And it's written for the GCP basically. However, it works on the other clouds (e.g. openSUSE OpenStack Cloud) with some modifications. [0] https://github.com/kelseyhightower/kubernetes-the-hard-way Kubernetes The Hard Way outlines:: 1. Prerequisites 2. Installing the Client Tools 3. Provisioning Compute Resources 4. Provisioning a CA and Generating TLS Certificates 5. Generating Kubernetes Configuration Files for Authentication 6. Generating the Data Encryption Config and Key 7. Bootstrapping the etcd Cluster 8. Bootstrapping the Kubernetes Control Plane 9. Bootstrapping the Kubernetes Worker Nodes 10. Configuring kubectl for Remote Access 11. Provisioning Pod Network Routes 12. Deploying the DNS Cluster Add-on 13. Smoke Test 14. Cleaning Up "Kubernetes" is one of the most popular and famous container orchestration open source software. And now, there are so many Kubernetes environments and deployment tools such as SUSE CaaS Platform, minikube, kubeadm, Rancher, GKE/AKS/EKS, etc. So, we can use or build a Kubernetes cluster with them very easily. However, it also prevents opportunities to understand Kubernetes technologies themselves from people who want to know the architecture itself. Therefore, if a Kubernetes cluster gets something wrong, it would be tough challenge to resolve it without such knowledge. For such a situation, here is a very good exercise document - "Kubernetes The Hard Way[0]" which is a tutorial for setting up Kubernetes the hard way on Google Cloud Platform(GCP). People can learn internal architecture of Kubernetes from that. In this session, attendees will get an opportunity to know how to set up a Kubernetes cluster on not only GCP but also an openSUSE OpenStack cloud based on the tutorial, and, will get to know its technology deeply. "Kubernetes The Hard Way"[0] has 14 chapters right now. And it's written for the GCP basically. However, it works on the other clouds (e.g. openSUSE OpenStack Cloud) with some modifications. [0] https://github.com/kelseyhightower/kubernetes-the-hard-way Kubernetes The Hard Way outlines:: 1. Prerequisites 2. Installing the Client Tools 3. Provisioning Compute Resources 4. Provisioning a CA and Generating TLS Certificates 5. Generating Kubernetes Configuration Files for Authentication 6. Generating the Data Encryption Config and Key 7. Bootstrapping the etcd Cluster 8. Bootstrapping the Kubernetes Control Plane 9. Bootstrapping the Kubernetes Worker Nodes 10. Configuring kubectl for Remote Access 11. Provisioning Pod Network Routes 12. Deploying the DNS Cluster Add-on 13. Smoke Test 14. Cleaning Up about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2456-eng-Kubernetes_The_Hard_Way_on_openSUSE_Cloud_environment_opus.opus?1558712044 7_UawP-ER0fSbXRipXqR-g 2019-05-24T00:00:00+02:00 Masayuki Igawa No osc19, 2456, Cloud and Containers Let's build your own cloud "Kubernetes" is one of the most popular and famous container orchestration open source software. And now, there are so many Kubernetes environments and deployment tools such as SUSE CaaS Platform, minikube, kubeadm, Rancher, GKE/AKS/EKS, etc. So, we can use or build a Kubernetes cluster with them very easily. However, it also prevents opportunities to understand Kubernetes technologies themselves from people who want to know the architecture itself. Therefore, if a Kubernetes cluster gets something wrong, it would be tough challenge to resolve it without such knowledge. For such a situation, here is a very good exercise document - "Kubernetes The Hard Way[0]" which is a tutorial for setting up Kubernetes the hard way on Google Cloud Platform(GCP). People can learn internal architecture of Kubernetes from that. In this session, attendees will get an opportunity to know how to set up a Kubernetes cluster on not only GCP but also an openSUSE OpenStack cloud based on the tutorial, and, will get to know its technology deeply. "Kubernetes The Hard Way"[0] has 14 chapters right now. And it's written for the GCP basically. However, it works on the other clouds (e.g. openSUSE OpenStack Cloud) with some modifications. [0] https://github.com/kelseyhightower/kubernetes-the-hard-way Kubernetes The Hard Way outlines:: 1. Prerequisites 2. Installing the Client Tools 3. Provisioning Compute Resources 4. Provisioning a CA and Generating TLS Certificates 5. Generating Kubernetes Configuration Files for Authentication 6. Generating the Data Encryption Config and Key 7. Bootstrapping the etcd Cluster 8. Bootstrapping the Kubernetes Control Plane 9. Bootstrapping the Kubernetes Worker Nodes 10. Configuring kubectl for Remote Access 11. Provisioning Pod Network Routes 12. Deploying the DNS Cluster Add-on 13. Smoke Test 14. Cleaning Up "Kubernetes" is one of the most popular and famous container orchestration open source software. And now, there are so many Kubernetes environments and deployment tools such as SUSE CaaS Platform, minikube, kubeadm, Rancher, GKE/AKS/EKS, etc. So, we can use or build a Kubernetes cluster with them very easily. However, it also prevents opportunities to understand Kubernetes technologies themselves from people who want to know the architecture itself. Therefore, if a Kubernetes cluster gets something wrong, it would be tough challenge to resolve it without such knowledge. For such a situation, here is a very good exercise document - "Kubernetes The Hard Way[0]" which is a tutorial for setting up Kubernetes the hard way on Google Cloud Platform(GCP). People can learn internal architecture of Kubernetes from that. In this session, attendees will get an opportunity to know how to set up a Kubernetes cluster on not only GCP but also an openSUSE OpenStack cloud based on the tutorial, and, will get to know its technology deeply. "Kubernetes The Hard Way"[0] has 14 chapters right now. And it's written for the GCP basically. However, it works on the other clouds (e.g. openSUSE OpenStack Cloud) with some modifications. [0] https://github.com/kelseyhightower/kubernetes-the-hard-way Kubernetes The Hard Way outlines:: 1. Prerequisites 2. Installing the Client Tools 3. Provisioning Compute Resources 4. Provisioning a CA and Generating TLS Certificates 5. Generating Kubernetes Configuration Files for Authentication 6. Generating the Data Encryption Config and Key 7. Bootstrapping the etcd Cluster 8. Bootstrapping the Kubernetes Control Plane 9. Bootstrapping the Kubernetes Worker Nodes 10. Configuring kubectl for Remote Access 11. Provisioning Pod Network Routes 12. Deploying the DNS Cluster Add-on 13. Smoke Test 14. Cleaning Up about this event: https://c3voc.de 00:25:49 https://media.ccc.de/v/2528-opensuse-microos As the world moves more and more towards containerised solutions, a number of real questions start to appear. - What is the perfect platform for running containers atop? - How to use this platform as part of a flexible, scalable, highly available infrastructure fabric? - How to minimize the maintenance and administration of this platform at scale? Many of these problems are well answered in enterprise container offerings, but for developers more interested in the state of containers & kubernetes upstream, new issues start to appear. With such fast moving upstreams, developers and enthusiasts need a platform that can keep up and is closely involved with those upstream developments. This platform needs to not only be able to run containers at scale, but also on single machine, all the while preserving the attributes of low maintenance so the focus can be on the containers, not the base system beneath them. And then the question becomes "What is so special about containers anyway?" - in more and more cases, people are deploying Linux VMs, Cloud instances, or bare metal to do 'just one job', with other jobs being handled by other machines. Can we simplify the Operating System and make it easier to live with if we optimise it for these 'single-purpose' deployments? This talk introduces openSUSE MicroOS, and explains how it addresses the above, being the perfect distribution for this modern age. The session will explore in some detail how MicroOS is developed in lockstep with the Tumbleweed rolling release and can be used for a wide variety of single-purpose systems. This talk will also discuss openSUSE Kubic, the MicroOS variant focused on containers. The talk will share how Kubic collaborates with various upstreams including kubeadm and CRI-O. Transactional Updates, Kubic's system update stack will be demonstrated and the benefits from such an atomic update approach discussed in some detail. Finally the kubictl Kubernetes cluster boostrapping tool will be discussed and some future plans shared for consideration and feedback. As the world moves more and more towards containerised solutions, a number of real questions start to appear. - What is the perfect platform for running containers atop? - How to use this platform as part of a flexible, scalable, highly available infrastructure fabric? - How to minimize the maintenance and administration of this platform at scale? Many of these problems are well answered in enterprise container offerings, but for developers more interested in the state of containers & kubernetes upstream, new issues start to appear. With such fast moving upstreams, developers and enthusiasts need a platform that can keep up and is closely involved with those upstream developments. This platform needs to not only be able to run containers at scale, but also on single machine, all the while preserving the attributes of low maintenance so the focus can be on the containers, not the base system beneath them. And then the question becomes "What is so special about containers anyway?" - in more and more cases, people are deploying Linux VMs, Cloud instances, or bare metal to do 'just one job', with other jobs being handled by other machines. Can we simplify the Operating System and make it easier to live with if we optimise it for these 'single-purpose' deployments? This talk introduces openSUSE MicroOS, and explains how it addresses the above, being the perfect distribution for this modern age. The session will explore in some detail how MicroOS is developed in lockstep with the Tumbleweed rolling release and can be used for a wide variety of single-purpose systems. This talk will also discuss openSUSE Kubic, the MicroOS variant focused on containers. The talk will share how Kubic collaborates with various upstreams including kubeadm and CRI-O. Transactional Updates, Kubic's system update stack will be demonstrated and the benefits from such an atomic update approach discussed in some detail. Finally the kubictl Kubernetes cluster boostrapping tool will be discussed and some future plans shared for consideration and feedback. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2528-eng-openSUSE_MicroOS_opus.opus?1558711804 drBsJm1OspmodxlcUlVZoA 2019-05-24T00:00:00+02:00 Richard Brown No osc19, 2528, Cloud and Containers A new distro for a new age As the world moves more and more towards containerised solutions, a number of real questions start to appear. - What is the perfect platform for running containers atop? - How to use this platform as part of a flexible, scalable, highly available infrastructure fabric? - How to minimize the maintenance and administration of this platform at scale? Many of these problems are well answered in enterprise container offerings, but for developers more interested in the state of containers & kubernetes upstream, new issues start to appear. With such fast moving upstreams, developers and enthusiasts need a platform that can keep up and is closely involved with those upstream developments. This platform needs to not only be able to run containers at scale, but also on single machine, all the while preserving the attributes of low maintenance so the focus can be on the containers, not the base system beneath them. And then the question becomes "What is so special about containers anyway?" - in more and more cases, people are deploying Linux VMs, Cloud instances, or bare metal to do 'just one job', with other jobs being handled by other machines. Can we simplify the Operating System and make it easier to live with if we optimise it for these 'single-purpose' deployments? This talk introduces openSUSE MicroOS, and explains how it addresses the above, being the perfect distribution for this modern age. The session will explore in some detail how MicroOS is developed in lockstep with the Tumbleweed rolling release and can be used for a wide variety of single-purpose systems. This talk will also discuss openSUSE Kubic, the MicroOS variant focused on containers. The talk will share how Kubic collaborates with various upstreams including kubeadm and CRI-O. Transactional Updates, Kubic's system update stack will be demonstrated and the benefits from such an atomic update approach discussed in some detail. Finally the kubictl Kubernetes cluster boostrapping tool will be discussed and some future plans shared for consideration and feedback. As the world moves more and more towards containerised solutions, a number of real questions start to appear. - What is the perfect platform for running containers atop? - How to use this platform as part of a flexible, scalable, highly available infrastructure fabric? - How to minimize the maintenance and administration of this platform at scale? Many of these problems are well answered in enterprise container offerings, but for developers more interested in the state of containers & kubernetes upstream, new issues start to appear. With such fast moving upstreams, developers and enthusiasts need a platform that can keep up and is closely involved with those upstream developments. This platform needs to not only be able to run containers at scale, but also on single machine, all the while preserving the attributes of low maintenance so the focus can be on the containers, not the base system beneath them. And then the question becomes "What is so special about containers anyway?" - in more and more cases, people are deploying Linux VMs, Cloud instances, or bare metal to do 'just one job', with other jobs being handled by other machines. Can we simplify the Operating System and make it easier to live with if we optimise it for these 'single-purpose' deployments? This talk introduces openSUSE MicroOS, and explains how it addresses the above, being the perfect distribution for this modern age. The session will explore in some detail how MicroOS is developed in lockstep with the Tumbleweed rolling release and can be used for a wide variety of single-purpose systems. This talk will also discuss openSUSE Kubic, the MicroOS variant focused on containers. The talk will share how Kubic collaborates with various upstreams including kubeadm and CRI-O. Transactional Updates, Kubic's system update stack will be demonstrated and the benefits from such an atomic update approach discussed in some detail. Finally the kubictl Kubernetes cluster boostrapping tool will be discussed and some future plans shared for consideration and feedback. about this event: https://c3voc.de 00:42:56 https://media.ccc.de/v/2480-dnf-vs-zypp-fight In one corner, we have Zypper: the successor to the motley of package management options from Ximian and SuSE. Created after the merger of the Ximian and YaST package manager teams, it was a pioneer in using the SAT solver for package management and proved that it worked well at scale in a large and popular Linux distribution platform (SUSE Linux). It spawned the development of libsatsolver, which became libsolv. Considered by many to be the most advanced and fastest package manager, it is created a class of package managers all on its own. It is used in openSUSE, but is also available in Fedora and other RPM-based Linux distributions. In the other corner, we have DNF: the anointed successor to YUM (Yellowdog Updater, Modified). DNF (Dandified YUM) was forked from YUM to rework the internals to leverage libsolv and offer a saner, more maintainable API. Forged from the blood, sweat, and tears of many package manager developers from Red Hat and others, DNF is built with the lessons in mind from the last decade of software and systems management experiences. A new up and comer, it is used in Fedora, Mageia, OpenMandriva, Yocto, and others. It is also available in openSUSE. How do these two package managers compare? Are they more similar than different? Has DNF made YUM no longer a trash heap? Does ZYpp still rule the roost? This talk explores both package managers and compares them from a technical, usability, and ecosystem perspective. Who knows? Perhaps there are lessons to still be learned for evolving both package managers. In one corner, we have Zypper: the successor to the motley of package management options from Ximian and SuSE. Created after the merger of the Ximian and YaST package manager teams, it was a pioneer in using the SAT solver for package management and proved that it worked well at scale in a large and popular Linux distribution platform (SUSE Linux). It spawned the development of libsatsolver, which became libsolv. Considered by many to be the most advanced and fastest package manager, it is created a class of package managers all on its own. It is used in openSUSE, but is also available in Fedora and other RPM-based Linux distributions. In the other corner, we have DNF: the anointed successor to YUM (Yellowdog Updater, Modified). DNF (Dandified YUM) was forked from YUM to rework the internals to leverage libsolv and offer a saner, more maintainable API. Forged from the blood, sweat, and tears of many package manager developers from Red Hat and others, DNF is built with the lessons in mind from the last decade of software and systems management experiences. A new up and comer, it is used in Fedora, Mageia, OpenMandriva, Yocto, and others. It is also available in openSUSE. How do these two package managers compare? Are they more similar than different? Has DNF made YUM no longer a trash heap? Does ZYpp still rule the roost? This talk explores both package managers and compares them from a technical, usability, and ecosystem perspective. Who knows? Perhaps there are lessons to still be learned for evolving both package managers. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2480-eng-DNF_vs_ZYpp_Fight_opus.opus?1558711534 6Vz-zO0BBM9WondOan6bJw 2019-05-24T00:00:00+02:00 Neal Gompa No osc19, 2480, Open Source A comparison of the two major RPM package managers In one corner, we have Zypper: the successor to the motley of package management options from Ximian and SuSE. Created after the merger of the Ximian and YaST package manager teams, it was a pioneer in using the SAT solver for package management and proved that it worked well at scale in a large and popular Linux distribution platform (SUSE Linux). It spawned the development of libsatsolver, which became libsolv. Considered by many to be the most advanced and fastest package manager, it is created a class of package managers all on its own. It is used in openSUSE, but is also available in Fedora and other RPM-based Linux distributions. In the other corner, we have DNF: the anointed successor to YUM (Yellowdog Updater, Modified). DNF (Dandified YUM) was forked from YUM to rework the internals to leverage libsolv and offer a saner, more maintainable API. Forged from the blood, sweat, and tears of many package manager developers from Red Hat and others, DNF is built with the lessons in mind from the last decade of software and systems management experiences. A new up and comer, it is used in Fedora, Mageia, OpenMandriva, Yocto, and others. It is also available in openSUSE. How do these two package managers compare? Are they more similar than different? Has DNF made YUM no longer a trash heap? Does ZYpp still rule the roost? This talk explores both package managers and compares them from a technical, usability, and ecosystem perspective. Who knows? Perhaps there are lessons to still be learned for evolving both package managers. In one corner, we have Zypper: the successor to the motley of package management options from Ximian and SuSE. Created after the merger of the Ximian and YaST package manager teams, it was a pioneer in using the SAT solver for package management and proved that it worked well at scale in a large and popular Linux distribution platform (SUSE Linux). It spawned the development of libsatsolver, which became libsolv. Considered by many to be the most advanced and fastest package manager, it is created a class of package managers all on its own. It is used in openSUSE, but is also available in Fedora and other RPM-based Linux distributions. In the other corner, we have DNF: the anointed successor to YUM (Yellowdog Updater, Modified). DNF (Dandified YUM) was forked from YUM to rework the internals to leverage libsolv and offer a saner, more maintainable API. Forged from the blood, sweat, and tears of many package manager developers from Red Hat and others, DNF is built with the lessons in mind from the last decade of software and systems management experiences. A new up and comer, it is used in Fedora, Mageia, OpenMandriva, Yocto, and others. It is also available in openSUSE. How do these two package managers compare? Are they more similar than different? Has DNF made YUM no longer a trash heap? Does ZYpp still rule the roost? This talk explores both package managers and compares them from a technical, usability, and ecosystem perspective. Who knows? Perhaps there are lessons to still be learned for evolving both package managers. about this event: https://c3voc.de 00:32:21 https://media.ccc.de/v/2429-eos-design-system In the past UX design was a commodity in the paid consumer world, where companies like Facebook, Google, Uber would invest millions on. Today the gap is closing. Enterprise and Open Source applications are in need of better UX too. On the other hand, many companies of all different sizes struggle with today's IT agendas: bleeding edge software, agile development, short time-to-market, etc., and this "new" (and really not so) kid on the block is not making it any easier for developers and designers to keep up: UX design. Companies struggling in this scenario will eventually suffer from a big level of inconsistency in their products portfolio, and sometimes even in one same product. Design Systems can help solve this problem, and a few more. Design Systems serve as a centralized source of information for UX, UI, and other brand-related guidelines that help not only developers find the UI element or component they need, but also designers to build faster prototypes while streamlining the collaboration between the two. But, building a Design System can take a very long time and be very expensive, this is why we're building EOS: an Open Source and customizable Design System. In this presentation, we will talk more about the problem Design Systems solve, how we are building EOS, and how it can be of great benefit to your company or project. More about EOS: http://eosdesignsystem.com In the past UX design was a commodity in the paid consumer world, where companies like Facebook, Google, Uber would invest millions on. Today the gap is closing. Enterprise and Open Source applications are in need of better UX too. On the other hand, many companies of all different sizes struggle with today's IT agendas: bleeding edge software, agile development, short time-to-market, etc., and this "new" (and really not so) kid on the block is not making it any easier for developers and designers to keep up: UX design. Companies struggling in this scenario will eventually suffer from a big level of inconsistency in their products portfolio, and sometimes even in one same product. Design Systems can help solve this problem, and a few more. Design Systems serve as a centralized source of information for UX, UI, and other brand-related guidelines that help not only developers find the UI element or component they need, but also designers to build faster prototypes while streamlining the collaboration between the two. But, building a Design System can take a very long time and be very expensive, this is why we're building EOS: an Open Source and customizable Design System. In this presentation, we will talk more about the problem Design Systems solve, how we are building EOS, and how it can be of great benefit to your company or project. More about EOS: http://eosdesignsystem.com about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2429-eng-EOS_Design_System_opus.opus?1558711503 7_nXG696JFYWmpcdiNjxjg 2019-05-24T00:00:00+02:00 csanchez@suse.de, Jesus Herman-Marina No osc19, 2429, Open Source The solution to bring good UX to all OSS In the past UX design was a commodity in the paid consumer world, where companies like Facebook, Google, Uber would invest millions on. Today the gap is closing. Enterprise and Open Source applications are in need of better UX too. On the other hand, many companies of all different sizes struggle with today's IT agendas: bleeding edge software, agile development, short time-to-market, etc., and this "new" (and really not so) kid on the block is not making it any easier for developers and designers to keep up: UX design. Companies struggling in this scenario will eventually suffer from a big level of inconsistency in their products portfolio, and sometimes even in one same product. Design Systems can help solve this problem, and a few more. Design Systems serve as a centralized source of information for UX, UI, and other brand-related guidelines that help not only developers find the UI element or component they need, but also designers to build faster prototypes while streamlining the collaboration between the two. But, building a Design System can take a very long time and be very expensive, this is why we're building EOS: an Open Source and customizable Design System. In this presentation, we will talk more about the problem Design Systems solve, how we are building EOS, and how it can be of great benefit to your company or project. More about EOS: http://eosdesignsystem.com In the past UX design was a commodity in the paid consumer world, where companies like Facebook, Google, Uber would invest millions on. Today the gap is closing. Enterprise and Open Source applications are in need of better UX too. On the other hand, many companies of all different sizes struggle with today's IT agendas: bleeding edge software, agile development, short time-to-market, etc., and this "new" (and really not so) kid on the block is not making it any easier for developers and designers to keep up: UX design. Companies struggling in this scenario will eventually suffer from a big level of inconsistency in their products portfolio, and sometimes even in one same product. Design Systems can help solve this problem, and a few more. Design Systems serve as a centralized source of information for UX, UI, and other brand-related guidelines that help not only developers find the UI element or component they need, but also designers to build faster prototypes while streamlining the collaboration between the two. But, building a Design System can take a very long time and be very expensive, this is why we're building EOS: an Open Source and customizable Design System. In this presentation, we will talk more about the problem Design Systems solve, how we are building EOS, and how it can be of great benefit to your company or project. More about EOS: http://eosdesignsystem.com about this event: https://c3voc.de 00:30:32 https://media.ccc.de/v/2522-yast-yet-another-suse-talk Presenter: Thomas Di Giacomo In this session we will first briefly describe how the openSUSE community and SUSE have been historically (well since Leap/Tumbleweed, not going back to the days before) collaborating together, e.g. Gnome and SUSE Linux Desktop, KDE and packagehub, then look at some of the more recent activities around MicroOS, container engines and tools, container networking such as Cilium, container management, etc. with respect to Kubic and SUSE CaaS Platform. As this is not only about a company and a community per se but a lot more primarily about people doing things, about contributors and developers, we’ll highlight a few specific example individuals in such a collaboration context, , and then share what we think are the aspects that work and ones where we could improve for both to benefit from. Presenter: Thomas Di Giacomo In this session we will first briefly describe how the openSUSE community and SUSE have been historically (well since Leap/Tumbleweed, not going back to the days before) collaborating together, e.g. Gnome and SUSE Linux Desktop, KDE and packagehub, then look at some of the more recent activities around MicroOS, container engines and tools, container networking such as Cilium, container management, etc. with respect to Kubic and SUSE CaaS Platform. As this is not only about a company and a community per se but a lot more primarily about people doing things, about contributors and developers, we’ll highlight a few specific example individuals in such a collaboration context, , and then share what we think are the aspects that work and ones where we could improve for both to benefit from. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2522-eng-YaST_-_Yet_another_SUSE_Talk_opus.opus?1558711353 las4wWdhvRQ8OBVwjCJf-w 2019-05-24T00:00:00+02:00 Thomas Di Giacomo No osc19, 2522, Keynote Or how are SUSE and the openSUSE community interacting together in 2019 Presenter: Thomas Di Giacomo In this session we will first briefly describe how the openSUSE community and SUSE have been historically (well since Leap/Tumbleweed, not going back to the days before) collaborating together, e.g. Gnome and SUSE Linux Desktop, KDE and packagehub, then look at some of the more recent activities around MicroOS, container engines and tools, container networking such as Cilium, container management, etc. with respect to Kubic and SUSE CaaS Platform. As this is not only about a company and a community per se but a lot more primarily about people doing things, about contributors and developers, we’ll highlight a few specific example individuals in such a collaboration context, , and then share what we think are the aspects that work and ones where we could improve for both to benefit from. Presenter: Thomas Di Giacomo In this session we will first briefly describe how the openSUSE community and SUSE have been historically (well since Leap/Tumbleweed, not going back to the days before) collaborating together, e.g. Gnome and SUSE Linux Desktop, KDE and packagehub, then look at some of the more recent activities around MicroOS, container engines and tools, container networking such as Cilium, container management, etc. with respect to Kubic and SUSE CaaS Platform. As this is not only about a company and a community per se but a lot more primarily about people doing things, about contributors and developers, we’ll highlight a few specific example individuals in such a collaboration context, , and then share what we think are the aspects that work and ones where we could improve for both to benefit from. about this event: https://c3voc.de 00:18:38 https://media.ccc.de/v/2534-building-containers-and-images-in-and-for-opensuse In this talk I explain how containers based on openSUSE Leap and Tumbleweed should be built and how the process for building and submitting official images works. In this talk I explain how containers based on openSUSE Leap and Tumbleweed should be built and how the process for building and submitting official images works. about this event: https://c3voc.de Fri, 24 May 2019 00:00:00 +0200 https://cdn.media.ccc.de/events/osc/2019/opus/osc19-2534-eng-Building_containers_and_images_in_and_for_openSUSE_opus.opus?1558711743 IvBZOa9uoXagwKyAqjiVkw 2019-05-24T00:00:00+02:00 favogt No osc19, 2534 In this talk I explain how containers based on openSUSE Leap and Tumbleweed should be built and how the process for building and submitting official images works. In this talk I explain how containers based on openSUSE Leap and Tumbleweed should be built and how the process for building and submitting official images works. about this event: https://c3voc.de 00:28:00 media.ccc.de / RSS 0.3.1 CCC media team media@c3voc.de CCC media team No CCC Congress Hacking Security Netzpolitik A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from osc19 as opus