adding taskotron-proxy role for dev

inventory/group_vars/taskotron-dev

@@ -23,5 +23,6 @@ master_user: buildmaster
 external_hostname: taskotron.dev.fedoraproject.org
 resultsdb_url: http://resultsdb-dev01.qa.fedoraproject.org/resultsdb/api/v1.0
 resultsdb_frontend_url: http://resultsdb-dev01.qa.fedoraproject.org/
+resultsdb_endpoint: resultsdb
 landingpage_title: "Taskotron Development"
 deployment_type: dev

playbooks/groups/taskotron-dev.yml

@@ -69,6 +69,7 @@
    - { role: taskotron/buildmaster-configure, tags: ['buildmasterconfig'] }
    - { role: taskotron/taskotron-trigger, tags: ['trigger'] }
    - { role: taskotron/taskotron-frontend, tags: ['frontend'] }
+   - { role: taskotron/taskotron-proxy, tags: ['taskotronproxy'] }
 
   handlers:
    - include: "{{ handlers }}/restart_services.yml"

roles/taskotron/taskotron-proxy/tasks/main.yml

@@ -0,0 +1,17 @@
+# this was designed to be used in dev where there is no global proxy
+# this way, we can get away with a single ip and ssl cert instead of
+# one for taskotron and one for resultsdb. The url scheme also stays
+# closer to stg/prod
+
+- name: ensure packages required for proxying are installedc
+  action: yum name={{ item }} state=latest
+  with_items:
+    - libsemanage-python
+
+- name: allow httpd tcp connections with selinux
+  seboolean: name=httpd_can_network_connect state=true persistent=yes
+
+- name: copy resultsdb proxy httpd config
+  template: src=resultsdb.conf.j2 dest=/etc/httpd/conf.d/resultsdb.conf owner=root group=root
+  notify:
+    - restart httpd

roles/taskotron/taskotron-proxy/templates/resultsdb.conf.j2

@@ -0,0 +1,4 @@
+<Location /{{ resultsdb_endpoint }}/ >
+  ProxyPass http://{{ resultsdb_frontend_url }}/
+  ProxyPassReverse http://{{ resultsdb_frontend_url }}/
+</Location>