Hi Imo, I believe I can provide some feedback on that. As we work with autoyast ourselves and I've supported many colleagues in creating profiles, I can tell that creating new profile is complex. Strategy of cloning existing system and modifying it, but that's also a lot of work as profile contains everything. Maybe fixing module for the profile generation can help here. In order to make profile work with other disk names, customers use shell script to modify xml in the runtime. Instead we could support multiple names so that same profile could be reused. Packages, patterns and modules get renamed. It's almost never the case that profile from one SP will work in the next one. This one is tricky to act on. As for the future, I have 2 ideas in mind. As yomi is out there (https://github.com/openSUSE/yomi), maybe we should look into developing that solution further to replace autoyast. Second thing I had in mind was actually to significantly simplify supported features and just provide interface to shell in order to reduce costs for the maintenance. So in case customers need creating users, they can run useradd command. I would also suggest to gather some feedback from enterprise customers too, as I believe they have different use-cases, like using AY with SUSE Manager to provision machines. Hope it helps, let me know if you have any questions. Thanks! On 4/17/20 9:10 AM, Imobach González Sosa wrote:
Hi all,
After rewriting our storage layer and, partially, our network stack, the YaST team is looking now to AutoYaST, which is showing its age.
Just in case someone does not know, AutoYaST is a software component that, using an XML based description, orchestrates YaST modules to install/upgrade and configure the system in an unattended way. You might want to check the docs[1][2] for more information.
We have started started to analyze and build a list of the things we would like to address, but we would love to hear your opinion. Do you have some use case you would like to see supported? Which problems have you faced when using AutoYaST? Which features do you miss? Do you have a different vision of what AutoYaST should be (we can learn from those opinions too)?
Any idea/comment is welcome. Thanks a lot in advance!
Regards, Imo
[1] https://documentation.suse.com/sles/15-SP1/html/SLES-all/book-autoyast.html [2] https://doc.opensuse.org/projects/autoyast/
--
Kind regards,
Rodion Iafarov