[ovirt-users] Re: New oVirt setup with OVN : Hypervisor with LACP bond : queries

On Sat, Jan 22, 2022 at 11:41 PM ravi k <kottapar(a)gmail.com&gt; wrote: Hi, Thank you for all the wonderful work you've been doing. I'm starting out Can you give some more details about your current vSphere infrastructure? What about the level of downtime you could give when migrating? Have you already planned the strategy to transfer your VMs from vSphere to oVirt? Take care that probably on your VMware side your VMs have virtual hw for nics defined as vmxnet, so when you migrate to oVirt, it will change and so depending on your OS type (Windows based or Linux based) and in case of Linux, depending on your distro and version, some manual operations could be required to remap vnic assignments and definitions. One possible first way to proceed could be to make a clone of one running VM into one disconnected from the vSphere infra and then test on it the steps to port to oVirt and so analyze times and impacts The downstream (RHV) documentation to do it is here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/... the upstream one is here: https://www.ovirt.org/documentation/administration_guide/#Adding_OVN_as_a... Take care that in RHV this feature is still considered Technology Preview, so not recommended for production. It could apply to oVirt even more, so... BTW, what do you mean with "... the fact that we have a SDN..."? Do you mean standard virtual networking in contrast with physical one or do you have any kind of special networking in vSphere now (NSX or such...)? That was a thread originated by me... ;-) But please consider that it is 5 years old now! At that time we were at 4.1 stage, while now we are at very different 4.4, so refer in case to recent threads and better recent upstream (oVirt) and downstream (RHV) official documentation pointed above Also, at that time ansible was not very much in place, while now in many configuration tasks it is deeply involved. The main concern in that thread was the impact of having OVN tunneling on the ovirtmgmt management network, that is the default choice when you configure OVN, in contrast with creating a dedicated network for it. The downstream documentation and notes for this is here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/... and upstream here: https://www.ovirt.org/documentation/administration_guide/#Assigning_Secur... some manual undocumented steps through OpenStack Networking API or Ansible could be required depending on your needs BTW: both upstream and downstream docs refer here to 4.2.7.... : " In oVirt 4.2.7, security groups are disabled by default. " and " In Red Hat Virtualization 4.2.7, security groups are disabled by default. " They should be changed with the corresponding version, or into something like "in 4.2.7 and above..." if that applies and is intended no problem ;-) Gianluca