Carlos Camacho 44ef2a3ec1 Change template names to rocky
The new master branch should point now to rocky.

So, HOT templates should specify that they might contain features
for rocky release [1]

Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.

[1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky
Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
2018-05-09 08:28:42 +02:00

37 lines
726 B
YAML

heat_template_version: rocky
parameters:
network:
type: string
default: ctlplane
fixed_ips:
default: []
type: json
name:
type: string
replacement_policy:
type: string
default: AUTO
ControlPlaneSubnet:
default: ctlplane-subnet
description: The name of the undercloud Neutron control plane subnet
type: string
resources:
ControlPlanePort:
type: OS::Neutron::Port
properties:
network: ctlplane
fixed_ips: [{subnet: {get_param: ControlPlaneSubnet}}]
name:
list_join:
- '-'
- - {get_param: name}
- port
replacement_policy: AUTO
outputs:
fixed_ips:
value: {get_attr: [ControlPlanePort, fixed_ips]}