tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml
Harald Jensås 679ecaada0 Set dns_name propery on ports and networks
Neutron's dns_assignments field includes a nice pice of
structured data. This is a prerequirement for Designate
usage. (No plan's to use that, but being a bit ready
does'nt hurt.)

  {"hostname": "my-vm",
   "ip_address": "192.0.2.16",
   "fqdn": "my-vm.example.org."}

Enable for the undercloud:
 - dns_domain_ports ml2 extension driver

Change-Id: I46eb9a24dd66821b27524fe4d1fdab617b6fa948
2020-04-03 08:57:38 +02:00

77 lines
1.6 KiB
YAML

heat_template_version: rocky
description: "
A fake OS::Neutron::Port stack which outputs fixed_ips and subnets based on
the input from the DeployedServerPortMap (set via parameter_defaults). This
lookup requires the use of port naming conventions. In order for this to work
with deployed-server the keys should be <hostname>-<network>.
Example:
parameter_defaults:
DeployedServerPortMap:
gatsby-ctlplane:
fixed_ips:
- ip_address: 127.0.0.1
subnets:
- cidr: 127.0.0.0/24
network:
tags:
- 127.0.0.0/24"
parameters:
name:
default: ''
type: string
dns_name:
default: ''
type: string
network:
default: ''
type: string
fixed_ips:
default: ''
type: comma_delimited_list
replacement_policy:
default: ''
type: string
DeployedServerPortMap:
default: {}
type: json
outputs:
fixed_ips:
value:
{get_param: [DeployedServerPortMap, {get_param: name}, fixed_ips]}
subnets:
value:
{get_param: [DeployedServerPortMap, {get_param: name}, subnets]}
network:
value:
{get_param: [DeployedServerPortMap, {get_param: name}, network]}
name:
value: {get_param: name}
status:
value: DOWN
allowed_address_pairs:
value: {}
device_id:
value: ''
device_owner:
value: {get_param: network}
dns_assignment:
value: ''
port_security_enabled:
value: False
admin_state_up:
value: False
security_groups:
value: {}
network_id:
value: ''
tenant_id:
value: ''
qos_policy_id:
value: ''
mac_address:
value: ''