Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
appnote:ibft [2016/01/17 00:49] nomizfs |
appnote:ibft [2016/01/17 00:54] nomizfs |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| ---- | ---- | ||
| - | **IMPORTANT NOTE:** | + | === IMPORTANT NOTE: === |
| - | + | ||
| - | //-------------- | + | |
| Using other than intel brand nic's can mess with nic interface ordering, especially in debian. If you have nic brands other than intel, and need to boot debian, you must read the important note at the end of the guide in addition to the debian section. You also need a debian installer that includes non-OSS firmware, or you need to include the drivers for your nic in the installer, or you need to add the kernel module manually afterwards (see reference wiki url).// | Using other than intel brand nic's can mess with nic interface ordering, especially in debian. If you have nic brands other than intel, and need to boot debian, you must read the important note at the end of the guide in addition to the debian section. You also need a debian installer that includes non-OSS firmware, or you need to include the drivers for your nic in the installer, or you need to add the kernel module manually afterwards (see reference wiki url).// | ||
| - | -------------- | ||
| ===== Step 1: ===== | ===== Step 1: ===== | ||
| Set up robinsmidsrod's ipxe scripts at https://gist.github.com/robinsmidsrod/2234639. Ask in #ipxe @ freenode or this thread if you have issues. You need to define the variables and defaults, and have the /boot directory for adding node defaults. Don't worry, that's actually the hard part. Setting up debian and dracut is the easy part :) | Set up robinsmidsrod's ipxe scripts at https://gist.github.com/robinsmidsrod/2234639. Ask in #ipxe @ freenode or this thread if you have issues. You need to define the variables and defaults, and have the /boot directory for adding node defaults. Don't worry, that's actually the hard part. Setting up debian and dracut is the easy part :) | ||
| + | ===== Debian Jessie and Wheezy based distros: ===== | ||
| - | ---- | + | ==== Jessie: ==== |
| - | + | ||
| - | ---- | + | |
| - | **Debian Jessie and Wheezy based distros:** | + | |
| - | + | ||
| - | + | ||
| - | ---- | + | |
| - | + | ||
| - | ---- | + | |
| - | **Jessie:** | + | |
| **1.** Install standard debian distro, it doesn't matter how: bootstrap, install to iscsi target via debian installer, install to iscsi backed KVM volume, install to raw file, install to disk. As long as you can export the resulting block device via iscsi you're good. | **1.** Install standard debian distro, it doesn't matter how: bootstrap, install to iscsi target via debian installer, install to iscsi backed KVM volume, install to raw file, install to disk. As long as you can export the resulting block device via iscsi you're good. | ||
| Line 78: | Line 67: | ||
| Done, your system will now boot from iscsi with static or dhcp based ip settings, which are defined only once server-side in ipxe boot scripts. (edit: might not be entirely true using static ip, but static ip setup kinda defies the whole idea of this guide) | Done, your system will now boot from iscsi with static or dhcp based ip settings, which are defined only once server-side in ipxe boot scripts. (edit: might not be entirely true using static ip, but static ip setup kinda defies the whole idea of this guide) | ||
| - | **Wheezy:** | + | ==== Wheezy: ==== |
| The procedure is exactly the same as above with the addition that changes are needed in halt and reboot scripts to prevent them from hanging while waiting for iscsi initiator to disconnect before unmounting root, which of course is impossible since root is on the remote target it wants to disconnect. | The procedure is exactly the same as above with the addition that changes are needed in halt and reboot scripts to prevent them from hanging while waiting for iscsi initiator to disconnect before unmounting root, which of course is impossible since root is on the remote target it wants to disconnect. | ||
| Line 85: | Line 74: | ||
| or no, just flip it, i can't remember what it was as default. | or no, just flip it, i can't remember what it was as default. | ||
| - | **Dracut:** | + | ==== Dracut: ==== |
| **1.** Install as usual to any block device, as with debian. | **1.** Install as usual to any block device, as with debian. | ||
| Line 91: | Line 80: | ||
| **2.** after installation do: | **2.** after installation do: | ||
| - | ''yum update && yum install -y iscsi-initiator-utils'' | + | ''yum update && yum install -y iscsi-initiator-utils'' |
| - | ''echo "add_dracutmodules+="iscsi"" > /etc/dracut.conf.d/ibft.conf'' | + | ''echo "add_dracutmodules+="iscsi"" > /etc/dracut.conf.d/ibft.conf'' |
| - | ''nano /etc/default/grub'' | + | ''nano /etc/default/grub'' |
| add the following 3 entries to GRUB_CMDLINE_LINUX="rd.iscsi.firmware=1 rd.iscsi.ibft=1 netroot=iscsi:ibft" | add the following 3 entries to GRUB_CMDLINE_LINUX="rd.iscsi.firmware=1 rd.iscsi.ibft=1 netroot=iscsi:ibft" | ||
| Line 171: | Line 160: | ||
| - | **-----------IMPORTANT NOTICE------------** | + | ==== IMPORTANT NOTICE ==== |
| For example adding a broadcom based nic to a node with one integrated intel nic, will probably flip the order of the nics at grub kernel boot, making the broadcom nic eth0 and the intel nic eth1. You need to be aware of this because in that case you need to change which MAC address is granted the DHCP configured hostname at boot, and also because in that case ipxe will see the intel MAC first, but after grub phase the linux kernel will switch the interfaces and thus the MAC and ip address of the client logging into the iscsi target _after_ grub phase will be different, meaning 2 entries for each node is needed in SAN firewall and/or iscsi target LUN access permissions. | For example adding a broadcom based nic to a node with one integrated intel nic, will probably flip the order of the nics at grub kernel boot, making the broadcom nic eth0 and the intel nic eth1. You need to be aware of this because in that case you need to change which MAC address is granted the DHCP configured hostname at boot, and also because in that case ipxe will see the intel MAC first, but after grub phase the linux kernel will switch the interfaces and thus the MAC and ip address of the client logging into the iscsi target _after_ grub phase will be different, meaning 2 entries for each node is needed in SAN firewall and/or iscsi target LUN access permissions. | ||
