Enable gateway discovery service to support a centralized discovery controller
- Dominant language
- Python
- Stars
- 132
- Forks
- 69
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 47
Description
An NVMe centralized discovery controller (CDC) serves the same purpose as a top-level discovery server (#71), but improves on that by eliminating the need for every host to completely enumerate all the discovery controllers on the network to find the namespaces they can/must attach to.
A centralized discovery controller interacts with "direct discovery controllers" (like the gateway's discovery service #63) in a new way recently added to the NVMe spec.
This feature provides the support in the gateway discovery service that enables it to act as a DDC to a CDC. This requires specific support in the DDC.
How widely adopted CDCs will be remains TBD. As much as anything this feature ticket is to distinguish this from #71 (which is much simpler).
Contributor guide
Research direction
Start by reviewing the gateway discovery service and the NVMe specification changes for centralized discovery controllers, then compare the related work in issues #63 and #71. Done means the discovery service can act as a direct discovery controller to a centralized discovery controller with the required protocol support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100