We're stopping rabbit, but it's part of the configuration the service,
so I didn't use manage:.  We may need to re-discuss the tags (mongo_3_0
works similarly when stopping mongo to manage config).

Files for building a docker container for rabbitmq

All apt-get over https

New third-party repos

Enforce correct rabbit version installed

Flag rabbit upgrading

Adds the CHECK_RABBIT_VERSION flag (true by default). If true and the
rabbitmq version found differs from the version specified in
RABBITMQ_VERSION, the role fails. If false in the same scenario, the
role continues but does not install rabbitmq (because it's already
installed).

This enables us to continue using this role without forcing us to
upgrade rabbitmq.

Rebase miss

Missed merge conflict marker

syntax and whitespace

latest rabbit.

This Dockerfile is based on the official image (rather than built from scratch by us) and includes the elasticsearch-head plugin.

This playbook will install carbon-cache and graphite-api to provide a
minimalistic starting point for metrics collection.

It currently installs all components from their upstream source (albeit
with defaults that point to tags, and not master/development branches).
It uses systemd, and so is tailored specifically to Ubuntu 16.04.

It currently does not support any of the advanced configuration such as
multiple carbon-cache process + carbon-relay.  It is also lacking many
variables to fully tweak the various configuration files, although
there's support for fully configuring the storage schemas.

There is a small "master" playbook -- edx-monitoring -- for running the
role, and in the future, supporting the culmination of other playbooks
to build out an all-in-one monitoring server: Graphite, Grafana, etc.

Prompted because the awscli on go-agents needs to be above 1.10.47 to be
able to take advantage of IAM roles for tasks automatically.

ECOM-7207

- Added file to allow bower to install as root
- Added xvfb, firefox, and gettext packages for testing and local development

We originally made these changes when trying to debug the connection
between the go-agent and go-server.  Having them here makes it harder to
upgrade go-agent versions since they are regularly making improvements
to the upstream dockerfiles.

This also means an update to java-8.

Analytics-Api will generally need to be built from a tag so that Insights
tests can run with that version.  Adding this line here to make it easier
to update when that process occurs.

This is purely for testing, as running docker inside docker
requires further shenanigans, but at least it'll catch if we
ever break this role.

These are the same versions as what the rest of configuration is currently set to.

ECOM-6570