modular autoinstall file ?
Hi, is it possible to organize the autoinstall file in a more modular way ? Can I include configuration files with only a subset of configuration information ? In this way I would have only one main file and include several configuration files according to my hardware and software selections and I could setup a simple construction kit for different hosts with different installation specifications. If yes, can I partially automatize this behavior ? For example : I define several classes of the different types of network interfaces in my workstation pool. Then I assign every host to one of these special classes. Due to this information I can make my installation decisions in my main autoinstall file for many hosts without to create an own autoinstall file for each host. What would be if I want to install some software packages only to a subset of hosts. I would define a corrsponding class and make my decisions in my main autoinstall file to install this software only to the hosts defined in this class -> If host member of class then install software ... Using the CMS it is possible to define classes, but I don't know how to use them. Exists there some reference manual which explains this in detailed or can anyone give me an Howto ? Or must I create for each host its own autoinstall file ? Tanks in advance Regards Werner Hack Universitaet Ulm
* Werner Hack <werner.hack@e-technik.uni-ulm.de> [Jan 28. 2003 11:13]:
Hi,
is it possible to organize the autoinstall file in a more modular way ? Can I include configuration files with only a subset of configuration information ? In this way I would have only one main file and include several configuration files according to my hardware and software selections and I could setup a simple construction kit for different hosts with different installation specifications.
If yes, can I partially automatize this behavior ? For example : I define several classes of the different types of network interfaces in my workstation pool. Then I assign every host to one of these special classes. Due to this information I can make my installation decisions in my main autoinstall file for many hosts without to create an own autoinstall file for each host. What would be if I want to install some software packages only to a subset of hosts. I would define a corrsponding class and make my decisions in my main autoinstall file to install this software only to the hosts defined in this class -> If host member of class then install software ...
Using the CMS it is possible to define classes, but I don't know how to use them. Exists there some reference manual which explains this in detailed or can anyone give me an Howto ? Or must I create for each host its own autoinstall file ?
I am currently working on an update package for networking which will allow hardware independent confguration of the network card. This might solve this problem. Current classes support wont help you cause classes ar merged 'offline'. One of the main features of the next release will be rule based auto-installation and 'online' class merge and evaluation. More on Rules and other new features later though. Another option would be to use XML Inlcudes. You can include a remote XML file (a portion of the control file, for example defining networking). This include file will be retrieved during installation and evaluated as a part of the control file. Unfortunatly this is an undocumented feature, but it's fairly easy to use of you are familier with XML. Regards, Anas
Tanks in advance Regards
Werner Hack Universitaet Ulm
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (2)
-
Anas Nashif -
Werner Hack