Update for all. The deployment finally detect the SAS collected storage. After manual compile the driver for the RAID control PCI card.

Nir is correct. FC detect anything that is not "NFS, iSCSI". As this time it also detect a local connected SATA SSD.

2020年8月10日月曜日 1:55:37 GMT+8、Nir Soffer <nsoffer@redhat.com>が書いたメール:

On Sat, Aug 8, 2020 at 6:56 AM Jeff Bailey <bailey@cs.kent.edu> wrote:
>
> I haven't tried with 4.4 but shared SAS works just fine with 4.3 (and has for many, many years).  You simply treat it as Fibre Channel.  If your LUNs aren't showing up I'd make sure they're being claimed as multipath devices.  You want them to be.  After that, just make sure they're sufficiently wiped so they don't look like they're in use.

Correct. FC in oVirt means actually not "iSCSI". Any device - including local
devices - that multipath expose, and is not iSCSI is considered as FC.

This is not officially supported and not documented anywhere. I learned
about it only we tried to deploy strict multipath blacklist allowing
only "iscsi"
or "fc" transport, and found that it broke users' setups with sas other esoteric
storage.

Since 4.4 is the last feature release, this will never change even if it is not
documented.

Nir

> On 8/7/2020 10:49 PM, Lao Dh via Users wrote:
>
> Wow. That's sound bad. Then what storage type you choose at last (with your SAS connected storage)? VMware vSphere support DAS. Red Hat should do something.
>
> 2020年8月8日土曜日 4:06:34 GMT+8、Vinícius Ferrão via Users <users@ovirt.org>が書いたメール:
>
>
> No, there’s no support for direct attached shared SAS storage on oVirt/RHV.
>
> Fibre Channel is a different thing that oVirt/RHV supports.
>
> > On 7 Aug 2020, at 08:52, hkexdong--- via Users <users@ovirt.org> wrote:
> >
> > Hello Vinícius,
> > Do you able to connect the SAS external storage?
> > Now I've the problem during host engine setup. Select Fibre Channel and end up show "No LUNS found".
> > _______________________________________________
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-leave@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RDPLKGIRN5ZGIEPWGOKMGNFZNMCEN5RC/
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2CLI3YSYU7BPI62YANJXZV7RIQFOXXED/
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WOBHQDCBZZK5WKRAUNHP5CGFYY3HQYYU/
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UY52JRY5EMQJTMKG3POE2YXSFGL7P55S/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/JYWUVULGUNLTU6QOY6WOUKBCA5IAO5QR/