networkservicemesh / networkservicemesh/api
Add list of supported types of mechanisms to NetworkServiceEndpoint entry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 22
- Avg merge
- 27m
- Merged PRs (30d)
- 3
Description
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 the Connection much faster on load. (NSMgr could just filter all NSEs from the registry before do Request to the next point)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pkg/api/registry/registry.proto at the NetworkServiceEndpoint definition and inspect how Mechanisms are represented. Add the SupportedMechanisms field as a list describing endpoint-supported mechanism kinds such as MEMIF and KERNEL; done means the schema directly exposes this information for registry filtering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100