YaST Development October 2020

yast-devel@lists.opensuse.org

8 participants
15 discussions

[yast-devel] Innovation time: A repository with AutoYaST XML profiles (PoC )

by Ladislav Slezak

Hi all! I'm implementing some new AutoYaST feature and I found out that it's not easy to test the AutoYaST functionality. 1. Even for testing a trivial scenario you have to write your own XML file. If you do not have much experience with AutoYaST you have to read the documentation, search the internet, etc... Cloning your current system helps a bit but usually the cloned profile contains too many options so you still need to polish it a bit... 2. When you have your profile ready you have to host it at some HTTP/FTP/NFS/... server so AutoYaST can use it for installation. I usually run simple "ruby -run -ehttpd" command to have a web server quickly, but that's quite tricky for people not familiar with Ruby. My idea is to have some repository with example XML profiles which would be publicly available and ready for instant use. We already have some XML files in the autoyast-profiles-test Git repository but writing something like autoyast=https://raw.githubusercontent.com/yast/autoyast-profiles-test/mast… on boot command line is a real pain. We could use some URL shortening service but I do not like that much. Shortened URLs do not look nice and it's not obvious where they point to (security). I'd like to have some nice URLs... So my proposal is to use the GitHub pages for building an AutoYaST profile repository. Then you could use autoyast=https://autoyast.github.io/mini/sles15.xml or autoyast=https://autoyast.github.io/mini/leap15.xml for testing a minimal SLES/Leap profile. Actually these URLs already work! :-) You can give it a try. Most likely you will need additional "netsetup=dhcp" boot option for configuring network. The profiles would be well described (what they do) and well commented (so the users can easily adapt them to their needs). The profiles could be automatically validated (via Travis) and it would be nice to use them also in openQA tests to be sure they really work. We could also link this repository from the official SUSE documentation. The proof of concept is available at https://autoyast.github.io, please check it. It is still just a concept for getting early feedback, there is a lot of work to do. See the README file in https://github.com/autoyast/autoyast.github.io What do you think about it? -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 months, 2 weeks

[yast-devel] Reminder: verify_partial_doubles is not default

by Josef Reidinger

Hi, again I hit by thinking that verify_partial_doubles is now default in rspec3. It is not and will be in rspec4. So what it means? rspec does not check if mocked methods exists at all and it can result in many not so funny errors in test suite. I am just faced it in network, so I create non trivial commit[1] that enables it there. It includes also how to avoid failures on mocked class[2] which avoided build dependencies. From list of errors it can check is typos[3], mocking of wrong class[4] and mocking non-existing methods[5]. So feel free to take it as inspiration and enable it also in your test helper. Josef [1] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [2] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [3] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [4] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… [5] https://github.com/yast/yast-network/pull/830/commits/e18da64fce25242a51710… -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

9 months, 2 weeks

[yast-devel] Innovation Time: Feedback from forums

by josef Reidinger

Hi, I use my todays innovation time to try to collect feedback from forums and as we have quite nice opensuse retrospective output, I try to focus on SLE. So I use forums.suse.com and here is few links with short description: AutoYast - looking for recommended autoyast profile for VM server http://forums.suse.com/discussion/13055/template-best-practices-and-hardeni… - problem with configuring network using autoyast ( not clear what is root of issue ) http://forums.suse.com/discussion/14165/autoyast-sles15-sp1 - easy way to install also custom rpms in autoyast http://forums.suse.com/discussion/14138/adding-custom-rpm-to-installer - trying to add packages iso to directory and use it in autoyast and failed http://forums.suse.com/discussion/14065/installer-fails-to-find-add-ons-fro… - not clear documenation how to reference files from enhanced DVD in autoyast http://forums.suse.com/discussion/13986/copy-a-file-from-the-installer-dvd - autoyast use case unattended installation from USB - documenation not clear http://forums.suse.com/discussion/12227/sles15-unattended-install-from-usb Storage - user trying to resize living system with partitioner and failed. Error probably does not help much: http://forums.suse.com/discussion/14113/resize-partition-error - kudos to partitioner for easy way of deleting btrfs snapshot http://forums.suse.com/discussion/11718/how-to-delete-btrfs-subvolume - switching DOS MBR and GPT real use case http://forums.suse.com/discussion/13961/need-to-convert-mbr-to-gpt - another fs resize http://forums.suse.com/discussion/13205/file-system-increase - another replacing filesystem, this time root one http://forums.suse.com/discussion/12576/replacing-root-filesystem-from-sdb2… Features ( new use cases ) - disable usb due to sec certificates - ca management missing and auth_server missing wizard like setup http://forums.suse.com/discussion/14022/authentication-server-with-yast-and… - again ca management missing http://forums.suse.com/discussion/13084/ca-management-yast-tool-missing - problem to configure proxy in SLES. Works in opensuse http://forums.suse.com/discussion/14221/install-sles-behind-a-proxy - offline self-update from medium http://forums.suse.com/discussion/13582/self-update-offline Misc - package search with RMT error message confuse user: http://forums.suse.com/discussion/14233/how-to-add-a-module-repo-to-an-exis… - issue with packager, cannot find patterns view http://forums.suse.com/discussion/14120/install-selinux-sles-15-sp1 - people use suse firewall module http://forums.suse.com/discussion/13097/sles-12-sp4-cant-manage-firewall-du… - looks like systemd sockets are not always understandable for users and complain to yast http://forums.suse.com/discussion/12846/vnc-server-service - upgrade of system to the same version sometimes can help with boot problems http://forums.suse.com/discussion/14797/sles12sp5-vm-stuck-at-grub-when-boo… - many confusion with SP1 DVD layout like in http://forums.suse.com/discussion/13504/yast-yast2-is-missing-after-install… - even servers is now installed using USB http://forums.suse.com/discussion/14228/install-from-usb Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

