- openSUSE Autoinstall

Own message in a popup window?
by Daniel Spannbauer 24 Feb '21

24 Feb '21

Hello, is it possible to open a popup window with a to-defined message before the partitioning starts? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München

1 0

autoinstall with cron or systemd-timer
by Andreas Vetter 22 Jan '21

22 Jan '21

Hi *, I did not find a way to install cronjobs for root in the autoyast docu. Since execution time matters in this case, /etc/cron.daily/ is not the way to go. Installing a complete crontab for root would be a way, but may be a problem when one has to combine several entries on the fly. Anyone using that? So i tend to use a systemd-timer, but that needs 3 files: The timer, the service and the actual script to run. What do others use? -- Mit freundlichen Gruessen, Andreas Vetter

3 2

[opensuse-autoinstall] Script after mounting, but before partitioning
by Daniel Spannbauer 30 Oct '20

30 Oct '20

Hallo, till 15.2 I used "pre-script" to run my scripts after mounting the installation-source and before the partitioning. No, the pre-script is called before the mouting of the installation source. Is this a bug? Or a new feature? How can I run a script after mounting and before paritioning? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] /tmp as tmpfs: no entry in fstab
by Daniel Spannbauer 30 Jul '20

30 Jul '20

Hello, we use autoyast for a long time now. We always configured /tmp as a tmpfs. For that, we add <drive> <device>/dev/tmpfs</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">tmpfs</filesystem> <format config:type="boolean">true</format> <fstopt>size=512m,nodev,mode=1777</fstopt> <mount>/tmp</mount> </partition> </partitions> <type config:type="symbol">CT_TMPFS</type> <use>all</use> </drive> But with Leap 15.2 , there is no entry for that in /etc/fstab anymore. Has something changed here? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

[opensuse-autoinstall] releasever in repo URL
by Andreas Vetter 28 Jul '20

28 Jul '20

Hi, is it possible to use $releasever in autoyast.xml file? E.g.: <add-on> <add_on_products config:type="list"> <listentry> <media_url><![CDATA[http://host.domain.com/path/$releasever/repo/ oss]]></media_url> ... -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] mksusecd: invalid signature
by Daniel Spannbauer 16 Jul '20

16 Jul '20

Hello, I try to build a custom installation media with the current mksusecd. mksusecd --verbose --sign -c "/tmp/create_dump-760099/myiso.iso" --vendor "me" --preparer "Daniel Spannbauer" --defaultrepo cd:/,hd:/ --sign-key "/home/ds/oss-secret-key-ascii.gpg" ISOTEMP After starting it via pxe boot with parameters "autoyast=nfs://nas/15.2/autoyast.xml install=nfs://nas/15.2" the installation starts as expected but fails with "nfs://nas/15.2/repodata/repmod.xml Invalid Signature". In that state I can switch to a console. I can the my key lying around under /pubkeys. Any Ideas how to get it working? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] guidance request for NIC/drive mapping and target configs
by Bryan Gartner 06 Jul '20

06 Jul '20

Looking for some guidance to help automate/modularize repeatable deployments ... 1) NIC setup scenario: - The target server systems have multiple NICs - The respective MAC addresses of each NIC can be found using BMC interface - User wishes to seed desired NIC usage by providing target MAC Address(es) (e.g. MACAddress1 - dhcp, MACAddress3 - IP/mask,gateway,...) After (re)reading the docs many times, seems like a possible approach might be (albeit have yet to succeed doing this) - generate an autoYaST pre-script with - desired MACAddress - desired "bootproto" - output = mapping to associated "device" name found during boot - leverage rules, classes, or even asks (to confirm) - pull in "interface" fragment, substituting "device" name and config specifics Bonus points / challenges - also seems doable to have "interface" fragments for more complicated setups: - bond these two devices - bond/bridge these N devices, etc. - managing firewall settings - perhaps using post-scripts (for anything beyond the one needed NIC for install) 2) Disk setup scenario - The target server systems have multiple drives - The respective drive (model, serial number, size, etc) of each drive can be found using BMC interface - User wishes to seed desired partitioning by providing a physical attribute (e.g. serial number - root, serial number - data) As above, after (re)reading the docs many times, seems like a possible approach might be (albeit have yet to succeed doing this) - generate an autoYaST pre-script with - desired serial number - desired partitioning type/label - output = mapping serial number to associated "device" name found during boot - leverage rules, classes, or even asks (to confirm) - pull in "drive" fragment targeting mapped "device" name and config specifics Bonus points / challenges - more difficult if storage controller has created LUNs of multiple drives - perhaps using post-scripts (for anything beyond the one needed drive for install) Thanks in advance for any guidance and suggestions on how to implement this, for a large set of systems that are to be (re)installed over time and may not be entirely homogeneous. The goal though is to only pre-seed those specifics (that can be found outside the installer) and generate/rely upon such mappings into for the fragments to provide a good level of consistency (vs. just using the interactive installer interface). Of course, either post-install or typical configuration management options could be layered on after the fact to complete the system configuration, beyond needing one (desired) NIC to access packages/repos and one (desired) drive to install upon. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

