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

Change Broker Allocation Algorithm #337

Open
kthare10 opened this issue Aug 29, 2023 · 1 comment
Open

Change Broker Allocation Algorithm #337

kthare10 opened this issue Aug 29, 2023 · 1 comment
Assignees
Labels

Comments

@kthare10
Copy link
Collaborator

https://fabric-testbed.atlassian.net/browse/FIP-714
Change Broker Allocation Algorithm to spread resources across available hosts more evenly as opposed to first fit.

@kthare10 kthare10 self-assigned this Aug 29, 2023
@kthare10
Copy link
Collaborator Author

kthare10 commented May 9, 2024

OOM issue has been resolved by reserving 24GB of RAM for the host and allocating rest to CF for allocation: https://fabric-testbed.atlassian.net/jira/servicedesk/projects/FIP/queues/custom/44/FIP-1405

Following change is requested for Allocation to avoid users from exhausting all shared NICs on a specific host.

Maybe we should have something like: Choose the first host in the list where the VM fits and the host has at least X% of the cores/ram/disk/shared_nics available, unless all the hosts have less than X% of the cores/ram/disk/shared_nics available. If all the hosts have less than X% of the cores/ram/disk/shared_nics available, then choose a random host that has enough resources.

@kthare10 kthare10 added the 1.8 label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant