
On Thu, Sep 13, 2018 at 9:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Sep 12, 2018 at 7:17 PM, Gal Ben Haim <gbenhaim@redhat.com> wrote:
Hi,
The most common way is to use SSH forwarding (local port).
Yes, that's what I was doing, but was hoping for something better. The problem with this is that I have to use custom ports, and to know beforehand the names. Even then, things such as pressing the "Console" button of a vm in the admin ui do not work - at least in my case, the vnc client tried to connect to the host's IP address, not to a name. So I couldn't fake a connection by adding an ssh tunnel and an entry to /etc/hosts.
How about e.g. making lago use a bridged network, instead of a NATted one? Or something like that? I see that I can change the network type in the lago init file to 'bridge'. Is this supported? In use? Documented? Now going to try...
A month later, an update: Network type 'bridge' didn't work for me. I managed to do what I wanted by using ssh -w. After spending quite a lot of time trying this without success, I searched and found this: https://unix.stackexchange.com/questions/268690/for-some-reason-sudo-ssh-w-a... sudo ssh -o Tunnel=ethernet -w 1:1 didi-box2 This created a tap1 device on both my laptop and didi-box2. Not sure which bridge I should connect to, on didi-box2. So did this: $ cd /home/ybardavi/git/ovirt-system-tests/deployment-basic-suite-master $ lago shell engine # grep FQDN /etc/ovirt-engine/engine.conf.d/*conf ENGINE_FQDN=engine # grep engine /etc/hosts 192.168.201.4 engine # ip a The devide with above address is eth0. It has mac address 54:52:c0:a8:c9:04 On didi-box2: # ip a No device there has that mac address. Closest one is vnet8, with fe:52:c0:a8:c9:04 . # brctl show vnet8 is in the bridge c946-7428207 . TODO Make all of above easier. E.g.: 1. Rename VM interfaces to show function - instead of 'eth0', call it 'mgmt', etc. 2. Rename host interfaces to show function - 'vnet8' -> 'engine-mgmt', or 'engine-mgmt-$RANDOM' 3. Rename host bridges to show function - e.g. 'c946-7428207' -> 'mgmt' (or 'mgmt-$RANDOM') Now: on didi-box2: # brctl addif c946-7428207 tap1 # ip link set tap1 up On didi-lap: # brctl addbr ost-mgmt # brctl addif ost-mgmt tap1 # ip link set tap1 up # dhclient -1 ost-mgmt # ip a ost-mgmt got 192.168.201.4 Now added to didi-lap's /etc/hosts: 192.168.201.4 engine Then connected with a browser on didi-lap to https://engine/ and it worked. Later, noticed that this killed my Internet connectivity. Checked and fixed with: ip route del default via 192.168.201.1 dev ost-mgmt TODO: Fix that too. Perhaps we can (optionally?) add custom configuration to the dhcp server to not pass a default gateway to some range of MAC addresses, or something like that. Best regards,
You can find an example in [1]. Please make sure to update /etc/hosts with a mapping from "engine" to the engine's VM IP, otherwise the UI and imageio will not work.
[1] - https://ovirt-system-tests.readthedocs.io/en/latest/general/running_tests/in...
On Wed, Sep 12, 2018 at 1:27 PM, Yedidyah Bar David <didi@redhat.com> wrote:
Hi all,
Is there a documented way to connect to lago VMs where lago runs on a remote machine?
I realize I can use ssh, ssh with tunelling, 'lago shell', etc., but this is a bit uncomfortable.
Case in point:
I want to use OST on some machine (not my laptop) and use it to debug imageio after ovirt-engine-rename. So I need to:
1. Get OST, e.g. basic suite, running 2. Verify that imageio works - here is where I am stuck. Ideally, I'd like to be able to run a browser on my laptop and upload an image directly to the OST env. 3. Run rename 4. Try again to upload an image and fix the broken stuff :-)
I realize that two solutions I can already use might be:
1. Run a browser, or perhaps a proxy, on the OST machine 2. Create a complex set of ssh tunnels
Anything else?
Thanks, -- Didi _______________________________________________ lago-devel mailing list -- lago-devel@ovirt.org To unsubscribe send an email to lago-devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/lago-devel@ovirt.org/message/TGX2FJ7J5...
-- GAL bEN HAIM RHV DEVOPS
-- Didi
-- Didi