f19 packstack wrkaround for iptables

* f19-havana does not a fw rule that allows contact
to port 35357 which prevents our reboot and openstack-status
check to pass.  This is a bug in f19-havana, packstack is not
configuring the iptables rules properly

Change-Id: I0306b10cc7687051ea635555fc0440254169def1
Change 'use_qemu_for_poc' in foreman seeds.rb to be true by default

Change-Id: I37c08113f05ae243c81319bf86cc885edda5697c
add poodle build mark for QE's jenkins server

Change-Id: I5127d7af13198bbc6466fcc7c84c8b9d4bf03726
able to add : to debug message

need for build tags on qe jenkins server

Change-Id: I4e83e7d374b41f6749cd0588ecce74692b7b6f6d
enable puppletlabs repo for rhel/centos

Change-Id: I3dd25ada97cbe2fd2f2e374590aac296b7ade1e4
packstack rdo/rhos debug clean up

Change-Id: If7952429857bad638a3805a346bba7fe3b280a5b
Setting.yml generation script

- run.sh: fix parsing args
- settings.py: fix tempest settings generation
- Adds test to test run.sh
- run.sh: fix collect_logs: failure when REMOTE_USER is not set
- test_run tests aio-rhel7
- run.sh: properly parse args, respect TAGS and SKIP_TAGS
- Remove Foreman from the add hosts task
- (cherry picked from commit 040baa227d9a00cd5ef498a8d5d9beeb0d57f8bf)
- Change pre to post in the foreman playbook
- (cherry picked from commit 5ed1d2c91fca1c3e81378b7620d748f476ac5f6f)
- settings: do not store tags and skip tags
- Ansible is broken is tags and skip tags are stored as
- variables. Probably reserved!
- run.sh: show settings files

- settings.py rewrite using CRUD functions

  Introduced Settings class to contain and handle the settings
  Introduced KeyPath class and keypaths (strings of keys separated by a
  dot)
  All configuration settings can be now addressed via a keypath.

  Order of the operations and defaults:
  job defaults are loaded from build/defaults.yml and tempest/defaults.yml
  The build paramaters are loaded from
  - job name (is splitted into basic components and assigned to config
    variables)
  - site/<site>.yml
  - build/<variant>.yml
  - tempest/<testsuite>.yml

  then a parameter can be overriden using four value sources, in order of
  ascending priority:
  - existent setting addressed via keypath
  - environment variable
  - cli command argument (when available)
  - generic CRUD function (--{update,set,delete,create}-variable)

  more than one generic CRUD function command line argument is allowed,

  CAVEATS
  - keys in keypaths cannot contain dots ".". When a dot is needed, a colon
  should be used instead (Ex "6:5" instead of "6.5")
  - numeric keys in keypaths during "create,set" are interpreted as list
  index and a list will be created

- improved documentation
- Added commented sample settings variable source files
- fixed principal parameters from job-name
- fixed get_values functions
- fixed tempest branch
- improved logging
- new settings generation is optional and must be activated with
  --generate-settings
- fixed generic variables handling

Change-Id: I79f22a41c0d5462ad6fc8efff9193fa7a692d9a3