Use custom role names in deployed-server roles
authorJames Slagle <jslagle@redhat.com>
Fri, 13 Jan 2017 20:17:14 +0000 (15:17 -0500)
committerJames Slagle <jslagle@redhat.com>
Mon, 16 Jan 2017 15:48:00 +0000 (10:48 -0500)
commit62a84e777b97ece95c4230986b754f26d1edf59c
tree6edb0e41cff66723f5ba5f76b327b1ebe356271d
parentc913d9b683af205cea0d4d7498d50e5931fca08a
Use custom role names in deployed-server roles

Custom role names need to be used in the deployed server role files,
otherwise the new customized roles are not generated by jinja since the
default roles are excluded from templating in j2_excludes.yaml.

This patch also removes the OS::TripleO::Services::Core service that was
recently removed from the default Controller role as well in
I48cd2b6a4593d673d5883b45feae088392e7e713

Partially-implements: blueprint split-stack-software-configuration
Change-Id: I60cb60382d472cd093f07e134245f666029f3b16
deployed-server/deployed-server-roles-data.yaml