Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
juju: add support for redirection when connecting to a model #5684
Conversation
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Does not match ['fixes-1593299', 'fixes-1594580', 'fixes-1593761', 'fixes-1591290', 'fixes-1581157', 'fixes-1593838', 'fixes-1586890'] |
|
$$JFDI$$ (signed off courtesy of cherylj) |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
cherylj
commented
Jun 22, 2016
|
$$JFDI$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$JFDI$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
rogpeppe commentedJun 21, 2016
•
Edited 1 time
-
ericsnowcurrently
Jun 21, 2016
We are going to have controllers which multiplex other
controllers. In such a case, we don't want to require
all the network traffic for the models that the sub-controllers
control to pass through the top level hub, so allow
a controller to return a "redirect required" error to cause
a client to connect to the model API in the sub-controller
(or some other server) directly.
There is more work to be done after this lands. In particular,
we should cache the API addresses that we were redirected
to and associate them with the model, so we can connect
directly on subsequent API opens.
(Review request: http://reviews.vapour.ws/r/5127/)