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

Feature Request: Dynamically update MinCount parameter #6587

Open
Waqiah opened this issue Dec 5, 2024 · 0 comments
Open

Feature Request: Dynamically update MinCount parameter #6587

Waqiah opened this issue Dec 5, 2024 · 0 comments

Comments

@Waqiah
Copy link

Waqiah commented Dec 5, 2024

It is noted that it is possible to update the MinCount parameter of a queue without stopping the compute fleet so that all jobs or VDI would still be running for users to be able to submit their jobs. As explained in this documentation, the QueueUpdatestrategy must be set to TERMINATE when decreasing the MinCount/MaxCount but is not needed when increasing the MinCount/MaxCount as well as in other cases such as adding of new queues to Scheduling/SlurmQueues and adding new compute resources Scheduling/SlurmQueues/ComputeResources to a queue.

Creating this feature request for a way to trigger the process directly from the headnode without having to install pcluster on the headnode to be able to monitor the queues, and automatically trigger the update based on custom rules (with the only parameter that would need to be updated being MinCount) as I understand that this is not possible at the moment.

Are there any workarounds to achieve the above or would such automation be implemented with a Lambda calling the ParallelCluster API?

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

1 participant