-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Ability to list all regions and their datacenters #243
Comments
Thanks for the suggestion! We would like to add more ways to inspect Nomad's internal state, including datacenters and regions. We haven't scheduled work on this yet but we'd be happy to look at a PR for it. |
Regions are now query-able, however the individual datacenters within each region are not currently available. This is a little more involved because we don't have the convenience of the gossip protocol for the client nodes, and by design only a single datacenter per region should have servers deployed in it. Nomad's API calls are all driven by the region ID and not the datacenter, so I'm not sure how useful it would even be. @F21 let me know if there is a specific use case you have in mind. |
@ryanuber My usecase is to build a web UI to perform monitoring and show the status of the nomad cluster. One of the key features would be to have a dashboard that shows all the clients and servers from all regions, and to be able to filter them by region and datacenter. |
For the time being, with the addition of the |
I think that should be sufficient for now, however querying each node poses a scalability issue if we have got loads of nodes. Maybe an endpoint to get the status of nodes in 1 go would be nice, but I think we should open another issue for that. |
The |
Disable parent directory fsync on windows
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
It would be nice if there's a way (using the cli and the http api) to get a list of all regions and their datacenters.
The text was updated successfully, but these errors were encountered: