23, 2016 at 6:07 AM
To:
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla] better solution for the non-ini format
configure file
Looks like a really cool feature, and possibly a w
o:openstack-dev@lists.openstack.org>>
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 mailto:andrew@gmail.com>>
Recently, we find this feature of ansible:
http:
Link: https://openstack.nimeyo.com/83165/?show=88496#a88496
From: AndrewLiu
Recently, we find this feature of ansible:http://docs.ansible.com/ansible/playbooks_loops.html#finding-first-matched-files
A specific path of template file can be add in the ansible task.
If a user want to customize an
On 5/5/16, 4:52 AM, "Paul Bourke" wrote:
>TL;DR keep globals.yml to a minimum, customise configs via
>host_vars/group_vars
>
>It seems right now the "best" approach may be to tokenise variables as
>required. This is the approach we currently use in Oracle. There are two
>other approaches I can
TL;DR keep globals.yml to a minimum, customise configs via
host_vars/group_vars
It seems right now the "best" approach may be to tokenise variables as
required. This is the approach we currently use in Oracle. There are two
other approaches I can think of available to us:
1) The overwrite me
I agree with your approach Jeffrey, although this is not ideal, this is an
approach already used in kolla.
2016-05-04 12:01 GMT-03:00 Jeffrey Zhang :
> Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the
> globals.yml file.
> Because there is no chance to change the horizon/apac
Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the
globals.yml file.
Because there is no chance to change the horizon/apache configure file now.
The root cause is that: Kolla do not support non-ini format configure file.
for the
ini-format file, we use a merge_config module[1] t
