The queue TTL happens on reply queues and fanout queues. I don’t think it
should happen on fanout queues. They should auto delete. I can understand the
reason for having them on reply queues though so maybe that would be a way to
forward?
Or am I missing something and it is needed on fanout que
I am new to openstack. I followed the initial openstack guild "OpenStack
Installation Guide for Red Hat Enterprise Linux and CentOS" with options 1
network. Everything else work well but failed in networking site.My vm
instance cannot get ip address from DHCP.
After further troubleshootin
Yeah, we've experienced it but hadn't had time yet to really dig in like this,
or gotten a good workaround. If you file a bug, please let me know what number.
Thanks,
Kevin
From: Sam Morrison [sorri...@gmail.com]
Sent: Sunday, July 24, 2016 11:27 PM
To: Op
Ah. Interesting.
The graceful shutdown would really help the Kubernetes situation too.
Kubernetes can do easy rolling upgrades and having the processes being able to
clean up after themselves as they are upgraded is important. Is this something
that needs to go into oslo.messaging or does it ha
I have filed a bug in oslo.messaging to track the issue [1] and my
colleague Kirill Bespalov posted a fix for it [2].
We have checked the fix and it is working for neutron-server, l3-agent and
dhcp-agent. It does not work for openvswitch-agent and metadata-agent
meaning they do not stop RPC server
Hello all,
Sorry for the delay there and skipping the last meeting - wasn't able to
find anyone to run it after asking some of the usual suspects.
The good news is, we have a meeting tomorrow!
==Next Meeting==
Unless there is further discussion, this the next meeting is at:
==> Tuesday, 26 o
Sam,
For your case I would suggest to lower rabbit_transient_queues_ttl until
you are comfortable with volume of messages which comes during that time.
Setting the parameter to 1 will essentially replicate bahaviour of
auto_delete queues. But I would suggest not to set it that low, as
otherwise yo
