ju
/
openinfraday
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Autocommit action=MODIFY on file=Follow the RabbitMQ - Plan.md detected

This commit is contained in:
Flatnotes 2024-05-05 20:45:15 +00:00
parent dab4bb0364
commit 92d3588542
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Follow the RabbitMQ - Plan.md
View File

@ -3,7 +3,6 @@
> What kind of issues we faced with rabbit > What kind of issues we faced with rabbit
> Is it a RabbitMQ setup issue or an Openstack issue ? > Is it a RabbitMQ setup issue or an Openstack issue ?
* Issues with rabbit ? * Issues with rabbit ?
* flap when rolling out agent / deploying new agent version * flap when rolling out agent / deploying new agent version
* even crash on big regions * even crash on big regions
@ -13,7 +12,6 @@
> Which methods did we use to troubleshoot those issues > Which methods did we use to troubleshoot those issues
> Observability, tools > Observability, tools
* What's going on with rabbit ? * What's going on with rabbit ?
* What we deployed to help troubleshooting issues * What we deployed to help troubleshooting issues
* reproduce workload with rabbit perftest * reproduce workload with rabbit perftest
@ -33,7 +31,6 @@
> Before going further, let's take some time to understand how oslo.messaging work > Before going further, let's take some time to understand how oslo.messaging work
> How RPC is implemented in Openstack > How RPC is implemented in Openstack
> [[ oslo.messaging - How it works with rabbit]] > [[ oslo.messaging - How it works with rabbit]]
* Under the hood ? * Under the hood ?
* pub/sub mechanism * pub/sub mechanism
* subscriber: RPC server topic=name * subscriber: RPC server topic=name
@ -46,7 +43,6 @@
* notifications for external use: kafka * notifications for external use: kafka
> What we did to put rabbits back to their holes > What we did to put rabbits back to their holes
* Journey to get a stable infra. * Journey to get a stable infra.
* Infra improvment * Infra improvment
* split rabbit-neutron / rabbit-\* * split rabbit-neutron / rabbit-\*
@ -64,3 +60,9 @@
* patch to avoid tcp reconnection when a queue is deleted (kombu/oslo) * patch to avoid tcp reconnection when a queue is deleted (kombu/oslo)
* reduce queues declared by a RPC server (3 queues by default to only 1) * reduce queues declared by a RPC server (3 queues by default to only 1)
* use same connection for mutiple topics * use same connection for mutiple topics
> ...
- Conclusion
- when rabbitmq is used for what it is designed for, it works better
- going further ?
- let's write an oslo.messaging driver for another backend ?