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

New OpenStack Swift scaler #1342

Closed
domminiks opened this issue Nov 18, 2020 · 3 comments
Closed

New OpenStack Swift scaler #1342

domminiks opened this issue Nov 18, 2020 · 3 comments
Labels

Comments

@domminiks
Copy link

domminiks commented Nov 18, 2020

My team (@sidilabs) and I want to contribute to KEDA by proposing and also implementing a RedHat/OpenStack Swift scaler.

More info about our proposal:

  • Scaler Source: Swift is the default object-store for OpenStack. It works much like AWS S3 or Azure Blob Storage.

    The OpenStack Object Store project, known as Swift, offers cloud storage software so that you can store and retrieve lots of data with a simple API. It's built for scale and optimized for durability, availability, and concurrency across the entire data set.

  • How do you want to scale: The idea is to scale based on the object count in a certain container. As the object count (number of files, folders, ...) changes, KEDA scales up or down accordingly.

  • Authentication: for authentication we must use Keystone (another OpenStack project). With Keystone, one can get an access token to be used for authentication/authorization. We've investigated two auth methods for getting a token and then querying the Swift API:

We understand that both auth methods should be implemented by the scaler.

@zroubalik
Copy link
Member

Looking good! That would be a great contribution.

Just a minor nit, implementing e2e tests with the scaler would be really great: https://github.com/kedacore/keda/tree/main/tests

@domminiks
Copy link
Author

Ok, I took a note about it, thanks!

Letting the community know about our progress soon 😄

@tomkerkhove
Copy link
Member

This was implemented, closing

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

No branches or pull requests

3 participants