10 months, 1 week

[yast-devel] btrfs level 0 qgroups

by Arvin Schnell

Hi, users can do funny things with btrfs qgroups leading to problems: When a subvolume is created a corresponding level 0 qgroup is also created by btrfs. The subvolume id and thus the qgroup id are not predictable (see below). The user can also manually create level 0 qgroups. So the user can 1) manually create qgroup 0/260 and 2) create a subvolume that could get id 260 and the corresponding qgroup gets the id 0/260. A nice qgroup id collision. If libstorage-ng would commit such a setup the manually creation of qgroup 0/260 would fail if it happens after the subvolume creation. Also the user could set different limits for both qgroups which is obviously impossible to commit correctly. I do not see any use-case for level 0 qgroups without a corresponding subvolume. Our btrfs developers also said that there is none. So to avoid such problems with libstorage-ng and YaST I propose to 1) disallow creating level 0 qgroups without an corresponding subvolume and 2) ignore level 0 qgroups without a corresponding subvolume during probing. Item 2) seems like a good idea anyway since btrfs does not delete qgroups when deleting subvolumes, so a hugh number (like several thousands) of useless level 0 qgroups may exist in the system. Comments? Why is the subvolume id not predictable? For once it is not just the next free id: E.g. after deleting all subvolume the ids do not restart at 257. Likely it is possible by further analysis of the btrfs to know the next id but that is internal to btrfs. And finally any other program, e.g. snapper, can concurrently create subvolumes and thus ruin any attempt to predict the ids. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.com> Senior Software Engineer, Research & Development SUSE Software Solutions Germany GmbH Maxfeldstraße 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

10 months, 2 weeks

[yast-devel] YaST: highlights of development sprint 111

by Ancor Gonzalez Sosa

The latest YaST Team report comes more varied than usual, including news about Cockpit and about the openSUSE + LibreOffice Virtual Conference. But, of course, the bulk of the post is still the new features in the installer and its ecosystem: - Unit tests for the installation-images Perl libraries. - New emergency mechanism to ignore storage probing errors. - Support in linuxrc to send DHCP requests in RFC2132 format. Check the whole report at https://yast.opensuse.org/blog/2020-10-30/sprint-111 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

