[ovirt-users] Start VM automatically

[Alex K]

You can overwrite the console ip at cluster -> console. Try to put there
the external ip and have NAT correctly set.  This should work.

Alex

On Feb 27, 2018 12:15, "Fabrice SOLER" <fabrice.soler at ac-guadeloupe.fr>
wrote:

> Hi,
>
> We want to install ovirt for every school in Guadeloupe (~70 schools)
>
> Each school has an internet connexion with a basic physical router (no
> vpn).
>
> We have bought one physical server for each school.
>
> We have installed an ovirt engine on our central site where we want to
> manage all the node which are in the school.
>
> In first, for the tests in laboratory, I have installed a node behind a
> routeur. The routeur forwarded all the traffic from the ovirt engine to the
> ovirmgmt ip address (NAT).
>
> It works but I cannot have access to the VM consoles : my Spice client try
> to access directly to the node private IP address. Is there a solution to
> resolv this ? In ovirt documentation, I read "Spice Proxy" and  "Websocket
> Proxy".  Could these features answer to this problematic ?
>
> In the ovirt engine, is it possible to provide a NAT address to the node ?
> then the VM consoles coud work.
>
> So, I give up the above architecture and move my ovirtmgmt ip address
> behind a VM routeur which has a tunneling IPSec to our central site. The
> access to the VM consoles is resolved but I discover that the VM does not
> start automaticaly whithout the engine (like vmware does).
>
> I hope you understand my problematic.
>
> Sincerely,
> --
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180228/43bb2b9c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fabrice SOLER.PNG
Type: image/png
Size: 16525 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180228/43bb2b9c/attachment.png>