Hi all, I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL. Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci@na.infn.it
Hello, you could use both version. I've tested both version of RabbitMQ, it worked fine. thanks 이 이메일에는 법적으로 보호받는 정보 또는 기밀사항이 포함되어 있을 수 있습니다. 당사의 동의 없는 이메일의 복사, 전달 및 사용 등 활용을 엄격히 금하며, 이를 위반 시 당사에 대한 민·형사상 책임이 발생할 수 있습니다. 만일 귀하가 정상적인 수신인이 아닐 경우 당사(legal@okestro.com)로 연락하여 주시고, 이메일과 첨부자료를 영구히 삭제하여 주시기 바랍니다. This email may contain information that is legally protected or confidential. Unauthorized use, copying, forwarding, or any other use of this email is strictly forbidden and may lead to legal actions against the violator. If you are not the intended recipient, please notify us immediately at legal@okestro.com and permanently delete this email and its attachments from your system. <hr dze_content_sep=""> 보내는사람: Francesco Di Nucci <francesco.dinucci@na.infn.it> 받는사람 : openstack-discuss <openstack-discuss@lists.openstack.org>,users@lists.rdoproject.org 보낸 날짜 : 2026-01-15 18:44 제목 : RabbitMQ version for OpenStack Epoxy Hi all, I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL. Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci@na.infn.it
Hi, we upgraded to Epoxy last year as well. Since our cloud runs on (Ubuntu) packages (not containerized), we were kind of forced to upgrade RabbitMQ as well (if we didn't want to fiddle with locking packages etc.). The transition wasn't very smooth in that regard though, we had to use RabbitMQ containers to gradually upgrade from 3.9 to 3.10 and 3.11. The RabbitMQ package version for Ubuntu 24 was 3.12, and we couldn't just skip because of missing features which had to be enabled in 3.10/3.11. So there was a short downtime for the services because we couldn't make it work with mixed versions. So we shut down RabbitMQ, started a 3.10 container mapping the rabbit database, stopped it, started a 3.11 container, stopped it. Then started the rabbit systemd service again. I hope we don't have to do it this way too often. :-D Maybe at some point we will decide to migrate to kolla-ansible, I don't know. For now we'll stay on packages as long as possible. Regards, Eugen Zitat von Francesco Di Nucci <francesco.dinucci@na.infn.it>:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email: francesco.dinucci@na.infn.it
Thanks, luckily I can have a downtime, so I can skip some intermediate releases even if it halts operations -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci@na.infn.it On 15/01/26 11:41, Eugen Block wrote:
Hi,
we upgraded to Epoxy last year as well. Since our cloud runs on (Ubuntu) packages (not containerized), we were kind of forced to upgrade RabbitMQ as well (if we didn't want to fiddle with locking packages etc.). The transition wasn't very smooth in that regard though, we had to use RabbitMQ containers to gradually upgrade from 3.9 to 3.10 and 3.11. The RabbitMQ package version for Ubuntu 24 was 3.12, and we couldn't just skip because of missing features which had to be enabled in 3.10/3.11. So there was a short downtime for the services because we couldn't make it work with mixed versions. So we shut down RabbitMQ, started a 3.10 container mapping the rabbit database, stopped it, started a 3.11 container, stopped it. Then started the rabbit systemd service again. I hope we don't have to do it this way too often. :-D Maybe at some point we will decide to migrate to kolla-ansible, I don't know. For now we'll stay on packages as long as possible.
Regards, Eugen
Zitat von Francesco Di Nucci <francesco.dinucci@na.infn.it>:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email: francesco.dinucci@na.infn.it
On 1/15/26 10:44 AM, Francesco Di Nucci wrote:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
Hi, Not sure about RDO and CentOS/Red Hat, but you have to know RabbitMQ 4.x doesn't have HA queues anymore. So if you are to upgrade, you must switch to quorum queues. Not sure as well if your system supports it. Cheers, Thomas Goirand (zigo)
Thanks, until now I was using a single node, now the deployment has scaled and I'll go for a cluster, so quorum queues be it :) -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci@na.infn.it On 16/01/26 09:53, Thomas Goirand wrote:
On 1/15/26 10:44 AM, Francesco Di Nucci wrote:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
Hi,
Not sure about RDO and CentOS/Red Hat, but you have to know RabbitMQ 4.x doesn't have HA queues anymore. So if you are to upgrade, you must switch to quorum queues. Not sure as well if your system supports it.
Cheers,
Thomas Goirand (zigo)
hi, I totally agree that you should target using quorum queues. You may also want to use stream queues and queue consistent naming, ending with a config like this: [oslo_messaging_rabbit] rabbit_quorum_queue = True rabbit_transient_quorum_queue = True rabbit_qos_prefetch_count = 1 use_queue_manager = True rabbit_stream_fanout = True or similar. Finally I recommend upgrade to the latest rabbitmq version since a lot of fixes for quorum queues were added in the last releases. Cheers, Arnaud. On 16.01.26 - 14:29, Francesco Di Nucci wrote:
Thanks,
until now I was using a single node, now the deployment has scaled and I'll go for a cluster, so quorum queues be it :)
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email: francesco.dinucci@na.infn.it
On 16/01/26 09:53, Thomas Goirand wrote:
On 1/15/26 10:44 AM, Francesco Di Nucci wrote:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
Hi,
Not sure about RDO and CentOS/Red Hat, but you have to know RabbitMQ 4.x doesn't have HA queues anymore. So if you are to upgrade, you must switch to quorum queues. Not sure as well if your system supports it.
Cheers,
Thomas Goirand (zigo)
participants (5)
-
Arnaud Morin
-
Eugen Block
-
Francesco Di Nucci
-
Thomas Goirand
-
홍민기