Merge lp:~allenap/maas/narrow-port-range--bug-1352923 into lp:~maas-committers/maas/trunk
Proposed by
Gavin Panella
Status: | Merged |
---|---|
Approved by: | Gavin Panella |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3930 |
Proposed branch: | lp:~allenap/maas/narrow-port-range--bug-1352923 |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
299 lines (+154/-21) 4 files modified
INSTALL.txt (+15/-0) src/maasserver/rpc/regionservice.py (+33/-5) src/maasserver/rpc/testing/fixtures.py (+1/-1) src/maasserver/rpc/tests/test_regionservice.py (+105/-15) |
To merge this branch: | bzr merge lp:~allenap/maas/narrow-port-range--bug-1352923 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mike Pontillo (community) | Approve | ||
Review via email: mp+259911@code.launchpad.net |
Commit message
Bind the region's RPC endpoints to a narrow range of ports between 5250 and 5259 inclusive.
To post a comment you must log in.
I had a quick chat with Gavin to answer some of my ignorant questions about this MP.
Q: Why do we need so many ports?! URL>/MAAS/ rpc/. (clusters periodically refresh this)
A: Because each cluster is responsible for connecting to every regiond process. (each RPC endpoint is listed in JSON format if you hit <SERVER_
Q: Why can't the cluster just connect to any random regiond?
A: Because any arbitrary regiond needs to be able to use this control channel to talk to any arbitrary clusterd. Any individual regiond has no way to directly contact any arbitrary clusterd otherwise.
That being the case, I think this change looks good. I noted a minor issue with an 'except' clause below, and possibly a more robust test case.