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

Sample Scheduler Framework plugins #85826

Open
Huang-Wei opened this issue Dec 2, 2019 · 7 comments
Open

Sample Scheduler Framework plugins #85826

Huang-Wei opened this issue Dec 2, 2019 · 7 comments

Comments

@Huang-Wei
Copy link
Member

@Huang-Wei Huang-Wei commented Dec 2, 2019

The Scheduler Framework is designed to engage end-users to easily build custom scheduling plugins to fit their particular requirements. We do have some basic examples and documents guiding users on how to use this (internally scheduler is refactoring its code to 100% adhere to the framework: Phase1, Phase2), however, for some complex and common requirements (e.g. batch), we'd like to create a SIG sub-repo (or other manner) to store qualified plugins code, so that those plugins can be developed iteratively in an open-source way, and hence reused by more users.

The eventual goal is to enable Scheduler Framework to fit more kinds of workload, so that Kubernetes itself can be more widely adopted as well.

/sig scheduling
/cc @ahg-g @ravisantoshgudimetla @hex108 @denkensk @everpeace

@Huang-Wei Huang-Wei changed the title Scheduler Framework Sample Scheduler Framework plugins Dec 2, 2019
@hex108

This comment has been minimized.

Copy link
Member

@hex108 hex108 commented Dec 3, 2019

I strongly aggree it!

It will be better if community could maintain common scheduler plugins in a SIG sub-repo(e.g. same as http://github.com/kubernetes-csi, it contains a lot of plugins). I once thought we could incoperate some of them into the default scheduler code base if they are widely used. Howerver it will make schedule more complex, it needs more consideration.

Pros and cons from my perspective:

  • The plugins code are under control, we could make some quality assurance for them. Howerver it needs some effort.
  • We could aovid some repetitive work if plugins are developed in a same repo.
@everpeace

This comment has been minimized.

Copy link
Contributor

@everpeace everpeace commented Dec 3, 2019

Yes, I agree it, too!

It will be better if community could maintain common scheduler plugins in a SIG sub-repo

+1 because custom scheduler using scheduling framework can be compiled independently. So separated repo can demonstrate more realistic example effectively.

@damemi

This comment has been minimized.

Copy link
Contributor

@damemi damemi commented Dec 3, 2019

+1 for a separate sub-repo for us and the community to work on plugins.

Maybe at some point we could also consider an index for plugins (similar to Krew for cli plugins) to encourage 3rd party plugin development without restricting contributors to our development cycle and freeing us from owning every plugin.

@everpeace

This comment has been minimized.

Copy link
Contributor

@everpeace everpeace commented Dec 3, 2019

Maybe at some point we could also consider an index for plugins (similar to Krew for cli plugins)

wow, interesting idea.

@ravisantoshgudimetla

This comment has been minimized.

Copy link
Contributor

@ravisantoshgudimetla ravisantoshgudimetla commented Dec 4, 2019

+1 to the suggestion.

I think initial goals of the sig-sponsored repo should be

  • Would be to validate the extension mechanism of the scheduler plugin framework for complex examples like batch workloads
  • Serve as an example to end-users on how to use develop plugins.

We can always make the repo to be an index of plugins once we see people want to have a common location where all the plugin can be stored.

/cc @swatisehgal

@swatisehgal

This comment has been minimized.

Copy link

@swatisehgal swatisehgal commented Dec 4, 2019

Thanks for pointing me to this. The Scheduler framework would be very useful for us and we are excited to play around with it to use it for Telemetry Aware Scheduling!

@ahg-g

This comment has been minimized.

Copy link
Member

@ahg-g ahg-g commented Dec 5, 2019

+1 This is exciting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.