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

Question: Autonomous scaler #39

Open
UnclePhil opened this issue Mar 2, 2022 · 7 comments
Open

Question: Autonomous scaler #39

UnclePhil opened this issue Mar 2, 2022 · 7 comments

Comments

@UnclePhil
Copy link

Hello,

Did you think it's possible to extract the Scaler part as an autonomous application ??
The idea is brilliant.

Best regards

@cuigh
Copy link
Owner

cuigh commented Mar 3, 2022

I haven't found many reasons to separate this function now. Can you tell me why you need a standalone scaler application?
Swirl is a very lightweight program if you use bolt store engine.

@UnclePhil
Copy link
Author

I'm working at a gov company, on 12 Onprem Swarm cluster, and we have a complete ecosystem with a central Portainer and a Gitlab CICD for the provisioning.
So the "standard" part of swarm management is present, but one of the missing part is a service to autoscale other components through labels reading.
And that's what you have create.

So if you can export this part as a single service, I will use it, and i know a lot of people who can use it too.

BTW: One service , One function is a very good philosophy with container.

Best regards

@cuigh
Copy link
Owner

cuigh commented Mar 7, 2022

I see. I'll think about it when I finish my another project.

@s4ke
Copy link

s4ke commented Jun 20, 2022

+1 on separating the autoscaler:

I think this would be a great standalone project which would help the Docker Swarm ecosystem in general.

@UnclePhil
Copy link
Author

UnclePhil commented Jun 20, 2022 via email

@s4ke
Copy link

s4ke commented Jun 20, 2022

Thanks for the link. Your script looks good, but there is something about such things written in bash that makes me uneasy. I guess it is fine, but a solution written in python/Go would make people want to contribute a bit more, maybe?

@UnclePhil
Copy link
Author

UnclePhil commented Jun 20, 2022 via email

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

No branches or pull requests

3 participants