YUNIKORN-1564 Constants for node attributes are not consistent in scheduler interface and shim #523
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.
What is this PR for?
Before we do more changes to remove nodename noderack in node attribute, and then add noderack to nodeinfo, also change in Scheduler Interface and webapp in https://issues.apache.org/jira/browse/YUNIKORN-1560
We first fix the consistence with interface and shim, then i will do above things.
And don't change the nodelabels field, because we will address new nodelabels pass instead of the json now in another jira:
https://issues.apache.org/jira/browse/YUNIKORN-1550
What type of PR is it?
Todos
What is the Jira issue?
[YUNIKORN-2] Gang scheduling interface parameters
How should this be tested?
Screenshots (if appropriate)
Questions: