Re: [openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

2017-09-25 Thread Miguel Angel Ajo Pelayo
--- Mail original - > > De: "Miguel Angel Ajo Pelayo" <majop...@redhat.com> > > À: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > Envoyé: Mercredi 20 Septembre 2017 11:15:12 > &

Re: [openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

2017-09-24 Thread Matthieu Simonin
- Mail original - > De: "Miguel Angel Ajo Pelayo" <majop...@redhat.com> > À: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Envoyé: Mercredi 20 Septembre 2017 11:15:12 > Objet: Re: [openstack-d

Re: [openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

2017-09-20 Thread Miguel Angel Ajo Pelayo
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 completely fine. Sadly I don't keep the test examples, I should have stored them in github or something. It shouldn't be hard to

[openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

2017-09-20 Thread Matthieu Simonin
Hello, In the Neutron docs about RPCs and Callbacks system, it is said[1] : "With the underlying oslo_messaging support for dynamic topics on the receiver we cannot implement a per “resource type + resource id” topic, rabbitmq seems to handle 1’s of topics without suffering, but creating