What you would like to be added?
Proposal for adding a scheduler backend framework. It will make Grove easily support multiple schedulers other than KAI-scheduler
Why is this needed?
Grove currently only supports the KAI scheduler. As more customers and schedulers begin to adopt Grove, it is essential to make Grove more extensible and easier to integrate with multiple scheduler backends. This proposal introduces a Scheduler Backend Framework that standardizes and simplifies the process of adding new scheduler support to Grove, minimizing invasive modifications required for future scheduler integrations. The framework provides a clear abstraction layer between Grove's control plane and various scheduler implementations, enabling seamless scheduler backend extensibility while maintaining backward compatibility with existing KAI scheduler deployments
What you would like to be added?
Proposal for adding a scheduler backend framework. It will make Grove easily support multiple schedulers other than KAI-scheduler
Why is this needed?
Grove currently only supports the KAI scheduler. As more customers and schedulers begin to adopt Grove, it is essential to make Grove more extensible and easier to integrate with multiple scheduler backends. This proposal introduces a Scheduler Backend Framework that standardizes and simplifies the process of adding new scheduler support to Grove, minimizing invasive modifications required for future scheduler integrations. The framework provides a clear abstraction layer between Grove's control plane and various scheduler implementations, enabling seamless scheduler backend extensibility while maintaining backward compatibility with existing KAI scheduler deployments