Hi Nicholas,
A quick-start guide would be a great addition and it's something that is on my radar, but I haven't had time to get it completed yet. I'll probably put it off until we have our next release branch of ESOS which will include a number of TUI enhancements, so I'd like to wait until then.
Yes, its a bit overwhelming, but if you follow the documents in that wiki, start with the numbered sections, they will flow in order of setup/configuration (eg, 12_Installation, 21_Initial_System_Configuration, 31_Basic_Back_End_Storage_Setup, etc.).
But here is a quick flow to get you started (in order, assuming a single-head setup):
- Create a ESOS USB flash drive.
- Use the ESOS USB drive in your HP server, boot from USB, boot into ESOS.
- At first boot, change the root password, set timezone, date/time, and NTP server (if using).
- Configure your network interface(s), host name, etc.
- Configure your "back-end storage" -- this would be using hardware RAID (eg, maybe a Smart Array controller in that HP), or maybe using software RAID, or straight LVM on the raw disks. Or maybe using RAID and then LVM on top of it, or you could even use a file system (eg, XFS) on top of the RAID device and create "virtual disk files" (basically using regular files as virtual disks and present those to initiators).
- For iSCSI, you'll need to add an iSCSI target interface (just one is probably fine). Do this in the targets menu, add iSCSI target, default name is fine (if you like).
- Then enable the iSCSI target (targets menu).
- Next you'll want to create a host "security group" -- this is like LUN groups, server groups, etc. as used on other disk array systems. Create a group on the iSCSI target you created above, then add initiators to group (these will be the IQN's from the servers/initiators that you want to present the storage to).
- Next you need to create a "device" -- these are part of the mapping from back-end storage to LUN's. I'd go with vdisk_blockio if using hardware/software RAID, LVM, etc. and if you're using virtual disk files on a file system, use vdisk_fileio. The defaults in the SCST device dialog should be fine.
- Finally, you'll map the SCST device you created in the step above to a LUN. Do this in the devices menu, I'd add a LUN 0 (most initiators expect this, so if you only have one, use LUN 0).
That should be about it in a nutshell... the sessions should show up. You may need to scan from the initiator side. If you don't get any connectivity, ensure you have a LUN 0 and that you have the initiator names entered correctly.
Let us know if you have any trouble or questions, we're happy to help.
--Marc