Migration network used also as vm network
Hello, I have a 10Gbit vlan defined as migration network and currently not enabled as vm network. When you configure a host interface, assigning a vlan that is defined as migration network, you must assign an ip to it on the host. Suppose I want to edit this vlan in DC so that I enable it to be also a VM network, are there any drawbacks having for example on a host the ip for this vlan (the migration ip) and also one or more running VMs with their vnics configured on this vlan too...? Thanks in advance, Gianluca
Hello Gianluca, This should work as expected. The only drawbacks that could be are loads on the link in case of heavy traffic. If for example the VMs using most of the link's traffic it may affect the migration and vise-versa. Cheers) On Tue, Jul 25, 2017 at 10:24 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
Hello, I have a 10Gbit vlan defined as migration network and currently not enabled as vm network. When you configure a host interface, assigning a vlan that is defined as migration network, you must assign an ip to it on the host.
Suppose I want to edit this vlan in DC so that I enable it to be also a VM network, are there any drawbacks having for example on a host the ip for this vlan (the migration ip) and also one or more running VMs with their vnics configured on this vlan too...?
Thanks in advance, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Michael Burman RedHat Israel, RHV-M Network QE Mobile: 054-5355725 IRC: mburman
Hello Gianluca, As far as i know this shouldn't be a problem, you can have ips on any interface. The only drawbacks can be related to performance of migrations if vms on that interface makes too much traffic. Luca Il 25 lug 2017 9:25 AM, "Gianluca Cecchi" <gianluca.cecchi@gmail.com> ha scritto:
Hello, I have a 10Gbit vlan defined as migration network and currently not enabled as vm network. When you configure a host interface, assigning a vlan that is defined as migration network, you must assign an ip to it on the host.
Suppose I want to edit this vlan in DC so that I enable it to be also a VM network, are there any drawbacks having for example on a host the ip for this vlan (the migration ip) and also one or more running VMs with their vnics configured on this vlan too...?
Thanks in advance, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
There is a security drawback involved as well, the VM/s can access the host through that IP. On Tue, Jul 25, 2017 at 10:45 AM, Luca 'remix_tj' Lorenzetto < lorenzetto.luca@gmail.com> wrote:
Hello Gianluca,
As far as i know this shouldn't be a problem, you can have ips on any interface.
The only drawbacks can be related to performance of migrations if vms on that interface makes too much traffic.
Luca
Il 25 lug 2017 9:25 AM, "Gianluca Cecchi" <gianluca.cecchi@gmail.com> ha scritto:
Hello, I have a 10Gbit vlan defined as migration network and currently not enabled as vm network. When you configure a host interface, assigning a vlan that is defined as migration network, you must assign an ip to it on the host.
Suppose I want to edit this vlan in DC so that I enable it to be also a VM network, are there any drawbacks having for example on a host the ip for this vlan (the migration ip) and also one or more running VMs with their vnics configured on this vlan too...?
Thanks in advance, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Edward Haas -
Gianluca Cecchi -
Luca 'remix_tj' Lorenzetto -
Michael Burman