On Fri, 22 Feb 2019 15:50:23 +0100 (CET) Karli Sjöberg <ka...@inparadise.se> wrote:
> > > Den 22 feb. 2019 15:48 skrev Dominik Holler <dhol...@redhat.com>: > On Fri, 22 Feb 2019 15:46:00 +0100 (CET) > > Karli Sjöberg wrote: > > > > > > > > > > > Den 22 feb. 2019 15:35 skrev Dominik Holler : > > > On Fri, 22 Feb 2019 15:02:10 +0100 (CET) > > > > Karli Sjöberg wrote: > > > > > > > > > > > > > > > > > > > Den 22 feb. 2019 09:24 skrev Nicolas Ecarnot : > > > > > Hello, > > > > > > > > > > > > I'm almost sure the following is useless as I think I know how it's > > > > > > working, but as I'm preparing a major change in our infrastructure, > > > > > > I'd > > > > > > rather be sure and not mess up. And also to be sure. > > > > > > (Just to be sure) > > > > > > > > > > > > For some reasons, and for the first time in our infra., one of our > > > > > > new > > > > > > DC will temporary include heterogeneous hosts : some networks will > > > > > > be > > > > > > available only on parts of them. > > > > > > > > > > > > > > Should work. > > > > > > > > > Hosts _needs_ the same networks to be available in the same cluster. > > > > > Different networked hosts needs to be put in a separate cluster. > > > > > > > > > > > > > This is the most straight approach, which is supported by oVirt. > > > > But there is the possibility to attach logical networks, which are > > > > neither required in the cluster, nor attached to all hosts in the > > > > cluster, to a VM. oVirt's scheduling will respect this. > > > > > > > So you're saying oVirt knows which other hosts in the cluster have the > > > non-mandatory network(s) the VM has and only chooses between those a host > > > to migrate the VM to? > > > > > > > Yes. If you try to trigger the migration manually, UI will provide you > > the list of possible hosts to migrate the VM. > > > Well, what about automatically migrated VM's? > The same rules apply. > /K > > > > > /K > > > > > > Of course this introduces some obvious limitations, e.g. you cannot > > > > hotplug a network to a VM, which runs on a host, which is not connected > > > > to this network or neither you nor oVirt can schedule a VM to a host, > > > > which does not provide all the networks attached to the VM. > > > > > > > > If you want to be even more sure, the reference to the relevant source > > > > https://github.com/oVirt/ovirt-engine/blob/7d111f3aa089f77f92049f4d3ec792e5ff7e5324/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/scheduling/policyunits/NetworkPolicyUnit.java#L132 > > > > > > > > > > > > > /K > > > > > > > > > > > > > > > > Please may someone confirm me that with every load balancing / VM > > > > > > startup / VM migration / host choice, oVirt will smartly choose the > > > > > > available host equipped with the adequate networks? > > > > > > > > > > > > -- > > > > > > Nicolas ECARNOT > > > > > > _______________________________________________ > > > > > > Users mailing list -- users@ovirt.org > > > > > > To unsubscribe send an email to users-le...@ovirt.org > > > > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > > > > oVirt Code of Conduct: > > > > > > https://www.ovirt.org/community/about/community-guidelines/ > > > > > > List Archives: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QGX3PHA4T3SXXDTYZ4VGY6UHECO7P6V5/ > > > > > > > > > > > > > > > > > > _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/C23VQXZZS6GS4OQS6JHWEOPVHLK73QCI/