10 months, 3 weeks

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

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-autoinstallation: - [PoC] Run the unit tests in parallel (61 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (174 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-devtools: - Fixed order in %yast_desktop_files macro (12 days) https://github.com/yast/yast-devtools/pull/155 - changes (21 days) https://github.com/yast/yast-devtools/pull/154 - Y2logs analyzer (243 days) https://github.com/yast/yast-devtools/pull/149 - Move desktop files (23 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (30 days) https://github.com/yast/yast-installation/pull/878 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (18 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (23 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (31 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-yast2: - Change the way groups are defined (23 days) https://github.com/yast/yast-yast2/pull/936 Pending requests in repository yast-ycp-ui-bindings: - [WIP] automatic tests for TUI (ncurses) (24 days) https://github.com/yast/yast-ycp-ui-bindings/pull/56 Pending requests in repository yast-ruby-bindings: - Distinguish parsing errors from internal errors (bsc#1174198) (10 days) https://github.com/yast/yast-ruby-bindings/pull/249 - [WIP] Don't crash on NoMethodError when Perl is involved (21 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (23 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (219 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Server Role should install the new yast2_server pattern (19 days) https://github.com/yast/skelcd-control-openSUSE/pull/217 - Fix update external link for non-x86 on Leap - bsc#1120938 (19 days) https://github.com/yast/skelcd-control-openSUSE/pull/215 - Adjust the roles to the new YaST Patterns (300 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (30 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (487 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (20 days) https://github.com/yast/yast-journal/pull/45 Pending requests in repository yast-vpn: - [SLE15-SP3] Place file selection buttons at the bottom (193 days) https://github.com/yast/yast-vpn/pull/18 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

10 months, 3 weeks

[yast-devel] Pending Pull Requests

by yast-ci＠opensuse.org

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-autoinstallation: - [PoC] Run the unit tests in parallel (54 days) https://github.com/yast/yast-autoinstallation/pull/670 - Find the Base Product (167 days) https://github.com/yast/yast-autoinstallation/pull/599 Pending requests in repository yast-devtools: - changes (14 days) https://github.com/yast/yast-devtools/pull/154 - Y2logs analyzer (236 days) https://github.com/yast/yast-devtools/pull/149 - Move desktop files (16 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - [WIP] Warn when an old package is selected to install (23 days) https://github.com/yast/yast-installation/pull/878 Pending requests in repository yast-instserver: - Adapt Rakefile and Dockerfile for SLE-15-SP2 (11 days) https://github.com/yast/yast-instserver/pull/50 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (16 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-theme: - Add pattern-budgie icon (boo#1176164) (24 days) https://github.com/yast/yast-theme/pull/131 Pending requests in repository yast-yast2: - Change the way groups are defined (16 days) https://github.com/yast/yast-yast2/pull/936 Pending requests in repository yast-ycp-ui-bindings: - [WIP] automatic tests for TUI (ncurses) (17 days) https://github.com/yast/yast-ycp-ui-bindings/pull/56 Pending requests in repository yast-ruby-bindings: - [WIP] Don't crash on NoMethodError when Perl is involved (14 days) https://github.com/yast/yast-ruby-bindings/pull/224 Pending requests in repository yast-rake: - Switch desktop directory (16 days) https://github.com/yast/yast-rake/pull/70 Pending requests in repository yast-cio: - convert to libyui ruby bindings (212 days) https://github.com/yast/yast-cio/pull/34 Pending requests in repository skelcd-control-openSUSE: - Server Role should install the new yast2_server pattern (12 days) https://github.com/yast/skelcd-control-openSUSE/pull/217 - Fix update external link for non-x86 on Leap - bsc#1120938 (12 days) https://github.com/yast/skelcd-control-openSUSE/pull/215 - Adjust the roles to the new YaST Patterns (293 days) https://github.com/yast/skelcd-control-openSUSE/pull/195 Pending requests in repository yast-auth-server: - Fix an issue where pkg dependencies were not install (23 days) https://github.com/yast/yast-auth-server/pull/63 - Fixes to make the YaST modules work (480 days) https://github.com/yast/yast-auth-server/pull/48 Pending requests in repository yast-journal: - Use Yast::Builtins.strftime in 'Change Filter' dialog (13 days) https://github.com/yast/yast-journal/pull/45 ERROR: API query limit exceeded -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

11 months

[yast-devel] Interesting blog post about ruby types

by josef Reidinger

Hi, some brain foor for innovation time. This blog post is quite interesting reading worth a time: https://brandur.org/nanoglyphs/015-ruby-typing#ruby-typing Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

11 months, 1 week

[yast-devel] openSUSE Conference 2020

by Ancor Gonzalez Sosa

For those of you who may have overlooked it, starting tomorrow the openSUSE + LibreOffice Virtual Conference will take place online. https://events.opensuse.org/conferences/oSLO Some talks may be interesting for YaST enthusiasts in general or for the YaST Team at SUSE in particular, so check the schedule. This is my particular list in that regard: Integration testing framework for YaST modules https://events.opensuse.org/conferences/oSLO/program/proposals/3277 Top 25 New Features in (Auto)YaST https://events.opensuse.org/conferences/oSLO/program/proposals/3265 Keep up with openSUSE Packaging https://events.opensuse.org/conferences/oSLO/program/proposals/3361 Leap Next https://events.opensuse.org/conferences/oSLO/program/proposals/2960 Transfer a Z System onto your own PC https://events.opensuse.org/conferences/oSLO/program/proposals/3140 Meet the openSUSE board https://events.opensuse.org/conferences/oSLO/program/proposals/3316 Of course, there are many other interesting sessions. Check the full schedule. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

11 months, 1 week

[yast-devel] Mounting Btrfs subvolumes when there are no snapshots

by Ancor Gonzalez Sosa

As part of the current effort to improve how we display Btrfs subvolumes in the Partitioner I was checking how we mount them. We always create a fstab entry for each subvolume like /home, /var... That makes a lot of sense when the system has support for snapshots, because the default subvolume is .snapshots/1/snapshot, so those fstab entries are needed to make the content of each subvolume available in the expected location. But when there are no snapshots, the default subvolume is the top-level one (in openSUSE) or the "@" (in SLE). All other subvolumes are children of that one, which means their content would be already available in the expected location. But still we redundantly mount all those subvolumes via fstab. I find that not only redundant but even confusing. If the users decides to umount, let's say, /home... they will see the content is still there after unmounting, which may be puzzling. Does somebody know what's the purpose of mounting those subvolumes when there are no snapshots? Cheers -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

11 months, 1 week

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development October 2020