April 2020 - YaST Development - openSUSE Mailing Lists

Re: [yast-devel] Meeting about changes to xml schema
by Lukas Ocilka 30 Apr '20

30 Apr '20

On 4/30/20 12:40 PM, josef Reidinger wrote: > [1] https://github.com/yast/yast-installation-control/pull/96 Checking the PR, I saw a diff from "disksize" to "string". That's right as there's no "disksize" data-type. We have also discussed that we should then modify our control.xml stored on disk during RPM-post-script (which is the right way as `zypper dup` is supported too). But I have a question: what happens in customers' AY profiles actually contain these "disksize" types? Are they going to be invalid? Should we replace/remove them when loading the profile first? I'd like to be careful here, because what used to be valid for ages now turns into invalid because of our internal change. That doesn't sound right even if our intentions were crystal clear. What do you think? Thx Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2

[yast-devel] AutoYaST tools: feedback wanted
by Imobach González Sosa 27 Apr '20

27 Apr '20

Hi all, After doing some research[1] (thanks all for your feedback), the YaST team has started to work on improving AutoYaST. We have identified some areas that we should focus on. One of them, is the process of creating an AutoYaST profile. Creating a profile can be quite challenging, so we offer two different tools to help you in this process: * The "yast2 clone_system" command, which generates a profile with the configuration of the current system. It allows to filter which parts of the profile take into account. * The "AutoYaST UI", which allows to create a profile from scratch (or by cloning the configuration of the current system) and modify the values using a UI. This tool is included in the "autoyast2" package. However, we wonder how do you create your profiles. Do you use any of those tools? Or do you just write some XML yourself? Perhaps you use the tools and tweak the results later... Moreover, we would love to know which problems do you face when you try to create a new profile. Is there anything our tools could do to make your life easier? What about providing some kind of "templates" (minimal, full...) you can tweak? Any other idea? Please, if you can, help us with providing your feedback. Of course, any comment beside these questions is highly appreciated as well. Regards, Imo [1] https://lists.opensuse.org/opensuse-factory/2020-04/msg00291.html -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- 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 27 Apr '20

27 Apr '20

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-apparmor: - Port to rake (317 days) https://github.com/yast/yast-apparmor/pull/40 Pending requests in repository yast-bootloader: - Fix resume with uuid partition (284 days) https://github.com/yast/yast-bootloader/pull/564 Pending requests in repository yast-core: - Fixes for gensalt handling with libxcrypt. (59 days) https://github.com/yast/yast-core/pull/144 Pending requests in repository yast-country: - Port to rake (284 days) https://github.com/yast/yast-country/pull/217 Pending requests in repository yast-devtools: - Y2logs analyzer (61 days) https://github.com/yast/yast-devtools/pull/149 - Supplement changes from YCC (89 days) https://github.com/yast/yast-devtools/pull/148 - Move desktop files (322 days) https://github.com/yast/yast-devtools/pull/143 Pending requests in repository yast-installation: - Stop plymouth splash to avoid serial terminal splutter. (45 days) https://github.com/yast/yast-installation/pull/841 - Demo: eager mode of zombie-killer 0.5 (535 days) https://github.com/yast/yast-installation/pull/761 Pending requests in repository yast-network: - network-ng: test cases document (draft) (157 days) https://github.com/yast/yast-network/pull/947 - add initial test cases document (283 days) https://github.com/yast/yast-network/pull/853 Pending requests in repository yast-nis-client: - fix build requires (48 days) https://github.com/yast/yast-nis-client/pull/47 Pending requests in repository yast-online-update-configuration: - drop old testsuite and convert to rake (31 days) https://github.com/yast/yast-online-update-configuration/pull/24 Pending requests in repository yast-packager: - Include some hints in the "Priority" label (bsc#1154693) (26 days) https://github.com/yast/yast-packager/pull/482 Pending requests in repository yast-pkg-bindings: - drop old empty testsuite (31 days) https://github.com/yast/yast-pkg-bindings/pull/127 Pending requests in repository yast-registration: - [SP3] Fix misleading default_skipping_text (BSC#1167795) (24 days) https://github.com/yast/yast-registration/pull/488 Pending requests in repository yast-sound: - drop old testsuite without replacement (31 days) https://github.com/yast/yast-sound/pull/36 Pending requests in repository yast-squid: - packaging: remove SuSEfirewall2 artifacts (275 days) https://github.com/yast/yast-squid/pull/30 Pending requests in repository yast-sudo: - WIP: Add a CFA model for handling the sudoers file (118 days) https://github.com/yast/yast-sudo/pull/12 Pending requests in repository yast-sysconfig: - Drop old testsuite (30 days) https://github.com/yast/yast-sysconfig/pull/30 Pending requests in repository yast-users: - Improve readme (81 days) https://github.com/yast/yast-users/pull/224 - Move back the UMASK default value to /etc/login.defs (bsc#1099153) (662 days) https://github.com/yast/yast-users/pull/161 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

1 0

[yast-devel] Re: [opensuse-factory] The (near) future of AutoYaST
by Imobach González Sosa 24 Apr '20

24 Apr '20

