treeherder/vagrant
Ed Morley 18e8971532 Bug 1340554 - Update from Elasticsearch 2.x to 5.x
* ES 5.x now requires JDK 8, and Ubuntu 14.04 only ships with openjdk 7,
  so a third party PPA must be used in Vagrant:
  https://launchpad.net/~openjdk-r/+archive/ubuntu/ppa
* ES 5.x changed the way it manages the heap size, such that:
  - The variables for controlling it have changed (now set via eg
    `ES_JAVA_OPTS="-Xms1g -Xmx1g"` or in the jvm.options file). See:
    https://www.elastic.co/guide/en/elasticsearch/reference/5.2/heap-size.html
  - The default heap size has increased from ~(min:256MB, max:1GB) to
    (min: 2GB, max: 2GB) which causes OOM in the VM, unless either
    lowered back down or the VM RAM increased.
* The Python ES clients must be updated to the latest releases:
  https://elasticsearch-py.readthedocs.io/en/master/#compatibility
* The previous test failures were fixed in #2403.
* The Vagrant provision now also waits for Elasticsearch to be ready
  before trying to run the Django migrations, since Elasticsearch can
  take a while to start (and always has). This prevents failures when
  the pip/yarn install steps are no-ops (when already up to date),
  causing the Django migration to run immediately after the ES install
  step.
2017-04-21 14:38:00 +01:00
..
.profile Bug 1353807 - Remove celerybeat-schedule during provision 2017-04-19 00:49:15 +01:00
env.sh Bug 1318295 - Vagrant: Move profile/env setup to shell provisioner 2017-03-21 22:48:51 +00:00
mysql.cnf Bug 1318295 - Vagrant: Move mysql setup to shell provisioner 2017-03-21 22:48:51 +00:00
setup.sh Bug 1340554 - Update from Elasticsearch 2.x to 5.x 2017-04-21 14:38:00 +01:00
varnish.vcl Bug 1318295 - Vagrant: Move Varnish to shell provisioner 2017-03-21 22:48:51 +00:00