[neutron]
Danny Webb
Danny.Webb at thehutgroup.com
Tue Mar 21 11:22:43 UTC 2023
Not via kolla-ansible as far as I know, tripleo had some migration steps built in that you may be able to mimic. When we did our migration we had our internal tenants evacuate the region and we rebuilt in situ.
________________________________
From: Kamil Madac <kamil.madac at gmail.com>
Sent: 21 March 2023 10:27
To: Danny Webb <Danny.Webb at thehutgroup.com>
Cc: openstack-discuss <openstack-discuss at lists.openstack.org>
Subject: Re: [neutron]
CAUTION: This email originates from outside THG
________________________________
Hi Danny,
thanks for sharing your positive experience. I'm going to deploy OVN in dev environment with kolla-ansible. Maybe one more question. Is there any official way to migrate from OVS to OVN with kolla-ansible, or have you used the official migration script https://docs.openstack.org/networking-ovn/latest/install/migration.html<https://docs.openstack.org/networking-ovn/latest/install/migration.html?>?
On Thu, Mar 16, 2023 at 5:43 PM Danny Webb <Danny.Webb at thehutgroup.com<mailto:Danny.Webb at thehutgroup.com>> wrote:
Hi Kamil,
We're currently running 4 (soon to be 5) production regions all using kolla ansible as our deployer with OVN as our neutron backend. It's been fairly solid for us and we've had less issues with OVN than the traditional hybrid OVS / Iptables neutron driver (which we ran for about a year before switching to OVN). Our regions are anywhere from 50-60 compute hosts with 1-2k+ VMs per region. As far as I know most of the new development is going into OVN so would be a good place to start. Ultimately, we've only really had 2 real issues whilst running it. First was an issue where we had the provider network spamming gateway changes into southbound as we had our anycast SVI bound to our top of rack switches which made OVN keep updating it's location. We mitigated this by moving the provider SVIs to our border routers and the issue went away and dropped the load on our OVN controllers significantly. Only other real issue we had was during an upgrade of a region we ended up with what we believed to be some sort of stale flows that resulted in some hypervisors losing connectivity until we rebooted them.
Hope this helps!
Cheers,
Danny
________________________________
From: Kamil Madac <kamil.madac at gmail.com<mailto:kamil.madac at gmail.com>>
Sent: 14 March 2023 09:46
To: openstack-discuss <openstack-discuss at lists.openstack.org<mailto:openstack-discuss at lists.openstack.org>>
Subject: [neutron]
CAUTION: This email originates from outside THG
________________________________
Hi All,
I'm in the process of planning a small public cloud based on OpenStack. I have quite experience with kolla-ansible deployments which use OVS networking and I have no issues with that. It works stable for my use cases (Vlan provider networks, DVR, tenant networks, floating IPs).
For that new deployment I'm looking at OVN deployment which from what I read should be more performant (faster build of instances) and with ability to cover more networking features in OVN instead of needing external software like iptables/dnsmasq.
Does anyone use OVN in production and what is your experience (pros/cons)?
Is OVN mature enough to replace OVS in the production deployment (are there some basic features from OVS missing)?
Thanks in advance for sharing the experience.
--
Kamil Madac<https://kmadac.github.io/>
Danny Webb
Principal OpenStack Engineer
Danny.Webb at thehutgroup.com<mailto:Danny.Webb at thehutgroup.com>
[THG Ingenuity Logo]<https://www.thg.com>
[https://i.imgur.com/wbpVRW6.png]<https://www.linkedin.com/company/thgplc/?originalSubdomain=uk> [https://i.imgur.com/c3040tr.png] <https://twitter.com/thgplc?lang=en>
--
Kamil Madac<https://kmadac.github.io/>
Danny Webb
Principal OpenStack Engineer
Danny.Webb at thehutgroup.com
[THG Ingenuity Logo]<https://www.thg.com>
[https://i.imgur.com/wbpVRW6.png]<https://www.linkedin.com/company/thgplc/?originalSubdomain=uk> [https://i.imgur.com/c3040tr.png] <https://twitter.com/thgplc?lang=en>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230321/e1672043/attachment.htm>
More information about the openstack-discuss
mailing list