--=_3a566eec-e693-4569-8838-2970ac73adac
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Hi,
In the way Ovirt is currently designed, is there a way to separate the following elements
in different VLANs :
1) Communication betweem nodes (hypervisors) and engine (manager)
2) Access to webadmin interface
3) access to user web interface
It seems that the following elements all rely on ovirtmgmt, right ?
Regards,
Alexis
--=_3a566eec-e693-4569-8838-2970ac73adac
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"font-family: arial, helvetica, sans-serif;
font-s=
ize: 12pt; color: #000000"><div>Hi,<br
data-mce-bogus=3D"1"></div><div><br =
data-mce-bogus=3D"1"></div><div><br
data-mce-bogus=3D"1"></div><div>In the =
way Ovirt is currently designed, is there a way to separate the following e=
lements in different VLANs :<br
data-mce-bogus=3D"1"></div><div><br data-mc=
e-bogus=3D"1"></div><div>1) Communication betweem nodes
(hypervisors) and e=
ngine (manager)<br data-mce-bogus=3D"1"></div><div>2) Access
to webadmin in=
terface<br data-mce-bogus=3D"1"></div><div>3) access to user
web interface<=
br data-mce-bogus=3D"1"></div><div><br
data-mce-bogus=3D"1"></div><div>It s=
eems that the following elements all rely on ovirtmgmt, right ? <br data-mc=
e-bogus=3D"1"></div><div><br
data-mce-bogus=3D"1"></div><div><br data-mce-b=
ogus=3D"1"></div><div>Regards,<br
data-mce-bogus=3D"1"></div><div>Alexis<br=
data-mce-bogus=3D"1"></div></div></body></html>
--=_3a566eec-e693-4569-8838-2970ac73adac--