On 23.08.2017 00:16, Jean-Philippe Evrard wrote:
> Hello,
>
> The variables documented in each of the roles defaults/ are generally what
> you can consider a user level interface (i.e.: what you can modify), while
> the variables from vars/ are generally what's best to avoid overriding.
>
>
Hello,
The variables documented in each of the roles defaults/ are generally what
you can consider a user level interface (i.e.: what you can modify), while
the variables from vars/ are generally what's best to avoid overriding.
We've been slowly phasing out variables insides templates, to
On 22.08.2017 09:46, Flávio Ramalho wrote:
> Hi Markus,
>
> I think you can achieve what you want by simple overriding the host
> variables, for example:
>
> In /etc/openstack_deploy/openstack_user_config.yml:
> compute_hosts:
>compute1:
> ip: 192.168.100.12
> host_vars:
>
Hi Markus,
I think you can achieve what you want by simple overriding the host
variables, for example:
In /etc/openstack_deploy/openstack_user_config.yml:
compute_hosts:
compute1:
ip: 192.168.100.12
host_vars:
nova_reserved_host_memory_mb: 256
compute2:
ip:
On 21.08.2017 16:40, Andy McCrae wrote:
> Hey Markus,
>
>
>> I'm wondering which possibilities I have to do group/host specific
>> config file overrides. After reading [1], I'm still a little clueless.
>> To be specific, I have this setup (expressed as Ansible inventory file):
>>
>>
Hey Markus,
> I'm wondering which possibilities I have to do group/host specific
> config file overrides. After reading [1], I'm still a little clueless.
> To be specific, I have this setup (expressed as Ansible inventory file):
>
> [z_compute_nodes]
> compute1
> # more nodes
>
I'm wondering which possibilities I have to do group/host specific
config file overrides. After reading [1], I'm still a little clueless.
To be specific, I have this setup (expressed as Ansible inventory file):
[z_compute_nodes]
compute1
# more nodes
[x_compute_nodes]
