tripleo-heat-templates/deployment/deprecated/masquerade-networks/masquerade-networks-baremetal-puppet.yaml
Cédric Jeanneret b1b989471d Manage masquerade via Ansible instead of Puppet
This last step should allow to get rid of the puppet-firewall module.

Change-Id: I8fbe512a8fd2f281e0e74c5db061a1d03b085527
2022-05-30 06:55:05 +00:00

45 lines
1.3 KiB
YAML

heat_template_version: wallaby
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. Use
parameter_merge_strategies to merge it with the defaults.
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: []