tripleo-heat-templates/puppet/services/masquerade-networks.yaml
Emilien Macchi 6f3e70313e masquerade: stop using YAQL for iptables data
See https://bugs.launchpad.net/tripleo/+bug/1760211 but the YAQL + Heat
format hasn't helped us to build the data needed by Puppet to create
IPtables rules for masquerading.

We'll solve it in puppet-tripleo with native hash iterations, so for
that we just export MasqueradeNetworks to Hiera and we'll use this data
from the puppet module directly.

Depends-On: I8dda3c164de90954855979529de4f1100a858b45

Related-Bug: #1760211
Change-Id: I81379cf93f505fb65c1ad7e6a2adcc6942b04bc0
2018-04-04 20:48:55 +00:00

48 lines
1.4 KiB
YAML

heat_template_version: queens
description: >
Configure TripleO Masquerade networks with Puppet.
parameters:
ServiceData:
default: {}
description: Dictionary packing service data
type: json
ServiceNetMap:
default: {}
description: Mapping of service_name -> network name. Typically set
via parameter_defaults in the resource registry. This
mapping overrides those in ServiceNetMapDefaults.
type: json
DefaultPasswords:
default: {}
type: json
RoleName:
default: ''
description: Role name on which the service is applied
type: string
RoleParameters:
default: {}
description: Parameters specific to the role
type: json
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
MasqueradeNetworks:
default: {'192.168.24.0/24': ['192.168.24.0/24', '192.168.25.0/24']}
description: Hash of masquerade networks to manage.
type: json
outputs:
role_data:
description: Role data for the TripleO Masquerade Networks service.
value:
service_name: masquerade_networks
config_settings:
masquerade_networks: {get_param: MasqueradeNetworks}
step_config: |
include tripleo::masquerade_networks
upgrade_tasks: []