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.

Sign up for GitHub

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

Jump to bottom

Don't show gateway as disconnected if they are connected in a different region #2406

Closed
laurensslats opened this issue Apr 23, 2020 · 3 comments
Closed

Don't show gateway as disconnected if they are connected in a different region #2406

laurensslats opened this issue Apr 23, 2020 · 3 comments
Assignees
@kschiffer @bafonins
Labels
c/console This is related to the Console in progress We're working on it ui/web This is related to a web interface

Comments

@laurensslats
Copy link

laurensslats commented Apr 23, 2020 •
edited

Summary

Gateways that are connected to a different region than the user is currently looking at seem offline, though they are online.

...

Why do we need this?

It seems like false information.
...

What is already there? What do you see now?

The gateway is connected to nam1 and I'm looking at the eu1 console.

You do see: Other Cluster in the specific gateway view, but not in the list with all gateway. See printscreens below.

Screenshot 2020-04-23 at 10 53 03

Screenshot 2020-04-23 at 10 46 17

...

What is missing? What do you want to see?

Change Other Cluster to Other Region. Show this in the gateway list and in the gateway page. See printscreens below:

Screenshot 2020-04-23 at 10 50 40

Screenshot 2020-04-23 at 10 52 54

...

How do you propose to implement this?

Easy fix.

...
@laurensslats
Copy link
Author

I'd say Other Region is clearer than Other Cluster. Let me know if you think otherwise.

@bafonins bafonins added c/console This is related to the Console needs/discussion We need to discuss this ui/web This is related to a web interface labels Apr 23, 2020
@bafonins bafonins added this to the Backlog milestone Apr 23, 2020
@bafonins
Copy link
Contributor

bafonins commented Apr 23, 2020 •
edited

The gateway is connected to nam1 and I'm looking at the eu1 console.

We show the Other Cluster indicator only if gateway_server_address configured for the gateway is not the same as the one in the current deployment. To be more specific hostname of eu1 is tti.eu1.cloud.thethings.industries while gateway_server_address is configured to tti.nam1.cloud.thethings.industries

Show this in the gateway list and in the gateway page.

Indeed, we should do that.

@htdvisser, @johanstokking what about changing Other Cluster to Other Region? Im fine with this. Here is the initial discussion regarding this: #243 (comment)

@bafonins bafonins modified the milestones: Backlog, Next Up Apr 23, 2020
@htdvisser
Copy link
Contributor

htdvisser commented Apr 23, 2020 •
edited

The correct term is "Cluster". We can have eu1 and eu2 that are the same geographical region (Europe), but not the same cluster.

@bafonins bafonins added in progress We're working on it and removed needs/discussion We need to discuss this labels Apr 26, 2020
@bafonins bafonins mentioned this issue Apr 26, 2020
Merged
6 tasks
rvolosatovs pushed a commit to rvolosatovs/lorawan-stack-fork that referenced this issue Nov 18, 2020
@htdvisser
Merge pull request TheThingsNetwork#2406 from TheThingsIndustries/rel…
02f0f2a 
…ease/v3.10.0-rc2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kschiffer kschiffer

@bafonins bafonins

Labels
c/console This is related to the Console in progress We're working on it ui/web This is related to a web interface
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@htdvisser @kschiffer @bafonins @laurensslats