On Wed, May 9, 2018 at 10:23 AM, Veiko Kukk <[email protected]> wrote: > 2018-05-09 11:07 GMT+03:00 Gianluca Cecchi <[email protected]>: >> >> " >> IMPORTANT >> If you are using iSCSI storage, do not use the same iSCSI target for the >> shared >> storage domain and data storage domain. >> " >> >> Does it simply remark that the LUN for the hosted engine storage (shared >> storage domain) should be different from the LUN(s) used then for normal >> VMs (data storage domain), or what? >> >> I think it doesn't refer to the portal that for some reason needs to be >> different, correct? >> >> Any clarification about this restrictions? >> >> >> > I do not know. But I would guess it might be to avoid errors during > mounting/unmounting those two logically separate storage domains if they > are on the same physical resource. > > Veiko > > Actually I don't understand the meaning of the limitation itself... what target stands for in this context? Eg if I configure an iSCSI server using RHEL/CentOS 7.x OS and using targetcli and follow this: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/online-storage-management#osm-target-setup
I have the hierarchy ../target/tpg/luns/[lun0,lun1,lun2] so it seems I have to create two different targets and put the hosted engine lun under target1/tpg1 and then the data domain luns under target2/tpg2 Normally if I connect to Enterrise Storage Arrays that offers iSCSI as a connection type (eg EQL or 3PAR) I simply put the portal ip and then I see the mapped LUNs granted to me, so in this case how can I differentiate "target", to be in the "safe/recommended" condition? Gianluca
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected]
