* Fixing some bugs in the manifest definition
* Database model and schema migration for tower settings
* Initial View and Serializer implementation using a strategy of merging
model instances and named tuples
* Settings manifest, mapping internal settings to what can be used in
the database along with type information etc.
* Initial Database model
* Helper object that overlays database settings on django settings
* upstream/release_2.3: (91 commits)
Include python-{paramiko,ecdsa} dependencies
Remove extra epel testing stanzas
Unit test for ec2 credentialless inventory
Fix issue with ec2 iam sync with no credential.
Use the htpasswd command instead the ansible module
Pip is no longer needed
check local user root or not in ./configure
Remove unneeded when check for super user addition
Improve distro detection in setup.sh
Fix superuser check on upgrade
Minor improvements to setup.sh
Remove ansible prerequisite check from configure
Attempt to install ansible within setup.sh
Allow munin processes to access postgres
Move up base package dependency install
fixes jenkins failures
Proper flake8 fix
fixes executing processes with correct PYTHONPATH will pickup .pth files
Show the repo for bundled package file dump
Proper flake8 fix
...
* inherit extra_vars from job_template
* overwrite with extra vars survey default vars
* overwrite with job extra_vars
* bypass extra_vars inherit logic for job relaunch
* with tests
Previously we could just check for the absence of the stdout file to
know we didn't yet/wouldn't ever have any stdout content. Now that we
are creating the stdout file ahead of time and persisting it we need to
also check to see if the file contains any data. This is also
necessary for some unit tests.
* Cleanup old code related to stdout download using temporary files
* Remove copy-into-database code
* Modify stdout download code to reference stdout file
Previously we could just check for the absence of the stdout file to
know we didn't yet/wouldn't ever have any stdout content. Now that we
are creating the stdout file ahead of time and persisting it we need to
also check to see if the file contains any data. This is also
necessary for some unit tests.
* Cleanup old code related to stdout download using temporary files
* Remove copy-into-database code
* Modify stdout download code to reference stdout file
* Defer loading result_stdout_text until specifically needed
* Conditionally display it based on the size of the field
* Provide a helpful message otherwise
