Comment 2 for bug 1836650

Radoslaw, I put Keystone because for the end-user (operators) that is what is going to look like at first sight. You use Kolla-ansible thinking that it will configure the basic messaging method, but it does not. Therefore, the first thing for us was to see what was going on there. Also, from what you told me, there is a lack of documentation with respect to this feature, that is why I put keystone as an affected project. We can remove it though.

I am confused, I am seeing the comments in the pull request, but I thought we were going to ignore the changes proposed there until we discuss the idea/plan we have with respect to this situation. Before moving on with a proposal to change Kolla-ansible (code-wise), I would like to understand and close on a goal (e.g. remote the feature from Kolla-ansible, change the feature as I initially proposed, and so on). Instead of having these discussions across different systems, this seems to be the right place for them, as you suggested there.

Do I need to take into consideration only your opinion? Or should we wait for other people from the community?