- openSUSE Autoinstall

[opensuse-autoinstall] Autoyast on installed system
by Joschi Brauchle 11 Oct '12

11 Oct '12

Hello all, I would like to update an installed system with a new AutoYast XML profile (containing only updated stuff) and found that there is a /sbin/yast ayast_setup setup filename=profile.xml command that does just that. Unfortunately, the docs about what this command does exactly are very spare. Uwe mentions on http://suse.gansert.net/?p=38 that (quoting): ------- The XML file will be read by AutoYaST and applied to your currently running system except (and that’s good – you want it that way, believe me) all 1st stage configuration like partitioning, bootloader, pre- and chrootscripts and software selection. ------- => Thus, for software updates I use post-packages, => for scripts I wanted to use post-scripts and init-scripts. But it looks like init-scripts are not run... is there a complete list of steps that are actually done by this command? Background: I would like to use zypper to enable a repo with the XML mentioned above. But as it does not run the init-scripts and Yast locks the RPM database during post-scripts, I looks like zypper cannot be used along with "ayast_setup setup" at all, right? Best regards, Joschi Brauchle

1 1

[opensuse-autoinstall] default values
by Marcus Moeller 10 Oct '12

10 Oct '12

Hi all. I just got a general question: When using yast2 autoyast module every value in a section is written on changes. e.g.I have only defined that the bootloader should be written to the mbr but the following properties are set in the XML: <global> <boot_boot>false</boot_boot> <boot_custom></boot_custom> <boot_extended>false</boot_extended> <boot_mbr>true</boot_mbr> <boot_root>false</boot_root> </global> As these seems to be default settings, can I just remove them from the XML? How do you handle it? Do you leave them in, as I guess next time the profile is edited with yast2 autoyast, they would be inserted again? Greets Marcus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 1

[opensuse-autoinstall] issue when using many repositories
by Robert Klein 10 Oct '12

10 Oct '12

Hi, I have an issue when using an autoyast profile with some 30 add-on repositories. One or two repositories always fail ("Failed to add add-on product"). Happens with repositories specified either as ftp or as nfs repositories. Is there anything known about this? I don't see anything in the log files of the ftp/nfs-server, just the connections stopping. Is there anything known about this? BTW, this is easier to see in the log files when using nfs, so I didn't notice it earlier: _seven_ connections per repository when adding it as an add-on product. Seems a bit much.. 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

1 0

[opensuse-autoinstall] Whats the purpose of classes? OR: How to modularize the XML profile?
by Joschi Brauchle 27 Sep '12

27 Sep '12

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

2 6

[opensuse-autoinstall] autoyast named by mac-adress
by Detlev Rolf 27 Sep '12

27 Sep '12

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

3 4

[opensuse-autoinstall] Migration SLES11 from 32-bit to 64-bit with autoyast?
by Jan Fader 25 Sep '12

25 Sep '12

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

3 2

[opensuse-autoinstall] 12.2 autoyast experience/changes to 12.1 (mostly sshd)
by Robert Klein 21 Sep '12

21 Sep '12

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

1 0

[opensuse-autoinstall] Marketing Jur�dico | Newsletter Inrise Consultoria | Edi��o 27 | Ano 05
by Inrise RH 18 Sep '12

18 Sep '12

1 0

[opensuse-autoinstall] Local add-on during unattended upgrade to sles11sp2
by Kent, Gregory 14 Sep '12

14 Sep '12

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

1 0

[opensuse-autoinstall] Automatic time zone configuration with Autoyast
by Rob Beglinger 12 Sep '12

12 Sep '12

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

4 4