Welcome to my presentation about OpenSUSE on the mainframe. I am Sarah Julia Krisch and I am a German DevOps consultant at Accenture and contribute to OpenSUSE since around nine years. Since one year I am a member of the S390X port at OpenSUSE and I am a member of the release engineering team. Many of you won't know something about mainframes, therefore I want to give you a small introduction into mainframes and the architecture S390X, what is the history and where it comes from. Then we are coming to the topic OpenSUSE, our two distributions OpenSUSE Tumbleweed and OpenSUSE Leap. Then what is new there, which features are new and which relationships do we have got during our development life cycle and in general from that we are coming to the OpenSUSE way and our new project about public container images for IBM C and at the end I will tell you something about OpenSUSE container platforms and our projects there. Mainframes are large high performance computer systems, many people are calling them also big Indians. If you are looking into upstream projects and something isn't enabled for mainframes then there is an issue that it would not be supported for big Indian systems as an example. These systems are used mostly for mission critical applications, so users are mostly banks and global players and you can run thousands of VMs on such a system. On the right side you can see a Linux 1 system that is an IBM system with a special configuration for Linux that exists also for Linux systems and without a special configuration. These systems are called IBM C1 and these systems together exist since 1964. As I said before, the mainframe architecture S390X is available for IBM C and Linux 1. The first IBM mainframe system had the name ES9000 and came in the year 1990 to the market. Afterwards there was the introduction of IBM 3090 in the middle of 1990 that was the 32-bit architecture and you call it system S390 and from that there was the name expanded to S390X for the 64-bit architecture in 2000 years and these architectures are available also for COS, CVSE, CTPF and the virtual machine system CVM of IBM besides of C-Linux. What is C-Linux? C-Linux is Linux in general for IBM C and there are multiple runnable Linux distributions on IBM C and Linux 1. The most important Linux distributions for IBM are via Enterprise Linux distributions Rails, Less and Ubuntu but were also community maintained Linux distributions for IBM C and Linux 1. The most important and since a long time community supported Linux distributions are Fedora, OpenSUSE and Debian and since around one year you can use also Gen2 Linux and Alpine Linux. Alpine Linux is mostly used for container systems and the other ones are mostly community driven and I will tell you a little bit more about OpenSUSE today. From that we are coming to OpenSUSE Tumbleweed. OpenSUSE Tumbleweed is our rolling release of OpenSUSE. It is recommended for development and really experienced users because you can receive latest packages via upstream development. It is tested with OpenQA. Many of our users are asking where is our rolling release. I don't receive any breaks or something else because it is so well tested. Yes, we are testing it with OpenQA automatically before the releases and OpenSUSE Tumbleweed is the base for OpenSUSE Leap and Sousi Linux Enterprise Server. OpenSUSE Tumbleweed exists also for S390X. The first Tumbleweed snapshot was in the year 2016, afterwards there was a small break because of missing resources and last year I joined this team and since 2020 we have got mostly weekly snapshots since this time because we have got more activity in our team. Our repositories are marked with C-Systems at the end where you can download our ISO images from download.openSUSE.org and the special architectures as ARM, C-Systems and everything else are ports of the X86 architecture and you are receiving your special packages forwarded to the ports. So our identicator is C-Systems so you are receiving all of our repositories, OpenSUSE software debug with default repo and everything else from these URLs. Besides of our rolling release we provide also our stable release where this has got the name OpenSUSE Leap. A stable release is yearly released and it is recommended for servers and desktops. These are our last version 15.3, our binaries are compatible with Sless, we are using the same packages as SUSE for our OpenSUSE Leap system and it is tested with OpenQA and our developers and users additionally. We provide yearly releases at the beginning of every OpenSUSE Leap release. It is equal to tumbleweed more rolling but with more stabilization and everything else it is more and more equal to a default stable release. OpenSUSE Leap 15.3 for S390X is our first stable release of OpenSUSE Leap for S390X. Since this time we have got the possibility to use the Linux 1 community cloud with a change from Sless to OpenSUSE because IBM officially supports only the enterprise Linux distributions and in our case because of the binary compatibility we can upgrade these VMs to OpenSUSE. So if you want to use for your community contributions or for upstream development a community Linux distributions you should choose Sless and upgrade to OpenSUSE when. The next planned release of OpenSUSE Leap is June 2022. The repositories for OpenSUSE Leap are more equal to our tumbleweed distribution. In this case you can find all architectures in one repository so you don't specify the C systems in this case all user images are added to one repo in this case. From our stories about our distributions we are coming to factory as the foundation for our development cycle here you can see the name submission that is equivalent to a commit to GitHub only in our OpenBuild service tool so you can receive upstream contributions as packages into our OpenBuild service then it will be reviewed automatically if the contributor is submitting it then we have got an integrated CI CD pipeline into our OpenBuild service and we have got additional manual reviews then it is all coming into factory our development base where all will be merged together and we create our user images based on that that all will come into QA or OpenQA system where our installation and everything will be tested is all working and if all tests are passed with a big requirement with these required packages then we are releasing OpenSUSE tumbleweed. OpenSUSE Leap has got something between QA and tumbleweed in this case instead of tumbleweed you have got additional users and testers there so we are testing and expanding it and then we release OpenSUSE Leap in this case. I told you we are using the same package foundation as the Linux Enterprise server for OpenSUSE Leap here you can see how we are doing that I told you about the development life cycle with OpenSUSE factory how we are receiving our tumbleweed releases and here you can see both the Linux distributions are forks of OpenSUSE tumbleweed on this way. We are using the same core packages we are receiving core packages from through the Linux Enterprise for OpenSUSE Leap the difference is the brand thing and the configuration then so we have got separate packages for the OpenSUSE branding with user branding and the special configurations and then we provide the through the Linux Enterprise the backpots packages so that you can use community packages on through the Linux Enterprise on this way we are collaborating together with SUSE but that is not all I have referenced the open source way here because VAT is the foundation for most communities and in general the Linux distributions Red Hat has created a guide for that you can find that on the opensourceway.org thank you who to cast and awarded some presentations before me here is a given a presentation about with OpenSUSE way 2.0 if you didn't see that I give you a small overview about VAT what it is it is the way to create and collaborate with in communities and for that you have to understand the core concepts of open source communities so you are collaborating with communities in our case I have referenced an example relationship between SUSE and OpenSUSE but at OpenSUSE we are collaborating not only with our main sponsor we are collaborating also with our partner communities here is the community collaboration with the open source way on top you can see the free enterprise distributions and of course all are collaborating a little bit they are in our case really close with their own community distributions we are sharing packages we are working together many employees of our main sponsors are contributing to us so Red Hat is collaborating with Fedora of course the same as SUSE is collaborating with OpenSUSE Ubuntu is based on Debian so VAT is really equal but there are small relationships between OpenSUSE and Fedora the same as between OpenSUSE and Debian VAT is because we have got multiple contributors contributing to different community distributions in parallel we have we are using the same foundation we are using the Linux kernel we are using base packages everywhere equal why shouldn't we make it possible that our contributors can contribute to multiple Linux distributions you can have a focus on a special package or you can say I want to contribute to a visc architecture but to multiple communities visc community contributors are called cross community members so you are a member in multiple community distributions I said we are using the Linux kernel as an example we are using KVM on the left side for upstream development you can see the glue tools or on the right side you can see the GitHub logo as an example for all the important GitHub upstream projects who are integrated into our community distributions these community distributions are also called upstream distributions so we are integrating the latest as software into our community distributions and the enterprise distributions are based on us from that we are coming a little bit to my company I am working for two digits within Accenture and Accenture has got the 360 degree values so we have got the goal of sustainability and we at two digits are receiving until eight hours per week for open source contributions and other activities usable for our customers and general purpose our goal with open source contributions is that you can reuse open source software and with that we want to provide our customers with freedom of choice with multiple platforms and multiple software on this way we can expand also our partner for you that is close to the open source way why shouldn't we collaborate with others and then we have got other benefits you can create innovation with open source development and we collaborate with communities and expand our network on this way we are using the linux one community cloud as a development environment thank you for IBM for sponsoring that oil there are multiple access types for the linux one community cloud IBM provides free access with 120 days for a single for single open source contributors these systems are based on slas or ubuntu but if you want to receive long-term access there is a way to receive the VMs for a longer time we at open source have received seven long term access VMs so we can distribute it in our team that we can work continuously on our VMs we are using these VMs for our open source day at the end of the week and on this way we can use it for education and hackathons and if you are interested for such a long-term access come speak with elisa bett from IBM and if you are writing as an open source project to this at ibm.com you can receive also such systems and you can upgrade it to open source perhaps or using it in general for the development stuff from that we are coming to our purpose what we are doing in this linux one community cloud at the moment we are seven employees at Accenture and we want to enable container platforms for ibmc the main problem was that there was only a small number of public container images for s390x on docker hub and the container registries by redhead and ibm are not public so we thought about the creation of container images via open source as a first step therefore i created an overview for containerization with open source way we don't want to do that only for open zoosl we want to have that for all so all running linux distributions and ibmc should be supported at the end so that you can run multiple container platforms on on this linux distributions and you can use public container images when most people who are using containers know docker hub yes we want to publish our containers also on docker hub at the end but we are developing based on the registry dot open zoosl org and registry fedora project dot org first we have started with registry dot open zoosl org so you are receiving open zoosl based images from registry dot open zoosl org and these container images should be runnable on open shift kubernetes in general okd mini cube oh our own kubernetes platform open zoosl cubic and rancher what is registry dot open zoosl org you have seen it besides of docker hub before registry dot open zoosl org is the container registry by open zoosl we are building multi-ice container images there so you can use it for x86 s390 x arm power pc and other architectures these container images are built with our open build service continuously based on open zoosl tumbleweed we plan to do that also with open zoosl leap but it is an easy step to expand it because our open build service gives us the possibility to build that all automatically without many overheads our created images until now for s390 x are firstly with a web server things httpd engine x and the application server tomcat besides of that i have added on top open aid up and nfs nfs server as a foundation then you want to will be able to compile and run your applications which was written in a specific language for that we have created a container images with golang open jdk and php8 together with engine x but i have added a line with databases so you can choose between maria db maria db client and post sql as databases in our first container images and then we are also a container images available with postfix ha proxy rmt server samba script and hugo at the moment we plan to create also some images based on fedora for that i thought about the the usage of fedora for redhead specific open source projects so you will find as an example wildfly based on fedora in the future from us i told you so much about the open build service and that we are using it for creation of container images the open build service is a sub project of opensusa and that's our tool of choice for the creation of either images packages and container images automatically the open build service has got an integrated cicd pipeline so the packages and container images are only published if the builds are really succeeded the same counts for either images but all is running also through our automated tests with a open qa and if you are interested for our tool how to build with that and everything else you can receive a nice overview via build.opensusa.org which is our own open build service but you can also install it for your own which is an open source project from opensusa so you can receive all the software for free as open source under openbuildservice.org the same counts for the documentation that is available and you can use it and test it our supported genox distributions in obs that's exactly the open source way again we don't support only opensusa and slas we are supporting multiple genox distributions here you can see we provide rails less and ubuntu then you can build for fedora opensusa and debian of course but we provide also univention, raspian, centOS, centOS stream, magaya, ice linux and scientific linux besides of that we have got also special installation types or distributions you can also build for ibm power kvm and app image what are the benefits of container images built with obs one i told you we are creating that continuously so you are receiving the latest package versions based on the linux distributions and then in your container registry released so you are receiving the latest versions and they are only released if they have passed the CI CD pipeline you can publish to all public container registry with that if you are looking to docker hub here to open through the tunnel with container image as an example you can see that is built with the open build service and published directly to docker hub this we are doing the same with our own container registry registry dot opensusa org so you can find the latest container images there and if we have tested it enough and we are saying we want to have it also in docker hub then we can add this registry and it will push automatically the updates are coming automated together with open through the tumbleweed so if tumbleweed is passing with our tests all will be released i told you before what our plan is with the architecture and the open source way with containerization for all linux distributions here you can see how we plan that with our open source and community distributions together on the right side you can see the open build service and we publish containers based on the community distributions to docker hub and registry dot opensusa org and then you can use it on all community distributions with multiple container platform span what is the future of community distributions on the mainframe until now opensusa fedora and debian are running all here on s390x and these community distributions can give access to open source container images at the end you can use all three kubernetes distributions based on mainframes when and on this way color variation is also possible together from this topic we spoke a lot here about open soose and the collaboration things and container images our goal is also to support multiple container platforms on ibmc and that should be also open source let's come back to this picture you can see yes kubernetes logo you can install kubernetes manually on your linux distribution of course then there's the logo of our own opensusa project opensusa cubic okd which is the open source container platform from redhead you can run it on fedora also mini cube and rancher which is also available for as an open source and free version from soose and it is supporting most linux distributions so what is opensusa cubic and what do we plan where that is the free container platform by opensusa and uh it has been founded in for may 2017 the start was of course for x86 now i want to release it also for s390x i plan that in around one month the base operating system is open through the micro os open through the micro os is a minimal operating system based on opensusa tumbleweed at the moment soose is providing something equal to that for enterprise customers and is releasing through the linux enterprise micro and so you can see equal to redhead with the redhead core os and fedora core os will provide something equal with the name opensusa micro os our default container runtime in opensusa cubic is potman it is possible to use our container runtimes there but the default container runtime which is pre-installed is potman you can find this project under cubic dot opensusa arc when we are coming to rancher here you can is see that is an open source container platform you can use it for free the same as enterprise container platform and it is runnable on most linux distributions here you can see a list they don't support only slas they are supporting real oracle linux opensusa and center as besides of soose linux enterprise server we have tested it with opensusa leap and tumbleweed on s390x now so you can use the free version before the release at the end of the year with soose linux enterprise server together for s390x i told you now a lot about opensusa and our plans here is a little bit some information about the s390x part and how you can speak with me and my team we are the team which is responsible for the opensusa development for ipmc and linux one you can see we are doing some more stuff because of our containerization project i am responsible for all opensusa distributions and stuff based on ipmc and linux one as a member of the release engineering team you can find most information about our team in our wiki under en opensusa arc c systems i told you about the open build system we have got our own project we have with all packages iso images and container images so you can find us under factory c systems i told you we are based on factory and we have got the c systems port where therefore that is the reason that we have got the opensusa factory c systems name for our project we have got also a mailing list c systems at lists dot opensusa arc you can ask questions where you can speak with us where so you are free to come in contact with us we have got also an irc channel on libera chat you can speak with us under opensusa c systems please welcome to us and now we are coming to q and a ask your questions


Hey there, Polycasters. Rob here, interrupting your regularly scheduled program to bring you this. It's the Chrome Developer Summit, and it's going on right now, unless you're watching this in the future. But either way, all of the content is available up on the Chrome Developer's YouTube channel. We've got talks from Paul Lewis and Paul Irish on building performant web apps. Alice Boxhall talks about accessibility and Taylor Savage and yours truly about building progressive web apps using Polymer. So definitely go check that out, and I'll catch you back here next week for a brand new episode of Polycast.