Hi,
Does anyone having a working autoyast example that uses iSCSI as storage?
Tried:
== <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
[...]
<iscsi-client> <initiatorname>iqn.2013-13.eu.maxnet:inittest</initiatorname> <targets config:type="list"> <listentry> <authmethod>None</authmethod> <portal>192.168.178.12:3260</portal> <startup>onboot</startup> <target>iqn.2008-08.com.starwindsoftware:jaguar-test</target> </listentry> </targets> <version>1.0</version> </iscsi-client> ==
But it does not seems to work and shows "device '' not found by storage backend" in Yast.
Also tried not specifying an iSCSI section and passing the information through the iBFT in the hope that the installer picks it up automatically (which does work for other OS like CentOS and Windows Server), with the same result.
Yours sincerely,
Floris Bos
Hi,
On Mon, Oct 28, Floris Bos / Maxnet wrote:
Hi,
Does anyone having a working autoyast example that uses iSCSI as storage?
Tried:
== <partitioning config:type="list">
<drive> <use>all</use> </drive> </partitioning>
[...]
<iscsi-client> <initiatorname>iqn.2013-13.eu.maxnet:inittest</initiatorname> <targets config:type="list"> <listentry> <authmethod>None</authmethod> <portal>192.168.178.12:3260</portal> <startup>onboot</startup> <target>iqn.2008-08.com.starwindsoftware:jaguar-test</target> </listentry> </targets> <version>1.0</version> </iscsi-client> ==
But it does not seems to work and shows "device '' not found by storage backend" in Yast.
Also tried not specifying an iSCSI section and passing the information through the iBFT in the hope that the installer picks it up automatically (which does work for other OS like CentOS and Windows Server), with the same result.
Sorry for late reply. I was on vacation.
Unfortunately specifying the iscsi setup in the <iscsi-client> section of a autoyast profile currently does not work. Autoyast would need to have code to do iscsi-client setup before trying to apply <partitioning> section and such code is currently simply not there. But it should not be too much work to add that, so I keep this in mind and most probably will add that for next release (openSuSE 13.2 and/or SLE12).
If the iscsi setup is done via iBFT on the other hand, it should work. In this case you should not need a <iscsi-client> section on autoyast profile at all since the iscsi disk is integrated into the system via Network card BIOS and should be available to autoyast like a physical disk. Could you provide me with the content of /var/log/YaST2 of such an installation attempt, so that I can check what is wrong. Unfortunatly I do not have a iBFT capable newtork card in one of my test systems.
Bye, Thomas Fehr
Hi,
On 11/18/2013 11:53 AM, Thomas Fehr wrote:
On Mon, Oct 28, Floris Bos / Maxnet wrote:
But it does not seems to work and shows "device '' not found by storage backend" in Yast.
Also tried not specifying an iSCSI section and passing the information through the iBFT in the hope that the installer picks it up automatically (which does work for other OS like CentOS and Windows Server), with the same result.
[...]
If the iscsi setup is done via iBFT on the other hand, it should work. In this case you should not need a <iscsi-client> section on autoyast profile at all since the iscsi disk is integrated into the system via Network card BIOS and should be available to autoyast like a physical disk. Could you provide me with the content of /var/log/YaST2 of such an installation attempt, so that I can check what is wrong. Unfortunatly I do not have a iBFT capable newtork card in one of my test systems.
Will get you the log files later (currently not at the right location)
Regarding the iBFT capable network card: I am not using any special network card either, but am creating the iBFT in software by booting iPXE ( http://www.ipxe.org/ ) first, and creating the iBFT using a script along the lines of:
== #!ipxe set initiator-iqn initiator-iqn set username my-username set password my-password set keep-san 1 set skip-san-boot 1 sanboot iscsi:1.2.3.4::3260::my-target-iqn kernel http://webserver-containing-opensuse/boot/x86_64/loader/linux textmode=1 install=http://webserver-containing-opensuse autoyast=https://my-webserver/autoyast-generating-script.php initrd http://webserver-containing-opensuse/boot/x86_64/loader/initrd boot ==
That works for other OSes, which search for the iBFT table left at a known memory region by iPXE and use the information. (they either call "iscsistart -b" which uses the information to connect automatically, or they modprobe iscsi_ibft, and query the information through /sys)
autoinstall@lists.opensuse.org
-
Floris Bos -
Floris Bos / Maxnet
-
Thomas Fehr