Repository navigation
test: forward the web interface and SSH of each DUT to the host - #1808
Conversation
troglobit
left a comment
There was a problem hiding this comment.
I don't see any why motivation anywhere for this? Also, if we decide to do this, why not also forward SSH?
An AFK discussion would be nice.
the why is to be able to test the web ui in obscure setups (that our test system gives us in various test cases), SSH i see no use for, since we already have the consoles to the duts exported |
Do you mean test manually from outside the Docker? Because from inside the docker the webui should already be accessible, right? If you mean manually, then I really do see a reason to also export SSH since the same use-case may very well appear there too. |
Yeah, it is manual/agent driven testing that the goal here. Ok, I can agree with that. Inside the docker it is available, yes. This is only to access the duts from outside the container. |
|
OK then I get it, please add SSH then 😃 Would be nice with even bigger topologies as well in that case ... |
d81625f to
08a33f3
Compare
To open the WebUI of a DUT in the virtual topology, or to SSH to it from the host, you had to set up a forward by hand inside the container, every time it started. Each DUT with a mgmt port now gets ports of its own. They are published to the host and follow the console ports: 9001 is the console of dut1, 9011 its web interface and 9021 its SSH server. Signed-off-by: Mattias Walström <lazzer@gmail.com>
08a33f3 to
5505f32
Compare
Description
To open the WebUI of a DUT in the virtual topology, or to SSH to it from the host, you had to set up a forward by hand inside the container, every time it started.
Each DUT with a mgmt port now gets ports of its own. They are published to the host and follow the console ports: 9001 is the console of dut1, 9011 its web interface and 9021 its SSH server.
Unsure if this is a good thing to always have, or if you should have this opt-in.
Checklist
Tick relevant boxes, this PR is-a or has-a:
test/env