tripleo-heat-templates/deployed-server/deployed-server-config.yaml
James Slagle c3d595c49a Use already Deployed/Installed servers
This patch provides a set of templates that enables
tripleo-heat-templates to be used with a set of already deployed,
installed, and running servers. In this method, Nova and Ironic are not
used to deploy any servers.

This approach is attractive for POC deployments where dedicated
provisioning networks are not available, or other server install methods
are dictated for various reasons.

There are also assumptions that currently have to be made about the software
installed on the already deployed servers.  Effectively, they must match the
standard TripleO overcloud-full image.

Co-Authored-By: Steve Hardy <shardy@redhat.com>

Change-Id: I4ab1531f69c73457653f1cca3fe30cc32a04c129
2016-07-11 16:20:07 -04:00

23 lines
652 B
YAML

heat_template_version: 2014-10-16
parameters:
user_data_format:
type: string
default: SOFTWARE_CONFIG
resources:
# We just need something which returns a unique ID, but we can't
# use RandomString because RefId returns the value, not the physical
# resource ID, SoftwareConfig should work as it returns a UUID
deployed-server-config:
type: OS::Heat::SoftwareConfig
outputs:
# FIXME(shardy) this is needed because TemplateResource returns an
# ARN not a UUID, which overflows the Deployment server_id column..
user_data_format:
value: SOFTWARE_CONFIG
OS::stack_id:
value: {get_resource: deployed-server-config}