<div dir="ltr">Fernando, That is the recommended approach, that ovirtmgmt bridge not also be used for VMs. This is for the sake of separation of privilege if I understand correctly, and there's no reason that VMs will not be able to communicate using that bridge. Whether or not you tag depends on your network's logical topology. If you don't tag in oVirt manager and your network uses VLANs, then the packets will be treated as belonging to the default VLAN, often ID 1, but certainly not always.<div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 31, 2016 at 12:20 PM Fernando Fuentes <<a href="mailto:ffuentes@darktcp.net" target="_blank">ffuentes@darktcp.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Team,<br>
<br>
Is it possible to move the ovirt management interface to a separate vlan<br>
and keep it from been on the same interface as my LAN?<br>
<br>
IE: assign a tag to ovirtmanagement and keep another interface as untag<br>
for my LAN to use with the VM's<br>
<br>
Thoughts ideas?<br>
<br>
TIA!<br>
<br>
Regards,<br>
<br>
--<br>
Fernando Fuentes<br>
<a href="mailto:ffuentes@txweather.org" target="_blank">ffuentes@txweather.org</a><br>
<a href="http://www.txweather.org" rel="noreferrer" target="_blank">http://www.txweather.org</a><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div></div></div>