[opensuse-zsystems] Contributions by an IBMer
Hello together, I am an IBM employee (Linux Developer) at IBM since this month. This week I have received the approval to contribute to openSUSE Packaging for Z. Additionally, I am open to communicate Z specific topics to our company for our team. Before I had studied Computer Science in Nuremberg and wrote my Bachelor Thesis at IBM. I will switch from the Translation Team to the Z Systems Team at openSUSE now. I was allowed to see many failed packages for Tumbleweed. So I can see how I can help you here. Best regards, Sarah -- To unsubscribe, e-mail: opensuse-zsystems+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-zsystems+owner@opensuse.org
Hi Sarah, I am Sergio, working as a QA engineer at SUSE. It is nice to have more people interested in openSUSE for IBM Z. I am helping from the testing side by enabling openQA tests. See https://openqa.opensuse.org/group_overview/34 I managed to enable two scenarios but we are having technical problems at the moment with the machine setup for the tests and they are showing only red. I expect to keep enabling the same scenarios that we have for SLE as soon as the testing machines are fixed. I have a lot of knowledge gaps in how the product is built, but just in case you need an overview, here is what I know. Tumbleweed installation for x86 is built in https://build.opensuse.org/project/show/openSUSE:Factory, but Tumbleweed installation for s390 is done in the sub project https://build.opensuse.org/project/show/openSUSE:Factory:zSystems And the build sent to openQA for testing is in https://build.opensuse.org/project/show/openSUSE:Factory:zSystems:ToTes t So, if you want to download and use the last Tumbleweed snapshot for s390, you can find it in https://build.opensuse.org/package/binaries/openSUSE:Factory:zSystems:T oTest/000product:openSUSE-dvd5-dvd-s390x/images A lot of packages are inherited from the x86 project, so when you try to fix an inherited package, the submit request has to be done to the x86 (factory) package and the changes will get forwarded to the zsystems project Some s390 specific changes are are made in “OBS package links”, so that those changes are not made in the x86 version. (But, I think that Berthold, someone who is also fixing packages for s390, wanted to unify the changes so that package links are not needed). If you have any question, do not hesitate to ask. It is exciting to see how this small group of mainframe enthusiasts (mainframers?) starts growing. Kind Regards and have a lot of fun! -- Sergio Lindo Mansilla Software developer with DevOps tendencies Portfolio: http://binary-sequence.github.com/
Hi Sarah, I have an interest in openSUSE on SystemZ also (together with RISC-V), let me know if I can be of any help to you, while my knowledge (and access) to SystemZ systems is limited, I do have extensive knowledge of RPM packaging. I think it is important for us in a long-run, if we introduce any sensible patches to fix SystemZ builds to upstream them to reduce the maintanance burden on us in the future.
Hi Mark, nice that you want to join our team. Firstly, we are working on it to get our existing tests on the mainframe running. We can not work without them. Many builds during packaging are failing at the moment. We are happy about every support in packaging: https://build.opensuse.org/project/show/openSUSE:Factory:zSystems Before fixing, look whether x86 is affected, too. If so, then submit to the regular Factory. We will announce our working openQA for s390x here. Because of the missing mainframe knowledge. There are some online courses about IBM mainframes. They don't tell you a lot about Linux on the mainframe. But they are a good introduction. - https://www.coursera.org/learn/introduction-enterprise-computing But I don't see that as a requirement for s390x packaging. Best regards, Sarah
Gesendet: Sonntag, 15. November 2020 um 17:27 Uhr Von: "Mark Stopka" <mstopka@opensuse.org> An: zsystems@lists.opensuse.org Betreff: [opensuse-zsystems] Re: Contributions by an IBMer
Hi Sarah, I have an interest in openSUSE on SystemZ also (together with RISC-V), let me know if I can be of any help to you, while my knowledge (and access) to SystemZ systems is limited, I do have extensive knowledge of RPM packaging.
I think it is important for us in a long-run, if we introduce any sensible patches to fix SystemZ builds to upstream them to reduce the maintanance burden on us in the future. _______________________________________________ openSUSE Z Systems mailing list -- zsystems@lists.opensuse.org To unsubscribe, email zsystems-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org
Hi, thanks for your warm welcome, I am looking into that, I am going to start with packages I am using / know something about (bird roudint at this point), I am glad you are going to introduce OpenQA to s390x images, that should really help! When I referred to limited knowledge of mainframes / s390x I meant Linux z/VM or LinuxONE :-), mainframes as such running zOS are a whole different can of worms (fun fact, I almost became a "mainframe guy" in 2010 :-) ), so I was more like referring to that I will have to build everything in Qemu s390x emulation environment, which is obviously slow. Anyhow, can someone add my account "m4r3k" between maintainers in the project so we can avoid unnecessary forking? In addition if you see any Haskell packages failing, feel free to throw them my way... -- Best regards / S pozdravem, BSc. Mark Stopka, BBA Managing Partner (at) PERLUR Group mobile: +420 704 373 561 website: www.perlur.cloud On Mon, Nov 16, 2020 at 8:16 AM Sarah Julia Kriesch <ada.lovelace@gmx.de> wrote:
Hi Mark,
nice that you want to join our team. Firstly, we are working on it to get our existing tests on the mainframe running. We can not work without them. Many builds during packaging are failing at the moment. We are happy about every support in packaging: https://build.opensuse.org/project/show/openSUSE:Factory:zSystems
Before fixing, look whether x86 is affected, too. If so, then submit to the regular Factory. We will announce our working openQA for s390x here.
Because of the missing mainframe knowledge. There are some online courses about IBM mainframes. They don't tell you a lot about Linux on the mainframe. But they are a good introduction. - https://www.coursera.org/learn/introduction-enterprise-computing
But I don't see that as a requirement for s390x packaging.
Best regards, Sarah
Gesendet: Sonntag, 15. November 2020 um 17:27 Uhr Von: "Mark Stopka" <mstopka@opensuse.org> An: zsystems@lists.opensuse.org Betreff: [opensuse-zsystems] Re: Contributions by an IBMer
Hi Sarah, I have an interest in openSUSE on SystemZ also (together with RISC-V), let me know if I can be of any help to you, while my knowledge (and access) to SystemZ systems is limited, I do have extensive knowledge of RPM packaging.
I think it is important for us in a long-run, if we introduce any sensible patches to fix SystemZ builds to upstream them to reduce the maintanance burden on us in the future. _______________________________________________ openSUSE Z Systems mailing list -- zsystems@lists.opensuse.org To unsubscribe, email zsystems-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org
Hi, I think I found a patch, https://gitlab.nic.cz/labs/bird/-/commit/2928c5bcc7c3caaeb6de34a84ca63de9a12... however when I try to verify: openSUSE:Factory:zSystems/bird> osc build --vm-type=qemu s390x I receive an error from the build system: [ 78s] [151/151] keeping gdb-9.2-3.3 [ 78s] now finalizing build dir... [ 81s] RTNETLINK answers: File exists [ 81s] RTNETLINK answers: File exists [ 87s] /.build/build.dist: No such file or directory [ 91s] [ 89.773069] sysrq: Power Off [ 91s] [ 89.785321] reboot: Power down Anyone got s390x packages building in Qemu using OSC? -- Best regards / S pozdravem, BSc. Mark Stopka, BBA Managing Partner (at) PERLUR Group mobile: +420 704 373 561 website: www.perlur.cloud On Mon, Nov 16, 2020 at 1:04 PM Mark Stopka <mstopka@opensuse.org> wrote:
Hi, thanks for your warm welcome, I am looking into that, I am going to start with packages I am using / know something about (bird roudint at this point), I am glad you are going to introduce OpenQA to s390x images, that should really help!
When I referred to limited knowledge of mainframes / s390x I meant Linux z/VM or LinuxONE :-), mainframes as such running zOS are a whole different can of worms (fun fact, I almost became a "mainframe guy" in 2010 :-) ), so I was more like referring to that I will have to build everything in Qemu s390x emulation environment, which is obviously slow.
Anyhow, can someone add my account "m4r3k" between maintainers in the project so we can avoid unnecessary forking? In addition if you see any Haskell packages failing, feel free to throw them my way... -- Best regards / S pozdravem, BSc. Mark Stopka, BBA Managing Partner (at) PERLUR Group
mobile: +420 704 373 561 website: www.perlur.cloud
On Mon, Nov 16, 2020 at 8:16 AM Sarah Julia Kriesch <ada.lovelace@gmx.de> wrote:
Hi Mark,
nice that you want to join our team. Firstly, we are working on it to get our existing tests on the mainframe running. We can not work without them. Many builds during packaging are failing at the moment. We are happy about every support in packaging: https://build.opensuse.org/project/show/openSUSE:Factory:zSystems
Before fixing, look whether x86 is affected, too. If so, then submit to the regular Factory. We will announce our working openQA for s390x here.
Because of the missing mainframe knowledge. There are some online courses about IBM mainframes. They don't tell you a lot about Linux on the mainframe. But they are a good introduction. - https://www.coursera.org/learn/introduction-enterprise-computing
But I don't see that as a requirement for s390x packaging.
Best regards, Sarah
Gesendet: Sonntag, 15. November 2020 um 17:27 Uhr Von: "Mark Stopka" <mstopka@opensuse.org> An: zsystems@lists.opensuse.org Betreff: [opensuse-zsystems] Re: Contributions by an IBMer
Hi Sarah, I have an interest in openSUSE on SystemZ also (together with RISC-V), let me know if I can be of any help to you, while my knowledge (and access) to SystemZ systems is limited, I do have extensive knowledge of RPM packaging.
I think it is important for us in a long-run, if we introduce any sensible patches to fix SystemZ builds to upstream them to reduce the maintanance burden on us in the future. _______________________________________________ openSUSE Z Systems mailing list -- zsystems@lists.opensuse.org To unsubscribe, email zsystems-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org
On 11/16/20 7:50 AM, Mark Stopka wrote:
Anyone got s390x packages building in Qemu using OSC?
No, because there's never been a need. Just branch from openSUSE:Factory:zSystems and test your update in your home:branch:whatever project. It will be a lot faster. Mark Post
On 11/16/20 2:15 AM, Sarah Julia Kriesch wrote:
Before fixing, look whether x86 is affected, too. If so, then submit to the regular Factory.
Whether x86_64 is affected or not, please verify that whatever fix you apply doesn't break other architectures, and then gets sent to openSUSE:Factory, not openSUSE:Factory:zSystems. We created openSUSE:Factory:zSystems for two reasons: 1. openSUSE:Factory doesn't build against s390x 2. For packages that might require major hacking before being submitted to openSUSE:Factory. Rather than trying to do local builds using qemu, just do an "osc branch openSUSE:Factory:zSystems" for the package and let the mainframe build workers do the build. Using qemu for that might take forever. Mark Post
Hi Mark, bird is now fixed[1], I have submitted my patch network/bird which is a devel package for Factory, from where it should automatically move to Factory as part of daily batch jobs, for the future I will use your proposed workflow, which I think would would the same way in the end... Thanks for all the feedback! https://build.opensuse.org/request/show/848877?notification_id=23896322 -- Best regards / S pozdravem, BSc. Mark Stopka, BBA Managing Partner (at) PERLUR Group mobile: +420 704 373 561 website: www.perlur.cloud On Mon, Nov 16, 2020 at 4:10 PM Mark Post <mpost@suse.com> wrote:
Before fixing, look whether x86 is affected, too. If so, then submit to
On 11/16/20 2:15 AM, Sarah Julia Kriesch wrote: the regular Factory.
Whether x86_64 is affected or not, please verify that whatever fix you apply doesn't break other architectures, and then gets sent to openSUSE:Factory, not openSUSE:Factory:zSystems. We created openSUSE:Factory:zSystems for two reasons: 1. openSUSE:Factory doesn't build against s390x 2. For packages that might require major hacking before being submitted to openSUSE:Factory.
Rather than trying to do local builds using qemu, just do an "osc branch openSUSE:Factory:zSystems" for the package and let the mainframe build workers do the build. Using qemu for that might take forever.
Mark Post _______________________________________________ openSUSE Z Systems mailing list -- zsystems@lists.opensuse.org To unsubscribe, email zsystems-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org
participants (4)
-
Mark Post -
Mark Stopka -
Sarah Julia Kriesch -
Sergio