On Wed, May 3, 2017 at 7:57 PM, wodel youchi <wodel.youchi@gmail.com> wrote:
Hi again, and sorry for the delay, I was sick, actually I am still sick.... :-(

Just to have more details, from what I have read about iSCSI offload, there are two modes, depending on the hardware you have (the adapter), using VMware terminology, no offense :-) , there is :

- Dependent mode : in this mode the adapter still need the software iSCSI to use the network configuration of the nic port, so the discovery is done on tcp, the rest on offload driver like bnxi2.

This one is similar to TCP offload - the iSCSI processing is done on the HW, the rest is done in software and is supported - it looks like regular iSCSI to oVirt. 

- Independent mode : in this mode the adapter takes all the work by itself, the network part, it will have it's own IP address and so on, and it does not need anything from the OS or the software iSCSI, the configuration is made in the BIOS of the adapter, and the connection is made before the OS is up.

This one indeed is transparent to the OS, and it looks like FC to oVirt.

Does the configuration on oVirt support the two modes? and is there any differences when using them, I mean during the setup.

Both are supported. The former looks like regular iSCSI, the latter like FC to oVirt.


2017-04-30 7:47 GMT+01:00 Yaniv Kaul <ykaul@redhat.com>:

On Sat, Apr 29, 2017 at 7:27 PM, wodel youchi <wodel.youchi@gmail.com> wrote:

We have two hypervisors, each one has a 10Gbe nic card with two ports, the cards support iSCSI offload.

Does oVirt 4.1 support this?

if yes how can someone use it on hosted-engine deployment? the VM engine will be in the SAN targeted by these cards.

Since iSCSI offloading is configured before the OS even loads, to the OS (and therefore oVirt hypervisors) it seems that the storage is 'just connected' - same as FC for all we care.



Virus-free. www.avast.com

Users mailing list