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.

Sign up for GitHub

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

Jump to bottom

on demand resources #24

Closed
praiskup opened this issue Oct 12, 2019 · 2 comments
Closed

on demand resources #24

praiskup opened this issue Oct 12, 2019 · 2 comments
Labels
enhancement RFE, feature

Comments

@praiskup
Copy link
Owner

Sometimes it would be useful to have pool which doesn't preallocate resources in advance because those wouldn't be used for a long time. It would be better if we started those resources on demand, when ticket requesting that comes.
@praiskup praiskup added the enhancement RFE, feature label Oct 12, 2019
@praiskup praiskup mentioned this issue May 7, 2020
Open
Closed
@pkking
Copy link

pkking commented Feb 24, 2023

Sorry for reopen this, these day im trying to use resalloc to alloc pod, which is pretty fast to alloc/release, but if the max_prealloc is zero, the pool will not alloc any resouce anymore, it sounds unreasonable.

@praiskup
Copy link
Owner Author

Thank you for the update. I suppose we'll have to implement yet another option on top of those we already have. Something like allocate_on_demand: true.

praiskup added a commit that referenced this issue Aug 3, 2023
@praiskup
On demand resources, started via on-demand tags
ac6c650 
On-demand tickets need to be prioritized over the normal tickets
(priority queue), otherwise we risk that normal tickets take "on demand"
resources.

If we want to prefer one "on demand" pool over the other "on demand"
(e.g. spot AWS over normal instances), we need to sort them through a
priority queue based on tag priority.  The fallback for spawn failures
(e.g. if SPOT instances don't start) isn't resolved yet, though.

Fixes: #24
praiskup added a commit that referenced this issue Aug 3, 2023
@praiskup
On demand resources, started via on-demand tags
952a31d 
On-demand tickets need to be prioritized over the normal tickets
(priority queue), otherwise we risk that normal tickets take "on demand"
resources.

If we want to prefer one "on demand" pool over the other "on demand"
(e.g. spot AWS over normal instances), we need to sort them through a
priority queue based on tag priority.  The fallback for spawn failures
(e.g. if SPOT instances don't start) isn't resolved yet, though.

Fixes: #24
praiskup added a commit that referenced this issue Aug 3, 2023
@praiskup
On demand resources, started via on-demand tags
de9be38 
On-demand tickets need to be prioritized over the normal tickets
(priority queue), otherwise we risk that normal tickets take "on demand"
resources.

If we want to prefer one "on demand" pool over the other "on demand"
(e.g. spot AWS over normal instances), we need to sort them through a
priority queue based on tag priority.  The fallback for spawn failures
(e.g. if SPOT instances don't start) isn't resolved yet, though.

Fixes: #24
praiskup added a commit that referenced this issue Aug 8, 2023
@praiskup
On demand resources, started via on-demand tags
1a6a729 
On-demand tickets need to be prioritized over the normal tickets
(priority queue), otherwise we risk that normal tickets take "on demand"
resources.

If we want to prefer one "on demand" pool over the other "on demand"
(e.g. spot AWS over normal instances), we need to sort them through a
priority queue based on tag priority.  The fallback for spawn failures
(e.g. if SPOT instances don't start) isn't resolved yet, though.

Fixes: #24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement RFE, feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pkking @praiskup