[Vote ended 2026-11-18] What collections should stay in the Ansible community package

Polls: What collections should stay in the Ansible community package

See the topic for context.

Here are one-per-collection polls for all the currently included collections.

The polls have two options:

  • Choose “Yes” if you think the collection satisfies the new inclusion criteria and should stay in the Ansible community package.
  • Choose “No” if you think it should be excluded.

Let’s keep it open for 2 weeks, and I’ll close it on 2026-11-18.
It’s a community public poll. The results will be informational.
I’ll adjust the PR correspondingly.
Then we could conduct the second poll in the steering committee if needed.

Please vote.

UPDATE: There are categories-related comments below the polls. As I would avoid editing the posts with open polls, please read the comments at the bottom of the thread.

1 Like

Collections suggested to keep (17) in the [PR]([Steering Committee vote is NEEDED before merge] ccollection_removal_roadmap.rst: add Ansible community package collections removal roadmap by Andersson007 · Pull Request #4113 · ansible/ansible-documentation · GitHub

ansible.netcommon
  • Yes
  • No
0 voters
ansible.utils
  • Yes
  • No
0 voters
community.general
  • Yes
  • No
0 voters
community.library_inventory_filtering_v1
  • Yes
  • No
0 voters
ansible.posix
  • Yes
  • No
0 voters
ansible.windows
  • Yes
  • No
0 voters
community.windows
  • Yes
  • No
0 voters
amazon.aws
  • Yes
  • No
0 voters
community.aws
  • Yes
  • No
0 voters
azure.azcollection
  • Yes
  • No
0 voters
google.cloud
  • Yes
  • No
0 voters
community.docker
  • Yes
  • No
0 voters
containers.podman
  • Yes
  • No
0 voters
kubernetes.core
  • Yes
  • No
0 voters
community.crypto
  • Yes
  • No
0 voters
community.dns
  • Yes
  • No
0 voters
community.libvirt
  • Yes
  • No
0 voters

Vendor-specific networking (14)

arista.eos
  • Yes
  • No
0 voters
check_point.mgmt
  • Yes
  • No
0 voters
cisco.aci
  • Yes
  • No
0 voters
cisco.intersight
  • Yes
  • No
0 voters
cisco.ios
  • Yes
  • No
0 voters
cisco.iosxr
  • Yes
  • No
0 voters
cisco.meraki
  • Yes
  • No
0 voters
cisco.mso
  • Yes
  • No
0 voters
cisco.nxos
  • Yes
  • No
0 voters
community.ciscosmb
  • Yes
  • No
0 voters
community.routeros
  • Yes
  • No
0 voters
dellemc.enterprise_sonic
  • Yes
  • No
0 voters
f5networks.f5_modules
  • Yes
  • No
0 voters
vyos.vyos
  • Yes
  • No
0 voters

Vendor-specific security appliances (2)

fortinet.fortimanager
  • Yes
  • No
0 voters
fortinet.fortios
  • Yes
  • No
0 voters

Vendor-specific server and hardware management

dellemc.openmanage
  • Yes
  • No
0 voters
ieisystem.inmanage
  • Yes
  • No
0 voters
inspur.ispim
  • Yes
  • No
0 voters

Vendor-specific secrets management (1)

cyberark.conjur
  • Yes
  • No
0 voters

Vendor-specific storage (10)

dellemc.powerflex
  • Yes
  • No
0 voters
everpure.flasharray
  • Yes
  • No
0 voters
everpure.flashblade
  • Yes
  • No
0 voters
hitachivantara.vspone_block
  • Yes
  • No
0 voters
hitachivantara.vspone_object
  • Yes
  • No
0 voters
ibm.storage_virtualize
  • Yes
  • No
0 voters
infinidat.infinibox
  • Yes
  • No
0 voters
netapp.ontap
  • Yes
  • No
0 voters
netapp.storagegrid
  • Yes
  • No
0 voters
netapp_eseries.santricity
  • Yes
  • No
0 voters

Vendor-specific server and hardware management (2)

kaytus.ksmanage
  • Yes
  • No
0 voters
wti.remote
  • Yes
  • No
0 voters

Cloud providers (6)

openstack.cloud
  • Yes
  • No
0 voters
cloudscale_ch.cloud
  • Yes
  • No
0 voters
community.hrobot
  • Yes
  • No
0 voters
hetzner.hcloud
  • Yes
  • No
0 voters
ngine_io.cloudstack
  • Yes
  • No
0 voters
vultr.cloud
  • Yes
  • No
0 voters

Vendor-specific virtualization and compute (8)

community.vmware
  • Yes
  • No
0 voters
community.okd
  • Yes
  • No
0 voters
community.proxmox
  • Yes
  • No
0 voters
kubevirt.core
  • Yes
  • No
0 voters
ovirt.ovirt
  • Yes
  • No
0 voters
vmware.vmware
  • Yes
  • No
0 voters
vmware.vmware_rest
  • Yes
  • No
0 voters

Databases (7)

ansible.mariadb
  • Yes
  • No
0 voters
ansible.mysql
  • Yes
  • No
0 voters
community.clickhouse
  • Yes
  • No
0 voters
community.mongodb
  • Yes
  • No
0 voters
community.postgresql
  • Yes
  • No
0 voters
lowlydba.sqlserver
  • Yes
  • No
0 voters
ravendb.ravendb
  • Yes
  • No
0 voters

Middleware and proxies (2)

community.proxysql
  • Yes
  • No
0 voters
community.rabbitmq
  • Yes
  • No
0 voters

Monitoring and SIEM (3)

community.zabbix
  • Yes
  • No
0 voters
splunk.es
  • Yes
  • No
0 voters
telekom_mms.icinga_director
  • Yes
  • No
0 voters

DevOps tools (3)

community.grafana
  • Yes
  • No
0 voters
community.hashi_vault
  • Yes
  • No
0 voters
grafana.grafana
  • Yes
  • No
0 voters

Vendor-specific directory services (1)

microsoft.ad
  • Yes
  • No
0 voters

Other domain-specific tools and platforms (8)

chocolatey.chocolatey
  • Yes
  • No
0 voters
community.sap_libs
  • Yes
  • No
0 voters
community.sops
  • Yes
  • No
0 voters
graphiant.naas
  • Yes
  • No
0 voters
infoblox.nios_modules
  • Yes
  • No
0 voters
microsoft.iis
  • Yes
  • No
0 voters
netbox.netbox
  • Yes
  • No
0 voters
pcg.alpaca_operator
  • Yes
  • No
0 voters
theforeman.foreman
  • Yes
  • No
0 voters

I voted no on storage related collections because they all seem vendor specific. But I also feel like some storage related stuff would be a good addition so I’m a bit conflicted.

Hopefully someone with more familiarity can express an opinion on any of them.

1 Like

community.hashi_vault should be under vendor-specific secrets management I think, not “devops” tools

1 Like

I think it can be seen as both. Also community.sops should likely be in the same categories. (SOPS is similar to Ansible Vault in that you can use it to encrypt secrets in your repository.)

1 Like

@briantist @felixfontein thanks for pointing this out! I mentioned your comments in the topic description

1 Like

IIRC if we include community.general won’t that automatically mean we need community.library_inventory_filtering_v1 as it’s a collection dependency for community.general.

3 Likes

I went through the list and voted for most of the collections (for some I’m unsure). Generally I voted for keeping a collection if it is not too niche and manages something which is open source and doesn’t require paying some vendor (by money or data) to use it. While I’m not sure whether it’s a good idea to select collections only based on that, I think it’s a general guideline that should play an important role in the decision.

3 Likes

I think that, if the purpose of the ACP is to give users something to start with, that’s a very small set of tools. If they are moving from that newbie level to something more serious, the very first thing they need to handle is ansible-galaxy install. Therefore, I voted no for almost everything. My old and beaten up 2 cents.

3 Likes

Joined to make this point but glad you have, for the vast majority of these things, I voted based on ‘if I were getting to know ansible from scratch again, coming from my floss tools first background, what do I need to successfully run a homelab or set up some management over some cloud boxes and rental VPSes, day 1, before I figured out what ansible-galaxy is or how to make a docker runner / ephemeral execution environment.’.

We know that ansible-core is for ‘the devs’ and ansible needs to be ‘enough to start with’, but I tried to leave in packages that will just be assumed to be necessary for broad uses cases (back in the day it was everybody has to install paramiko for windows etc. etc.)

5 Likes

I agree with @russoz. Me specifically, I work mostly with the Check Point collections. When I first started, the immediate thing I noticed was that the ACP package was already outdated and I still had to do ansible-galaxy install. My first thought back then was “well that was a waste of effort for the ACP folks…”.

Later, I did work with the Azure, then VMware, collections and again had the same issue and thoughts (plus, “huh? There are TWO VMware collections!?”). So yeah, vendors should do their own work if they’re gonna be serious about it.

I don’t mean to be specifically “vendor-shaming”, but… well, maybe just a wee bit.

Thank you, Steering Committee, for making this poll available!

3 Likes

Apropos of nothing, comunity.grafana and community.hashi_vault are on my list of possibly unmaintained collections in ACP 15.0.0. Looks like there haven’t been new releases since last year, at least as far as I can see…

1 Like

@mariolenz thanks for the info! Let’s start the usual removal process - they’ll go faster that way:)

I’ve just closed the polls - thank you all very much for spending some time on voting and discussing the stuff! I’ll move the not-overwhelmingly-no collections to the “keep list” in the PR