Enable 'auto_delete' of queue's property configurable

[Alex Xu]

Currently TopicConsumer and TopicPublisher declare exchange and queue as auto_delete = False by hardcode. We can enable 'auto_delete' configurable, that used to prevent publisher's rpc messages flood consumer. The reason was if consumer startup later then publisher, the queue will buffer all the message that sent by publisher. After publisher startup, all message that buffered in queue will send to publisher immediately, that may flood the publisher.

qpid didn't have this problem, because qpid backend set auto-delete as default.

So there is inconsistent between qpid and rabbitmq.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/24904

[Mark McLoughlin (markmc)]

Should it really be configurable, or is it that it should be enabled?

[Doug Hellmann (doug-hellmann)]

This doesn't seem like something the deployer needs to control, especially since whether it should be enabled depends on the topic. For example, ceilometer would never want notifications discarded.

[Alex Xu (xuhj)]

qpid backend have already enabled auto-delete. If we shouldn't enable this, there will be a bug for qpid.

[Doug Hellmann (doug-hellmann)]

I agree that qpid and Korbut should act the same way. I don't think that requires adding a configuration setting, though. It is not clear why the user would ever change the setting.

[Alexey Khivin (akhivin)]

Is this issue the same as
https://bugs.launchpad.net/oslo.messaging/+bug/1366597