Q: autoyast with NFS install root and DHCP
Hello, I am new to this list and just exploring the possibilities with the yast2 autoinstallation with suse8.0. I came across several questions that were not really clear to me after reading the documentation: I would like to configure a client to be installed as far as possible by DHCP. So the client should receive the SuSE-NFS installation source DIR and its server from DHCP and as far as possible I would like the client to get the location of the autoinst-controlfile as well from DHCP. At the moment my DHCP-server sets the nextserver and the filename options with IP-Address and PATH of the NFS server with the SUSE-CDs. Now when I start the installation and enter eg. autoyast=tftp://my-tftp-serverip/path/control.xml it seems autoyast does something different than expected. It configures the networkinterface via DHCP (gets correct values) but then complains that it cannot find the installation source. Well I had expected that the installtion source is received automatically by DHCP using the filename and nextserver-options and the the controlfile would then be received by tftp from the server given. But it is not. How can I do this? Ideally I would like to enter only something like autoyast=dhcp on the kernel commandline and then it should retrieve all information needed from the DHCP-server and start autoinstallation. Can this be done? What dhcp options are needed? A last question is, if it is possible to do a semi automatic installtion. Installing a client I always have to answer questions like Installation source, language, where to install the bootloader etc. My answers are usually always the same but on the other side the partitioning of the harddisk is different. So I would like to have defaults for most of the questions yast2 asks me during a manual installtion without beeing asked but have a way to partition the haddisk myself interactively. Does anyone know a way for this? Thanks Rainer -- ---------------------------------------------------------------------------- Rainer Krienke krienke@uni-koblenz.de Universitaet Koblenz, http://www.uni-koblenz.de/~krienke Rechenzentrum, Voice: +49 261 287 - 1312 Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1001312 -----------------------------------------------------------------------------
* Rainer Krienke <krienke@uni-koblenz.de> [Jun 11. 2002 09:08]:
Hello,
I am new to this list and just exploring the possibilities with the yast2 autoinstallation with suse8.0. I came across several questions that were not really clear to me after reading the documentation:
I would like to configure a client to be installed as far as possible by DHCP. So the client should receive the SuSE-NFS installation source DIR and its server from DHCP and as far as possible I would like the client to get the location of the autoinst-controlfile as well from DHCP. At the moment my DHCP-server sets the nextserver and the filename options with IP-Address and PATH of the NFS server with the SUSE-CDs.
Now when I start the installation and enter eg. autoyast=tftp://my-tftp-serverip/path/control.xml it seems autoyast does something different than expected. It configures the networkinterface via DHCP (gets correct values) but then complains that it cannot find the installation source. Well I had expected that the installtion source is received automatically by DHCP using the filename and nextserver-options and the the controlfile would then be received by tftp from the server given. But it is not. How can I do this?
use the root-path option in dhcp or supplu install=nfs://<server>/<path>
Ideally I would like to enter only something like autoyast=dhcp on the kernel commandline and then it should retrieve all information needed from the DHCP-server and start autoinstallation. Can this be done? What dhcp options are needed?
You still need to supply where the profile resides! We are looking into possibilities of adding an option autoyast=dhcp but that is currently not supported
A last question is, if it is possible to do a semi automatic installtion. Installing a client I always have to answer questions like Installation source, language, where to install the bootloader etc. My answers are usually always the same but on the other side the partitioning of the harddisk is different. So I would like to have defaults for most of the questions yast2 asks me during a manual installtion without beeing asked but have a way to partition the haddisk myself interactively. Does anyone know a way for this?
This is a feature of the next release. It is already implemented and should answer all your questions above. Regards, Anas
Thanks Rainer -- ---------------------------------------------------------------------------- Rainer Krienke krienke@uni-koblenz.de Universitaet Koblenz, http://www.uni-koblenz.de/~krienke Rechenzentrum, Voice: +49 261 287 - 1312 Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1001312 -----------------------------------------------------------------------------
-- 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
On Dienstag, 11. Juni 2002 18:15, Anas Nashif wrote:
* Rainer Krienke <krienke@uni-koblenz.de> [Jun 11. 2002 09:08]:
Hello, ...
I would like to configure a client to be installed as far as possible by DHCP. So the client should receive the SuSE-NFS installation source DIR and its server from DHCP and as far as possible I would like the client to get the location of the autoinst-controlfile as well from DHCP. At the moment my DHCP-server sets the nextserver and the filename options with IP-Address and PATH of the NFS server with the SUSE-CDs.
... use the root-path option in dhcp or supplu install=nfs://<server>/<path>
This does not seem to be working with DHCP. I tried option root-path=nfs://server_ip:/path_to_nfs_dir option root-path=server_ip:/path_to_nfs_dir option root-path=/path_to_nfs_dir (assuming "nextserver" would possibly be evaluated) but the message is always that yast was unable to find the installation source. The option nextserver and filename are set accordingly to "server_ip" and "path_to_nfs_dir". On the kernel command line I specified tftp as the method for retrieving the control file. Using additional the install= parameter on the kernel command line it worked as expected.
Ideally I would like to enter only something like autoyast=dhcp on the kernel commandline and then it should retrieve all information needed from the DHCP-server and start autoinstallation. Can this be done? What dhcp options are needed?
You still need to supply where the profile resides! We are looking into possibilities of adding an option autoyast=dhcp but that is currently not supported
In principle this should not be a problem if the path to the control file, i.e. the URL I have to specify manually on the kernel commandline is retrieved from the DHCP-server?
A last question is, if it is possible to do a semi automatic installtion. Installing a client I always have to answer questions like Installation source, language, where to install the bootloader etc. My answers are usually always the same but on the other side the partitioning of the harddisk is different. So I would like to have defaults for most of the questions yast2 asks me during a manual installtion without beeing asked but have a way to partition the haddisk myself interactively. Does anyone know a way for this?
This is a feature of the next release. It is already implemented and should answer all your questions above.
This is fine. Will the next release be only available with the next SuSE-Linux release i.e. 8.1 or is it available independently of the suse-linux release? Thanks Rainer -- ---------------------------------------------------------------------------- Rainer Krienke krienke@uni-koblenz.de Universitaet Koblenz, http://www.uni-koblenz.de/~krienke Rechenzentrum, Voice: +49 261 287 - 1312 Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1001312 -----------------------------------------------------------------------------
* Rainer Krienke <krienke@uni-koblenz.de> [Jun 12. 2002 09:14]:
This does not seem to be working with DHCP. I tried
option root-path=nfs://server_ip:/path_to_nfs_dir option root-path=server_ip:/path_to_nfs_dir
option root-path=/path_to_nfs_dir (assuming "nextserver" would possibly be evaluated)
This is the right syntax. Just tested it, i.e group { next-server 192.168.1.1; host cyber { hardware ethernet 00:50:ba:3f:b5:d5; fixed-address cyber; option T129 "autoyast=http://192.168.1.1/profiles/ install=nfs nosshd"; option root-path "/work/CDs/original-8.0"; filename "vmlinuz.nbi-8.1"; } } And it works as expected! Check on the server side what is linuxrc trying to mount!
but the message is always that yast was unable to find the installation source. The option nextserver and filename are set accordingly to "server_ip" and "path_to_nfs_dir". On the kernel command line I specified tftp as the method for retrieving the control file. Using additional the install= parameter on the kernel command line it worked as expected.
In principle this should not be a problem if the path to the control file, i.e. the URL I have to specify manually on the kernel commandline is retrieved from the DHCP-server?
See above how I do that. But I agree with you that a solution for all cases must be provided.
This is a feature of the next release. It is already implemented and should answer all your questions above.
This is fine. Will the next release be only available with the next SuSE-Linux release i.e. 8.1 or is it available independently of the suse-linux release?
autoyast is not independent and itheavily relies on YaST2 and development of YaST2. So the answer is no, autoyast with new features will only be availbe with new SuSE Linux releases, i.e. 8.1 Regards, Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
On Mittwoch, 12. Juni 2002 18:49, Anas Nashif wrote:
* Rainer Krienke <krienke@uni-koblenz.de> [Jun 12. 2002 09:14]:
This does not seem to be working with DHCP. I tried
option root-path=nfs://server_ip:/path_to_nfs_dir option root-path=server_ip:/path_to_nfs_dir
option root-path=/path_to_nfs_dir (assuming "nextserver" would possibly be evaluated)
This is the right syntax.
Just tested it, i.e group {
next-server 192.168.1.1; host cyber { hardware ethernet 00:50:ba:3f:b5:d5; fixed-address cyber; option T129 "autoyast=http://192.168.1.1/profiles/ install=nfs nosshd"; option root-path "/work/CDs/original-8.0"; filename "vmlinuz.nbi-8.1"; } }
And it works as expected! Check on the server side what is linuxrc trying to mount!
I found what was wrong. After all it was my fault. I found the error because of the exmaple from you above. I forgot to say install=nfs on the kernel-commandline thinking since I set the appropriate variables in DHCP autoyast would assume that if these values are present then it would automatically install from NFS. Thanks Rainer -- ---------------------------------------------------------------------------- Rainer Krienke krienke@uni-koblenz.de Universitaet Koblenz, http://www.uni-koblenz.de/~krienke Rechenzentrum, Voice: +49 261 287 - 1312 Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1001312 -----------------------------------------------------------------------------
participants (2)
-
Anas Nashif -
Rainer Krienke