-
Notifications
You must be signed in to change notification settings - Fork 69
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
Connectivity and service discovery should be full-blown components #1102
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
Handling of connectivity and service discovery as components should allow them to be fully pluggable, i.e. they should provide a common interface which
subctl
or any other implementations can use without knowing details.(This started off as a request to make Globalnet a component, but Globalnet doesn’t fit into a component model and this will need to be reconsidered for Globalnet 2 anyway.)
The text was updated successfully, but these errors were encountered: