[ovirt-users] Re: Self Hosted Engine and iSCSI doubt

On Wed, May 9, 2018 at 10:37 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com&gt; wrote: That limitation was due to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1351213 The root issue is clearly explained here: https://bugzilla.redhat.com/show_bug.cgi?id=1351213#c4 The issue was mainly related to the auto import process and now in node-0 deployment flow we are not relying on that anymore (the hosted-engine storage domain is directly created by the engine running on the bootstrap local VM and so it's known by the engine by design) so probably we can just ignore that limitation but honestly I'm not 100% you will not encounter other minor gaps so I'd suggest to still keep two distinct storage domains over two distinct iSCSI targets for production systems. We are still working to handle the HE storage domain exactly as a regular storage domain but we still have some gaps so it's targeted to 4.3: https://bugzilla.redhat.com/show_bug.cgi?id=1451653 You can use a single target portal group (by the way now hosted-engine is able to connect all the portals in the same portal group) but I'd recommend to expose two distinct targets so, as an example with targetcli: /> iscsi/ create iqn.2018-05.com.example:target1 /> iscsi/ create iqn.2018-05.com.example:target2