On Mon, Jan 24, 2022 at 10:30 AM ravi k <[email protected]> wrote: > > 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? > > We are still in the initial stages and so conducting a POC. > > > 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. > > We are planning to clone a VM and then migrate it to note down the > findings. We will surely verify the virtual nic hw as well. > > > 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...)? > > We have SDN implemented at our physical network level. IIRC it is Cumulus. > We do not have NSX. What I meant was as we have SDN implemented at the > physical network level. So will it make it easier to connect our Ovirt to > the physical network. > I will go through the docs you updated and come back. > > > 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. > > My apologies. I wasn't clear. As the IP was assigned on bond0 which is a > LACP bond, do we need to make any changes before running the vdsm-tool > ovn-config <ovn-central-ip> <hypervisor ip> ? >
You should not run ovn-config manually, if the host bond0 has ovirtmgmt on top of it. That is all done by host deploy. The step might be needed if you want to have a tunnel on a different interface than ovirtmgmt is using. > > some manual undocumented steps through OpenStack Networking API or > Ansible > > could be required depending on your needs > > I'll go through the docs you mentioned and update here about my progress. > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/FCOB5JRZVHFYDDUNWP5JUL2T6OA2IILG/ > -- Ales Musil Senior Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> [email protected] IM: amusil <https://red.ht/sig>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/4XDK2BWKZIV5YLNHK6LOSU5BLW7LEEL7/
