# Several collections have been deprecated by the Ansible Network team **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, collections\ **Created:** [June 13, 2024, 3:22pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360 "2024-06-13T15:22:12Z")\ **Posts on this page:** 12\ **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 13, 2024, 3:22pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/1 "2024-06-13T15:22:12Z")
This joins the following discussions: - [Unmaintained collection: frr.frr](http://forum.ansible.com/t/6243) - [Unmaintained collection: openvswitch.openvswitch](http://forum.ansible.com/t/6245) - [Unmaintained collection: vyos.vyos](http://forum.ansible.com/t/6244) The reason is that the situation for those three collections is the same. It’s probably easier to have the discussion about them in one place. Important information on the deprecation: > [@Unmaintained collection: frr.frr](http://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/4): > > deprecated in December, 2023 and will reach end-of-life on December, 2025 So I thought to remove it from Ansible 13. _But_: > [@Unmaintained collection: vyos.vyos](http://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/5): > > 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. So maybe we should remove it earlier. Not sure 🤷 ---
**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 13, 2024, 3:51pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/2 "2024-06-13T15:51:34Z")
So they are testing against what is currently the core version in Ansible community package 11, and will not be tested for the core version for what will be Ansible community package 12. So yeah, feels like if it’s not breaking any rules, they should be deprecated asap so we can remove in Ansible community package 12. ---
**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, 5:10pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/3 "2024-06-13T17:10:35Z")
It would help if [@network-wg](https://forum.ansible.com/groups/network-wg) would make clear that they will _not_ support ansible-core \> 2.17. I think “compatibility with ansible-core versions \>2.17 will not be guaranteed” is a little bit unclear. ---
**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 14, 2024, 4:27am UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/4 "2024-06-14T04:27:36Z")
@mariolenz thank you for pointing it out! I’ve updated the README to be more specific. ---
**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 14, 2024, 4:27am UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/5 "2024-06-14T04:27:53Z")
@samccann @mariolenz The Ansible Network team is okay with deprecating these collections from Ansible 11 and removing them in Ansible 12. Please let us know if there’s anything needed from our side. Thank you! ---
**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 14, 2024, 5:12am UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/6 "2024-06-14T05:12:02Z")
> [@samccann](#): > > So they are testing against what is currently the core version in Ansible community package 11, and will not be tested for the core version for what will be Ansible community package 12. Ansible 10 is based on ansible-core 2.17, which the collections tests against. Ansible 11 will be based on ansible-core 2.18, which the collections do no longer test against, if I understood correctly. ---
**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 14, 2024, 3:17pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/7 "2024-06-14T15:17:27Z")
> [@felixfontein](#): > > Ansible 11 will be based on ansible-core 2.18, which the collections do no longer test against, if I understood correctly. Not only not tested against, those collections are not supported with ansible-core\>2.17: current [frr.frr README](https://github.com/ansible-collections/frr.frr/blob/90fa27060a0195a211911398d9959049985bbbba/README.md), [openvswich.openvswitch README](https://github.com/ansible-collections/openvswitch.openvswitch/blob/edf3538ed34198f44ced8b7c3dd4501837a69ea0/README.md) and [vyos.vyos README](https://github.com/ansible-collections/vyos.vyos/blob/37baff3d4d547911bec1387218edfd477ca79062/README.md) @nilashishc I’m not sure if this is really supported and would work, but maybe you should change `requires_ansible: ">=2.9.10"` in `meta/runtime.yml` to `requires_ansible: ">=2.9.10,<2.18.0"` ---
**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 18, 2024, 10:01am UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/8 "2024-06-18T10:01:49Z")
> [@mariolenz](#): > > @nilashishc I’m not sure if this is really supported and would work, but maybe you should change `requires_ansible: ">=2.9.10"` in `meta/runtime.yml` to `requires_ansible: ">=2.9.10,<2.18.0"` Thanks @mariolenz. That’s a good idea. I’ll update the runtime information. ---
**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 18, 2024, 4:37pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/9 "2024-06-18T16:37:00Z")
It looks like `meta/runtime.yml` now states `requires_ansible: ">=2.9.10,<2.18.0"` for `frr.frr` and `openvswitch.openvswitch`, but not for `vyos.vyos`. Is there a reason for this? Or is it just a question of finding the time to do it? I don’t want to put any pressure on anyone, I just want to understand 😇 ---
**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 19, 2024, 9:11am UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/10 "2024-06-19T09:11:44Z")
@mariolenz There’s a possibility of vyos.vyos being taken up by another set of maintainers. We’re currently in discussions regarding that. This is why I’ve not made the same meta/runtime.yml change in it. ---
**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, 2:56pm UTC](https://forum.ansible.com/t/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/11 "2024-06-19T14:56:10Z")
I thought something like this might be the reason. Thanks for the info 🙂 ---
**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/several-collections-have-been-deprecated-by-the-ansible-network-team/6360/12 "2024-06-20T18:29:57Z")
[Remove frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) Let’s move the discussion about `vyos.vyos` back to [Unmaintained collection: vyos.vyos](http://forum.ansible.com/t/6244)