repo: community.proxmox

[krauthosting]

SUMMARY

As spoken at CfgMgmtCamp'24 let's group around the current Proxmox modules.
Beside modules from community.general we want to contribute more modules.
Some out-of-tree on GitHub but also an active development of a connection plugin.
Users are also very interested in roles to interact with Proxmox as VMware alternative.
Goal is an collection alternative to community.vmware with community.proxmox 😃

Name of collection

community.proxmox

GitHub maintainers

https://github.com/krauthosting
https://github.com/Thulium-Drake
https://github.com/johanvdw
https://github.com/UnderGreen
https://github.com/jilijamt
https://github.com/UnderGreen
https://github.com/helldorado
https://github.com/castorsky
https://github.com/Kogelvis
https://github.com/jwbernin
https://github.com/l00ptr
https://github.com/paginabianca

[Andersson007]

@krauthosting hello, thanks for requesting the repo, we'll handle the request ASAP

[Andersson007]

the repo has been created and the folks listed were added as maintainers (please let them know to check their mailboxes for the invite)

• they all have the maintainer permission level, i.e. they can merge stuff. If you need any adjustments, please let me know
• https://github.com/jilijamt shows 404

[Andersson007]

@krauthosting @Thulium-Drake @johanvdw @UnderGreen @helldorado @castorsky @Kogelvis @jwbernin @l00ptr @paginabianca

Could you please:

• Consider requesting a forum tag and a group and actively using it instead of GH discussion, etc. Then please refer to it from the collection's README.
• Subscribe to the news-for-maintainers repo and track announcements there. The ansible-core folks publish changes related to CI (and not only). So if you later set up testing, you'll be informed in advance about the changes. Otherwise, your CI will get red one day in PRs for unclear reasons.
• Also some announcements can be made via Forum, so all maintainers should join the collection maintainers group.
• Optionally but highly recommended, subscribe to Bullhorn.
• We have the Maintainer guidelines. Might be useful to take a look.
• If one day you want to see the collection to the ansible community package, I would recommend to take a look at the Collection checklist (it's a short version of the Collection requirements). Taking it in consideration at the development stage will potentially make the inclusion process easier for maintainers and reviewers.
• Share the above with future maintainers.
• Also the repo will be added to Zuul: when Zuul will see a tag, it'll automatically publish the release on Galaxy.

I'll close the issue. If there are any questions, feel free to ask here or on Matrix (andersson007_) or here.
Thanks!

PS thanks for the effort to move the stuff from community.general and the desire to maintain and develop it!

[krauthosting]

@Andersson007 Thanks 😚 Put could you empty the repo from the initial commit?
We're aiming to use "git filter-repo" to keep the history on all Proxmox modules.
@felixfontein guessed it would be a blank repo and no ugly force push needed.

Will need a bit time till we initialize the repo with history of community.general.
Next commit will add then README & co, before we start merging actual PRs.
Are scheduling internal work time for all that from the 19-23th of February on.

@felixfontein Thanks for sorting out and mentioning all on those pending work:
ansible-collections/community.general#4027
ansible-collections/community.general#6872
ansible-collections/community.general#7728

Could somebody still take care if we need to merge them before splitting repos?
Or we just merge current PRs as is, move the issue to stabilize till next release?
Our primary goal would to have a clean git while ramping up regular work time.

[felixfontein]

Put could you empty the repo from the initial commit?

In case the branch protections aren't active yet, you can simply force push over the current repo contents to get rid of them :) I would only enable branch protections once the basic repo setup is done.

BTW, if someone can give me moderator or even commit rights (not sure what's really needed) for the repo, I can move issues over from community.general. (To move issues between repos in one organization one needs appropriate access rights in both repos.)

Could somebody still take care if we need to merge them before splitting repos?

It's easier to handle them before splitting, but you can always cherry-pick the commits over after the split. It's a bit more work, but doable :)

@krauthosting what do you think if I add you to the maintainer list for the proxmox stuff in c.g? Then you'll get pinged for every issue and PR that involves the proxmox modules (both existing, and new ones once they are created). Then you can directly interact with folks who created issues/PRs in the wrong repo (which will probably happen for some time, or even years, speaking from experience :) ) - at least as long as the modules/plugins are still in c.g's main branch.

[Andersson007]

@felixfontein @krauthosting i've just disabled Require linear history so you can purge the repo (not sure if's that setting though). There are no other rules enabled for main.
@felixfontein i made you a maintainer too
Folks please let me know when i can enable Require linear history again.
thanks!

[felixfontein]

@Andersson007 there are still branch protections for the main branch which prevent force pushes:

remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: error: Cannot force-push to this branch

In branch protections, there's a box at the bottom "Rules applied to everyone including administrators" where you can enable force pushes. But I guess it's easiest to simply delete the branch protection for main completely for now.

Another problem is that there's now the tag "generated from https://github.com/ansible-collections/collection_template", which really shouldn't be there. The only way to get rid of it seems to be by deleting the repository.

@krauthosting another thing I remembered you have to take care of when using git filter-repo: the modules directory of c.g was reorganized in http://github.com/ansible-collections/community.general/commit/b531ecdc9bfe48fe98ea6b67279eb048e0c9071d:

plugins/modules/{cloud/misc => }/proxmox.py       
plugins/modules/{cloud/misc => }/proxmox_disk.py  
.../{cloud/misc => }/proxmox_domain_info.py       
.../modules/{cloud/misc => }/proxmox_group_info.py
plugins/modules/{cloud/misc => }/proxmox_kvm.py   
plugins/modules/{cloud/misc => }/proxmox_nic.py   
plugins/modules/{cloud/misc => }/proxmox_snap.py  
.../{cloud/misc => }/proxmox_storage_info.py      
.../modules/{cloud/misc => }/proxmox_tasks_info.py
.../modules/{cloud/misc => }/proxmox_template.py  
.../modules/{cloud/misc => }/proxmox_user_info.py 
.../modules/{cloud/misc => }/test_proxmox_kvm.py  
.../modules/{cloud/misc => }/test_proxmox_snap.py 
.../{cloud/misc => }/test_proxmox_tasks_info.py   

[Andersson007]

@felixfontein

• deleted the rule; please let me know when i can add it again
• i wouldn't like to remove the repo if it's not super necessary.. it's added to Zuul already (who knows maybe it'll brake something) and all the folks were added and they got subscribed. Though, If necessary, I'll remove and will create from scratch.

[krauthosting]

@felixfontein Thanks for taking care and sure add us to the maintainer list for the Proxmox. As said in Ghent we will try to schedule regular work time, so at least initially it might help to redirect PRs & co. Brilliant idea, thanks for taking care! Also for mentioning the renaming for git filter-repo ❤️ We scheduled to look at it next week ...

@Andersson007 Also big thanks for helping 🥇 Should have stated our goals better before the repo creation knowing "best practice" in Ansible was to dump git history. Not huge fans of Microsoft's closed-source AI training 'Hub we just care git itself is clean. But will just git push --force if too cumbersome to mess with the project as is ... like in godmode 🤣