tripleo-heat-templates/deployment/swift
Kevin Carter 50367fbe35 Convert firewall rules to use TripleO-Ansible
This change converts our filewall deployment practice to use
the tripleo-ansible firewall role. This change creates a new
"firewall_rules" object which is queried using YAQL from the
"FirewallRules" resource.

A new parameter has been added allowing users to input
additional firewall rules as needed. The new parameter is
`ExtraFirewallRules` and will be merged on top of the YAQL
interface.

Depends-On: Ie5d0f51d7efccd112847d3f1edf5fd9cdb1edeed
Change-Id: I1be209a04f599d1d018e730c92f1fc8dd9bf884b
Signed-off-by: Kevin Carter <kecarter@redhat.com>
2019-11-18 15:40:22 -06:00
..
external-swift-proxy-baremetal-puppet.yaml Move masq-nets, swift-external, and validations to deployment 2019-05-30 20:37:30 +00:00
swift-base.yaml flatten the swift service configurations 2019-01-26 17:10:27 -05:00
swift-dispersion-baremetal-puppet.yaml flatten the swift service configurations 2019-01-26 17:10:27 -05:00
swift-proxy-container-puppet.yaml Convert firewall rules to use TripleO-Ansible 2019-11-18 15:40:22 -06:00
swift-ringbuilder-container-puppet.yaml Add swift_config puppet-tag for swift-ringbuilder 2019-07-17 14:44:05 +05:30
swift-storage-container-puppet.yaml Convert firewall rules to use TripleO-Ansible 2019-11-18 15:40:22 -06:00