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

Add details on scheduling strategies #127

Merged
merged 1 commit into from
Aug 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion reference/ams-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ The Anbox Management Service (AMS) provides various configuration items to custo
| `registry.mode`<br/>*(string, `pull`)* | Mode in which the {ref}`exp-aar` client in AMS operates: `manual`, `pull`, `push` |
| `registry.update_interval`<br/>*(string, `1h`)* | Frequency of {ref}`exp-aar` updates (for example: 1h, 30m). |
| `registry.url`<br/>*(string, N/A)* | URL of the {ref}`exp-aar` to use. |
| `scheduler.strategy`<br/>*(string, `spread`)* | Strategy that the internal instance scheduler in AMS uses to distribute instances across available LXD nodes: `binpack`, `spread` |
| `scheduler.strategy`<br/>*(string, `spread`)* | Strategy that the internal instance scheduler in AMS uses to distribute instances across available LXD nodes: `binpack`, `spread`<br/> Choose a scheduling strategy that best suits your needs:<br/> - `spread` provides a distributed workload, picking the node with the most free resources.<br/>- `binpack` is useful when you are working with a small cluster as it picks the node that is most used until it is out of capacity before moving on to the next node. |

(sec-node-configuration)=
## Node-specific configuration
Expand Down
Loading