From 0007d3325d22e27cac938aeb0cd7f914c469b5b2 Mon Sep 17 00:00:00 2001
From: Sam Yaple <sam@yaple.net>
Date: Mon, 27 Jul 2015 10:38:35 +0000
Subject: Properly use groups throught Ansible

Additionally, make each service optional witha config option allowing
for extreme flexibility should the deployer want to replace a service
with a non-kolla one (the database for example).

Change-Id: I7b644da7cfa7e8e6b6878eb1b1aa97db830504ae
Closes-Bug: #1478509
---
 etc/kolla/defaults.yml | 11 +++++++++++
 1 file changed, 11 insertions(+)

(limited to 'etc')

diff --git a/etc/kolla/defaults.yml b/etc/kolla/defaults.yml
index e2ab12d11..5ed397cbf 100644
--- a/etc/kolla/defaults.yml
+++ b/etc/kolla/defaults.yml
@@ -32,3 +32,14 @@ glance_registry_port: "9191"
 nova_api_port: "8774"
 
 neutron_server_port: "9696"
+
+
+# These roles are required for Kolla to be operation, however a savvy deployer
+# could disable some of these required roles and run thier own services.
+enable_glance: "yes"
+enable_haproxy: "yes"
+enable_keystone: "yes"
+enable_mariadb: "yes"
+enable_neutron: "yes"
+enable_nova: "yes"
+enable_rabbitmq: "yes"
-- 
cgit v1.2.3