18:00:03 <felixfontein> #startmeeting Ansible Community Meeting
18:00:03 <zodbot> Meeting started Wed May 18 18:00:03 2022 UTC.
18:00:03 <zodbot> This meeting is logged and archived in a public location.
18:00:03 <zodbot> The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <zodbot> The meeting name has been set to 'ansible_community_meeting'
18:00:03 <felixfontein> #topic Agenda https://github.com/ansible/community/issues/645
18:00:03 <felixfontein> acozine andersson007_ baptistemm bcoca briantist cyberpear cybette dericcrago dmsimard felixfontein geerlingguy gundalow gwmngilfen ikhan_ jillr jtanner lmodemal misc nitzmahone resmo samccann tadeboro cidrblock thaumos zbr: ping!
18:00:07 <felixfontein> #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics
18:00:08 <dmsimard> o/
18:00:10 <felixfontein> #topic Updates
18:00:24 <felixfontein> #chair dmsimard gundalow
18:00:24 <zodbot> Current chairs: dmsimard felixfontein gundalow
18:00:26 <dmsimard> #info ansible 6.0.0a3 (including ansible-core 2.13.0) is now available for testing: https://groups.google.com/g/ansible-announce/c/x51luOaarOk
18:00:38 <dmsimard> #info ansible 5.8.0 has been released: https://groups.google.com/g/ansible-announce/c/pT_VuSf9uS4
18:00:51 <briantist> o/
18:01:03 <felixfontein> #chair briantist
18:01:03 <zodbot> Current chairs: briantist dmsimard felixfontein gundalow
18:01:17 <briantist> double plus booked so might be flighty 🕊
18:01:39 <hunleyd[m]> #info community.postgresql is seeking feedback on supported PG versions: https://github.com/ansible-collections/community.postgresql/issues/276
18:01:46 <samccann> 0/
18:01:49 <orandon[m]> o/
18:01:51 <cyberpear> o/
18:01:54 <felixfontein> #chair samccann orandon[m] cyberpear
18:01:54 <zodbot> Current chairs: briantist cyberpear dmsimard felixfontein gundalow orandon[m] samccann
18:02:30 <dmsimard> #info Ansiblefest 2022 announced in Chicago, October 19th & 20th and CFP is open: https://www.ansible.com/ansiblefest
18:02:53 <felixfontein> #info Active vote until Friday: history visibility in chat (https://github.com/ansible-community/community-topics/issues/43)
18:03:05 <dmsimard> ^ There will be a contributor summit attached to ansiblefest but we are still working out the details
18:03:15 <felixfontein> #info Active vote until Monday: adopt process for renaming collections included in Ansible (https://github.com/ansible-community/community-topics/issues/102)
18:03:34 <felixfontein> dmsimard: great news! (though I won't attend in person :) )
18:04:01 <dmsimard> It will be in hybrid format with virtual attendance so people who don't/can't travel can participate
18:05:02 <gundalow> #info Contributors Summit will be in-person & online on 18th October
18:05:26 <dmsimard> oh, thanks gundalow :)
18:07:53 <felixfontein> #info ansible-test sanity now has a Python 3.11 import test
18:08:00 <felixfontein> #undo
18:08:00 <zodbot> Removing item from minutes: INFO by felixfontein at 18:07:53 : ansible-test sanity now has a Python 3.11 import test
18:08:03 <felixfontein> #info ansible-test sanity (devel branch) now has a Python 3.11 import test
18:09:27 <mariolenz[m]> Any mor ideas about having a [machine-readable maintainers file in collections](https://github.com/ansible-community/community-topics/issues/100)? I still fell that `galaxy.yml` would be the "natural" place to define this...
18:10:05 <mariolenz[m]> s/mor/morr/, s/fell/feel/
18:10:09 <gundalow> Don Naro: Would you like to introduce yourself, if you start it with `#info` It will end up in the summary
18:10:45 <felixfontein> galaxy.yml would indeed be the natural place, but getting that in there is probably quite some effort
18:10:49 <mattclay> felixfontein: It also has some support for multi-arch containers now (base, default, distro containers), with more coming.
18:10:53 <mariolenz[m]> s/mor/more/, s/fell/feel/
18:11:14 <gundalow> bcoca: Do you know if we can add things to a collection's `galaxy.yml`, or is that spec locked down to ansible-core releases?
18:11:38 <orandon[m]> thanks gundalow ! yes. I was just trying to figure out what to say. I'm probably not the best at intros.
18:11:51 <felixfontein> mattclay: ah, nice. though I guess that requires to have such an architecture in CI :)
18:12:34 <mattclay> felixfontein: Or be running an aarch64 system locally.
18:13:01 <mattclay> Anyone running a native Linux VM on Apple Silicon for example.
18:13:28 <mattclay> felixfontein: Also, we have aarch64 instances in CI now (RHEL, Ubuntu, FreeBSD).
18:14:08 <felixfontein> #info cisco.dnac will be included in Ansible if nobody objects; deadline for objections is May 19th (https://github.com/ansible-community/community-topics/issues/101)
18:14:34 <bcoca> gundalow: core and galaxy_ng need to coordinate on that
18:14:36 <orandon[m]> #info Hey everyone, I think I've met some of you already but I'm still pretty new so would like to give myself a brief intro. I'm going to be helping out with Ansible docs and contributing to the community. I have been working with the Infinispan community for the past 4+ years and working with them on everything from the community site to docs to the React.JS console. I'm big on the "community first" approach and am really
18:14:36 <orandon[m]> excited to be here and look forward to working with you all and building great things. Thank you.
18:14:51 <felixfontein> welcome orandon[m]!
18:15:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:15:27 <gundalow> Great to have you here
18:17:00 <dmsimard> Maybe a last update from me, hang on
18:17:50 <dmsimard> #info We're down from 59 to 51 collections with failing sanity tests as of ansible 6.0.0a3, more details in the issue: https://github.com/ansible-community/community-topics/issues/96
18:18:14 <dmsimard> I have to head out, will catch up later
18:18:19 <gundalow> That's solid progress
18:18:23 <gundalow> thanks dmsimard
18:20:59 <felixfontein> btw, I just noticed we still can't build an EE for Ansible 5.8.0 since collections have conflicting Python dependencies...
18:21:07 <felixfontein> for example:  - 'azure-mgmt-resource==10.2.0,>=16.1.0  # from collection azure.azcollection,netapp.cloudmanager'
18:22:14 <felixfontein> it's also not helpful that there are quite a few collections that specify their Python requirements with `==` instead of specifying ranges. that's pretty much waiting for a disaster
18:22:32 <mariolenz[m]> <felixfontein> "galaxy.yml would indeed be the..." <- I'd prefer to have some effort and do it right over just implementing a work-around. I've been working long enough in IT to know that work-arounds will get you into trouble sooner or later.
18:22:58 <bcoca> felixfontein:  why we gave up on a 'kitchen sync' EE
18:23:08 <felixfontein> maybe it's just unrealistic to expect to build a EE from Ansible...
18:23:20 <felixfontein> bcoca: I can fully understand :)
18:24:25 <felixfontein> anyway, at least now `ansible-galaxy collection install` can install the collections from Ansible 5.8.0 since there's no longer a dependency mismatch...
18:24:47 <bcoca> woot
18:25:58 <felixfontein> one could argue that it should have always worked, but unfortunately it didn't :)
18:26:14 <gundalow> felixfontein: Do you know which have `==`, I can feed that back to Partner Engineering, and we can see if they can update that
18:26:39 <felixfontein> gundalow: https://github.com/ansible-collections/azure/blob/dev/requirements-azure.txt for example
18:27:07 <felixfontein> gundalow: basically you can look in the output of https://github.com/ansible-community/images/runs/6493876894?check_suite_focus=true - it shows all combined Python dependencies
18:27:21 <gundalow> felixfontein: Brilliant, thank you
18:27:31 <felixfontein> apparently the order in the comment seems to be the order of the requirements on the left side
18:29:16 <felixfontein> I'm wondering whether it's better to have users just build their own EEs with the collections they need... that will probably increase the chance that it works. on the other hand, if we can get collections to loosen their dependencies that will also make user's life easier, since it decreases the chance that non-trivial EEs fail building
18:29:35 <felixfontein> one thing I still want to try is building an EE based on Debian or Arch
18:29:46 <felixfontein> just never got around to do that :)
18:30:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:36:47 <gundalow> Would be good to get an understand of the interest/demand for this
18:37:10 <gundalow> I'm OK smaller/incremental process
18:37:37 <gundalow> We can move to the next topic if folks don't have any more comments on this one
18:38:42 <jtanner> hi
18:39:26 <gundalow> #chair jtanner
18:39:26 <zodbot> Current chairs: briantist cyberpear dmsimard felixfontein gundalow jtanner orandon[m] samccann
18:39:46 <gundalow> jtanner: Afternoon, anything you'd like to share?
18:39:52 <jtanner> nope
18:41:28 <jtanner> i presume the '==' in most requirement files comes from a pip freeze or similar
18:41:47 <briantist> sorry, I totally got pulled away
18:41:59 <jtanner> authors probably won't know a range of versions that would work unless they build a test matrix
18:42:11 <briantist> contributor summit in October is going to be in person? that's exciting, any more info on that? location, etc.?
18:42:13 <gundalow> jtanner: could well be. I think I remember reading that azure dependencies were very particular
18:42:45 <jtanner> pretty sure i remember hearing the same
18:42:56 <gundalow> briantist: Chicago, Illinois.
18:43:03 <gundalow> https://www.ansible.com/ansiblefest
18:43:03 <jtanner> probably due to the generative nature of their client libs?
18:43:10 <briantist> thx!
18:45:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:49:27 <mariolenz[m]> <felixfontein> "galaxy.yml would indeed be the..." <- At least, we should give it a try. Should I open a feature request in [ansible-core](https://github.com/ansible/ansible) for this? Or somewhere else?
18:52:07 <felixfontein> jtanner: do you know how much the galaxy.yml / MANIFEST.json format is fixed / can be extended? ^
18:52:47 <jtanner> the resulting MANIFEST.json created from galaxy.yml is controlled by core
18:52:58 <jtanner> the validation of MANIFEST.json is handled by galaxy-importer, iirc
18:55:53 <jtanner> https://github.com/ansible/galaxy-importer/blob/master/galaxy_importer/schema.py
18:56:30 <felixfontein> i.e. when something is added to galaxy.yml, it also needs to be handled by galaxy-importer, I guess?
18:57:09 <jtanner> +galaxy_importer, +pulp_ansible https://github.com/pulp/pulp_ansible/blob/main/pulp_ansible/app/models.py#L94
18:57:18 <jtanner> i -think-
18:59:13 <felixfontein> mariolenz[m]: ^
18:59:19 <felixfontein> jtanner: thanks!
19:00:51 <jtanner> https://github.com/pulp/pulp_ansible/blob/main/pulp_ansible/app/serializers.py#L437 the serializer returns the whole json blob afaict, so maybe that doesn't need updating
19:01:35 <jtanner> FYI, i'm answering to galaxy_ng .. i have no clue for "galaxy"
19:04:07 <felixfontein> :)
19:04:22 <felixfontein> it uses galaxy_importer as well, so maybe that already solves it
19:06:52 <felixfontein> but yeah... it's easier to add a new file :)
19:06:57 <felixfontein> ok, time's up....
19:07:07 <felixfontein> thanks everyone for the discussion (even though there wasn't much today)
19:07:10 <felixfontein> #endmeeting