feat: Add functionality to ensure that at least one node from each operator is in use #1063
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
…erator is in use If a node operator does not have any node assigned to a subnet, we cannot know if these nodes are in good shape. When there is no reduction in decentralization (!), let's try to have at least one node of each operator in a subnet, since we will have better insights into node health. The new functionality can be called with: ``` dre network --ensure-operator-nodes-assigned ``` Also, a few minor changes in the PR: - silence ic-admin notices since we are running it from automation - Refactor decentralization change handling, to make impact of a change on decentralization more consistent across operations - Rename the "heal" subcommand with "network --heal", but keep backwards compatibility. We may remove it at some point in the future
DFINITYManu
approved these changes
Nov 11, 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.
If a node operator does not have any node assigned to a subnet, we cannot know if these nodes are in good shape. When there is no reduction in decentralization (!), let's try to have at least one node of each operator in a subnet, since we will have better insights into node health.
The new functionality can be called with:
Also, a few minor changes in the PR: