Skip to content
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

Allow visors to advertise themselves as running on Public IP #574

Closed
jdknives opened this issue Oct 23, 2020 · 0 comments
Closed

Allow visors to advertise themselves as running on Public IP #574

jdknives opened this issue Oct 23, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@jdknives
Copy link
Member

Feature description

We should make it easier for users to establish transports automatically. The best scenario would be to make them establish stcpr transports to visors on public IPs. We should allow visors on public IPs to register themselves in the service discovery so other visors can establish transports to them upon startup.

Is your feature request related to a problem? Please describe.
Currently, if visors want to open up a route to another visor, they need to establish transports manually.

Describe the solution you'd like
I would suggest we go with a semi-manual way of solving this issue by allowing operators of visors to set a config value that indicates their visor is reachable for stcpr transports. When this is set, the visor registers itself in the service discovery. Otherwise we would have to automate the detection of whether visor is reachable for stcpr. In any case, we should verify in the service disc whether entries are valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant