Allow per node configuration with augments
This type of per node configuration is required to support things like availability zones for nova. As always, if this file doesnt exist it doesnt get used so this change is safe. TrivialFix Change-Id: Iff8172af522c2c96e5f2c173b24a5dfd4d522ed2
Showing
- ansible/roles/ceph/tasks/config.yml 1 addition, 0 deletionsansible/roles/ceph/tasks/config.yml
- ansible/roles/cinder/tasks/config.yml 1 addition, 0 deletionsansible/roles/cinder/tasks/config.yml
- ansible/roles/glance/tasks/config.yml 1 addition, 0 deletionsansible/roles/glance/tasks/config.yml
- ansible/roles/heat/tasks/config.yml 1 addition, 0 deletionsansible/roles/heat/tasks/config.yml
- ansible/roles/ironic/tasks/config.yml 1 addition, 0 deletionsansible/roles/ironic/tasks/config.yml
- ansible/roles/keystone/tasks/config.yml 1 addition, 0 deletionsansible/roles/keystone/tasks/config.yml
- ansible/roles/magnum/tasks/config.yml 1 addition, 0 deletionsansible/roles/magnum/tasks/config.yml
- ansible/roles/manila/tasks/config.yml 1 addition, 0 deletionsansible/roles/manila/tasks/config.yml
- ansible/roles/mariadb/tasks/config.yml 1 addition, 0 deletionsansible/roles/mariadb/tasks/config.yml
- ansible/roles/mistral/tasks/config.yml 1 addition, 0 deletionsansible/roles/mistral/tasks/config.yml
- ansible/roles/murano/tasks/config.yml 1 addition, 0 deletionsansible/roles/murano/tasks/config.yml
- ansible/roles/neutron/tasks/config-neutron-fake.yml 2 additions, 0 deletionsansible/roles/neutron/tasks/config-neutron-fake.yml
- ansible/roles/neutron/tasks/config.yml 2 additions, 0 deletionsansible/roles/neutron/tasks/config.yml
- ansible/roles/nova/tasks/config-nova-fake.yml 1 addition, 0 deletionsansible/roles/nova/tasks/config-nova-fake.yml
- ansible/roles/nova/tasks/config.yml 1 addition, 0 deletionsansible/roles/nova/tasks/config.yml
- ansible/roles/swift/tasks/config.yml 5 additions, 0 deletionsansible/roles/swift/tasks/config.yml
Loading
Please register or sign in to comment