We got the pipeline change out for both of these today (and there green) I’ll get the release out.
Technically there no customer face code changes in there release. They just update the mock, and unitest.py to match the one in ansible.
OK i have the release for Netapp.cloudmanager 21.24.0 and netapp.storagegrid 21.13.0 pushed to galaxy and github.
2 Likes
Thanks! The netapp.storagegrid repository looks a lot better by now!
One small note: according to meta/runtime.yml you support ansible-core >= 2.14, but you only test against ansible-core >= 2.16. That’s something you probably want to adjust.
Another note: GHA has several warnings about outdated actions (see for example Sync bitbucket and GitHub · ansible-collections/netapp.storagegrid@6b3f53d · GitHub); these are likely due to actions/checkout@v2 and actions/setup-python@v2, of which there are newer versions.
And another: the name of the test is “Sanity”, but they run sanity tests and unit tests. These are all small points that don’t need to be changed right now, but it’s probably a good idea to look at them somewhen soon 
Ok, let’s vote on whether to cancel the deprecation/removal of netapp.storagegrid from Ansible 11 according to our process. The vote ends on Tuesday, November 5th in the early morning in Europe (to allow updating ansible-build-data before the Ansible 11.0.0b1 freature freeze release on Tuesday).
Should we cancel the removal of netapp.storagegrid from Ansible 11, now that maintenance is active again? (Steering Committee vote.)
- Cancel deprecation and keep netapp.storagegrid in Ansible 11
- Remove netapp.storagegrid from Ansible 11 as planned
0
voters
Should we cancel the removal of netapp.storagegrid from Ansible 11, now that maintenance is active again? (Community vote.)
- Cancel deprecation and keep netapp.storagegrid in Ansible 11
- Remove netapp.storagegrid from Ansible 11 as planned
0
voters
Dear @SteeringCommittee, please check out the above poll. Since Ansible 11’s feature freeze is on next Tuesday, the deadline for this vote is rather tight. Please take a look at this latest on Monday 
@SteeringCommittee Not much time left, please vote!
I will abstain from this one: as I expressed many times I think we should remove as many packages as we could from the Ansible package. However, it would not be fair to vote against a move that followed all the advertised rules. So, I will sit this one out not to betray our users’ trust, nor my convictions.
I’ve closed the vote, thanks everyone. Unfortunately the vote did not reach quorum (there are 13 members, so 7 SC votes would have been required), and thus the removal of netapp.storagegrid from Ansible 11 will not be cancelled. @carchi8py I’m sorry, looks like the timing was too tight 
Usually votes go for at least a week, but that would have missed feature freeze for Ansible 11.
Ok i can start the process then for here (GitHub - ansible-collections/ansible-inclusion: Requests to include new collections into the ansible package) to get it added in Ansible 12 then correct.
My interpretation of the process was wrong, sorry for that. A missed quorum results in readding the collection, not in not cancelling the removal. We discussed this at today’s community meeting; we definitely have to improve the formulation of the process (it’s not that simple to understand) and clarify some aspects (like how we get the clear reason if a majority says no). We decided to make another beta release (11.0.0b2) with the collection re-added today.
Sorry for my screw-up!
1 Like
Hey everyone,
I saw that the vote on the netapp.storagegrid collection ended recently. It’s unfortunate to see this becoming unmaintained, as it was a valuable resource for managing NetApp StorageGRID integrations. Does anyone know if there are plans for alternative support or if a community-driven fork is being considered?
If anyone has insights or recommendations for similar collections/tools, I’d love to hear about them. Thanks!
@anoboy712 it not unmaitained and as Felix mentioned above it was readded back.
On the NetApp side we did move the teams around recently. Because each team had worked on their own ansible collection. We recently moved the CloudManager, StorageGrid and ONTAP ansible collection under one team. So that support and cadance is more uniform.
We have the first release under the new team for StorageGrid coming either in Dec or Jan.
1 Like