DANM 4.0 EP7: Adapting Svcwatcher code to independently recognize the three network management APIs #101
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
…PIs indepedently from each other
Levovar
force-pushed
the
svcwatcher_fourdoto
branch
from
1b55711
to
af32aed
Compare
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.
We do this by adding two new network selectors into the DANM compatible Service API schema.
Each network API has its own, explicit selector, independent from each other.
Thus it becomes possible for users to explicitly control which management API they want their EndPoints to select. This functionality is needed, because the different APIs can contains networks with the exact same name, even within the exact same namespace (e.g. if someone would use DanmNet and TenantNetwork together, for some reason)