<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><div>Using self-hosted engine.<br></div><div>I thought about using several interfaces on the engine VM.</div><div><br></div><div>The reason why I want to do that : I would like the users accessing the web interface not to be on the same network that ovirt is using to communicate betweem hosts and engine.</div><div>But it would mean that 2 different FQDN are necessary, right ? I heard HA requires to access to the engine FQDN...</div><div><br></div><div>Do you have any idea how to solve this situation ?</div><div><br></div><div><br></div><div>Alexis</div><br></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div data-marker="__QUOTED_TEXT__">On 24 August 2017 at 15:39, Alexis HAUSER<br><alexis.hauser@imt-atlantique.fr> wrote:<br>><br>> In the way Ovirt is currently designed, is there a way to separate the<br>> following elements in different VLANs :<br>><br>> 1) Communication betweem nodes (hypervisors) and engine (manager)<br>> 2) Access to webadmin interface<br>> 3) access to user web interface<br>><br>> It seems that the following elements all rely on ovirtmgmt, right ?<br><br>Only #1. #2 and #3 could be changed AFAIK, depending on where and how<br>you run the engine (Fir e.g. if you run it on a separate host, you<br>could attach other interfaces with other VLANs to it).<br><br><br>-- <br>Barak Korren<br>RHV DevOps team , RHCE, RHCi<br>Red Hat EMEA<br>redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted<br></div></div></body></html>