Allow control of hostname formatting
authorSteven Hardy <shardy@redhat.com>
Mon, 15 Jun 2015 09:13:07 +0000 (05:13 -0400)
committerSteve Baker <sbaker@redhat.com>
Tue, 16 Jun 2015 22:23:09 +0000 (10:23 +1200)
commit1f37302f6b8ef7e6ce8dfe37eba528535493dbf9
tree385276e1674166716cd35a52da8a6e27a75f377a
parent48d07db384a3e8a36a2a92e95ef3ad4ed5c6071e
Allow control of hostname formatting

Currently, we use the heat default server names, which results in some
fairly unreadable hostnames due to the level of nesting in the templates.

e.g ov-sszdbj5rdne-0-bhseh65edxv6-Controller-zoqc6tlypbdp

Instead, we allow the user to specify a format string per role, defaulted
to a string which formats the name e.g <stackname>-controller-<index>

e.g overcloud-controller-0

Optionally additional hostname components (not replaced by heat) could be
added, such that deployment time customization of hostnames via firstboot
scripts (e.g cloud-init) may be possible.

Should anyone wish to maintain the old heat-generated names, they can pass
an empty string via these parameters, which heat will treat as if no "name"
property was provided to OS::Nova::Server.

Change-Id: I1730caa0c2256f970da22ab21fa3aa1549b3f90b
ceph-storage.yaml
cinder-storage.yaml
compute.yaml
controller.yaml
overcloud-without-mergepy.yaml
puppet/ceph-storage-puppet.yaml
puppet/cinder-storage-puppet.yaml
puppet/compute-puppet.yaml
puppet/controller-puppet.yaml
puppet/swift-storage-puppet.yaml
swift-storage.yaml