El vie, 24-04-2020 a las 00:24 +0200, suse(a)a-domani.nl escribió: [..] > > Firstly, my gratitude for maintaining autoyast. You are welcome! Thanks you for using it. > Through it, you can pre-define each and every option there is during > Suse installation > (and actually you can even set things that are not even asked :-) > I used it for installing countless HP-servers: each and everyone got > installed identically (something my colleagues never were able to > obtain) It sounds great :) > And it works lightning fast: HP-servers needed more time through the > BIOS than the entire installation + update, by feeding the autoyast > file > to the TFTPboot + PXE > (before that, a co-worker was assigned an entire DAY for installing > and > configuring ) > And, not just bare metal, but also virtual-clients > > I do know that you can pre-configure systems with kiwi (and can even > supply an autoyastfile) but that is a rather bumpy road, not stable, > and > KIWI had a tendency to have a mind of its own (not configurable), > especially with regards to configuring disks, LVM and crypt. > > So, keep it all configurable, even invisible options, please. Sure. We do not plan to remove any option at this point. The plan is to fix a few things that we know are broken, make it more robust (improving the code quality and test coverage) and improve/add a few features. We will keep all of you informed! Thanks! Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- 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] Marketing for Leap 15.2
by Ancor Gonzalez Sosa 23 Apr '20

23 Apr '20

As usual, I was asked to help with the Features Page and with the Release Announcement of openSUSE Leap 15.2, from the YaST point of view. If you are curious about what we will say to the world or you want to improve it, take a look to the "Snapper", "YaST" and "AutoYaST" sections of https://en.opensuse.org/Features_15.2 I also summarized two of those (sub)sections ("Installer improvements" and "AutoYaST") into the corresponding "Installation Process" section of the draft for the Release Announcement. You can find the draft here: https://etherpad.opensuse.org/p/leap152release I was unable to summarize the rest into the corresponding section of the Release Announcement. Hopefully Doug will do, but feel free to reach him and offer your help. 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] List of AutoYaST things to improve/fix
by Imobach González Sosa 22 Apr '20

22 Apr '20

Hi, For the time being, we are putting aside the discussion about how to collaborate with Yomi, as we do not see how it fits in our short term goals. However, further discussions will take place in the future for sure. I would like to share with you a not finished list of items that we would like to tackle sooner than later. We are still checking the status of our network code and how we handle the 2nd stage (and the hooks for 3rd party modules). Additionally, I am having a look at kickstart tooling. The list (including other relevant information) lives (temporarily) in as a Gist: https://gist.github.com/imobachgs/78f6a4946742ea5c5d132c66c7fc6f64 Please, do no hesitate to ask if you think we are missing something important. Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/

1 0

Re: [yast-devel] Change in Yast-Ntp-Module
by Lukas Ocilka 22 Apr '20

22 Apr '20

On 4/22/20 8:51 AM, Bernd Ritter wrote: > Couldn't this could be done via a systemd timer unit as well? This would > consequently use systemd instead of a remaining cron-job somewhere. Hi Bernd, We thought we have changed that half year ago, see https://github.com/yast/yast-ntp-client/pull/151 But this is in Leap 15.2 (and later) only. Older releases still use cronjob as it doesn't make sense to change already installed and working systems. Please, check our implementation if you want/can. Thanks Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2

[yast-devel] Change in Yast-Ntp-Module
by Bernd Ritter 22 Apr '20

22 Apr '20

Hi there, when configuring my system I recently found that the Yast-Ntp module (Network Services -> NTP configuration) still uses a cronjob to perform the option "synchronize without daemon". Couldn't this could be done via a systemd timer unit as well? This would consequently use systemd instead of a remaining cron-job somewhere. Is there reason to this? If the change would be desirable I would love to look into that and do it. Cheers, Bernd -- 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 97th sprint report
by Imobach González Sosa 21 Apr '20

21 Apr '20

Hi all, The YaST team has published another sprint report. We have focused on: * NCurses installation in old graphic chips * Booting from Remote Encrypted devices * Smarter network configuration in Linuxrc with the new try keyword * Better support for auto-configured devices in S/390 systems * Researching about how to improve XML YaST’s parser You can find the whole report at http://yast.opensuse.org/blog/2020-04-20/sprint-97 Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- 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] Meeting about XML parser future
by josef Reidinger 21 Apr '20

21 Apr '20

Hi, I would like to arrange meeting about future of XML parser as we discuss on review and planning meeting. I propose to have it next Tuesday after daily call if everyone interested has a time. And topics? Two main ones: improvements for SLE15 SP3/Leap 15.3 and roadmap for further future. Result of both topics should be trello cards with clear goals. SP3 topics: - discuss if all quirks mentioned in respective trello card make sense and if not, if we can remove it ( as example skipping content of hash and array if it contain nil, removing non string keys in hash, etc ) - discuss if we can depend on nokogiri - see https://github.com/yast/yast-yast2/pull/1039#issuecomment-614441891 - and related what to do with schema validation in SP3 Roadmap topics: - schema validation in long term - use cases for xml parser - approach for xml parser - serializer versus easy writting of xml for users - error handling Proposed Attends: - whoever is interested in topic - ideally Imo and Schubi as autoyast is big xml parser user - lslezak as he knows a lot about usage in control files - mvidner as he knows a lot about old xml parser Any other ideas and how does time fit for you? Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3