May 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Generic / Repo-specific READMEs at GitHub
by Lukas Ocilka 23 Feb '16

23 Feb '16

Hi, When Christopher was in Prague, a few of us had a brainstorming about the need of having devel-documentation placed directly in a Yast/libstorage/linuxrc repository. There are no doubts that it's one of the most important parts of projects hosted at GitHub. All their howtos mention "create README[.md]" as the very first step. In fact, we'll have new hires in the team and in such situations, good documentation is one of the most important parts. Good documentation goes from very high level to lower and lower level. We have already summarized that in Yast Team Challenges, but the summary doesn't belong to this document as it's too detailed. That's why I'm putting it here as a WIP item and deleting it from that document: --- cut --- The README should at least describe the steps needed for maintenance (for a person without expert knowledge in the area) including: * What is the project good for - what does it actually do (and how), what it cannot do (unsupported scenarios), limitations * Links to the documentation, high level and low level descriptions (e.g. RFC, wikipedia articles, man pages, project documentation, openSUSE wiki), terminology * How to fetch the source code (if something outside Git is needed it should be mentioned) * What prerequisites are needed to build the sources (external libraries, gems, scripts, …) * How to build the sources (make/rake commands…) * How to setup a testing environment (e.g. iSCSI target for iSCSI client) * How to run the code to test a change (esp. needed for non trivial projects like linuxrc) * How to run automated tests * How to build a package for submission * How to submit the package (if it needs some manual steps) * Troubleshooting (how to solve typical problems) The README should be reasonably short, if some section is too long it should be moved to a separate document (or to GitHub wiki) and linked. --- cut --- The project consists of - Taking a decision where to go - How to get there - Implementing this important documentation Those two who, according to my knowledge, were working on this were Ladislav and Christopher, but there were not the only ones and a pilot project for READMEs has been done a few months ago by Martin. It's still not finished, but moving forward. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 3

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 29 May '15

29 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-bootloader: - ensure libstorage runs in 'normal' mode so it really returns us the m… (7 days) https://github.com/yast/yast-bootloader/pull/235 Pending requests in repository yast-core: - fix more compilation warnings (14 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (5 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (38 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (38 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (8 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (8 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (8 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (8 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (63 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (8 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 28 May '15

28 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-bootloader: - ensure libstorage runs in 'normal' mode so it really returns us the m… (6 days) https://github.com/yast/yast-bootloader/pull/235 Pending requests in repository yast-core: - fix more compilation warnings (13 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-devtools: - use m4sh-script-dir obsoleting pre-generation of acinclude.m4 (4 days) https://github.com/yast/yast-devtools/pull/89 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (37 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (37 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (7 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (7 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (7 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (7 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (62 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (7 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Some recipes for running jobs in openQA
by Ancor Gonzalez Sosa 27 May '15

27 May '15

