On Thu, Dec 2, 2021 at 9:22 AM Artur Socha <asocha@redhat.com> 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 <pub.virtualization@gmail.com> 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-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/EREUPD7LZIFV6YUKSK3NYD64ENPRS2ZX/

--
Artur Socha
Senior Software Engineer, RHV
Red Hat