From c5f686ac43e258fab16d2d9d50d26ab7ea205c0e Mon Sep 17 00:00:00 2001 From: Ryan Hallisey Date: Wed, 18 May 2016 13:04:14 -0400 Subject: [PATCH] Generate configuration using ansible for any project Give outside projects the ability to consume kolla-ansible as a config generation mechanism by allowing for the developer to define a directory structure within /etc/kolla that fits a project's needs. For example, kolla-kubernetes does not define configuration in terms of serivces, but in terms of pods (groups of services). Partially implements: blueprint multi-project-config Change-Id: If08443aefcaf5fa5604b243b39a6a2d54e431cff --- ansible/group_vars/all.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ansible/group_vars/all.yml b/ansible/group_vars/all.yml index 8d9f408fdf..7236b6a6c2 100644 --- a/ansible/group_vars/all.yml +++ b/ansible/group_vars/all.yml @@ -6,8 +6,11 @@ # again. Persistent files allow for idempotency container_config_directory: "/var/lib/kolla/config_files" +# The project to generate configuration files for +project: "" + # The directory to store the config files on the destination node -node_config_directory: "/etc/kolla" +node_config_directory: "/etc/kolla/{{ project }}" ###################