-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* feat: add occupied slots to game rooms api (#641) * feat: add occupied slots to game rooms api * fix: rename api parameter * fix: failing tests * chore: upgrade and remove some dependencies (#644) * chore: upgrade and remove some dependecies * feat: allow maestro to deal with multiple matches per game server (#646) * feat: allow maestro to deaul with multiple matches per game server * fix: removing cooling status * feat: add new metrics (#649) * feat: add new metrics * fix: metrics reporter tests * fix: protobuf linter offenses * fix: update buf dependencies before running linter * fix: add max validation to minFreeSlots fields * feat: removing unused field minFreeSlots * chore: update dependencies * fix: project dependencies * chore: upgrading go version on CI * chore: upgrade docker image for build step * fix: backward compatibility with exiting schedulers * fix: linter offenses * fix: adding default match allocation configuration when not provided * fix: missing match allocation configuration * feat: create simulation service * fix: missing license headers * fix(policy): compute desired number of matches before rooms (#654) If we first divide the number of running matches per maxMatches we might end up with a number between 0 and 1, which is quirky when using math.Ceil because it would propagate the error to when computing number of desired rooms. To simplify and fix this, instead we now compute how many matches is the desired and then convert the final number to the amount of rooms/instances/pods needed to provide this number of matches: 1. How many running matches we have? * Get the value from the redis: scheduler:<scheduler_name>:occupancy 2. How many matches do we need to have based on readyTarget? * Divide running matches by 1 - readyTarget 3. How many game rooms are needed to provide this amount of matches? * Get the desired number of matches and divide by the max number of matches per room as defined in the scheduler * fix(allocation): maxMatches limit to 35 (#655) Some games might choose to run larger pod resources and increase number of matches running in each room/instance, thus increasing from 30 to 35. The limit in the max matches is useful so configuration stays in a sane number to help in autoscaling and roundings. * fix: setting running matches when not given * fix: adding transition from unready to active * fix: adding transition from occupied to active * fix: multiple matches status calculation * feat: report metric with scheduler max matches * fix: sync scheduler before sending metrics --------- Co-authored-by: Pedro Soares <pedro.soares@wildlifestudios.com>
- Loading branch information
1 parent
3727313
commit fb1c2b2
Showing
136 changed files
with
6,301 additions
and
8,960 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -53,4 +53,5 @@ kubeconfig.yaml | |
e2e/framework/maestro/kubeconfig.yaml | ||
|
||
# MkDocs | ||
site/ | ||
site/ | ||
buf.lock |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
version: v2 | ||
plugins: | ||
- remote: buf.build/protocolbuffers/go:v1.35.1 | ||
out: pkg/ | ||
opt: paths=source_relative | ||
- remote: buf.build/grpc/go:v1.5.1 | ||
out: pkg/ | ||
opt: paths=source_relative | ||
- remote: buf.build/grpc-ecosystem/gateway:v2.22.0 | ||
out: pkg/ | ||
opt: paths=source_relative | ||
- remote: buf.build/grpc-ecosystem/openapiv2:v2.22.0 | ||
out: proto/ | ||
opt: allow_merge=true |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
version: v2 | ||
deps: | ||
- buf.build/googleapis/googleapis | ||
- buf.build/grpc-ecosystem/grpc-gateway | ||
|
||
modules: | ||
- path: proto | ||
|
||
breaking: | ||
use: | ||
- FILE | ||
|
||
lint: | ||
use: | ||
- DEFAULT | ||
- COMMENTS | ||
except: | ||
- PACKAGE_VERSION_SUFFIX |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.