On 25/04/16 09:28, Leo Yan wrote:
On Mon, Apr 25, 2016 at 08:52:39AM +0100, Daniel Thompson wrote:
[...]
As part of Leo's work for one of the members we would like to interactively run some tests on Juno.
We think the ideal structure looks pretty much like the one below:
+------------------------------------------+ + | | | | +--------------+ +-------------+ | | | | Orchestrator | ssh | | |Leo +---------------> (lisa or +---------> Juno | | | | | workflow | | | | | | | automation) | | | | + | +--------------+ +-------------+ | China | KVM Target | Firewall | lava-lab | | | +------------------------------------------+
Some observations and rationale:
- Leo needs to be able to interact with the software running on the Orchestrator via a http:// (or maybe https://) socket. An SSH tunnel with port forwarding is a good way to achieve this since then the web socket can be bound to the lo interface. This is what drives the interest in running this setup as a hacking session.
One more question, the kvm will only boot with a text console. So bind web socket with lo interface, we can launch web browser within kvm itself. So should we bind web socket with kvm's eth0, and then use my local PC to remote access Orchestrator with http://?
Sorry Leo. I was mixing requirements and potential solutions. Right now it is more important for us to clearly express the requirements. There's plenty we don't know about LAVA so better to describe what we need rather than how we try to achieve it!
The *requirement* is that you need to be able to use a web browser running on your laptop to access a service running on the orchestrator.
With the requirement stated clearly, we can go back to my original point. ssh can meet the above requirement. When it forwards a socket it can connect within the KVM using the loopback interface; that what localhost means when it appears in "-L 8888:localhost:8888".
Daniel.