Hi Yevgeni,

From a purely architectural perspective, here are a few points:

1. A lot will depend on what hypervisors you’re planning to run. Hyper-V won’t 
work with either.
2. A lot also depends on the existing network setup, and how far you’re willing 
to go to tweak it. If you look at pure physics, FCs are definitely faster - but 
the network setup is far more complex, and you need more specialised equipments 
- switches, adapters, and so on. I’ll go out on a limb and say that although 
theoretically FCs give you better performance, iSCSI isn’t too bad either when 
you’ve got separate high-speed switches for your storage layer.
3. Well it also depends on what your scaling plans are. If you’re looking at 
adding more compute and storage cap to your setup frequently, FCs are 
definitely not the best way to go. They’re not great when it comes to scaling.
4. Your biggest tradeoff is between reliability and scalability. FCs are 
theoretically more reliable - but not easy to scale. iSCSI may not have the 
same level of reliability, but it’s decent enough - and easier to scale.

As a starting point, perhaps looking at Ceph or Storpool with iSCSI gateways 
might be a good idea, I personally feel.


Best!

Rudraksh Mukta Kulshreshtha
Vice-President - DevOps & R&D
IndiQus Technologies
O +91 11 4055 1411 | M +91 99589 54879
indiqus.com

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information that is confidential and/or 
privileged. If you are not the intended recipient please delete the original 
message and any copy of it from your computer system. You are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited unless proper authorization has been obtained for such 
action. If you have received this communication in error, please notify the 
sender immediately. Although IndiQus attempts to sweep e-mail and attachments 
for viruses, it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses.
On 1 Sep 2021, 1:49 PM +0530, Дикевич Евгений Александрович 
<evgeniy.dikev...@becloud.by>, wrote:
> Hi all!
> Which is better solution to use KVM with iSCSI or FC shared storage in 2021:) 
> ?
> Now we have many vendor's supported storages which we can't swap. Some of 
> them we can reconfigure to use NFS but another- not:(
> How we can use that storages with KVM? Maybe someone have success stories 
> with similar configurations?
>
> Please give me any ideas or advices or success stories:)
> Thx a lot
>
>
>
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются 
> конфиденциальными и предназначены исключительно для использования лицом 
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
> (лицами), которому (которым) предназначено это письмо, не копируйте и не 
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
> почтовой системы. Любое несанкционированное использование, распространение, 
> раскрытие, печать или копирование этого электронного письма и прикрепленных к 
> нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
> является незаконным и запрещено. Принимая во внимание, что передача данных 
> посредством Интернет не является безопасной, мы не несем никакой 
> ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
> при передаче данных или этим сообщением и прикрепленными к нему файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended solely 
> for use by the person (or persons) referred to (mentioned) as the intended 
> recipient (recipients). If you are not the intended recipient of this email, 
> do not copy or disclose its contents and delete the message and any 
> attachments to it from your e-mail system. Any unauthorized use, 
> dissemination, disclosure, printing or copying of this e-mail and files 
> attached to it, except by the intended recipient, is illegal and is 
> prohibited. Taking into account that data transmission via Internet is not 
> secure, we assume no responsibility for any potential damage caused by data 
> transmission errors or this message and the files attached to it.

Reply via email to