Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for OpenStack Swift storage #905

Closed
tlvenn opened this issue Aug 16, 2019 · 14 comments · Fixed by #1982
Closed

Add support for OpenStack Swift storage #905

tlvenn opened this issue Aug 16, 2019 · 14 comments · Fixed by #1982
Labels
component/loki type/feature Something new we should do

Comments

@tlvenn
Copy link

tlvenn commented Aug 16, 2019

It would be great if object_store could use OpenStack Swift containers.

@adityacs
Copy link
Contributor

adityacs commented Aug 16, 2019

@tlvenn Loki supports any object storage with S3 compatible APIs. Swift supports S3 APIs as mentioned here.

Also, please refer S3 section in this doc

@tlvenn
Copy link
Author

tlvenn commented Aug 17, 2019

Yes I know but this middleware is optional and some cloud providers choose not to enable it, OVH for example as far as I know.

@adityacs
Copy link
Contributor

@tlvenn Loki is dependent on Cortex for storage implementation. Could you please raise an issue in cortexproject/cortex ?

@tlvenn
Copy link
Author

tlvenn commented Aug 19, 2019

Sure will do. Quick question related with Cortex. Is it on the roadmap to be able to have 2 stores, one for recent data only that could be co located with the service and one long term to store all the log that would leverage S3 and the like ?

@tlvenn
Copy link
Author

tlvenn commented Aug 19, 2019

Or does Cortex support both Short & Long term storages ? On the surface, it seemed to be targeted at the latter.

@tlvenn
Copy link
Author

tlvenn commented Aug 19, 2019

@tomwilkie, it would be great when you have the time to shed some light on this, thx in advance !

@sh0rez
Copy link
Member

sh0rez commented Sep 6, 2019

@tlvenn at least regarding Loki, you have this behaviour (kind of):

The Ingester component, which is responsible for storing data, is a stateful service which keeps the last ~12h of working data in memory, to run optimizations and similar things.

This data is continuously written in batches to the chunk store (bigtable, cassandra, s3 etc.) and a reference to it is stored in the index store (another bigtable, cassandra etc).

See the cortex docs for more details on this:

They basically apply for Loki as well, just keep in mind Loki is dealing with a much bigger data volume than Cortex.

Does that help?

@sh0rez sh0rez added component/loki type/feature Something new we should do labels Sep 6, 2019
@adityacs
Copy link
Contributor

@sh0rez Any plans to support Swift storage? If yes, I can work on this. Pl let me know.

@stale
Copy link

stale bot commented Oct 26, 2019

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Oct 26, 2019
@stale stale bot closed this as completed Nov 2, 2019
@Madko
Copy link

Madko commented Apr 9, 2020

any news on this ?

@cyriltovena
Copy link
Contributor

@cyriltovena
Copy link
Contributor

PR open cortexproject/cortex#2440 there is still some work but the biggest is done.

@Madko
Copy link

Madko commented Apr 10, 2020

ah great news ! Thank you Cyril

@cyriltovena cyriltovena reopened this Apr 24, 2020
@stale stale bot removed the stale A stale issue or PR that will automatically be closed. label Apr 24, 2020
cyriltovena added a commit to cyriltovena/loki that referenced this issue Apr 24, 2020
This brings fixes for traceID in the logger and swift.
I've also added a bit of configuration for swift.

Fixes grafana#905

Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>
cyriltovena added a commit that referenced this issue Apr 27, 2020
* Update cortex to latest.

This brings fixes for traceID in the logger and swift.
I've also added a bit of configuration for swift.

Fixes #905

Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>

* Fixes a test.

Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>

* Update go.sum

Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>
@Morishiri
Copy link

Morishiri commented Aug 1, 2023

@cyriltovena is it possible to add support for it to the helm chart as well? Currently I don't see the option to configure that. Shall I open an issue/PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/loki type/feature Something new we should do
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants