[openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint
Miguel Angel Ajo Pelayo
majopela at redhat.com
Wed Sep 20 09:15:12 UTC 2017
I wrote those lines.
At that time, I tried a couple a publisher and a receiver at that scale. It
was the receiver side what crashed trying to subscribe, the sender was
Sadly I don't keep the test examples, I should have stored them in github
or something. It shouldn't be hard to replicate though if you follow the
On Wed, Sep 20, 2017 at 9:58 AM, Matthieu Simonin <matthieu.simonin at inria.fr
> In the Neutron docs about RPCs and Callbacks system, it is said :
> "With the underlying oslo_messaging support for dynamic topics on the
> we cannot implement a per “resource type + resource id” topic, rabbitmq
> to handle 10000’s of topics without suffering, but creating 100’s of
> oslo_messaging receivers on different topics seems to crash."
> I wonder if this statements still holds for the new transports supported in
> oslo.messaging (e.g Kafka, AMQP1.0) or if it's more a design limitation.
> I'm interested in any relevant docs/links/reviews on the "topic" :).
> Moreover, I'm curious to get an idea on how many different resources a
> Agent would have to manage and thus how many oslo_messaging receivers
> would be
> required (e.g how many security groups a neutron agent has to manage ?) -
> least the order of magnitude.
> : https://docs.openstack.org/neutron/latest/contributor/
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev