This is a step towards upgrading to elasticutils 0.7, which uses pyelasticsearch.
First we can drop in pyelasticsearch into the requirements and update AMO to use this to get an ES object rather than using pyes' `get_es`. AMO doesn't use elasticutils yet so it just needs an ES connection to be used in its own ES wrapper code. When AMO is all good, we can safely focus on MKT side.
First step... isolate AMO code that depends on elasticutils using pyes:
I pushed this forward a bit this week:
Next steps are tests and to update mkt search code to use the new index and the elasticutils lib. There's also a bug in the reindexing code that triggers an elasticsearch timeout error.
This went out as part of bug 867288.