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>

deployment/database/redis-container-puppet.yaml

@@ -62,18 +62,18 @@ outputs:
     description: Role data for the Redis API role.
     value:
       service_name: redis
+      firewall_rules:
+        '108 redis':
+          dport:
+            - 6379
+            - 26379
       config_settings:
         map_merge:
           - {get_attr: [RedisBase, role_data, config_settings]}
           - redis::daemonize: false
             tripleo::stunnel::manage_service: false
             tripleo::stunnel::foreground: 'yes'
-          - tripleo::redis::firewall_rules:
-              '108 redis':
-                dport:
-                  - 6379
-                  - 26379
-            tripleo::profile::base::database::redis::tls_proxy_bind_ip:
+          - tripleo::profile::base::database::redis::tls_proxy_bind_ip:
               str_replace:
                 template:
                   "%{hiera('$NETWORK')}"