Skip to content
This repository has been archived by the owner on May 18, 2020. It is now read-only.

Naming to support other backends #23

Closed
yurishkuro opened this issue Jul 27, 2017 · 3 comments
Closed

Naming to support other backends #23

yurishkuro opened this issue Jul 27, 2017 · 3 comments

Comments

@yurishkuro
Copy link
Member

The Elasticsearch backend is ready, I assume we'll eventually want to have templates for it as well. How should this affect the naming of directories and files in this repo?

@pavolloffay
Copy link
Member

First we have to split cassandra related stuff from jaeger deployment. Adding ES will probably require some changes to jaeger deployment (use some flag etc.). The problem is that K8s resource files do not support parameters, so we might use something like helm (I don't know yet).

In terms of storage templates maybe it would be if we could reuse ES deployment from k8s and just make sure that it works with Jaeger.

@pavolloffay
Copy link
Member

Related to #54

@pavolloffay
Copy link
Member

I will close this in favour of #54

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants