feat: introducing features to push generation of nodes to system subnets#53
Open
NikolaMilosa wants to merge 14 commits intomainfrom
Open
feat: introducing features to push generation of nodes to system subnets#53NikolaMilosa wants to merge 14 commits intomainfrom
NikolaMilosa wants to merge 14 commits intomainfrom
Conversation
This file contains hidden or 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
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.
With the release of SEV-SNP nodes we want to not just make subnets that have all SEV-SNP nodes but also push the important subnets to have as many SEV-SNP nodes as possible since the protocol accepts a mix of SEV enabled and regular nodes.
This PR does that by adding an accumulating penalty if the solver doesn't use the SEV nodes in the SEV-prefered subnets if the tool isn't enforcing SEV.
If the tool is enforcing SEV then it becomes a hard requirement to have all SEV nodes in SEV subnets.