[ovirt-users] Re: oVirt 3 Node with GlusterFS
Moin, We use in our Enviroment three ssd drives with four TB space in a Raid 5 on a adaptec contrioller and use on the ovirt installation the jbod on the drive which the Adaptec Controller provide. If we have three Servers in place we use the same config but each volume will be replicate to the other servers. Next year we plan to use a Raid 10 with four drives and the rest will be the same. I think the speed will not be the best one but für the data we have enough redundancy im place. brMarcel Am Donnerstag, dem 02.12.2021 um 18:30 + schrieb Strahil Nikolov via Users: > For SSDs , I would use each ssd as a single brick. > Don't forget to align the LVM/XFS in case you are not using Gluster's > Ansible /which oVirt also uses for deployment/ : > https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/administration_guide/brick_configuration > > Best Regards, > Strahil Nikolov > > > > On Thu, Dec 2, 2021 at 9:48, Joseph Goldman > > wrote: Sorry to be clearer > > > > There is 15 Spin disks total > > > > 9 SSD disks total > > > > Spin will be split into 3x RAID-5's on the physical hosts (5 disks) > > SSD will be split into 3x RAID-5's on the physical hosts (3 disks) > > > > My plan was as you said, create a single brick on each of the 3 > > spin > > RAID-5's and a single brick on each of the 3 SSD RAID-5's - just > > wasn't > > sure if there was a better way to go about it. > > > > Thanks, > > Joe > > > > -- Original Message -- > > From: "dhanaraj.ramesh--- via Users" > > To: users@ovirt.org > > Sent: 2/12/2021 5:40:47 PM > > Subject: [ovirt-users] Re: oVirt 3 Node with GlusterFS > > > > >if you go with RAID 5 option it is expected to have performance > > degradation but you will have double protection for your data. > > > > > >my suggestion, go with each HDD disks as individual bricks with > > replica 3 volumes and same for SSD's > > >___ > > >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/6777XHHUNWWFXWPN7VNKJC35QHS4JDE5/ > > ___ > > 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/IX7ECAXCG3PTHDVPY6JT5GQFP2TV2W4O/ > > > > ___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/GUYTHI2W247WLIHBTXKFHEZCLVMVHGZG/ ___ 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/KCFF4VAZ7PNWJWKTBV5BWWI55KJZNRNP/
[ovirt-users] Re: oVirt 3 Node with GlusterFS
For SSDs , I would use each ssd as a single brick. Don't forget to align the LVM/XFS in case you are not using Gluster's Ansible /which oVirt also uses for deployment/ : https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/administration_guide/brick_configuration Best Regards,Strahil Nikolov On Thu, Dec 2, 2021 at 9:48, Joseph Goldman wrote: Sorry to be clearer There is 15 Spin disks total 9 SSD disks total Spin will be split into 3x RAID-5's on the physical hosts (5 disks) SSD will be split into 3x RAID-5's on the physical hosts (3 disks) My plan was as you said, create a single brick on each of the 3 spin RAID-5's and a single brick on each of the 3 SSD RAID-5's - just wasn't sure if there was a better way to go about it. Thanks, Joe -- Original Message -- From: "dhanaraj.ramesh--- via Users" To: users@ovirt.org Sent: 2/12/2021 5:40:47 PM Subject: [ovirt-users] Re: oVirt 3 Node with GlusterFS >if you go with RAID 5 option it is expected to have performance degradation >but you will have double protection for your data. > >my suggestion, go with each HDD disks as individual bricks with replica 3 >volumes and same for SSD's >___ >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/6777XHHUNWWFXWPN7VNKJC35QHS4JDE5/ ___ 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/IX7ECAXCG3PTHDVPY6JT5GQFP2TV2W4O/ ___ 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/GUYTHI2W247WLIHBTXKFHEZCLVMVHGZG/
[ovirt-users] Re: broker.log file filling up
You need to restart ovirt-ha-broker.service and ovirt-ha-agent.service Best Regards,Strahil Nikolov On Mon, Nov 29, 2021 at 18:31, Valerio Luccio wrote: ___ 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/ABCACVKMVJ6YE2UE2TSOAQSFUOXRWNMN/ ___ 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/7DKRCZFI6P2RVCWFYCCARPXQMFWZVU7A/
[ovirt-users] Re: How to set Disk profile via REST API?
I mean $hostname $description $cluster $template $disk_profile < How please? :-D 1 $cpu 1 $ramMB true $ramMBguaranteed $ramMBmax ___ 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/PP3WBLW22NQJRSVCUNSAHGNB3L4FIVKT/
[ovirt-users] Re: Questions about VDSM communication protocol
On Thu, Dec 2, 2021 at 9:22 AM Artur Socha wrote: > Hi Henry, > Let me answer your questions at least partially. > > Stomp provides a simplified protocol for the messaging which at a time > greatly helped effectively adding new functionalities. > > We do not have any development plans to separate the broker. AFAIK, in the > past there were some attempts to use Rabbit MQ but that has never left the > PoC stage(please somebody correct me if I am wrong). The current > implementation with internal broker is performant enough (and reliable) to > support huge installations (I cannot find relevant documentation right now, > hopefully others will post urls) and gives enough flexibility to implement > new messaging flows. By huge I mean hundreds of hosts and thousands of VMs > communicating with each other. > > @Piotr Kliczewski @Martin Perina > Would you like to add anything more? > In general the motivation was to make the transport layer asynchronous and allow for push notifications from vdsm. In the initial phase we were exploring a need for a broker and after some exploration and testing decided not to do it. We came to a point where transport was no longer a bottleneck. There were other parts (engine mostly) which would need to be improved to scale further. Please let me know if you any further questions > > Artur > > > > On Thu, Dec 2, 2021 at 2:31 AM Henry lol > wrote: > >> Hello, >> >> 1. I know vdsm communication adopted rpc over "stomp" and i'm wondering >> if it's due to use of the message broker or any other purpose. >> >> 2. according to >> https://www.ovirt.org/develop/release-management/features/infra/jsonrpc.html, >> vdsm has the final plan to completely separate msg broker. Is it still >> valid and under development? >> >> 3. if so, why is vdsm trying to use msg broker? because it seems enough >> even without msg broker. >> >> >> thanks, >> ___ >> 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/EREUPD7LZIFV6YUKSK3NYD64ENPRS2ZX/ >> > > > -- > Artur Socha > Senior Software Engineer, RHV > Red Hat > ___ 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/TAI4HVGLFR2TYX3ZO2FSXPUGRABWPR3K/
[ovirt-users] Re: Questions about VDSM communication protocol
Hi Henry, Let me answer your questions at least partially. Stomp provides a simplified protocol for the messaging which at a time greatly helped effectively adding new functionalities. We do not have any development plans to separate the broker. AFAIK, in the past there were some attempts to use Rabbit MQ but that has never left the PoC stage(please somebody correct me if I am wrong). The current implementation with internal broker is performant enough (and reliable) to support huge installations (I cannot find relevant documentation right now, hopefully others will post urls) and gives enough flexibility to implement new messaging flows. By huge I mean hundreds of hosts and thousands of VMs communicating with each other. @Piotr Kliczewski @Martin Perina Would you like to add anything more? Artur On Thu, Dec 2, 2021 at 2:31 AM Henry lol wrote: > Hello, > > 1. I know vdsm communication adopted rpc over "stomp" and i'm wondering if > it's due to use of the message broker or any other purpose. > > 2. according to > https://www.ovirt.org/develop/release-management/features/infra/jsonrpc.html, > vdsm has the final plan to completely separate msg broker. Is it still > valid and under development? > > 3. if so, why is vdsm trying to use msg broker? because it seems enough > even without msg broker. > > > thanks, > ___ > 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/EREUPD7LZIFV6YUKSK3NYD64ENPRS2ZX/ > -- Artur Socha Senior Software Engineer, RHV Red Hat ___ 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/A5JWGPTUSXVVDOENXW2VCSD6CCN24ONQ/
