plugin scheduler

[yannicks1]

This PR moves the (spyre specific) scheduler class into the plugin repo vllm-spyre.
it goes along with this ->PR<- in the vllm-spyre repository

Changes:

• vllm/config.py: importing SchedulerConfig from vllm-spyre plugin instead of using the upstream SchedulerConfig
• vllm/core/scheduler.py: importing Scheduler from vllm-spyre plugin instead of using the upstream Scheduler
• vllm/envs.py: removing spyre specific variables (moved to vllm-spyre)

Note: I squashed the four commits of this iterative process to arrive at this solution into one commit for better readability.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[sducouedic]

LGTM

[sducouedic]

We will have issue with the git workflow which cannot import vllm_spyre...
We will probably need to update the workflows before merging with main or the 17.01.2025 branch.

[tdoublep]

I think we should first implement the mechanism to make the scheduler pluggable before moving the scheduler code into vllm-spyre. Otherwise, we end up creating a dependency on vllm-spyre within vllm itself, which is not what we want.

We can implement the scheduler pluggable stuff on this fork first, verify that it works, and then try to get the changes accepted upstream.

[yannicks1]

this PR is replaced by an alternative implementation see this PR