Before I go on vacation... Most likely NOT all parameters are needed in all cases. These are just examples. 1) Running an installation to generate an hard disk image (to be used afterward for running application tests, for example). Key param PUBLISH_HDD_1 /usr/share/openqa/script/client jobs post ARCH=x86_64 BACKEND=qemu BUILD=132 DISTRI=opensuse DESKTOP=kde DVD=1 FLAVOR=DVD FULLURL=1 ISO=openSUSE-13.2-DVD-x86_64.iso TEST=generate-kde-hdd VERSION=13.2 PUBLISH_HDD_1=openSUSE-13.2-kde.hdd INSTALLONLY=1 2) Using the generated hard disk image to run our new distri (which only includes our own application tests).Key params HDD_1 and DISTRI=yast-modules /usr/share/openqa/script/client jobs post ARCH=x86_64 BACKEND=qemu BUILD=132 DISTRI=yast-modules DESKTOP=kde TEST=yast-modules-experiment VERSION=13.2 HDD_1=openSUSE-13.2-kde.hdd 3) Same that (2) but with an additional step to install all the updates from YaST:Head (I don't promise it will work). Key param YAST_HEAD /usr/share/openqa/script/client jobs post ARCH=x86_64 BACKEND=qemu BUILD=132 DISTRI=yast-modules DESKTOP=kde TEST=yast-modules-experiment VERSION=13.2 HDD_1=openSUSE-13.2-kde.hdd YAST_HEAD=1 4) Loading a DUD before performing the installation (with the changes mentioned in my previous mail and still not merged into upstream openQA). Key params DUD, ISO_1 and ADDONS /usr/share/openqa/script/client jobs post ARCH=x86_64 BACKEND=qemu BUILD=0951 DISTRI=sle MACHINE=64bit QEMUCPU=qemu64 VERSION=12 FLAVOR=Server-DVD ISO=SLE-12-Server-DVD-x86_64-GM-DVD1.iso DUD=iso ISO_1=dud-sle12-whatever.iso ADDONS=1 TEST=whatever All the examples SHOULD work with all distros (sle, 13.2, TW) and all tests. Just take the relevant params and combine them with your our needs. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] YaST and openQA
by Ancor Gonzalez Sosa 27 May '15

27 May '15

Cross-posting. This should be interesting to both sides. At the end of the mail there is a small glossary, since I assume some readers will not be familiar with some of the used terms. Since we (the YaST team) plan to implement the writing openQA tests into our regular development workflow, Imo and me have spent the last couples of days playing with openQA and our current development tools. We are not interested in the iso-oriented approach used at openqa.suse.de and openqa.opensuse.org. We want to run single jobs for the code we are developing right now. There are 2 kind of jobs we want to run: testing the installation and testing a YaST module (like any other application). 1) Testing the installation If we introduce these changes (or very similar ones) in openQA[1], we will be able to generate a DUD, submit it to the openQA host and execute a single job to run the installation including our changes. We already applied the process successfully[2] and we already have rake tasks that automate the whole process. [1] https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/460 https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/461 https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/4 [2] https://dhcp78.suse.cz/tests/12 https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/462 2) Testing the applications The DUD approach proved to be very useful for installation and we think can be applied to applications as well. I already have an special distri that takes an already installed system, boots it, applies all the updates from the YaST:Head repo and then run a list of application tests. My plan is to modify it to support installing packages from an uploaded DUD, as the installation already does. We could share the needles repositories of openSUSE/SLE and have all the application tests in a specific directory, so the mechanism for sharing code and needles will be very similar to the one already used for SLE and openSUSE. Most of the rake tasks would be completely reused. Generating and refreshing the installed systems (an asset) used as starting point for these jobs can be easily automated thanks to PUBLISH_HDD, as you can see here[3]. The test proving that the new distri works were lost in a recent hard disk accident, but they will be available today again [3] https://dhcp78.suse.cz/tests/1 So we already have all the pieces and our first installation test (test module to be precise) for a functionality still on development. Let's open the discussion! Cheers. And now the glossary: DUD - ftp://ftp.suse.com/pub/people/hvogel/Update-Media-HOWTO/Update-Media-HOWTO.… The most convenient way to deliver updates to the system (including the installer) in a file or cd image. asset - The elements used to feed the openQA jobs. Can be an ISO, a hard disk image or a repository. They can be registered manually (like our rake tasks do) or generated by another job (like in [3] that generates the installed system to be used in other tests). rake - https://github.com/ruby/rake The tool the YaST team uses to automate the development work. distri - A set of tests in openQA. It defines the steps (a.k.a. test modules), in which order the steps are run and how to react to some environment variables. We have a separate distri for openSUSE and SLE, although they share the definition of the steps (modules). -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 11

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 27 May '15

27 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-bootloader: - ensure libstorage runs in 'normal' mode so it really returns us the m… (5 days) https://github.com/yast/yast-bootloader/pull/235 Pending requests in repository yast-core: - fix more compilation warnings (12 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (36 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (36 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-storage: - fix for bsc#919980 (6 days) https://github.com/yast/yast-storage/pull/123 Pending requests in repository yast-support: - Remove ANSI escape codes (bnc#921233) (6 days) https://github.com/yast/yast-support/pull/10 Pending requests in repository yast-theme: - Add icons for MATE pattern (6 days) https://github.com/yast/yast-theme/pull/55 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (6 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (61 days) https://github.com/yast/yast-ruby-bindings/pull/140 Pending requests in repository yast-docker: - Start making this a gem (6 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] New ruby way to use extension in inst-sys
by Josef Reidinger 26 May '15

26 May '15

Hi, I would like to point you to new functionality, when you need to use extension in inst-sys. I write new wrapper, that allow using block form for loading such extension and doing automatic unloading after block. Example of usage: InstExtensionImage.with_extension("snapper") do WFM.Execute(path(".local.bash"), "snapper magic") end Thanks Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 26 May '15

26 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - fix more compilation warnings (11 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (35 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (35 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (60 days) https://github.com/yast/yast-ruby-bindings/pull/140 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 25 May '15

25 May '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-core: - fix more compilation warnings (10 days) https://github.com/yast/yast-core/pull/101 Pending requests in repository yast-network: - Autoyast: do not overwrite firewall settings (34 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (34 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-ruby-bindings: - [Do not merge] First experiment to implement rails-like core extensions (59 days) https://github.com/yast/yast-ruby-bindings/pull/140 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0