Re: [opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 29 Jun '20

29 Jun '20

On Mon, Jun 29, 2020 at 04:45:31PM +0100, Imobach Gonz?lez Sosa wrote: > Perhaps I am missing something, but mixing packages for multiple releases in > the same repository does not look like a good idea at all. Why not just having > a separate repository for each release? OBS[1] can help with that. Until I got this far down the road, I did not think this was an issue. But, this advice is valuable, and I will look into the pointer you've provided. Thanks! > [..] > > Regards, > Imo > > [1] https://openbuildservice.org/ > > -- > Imobach Gonz?lez Sosa > Blog: https://imobachgs.github.io/ > Twitter: @imobachgs -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

Re: [opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 29 Jun '20

29 Jun '20

On Mon, Jun 29, 2020 at 10:53:05AM -0300, Perry Werneck wrote: > Hi, > > I think you can do this using a meta-package requiring the bash in the exat > version you need. I suppose I should be transparent about what I'm trying to accomplish: At $WORK, we produce SUSE-based appliances for customers, ultimately delivered as an OVA. Internally, we do not use repositories for deployment via autoyast; we have some home-rolled mechanism that is showing it's age. I've been exploring, with some success, using a single private repository, to contain our RPMs of multiple releases, and with 'zypper', I can with fine detail, describe installation and upgrade tasks. (I'm using 'createrepo' to manage that metadata.) I'm now exploring deployments via autoyast, and am finding I don't have the fine-grained control that zypper offers, to declare 'deploy with version 4 vs version 5'. I was considering your suggestion, maintaining a meta-RPM that called out specific dependencies, but as I would implicitly want multiple versions of that meta-RPM, I still suffer from the constraint of <package> in autoyast not letting me call out version numbers. It's entirely possible there's richer metadata in my repo I can manage (for example, I don't really get 'products' yet) that would get me over this planning, if this tactic was in fact possible. > -- > Perry Werneck > Bras??lia/DF -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] when using autoyast, can a specific version of a package be required?
by Brian Reichert 26 Jun '20

26 Jun '20

This is in a SLES 12 SP5 environment, not opensuse, but I'm having difficulty getting questions answered in the SLES web forums. So, I'm poking at folks here. When I use autoyast to introduce a package, I can name the package: <package>bash</package> If a repository has more than one version of a package, autoyast seems to default to using the latest version available. bash-4.3-82.1.x86_64.rpm bash-4.3-83.23.1.x86_64.rpm How can I, via autoyast, communicate I want a specific version? I tried to use <package>bash-4.3-82.1</package> But yast2 said 'no such package in the repository' (I'm paraphrasing here.) -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1