-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add list of supported types of mechanisms to NetworkServiceEndpoint entry #85
Comments
The main questions are:
|
|
For this case, we could just reject the incoming request on the registry side.
Currently, I see only fields that can be improved. I.e. no more permutation on selecting NSE/cross-NSE and also this should reduce requests count to the registry from nsmgr. Also, third-party apps that using the registry API could fast find NSEs that support specific mechanisms. |
/cc @fkautz |
@edwarnicke Do we have any updates on this? |
@denis-tingaikin Not yet... but I'll leave it in my notifications so I make sure to circle back to it. |
Description
We can add the
SupportedMechanisms
field into NetworkServiceEndpoint to directly indicate what kinds of mechanisms the Endpoint could handle.SupportedMechanisms is a list of Mechanisms kind, such as 'MEMIF', 'KERNEL', and so on.
Motivation
This can reduce the count of NSMgr tries on selecting cross-nse or nse. It can make
Request
for theConnection
much faster on load. (NSMgr could just filter all NSEs from the registry before doRequest
to the next point)Closes networkservicemesh/sdk#802
The text was updated successfully, but these errors were encountered: