[opensuse-factory] AutoYaST tools: feedback wanted
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: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 27. April 2020, 17:30:45 CEST schrieb Imobach González Sosa:
Any other idea?
One of the most interesting ideas in this area came from Neal and the Fedora realm (if I recall and understand him correctly): After an ordinary installation, save that, e.g. in root's root be enabling one switch (Save AutoYaST profile, with an optional comment field), such as this could be loaded from another installation process. During installation, check USB drives for these files, and allow to recreate this installation, if the user selects one. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi there, On Mon, 27 Apr 2020, 18:21:52 +0200, Hans-Peter Jansen wrote:
Am Montag, 27. April 2020, 17:30:45 CEST schrieb Imobach González Sosa:
Any other idea?
One of the most interesting ideas in this area came from Neal and the Fedora realm (if I recall and understand him correctly): After an ordinary installation, save that, e.g. in root's root be enabling one switch (Save AutoYaST profile, with an optional comment field), such as this could be loaded from another installation process.
During installation, check USB drives for these files, and allow to recreate this installation, if the user selects one.
I can only second this! FWIW and IIRC, years ago there used to exist a file called autoyast.xml in /root after an installation, so the logic did exist. Dunno if this was SLES only, though.
Cheers, Pete
Cheers. l8er manfred
On Mon, 27 Apr 2020 18:39:07 +0200
Manfred Hollstein
Hi there,
On Mon, 27 Apr 2020, 18:21:52 +0200, Hans-Peter Jansen wrote:
Am Montag, 27. April 2020, 17:30:45 CEST schrieb Imobach González Sosa:
Any other idea?
One of the most interesting ideas in this area came from Neal and the Fedora realm (if I recall and understand him correctly): After an ordinary installation, save that, e.g. in root's root be enabling one switch (Save AutoYaST profile, with an optional comment field), such as this could be loaded from another installation process.
During installation, check USB drives for these files, and allow to recreate this installation, if the user selects one.
I can only second this! FWIW and IIRC, years ago there used to exist a file called autoyast.xml in /root after an installation, so the logic did exist. Dunno if this was SLES only, though.
Also it would be very useful to differentiate the options that user picked and the options that were left to defaults. Perhaps commenting out the defaults in the resulting profile would work. Thanks Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 27.04.2020 um 18:45 schrieb Michal Suchánek:
On Mon, 27 Apr 2020 18:39:07 +0200 Manfred Hollstein
wrote: Hi there,
Am Montag, 27. April 2020, 17:30:45 CEST schrieb Imobach González Sosa:
Any other idea? One of the most interesting ideas in this area came from Neal and the Fedora realm (if I recall and understand him correctly): After an ordinary installation, save that, e.g. in root's root be enabling one switch (Save AutoYaST profile, with an optional comment field), such as this could be loaded from another installation process.
During installation, check USB drives for these files, and allow to recreate this installation, if the user selects one. I can only second this! FWIW and IIRC, years ago there used to exist a file called autoyast.xml in /root after an installation, so the logic did exist. Dunno if this was SLES only, though. Also it would be very useful to differentiate the options that user
On Mon, 27 Apr 2020, 18:21:52 +0200, Hans-Peter Jansen wrote: picked and the options that were left to defaults. Perhaps commenting out the defaults in the resulting profile would work.
Thanks
Michal
My wishlist from 15.1: The xml should not contain long lists of system users, packages or services, that are just default. - System users should be left to the packages that need them. - Patterns should be used as much as possible to reduce the package list - if possible use patterns and deselect packages. - Services should only show up, when state changed, e.g. from disabled to enabled. Don't know if 15.2 is better at that, since i use a 15.1 xml for 15.2. Thanks, Andreas -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El lun, 27-04-2020 a las 20:38 +0200, Andreas Vetter escribió: Hi all, [..]
My wishlist from 15.1: The xml should not contain long lists of system users, packages or services, that are just default.
- System users should be left to the packages that need them.
- Patterns should be used as much as possible to reduce the package list - if possible use patterns and deselect packages.
- Services should only show up, when state changed, e.g. from disabled to enabled.
Thanks a lot for sharing. It looks like a bloated profile (containing a lot of information, although in some cases is the default) is one of the main problems our users are facing.
Don't know if 15.2 is better at that, since i use a 15.1 xml for 15.2.
Unfortunatelly 15.2 is not (and will not) better at this (perhaps we can get some minor improvements during 15.2 lifecycle). But we expect 15.3 to be better at this.
Thanks, Andreas
Thanks! Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El lun, 27-04-2020 a las 18:39 +0200, Manfred Hollstein escribió:
Hi there,
Hi all,
On Mon, 27 Apr 2020, 18:21:52 +0200, Hans-Peter Jansen wrote:
Am Montag, 27. April 2020, 17:30:45 CEST schrieb Imobach González Sosa:
Any other idea?
One of the most interesting ideas in this area came from Neal and the Fedora realm (if I recall and understand him correctly): After an ordinary installation, save that, e.g. in root's root be enabling one switch (Save AutoYaST profile, with an optional comment field), such as this could be loaded from another installation process.
During installation, check USB drives for these files, and allow to recreate this installation, if the user selects one.
Well, if you use "autoyast=usb:///autoinst.xml", AutoYaST will try to fetch the autoinst.xml file from an USB device. It is not done automatically, though.
I can only second this! FWIW and IIRC, years ago there used to exist a file called autoyast.xml in /root after an installation, so the logic did exist. Dunno if this was SLES only, though.
Yes, you are right. We used to put that file in /root/autoinst.xml. However, we stopped doing it during SLE 12 SP2 times. It turned out that as some things cannot be configured during installation, those options were not included in that file. Rebooting and running "yast2 clone_system" caused a different result. Thanks for your comments! Regards, Imo -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Vetter
-
Hans-Peter Jansen
-
Imobach González Sosa
-
Manfred Hollstein
-
Michal Suchánek