Support separate RPC interfaces for multiple regions
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Issue:
There is only one interface for RPC currently. The problem is that in a multi DC setup with federation we have to specify public IP's. This is a bad tradeoff for intra-region scaling of of nomad clients in that we would have to punch security group rules for each new nomad client added to a DC e.g. we should be using private ips for RPC intra-region.
Proposal:
Per discussion on IRC with diptanu add "wan_advertise" for cross region federation and allow "rpc" to be used for intra region rpc.
Related maybe: https://github.com/hashicorp/nomad/issues/304.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing Nomad's RPC and federation configuration, then compare the related issue #304; done means supporting separate intra-region rpc and cross-region wan_advertise addresses without requiring public IPs for intra-region clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100