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
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
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
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
