Prep for code deploys to umad1 using git-deploy tool
Prep for deploy to new-style target, production cluster
Drop RUNNING_VERSION into the just-deployed frontend
Don't freak out about non-existent indices when querying ES
Put indexing_worker into its own directory as a distinct component

This will make things clearer, and easier to separate and run them as
individual components.
Find the redis server from environment variables
Put indexing_listener into its own directory as a separate component
indexing worker needs to see the CA cert in the right place
The umad user can now restart the whole umad taskgroup instead of one-by-one
Oops, tell the truth about who we are when accessing provsys
Add a script for poking provsys with trivial changes
Put analytics server in its own box and tidy SSL handling a little

The SSL handling still isn't quite ideal, as it needs a level of
privilege that might be a bit high, but it *does* keep the deployment
simple for now. I've included a self-signed cert to simplify the task of
local testing.
Don't verify SSL cert in testing script

This is an annoyance, but Python2's support for SNI is lacklustre. In an
SNI deployment, the Requests library will get confused if it gets a
hostname-to-certificate mismatch, which this change dodges. Less of a
problem if you have a handy wildcard cert, but you may not have one for
your staging/testing subdomain.
Merge branch 'master' of barneydesmond.github.com:anchor/umad