Ok.... apparently the "path" is not just any desired device I want it to be called once set up. From ietadm man page:
add a new logical unit with [lun] to specific target with [id]. The logical unit is offered to the initiators. [path] must be block device files (including LVM and RAID devices) or regular files.
So I created a regular file in my FS and then I reissued the command with the new path and it worked. But I can't see the device yet:
Jan 2 09:27:57 cluster1 iSCSILogicalUnit: DEBUG: Calling ietadm --op new --tid=1 --lun=1 --params Path=/usr/local/sanoswww,Type=fileio,ScsiId=sanwwwsanos,ScsiSN=151c9bde,
Jan 2 09:27:57 cluster1 iSCSILogicalUnit: DEBUG: Exit code 0
Jan 2 09:27:57 cluster1 iSCSILogicalUnit: DEBUG: Command output: ""
Sweet! But the san resource is not anywhere to be found if you ask me:
root@cluster1:/usr/lib/ocf# fdisk -lu
Disk /dev/sda: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders, total 20480000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008089e
Device Boot Start End Blocks Id System
/dev/sda1 * 2046 16623615 8310785 5 Extended
/dev/sda5 2048 999423 498688 82 Linux swap / Solaris
/dev/sda6 1001472 16623615 7811072 83 Linux
So, where's the logical unit?