<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I looked more at this solution and am struggling to come up with a solution for:</div>
<div><a href="https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L69-L85"></a>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures"><a href="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</a></span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures"><br>
</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures">That doesn't involve creating a task per file.</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures"><br>
</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures">Any ideas?</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures"><br>
</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures">Regards</span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures">-steve</span></p>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Steven Dake <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, June 23, 2016 at 6:07 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla] better solution for the non-ini format configure file<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>OpenStack Mailing List Archive <<a href="mailto:corpqa@gmail.com">corpqa@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, June 22, 2016 at 8:47 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla] better solution for the non-ini format configure file<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>Link: <a href="https://openstack.nimeyo.com/83165/?show=88496#a88496">https://openstack.nimeyo.com/83165/?show=88496#a88496</a><br>
From: AndrewLiu <<a href="mailto:andrew.lhj@gmail.com">andrew.lhj@gmail.com</a>><br>
<br>
<p>Recently, we find this feature of ansible:<br>
<a rel="nofollow" href="http://docs.ansible.com/ansible/playbooks_loops.html">http://docs.ansible.com/ansible/playbooks_loops.html</a><a rel="nofollow" href="https://openstack.nimeyo.com/tag/finding-first-matched-files">#finding-first-matched-files</a></p>
<p>A specific path of template file can be add in the ansible task.</p>
<p>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.</p>
<p>An example of how to modify the ansible task:</p>
<p>change from:</p>
<pre><code>- name: Copying over horizon.conf
template:
src: "{{ item }}.conf.j2"
dest: "{{ node_config_directory }}/{{ item }}/{{ item }}.conf"
with_items:
- "horizon"
</code></pre>
<p>to:</p>
<pre><code>- 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"
</code></pre>
<p>But a convention of how to organize the directory structure of customization template files should be addressed.</p>
</div>
</div>
</blockquote>
</span></div>
</div>
</blockquote>
</span>
</body>
</html>