Use templated ElasticSearch config for single-instance deployment

Validate certs everywhere

Until now it's only been used for clustered deployment,
but it works fine in single-instance mode, too.

roll back hotfix file size limit

Add more travis testing.

Allow for some overhead in profile image uploads

update maximum profie image size

Minor update and typo fix for mariadb

Add ecommerce, insights, and analyticsapi to pre-supervisor checks

Set default for GIT_REPO_EXPORT_DIR

Require a newer version of pip.

Jibsheet/flower oauth

0.7.0 is from May 2014 and lacks OAuth support and a number of other
updates.

Switch to having Flower use a config file, enable OAuth

Google OAuth requires an additional 4 command line args or environment
variables, so it was time for Flower to get a proper config file.

The broker configuration remains a command line argument because it is
consumed by Celery's configuration parser, not Flower's configuration
parser.

I can't think of a reason our oauth keys need to be world readable

Move templates to live in our new directory layout

Paths under templates/ should mirror their default installation path on
disk to make it easier to correlate deployed files back to source
templates.

Fix the callback plugin for cases where stderr is a boolean and not a string.

Fix profile image backend docs

Update syntax to match the new format.

The old syntax was:
 - causing the module name lookup to fail probably because it was having trouble dealing with the white space.
 - using an older name for a module argument

Feanil/update ansible

Minos should not be on sandboxes

The short circuit logic does not work on jenkins.

Don't run `/edx/bin/update`  with `--tags deplay` by default.

Having `--tags deploy` be part of the ansible-playbook call
that `/edx/bin/update` makes is not intuitive.  It's broken
us a few times recently and I don't think the benefit it
provides is worth the cost and confusion.  I feel that anyone
who wants to use tags will know how to do it without using
`/edx/bin/update`.

```
13:08:11 + ret=0
13:08:11 + echo 0
13:08:11 0
13:08:11 + '[' 0 -ne 0 ']'
13:08:11 Build step 'Virtualenv Builder' marked build as failure
13:08:11 [ssh-agent] Stopped.
13:08:11 Finished: FAILURE
```

The example above is a snippet from jenkins which the integration test runs into,
meaning it is often suceeding but reporting it as failure.  There is still an issue
with the cms worker which is related to 'stopwaitsecs' which is really high for all
workers due to grading.  That work will need to be refactored so that cms workers
don't wait so long before killing the worker.

The problem is the same as what is described here but more investigation will be
useful.

http://stackoverflow.com/questions/9971627/why-is-celery-not-shutting-down-cleanly

More clients