Folks, it seems the situation with Kilo support for RabbitMQ heartbeats should be elaborated. There is a bug [0] and a ML [1] related. The questions are: a) Should Fuel 7.0 with Kilo *explicitly* disable via puppet the upstream implementation of heartbeats for all OpenStack components (Neutron example [2]) and keep the MOS specific implementation of heartbeats configured the same way as it was for Juno? b) Or should we change nothing additionally allowing Oslo defaults for Kilo being populated for heartbeats settings out of box? Related question - what are upstream heartbeat defaults in MOS, do they differ to upstream ones? [0] https://bugs.launchpad.net/fuel/+bug/1477689 [1] http://lists.openstack.org/pipermail/openstack-dev/2015-July/068751.html [2] https://review.openstack.org/#/c/194381/ -- Best regards, Bogdan Dobrelya, Irc #bogdando