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.
Node colors are procedurally generated by a node's rank. This can be a
string like
tnsfork/lb-1
. Now if all the nodes share the sameprefix in their rank, e.g.
tnsfork/
they will all get the samecolor.
An approach to separate colors a bit more would be to remove the longest
common rank prefix and set that as the color key.
Pros:
Cons:
similarly (which is what happens now)
switch based on their new LCP
color because that node is loaded in isolation (LCP of that
topology's nodes is undetermined)