[all] [oslo.messaging] Interest in collaboration on a NATS driver

Tobias Urdin tobias.urdin at binero.com
Mon Sep 5 07:51:57 UTC 2022


Thanks! It seems that we have some traction here to get started in a more structured manner.

I’m on PTO today but back tomorrow, what do people feel about scheduling a recurring meeting about this topic? I still
need to read through the old spec and old implementation of NATS, and I am a bit restricted on time currently but we
could brainstorm in that meeting and get us started on a new/updated the other spec.

Should also note that, to anybody interested, that the topic is a little bit more broader than just a new messaging driver
as it includes planning and/or working around the usage of eventlet etc, if you are interested in that topic please also
reach out to us!

Best regards
Tobias

> On 2 Sept 2022, at 10:35, Felix Hüttner <felix.huettner at mail.schwarz> wrote:
> 
> +1, we would also be interested in helping out. Let me know where we can help out with reviews, writing code, testing, etc.
> 
> --
> Felix Huettner
> 
>> +1, I'm also interested in this topic. I did some tests with nats-py to see how it works and I'm volunteering to go further with this technology.
>> Let me know if you need reviews, help etc...
>> 
>> Le jeu. 1 sept. 2022 à 15:50, Tobias Urdin <mailto:tobias.urdin at binero.com> a écrit :
>> Hello Kai,
>> 
>> Great to hear that you're interested!
>> I'm currently just testing this as a POC directly in devstack so there is real-world testing (not should it yet I think, needs more development first).
>> 
>> Best regards
>> Tobias
>> 
>>> On 30 Aug 2022, at 18:32, Kai Bojens <mailto:kb at kbojens.de> wrote:
>>> 
>>> Am 29.08.22 um 15:46 schrieb Tobias Urdin:
>>> 
>>>> If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to
>>>> reach out. I'm hoping somebody will bite but atleast I've put it out there for all of you.
>>> 
>>> Hi,
>>> I am very much interested to take a closer look at your work and maybe contribute to it. Although I'm working with OpenStack for my employer at the moment, I'd do this in my spare time as I'm not sure that I can convince him to add another staging system with a full OpenStack installation just for developing a RabbitMQ replacement. That's not on our agenda as we are mostly users and not developers of OpenStack.
>>> 
>>> As I'm pretty new to the messaging topic and had just heard of NATS and your idea, I'll first would have to dive into NATS and then I would take a closer look at your code and maybe try to create some documentation or tests. So, I can't promise anything but as I said I'm very interested in your approach as I also see the massive load from RabbitMQ.
>>> 
>>> This brings me to the most important question: Where do you run and test your code?
>>> 
>>> Greetings,
>>> Kai
> 
> Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.



More information about the openstack-discuss mailing list