Open Stack

Folks,

At the Boston summit the oslo.messaging team decided to deprecate the
pika driver.  It is planned to be removed from oslo.messaging in Rocky
[1].

If you're asking yourself "what's a pika??", read on.

The pika driver was intended to be a replacement for the default
rabbit driver.  It was developed after the RabbitMQ community
recommended using the Pika client library [2] instead of kombu [3],
which is the basis for the default rabbit driver.  The goal was to
create a more performant and stable driver for use with the RabbitMQ
broker.

However, as referenced in [1], there's been no evidence that this
driver is either more stable or better performing than the existing
default rabbit driver. Coupled with the risk of replacing the widely
used default driver with something with less in-the-field exposure
("better the devil you know..."), it doesn't make sense to spend our
development resources trying to support two drivers for RabbitMQ.

Users of the pika driver are recommended to transition to the default
rabbit driver.

"How do I know that this affects me?"

Good question.  Check your configuration for the setting of the
oslo.messaging transport_url option.  If that URL string starts with
"pika://", then you are affected and should transition to the default
rabbit driver by using the "rabbit://" URL schema instead.

And certainly reach out if you have any questions,
thanks

-- 
Ken Giusti  (kgiusti at gmail.com)


[1] https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
[2] https://github.com/pika/pika
[3] https://github.com/celery/kombu