Shift stage DAs to new machines #99
Merged
Conversation
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
kanshi
reviewed
Oct 15, 2024
There was a problem hiding this comment.
For the build to work, the client that is used will have to know about the new DAs, it gets that info from here - https://github.com/anyone-protocol/ator-protocol/blob/main/src/app/config/auth_dirs_stage.inc
and its set at build time, so the new stage builds (and all related tools with relays) will have to be running the updated version.
|
Already noticed this. We need the new fingerprints for this file to be changed? |
kanshi
approved these changes
Oct 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prepares the shift of stage DA auths to different machines. It also aims to solve the bug of the first machine in the job spec not being assigned any job instances. There has also been a change to the cert scripts such that the latest and correct client image is used.
How
For further information regarding point 2. The first job now uses the
distinct_hostsconstraint to specify all three instances must be on 3 distinct hosts. This way no instance within a group can be assigned the same machine and must use the "starved" machine.