Given: SLES11 SP1 Problem: I have a control file which looks like <?xml version="1.0"?> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude"> http://10.11.8.3/export/suse/etc/tce_script.xml"/> http://10.11.8.3/export/suse/sles11sp1/autoinstall/classes/tce_post.xml"/> .... Autoyast does not complain during installation but its looks like that these xml file are never been executed. The xincludes files containing simple post-script sections. Thus nothing is found in "grep tce /var/log/Yast2/* " and " find /var/adm/autoinstall/ " does not show any script been executed. The current state is very annoying since i find no documentation about how the merge and how the xml file processing really works and what are the requirements to make "xincludes" working. My current understanding of the autoyast process for automated network installations is Autoyast ( Autoinstallation ) 1) autoyast reads ./rules/rules.xml from the installation server and mergers according to the rules. The result will be written to /tmp/profile/autoinst.xml of the installation environment. 2) The /tmp/profile/autoinst.xml file will be parsed by autoyast. 2.1) The xinclude(s) from /tmp/profile/autoinst.xml will be loaded 3) The pre-scripts will be executed 3.1) In case a /tmp/profile/modified.xml exist this file will be parsed again. Hint: a) To modifiy the /tmp/profile/autoinst.xml at this stage copy it to /tmp/profile/modified.xml and make any modification on this file vi pre-script. b) Use in a pre-script as the last command "cp /tmp/profile/*.xml /mnt/var/tmp/" to save the used xml files. This way you can compare after the installation the autoinst.xml with your generated modified.xml 4.0) If the /tmp/profile/modified.xml exist it will be used otherwise the /tmp/profile/autoinst.xml Its not clear how the xincludes file will be executed or if i can have within a section of a control file a xinclude or not. Example: ... <nis> <!-- Is the next line valid ? --> http://10.11.8.3/export/suse/etc/tce_nis.xml"/> ... </nis> <dns> http://10.11.8.3/export/suse/etc/tce_dns.xml"/> </dns> Information and/or links are appreciated. Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

I'll be trying something like the following shortly on vmware, I used a similar method to do provisioning on xen domUs. I might be missing something but I was doing something like the following. Make gold VM with the following vmdks - boot/root - swap - data Go ahead and format/partition the 1st vmdk only. Mount it and then install grub, mbr, and autoyast kernel/initrd that you would serve over tftp. Set the grub boot line to start off the autoyast with the options/control file/etc you want. At that point it's autoyasting just like it was pxe booting, you have just removed the need to pxe. So when someone clones the gold VM they are just cloning something that will boot and kickoff an autoyast. Kinda lame, since pxe has it's own advantages that you are no longer using. The only real difference in this is that it's not pxe booting, and the vmware guys _think_ they are cloning with their mouse click. -- BigBeerJR On Wed, Mar 30, 2011 at 8:58 AM, Tim Kirby wrote:

Has anyone written any thoughts on the interplay between VM cloning and autoyast ? I haven't seen anything that I can recall but then again I haven't been watching closely... but it appears to have appeared on my radar screen now, so I thought I'd ask.

Tim -- Tim Kirby                                       651-605-9074 trk@cray.com                   Cray Inc. Information Systems

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org