Hi, The generation of Neutron configuration files using the oslo config generator is being introduced in Mitaka as part of blueprint [1] and bug [2]. This is broken down into two phases: Neutron core and Neutron *aaS projects. The first part of the first phase is the generation of sample core configuration files in patch [3]. The next part is the removal of the sample configuration files from the core repository in patch [4]. Patch [3] and [5] make the static sample configuration files in the Neutron repository redundant. Developers should no longer update these configuration files as they will be removed in patch[4]. Refer to the Neutron contribution guide for more details. The final phase of the blueprint is the update of the Neutron *aaS projects for configuration generation. These commits will be associated to bug [2]. It is advised that Neutron sub-projects do not keep their configuration files in their respective trees and instead generate them using a similar approach as Neutron does. Operators should refer to the release notes for more details. [1] https://blueprints.launchpad.net/neutron/+spec/autogen-neutron-conf-file [2] https://bugs.launchpad.net/neutron/+bug/1199963 [3] https://review.openstack.org/#/c/204206/ [4] https://review.openstack.org/#/c/251348/ [5] https://review.openstack.org/#/c/204722/ Regards, Martin