community.grafana
community.grafana copied to clipboard
ansible-collections
Grafana Pinboard
We could collectively benefit from forming a Working Group related to Grafana integration. We have quite some contributors on GitHub and users on IRC that are interested in improving this integration.
So this issue is a call for potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
- test, review and add shipits to existing Grafana PRs
- work collectively on the Grafana roadmap
- provide a single-point-of-contact for interested Grafana contributors
- collaborate on an Grafana Wiki
- have a $team_grafana in BOTMETA.yml for auto-notifying team members
- implement auto-labeling grafana issues and PRs
@seuf @rrey Feel free to use this issue for communication and https://github.com/ansible/community/wiki/Grafana for documentation.
Please give me a shout if there is anything else. I wonder if reviewing the existing PRs would be a good place to start
Bot meta update https://github.com/ansible/ansible/pull/63859
Means you can do shipit on any PR.
Any problems or questions please shout out. #ansible-devel on Freenode is the best place
Hi,
Could you please git mv the existing grafana modules to monitoring/grafana/ see https://github.com/ansible/ansible/pull/64497/files for an example.
I didn't want to do by myself now as there seem to be a number of open Grafana PRs https://ansible.sivel.net/pr/byfile.html (ctrl+f grafana). Once the new directory has been created the new module PRs will need rebasing and adding into the new directory.
Thanks
@gundalow I made the PR here : https://github.com/ansible/ansible/pull/64657
I think it can be merged after https://github.com/ansible/ansible/pull/50816. I will deal with the contributors on the other open PRs.
@gundalow have no answer from author on ansible/ansible#50816 so I think we the ansible/ansible#64657 can be merged whenever you want. I have just rebased it, do you need any thing else on this PR ?
What are the next steps for working groups about the move to collections ?
@rrey Looks like the above got merged, which is great.
For the Grafana Working group the question is:
Would you want your own repo, or be in the general Community Collection repo?
Being in your own repo gives you some more control, and freedom to do a release of the Grafana collection independently of the main Community Collection.
I am looking for some willing Working Groups to test this out. Basically we'd freeze ansible/ansible and just do the work in the new collection repo.
I'm happy to jump on a call and discuss any of this if that may be easier.
Hi !
I think it makes more sense to have a lifecycle for each working group. I would go for a dedicated repo ! So you found a working group to test this out as far as I'm concerned !
@rrey @seuf Hi, I've created https://github.com/gundalow-collections/grafana which is a copy of what's currently in ansible/ansible:devel. It has basic CI (Python 3.6 on Ubuntu 1804). I've invited you both to the org, you should receive an email from GitHub to accept joining the team.
I wonder if one of the PRs from https://github.com/ansible/ansible/labels/grafana could be reworked for the new repo, perhaps https://github.com/ansible/ansible/pull/62930 or https://github.com/ansible/ansible/pull/64097 ?
Thanks ! I think I can move ansible/ansible#62930 quickly on the collection repo. I'll start there.
@gundalow what should we do for our modules maintenance ?
Should we use the gundalow-collections/grafana to push all the new fixes and content ?
Should we keep on fixing modules on ansible/ansible ?
@rrey @seuf I think we can ignore Grafana files in ansible/ansible for the moment.
I've just your closed the two PRs (one from each of you) that have been replicated in ansible-collections/grafana
-
Should I move
gundalow-collections/grafanatoansible-collections/grafananow, we can continue to prototype GitHub workflow there. I think this should be done before we ask anyone else to contribute to make it look more official (rather than in my personal GH Org) -
Do you think we are ready to ask https://github.com/ansible/ansible/pulls?q=label%3Agrafana+is%3Aopen+is%3Apr to re-create their PRs in the new repo?
-
Let's go !!
-
Only #55651 is directly related to grafana. I think we can ask the author once the new repo is ready.
-
Done https://github.com/ansible-collections/grafana You should both receive emails that invite you to be members of the new repo.
-
I've put a comment on https://github.com/ansible/ansible/pull/55651 lets see how that works out.
I'm going to try to migrate this pinboard to https://github.com/ansible-collections/community.grafana but there may be a slight disruption as it requires multiple moves. I will follow up when the migration has been completed.
I'm happy to announce that the registration (free) for the Ansible Contributor Summit is open.
Which day should you attend?
- If you are wondering what it means to "contribute" to Ansible, or if you have been using Ansible for a while and are thinking of ways to get more involved with the project and community, then Day 1 (September 28, Tuesday) is for you!
- If you have already been contributing or participating in our previous Contributor Summits, you are still welcome to attend Day 1, however we think that Day 2 (October 1, Friday) will be more interesting for you.
Refer to the registration page for details.
See you at the summit!
Reminder - AnsibleFest and Ansible Contributor Summit are 1 week away!
In case you missed it, we will also be having a Hackathon throughout the entire Ansible Contributor Summit and AnsibleFest. This is a great opportunity to collaborate in real time with other members of the Ansible Community!
For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD.
Reminder - Day 1 of the Ansible Contributor Summit and the Hackathon start tomorrow (Tuesday, 28 September 2021)!
For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD.