From 1f37302f6b8ef7e6ce8dfe37eba528535493dbf9 Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Mon, 15 Jun 2015 05:13:07 -0400 Subject: 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 -controller- 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 --- controller.yaml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'controller.yaml') diff --git a/controller.yaml b/controller.yaml index 9fc91562..7baa5761 100644 --- a/controller.yaml +++ b/controller.yaml @@ -447,6 +447,9 @@ parameters: description: > Setting to a previously unused value during stack-update will trigger package update on all nodes + Hostname: + type: string + default: '' # Defaults to Heat created hostname resources: @@ -461,6 +464,7 @@ resources: - network: ctlplane user_data_format: SOFTWARE_CONFIG user_data: {get_resource: NodeUserData} + name: {get_param: Hostname} NodeUserData: type: OS::TripleO::NodeUserData -- cgit 1.2.3-korg