3a8ab855a8
The idea here is to provide a way for magnum to discover and interact with templates meant to build bays. Template definition discovery is done through python entry_points, and each class lists the bay_types it can provide. Each template definition contains a mapping of magnum object attributes and heat template parameters/outputs. This will be useful for not only allowing different CoEs, OSes, and platforms. But can also provide the discovery mechanism for templates once they are pulled into their own repository. Partial-Implements: bp multiple-bay-templates Change-Id: Ia596657856cd861c94e58dcd65acae0677a36d73
45 lines
851 B
YAML
45 lines
851 B
YAML
heat_template_version: 2013-05-23
|
|
|
|
description: >
|
|
This is just an example template. It does not produce a usable bay.
|
|
|
|
parameters:
|
|
#
|
|
# REQUIRED PARAMETERS
|
|
#
|
|
ssh_key_name:
|
|
type: string
|
|
description: name of ssh key to be provisioned on our server
|
|
|
|
#
|
|
# OPTIONAL PARAMETERS
|
|
#
|
|
server_image:
|
|
type: string
|
|
default: centos-atomic
|
|
description: glance image used to boot the server
|
|
|
|
server_flavor:
|
|
type: string
|
|
default: m1.small
|
|
description: flavor to use when booting the server
|
|
|
|
resources:
|
|
|
|
example_server:
|
|
type: "OS::Nova::Server"
|
|
properties:
|
|
image:
|
|
get_param: server_image
|
|
flavor:
|
|
get_param: server_flavor
|
|
key_name:
|
|
get_param: ssh_key_name
|
|
|
|
outputs:
|
|
|
|
server_address:
|
|
value: {get_attr: [example_server, accessIPv4]}
|
|
|
|
node_addresses:
|
|
value: [] |