Docker compose for deployment of individual components

[jpkrohling]

See #466 for context and https://github.com/jaegertracing/jaeger-kubernetes/blob/master/production/jaeger-production-template.yml for reference

This should be done in a separate repository, like there is for Kubernetes and OpenShift.

[jpkrohling]

See #306 for a starting point.

[ishanjain28]

Hi, I'd like to take this up if it is still available.

[sssoleileraaa]

Note: jaeger-kubernetes/production/jaeger-production-template.yml was renamed to jaeger-kubernetes/production/cassandra.yml (see jaegertracing/jaeger-kubernetes@f930d0a#diff-0b3583916142302afe2c114d88c1f7c1) - Issue description with this reference needs to be updated.

[sssoleileraaa]

@ishanjain28 are you interested in working together on this?

I was just wondering what name we should give to the new repo. Maybe something like jaeger-compose?

[ishanjain28]

@AllieOop Yeah, Sure. jaeger-compose sounds good to me.

[pavolloffay]

@ishanjain28 see #493

[sssoleileraaa]

If I'm understanding this correctly, it sounds like the goal of this issue is to move the docker compose file into a separate repo so that it can be used to support multiple storages. I see the following question asked in #493 (comment): do we want to move the docker compose file into a separate repo? But I don't see any further discussion. If anyone has any thoughts on why this should be done, it would be helpful to discuss it here in this issue, like what storages do we want to support that aren't currently supported, or anything else?

[pavolloffay]

it sounds like the goal of this issue is to move the docker compose file into a separate repo so that it can be used to support multiple storages.

Compose file can be here on in a different repo and still support different storages.

I think it's easier to have it directly here because:

• it's used in crossdock - it's automatically tested
• can more quickly adopt new changes

cc @jpkrohling @yurishkuro

[pavolloffay]

We can reuse this compose file in different jaeger repositories to run xdock tests:

docker-compose -f https://github.com/jaegertracing/jaeger/master/compose.yml -f $(XDOCK_YAML) run crossdock 

[jpkrohling]

I'm not really familiar with how the cross-dock setup works, but docker-compose is an orchestration tool like OpenShift or Kubernetes. If the right place for the compose.yml file is here on this repo, then we might consider moving OpenShift's and Kubernetes' here as well.

[pavolloffay]

done in #493.

I will open next issue for further improvements.