I looked more at this solution and am struggling to come up with a solution for: <https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L69-L85>
https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L69-L85 That doesn't involve creating a task per file. Any ideas? Regards -steve From: Steven Dake <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, June 23, 2016 at 6:07 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [openstack-dev] [kolla] better solution for the non-ini format configure file Looks like a really cool feature, and possibly a way to non-ini files, such as policy.json files which we just want to copy rather then override. Kolla already has ini merging for ini files though and the example you provide is an ini file. I like Kolla's ini merging, and it is sort of an external interface, since operators have been using it, so to remove it would mean following the deprecation cycle. I do agree this would be fantastic for straight copies of non-ini configuration files. Regards -steve From: OpenStack Mailing List Archive <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, June 22, 2016 at 8:47 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [openstack-dev] [kolla] better solution for the non-ini format configure file Link: https://openstack.nimeyo.com/83165/?show=88496#a88496 From: AndrewLiu <[email protected]<mailto:[email protected]>> Recently, we find this feature of ansible: http://docs.ansible.com/ansible/playbooks_loops.html#finding-first-matched-files<https://openstack.nimeyo.com/tag/finding-first-matched-files> A specific path of template file can be add in the ansible task. If a user want to customize an non-ini template file, the user can copy the template file to the customization directory, and modify the template file as the user wants. An example of how to modify the ansible task: change from: - name: Copying over horizon.conf template: src: "{{ item }}.conf.j2" dest: "{{ node_config_directory }}/{{ item }}/{{ item }}.conf" with_items: - "horizon" to: - name: Copying over horizon.conf template: src: "{{ item }}" dest: "{{ node_config_directory }}/horizon/horizon.conf" with_first_found: - "{{ node_custom_config }}/horizon.conf.j2" - "horizon.conf.j2" But a convention of how to organize the directory structure of customization template files should be addressed.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
