QA (public) » openQA Project (public)

After it turned out that the resource allocator could just be removed without adding a replacement, i started to wonder if that might be the case for all our current uses of dbus. While it's not quite as straight forward for the websocket server and scheduler, there might be better options than using redis. I'm currently exploring the use of postgres pub/sub and/or plain HTTP as a replacement for dbus rpc. This might take a little time to figure out due to my limited understanding of the big picture, but the much simpler overall architecture should be worth it.

Also worth mentioning that my original proposal to use redis was based on the assumption that dbus was used for message passing in openQA. But that turned out to be false, in all instances it is used exclusively for blocking RPC.

The websocket server has been refactored into a well structured Mojolicious application now. So everything is prepared for using HTTP as a new RPC mechanism, which will be the next step. https://github.com/os-autoinst/openQA/pull/2037

I've opened a PR https://github.com/os-autoinst/openQA/pull/2043 for replacing D-Bus with HTTP in the websocket server. Now it just needs to be tested on the staging machines.

Opened another (and hopefully final) PR for removing the final traces of D-Bus in openQA. https://github.com/os-autoinst/openQA/pull/2090

deployed on o3 since yesterday without any visible problems. I wonder about one thing: Do we still have AMQP messages output? Not sure if this is related but the only thing I could think of right now that can still go wrong ;)

how is amqp relate to dbus and/or the scheduler?

hopefully not at all :) Just thought maybe some "events" would be hijacked which are not there even more. But if you say it's not the case I am sure we are good.