Skip to content
This repository has been archived by the owner on Mar 31, 2022. It is now read-only.

InfluxDB ephemeral and persistent volumes #21

Open
gianarb opened this issue Jan 25, 2018 · 3 comments
Open

InfluxDB ephemeral and persistent volumes #21

gianarb opened this issue Jan 25, 2018 · 3 comments

Comments

@gianarb
Copy link
Contributor

gianarb commented Jan 25, 2018

Data in InfluxDB are stored on file system. at the moment we are not creating volumes or whatever.

my current opinion is that we should continue in this way plus we should add support for persisted volumes.
What I am saying is that I don't like to create local volumes only persisted or nothing.

@fntlnz fntlnz changed the title InfluxDB effimeral and persistend volumes InfluxDB ephemeral and persistend volumes Jan 26, 2018
@fntlnz fntlnz changed the title InfluxDB ephemeral and persistend volumes InfluxDB ephemeral and persistent volumes Jan 26, 2018
@fntlnz
Copy link
Collaborator

fntlnz commented Jan 26, 2018

This is definitely a thing that needs to be handled out of the operator, I see two ways of using it:

  • you don't persist
  • you create your own persistent volumes and you pass their names to the operator

This choice needs to be like this because storage is very coupled with the infrastructure needs to be managed in different ways each time.

I don't agree that we should not support local volumes, if a user wants to use the local persistent volume type that should be doable.

Also local seems a pretty desirable way to run an InfluxDB instance since it's aware of the volume's constraints given a specific affinity.

And finally, supporting local volumes costs us nothing more than implementing just persistent volumes support.

@gianarb
Copy link
Contributor Author

gianarb commented Feb 8, 2018

Based on the experience we made these weeks we need to implement a persistent volume claim.

@fntlnz
Copy link
Collaborator

fntlnz commented Feb 8, 2018

Yea totally, I like the idea of creating the pvcs from the operator allowing the user to personalize them by doing some kind of ‘volumeClaimTemplate’ thing

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

No branches or pull requests

2 participants