openSUSE Autoinstall September 2012

autoinstall@lists.opensuse.org

13 participants
13 discussions

by John Willis

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

9 years, 5 months

[opensuse-autoinstall] openSUSE 12.2 and autoyast-configured services

by Conny Seidel

Hello list, I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. Our current way doesn't work anymore: <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service". -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel(a)amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ################################################################## -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 6 months

[opensuse-autoinstall] Whats the purpose of classes? OR: How to modularize the XML profile?

by Joschi Brauchle

Hello all, I've been using AutoYast successfully for a while now (incl. rules), but I never got to understand the purpose of classes or how exactly to use them... (even after reading the documentation about it :-) The docs about rules are quite nice, providing working examples. But for classes, I couldn't find a complete working example/setup. I have the following questions: 1) Until now, I came to understand that classes provide a way to include/merge external XML files. So how are they *different* from a set of XIncludes? 2) If they are different, how does a node know/decide which class it "belongs to" and thus, which XML files it is supposed to merge? Is there some kind of decision process like for rules? The reason I am asking these questions is that I would like to make a modular AutoYast profile XML. Currently, I have one giant_base.xml file plus some small amendments confX.xml, which are merged via rules.xml. My setup looks like this: /autoyast/ |--giant_base.xml |--conf1.xml |--conf2.xml | ... |--confN.xml `--rules `--rules.xml Unfortunately the giant_base.xml became too big to oversee things. What I would like to have is a more or less empty base.xml that simply imports all common parts from sub XMLs (i.e. I would like the partitioning section to have its own file, same with common software, networking stuff and so on). Once all common parts are included, the rules should merge the hardware/host specific changes. It should look like: /autoyast/ |--base_that_includes_common_stuff.xml |`--common | |--common_partitioning.xml | |--common_software.xml | ... | `--common_whatever.xml `--rules | `--rules.xml | ... How would one do this with AutoYast? Thanks for your help :-)

9 years, 7 months

[opensuse-autoinstall] autoyast named by mac-adress

by Detlev Rolf

Hello, I'm trying to install our OES2 SP1 /SLES11 SP1 -Server via autoyast, booting with minicd. Everything works fine, but I have a problem with the naming of the autoinstallation-file. I saved the file on a server on an http and nfs-share. I wrote the path to the file in the autoyast=-parameter of the isolinux.cfg on the minicd (I tried it with http and nfs). It works if I - add the correct filename to the path - rename the autoinst.xml to "default" - rename the autoinst.xml to hexadecimal naming of the ip-adress. But it doesn't work if I rename the file like the MAC-address of the server as described in http://doc.opensuse.org/products/draft/SLES/SLES-deployment_sd_draft/cha.de… When I look with wireshark, I can see that the installation doesn't search for a file named as the MAC-address, only IP-address or "default" is searched for. Is this a bug or do I have to pass any other parameters to the isolinux.cfg Thanks, Detlev -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 7 months

[opensuse-autoinstall] Migration SLES11 from 32-bit to 64-bit with autoyast?

by Jan Fader

Hi List We have to migrate some server with SLES11-SP2 from x86 to x86_64. The hardware is already 64-bit and we're are thinking about an update via autoyast and PXE. Has anybody done such a migration (with or without autoyast) without a fresh installation? Do you have any concerns doing it via autoyast? Kind regards Jan Fader -- - Jan Fader ------- bpm consult ag ------------ beeline solutions + E-Mail: jf(a)bpm.ch - Telefon: +41 61 417 10 64 - Fax: +41 61 417 10 11| - Klünenfeldstrasse 22 - CH-4127 Birsfelden - Web: www.bpm.ch + -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 7 months

[opensuse-autoinstall] 12.2 autoyast experience/changes to 12.1 (mostly sshd)

by Robert Klein

Hi everyone, I did a couple of tests with openSUSE 12.2 and compared it with 12.1 and early 12.2 milestones/betas. Some of the workarounds necessary for 12.1 are no longer necessary: - you don't have to explicitly install yast2-runlevel (via <software><packages><package>yast2-runlevel</package>...) anymore. (I'm not sure if this was sshd related or not.) - you no longer need to insserv autoyast and sshd in a post-partitioning-script. I didn't check this in 12.1, but if you disable ip6 in 12.2 you might want to set the AddressFamily in your autoyast profile: <sshd> <config> <AddressFamily config:type="list"> <listentry>inet</listentry> </AddressFamily> ... </config> <status config:type="boolean">true</status> </sshd> A big thanks to the developers! Best regards Robert -- Robert Klein - Max Planck-Institut für Polymerforschung Ackermannweg 10 55128 Mainz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 8 months

[opensuse-autoinstall] Marketing Jur�dico | Newsletter Inrise Consultoria | Edi��o 27 | Ano 05

by Inrise RH

9 years, 8 months

[opensuse-autoinstall] Local add-on during unattended upgrade to sles11sp2

by Kent, Gregory

Hi, I've got a couple of questions about Upgrading to SLES11SP2 using an autoyast file. I've got an add-on that is a local iso and have configured it using the xml below. <add-on> <add_on_products config:type="list"> <listentry> <media_url>iso:///?iso=software.iso&url=file:///mnt/var/local/install/</media_url> <ask_on_error config:type="boolean">false</ask_on_error> </listentry> </add_on_products> </add-on> Normally the iso is in /var/local/install but during Upgrade stage 1 its located at /mnt/var/local/install The problem occurs during Upgrade stage 2 as the iso is now back at /var/local/install The error that is displayed is "Cannot not access installation media". I would like to install packages during stage 1 and stage 2 from this iso. Is this possible? Am I configuring the path wrong in the autoyast xml? Thanks Greg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 8 months

[opensuse-autoinstall] Automatic time zone configuration with Autoyast

by Rob Beglinger

Is it possible for autoyast to query an external source to determine the appropriate time zone for a device? I have 5000+ machines that are identical except that they reside in different time zones, US/Mountain, US/Eastern and US/Central. I would like to only have one autoyast.xml file to maintain, but as these are all at remote sites, I cannot have a prompt pop up to have a user select the appropriate time zone. Does anyone have any suggestions? Thanks, Rob -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 8 months

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups

by big beer

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

9 years, 8 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall September 2012