# Unmaintained collection: openvswitch.openvswitch **URL:** \ **Category:** Project Discussions\ **Tags:** resolved, community-wg, awx, collections\ **Created:** [June 7, 2024, 3:07pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245 "2024-06-07T15:07:08Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 7, 2024, 3:07pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/1 "2024-06-07T15:07:08Z")
There has been a deprecation announcement in [The Bullhorn #123](http://forum.ansible.com/t/2568) for the [openvswitch.openvswitch](https://github.com/ansible-collections/openvswitch.openvswitch) collection. It says there won’t be any more major releases, but I don’t see any minor or even bugfix release either for quite some time. There is no information about deprecation neither in the repo nor on [galaxy](https://galaxy.ansible.com/ui/repo/published/openvswitch/openvswitch/). However, I suggest to remove it ASAP. That is in the Ansible Community Package 11. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 8, 2024, 12:37pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/2 "2024-06-08T12:37:09Z")
I have created a [Removal from Ansible Community Package](https://github.com/ansible-collections/openvswitch.openvswitch/issues/120) issue in the repository. It’s loosely based on the text that I use for the [Identifying and removing an unmaintained collection process](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#id6). But since they did announce the removal in The Bullhorn but nowhere else, this doesn’t really fit and I’ve improvised a bit. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 9, 2024, 12:28pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/3 "2024-06-09T12:28:45Z")
Also, it looks like sanity tests are failing for `stable-2.16`+. ---
**Author:** ![dom\_Salvator](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dom_salvator/32/3678_2.png) [@dom\_Salvator](https://forum.ansible.com/u/dom_Salvator)\ **Post date:** [June 10, 2024, 4:51am UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/4 "2024-06-10T04:51:04Z")
Hello, I am new to this community, but as I go through this discussion I am curious about the openvswitch collection. Can you explain it in simple terms? ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 10, 2024, 3:24pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/5 "2024-06-10T15:24:55Z")
> [@dom\_Salvator](#): > > Can you explain it in simple terms? What, the collection? No, I don’t really know it 🤷 From the name (and the desription you can find, for example, in the repository README) it’s about configuring [Open vSwitch](https://en.wikipedia.org/wiki/Open_vSwitch). Or do you mean this discussion in general? Well, in simple terms: From time to time we have a look at the collections included in the [Ansible Community Package](https://pypi.org/project/ansible/) (ACP) and ask ourselves if there are some that should be removed to keep it sane. And working on those [that are possibly unmaintained](http://forum.ansible.com/t/6162) is a good starting point. This is _just_ about removing a collection from ACP, nothing else. It will stay available on GitHub and Galaxy. If not, someone else will have removed it but not us. ---
**Author:** ![dom\_Salvator](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dom_salvator/32/3678_2.png) [@dom\_Salvator](https://forum.ansible.com/u/dom_Salvator)\ **Post date:** [June 12, 2024, 5:47am UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/6 "2024-06-12T05:47:45Z")
Thank you for the explanation and informative links 😇 ---
**Author:** ![nilashishc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nilashishc/32/3961_2.png) [@nilashishc](https://forum.ansible.com/u/nilashishc)\ **Post date:** [June 12, 2024, 2:23pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/7 "2024-06-12T14:23:39Z")
Hello @mariolenz! I’m from the Ansible Network team, that maintains the openvswitch.openvswitch collection. This collection was deprecated in December, 2023 and will reach end-of-life on December, 2025. During this period, we will _only_ be doing patch releases for this collection if a critical bug or security vulnerability has been reported. We will continue to run `ansible-test` in CI for ansible-core\<=2.17, \>=2.15 and as such compatibility with ansible-core versions \>2.17 will not be guaranteed. I have opened a PR that fixes the sanity failure with \>=stable-2.16 and also an update to the README mentioning all the above. (Apologies to the Community for not doing that along with the Bullhorn announcement.) Please let me know if the above points would qualify this collection to continue being included in the Ansible Community Package. Thank you! ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 12, 2024, 3:29pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/8 "2024-06-12T15:29:31Z")
> [@nilashishc](#): > > This collection was deprecated in December, 2023 and will reach end-of-life on December, 2025. During this period, we will _only_ be doing patch releases for this collection if a critical bug or security vulnerability has been reported. Thanks @nilashishc, this is a very important and valuable information! This sounds like we shouldn’t remove the collection ASAP / from Ansible 11. But also that we might want to announce the deprecation / removal from a future version of the Ansible Community Package. If we keep releasing new Ansible versions as we did in the past, I think 13 would have an ETA of around November 2025 and would be a good time. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 12, 2024, 5:57pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/9 "2024-06-12T17:57:06Z")
[Compatibility with ansible-core\>2.17 is not guaranteed](https://github.com/ansible-collections/openvswitch.openvswitch/blob/main/README.md) looks problematic. ---
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [June 12, 2024, 7:33pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/10 "2024-06-12T19:33:27Z")
So for my understanding, this collection would need to be officially deprecated in… Ansible community package 11.0.0 release so it can be removed in 13? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [June 12, 2024, 8:03pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/11 "2024-06-12T20:03:47Z")
We can also deprecate it now and remove it already from 11.0.0. Or from 12.0.0. Or from 13.0.0. Whatever we prefer (and decide on). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 13, 2024, 3:28pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/12 "2024-06-13T15:28:26Z")
Let’s move the discussion to [Several collections have been deprecated by the Ansible Network team](http://forum.ansible.com/t/6360). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 19, 2024, 7:45pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/13 "2024-06-19T19:45:34Z")
Since this collection hasn’t been only deprecated, but it’s clear now that ansible-core 2.18 won’t be supported (see [here](https://github.com/ansible-collections/openvswitch.openvswitch/commit/edf3538ed34198f44ced8b7c3dd4501837a69ea0) and [here](https://github.com/ansible-collections/openvswitch.openvswitch/commit/645088eba8ec2b29b196c25559352f583bda0d6e)) we _have_ to remove it from the Ansible Community Package 11 because it will be based on this. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 20, 2024, 6:29pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/14 "2024-06-20T18:29:22Z")
We’ve [removed both frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) from the Ansible Community Package 11. In case anyone wonders why we didn’t vote on this: We’ve talked about this in the community meeting and decided we don’t need one because of [Removing a collection that has been explicitly deprecated or abandoned by its (former) maintainers](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#removing-a-collection-that-has-been-explicitly-deprecated-or-abandoned-by-its-former-maintainers). ---
**Author:** ![TafkaMax](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tafkamax/32/8430_2.png) [@TafkaMax](https://forum.ansible.com/u/TafkaMax)\ **Post date:** [June 18, 2025, 7:26am UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/15 "2025-06-18T07:26:43Z")
So is there an alternative? ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [June 18, 2025, 7:45am UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/16 "2025-06-18T07:45:26Z")
You can still install them using ```auto ansible-galaxy collection install frr.frr # or replace the name ``` If there’s a different collection for one (or both) of the technologies, that should be found in Galaxy, and installed the same way as described above. ---
**Author:** ![noonedeadpunk](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/noonedeadpunk/32/7605_2.png) [@noonedeadpunk](https://forum.ansible.com/u/noonedeadpunk)\ **Post date:** [August 19, 2025, 6:05pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/17 "2025-08-19T18:05:55Z")
fwiw, specifically for FRR, we also maintain a role here which is not dependent on `frr.frr` collection. It’s not published to galaxy though (so far): > **[ansible-role-frrouting](https://opendev.org/openstack/ansible-role-frrouting)** > > Ansible role to deploy FRRouting ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [November 18, 2025, 3:51pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/18 "2025-11-18T15:51:31Z")
@nilashishc (or anyone else from the Ansible Network team) Do you think you could help with [Picking up maintenance of that repository](https://github.com/ansible-collections/openvswitch.openvswitch/issues/127)? cc @gundalow ---
**Author:** ![noonedeadpunk](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/noonedeadpunk/32/7605_2.png) [@noonedeadpunk](https://forum.ansible.com/u/noonedeadpunk)\ **Post date:** [November 18, 2025, 4:04pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/19 "2025-11-18T16:04:49Z")
I was involved in the original discussion and can also volunteer to help out with maintenance of the openvswitch.openvswitch collection, as we are using it in our tooling. ---
**Author:** ![nilashishc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nilashishc/32/3961_2.png) [@nilashishc](https://forum.ansible.com/u/nilashishc)\ **Post date:** [November 18, 2025, 4:13pm UTC](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245/20 "2025-11-18T16:13:13Z")
Hi. I’m no longer a part of the Ansible Network team. I request you to check with Rohit Thakur or Sagar Paul (KB-perByte). However, I do know that there’s an on-going discussion with someone from a different organization around taking ownership of this collection. Rohit/Sagar can provide more details. Thanks! [Next page](https://forum.ansible.com/t/unmaintained-collection-openvswitch-openvswitch/6245.md?page=2)