[ovirt-users] Re: Number of data bricks per oVirt HCI host
Thank You Strahil ! On Thu, Oct 15, 2020 at 8:05 AM Strahil Nikolov wrote: > >Please clarify what are the disk groups that you are referring to? > Either Raid5/6 or Raid10 with a HW controller(s). > > > >Regarding your statement "In JBOD mode, Red Hat support only 'replica 3' > >volumes." does this also mean "replica 3" variants ex. > >"distributed-replicate" > Nope, As far as I know - only when you have 3 copies of the data ('replica > 3' only). > > Best Regards, > Strahil Nikolov > > > On Wed, Oct 14, 2020 at 7:34 AM C Williams > wrote: > > Thanks Strahil ! > > > > More questions may follow. > > > > Thanks Again For Your Help ! > > > > On Wed, Oct 14, 2020 at 12:29 AM Strahil Nikolov > wrote: > >> Imagine you got a host with 60 Spinning Disks -> I would recommend you > to split it to 10/12 disk groups and these groups will represent several > bricks (6/5). > >> > >> Keep in mind that when you start using many (some articles state > hundreds , but no exact number was given) bricks , you should consider > brick multiplexing (cluster.brick-multiplex). > >> > >> So, you can use as many bricks you want , but each brick requires cpu > time (separate thread) , tcp port number and memory. > >> > >> In my setup I use multiple bricks in order to spread the load via LACP > over several small (1GBE) NICs. > >> > >> > >> The only "limitation" is to have your data on separate hosts , so when > you create the volume it is extremely advisable that you follow this model: > >> > >> hostA:/path/to/brick > >> hostB:/path/to/brick > >> hostC:/path/to/brick > >> hostA:/path/to/brick2 > >> hostB:/path/to/brick2 > >> hostC:/path/to/brick2 > >> > >> In JBOD mode, Red Hat support only 'replica 3' volumes - just to keep > that in mind. > >> > >> From my perspective , JBOD is suitable for NVMEs/SSDs while spinning > disks should be in a raid of some type (maybe RAID10 for perf). > >> > >> > >> Best Regards, > >> Strahil Nikolov > >> > >> > >> > >> > >> > >> > >> В сряда, 14 октомври 2020 г., 06:34:17 Гринуич+3, C Williams < > cwilliams3...@gmail.com> написа: > >> > >> > >> > >> > >> > >> Hello, > >> > >> I am getting some questions from others on my team. > >> > >> I have some hosts that could provide up to 6 JBOD disks for oVirt data > (not arbiter) bricks > >> > >> Would this be workable / advisable ? I'm under the impression there > should not be more than 1 data brick per HCI host . > >> > >> Please correct me if I'm wrong. > >> > >> Thank You For Your Help ! > >> > >> > >> ___ > >> Users mailing list -- users@ovirt.org > >> To unsubscribe send an email to users-le...@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/OGZISNFLEG3GJPDQGWTT7TWRPPAMLPFQ/ > >> > > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/CIXPK66DMDN24WQQWXEJJAHZ54ATQDLG/
[ovirt-users] Re: Number of data bricks per oVirt HCI host
>Please clarify what are the disk groups that you are referring to? Either Raid5/6 or Raid10 with a HW controller(s). >Regarding your statement "In JBOD mode, Red Hat support only 'replica 3' >>volumes." does this also mean "replica 3" variants ex. >"distributed-replicate" Nope, As far as I know - only when you have 3 copies of the data ('replica 3' only). Best Regards, Strahil Nikolov On Wed, Oct 14, 2020 at 7:34 AM C Williams wrote: > Thanks Strahil ! > > More questions may follow. > > Thanks Again For Your Help ! > > On Wed, Oct 14, 2020 at 12:29 AM Strahil Nikolov > wrote: >> Imagine you got a host with 60 Spinning Disks -> I would recommend you to >> split it to 10/12 disk groups and these groups will represent several bricks >> (6/5). >> >> Keep in mind that when you start using many (some articles state hundreds , >> but no exact number was given) bricks , you should consider brick >> multiplexing (cluster.brick-multiplex). >> >> So, you can use as many bricks you want , but each brick requires cpu time >> (separate thread) , tcp port number and memory. >> >> In my setup I use multiple bricks in order to spread the load via LACP over >> several small (1GBE) NICs. >> >> >> The only "limitation" is to have your data on separate hosts , so when you >> create the volume it is extremely advisable that you follow this model: >> >> hostA:/path/to/brick >> hostB:/path/to/brick >> hostC:/path/to/brick >> hostA:/path/to/brick2 >> hostB:/path/to/brick2 >> hostC:/path/to/brick2 >> >> In JBOD mode, Red Hat support only 'replica 3' volumes - just to keep that >> in mind. >> >> From my perspective , JBOD is suitable for NVMEs/SSDs while spinning disks >> should be in a raid of some type (maybe RAID10 for perf). >> >> >> Best Regards, >> Strahil Nikolov >> >> >> >> >> >> >> В сряда, 14 октомври 2020 г., 06:34:17 Гринуич+3, C Williams >> написа: >> >> >> >> >> >> Hello, >> >> I am getting some questions from others on my team. >> >> I have some hosts that could provide up to 6 JBOD disks for oVirt data (not >> arbiter) bricks >> >> Would this be workable / advisable ? I'm under the impression there should >> not be more than 1 data brick per HCI host . >> >> Please correct me if I'm wrong. >> >> Thank You For Your Help ! >> >> >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@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/OGZISNFLEG3GJPDQGWTT7TWRPPAMLPFQ/ >> > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/M47YCSFNYYNPYTR7Z3TC63ZSVIR7QUGG/
[ovirt-users] Re: Number of data bricks per oVirt HCI host
Strahil, Please clarify what are the disk groups that you are referring to? Also, Regarding your statement "In JBOD mode, Red Hat support only 'replica 3' volumes." does this also mean "replica 3" variants ex. "distributed-replicate" Thank You For Your Help ! On Wed, Oct 14, 2020 at 7:34 AM C Williams wrote: > Thanks Strahil ! > > More questions may follow. > > Thanks Again For Your Help ! > > On Wed, Oct 14, 2020 at 12:29 AM Strahil Nikolov > wrote: > >> Imagine you got a host with 60 Spinning Disks -> I would recommend you to >> split it to 10/12 disk groups and these groups will represent several >> bricks (6/5). >> >> Keep in mind that when you start using many (some articles state hundreds >> , but no exact number was given) bricks , you should consider brick >> multiplexing (cluster.brick-multiplex). >> >> So, you can use as many bricks you want , but each brick requires cpu >> time (separate thread) , tcp port number and memory. >> >> In my setup I use multiple bricks in order to spread the load via LACP >> over several small (1GBE) NICs. >> >> >> The only "limitation" is to have your data on separate hosts , so when >> you create the volume it is extremely advisable that you follow this model: >> >> hostA:/path/to/brick >> hostB:/path/to/brick >> hostC:/path/to/brick >> hostA:/path/to/brick2 >> hostB:/path/to/brick2 >> hostC:/path/to/brick2 >> >> In JBOD mode, Red Hat support only 'replica 3' volumes - just to keep >> that in mind. >> >> From my perspective , JBOD is suitable for NVMEs/SSDs while spinning >> disks should be in a raid of some type (maybe RAID10 for perf). >> >> >> Best Regards, >> Strahil Nikolov >> >> >> >> >> >> >> В сряда, 14 октомври 2020 г., 06:34:17 Гринуич+3, C Williams < >> cwilliams3...@gmail.com> написа: >> >> >> >> >> >> Hello, >> >> I am getting some questions from others on my team. >> >> I have some hosts that could provide up to 6 JBOD disks for oVirt data >> (not arbiter) bricks >> >> Would this be workable / advisable ? I'm under the impression there >> should not be more than 1 data brick per HCI host . >> >> Please correct me if I'm wrong. >> >> Thank You For Your Help ! >> >> >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@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/OGZISNFLEG3GJPDQGWTT7TWRPPAMLPFQ/ >> > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/Z4HUGVEPTXY2LGTGMO656K4KADCXRLND/
[ovirt-users] Re: Number of data bricks per oVirt HCI host
Thanks Strahil ! More questions may follow. Thanks Again For Your Help ! On Wed, Oct 14, 2020 at 12:29 AM Strahil Nikolov wrote: > Imagine you got a host with 60 Spinning Disks -> I would recommend you to > split it to 10/12 disk groups and these groups will represent several > bricks (6/5). > > Keep in mind that when you start using many (some articles state hundreds > , but no exact number was given) bricks , you should consider brick > multiplexing (cluster.brick-multiplex). > > So, you can use as many bricks you want , but each brick requires cpu time > (separate thread) , tcp port number and memory. > > In my setup I use multiple bricks in order to spread the load via LACP > over several small (1GBE) NICs. > > > The only "limitation" is to have your data on separate hosts , so when you > create the volume it is extremely advisable that you follow this model: > > hostA:/path/to/brick > hostB:/path/to/brick > hostC:/path/to/brick > hostA:/path/to/brick2 > hostB:/path/to/brick2 > hostC:/path/to/brick2 > > In JBOD mode, Red Hat support only 'replica 3' volumes - just to keep that > in mind. > > From my perspective , JBOD is suitable for NVMEs/SSDs while spinning disks > should be in a raid of some type (maybe RAID10 for perf). > > > Best Regards, > Strahil Nikolov > > > > > > > В сряда, 14 октомври 2020 г., 06:34:17 Гринуич+3, C Williams < > cwilliams3...@gmail.com> написа: > > > > > > Hello, > > I am getting some questions from others on my team. > > I have some hosts that could provide up to 6 JBOD disks for oVirt data > (not arbiter) bricks > > Would this be workable / advisable ? I'm under the impression there > should not be more than 1 data brick per HCI host . > > Please correct me if I'm wrong. > > Thank You For Your Help ! > > > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/OGZISNFLEG3GJPDQGWTT7TWRPPAMLPFQ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/XA2CKVS7OMFJEKOXXCZB4UTXVZMEL7TB/
[ovirt-users] Re: Number of data bricks per oVirt HCI host
Imagine you got a host with 60 Spinning Disks -> I would recommend you to split it to 10/12 disk groups and these groups will represent several bricks (6/5). Keep in mind that when you start using many (some articles state hundreds , but no exact number was given) bricks , you should consider brick multiplexing (cluster.brick-multiplex). So, you can use as many bricks you want , but each brick requires cpu time (separate thread) , tcp port number and memory. In my setup I use multiple bricks in order to spread the load via LACP over several small (1GBE) NICs. The only "limitation" is to have your data on separate hosts , so when you create the volume it is extremely advisable that you follow this model: hostA:/path/to/brick hostB:/path/to/brick hostC:/path/to/brick hostA:/path/to/brick2 hostB:/path/to/brick2 hostC:/path/to/brick2 In JBOD mode, Red Hat support only 'replica 3' volumes - just to keep that in mind. From my perspective , JBOD is suitable for NVMEs/SSDs while spinning disks should be in a raid of some type (maybe RAID10 for perf). Best Regards, Strahil Nikolov В сряда, 14 октомври 2020 г., 06:34:17 Гринуич+3, C Williams написа: Hello, I am getting some questions from others on my team. I have some hosts that could provide up to 6 JBOD disks for oVirt data (not arbiter) bricks Would this be workable / advisable ? I'm under the impression there should not be more than 1 data brick per HCI host . Please correct me if I'm wrong. Thank You For Your Help ! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OGZISNFLEG3GJPDQGWTT7TWRPPAMLPFQ/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/XP3KR6S47ZIVK3K3AWIXCJQG7ZKTTO7Q/