-
Notifications
You must be signed in to change notification settings - Fork 47
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
Implement server provisioning #300
Conversation
36dc944
to
e26ae71
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @MasterPtato and the rest of your teammates on Graphite |
959d619
to
2297c2f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this review is still wip
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to delete watches & yarn.lock
wip review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wip
74532cd
to
844901c
Compare
cc4bd90
to
f698d5d
Compare
f698d5d
to
51898f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
high level changes
- needs to document the prebake process & how we do normal installs when waiting for prebake servers to finish
- it's not clear that the server token is meant to be reused in the image and servers are identified by public ip. just needs some comments around that.
- do we taint all servers once a new prebaked image is ready?
- make sure the logic is sound such that servers can be recreated with a recycled public ip
- see comments on figma for diagram
load testing
was trying to think about what it would take to feel confident in shipping this without taking everythign down. i think the biggest thing is load testing it with fault injection on staging (since that's on eks). that consists of:
- using mm-sustain with an up and down in terms of players online. we want to mix job types between 1d8, 1d4, etc, 4d1. want to test the equivalent of 2k->10k->2k ccu repeating with 16 players/core.
- inject faults in to the linode + cloudflare api by passing an env var with the failure percent. we can write a macro or something that injects faults here.
- do we have a way to read the linode api to make sure that the servers match what we have internally? like a "doctor" service that prints anything wrong. this will help us catch leaked servers.
i know this is scope creep, but i'm hoping this will save us a series of headaches. i don't think it's too hard afaik, the hard part of load tests is already done.
2e895aa
to
3602c68
Compare
Merge activity
|
<!-- Please make sure there is an issue that this PR is correlated to. --> Depends on rivet-gg/rfcs#7 Merge with rivet-gg/rivet-ee#6 ## Changes - Move server provisioning to a service for future automation and flexibility <!-- If there are frontend changes, please include screenshots. -->
3602c68
to
175904e
Compare
<!-- Please make sure there is an issue that this PR is correlated to. --> Depends on rivet-gg/rfcs#7 Merge with rivet-gg/rivet-ee#6 ## Changes - Move server provisioning to a service for future automation and flexibility <!-- If there are frontend changes, please include screenshots. -->
175904e
to
82b02c6
Compare
<!-- Please make sure there is an issue that this PR is correlated to. --> Depends on rivet-gg/rfcs#7 Merge with rivet-gg/rivet-ee#6 ## Changes - Move server provisioning to a service for future automation and flexibility <!-- If there are frontend changes, please include screenshots. -->
82b02c6
to
ec2edc8
Compare
<!-- Please make sure there is an issue that this PR is correlated to. --> Depends on rivet-gg/rfcs#7 Merge with rivet-gg/rivet-ee#6 ## Changes - Move server provisioning to a service for future automation and flexibility <!-- If there are frontend changes, please include screenshots. -->
ec2edc8
to
1aa344e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will resolve remaining issues in follow up prs
Do not merge until rivet-gg/rivet#300 is deployed
Depends on https://github.com/rivet-gg/rfcs/pull/7
Merge with https://github.com/rivet-gg/rivet-ee/pull/6
Changes