Setting up the testbed locally with Docker Compose

[jholleran]

Currently there are a lot of containers to startup for setting up the testbed locally. This could be simplified with a docker-compose.yml file that would start Elasticsearch, Metricbeat, & Grafana.

[gregjan]

It seems like this would help to start and connect all of the docker containers. Would we still need to have the bash script at the center of things at that point? I am tempted to move in the direction of having the gatling-testbed do potentially more of that and moving the rest into the .env file for this big stack.. I suppose the limitation in a stack is that you get little control over order of startup, so this would imply that the testbed only "starts" when everything else is ready. So it might have to poll for the other services?

[jholleran]

My initial thinking on this was just to simplify spinning this up in locally or in a dev environment. One compose file to start Elasticsearch, Metricbeat, & Grafana another file to start the LDP server but it would be nice if this could be used to simplify the script also.

We are starting to set this up fully in a performance env so I'll let you know how we get on with this. We will be using kubernetes to manage the containers so it will be a bit different.