Skip to content

Instantly share code, notes, and snippets.

@cybette
Created March 12, 2021 01:31
Show Gist options
  • Save cybette/e18269214cf70f83f4bbba08e7d71307 to your computer and use it in GitHub Desktop.
Save cybette/e18269214cf70f83f4bbba08e7d71307 to your computer and use it in GitHub Desktop.
Chat log from Ansible Contributor Summit, March 9, 2021
Ansible Contributor Summit 2021.03 (2021-03-09 at 04:01 GMT-8)
00:00:02.842,00:00:05.842
Baptiste Mille-Mathias: I'm just lurking around
00:00:11.194,00:00:14.194
Felix Fontein: Hi Baptiste!
00:00:30.888,00:00:33.888
Baptiste Mille-Mathias: can't speak today
00:01:53.592,00:01:56.592
Mark Chappell: Q&A is hidden under the icon on the right that's a triangle over a square and circle
00:02:55.268,00:02:58.268
Carol Chen: Agenda: https://hackmd.io/@ansible-community/contrib-summit-202103
00:03:24.130,00:03:27.130
Ton Kersten: I will only be listening in today. Still hard at work
00:03:37.469,00:03:40.469
Brian Coca: greetings (non tz specific)
00:05:45.869,00:05:48.869
James Cammarata: hehe jiminy... haven't heard that one in a while
00:07:33.159,00:07:36.159
James Cammarata: chipmunk coca
00:07:41.947,00:07:44.947
Baptiste Mille-Mathias: Daft punk is back
00:07:47.860,00:07:50.860
James Cammarata: this is a long standing issue with bcoca's mic...
00:08:24.537,00:08:27.537
James Cammarata: poor west coast people...
00:10:13.420,00:10:16.420
Brad Thornton: "best" coast, is what we call it...
00:11:04.674,00:11:07.674
James Cammarata: i'm in the middle, no dog in that fight :)
00:12:37.928,00:12:40.928
Brian Coca: best mountain range is where i have opinions, since i hate beaches
00:14:01.980,00:14:04.980
David Moreau Simard: cybette-clock says 5 minutes left for this topic :)
00:14:50.552,00:14:53.552
Brian Coca: @tim good hostage video
00:15:40.201,00:15:43.201
Gundalow Barker: I know there are a lot of other people here that we will not get a chance to introduce themselves.
If you to say your 1) GitHub/IRC name. 2) Your interest in Ansible 3) Where in the world you are 4) What you are hoping to get from today
00:19:02.667,00:19:05.667
Carol Chen: haha thanks David :)
00:19:48.554,00:19:51.554
Ton Kersten: - Ton Kersten / Netherlands (UTC+1) / GH: tonk / IRC: tkersten / Ansible user+contributor since 2012/ Meetup organizer / Learn about the future of Ansible
00:20:06.916,00:20:09.916
Carol Chen: hi Ton! :wave:
00:20:27.237,00:20:30.237
Abhijeet Kasurde: hi Ton! Welcome
00:20:45.121,00:20:48.121
Ton Kersten: Hello all. I'm just listening in. Still at work
00:21:43.205,00:21:46.205
Jacob Evans: 1) @JacobPEvans
2) Huge fan of Splunk, I've been using Ansible to automate a full cloud-based Splunk deployment. I see a lot of value in Ansible elsewhere though (e.g. server hardening)
3) Balkans / East Europe
4) Just watching, we'll see what happens! Always curious to know the latest & greatest
00:21:43.495,00:21:46.495
Timothy Appnel: @bcoca Sun hasn't quite come up here. Trying not to wake up the rest of the house.
00:22:13.367,00:22:16.367
Abhijeet Kasurde: hi Jacob
00:22:27.672,00:22:30.672
Carol Chen: hello Jacob!
00:23:38.626,00:23:41.626
Ton Kersten: Hi Carol and all the RH Ansibulls
00:24:10.729,00:24:13.729
Carol Chen: @Ton we just received new ansibulls and I'll be sending some your way!
00:25:56.726,00:25:59.726
Gagan Deep: Hi everyone!
I am Gagan Deep from India. I go by username "pandafy" on GitHub and IRC.
I across Ansible while working on OpenWISP. Currently, I am not a contributor yet :(, but I am looking forward to it.
Pronouns: He/him/his
00:26:13.844,00:26:16.844
Ton Kersten: @Carol: Wonderful, looking forward to it
00:26:14.671,00:26:17.671
Carol Chen: hi Gagan! welcome :)
00:26:35.517,00:26:38.517
Sagi Shnaidman: Is this presentation available in public?
00:26:38.341,00:26:41.341
Carol Chen: Agenda for those who just joined: https://hackmd.io/@ansible-community/contrib-summit-202103
00:26:45.785,00:26:48.785
Carol Chen: Sagi: we'll share slides after the event
00:27:01.328,00:27:04.328
Sagi Shnaidman: cool
00:29:25.175,00:29:28.175
Carol Chen: in the meantime you can check out details in this HackMD: https://hackmd.io/nAHJNmBbSYm90KZM1RPK6w
00:32:32.722,00:32:35.722
Gundalow Barker: Hi Resmo :)
00:33:06.561,00:33:09.561
Daniel S: sorry, was just listening during the last 30 minutes. still at work and need to "background" you every now and then. :)
Therefore: Hi all, nice to see you.
00:33:16.929,00:33:19.929
Carol Chen: Hi Resmo! Hi Daniel!
00:37:05.036,00:37:08.036
Carol Chen: For those curious, my background is a picture from the Ansible office in Durham, which I took in 2018 when I visited
00:37:45.118,00:37:48.118
René Moser: hi Carol, looks good ;)
00:39:12.630,00:39:15.630
Abhijeet Kasurde: There is bird in the meeting
00:39:29.645,00:39:32.645
Abhijeet Kasurde: @alex ^^
00:39:48.789,00:39:51.789
Carol Chen: birdie!
00:40:11.361,00:40:14.361
Alina Buzachis: 😍
00:40:44.915,00:40:47.915
Abhijeet Kasurde: Cats and Dogs are so mainstream. We have bird in Ansible Contributor Summit.
00:45:05.924,00:45:08.924
Carol Chen: yes! we're so glad to have the birds attending the contributor summit :D
00:45:57.209,00:46:00.209
Brian Coca: we even have a badger!
00:46:21.398,00:46:24.398
Alex Sowitzki: @carol hope I do not distract :)
00:46:33.895,00:46:36.895
Alex Sowitzki: where ist the badger?
00:47:01.187,00:47:04.187
Sviatoslav Sydorenko: @Alex: "abadger" is Toshio's handle
00:47:15.648,00:47:18.648
Toshio Kuratomi: /me waves
00:47:45.150,00:47:48.150
Alex Sowitzki: ooooh! hi :)
00:48:36.008,00:48:39.008
Alex Sowitzki: @gregory: love those charts, thanks for assembling
00:53:13.698,00:53:16.698
Gundalow Barker: If you are interested in the graphs and details that gwmngilfen is currently presenting, take a look at the more detailed blogs on https://emeraldreverie.org/ which some amazing graphs and write ups
00:53:21.637,00:53:24.637
Gundalow Barker: The list of potential statistics we are interested in, and other questions we have are tracked here https://github.com/ansible-community/stats-collections/issues
00:56:22.711,00:56:25.711
Gundalow Barker: QUESTION: What thoughts and ideas do people have
00:59:17.215,00:59:20.215
Carol Chen: https://stats.eng.ansible.com/
01:03:44.046,01:03:47.046
Gundalow Barker: ============================================
01:03:45.166,01:03:48.166
Gundalow Barker: #info Blog posts on ansible recent version changes https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package & https://www.ansible.com/blog/ansible-3.0.0-qa
01:05:38.482,01:05:41.482
Gundalow Barker: Slides that dmsimard is currently presenting http://ansible.github.io/community/decks/3.0.0-community-update.html#/ (had lots of links)
01:07:38.400,01:07:41.400
Gundalow Barker: ansible and ansible-core roadmaps https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html
01:14:54.619,01:14:57.619
Gundalow Barker: Link to the Ansible Bullhorn (fortnightly email for Ansible Developers) https://us19.campaign-archive.com/home/?u=56d874e027110e35dea0e03c1&id=d6635f5420
01:16:13.909,01:16:16.909
Felix Fontein: There is a question in Q&A
01:16:41.331,01:16:44.331
Carol Chen: Reddit: https://www.reddit.com/r/ansible/
01:17:01.605,01:17:04.605
Toshio Kuratomi: major, minor, micro (patch)
01:17:22.467,01:17:25.467
Abhijeet Kasurde: OK Cool
01:20:40.582,01:20:43.582
Sorin Ionuț Sbârnea: If ansible-core release x.y.123, how long until ansible-3.x makes a new release. My guess is that: it does not have to do one as it is not pinning the core patch version.
01:21:56.078,01:21:59.078
Gundalow Barker: FYI we are keeping a summary of the discussions at the end of https://hackmd.io/uZDSLOOdS1Kx0xfZVIATmQ
The session is being recorded and will be on YouTube. There will be blog posts containing a summary of the discussions and call to actions. Subscribe to The Bullhorn to know when they are published https://us19.campaign-archive.com/home/?u=56d874e027110e35dea0e03c1&id=d6635f5420
01:24:03.275,01:24:06.275
Daniel S: Thanks to all the speaker until now :)
01:24:37.128,01:24:40.128
Carol Chen: Thanks David, and thanks to everyone for the questions and discussions!
01:26:12.295,01:26:15.295
René Moser: @Carol, you might want to pause recording ;)
01:26:51.746,01:26:54.746
Carol Chen: Rene: I will pause at the munch hour :) (Recording has to be on for the chats to be logged, I think)
01:27:28.397,01:27:31.397
Abhijeet Kasurde: I need real (in-person) contributor summits
01:27:43.285,01:27:46.285
Gundalow Barker: Mr VMware: Me too
01:28:04.112,01:28:07.112
Gundalow Barker: FYI Greg's "The year in Review" presentation is now available on http://ansible.github.io/community/decks/2021-03-contrib-summit-stats-collections-1yr-review.html
01:28:09.619,01:28:12.619
Gundalow Barker: (Open source presentations)
01:33:12.614,01:33:15.614
Carol Chen: oh yes I miss in-person events terribly
01:34:43.983,01:34:46.983
Brian Coca: i prefer virtual, does not require having a dress code
01:35:10.215,01:35:13.215
Rick Elrod: I miss traveling in general. :(
01:36:08.198,01:36:11.198
Gregory Sutcliffe: i do not miss travelling. but being in other places, yes
01:36:40.655,01:36:43.655
Timothy Appnel: +1 to travel and in-person
01:36:58.412,01:37:01.412
Daniel S: Gregory, so next project teleportation? ;)
01:37:29.403,01:37:32.403
Carol Chen: teleporting would be cool
01:37:39.549,01:37:42.549
Gundalow Barker: 1 year 3 days since I was at Ansible and Red Hat offices
01:38:01.166,01:38:04.166
David Moreau Simard: While we are still in break, I encourage people to fill in a doc about contributor and maintainer experience for a discussion later: https://hackmd.io/z0LmOzdBSQ2MkecSIf5gxw
01:38:04.571,01:38:07.571
Gregory Sutcliffe: so the fun thing about teleporting is that it requires you to condone murder to achieve it :)
01:38:42.223,01:38:45.223
Carol Chen: lol
01:38:44.844,01:38:47.844
Gregory Sutcliffe: (heisenberg uncertainty principle will require that you exist in both praces briefly, and then one of you has to be destroyed
01:38:45.839,01:38:48.839
Carol Chen: but true
01:38:53.115,01:38:56.115
Gregory Sutcliffe: *places
01:39:09.696,01:39:12.696
Gundalow Barker: =================
01:41:03.399,01:41:06.399
Gundalow Barker: QUESTION: Have people heard of Execution Enrotonments before?
01:42:22.396,01:42:25.396
Gundalow Barker: wow, nice typo there gundalow
01:42:22.597,01:42:25.597
Carol Chen: please vote in poll ^
01:42:32.687,01:42:35.687
Amin Vakil: no, a couple of months before i saw ansible-builder and found it interesting, but never found time to search and learn it
01:43:03.730,01:43:06.730
Tadej Borovšak: I had to add a bit of metadata to one of our certified Ansible collections in order to be usable with ansible-builder.
01:43:12.401,01:43:15.401
Abhijeet Kasurde: no
01:45:03.975,01:45:06.975
David Moreau Simard: To my knowledge installing collections does *not* pull in python dependencies
01:45:32.739,01:45:35.739
Gundalow Barker: correct
01:45:47.047,01:45:50.047
Tadej Borovšak: @David Moreau Simard It does in the world of EE. Collection just need to declare them.
01:46:00.397,01:46:03.397
Felix Fontein: David: ansible-builder does that, if they are specified by the collection in a format it understands
01:46:03.472,01:46:06.472
David Moreau Simard: Through that requirements.txt file, yes ?
01:46:25.857,01:46:28.857
Felix Fontein: Is there some documentation for collection maintainers what they need to do to support ansible-builder?
01:46:39.377,01:46:42.377
Tadej Borovšak: requirements.txt is the default location, but it can be anything as long as it is specified in the metadata.
01:46:53.624,01:46:56.624
David Moreau Simard: ok
01:48:34.820,01:48:37.820
Tadej Borovšak: https://ansible-builder.readthedocs.io/en/latest/collection_metadata.html
01:49:52.366,01:49:55.366
Tadej Borovšak: The docs would benefit from expansion a bit (I had to read through the ansible-builder code to fill in all the details I needed), but the basic info is there.
01:49:56.722,01:49:59.722
Abhijeet Kasurde: Sleek
01:50:10.015,01:50:13.015
Abhijeet Kasurde: Thanks Nikhil
01:50:49.930,01:50:52.930
Aytunc Beken: Is it possible to bundle all playbooks and inventory in that docker image which we build with ansible-builder ?
01:50:54.402,01:50:57.402
Felix Fontein: Thanks!
01:52:02.224,01:52:05.224
Sorin Ionuț Sbârnea: AFAIK, this means that you will not be able to run/test your local ansible code without rebuilding the container first.
01:52:59.380,01:53:02.380
Aytunc Beken: Yes, my idea is to bundle and distribute that image which has everything in it.
01:53:01.174,01:53:04.174
Mark Chappell: It's really helpful where you also need to think about some of the more complex python dependencies.
01:55:40.081,01:55:43.081
Aytunc Beken: Got it, thanks
01:55:55.094,01:55:58.094
Timothy Appnel: Right Mark. Some organizations have dozens of different virtual environments each with dependencies. Those virtual environments are not portable either so each system has to be kept in sync.
01:56:59.052,01:57:02.052
Sorin Ionuț Sbârnea: Clearly it makes distribution of a specific collection/product easy. But i am not sure how this will play if you need to combine 5-10 complex collections into a single container.
01:58:08.273,01:58:11.273
Timothy Appnel: @sorin How is it different then complex virtual environments with 5-10 complex collections and all of their dependencies?
01:58:25.273,01:58:28.273
Sorin Ionuț Sbârnea: Assuming that we have teams producing container based environments for openshift, openstack,.... I can see them happy to produce these containers. Now, what if the customer wants to combine all of them,... into a single environment.
01:58:33.214,01:58:36.214
Brian Coca: containment does not mean it eliminates complexity, just that it is 'contained'
01:58:34.461,01:58:37.461
Timothy Appnel: There are many enterprise users already wrestling that now.
01:59:18.124,01:59:21.124
Sorin Ionuț Sbârnea: i can see how someone would endup struggling to combine two or more containers into one :p
01:59:50.417,01:59:53.417
Daniel S: Nikhil, are you on Twitter/having a blog or something?
01:59:53.157,01:59:56.157
Andrius Benokraitis: @sorin - it is easier in the long-run, but harder in the short-term for other products integrating a containerized ansible
02:00:12.899,02:00:15.899
Gundalow Barker: ==============
02:00:24.410,02:00:27.410
Jesse Pretorius: if a custom dockerfile is used to layer containers then wouldn't that resolve the issue as long as they're using the same underlying python/ansible base?
02:00:47.049,02:00:50.049
Gundalow Barker: Follow along at home https://hackmd.io/z0LmOzdBSQ2MkecSIf5gxw?both
02:02:13.918,02:02:16.918
Gundalow Barker: This is an interactive topic. Please chat here , or feel free to unmute your microphone
02:02:31.261,02:02:34.261
Andrius Benokraitis: @jesse - maybe? all depends what you consider the "source" container
02:03:03.069,02:03:06.069
Brian Coca: until the containers use conflicting versions of requests lib ...
02:03:05.379,02:03:08.379
Andrius Benokraitis: if everyone is making their own base containers then there's not a lot of consistency
02:03:13.810,02:03:16.810
Nikhil Jain: Daniel, not a social media guy, but there is an existing blog for EE and builder here https://www.ansible.com/blog/introduction-to-ansible-builder
02:04:02.743,02:04:05.743
Andrius Benokraitis: https://ansible-builder.readthedocs.io/en/latest/
02:04:18.849,02:04:21.849
Gundalow Barker: QUESTION: What had caused you pain, what's been difficult, what has been difficult to understand
02:06:05.579,02:06:08.579
Timothy Appnel: IRC
02:06:25.346,02:06:28.346
Gregory Sutcliffe: matrix++
02:06:52.888,02:06:55.888
René Moser: CI/CD
02:07:42.328,02:07:45.328
Sorin Ionuț Sbârnea: the path requirement was big PITA for development and required a lot of plumbing being added to molecule, ansiblel-lint and tox-ansible tools, just to bring the tested code into a form that is recognized by ansible.
02:08:06.571,02:08:09.571
Timothy Appnel: Sorin +1
02:09:23.436,02:09:26.436
Sorin Ionuț Sbârnea: IMHO, the idea of "you must clone code to a magic location on disk" in order to be able run ansible-test, was.... a serious design flow. Still, I think it is fixable.
02:10:18.886,02:10:21.886
Tadej Borovšak: https://sensu.github.io/sensu-go-ansible/hacking.html
02:10:19.070,02:10:22.070
Gundalow Barker: Interactive Training Scenario. If you are new to contributing to Ansible it's really worth the 20 minutes to run through the session. It's all in the website so nothing needed on your computer. https://www.katacoda.com/ansible-community/scenarios/fixing-a-bug
02:11:42.913,02:11:45.913
Andrius Benokraitis: will the docs split help here?
02:11:42.981,02:11:45.981
Sorin Ionuț Sbârnea: imho, I would personally focus on what bootstrapping steps we can avoid. That is even better than documenting them. If we endup with 100 steps very well documented, we may still fail to give an optimal developer experience.
02:12:18.721,02:12:21.721
Daniel S: for the "do you know/use" section: anyone aware of: https://github.com/fboender/ansible-cmdb
02:12:28.630,02:12:31.630
Andrius Benokraitis: collection_prep helper for Galaxy? Would that help for docs in the meantime?
02:12:33.316,02:12:36.316
Sandra McCann: Andrius - there is still a lot of collection level info that is only in github right now. We haven't had the people to bring all that into docs.ansible.com yet
02:14:06.570,02:14:09.570
Andrius Benokraitis: @Sandra - yeah, just wondering about this, thx
02:14:12.948,02:14:15.948
Timothy Appnel: there also a lot of areas of docs that are DYI -- there is no standard format place or format. for example, docs for a role. what variables does it use? what are their defaults? which are required? what does it even do?
02:14:35.335,02:14:38.335
Brian Coca: @tima role argspec in 2.11
02:14:45.561,02:14:48.561
Timothy Appnel: hopefully that stuff goes into the README, but everyone does it differently.
02:14:46.133,02:14:49.133
Brian Coca: ansible-doc -t role rolename
02:15:12.968,02:15:15.968
Andrius Benokraitis: @Tadej - where is the #1 place you'd expect the docs to be? Is this a "I can't find what I want" or "what in collection docs aren't enough and not consistent across the board?"
02:15:14.340,02:15:17.340
Timothy Appnel: hooray bcoca -- I've only been lobbying for that one for like 3 or 4 years.
02:15:20.906,02:15:23.906
Timothy Appnel: ;)
02:15:25.925,02:15:28.925
Brian Coca: tima my proposal is 6yrs old ...
02:15:33.629,02:15:36.629
Timothy Appnel: there you go.
02:15:43.769,02:15:46.769
Brian Coca: and we had 3 previous implementations ...
02:15:58.015,02:16:01.015
Brian Coca: but finally we got the 'official' and integrated one
02:17:17.949,02:17:20.949
Sorin Ionuț Sbârnea: I need to go now. I will try to connect from phone.
02:17:23.645,02:17:26.645
Timothy Appnel: does argspec cover anything more then args though? like what does the role do?
02:17:56.795,02:17:59.795
Sam Doran: @tima - No, it just validates inputs against the spec.
02:18:04.086,02:18:07.086
Sam Doran: Doesn't make any assertions about what the role does.
02:18:27.078,02:18:30.078
Tadej Borovšak: @Andrius Benokraitis In the ideal case, I would see the docs on Ansible Galaxy just like I can see the docs in the AH for example.
02:18:44.247,02:18:47.247
Timothy Appnel: @sdoran does ansible-doc generate some docs off of that spec?
02:19:16.189,02:19:19.189
Andrius Benokraitis: @Tadej, agreed, the product team has been using this in the meantime: https://github.com/ansible-network/collection_prep/
02:19:23.307,02:19:26.307
Brian Coca: it displays them and there is --json, but no html yet , if that is what you are asking
02:19:30.955,02:19:33.955
Sam Doran: @tima - Yes.
02:20:16.717,02:20:19.717
Daniel S: https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html
02:20:19.905,02:20:22.905
Sandra McCann: @Timothy - my understanding was that a docs section would be eventually added to the role argspec (much like docs are handled in plugins)... but that was an old old comment so it may not still be on the roadmap
02:20:28.739,02:20:31.739
Sviatoslav Sydorenko: yes
02:21:10.913,02:21:13.913
Sam Doran: @tima - Here's the docs on it: https://docs.ansible.com/ansible/devel/user_guide/playbooks_reuse_roles.html#role-argument-validation
02:21:14.974,02:21:17.974
Brian Coca: ansible-galaxy init -p /path/to/role
02:22:21.367,02:22:24.367
Brian Coca: github.com/ansible/proposals
02:23:01.730,02:23:04.730
Toshio Kuratomi: Is someone looking at ansible/proposals now? If not, then we should not point people at that
02:23:39.650,02:23:42.650
Brian Coca: yes
02:24:19.533,02:24:22.533
Andrius Benokraitis: you need a role init from within a collection init?
02:24:21.987,02:24:24.987
Brian Coca: ansible-galaxy init -p <collection>/roles/rolename
02:25:36.023,02:25:39.023
Brian Coca: argspec is still in devel, will be out in next release
02:25:54.815,02:25:57.815
Amin Vakil: i had a problem just yesterday with redhat containers, i'm not sure about licensing of redhat and whether there is a license which can be used for ansible-test integration test
02:26:58.024,02:27:01.024
Gundalow Barker: Amin: No license to use ansible-test
02:27:13.841,02:27:16.841
Gundalow Barker: Though I maybe missreading your question
02:27:42.038,02:27:45.038
Amin Vakil: my PR passed centos 8, but it didn't pass rhel 8, although i could realize after some time what is the problem
02:28:05.862,02:28:08.862
Amin Vakil: i wanted to know if there is going to be a rhel image which can be used with ansible-test integration --docker rhel8 or something like that
02:29:20.890,02:29:23.890
Andrius Benokraitis: @Amin: RHEL images can't be re-distributed due to the EULA. If you are a Red Hat Technology Partner there are different claims that we can talk about offline.
02:30:06.664,02:30:09.664
Amin Vakil: i'm not, i have to restart ci in my PR then which is fine, thanks!
02:30:27.404,02:30:30.404
Gundalow Barker: For the Collection Repositories under github.com/ansible-collections we (Red Hat) provide CI that allows you to run PRS against various operating systems including RHEL
02:30:34.866,02:30:37.866
Andrius Benokraitis: you can try a Developer subscription with RHEL
02:30:57.508,02:31:00.508
Amin Vakil: i have a developer subscription, can it be used with ansible-test integration somehow?
02:31:11.812,02:31:14.812
Jeff Geerling: Sounds good, I'm just getting everything set up for the day :D
02:31:16.892,02:31:19.892
Brian Coca: I was going to let him think we just went quiet cause he joined!
02:31:22.325,02:31:25.325
Jeff Geerling: lol
02:31:25.227,02:31:28.227
Daniel S: :'D
02:31:25.540,02:31:28.540
Andrius Benokraitis: @amin: https://www.redhat.com/en/blog/new-year-new-red-hat-enterprise-linux-programs-easier-ways-access-rhel
02:31:25.913,02:31:28.913
Brian Coca: ;-p
02:31:28.757,02:31:31.757
David Moreau Simard: yeah exactly what I didn't want to happen lol
02:32:29.606,02:32:32.606
Timothy Appnel: we need some music during the break. ;)
02:32:33.446,02:32:36.446
Andrius Benokraitis: @Amin should Just Work if you have a valid RHEL Developer subscription pulling from RHEL repos, and then setting up Ansible on top
02:32:46.786,02:32:49.786
Carol Chen: anyone wants to play some music? :)
02:32:50.125,02:32:53.125
Andrius Benokraitis: is it too early for karaoke
02:33:02.482,02:33:05.482
Amin Vakil: @andrius, it's not as easy as ansible-test integration --docker for sure :)
02:33:06.381,02:33:09.381
Brian Coca: final 'cut'
02:33:10.473,02:33:13.473
Timothy Appnel: boo!
02:33:26.080,02:33:29.080
Gagan Deep: NCS for the win!
02:33:30.582,02:33:33.582
Timothy Appnel: kumbaya...
02:33:38.827,02:33:41.827
Brian Scholer: brb pitch shifting "Never gonna give you up"
02:33:42.380,02:33:45.380
Andrius Benokraitis: @amin you can try the UBI8 images on registry.redhat.io if you have a login
02:33:51.172,02:33:54.172
Amin Vakil: letting ci test the PR is easier than running an rhel instance
02:33:56.816,02:33:59.816
Timothy Appnel: 99 bottles of beers on the wall...
02:34:05.424,02:34:08.424
Daniel S: Andrius: afaik one cannot install additonal packages to it, when not running on rhel
02:34:13.283,02:34:16.283
Brian Coca: 99 empty bottles of beer on the wall ...
02:34:19.305,02:34:22.305
Andrius Benokraitis: but if you have a RHEL developer sub you can AFAIK
02:34:30.158,02:34:33.158
Daniel S: sure, but not in azure, github, travis ^^
02:34:31.108,02:34:34.108
Andrius Benokraitis: you just can't redistribute the product
02:34:35.011,02:34:38.011
Ton Kersten: Carol: Check Jamulus. Special made for this
02:35:01.091,02:35:04.091
Andrius Benokraitis: yup, that's a known issue per RHEL folks
02:35:07.283,02:35:10.283
Amin Vakil: i have only a free developer program, i'm not sure if i can use that,
02:35:42.234,02:35:45.234
Sam Doran: For the RHEL tests in CI, we actually use a VM on AWS. It's not a container.
02:36:16.022,02:36:19.022
Andrius Benokraitis: seems like an opinionated "building an Ansible CI system" would be a good topic for one of these events :-)
02:36:27.963,02:36:30.963
Daniel S: would be terrific
02:37:20.640,02:37:23.640
Sam Doran: That's how we handle the registration challenge in Ansible CI.
02:37:59.272,02:38:02.272
Amin Vakil: @samdoran: ansible-test integration --color -v --retry-on-error shippable/posix/group1/ --coverage-check --changed --allow-unstable-changed --python 3.6 --remote rhel/8.3 --remote-terminate always --remote-stage prod --remote-provider default
02:38:04.844,02:38:07.844
Carol Chen: brb grabbing a snack
02:38:21.516,02:38:24.516
Amin Vakil: this is what i see in azure, it's not using docker then
02:38:23.320,02:38:26.320
Amin Vakil: i didn't know that
02:38:57.951,02:39:00.951
Jeff Goldschrafe: My favorite HP/E server story: once upon a time, by talking to the person who talked to the person who put the server orders in with a hosting company, I managed to spot a bug in an HP configuration tool used by their sales engineers that resulted in at least 10,000 servers being shipped with memory configurations
02:39:14.600,02:39:17.600
Jeff Goldschrafe: incorrect memory configurations*
02:43:38.498,02:43:41.498
Gagan Deep: wow!
02:43:42.982,02:43:45.982
Joanna Delaporte: That sounds like a great way to diagnose a RAID.
02:44:00.380,02:44:03.380
Gundalow Barker: Joanna Delaporte Hi :)
02:44:03.973,02:44:06.973
Joanna Delaporte: I have made educated guesses based on drive temp.
02:44:11.920,02:44:14.920
Joanna Delaporte: Hi John!
02:45:03.897,02:45:06.897
James Cammarata: different expectations re: screaming at computers in the age of alexa...
02:45:08.766,02:45:11.766
Sam Doran: @Amin - I think the best way would be make a local RHEL VM, which you could register with your dev subscription if needed. Then just run the test locally inside that VM. That's more or less what ansible-test is (currently) doing: copying the code into the RHEL VM and running it against localhost.
02:46:08.547,02:46:11.547
Sam Doran: @Amin - I can help you out if you get stuck. Just ping me on IRC (sdoran).
02:47:17.071,02:47:20.071
Toshio Kuratomi: Hey Joanna!
02:48:03.760,02:48:06.760
Joanna Delaporte: Is it still called a class action when the lawsuit is filed against the public?
02:48:04.074,02:48:07.074
Carol Chen: For those who just joined, we are having a longer break (30 min left). Feel free to chat and socialise in the meantime, just like during lunch/coffee breaks.
02:48:16.979,02:48:19.979
Joanna Delaporte: Instead of the other way around?
02:49:22.417,02:49:25.417
Sam Doran: Hey Joanna! 👋
02:49:23.539,02:49:26.539
Amin Vakil: @Sam: thanks! i think i have to do it at last, as i'm mostly working with issues and pull requests which work with rhel-based distros, and later on i don't know if centos 8 stream is going to be included in integration tests of it (as it changes a lot because of its concept)
02:49:34.000,02:49:37.000
Toshio Kuratomi: I think people are suing robinhood.
02:50:47.224,02:50:50.224
Amin Vakil: is c8s going to be included in ansible distro test containers?
02:52:05.611,02:52:08.611
Brian Coca: though i doubt that suit is going to succeed, both the EULA and SEC rules cover the company
02:53:12.956,02:53:15.956
Brian Coca: unless someone sent a very stupid email that is found during discovery (has happened before), it will be really hard for suit to go forward
02:54:59.119,02:55:02.119
Toshio Kuratomi: If chance of success were a requirement for filing a lawsuit, Rudy Giuliani would have been out of a job months earlioer.
02:55:06.417,02:55:09.417
Sam Doran: @Amin - Yes, we plan to keep on testing with CentOS 8. I don't think there will a separate Stream image. We'll just update the base image to the latest CentOS 8 whenever our test image needs updating.
02:56:32.795,02:56:35.795
Amin Vakil: aha, so if i understood correctly current centos8 image's base is going to be changed to stream at the end of 2021 where centos 8 will not get any updates anymore?
02:56:37.124,02:56:40.124
Brian Coca: hehe, true, that is why they filed, i'm just saying they have little chance of success
02:57:22.404,02:57:25.404
Brian Coca: /me files lawsuit against british royalty for not recognizing him as emperor
02:58:15.831,02:58:18.831
Joanna Delaporte: I have a couple hours of training to attend. I plan to drop in again later.
02:59:50.277,02:59:53.277
Jeff Goldschrafe: Also have a couple meetings, popping back in about an hour!
03:00:06.723,03:00:09.723
Brian Coca: <= world of warcraft
03:00:39.508,03:00:42.508
Brian Coca: oxigen not included
03:00:49.150,03:00:52.150
Alex Sowitzki: loop hero!
03:00:57.848,03:01:00.848
Sorin Ionuț Sbârnea: gta 3.0 (go to ansible)?
03:00:58.309,03:01:01.309
James Cammarata: Ansible Twitch Summit
03:01:30.006,03:01:33.006
Brian Coca: rimworld!
03:01:57.961,03:02:00.961
Alex Sowitzki: astroneers?
03:02:27.079,03:02:30.079
Brian Coca: factorio is great way to find 'spaghetti programming'
03:03:17.052,03:03:20.052
Alex Sowitzki: did not expect this to happen
03:03:34.111,03:03:37.111
Alex Sowitzki: <insert I love this community meme>
03:03:59.725,03:04:02.725
Carol Chen: <3
03:04:08.638,03:04:11.638
Brian Coca: he, im opposite, i cannot learn unless i visualize
03:05:53.131,03:05:56.131
Carol Chen: greg's caricature: https://twitter.com/Gwmngilfen/photo
03:06:00.471,03:06:03.471
Sam Doran: @Amin - Maybe, maybe not. We update our test images on an informal, as needed schedule. Currently we are using 8.2.2004. The latest tag is 8.3.2011, which is not stream. We will use whatever the latest version tag is when we update the base image. I imagine that will eventually be stream.
03:06:05.404,03:06:08.404
Alex Sowitzki: @gregory did you also play the DLC? it is amazing
03:06:13.443,03:06:16.443
Brian Coca: entertainment!
03:06:18.237,03:06:21.237
Brian Coca: love the 'gopher power'
03:06:30.853,03:06:33.853
Brian Coca: s/gopher/hamster/
03:06:47.030,03:06:50.030
Alex Sowitzki: you have multiple asteroids and rocket transit
03:07:01.342,03:07:04.342
Alex Sowitzki: so much suffocation
03:08:25.860,03:08:28.860
Carol Chen: oops forgot I was sharing that window. sorry for dropping the timer for a minute there
03:12:27.785,03:12:30.785
Ton Kersten: I'm gonna call it a day. Hope to see you IRL real soon
03:12:33.948,03:12:36.948
Alex Sowitzki: I would watch it
03:12:45.998,03:12:48.998
Brian Coca: you need lots of water to stream .. dry mouth ..
03:14:26.900,03:14:29.900
Sam Doran: @Amin - I updated our base images a while ago to use a specific version tag. The CentOS repo currently has “stream” and “stream8” tags. I’m not sure if they plan to add version tags for stream or just move those “stream” tags, much like “latest”. If they don't offer specific version tags, then I suppose we'll have to move to using the "stream" tag. But we haven't really discussed it.
03:15:08.281,03:15:11.281
Sam Doran: Hallway track is the best. I miss being with you all IRL.
03:15:28.829,03:15:31.829
Brian Coca: ended up talking about how to most efficiently kill chickens in elevator with fellow person that grew up on farm ... rest of peopel in elevator ran off as soon as doors opened
03:15:34.069,03:15:37.069
Carol Chen: Thanks for joining Ton, see you soon!
03:16:00.579,03:16:03.579
Carol Chen: we'll be resuming in about 2 minutes
03:17:26.929,03:17:29.929
Toshio Kuratomi: I can barely hear it
03:18:05.121,03:18:08.121
Gagan Deep: Clacky keyboards creates Keyboard ASMR
03:18:15.167,03:18:18.167
Brian Coca: now you paste sponsored link to game purchase
03:18:25.188,03:18:28.188
Sam Doran: I found clacky keyboards to be soothing. But I don't really hear it.
03:18:53.771,03:18:56.771
Gregory Sutcliffe: brian: klei make all their games available for linux, go buy them ;)
03:19:01.563,03:19:04.563
Alex Sowitzki: dont forget to subscribe and hit the vell!!!
03:19:08.275,03:19:11.275
Alex Sowitzki: *bell
03:19:35.511,03:19:38.511
Amin Vakil: @sam gotcha, thanks!
03:21:11.041,03:21:14.041
Gundalow Barker: Brad is currently presenting https://github.com/ansible/community/wiki/Network%3A2021-Spring-Roadmap
03:21:20.679,03:21:23.679
Sam Doran: @Amin - You can always reach out to me on IRC with more questions. It's complicated. 🤪
03:21:21.502,03:21:24.502
Andrius Benokraitis: TL;DR: resource modules vs. command/config modules (basically)
03:22:03.488,03:22:06.488
Sam Doran: Resource modules are so awesome.
03:23:49.786,03:23:52.786
Andrius Benokraitis: FYI there are lots of blogs on resource modules on ansible.com/blog
03:24:12.551,03:24:15.551
Andrius Benokraitis: Return values: https://www.ansible.com/blog/ansible-network-resource-modules-deep-dive-on-return-values
03:24:59.814,03:25:02.814
Andrius Benokraitis: vlans resource module: https://www.ansible.com/blog/deep-dive-on-vlans-resource-modules-for-network-automation
03:25:41.962,03:25:44.962
Andrius Benokraitis: Cisco ASA ACLs resource module: https://www.ansible.com/blog/ansible-security-automation-resource-modules
03:26:14.619,03:26:17.619
Andrius Benokraitis: Deep dive on ACLs resource module: https://www.ansible.com/blog/deep-dive-acl-configuration-management-using-ansible-network-automation-resource-modules
03:26:42.424,03:26:45.424
Andrius Benokraitis: Getting started with OSPFv2 resource module: https://www.ansible.com/blog/getting-started-with-ospfv2-resource-modules
03:26:49.401,03:26:52.401
James Cassell (cyberpear): too bad about "single user mode" overload of meaning vs Linux
03:28:19.730,03:28:22.730
James Cassell (cyberpear): does that muck w/ BSD licensed modules licensing? or no concern since it's optional?
03:29:03.369,03:29:06.369
Brian Coca: no, being imported wont, only time you are affected is when you yourself import gpl code
03:29:12.733,03:29:15.733
Brian Coca: opposite direction
03:30:29.750,03:30:32.750
Toshio Kuratomi: cyberpear: BSD (w/out ad clause), no. But it sounds like it could open the door to new licensing issues.
03:31:54.504,03:31:57.504
Andrius Benokraitis: "Are you using network resource modules?" poll just landed
03:32:02.996,03:32:05.996
Gundalow Barker: ^^^^^^^^^^^^^^^^^^^^^
03:32:36.460,03:32:39.460
Gundalow Barker: DING DING DING We'd really appreciate people taking the time to do the Polls in Google Meet (top right of the chat window)
03:39:28.848,03:39:31.848
Mark Chappell: I've done things like this in custom (local) modules before.
03:40:49.973,03:40:52.973
Sviatoslav Sydorenko: cyberpear: you forgot to unclick the "raise hand" button
03:41:04.988,03:41:07.988
James Cassell (cyberpear): thx
03:41:45.473,03:41:48.473
Gundalow Barker: ==============================
03:42:55.477,03:42:58.477
Sagi Shnaidman: In openstack we use launchpad teams and that works fine
03:43:29.884,03:43:32.884
Gundalow Barker: Sagi that's good feedback, thank you. Do you have a dedicated bot/service account for automated builds?
03:44:33.578,03:44:36.578
Sagi Shnaidman: @gundalow, we use launchpad as a bugtracker only though
03:44:40.476,03:44:43.476
Toshio Kuratomi: sshnaid: The problem right now is we need to have a launchpad user converted into a team.
03:45:24.887,03:45:27.887
Toshio Kuratomi: (Waiting on launchpad admins to do that for us)
03:47:40.916,03:47:43.916
Sagi Shnaidman: FYI we have RPMs for each collection in Fedora?
03:47:54.237,03:47:57.237
Daniel S: hopefully not
03:48:30.234,03:48:33.234
Gundalow Barker: Anyone interested in helping with packaging?
03:49:29.394,03:49:32.394
David Moreau Simard: @Sagi not yet that I know of
03:49:33.966,03:49:36.966
Sagi Shnaidman: https://koji.fedoraproject.org/koji/search?terms=ansible-collection*&type=package&match=glob
03:49:58.245,03:50:01.245
Anastasios Lisgaras: Are there any notes/documents on how we can help?
03:50:05.430,03:50:08.430
Sam Doran: Truth!
03:50:21.193,03:50:24.193
Sam Doran: Doesn't everyone just run Ansible from source?
03:50:23.080,03:50:26.080
Sagi Shnaidman: @David, I'm in the process of packaging last collection in Fedora now: https://bugzilla.redhat.com/show_bug.cgi?id=1927697
03:50:28.953,03:50:31.953
Andrius Benokraitis: is this ansible and ansible-core both on PPA?
03:50:34.472,03:50:37.472
Daniel S: @gundalow: For fedora? Currently, the server WG is somewhat "re-defining" itseölf. Not sure, if there is much attention to ansible for a while (server wise). It may be another story for workstation.
03:51:14.502,03:51:17.502
Toshio Kuratomi: andrius: yes. Right now ansible-base is in PPA but not ansible.
03:51:48.360,03:51:51.360
David Moreau Simard: @Sagi I think the intention for Fedora is to package the collections that are included in the Ansible community package but it's still very WIP
03:52:31.530,03:52:34.530
Brian Coca: distributions are much more conservative on versions
03:53:05.178,03:53:08.178
Amin Vakil: debian is on 2.7.7 on buster (stable) :)
https://packages.debian.org/search?keywords=ansible
03:53:08.390,03:53:11.390
Felix Fontein: Debian currently has Ansible 2.7 on buster (stable): https://packages.debian.org/buster/ansible
03:53:42.803,03:53:45.803
Deric Crago: what I've done for testing so far (not official): https://github.com/dericcrago/ansible.ppa/tree/main/.github/workflows -> https://launchpad.net/~deric.crago
03:54:03.519,03:54:06.519
Amin Vakil: thanks!
03:54:32.332,03:54:35.332
Gundalow Barker: ==================================================
03:56:33.917,03:56:36.917
Carol Chen: https://docs.ansible.com/ansible/
03:56:37.419,03:56:40.419
Carol Chen: https://docs.ansible.com/ansible-core/
03:58:46.553,03:58:49.553
Brian Scholer: 👏
03:59:20.386,03:59:23.386
Brian Coca: cyan and black stickers!
04:01:12.562,04:01:15.562
Cruz Pitre: Exactly; what are we doing for search between the sites?
04:02:52.076,04:02:55.076
Alicia Cozine: Agenda for the Docs Working Group: https://github.com/ansible/community/issues/579
04:03:36.878,04:03:39.878
Cruz Pitre: The "edit in github" functionality available, or planned?
04:04:28.192,04:04:31.192
Cruz Pitre: Thanks for both answers!!
04:04:34.125,04:04:37.125
Brian Scholer: I wonder if it could be a field in plugin/module docstrings, to signal or provide a URL for editing
04:04:52.322,04:04:55.322
Alicia Cozine: interesting idea Brian
04:05:03.474,04:05:06.474
Gundalow Barker: Brian: It's possible, we do know the namespace and collection name
04:05:03.885,04:05:06.885
Alicia Cozine: definitely bring it to the DaWGs meeting if you can
04:05:32.335,04:05:35.335
Carol Chen: go DaWGs!
04:05:33.018,04:05:36.018
Brian Scholer: sure will do, I usually attend (@briantist) but I'm often in other meetings simultaneously 😅
04:05:56.909,04:05:59.909
Felix Fontein: The situation is more tricky for collections like community.general, where symlinks / redirects hide the real path of modules.
04:05:59.240,04:06:02.240
Gundalow Barker: Though we may need to hardcode (or do a lookup at docs build time) for the mapping from Collection name to GitHub Repo. I believe that data is available via the Galaxy API
04:05:59.500,04:06:02.500
Daniel S: have to drop off for now, but will be beack 17:30 UTC. Thanks a all :)
04:06:15.053,04:06:18.053
Gundalow Barker: Daniel: Thank you for being here
04:06:24.752,04:06:27.752
Carol Chen: thanks, see you Daniel!
04:06:53.032,04:06:56.032
Carol Chen: maybe we can play the ansible song
04:07:30.143,04:07:33.143
Carol Chen: https://www.youtube.com/watch?v=NpqPEGLAo8o&ab_channel=KarolyVEGH
04:09:36.549,04:09:39.549
Toshio Kuratomi: github repo url is optional metadata
04:09:54.224,04:09:57.224
Toshio Kuratomi: and it might not even point to github
04:10:14.918,04:10:17.918
Jeff Geerling: @Gregory - if in OBS, you'd need to go to advanced audio properties on that channel and then select the option to monitor and send through stream
04:10:26.003,04:10:29.003
Jeff Geerling: then you can monitor in headphones while it is also streamed out
04:10:39.180,04:10:42.180
Jeff Geerling: (just don't do that through speakers with a mic, instant feedback loop :D)
04:10:55.455,04:10:58.455
Jeff Geerling: This is the community content we need.
04:11:27.806,04:11:30.806
Anastasios Lisgaras: Gregory you are fantastic!
04:11:30.043,04:11:33.043
Anastasios Lisgaras: xaxa thank you! :-)
04:11:33.415,04:11:36.415
David Moreau Simard: Great song :p There was also the pep8 song recently https://www.youtube.com/watch?v=hgI0p1zf31k
04:11:39.061,04:11:42.061
Anastasios Lisgaras: Very nice!!
04:11:58.764,04:12:01.764
Lydie Mode-Malivert: Nice!
04:12:24.111,04:12:27.111
Jeff Geerling: aaah...
04:12:32.241,04:12:35.241
Jeff Geerling: application audio capture can be funky
04:18:35.178,04:18:38.178
Timothy Appnel: Question: what is the recommended way to disambiguate "ansible" in a general sense (community+product+language) from the community distribution since it is not supposed to be referred to as ACD or the like? I trip over my words communicating which of these I'm referring to currently.
04:19:38.658,04:19:41.658
Gundalow Barker: =========================
04:19:40.894,04:19:43.894
David Moreau Simard: @Tim good question I don't have an answer for but worth discussing
04:21:37.858,04:21:40.858
Toshio Kuratomi: @tima: ansible project or ansible ecosystem if you want to mean "everything"
04:22:44.346,04:22:47.346
Toshio Kuratomi: I use "ansible package" most of the time when refering to the ansible package on pypi since I never knwo if I'm talking to someone who uses ansible to mean ansible-core.
04:23:12.638,04:23:15.638
Toshio Kuratomi: a survery about the survey ;-)
04:23:48.217,04:23:51.217
Brad Thornton: I've switched to referring to it as "Ansible package" when referring to the community distribution, because gundalow told me to.
04:25:23.185,04:25:26.185
Timothy Appnel: ACD would have been so much easier since it describes to anyone exactly what it is. :/
04:26:42.191,04:26:45.191
David Moreau Simard: The name of the actual package is ansible, though, not acd -- so referring to it as the ansible package is not wrong
04:27:10.058,04:27:13.058
Toshio Kuratomi: yeah, referring to it as acd would be really confusing since the package name is ansible.
04:27:59.211,04:28:02.211
Gundalow Barker: https://emeraldreverie.org/2021/02/23/docs-survey-2020-results/
04:28:47.276,04:28:50.276
Sagi Shnaidman: 'package' may refer to RPM package as well, which can confuse..
04:30:07.018,04:30:10.018
Alicia Cozine: https://docs.ansible.com/ansible/latest/collections/index_module.html
04:30:17.988,04:30:20.988
Alicia Cozine: https://docs.ansible.com/ansible/latest/collections/all_plugins.html
04:33:39.647,04:33:42.647
Brian Coca: also ansible package for <=2.9 very diff than ansible package for >=2.10
04:33:41.398,04:33:44.398
Brian Scholer: I honestly don't remember if I took the survey 😭it's something I would've responded to if I saw it.. but I have no memory of it.. which is more an indictment of my memory than anything else
04:33:55.878,04:33:58.878
Gundalow Barker: DING DING DING: Please take the time to do the Poll. Top right of the chat window the Triangle, Square, Circle icon
04:34:11.982,04:34:14.982
Jesse Pretorius: I barely recall what I had for breakfast. :p
04:34:26.447,04:34:29.447
Toshio Kuratomi: for end user experience, the ansible package for 2.9 and 2.10 should be almost the same (about the same as 2.8 and 2.9(
04:36:53.333,04:36:56.333
Cruz Pitre: lol @gundalow all good so far.
04:40:00.642,04:40:03.642
Gundalow Barker: ==========================
04:40:09.735,04:40:12.735
James Cammarata: we're doin it live!
04:40:25.679,04:40:28.679
Andrius Benokraitis: https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/roadmap/ROADMAP_2_11.rst
04:41:52.826,04:41:55.826
Sviatoslav Sydorenko: The docs page is https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_11.html
04:42:10.531,04:42:13.531
David Moreau Simard: 2.11 will also ship improvements to make it easier to run with (or without!) selinux/yum/dnf/apt libs that tend to be an issue when running out of virtualenvs and stuff like that
04:45:06.091,04:45:09.091
James Cassell (cyberpear): drawbacks of using ctypes?
04:45:14.209,04:45:17.209
James Cassell (cyberpear): vs SELinux python deps?
04:45:33.064,04:45:36.064
Matt Davis: I can talk about that in a bit if there's time
04:47:41.345,04:47:44.345
Brian Coca: xml_file ...
04:47:44.622,04:47:47.622
James Cassell (cyberpear): selogin, seboolean would need the respawn?
04:47:53.439,04:47:56.439
Matt Davis: correct
04:49:25.226,04:49:28.226
Sorin Sbarnea: happy to hear about backporting
04:49:37.734,04:49:40.734
Gundalow Barker: Thoughts, comments, concerns?
04:51:34.006,04:51:37.006
Brian Coca: still trying to mount flamethrower on pitchfork
04:51:48.052,04:51:51.052
Sorin Sbarnea: dropping py27 all ok, going directly to py38 -- will prevent rhel 8 users from using newer ansible too.
04:52:21.877,04:52:24.877
Sam Doran: Python 3.8 is available on RHEL 8.
04:52:46.015,04:52:49.015
David Moreau Simard: available != default
04:53:02.607,04:53:05.607
Sorin Sbarnea: exactly, default matters
04:53:26.903,04:53:29.903
Sorin Sbarnea: especially as this is directly related to ability to produce rpms./
04:53:30.791,04:53:33.791
Matt Davis: Default matters for targets, not for controllers. None of our other deps are there by default either, yet it works...
04:53:36.934,04:53:39.934
Sviatoslav Sydorenko: not anymore, with the respawning work done
04:53:50.437,04:53:53.437
Matt Davis: Yeah, that was why the respawn needed to happen
04:54:09.449,04:54:12.449
Matt Davis: (still only for controller though- it already would've worked fine as a target, since we're not touching the target Python versions)
04:55:25.246,04:55:28.246
Rick Elrod: @Sorin it is available as an AppStream by default. You can `dnf install python38` on a fresh RHEL 8 box (with AppStream enabled) without needing to do anything fancy or enable any modules or anything.
04:56:18.509,04:56:21.509
Matt Davis: (sidecar also a win for non-Python plugins, of which there are ever more)
04:56:33.147,04:56:36.147
Brian Coca: the sidecar currently is the .py file
04:58:39.504,04:58:42.504
Matt Davis: we doubled-dog-dared him
04:59:17.817,04:59:20.817
Felix Fontein: more tooling is always great :)
05:01:13.574,05:01:16.574
Sorin Sbarnea: sure we have phillips, Pozidriv, ...
05:01:14.849,05:01:17.849
Toshio Kuratomi: Sorta security only... since it's also getting targetted backports of new features, right?
05:01:44.533,05:01:47.533
Toshio Kuratomi: Ah, okay :-)
05:02:03.046,05:02:06.046
Toshio Kuratomi: "Never say never again" ;-)
05:02:32.197,05:02:35.197
Rick Elrod: Yeah, so one more bugfix release cycle for 2.9 as of right now. So if anyone needs anything in before it goes security-only, do that soon :)
05:02:35.796,05:02:38.796
Sorin Sbarnea: My my concern is that any tooling that works only with the shiny/bleeding edge ansible, will have low chances of being adopted by most users.
05:03:08.264,05:03:11.264
Sorin Sbarnea: the policy of no feature backporting is in direct conflict with tooling concept.
05:03:32.504,05:03:35.504
Timothy Appnel: sorin +1
05:03:47.322,05:03:50.322
Sviatoslav Sydorenko: https://hynek.me/articles/semver-will-not-save-you/
05:03:59.602,05:04:02.602
Sorin Sbarnea: yeah good article and very real
05:03:59.941,05:04:02.941
Brian Coca: we do follow 'kindof' semver just shifted by 1
05:04:36.365,05:04:39.365
Sorin Sbarnea: i need to add a shortcut for a quick reply to anyone that advocates SemVer too agresively.
05:05:40.790,05:05:43.790
Brian Coca: its our version of perl's 'fixed in six'
05:06:50.342,05:06:53.342
Sorin Sbarnea: so no plans to rewrite ansible core in rust? ;)
05:07:00.381,05:07:03.381
James Cammarata: i did it in golang already...
05:07:04.914,05:07:07.914
Brian Coca: zig, rust is too old now
05:07:08.426,05:07:11.426
Gundalow Barker: I think Sivel has a fork. Jimi has a golang
05:07:08.819,05:07:11.819
James Cammarata: that was enough
05:07:22.610,05:07:25.610
Brian Coca: there are 5 haskell ports ...
05:08:50.664,05:08:53.664
Sorin Sbarnea: So I will go for an Swift approach,... you know to get both scripting and compiled,...
05:09:17.818,05:09:20.818
Felix Fontein: let's do a javascript port, then you can just run it in a browser
05:09:21.944,05:09:24.944
Sviatoslav Sydorenko: could always write a random new ansible version package name generator in rust
05:10:14.474,05:10:17.474
Alicia Cozine: or a choose-your-own-language release, with competitions among ^^^
05:10:22.776,05:10:25.776
Toshio Kuratomi: Eh, that blog post starts out with a false statement at the very beginning.
05:10:24.428,05:10:27.428
Felix Fontein: var Ansible = function() { return { 'main': function() { ... } } }
05:11:28.639,05:11:31.639
Sorin Sbarnea: my big dilemma is which is going to be the nam of the core package in 2 years from now? ansible-nucleus, ansible-boson?
05:11:34.100,05:11:37.100
Felix Fontein: Toshio: which statement do you mean? Having tuples of integers?
05:11:54.708,05:11:57.708
Toshio Kuratomi: "Let’s set the stage by laying down the ultimate task of version numbers: being able to tell which version of an entity is newer than another. "
05:12:14.253,05:12:17.253
Toshio Kuratomi: That's true for some projects but not for others.
05:12:57.078,05:13:00.078
Felix Fontein: For most people, being able to decide which version is newer is the main purpose though.
05:13:05.905,05:13:08.905
Toshio Kuratomi: I skipped to the end of the blog, though, and his summary looks like there's probably some interesting ideas inside of it. But maybe learning the wrong things from those ideas.
05:13:41.642,05:13:44.642
Toshio Kuratomi: I don't know about that.
05:14:08.957,05:14:11.957
Toshio Kuratomi: I mean, if the goal is "I always want the latest", then everyone would use git.
05:14:23.944,05:14:26.944
Carol Chen: brb
05:14:25.358,05:14:28.358
Toshio Kuratomi: Or everyone familiar with open source would always use upstream.
05:14:58.932,05:15:01.932
Toshio Kuratomi: There's a ton of work done so that usrs don't have to get the latest.
05:15:40.293,05:15:43.293
Toshio Kuratomi: A Linux distro does the work so that people can get something that's compatible with the libraries and base packages that are on their system,. for instance.
05:18:13.038,05:18:16.038
Felix Fontein: True. But users still use version numbers to figure things like "has this version feature X" by determinining whether the version is smaller or larger than the version feature X was added.
05:18:35.124,05:18:38.124
Felix Fontein: (Is this chat terribly slow for anyone else as well? Sometimes typing here takes seconds for text to appear.)
05:19:50.624,05:19:53.624
Brian Coca: tis slooow
05:20:30.255,05:20:33.255
Brian Coca: well, normally everyone 'wants the lastest, but dont break anything im using even if its not a documented feature'
05:20:54.984,05:20:57.984
Jeff Geerling: /me is anticipating the next session
05:20:58.602,05:21:01.602
Brian Coca: the trick is balancing on which side to err (minization of pitchforks and torches)
05:21:03.213,05:21:06.213
Jeff Geerling: zbr/Sorin: Hi!
05:21:05.834,05:21:08.834
Toshio Kuratomi: felixfontein yep. But alsol "has this feature been removed?"
05:21:31.564,05:21:34.564
Felix Fontein: Jeff: me too :)
05:21:35.258,05:21:38.258
Timothy Appnel: The thing I think we forget is that what comes to us as second nature is completely foreign to most others who don't live and breath ansible or python or open source.
05:21:57.053,05:22:00.053
Rick Elrod: @bcoca reminds me of people who want RHEL because they need super stable systems...and then they run their most important apps/libs at git HEAD and defeat the whole point :)
05:22:09.703,05:22:12.703
Carol Chen: re: slow chat, google meet supposedly can handle 250 participants in this set up but definitely one of the slowest chat sessions I've experienced
05:22:29.428,05:22:32.428
Felix Fontein: Carol: it is probably not optimized for 250 people using the chat all the time :D
05:22:38.865,05:22:41.865
Carol Chen: yep!
05:22:43.730,05:22:46.730
Felix Fontein: Feels a bit like AZP ;)
05:22:54.730,05:22:57.730
Felix Fontein: (when builds are still running ;) )
05:23:09.844,05:23:12.844
Carol Chen: :D
05:23:19.045,05:23:22.045
Toshio Kuratomi: I think what a user really wants to achieve is usually, "I want to maximize the wroking features of my system without breaking anything that I currently use"
05:23:30.040,05:23:33.040
Felix Fontein: I would have expected better from google :)
05:23:55.041,05:23:58.041
Jeff Geerling: you'd think after 25 Google chat products over the years, at least chat would be rock solid and fast
05:24:07.194,05:24:10.194
Toshio Kuratomi: I'd expect the opposite ;-)
05:24:11.474,05:24:14.474
Jeff Geerling: /me stares at the dumpster fire that is gchat
05:24:32.025,05:24:35.025
Carol Chen: google wave, google buzz...
05:25:14.196,05:25:17.196
Felix Fontein: /me looks at IRC, which feels like stone-age compared to the modern stuff, but just works :)
05:25:37.151,05:25:40.151
Toshio Kuratomi: I bet there's something in Fred Brooks' writing that describes google's chat program history perfectly...
05:27:39.191,05:27:42.191
Carol Chen: I'm going to stop and restart the recording to see if it helps
Gundalow Barker7:29 PM
============================
Community Galaxy update
Felix Fontein7:30 PM
Carol: it's probably the amount of chat history
Jeff Geerling7:31 PM
lol 'recording stopped' 'recording stopped' 'recording stopped'
00:00:10.013,00:00:13.013
Brian Coca: the present is just the future 'actualized'
00:01:24.491,00:01:27.491
Jeff Geerling: french horn spotted
00:02:19.895,00:02:22.895
Carol Chen: Felix: possibly, but still, you'd think google can handle that :P
00:02:46.102,00:02:49.102
Brian Coca: 12039854774 <= num of times i was asked 'when are you OSS tower?'
00:03:56.505,00:03:59.505
Jeff Geerling: 12039854772 <= num of times I asked bcoca that
00:05:11.360,00:05:14.360
Brian Coca: no, i redirectd you to bot after first million
00:05:23.133,00:05:26.133
Brian Coca: ;-p
00:05:37.899,00:05:40.899
Sandra McCann: bcoca-bot!
00:07:48.167,00:07:51.167
Sorin Sbarnea: i did not hear mazer yet...
00:07:54.843,00:07:57.843
Brian Coca: ssssshhhhh
00:08:05.662,00:08:08.662
Timothy Appnel: long live mazer!
00:08:57.854,00:09:00.854
Jeff Geerling: Collections = amazingly better experience for everything not a role
00:09:01.207,00:09:04.207
Jeff Geerling: ;)
00:09:06.468,00:09:09.468
Toshio Kuratomi: geerlingguy: I wish I could have seen your expressions for those last two bullet points
00:09:11.297,00:09:14.297
Rich Megginson: +1
00:09:11.873,00:09:14.873
Sorin Sbarnea: lets say that mazel did not get much mazel tov
00:09:14.131,00:09:17.131
Timothy Appnel: +1
00:09:51.652,00:09:54.652
Brian Coca: /me can see geerlinguy smile now
00:10:39.560,00:10:42.560
Rich Megginson: if it were 1) trivially easy to collection-ize roles 2) support for "private" roles, modules, plugins in a collection - then the system roles team could have supported collections much much earlier
00:11:04.126,00:11:07.126
Brian Coca: its trivial unless you had plugins in the roles .. then its 'fun'
00:11:33.209,00:11:36.209
James Cammarata: @rich check out the script sivel mentioned earlier, it takes care of most things for you
00:11:36.121,00:11:39.121
Brian Coca: see the migration tool we used in the 'collection disaspora' and that still had many things that were left to manual updates (specially docs)
00:11:36.658,00:11:39.658
Rich Megginson: https://github.com/linux-system-roles/auto-maintenance/blob/master/lsr_role2collection.py
00:11:57.839,00:12:00.839
Sorin Sbarnea: i already discovered the moduleutils issue matt is talking about, lucky for me the shared bit was shared with a single module, so I combined them.
00:12:06.027,00:12:09.027
Rich Megginson: yes - we took that script and extended it in all sorts of complicated ways to handle all of our strange corner cases
00:12:52.370,00:12:55.370
James Cammarata: @rich - feedback on what those corner-cases were would be greatly appreciated
00:14:07.731,00:14:10.731
Jeff Geerling: Yes. Giving some goalposts I can look to for a migration process is the main thing.
00:14:21.154,00:14:24.154
Jeff Geerling: I'd love to use Collections... once I can migrate to them :)
00:14:26.753,00:14:29.753
Rich Megginson: plus - the system roles team will have to support the legacy roles format for the foreseeable future
00:14:52.939,00:14:55.939
Jeff Geerling: Wait which features?! Can't leave us hanging :P
00:15:05.819,00:15:08.819
Rich Megginson: so we keep our github repos in the old role format and dynamically generate the collection in our build
00:15:59.049,00:16:02.049
Sorin Sbarnea: jeff: i suspect that side-effects like the fact that embedded module becomes availble to the playbook after a role run, will go away. AFAIK, that can be considered a bug, and not a feature.
00:16:01.048,00:16:04.048
Rich Megginson: using ruamel so that the converted code matches as closely as possible to the original (keeps the ansible-lint, yamllint, etc. suppressions down to a minimum, helps with debugging the collection if we can easily match that with the role source, etc.)
00:16:42.953,00:16:45.953
Toshio Kuratomi: Hmm... that might put galaxy.ansible.com in danger of GPL violation (assuming that the system roles are licensed GPL)
00:16:43.433,00:16:46.433
Sorin Sbarnea: ruamel will not happen, the maintenance status of the project is very problematic, i started a fork about an year ago.
00:17:20.695,00:17:23.695
Rich Megginson: we only use ruamel in our build - we don't actually package or otherwise distribute it - how is it problematic?
00:17:45.891,00:17:48.891
Jeff Geerling: The funny thing is, my docker role is one that I actually use the least :D I'm guessing somebody's system setup playbook uses it and it's been forked like a jillion times or something
00:17:49.377,00:17:52.377
Rich Megginson: is there another python yaml lib that can do a reasonable "round trip"?
00:17:50.176,00:17:53.176
Brian Coca: @Rich we did find corner cases in whcih ruamel also behaved differently and would not port the tests correctly, why we ended up migrating via pyyaml
00:18:00.243,00:18:03.243
Jeff Geerling: (But at least I use it... a few of my roles I don't use, just barely maintain now)
00:18:07.825,00:18:10.825
Felix Fontein: Jeff: maybe some CI systems use it... ;)
00:18:09.685,00:18:12.685
Sorin Sbarnea: maintainer did block access to some issues, as in making them private, some real censorship.
00:18:48.739,00:18:51.739
Rich Megginson: hmm - well hopefully we can limp along with the current ruamel implementation until we can drop the legacy role format altogether . . .
00:18:55.985,00:18:58.985
Sorin Sbarnea: some details are on https://github.com/pycontribs/ruyaml/issues/1
00:19:20.977,00:19:23.977
Jeff Geerling: We're only seeing the 'feature polls' slide with the 10. At least I am only seeing that :/
00:19:33.247,00:19:36.247
Gundalow Barker: DING DING DING: Voting time. Top of the chat window, click the "Triangle, Square, Circle" then click polls.
00:19:42.301,00:19:45.301
Carol Chen: please vote on the polls (top right with bunch of shapes -> click -> polls)
00:19:45.385,00:19:48.385
Carol Chen: in google meet
00:19:59.767,00:20:02.767
Jeff Geerling: ooh
00:22:16.601,00:22:19.601
Sorin Sbarnea: I hope to see someone from galaxy team involved with ansible-lint, galaxy is stuck on old version of linter and I want to hear what prevents it from using newer version.
00:22:44.494,00:22:47.494
Jeff Geerling: heh... right now the answer could be "until 5.0.3 is released, all geerlingguy's roles start failing" ;)
00:22:59.587,00:23:02.587
Jeff Geerling: (my selfish reason)
00:23:05.683,00:23:08.683
Sorin Sbarnea: I am not asking for eng-effort to fix bugs, but only collaboration / consultation.
00:23:57.155,00:24:00.155
Jeff Geerling: @Sorin - It would be really cool if maybe galaxy qa would be able to run the latest rc release (or even dev) of ansible-lint and then you could see if it will break there or not, or could do a diff of quality scores before/after or something
00:24:03.144,00:24:06.144
Jeff Geerling: so many moving parts though
00:24:19.940,00:24:22.940
Daniel S: There was an option missing: "PLease don't"
00:24:51.706,00:24:54.706
Felix Fontein: I'm not sure how to understand that GH SSO poll.
00:25:12.587,00:25:15.587
Sorin Sbarnea: We could extend the proposed canary test to test the first 50? most popular roles listed and report errors, so we are confident that we do not upset existing users w/o good reasons.
00:25:24.204,00:25:27.204
Jeff Geerling: Can I get an "I voted" sticker? ;)
00:25:31.381,00:25:34.381
Daniel S: For #7, do we really want/need github as auth backend? For some this may be actually a problem
00:25:41.536,00:25:44.536
Carol Chen: Jeff: I'll see what I can do xD
00:25:54.120,00:25:57.120
Sviatoslav Sydorenko: I saw some reddit users annoyed by having to login via GH
00:26:49.057,00:26:52.057
Andrius Benokraitis: are all these features for galaxy_ng and NOT the current galaxy.ansible.com?
00:26:53.286,00:26:56.286
Sorin Sbarnea: i really do not understand polls with "A vs B" where answers are like I do not care, or care.
00:26:55.837,00:26:58.837
Daniel S: Since there is already FAS/RH SSO, etc. Why not using these?
00:27:03.341,00:27:06.341
Sorin Sbarnea: wasn't this about a "vs"?
00:27:18.306,00:27:21.306
Jeff Geerling: @Andrius - It seems like the idea is these decisions would guide what goes into NG from community galaxy current gen
00:27:37.810,00:27:40.810
Jacob Evans: There are definitely some anti-Microsoft people out there that do not like the fact that they own GitHub now. I would bet that's where much of the anti-GitHub sentiment comes from
00:27:44.234,00:27:47.234
Jeff Geerling: @Daniel - I'd love to avoid tying things to my RH account. That account system is a dumpster fire
00:27:55.978,00:27:58.978
Andrius Benokraitis: right, so it goes into galaxy_ng, and then would apply once galaxy.ansible.com is migrated to the new codebase
00:27:56.202,00:27:59.202
Jeff Geerling: (for anyone who isn't deep in the RH ecosystem already)
00:28:10.386,00:28:13.386
Daniel S: @jeff same for my github account ;)
00:28:26.559,00:28:29.559
Daniel S: If I have my code at my own repo, I still need a gh account to push collections/roles
00:29:14.301,00:29:17.301
Sorin Sbarnea: At this moment galaxy namespace cannot even be mentioned inside any in-repo file, and thus makes testing of installed role a gamble.
00:29:46.002,00:29:49.002
Sorin Sbarnea: galaxy_info, does not have a namespace field, only a role name one.
00:29:48.341,00:29:51.341
David Moreau Simard: +1 on survey, contributor summit audience is limited
00:29:51.071,00:29:54.071
Andrius Benokraitis: I think the moral of the story is that there are multiple team that are impacted for feature requests to "galaxy" which could mean ansible-galaxy CLI, the backend galaxy_ng, and ansible-core
00:30:31.019,00:30:34.019
Jeff Geerling: @Andrius plus community tools like ansible-lint, molecule
00:30:42.944,00:30:45.944
Felix Fontein: I'm glad to hear the part on roles being planned to be supported long-term!
00:30:58.069,00:31:01.069
Daniel S: yup, awesome news
00:31:14.654,00:31:17.654
Sorin Sbarnea: i wonder how galaxy experience will improve considering that the server side is "maintenance" mode until ng is ready and that the client cannot be modified for older versions of ansible.
00:32:41.911,00:32:44.911
Andrius Benokraitis: @sorin this is the $64,000 question
00:33:12.602,00:33:15.602
Felix Fontein: Yeah, would be nice if `ansible-galaxy collection install` would get more stable / performant :)
00:33:18.471,00:33:21.471
Gundalow Barker: DING DING DING: Please do the polls
00:33:21.938,00:33:24.938
Gundalow Barker: ========================
00:34:08.047,00:34:11.047
Toshio Kuratomi: This one sounds like it will be good to have awcrosby listening in.
00:34:41.510,00:34:44.510
Brian Coca: for galaxy/AH to display these docs also
00:34:57.742,00:35:00.742
Jeff Geerling: GALAXY for docs++
00:34:59.953,00:35:02.953
Toshio Kuratomi: or at least, so that they don't conflict.
00:35:03.205,00:35:06.205
Jeff Geerling: that just makes sense
00:35:11.932,00:35:14.932
Daniel S: indeed
00:35:52.301,00:35:55.301
Brian Coca: TeX
00:35:54.963,00:35:57.963
Felix Fontein: RST! RST! RST!
00:35:55.923,00:35:58.923
Sorin Sbarnea: while I do not see myself looking for docs inside galaxy, I do fancy the idea of seeing galaxy enforcing docs to be present on upload.
00:35:56.228,00:35:59.228
Sagi Shnaidman: galaxy should have docs for released collection on galaxy, dos.ansible - for collection released in ansible package?
00:35:59.237,00:36:02.237
Sviatoslav Sydorenko: html
00:36:04.499,00:36:07.499
Sagi Shnaidman: HTML
00:36:09.613,00:36:12.613
Jeff Geerling: also allows collections to evolve tied to galaxy, and not requiring docs team involvement in the nitty gritty and things like module redirection
00:36:13.610,00:36:16.610
Felix Fontein: (Brian: TeX would be great, but RST is more realistic ;) )
00:36:48.490,00:36:51.490
Sorin Sbarnea: I hope we endup documenting roles using a model very similar with how is done for modules.
00:37:06.017,00:37:09.017
Jeff Geerling: markdown preferred, but I can write whatever. In the end, I like formats that require less time looking up 'how do I do this thing that I know how to do in HTML' :)
00:37:08.620,00:37:11.620
Rich Megginson: ++sorin
00:37:19.899,00:37:22.899
Jeff Geerling: Sorin++
00:37:31.800,00:37:34.800
Jeff Geerling: Docs only on galaxy
00:37:36.112,00:37:39.112
Daniel S: same
00:37:38.461,00:37:41.461
Jeff Geerling: 💯
00:37:50.744,00:37:53.744
Andrius Benokraitis: whatever is searchable
00:37:59.961,00:38:02.961
Jeff Geerling: whatever google can index
00:38:06.803,00:38:09.803
Brian Coca: grep collection/docs/ *
00:38:07.505,00:38:10.505
Jeff Geerling: docs.ansible.com search doesn't get me what I want :P
00:38:12.772,00:38:15.772
Timothy Appnel: probably galaxy because of versions
00:38:13.674,00:38:16.674
Sviatoslav Sydorenko: google + site:galaxy.ansible.com
00:38:14.018,00:38:17.018
Felix Fontein: I like docs to be on docs.ansible.com as well, at least the docs fofr collections included in the Ansible package.
00:38:19.463,00:38:22.463
Jeff Geerling: so I always do site:galaxy.ansible.com then search ;)
00:38:29.921,00:38:32.921
Jill Rouleau: Felix++
00:38:35.526,00:38:38.526
Sagi Shnaidman: Felix++
00:38:45.362,00:38:48.362
Brad Thornton: docs independant of ansible package inclusion
00:38:48.352,00:38:51.352
Amin Vakil: felix++
00:38:50.788,00:38:53.788
Brian Scholer: I really would prefer the docs for collections Felix++
00:38:58.280,00:39:01.280
Andrius Benokraitis: I think the question should be, "what should be the docs source of truth?"
00:39:01.025,00:39:04.025
Jeff Geerling: scenario guides should be outside of collections (IMHO)
00:39:08.089,00:39:11.089
Sorin Sbarnea: Everything should start with ansible-doc -- which should be able to generate the docs.
00:39:10.018,00:39:13.018
Felix Fontein: especially because the docs there will be for the version of the collection included in Ansible. I guess docs on Galaxy wlil be for the latest released version only.
00:39:45.871,00:39:48.871
Sorin Sbarnea: documentation can be build and stored inside the repo at the same time.
00:39:53.820,00:39:56.820
Jeff Geerling: @Felix - could make it so you can switch versions in collection on galaxy to see older versions, I presume
00:40:27.849,00:40:30.849
Jeff Geerling: (This all assumes Galaxy will be upgraded at some point... either investment in old codebase or get all the role MVP stuff into Galaxy NG faster)
00:40:55.539,00:40:58.539
Felix Fontein: Jeff: true, but that needs a lot more storage. Also there's the problem with doc fragments, which can come from other collections that have different versions. Combining all the possibilities is pretty much futile :)
00:41:11.989,00:41:14.989
Brian Coca: it does display them, so they are already making a choice
00:43:09.804,00:43:12.804
Tadej Borovšak: For reference: https://sensu.github.io/sensu-go-ansible/
00:43:29.388,00:43:32.388
Matt Davis: I think the ones in Galaxy today are relying on internally-supplied doc fragments, but suspect that wouldn't work for arbitrary other-collection doc fragment refs
00:43:29.624,00:43:32.624
Jeff Geerling: Right now, it's hard to document your collection
00:43:36.630,00:43:39.630
Toshio Kuratomi: I think what I'm hearing is that the complete set of people want it in both palces.
00:43:37.754,00:43:40.754
Jeff Geerling: Answer is currently "build your own documentation system" :D
00:43:49.112,00:43:52.112
Toshio Kuratomi: With individuals wanting it to be in either one or the other.
00:43:50.859,00:43:53.859
Sorin Sbarnea: i wonder if it would be possible to have a single document documentation for each collection/role or this would not scale. Why? single doc approach reduces a lot of complexity.
00:44:08.333,00:44:11.333
Felix Fontein: I've created a WIP PR to allow including own RST files into the auto-generated docs for antsibull-docs: https://github.com/ansible-community/antsibull/pull/255
00:44:13.036,00:44:16.036
Sorin Sbarnea: i think that build-your-own is not what people are asking for.
00:44:18.769,00:44:21.769
Jeff Geerling: the video is like 10 seconds off from audio :D
00:44:42.481,00:44:45.481
Brian Coca: not in general, but some do want to build their own, question is are they enough for it to be worth the effort
00:44:48.688,00:44:51.688
Felix Fontein: It's somewhat basic, but at least it allows to add a lot of extra documents (and to document things like filter/test plugins and roles!)
00:44:53.377,00:44:56.377
Carol Chen: Jeff: is it that bad? maybe I don't see it as the host
00:45:18.461,00:45:21.461
Matt Davis: Yeah, I haven't seen any A/V issues today
00:45:33.001,00:45:36.001
Ben Watson: yeah, a good 10 seconds
00:45:34.932,00:45:37.932
Sviatoslav Sydorenko: Why not both?
00:45:38.040,00:45:41.040
Sorin Sbarnea: zuul-ci defined its own standards based on rst, for documenting roles inside the big zuul-jobs, repo. Yet another DIY solution, because there was no framework for doing it "by-the-book".
00:45:47.764,00:45:50.764
Carol Chen: the chat is a bit slow, but A/V has been working wwell for me
00:45:51.337,00:45:54.337
Deric Crago: hmm... my A/V is pretty in sync
00:46:01.119,00:46:04.119
Sviatoslav Sydorenko: It's possible to use MyST parser along with RST with all of the features of RST
00:46:02.768,00:46:05.768
Brian Coca: mine is off by 0.5s
00:46:38.718,00:46:41.718
Felix Fontein: for me A/V is also out of sync, but I have no clue by how much. It's definitely moret han 0.5 s.
00:46:47.697,00:46:50.697
Sorin Sbarnea: from my point of view I care the most about documenting arguments for roles and modules, with a major problem if the doc is not generated it gets out of sync with implementation.
00:46:51.634,00:46:54.634
Felix Fontein: could be ~10 seconds
00:47:11.469,00:47:14.469
Sviatoslav Sydorenko: markdown allows HTML natively
00:47:23.089,00:47:26.089
Felix Fontein: Sorin: now that we have role argspecs, auto-generating role docs comes closer :)
00:47:24.590,00:47:27.590
Brian Coca: tables = bane of all presentation encodings
00:47:30.169,00:47:33.169
Sorin Sbarnea: in fact sphinx has decent support for md these days.
00:47:48.758,00:47:51.758
Sorin Sbarnea: yep: i am strongly against tables!
00:48:00.410,00:48:03.410
Brian Coca: why we need clones!
00:48:17.822,00:48:20.822
Sorin Sbarnea: tables and narrow displays,....
00:48:19.181,00:48:22.181
Daniel S: From my very personal view: a collection should include the documentation (like manpages for packages). There must be some kind of default format (I dont care whcih format) and possibility to search these. And this search must not be "use google", but something valid. IMHO, this is a must-have in galaxy, since it provides the packages. If I want to know something about a container image at docker.io, I will look it up there and not on docs.docker.com.
00:48:34.785,00:48:37.785
Tadej Borovšak: I was thinking about creating Ansible Sphinx domain, but then I remembered my previous domain-writing experience ...
00:49:01.531,00:49:04.531
Sviatoslav Sydorenko: Tadej: +1
00:49:39.871,00:49:42.871
Jeff Geerling: @Daniel S++
00:49:57.162,00:50:00.162
Jeff Geerling: When I want to find docs for a ruby gem, I don't search ruby's documentation.
00:50:05.362,00:50:08.362
Daniel S: exactly
00:50:19.327,00:50:22.327
Jeff Geerling: even if that gem is used in Ruby on Rails, I don't expect to find docs for that gem in the RoR docs site
00:50:28.243,00:50:31.243
Sorin Sbarnea: whatever we go for: is that I hope there will be an easy way to prevent someone from adding a new var for a role without documenting it. I want to be able to add linter rule for that.
00:50:58.225,00:51:01.225
Brian Coca: to throw another wrench into it, once you have it displayed in galaxy/ah ... do you want it locally via ansible-doc?
00:51:05.962,00:51:08.962
Sviatoslav Sydorenko: It'd be nice if collections could publish their own RTD sites
00:51:08.630,00:51:11.630
Felix Fontein: Sorin: you mean like the version_added sanity test in ansible/ansible, which forces all new options to have the correct version_added string?
00:51:13.429,00:51:16.429
Brian Coca: or you'll download your own chm?
00:51:13.845,00:51:16.845
Jeff Geerling: It's only hard because of the whole "batteries are kinda sorta part of community but sorta not in some ways"
00:51:34.683,00:51:37.683
Jeff Geerling: @bcoca — I don't ever use ansible-doc, I just google it
00:51:42.512,00:51:45.512
Timothy Appnel: that sounds right to me. these collections with these versions.
00:51:42.924,00:51:45.924
Jeff Geerling: easier to read in the browser ;)
00:51:50.473,00:51:53.473
Oleksandr Saprykin: Sviatoslav: +1
00:52:04.151,00:52:07.151
Brian Coca: @jeff i use w3m to google stuff ...
00:52:07.926,00:52:10.926
Brian Coca: why i need to ask
00:52:31.714,00:52:34.714
Timothy Appnel: NO.
00:52:33.613,00:52:36.613
Timothy Appnel: ;)
00:52:58.638,00:53:01.638
Jeff Geerling: I'd be greatly annoyed if I had to do rst for non-plugin docs but that would not be the straw that breaks this camel's back.
00:53:20.726,00:53:23.726
Daniel S: as long as you dont want docx, I am fine.
00:53:26.333,00:53:29.333
Jeff Geerling: (Outside of Python, Markdown feels to me like 99.9% of the world nowadays)
00:53:29.859,00:53:32.859
Carol Chen: Daniel :D
00:53:38.629,00:53:41.629
Felix Fontein: Daniel: PDF-A :D
00:53:39.696,00:53:42.696
Timothy Appnel: Only python people know RST and most Ansible users aren't python people.
00:53:52.086,00:53:55.086
Sorin Sbarnea: tim++
00:53:55.044,00:53:58.044
Brian Scholer: I think that's reasonable to say "if you want it on our docsite, you have to give it to us in a specific format", as it still leaves it open for people to conversion to RST themselves
00:53:59.041,00:54:02.041
Jeff Geerling: It'd be like if a math library person said you gotta write your readme file in latex
00:54:04.917,00:54:07.917
Toshio Kuratomi: <nod> But collection writers are python people.
00:54:09.790,00:54:12.790
Toshio Kuratomi: (as opposed to role writers)
00:54:16.250,00:54:19.250
Sorin Sbarnea: while I know RST, I do see it as a high barrier
00:54:24.715,00:54:27.715
Jeff Geerling: @Toshio - But if collections want to invite role authors to participate...
00:54:30.365,00:54:33.365
Jeff Geerling: one more barrier to entry
00:54:35.360,00:54:38.360
Sorin Sbarnea: some authors are expected not to be python developers.
00:54:41.946,00:54:44.946
Timothy Appnel: toshio! i thought we just said collections are the future for roles.
00:54:52.706,00:54:55.706
Brian Scholer: (I don't want to write stuff directly in RST.. I don't really know it.. but I can't really see demanding a site based on it to accept or convert other formats on my behalf)
00:54:53.446,00:54:56.446
Timothy Appnel: /me smh
00:54:54.970,00:54:57.970
Felix Fontein: you can always use a tool to convert MD to RST. the result may look ugly, but it should work :)
00:55:13.457,00:55:16.457
Toshio Kuratomi: Converting rst to MD should work better.
00:55:22.990,00:55:25.990
Sviatoslav Sydorenko: felix: no need, that can be natively integrated alongside RST
00:55:30.853,00:55:33.853
Brian Coca: https://github.com/chrissimpkins/md2rst
00:55:33.880,00:55:36.880
Timothy Appnel: but you have to write in RST to begin with.
00:55:33.907,00:55:36.907
Sviatoslav Sydorenko: (with all of the features it has)
00:55:35.814,00:55:38.814
Ben Watson: +1 to the PyPi example
00:55:44.897,00:55:47.897
Sviatoslav Sydorenko: @Timothy: no
00:55:51.731,00:55:54.731
Toshio Kuratomi: rst is a richer format to md. So it's okay to lose info sa you go that way. But there's no way to regain the info going the other way.
00:55:56.966,00:55:59.966
David Moreau Simard: "hope is not a strategy" :)
00:56:17.077,00:56:20.077
Oleksandr Saprykin: and sphinx is a very powerful tool to generate docs out of RST
00:56:18.776,00:56:21.776
Sorin Sbarnea: HTML is even richer, but that does not make it better.
00:56:18.838,00:56:21.838
Sviatoslav Sydorenko: @Timothy: http://myst-parser.rtfd.io/ allows to write MD but still use RST features when necessary
00:56:25.022,00:56:28.022
Andrius Benokraitis: so is the current flow ansible-doc->docs.ansible.com->galaxy.ansible.com ?
00:56:42.042,00:56:45.042
Jeff Geerling: strict XML only :D
00:56:48.009,00:56:51.009
Brian Coca: SGML
00:56:52.329,00:56:55.329
Toshio Kuratomi: Tim I thought that roles were going to be pulled and autoformatted?
00:56:54.807,00:56:57.807
Jeff Geerling: assembly
00:56:59.185,00:57:02.185
Toshio Kuratomi: s/pulled/extracted/
00:57:06.982,00:57:09.982
Timothy Appnel: No RTF! Semantic Web baby!
00:57:29.779,00:57:32.779
Sorin Sbarnea: Jeff: I am surprised you did not mention youtube as the ideal docs distribution format.
00:57:44.115,00:57:47.115
Brian Coca: next, which is he sanctioned editor ... vi!
00:57:46.944,00:57:49.944
Sandra McCann: @andrius - afaik ansible-doc has different rendering than docs.ansible.com, which has different rendering than galaxy-hg
00:58:18.293,00:58:21.293
Jeff Geerling: @Sorin lol, way too much work
00:58:20.300,00:58:23.300
Andrius Benokraitis: "there you have it" gif
00:58:20.877,00:58:23.877
Sandra McCann: @andrius - but we are talking beyond the plugin docs to actual user guides per collection
00:58:27.401,00:58:30.401
Andrius Benokraitis: got it
00:58:27.516,00:58:30.516
Brian Coca: @andrius ansible-doc --json can be used to get 'raw data' and reformat for most plugins, question is if we want to extend that to more
00:58:31.784,00:58:34.784
Matt Davis: @Sorin: only redshirt Jeff feels that way ;)
00:58:35.279,00:58:38.279
Toshio Kuratomi: sammcann: yesm that is correct.
00:58:41.506,00:58:44.506
Felix Fontein: The data exported by `ansible-doc --json` (which is pretty much unprocessed documentation from source) is used by both docs.ansible.com and AH I think
00:58:53.798,00:58:56.798
Jeff Geerling: red shirt jeff writes in plain text. no need to mark up anything, just WRITE ALL CAPS
00:58:58.672,00:59:01.672
Andrius Benokraitis: hence why collection_prep is used by the Content Team
00:58:59.449,00:59:02.449
Toshio Kuratomi: amsob;e=dpc ==json is not good.
00:59:05.309,00:59:08.309
Toshio Kuratomi: ansible-doc --json
00:59:10.453,00:59:13.453
Matt Davis: lol
00:59:12.977,00:59:15.977
Toshio Kuratomi: it's not normalized
00:59:14.884,00:59:17.884
Sandra McCann: sorry not sure what you are 'hencing' Andrius
00:59:21.395,00:59:24.395
Sorin Sbarnea: that was my hope that ansible-doc will be able to produce documentation for all consumers.
00:59:27.528,00:59:30.528
Andrius Benokraitis: (brb)
00:59:30.290,00:59:33.290
Alicia Cozine: we also haven't mentioned testing the documentation - historically the docs toolchain has caught a lot of mistakes
00:59:30.827,00:59:33.827
Toshio Kuratomi: (My laptop keyboard broke, so I'm using a full-sized keyboard for the first time in a while)
00:59:35.544,00:59:38.544
Sorin Sbarnea: but this requires us to define an input format.
00:59:51.206,00:59:54.206
Jeff Geerling: "it's a hard problem" is the conclusion
01:00:00.229,01:00:03.229
Jeff Geerling: video is in sync, yay!
01:00:05.031,01:00:08.031
Gundalow Barker: ===============================
01:00:38.655,01:00:41.655
Jeff Geerling: "Nothing too contentious." (Sees kubernetes.core / community.kubernetes) Me: "Heh."
01:00:46.321,01:00:49.321
Brian Coca: /me ducks
01:02:27.135,01:02:30.135
Felix Fontein: finally :)
01:04:05.441,01:04:08.441
Gundalow Barker: Any questions?
01:04:16.004,01:04:19.004
Timothy Appnel: more time to argue RST vs markdown and the merits of semantic versioning! ;p
01:04:24.458,01:04:27.458
Brian Coca: is content team taking over the guides?
01:04:44.481,01:04:47.481
Felix Fontein: Brian: do you mean the scenario guides?
01:05:19.048,01:05:22.048
Sorin Sbarnea: molecule can do that :D
01:06:22.485,01:06:25.485
Brian Coca: @felix guides related to the collections
01:06:25.132,01:06:28.132
Felix Fontein: Moving content is mainly problematic for Ansible 2.9 :)
01:07:22.022,01:07:25.022
Brian Scholer: so glad to hear that, a lot of confusion reporting issues with community modules when the problem lies in module util in the other collection, hard for end users to know that
01:08:19.539,01:08:22.539
Brian Coca: unlike when we had extras/core split, github allows moving issues
01:08:19.877,01:08:22.877
Brian Scholer: yeah that makes sense, duplication does sound worse
01:08:47.394,01:08:50.394
James Cassell (cyberpear): I had to step out for a bit... was community.okd vs redhat.openshift covered?
01:08:49.324,01:08:52.324
Jeff Geerling: I think the solution is to just put all the modules together into ansible/ansible
01:08:52.503,01:08:55.503
Jeff Geerling: hehehe
01:08:55.270,01:08:58.270
Sorin Sbarnea: moving tickets worked fine for molecule when I did the big-split. duplication sounds like nightmare.
01:09:03.909,01:09:06.909
Brian Coca: @jeff we did that!
01:09:05.353,01:09:08.353
Felix Fontein: Jeff: oh, great idea, let';s do that!
01:09:16.824,01:09:19.824
Felix Fontein: what could go wrong?
01:09:21.348,01:09:24.348
James Cassell (cyberpear): usability of playbook/roles written for one being run w/in another
01:09:31.802,01:09:34.802
Brian Coca: @felix we have a good list from last time
01:09:42.996,01:09:45.996
Jeff Geerling: @Jill - The difficulty is that if someone wants to write code / playbooks / examples using those modules, they could not write them in a way that works with Ansible 'for enterprises' and Ansible 'for not having support contract'
01:09:50.718,01:09:53.718
Felix Fontein: Brian: but THIS time it will be 100% different!
01:10:10.660,01:10:13.660
Sorin Sbarnea: lets call the new-one ansible-blob
01:10:24.065,01:10:27.065
Jeff Geerling: /me spies writing any examples for book content... have to add extra notes like "all the module references in this chapter will be different depending on if you have a support contract with Red Hat or not"
01:10:25.520,01:10:28.520
Jeff Geerling: :P
01:10:27.226,01:10:30.226
James Cassell (cyberpear): not fun to re-write every role that uses fqcn for community vs downstream
01:10:35.265,01:10:38.265
Timothy Appnel: Jeff: That's a topic I'd like to see us publish guidance on how to do that more effectively.
01:10:39.138,01:10:42.138
Jeff Geerling: It's always the lawyers
01:10:51.712,01:10:54.712
Rich Megginson: there are redirects for modules/plugins but not for roles . . .
01:11:08.021,01:11:11.021
Rich Megginson: why not add redirect support for roles?
01:11:14.564,01:11:17.564
James Cassell (cyberpear): call it kubernetes.okd to remove "community" name?
01:11:23.146,01:11:26.146
Brian Coca: @rich not impossible
01:11:31.221,01:11:34.221
Jeff Geerling: Famous last words!
01:11:32.051,01:11:35.051
Brian Coca: rename to /dev/null
01:11:57.941,01:12:00.941
Jeff Geerling: next week legal says "you're gonna have to rename community.aws to community.amazon" :D
01:12:22.740,01:12:25.740
Jill Rouleau: That we already had a conversation around, we should be good on AWS
01:12:39.789,01:12:42.789
Daniel S: @jeff: community.amazon®, please
01:12:53.322,01:12:56.322
James Cassell (cyberpear): do we need AMZN permission to call something amazon.aws?
01:12:59.059,01:13:02.059
Felix Fontein: I don't think I'm the only one who doesn't have any background on this legal problem
01:13:04.797,01:13:07.797
Felix Fontein: could someone please explain it a bit in omre detail?
01:13:11.526,01:13:14.526
Matt Davis: nah, just need to come up with a retronym for AWS ;)
01:13:12.086,01:13:15.086
Gundalow Barker: ==========================
01:13:24.024,01:13:27.024
Jill Rouleau: @cyberpear as far as I've been told, no
01:13:26.529,01:13:29.529
Jeff Geerling: community.amazing-web-systems
01:13:34.248,01:13:37.248
Daniel S: :D
01:13:37.490,01:13:40.490
Jeff Geerling: muted!
01:13:41.485,01:13:44.485
Felix Fontein: So the problem is that redhat.openshift has redhat in the name and cannot be used outside AH, or whta?
01:13:50.768,01:13:53.768
Brian Coca: just introduce collection aliases and use random sha1 as 'real namespace'
01:14:01.485,01:14:04.485
Felix Fontein: and community.okd doesn't sound official enough?
01:14:16.862,01:14:19.862
Jill Rouleau: Numerous folks at AMZN/AWS are aware of the collections and the skies have not been darkened with lawyers yet
01:14:45.971,01:14:48.971
Brian Coca: amazon tends not to care about naming, until they copy your product into their services and drive you out
01:15:18.405,01:15:21.405
Jeff Geerling: they kinda tried that with ansible heh
01:15:35.209,01:15:38.209
Brian Coca: they've tried that with everything .. just not all stuck
01:15:54.818,01:15:57.818
Jeff Geerling: @Felix - yeah I think that was the gist of it, apparently nothing in "community galaxy" can have anything with the name "redhat".
01:16:01.044,01:16:04.044
Brian Scholer: is the answer different than when that content was part of the ansible repo?
01:16:15.847,01:16:18.847
Brian Scholer: (it was still "community" supported then right?)
01:16:22.322,01:16:25.322
Sorin Sbarnea: @bcoca now sure if you read the last update on https://github.com/aws/aws-cli/issues/4947#issuecomment-793192340 -- basically they do not care about many things.
01:17:10.966,01:17:13.966
Timothy Appnel: i admit to barely keeping up with what i was getting second hand from the RHT legal. it seems being Red Hat publishing the content is significant and that is why we can have ibm.* and cisco.* etc content upstream and downstream.
01:18:28.280,01:18:31.280
Rick Elrod: What would be done to ensure any "local" (ansible-package patches) get sent back upstream? How do we ensure ansible x.y.z's patch doesn't get lost in ansible x.y.z+1 when the collection releases an update but never got the CVE fix?
01:21:53.698,01:21:56.698
Mark Chappell: What about the collections where modules have different owners? Some modules may be actively maintained others less well maintained...
01:23:03.173,01:23:06.173
Gundalow Barker: @Mark: community.general and community.network are good examples of different activity levels of maintainers
01:23:10.007,01:23:13.007
Daniel S: Are there actually community collections shipped with 3.0.0?
01:23:31.706,01:23:34.706
Felix Fontein: Daniel: you mean new ones?
01:23:52.976,01:23:55.976
Daniel S: yup, aside from builtin, I mean
01:23:56.809,01:23:59.809
Felix Fontein: community.sops is a new community collection that wasn't in Ansible 2.9
01:24:04.920,01:24:07.920
Daniel S: naaa
01:24:29.013,01:24:32.013
Andrius Benokraitis: IMO this is not a technical issue this is more about policy
01:24:32.402,01:24:35.402
Daniel S: If I install ansible (pip install ansible=3.0.0), is there actually a collection included?
01:24:38.036,01:24:41.036
Toshio Kuratomi: as felixfontein said, but I agree :-)
01:24:43.386,01:24:46.386
Brian Coca: well, the policy has many technical implications
01:24:52.635,01:24:55.635
Amin Vakil: bcoca++
01:24:59.716,01:25:02.716
Toshio Kuratomi: danielS yes.
01:25:25.812,01:25:28.812
Sorin Sbarnea: can we afford to maintain patches? i really doubt. We can only remove stuff with CVE. IMHO, including something is a perk, not an obligation.
01:26:20.133,01:26:23.133
Toshio Kuratomi: ssbarnea, yep. LInux distro maintainers essentially have a duplicate set of maintainers for their packages and patches that's in addition to upstreams
01:26:26.904,01:26:29.904
Sorin Sbarnea: the big issue is when the unmaintained collection is used by another 5 other ones. Do we remove a huge part as a side effect?
01:26:39.816,01:26:42.816
Brian Coca: node left trim!
01:26:53.004,01:26:56.004
Andrius Benokraitis: how is this different from 2.9? There is a pile of unmaintained things in there, that are still in there...
01:27:01.368,01:27:04.368
Sorin Sbarnea: I see the cores laughing in the background,.... is not our problem anymore. :D
01:27:03.883,01:27:06.883
Felix Fontein: Sorin: if you depend on a collection, you should make sure it is maintained :)
01:27:05.252,01:27:08.252
Brian Coca: core team ended up being responsible for it
01:27:11.098,01:27:14.098
Tadej Borovšak: I need to run (other meeting coming up). Thank you all!
01:27:11.516,01:27:14.516
Matt Davis: --^ yep
01:27:11.949,01:27:14.949
Andrius Benokraitis: buck passed
01:27:14.269,01:27:17.269
Brian Coca: ^ i've had to fix many unmaintained CVEs
01:27:17.350,01:27:20.350
Rick Elrod: It feels weird to me for us to decide if something is "secure enough" to be on Galaxy. It'd be like GitHub removing a repo because they thought it wasn't secure or written well enough.
01:27:42.352,01:27:45.352
Daniel S: the problem is, github does not actually ship these packages
01:27:47.560,01:27:50.560
Brian Coca: @Rick i dont expect that to be the norm, but if something really extreme appears
01:27:48.019,01:27:51.019
Daniel S: ansible does
01:28:13.972,01:28:16.972
Brian Scholer: have to run to another meeting, will be be back soon
01:28:19.491,01:28:22.491
Rick Elrod: @Daniel I'm just drawing a comparison. It just feels weird to me for us to be in that business.
01:30:10.098,01:30:13.098
Felix Fontein: It might make sense to do additional bugfix releases when (important enough) CVEs show up.
01:31:13.957,01:31:16.957
Felix Fontein: community.general backports bugfixes to older major versions :)
01:31:15.548,01:31:18.548
Daniel S: As I heard of collections the first time some years ago, I assumed, Ansible will itself reduce to some ansible-core + some core functionality. For these, I expected maintenance. For all other collections, be it company.tool or community.scope, I expected that the owner takes over maintenance. It's the same for nodejs packages, ruby gems, chef recipes, docker images, etc. Maintaining code from 3rd party seems completely out of scope for me.
01:32:04.204,01:32:07.204
Brian Coca: and that is true for most, but there is still the 'ansible' community package that includes collections from non upstream
01:32:09.208,01:32:12.208
Sorin Sbarnea: Daniel is right, but there is a catch here: ansible must allow people to alias them.
01:32:11.058,01:32:14.058
Brian Coca: so ansible-core is exactly as you describe
01:32:59.395,01:33:02.395
Brian Coca: some collections are aleardy perfect!
01:33:10.773,01:33:13.773
Daniel S: yep :)
01:33:33.867,01:33:36.867
Daniel S: dont ship them with ansible-package ;)
01:33:38.824,01:33:41.824
Brian Coca: its more a question of collections that ship new versions but no update for previouslly shipoped
01:35:19.976,01:35:22.976
Brian Coca: yes, in the end its up to the community around a collection (mostly the maintainers) to decide on that
01:37:57.473,01:38:00.473
Sviatoslav Sydorenko: $ANSIBLE_COLLECTIONS_PATHS
01:38:47.700,01:38:50.700
Sorin Sbarnea: Are you you you used the correct number of plurals? ;)
01:39:38.940,01:39:41.940
Felix Fontein: I never remember...
01:39:55.838,01:39:58.838
Felix Fontein: I usually start grepping lib/ansible/config/ :)
01:40:27.598,01:40:30.598
Brian Coca: git grep is my friend
01:40:36.656,01:40:39.656
Brian Coca: ansible-config list
01:41:30.485,01:41:33.485
Daniel S: One can live without google, but not without grep? ;)
01:41:44.628,01:41:47.628
Brian Coca: google == distributed grep
01:41:45.259,01:41:48.259
Felix Fontein: grep is one of the most imporant tools
01:41:58.832,01:42:01.832
Felix Fontein: distributed grep with ads :D
01:42:14.923,01:42:17.923
Brian Coca: /me needs to start new 'grep' search engine
01:44:15.222,01:44:18.222
Jeff Geerling: This points to another good reason to include automatic scanning/rating for those standards in galaxy (saves someone from having to verify it all manually)
01:45:09.473,01:45:12.473
Sorin Sbarnea: Jeff, we can use the linter and assure nobody can pass its checks ;)
01:45:24.669,01:45:27.669
Amin Vakil: sorin :)
01:46:02.524,01:46:05.524
Daniel S: sounds like a plan.
01:48:36.942,01:48:39.942
Sorin Sbarnea: We can put old ones on probation, if we we do not have consistent rule, contributors will feel marginalized.
01:59:09.381,01:59:12.381
Brian Coca: kidnapping people at pycon has already been prposed and dismissed
02:00:58.349,02:01:01.349
Gundalow Barker: New collection inclusion review: https://github.com/ansible-collections/ansible-inclusion/discussions/categories/new-collection-reviews
02:01:34.197,02:01:37.197
Gundalow Barker: Summary of checklist: https://github.com/ansible-collections/overview/blob/main/collection_checklist.md
02:01:45.250,02:01:48.250
Gundalow Barker: Full checklist https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst
02:05:19.370,02:05:22.370
Sorin Sbarnea: yeah: good point: ansible own examples do not pass our recommandations.
02:05:28.279,02:05:31.279
Brian Coca: what we really need is 'test profiles' for the diff uses of ansible-test
02:06:05.375,02:06:08.375
Rich Megginson: is there some way that `ansible-test sanity` can differentiate between running against core ansible vs. running to validate a collection for inclusion into galaxy/AH/etc.?
02:06:20.218,02:06:23.218
Brian Coca: not yet, ^ why im talking about profiles
02:06:32.061,02:06:35.061
Brian Coca: you can specifically exclude/include tetsts, but that gets onerous
02:06:48.977,02:06:51.977
Rich Megginson: yes - it definitely gets onerous . . .
02:07:02.933,02:07:05.933
Daniel S: I am not against including more collections. This may be quite convenient for some users.
But... Why do we even want to include more (3rd party) collections in the ansible-package? What is the reason to do this, since everybody can install collections on deman via ansible-galaxy?
02:07:50.118,02:07:53.118
Rich Megginson: I think it is ok to enforce style - as long as it is easy to say "I have my own style - please allow it"
02:09:02.911,02:09:05.911
Sorin Sbarnea: Rich is right, users can override the default settings of the "enforcer" tool.
02:09:10.836,02:09:13.836
David Moreau Simard: By "style" I mean conventions and best practices i.e: https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html
02:10:49.078,02:10:52.078
Sorin Sbarnea: my experience with enabling ansible-test sanity was not ideal, but I did not bother much to challenge its checks.
02:11:13.836,02:11:16.836
Toshio Kuratomi: Daniel S, I'll try to answer that once the ansible-test discussion finishes
02:11:23.442,02:11:26.442
Sorin Sbarnea: the real pain was to run it, not to fix the reported issues.
02:11:24.468,02:11:27.468
Jeff Geerling: it's also something that basically targets / is good for pythonic code in its current state — it provides little value for end-user code (e.g. ansible playbooks / roles) at the current time, especially in comparison to Molecule (IMHO)
02:12:26.750,02:12:29.750
Rich Megginson: @jeff - in what way is molecule better than ansible-test than roles?
02:12:43.837,02:12:46.837
Sorin Sbarnea: for the moment ansible-test should fix the issue where it has different expectations for collection or ansible core.
02:12:48.952,02:12:51.952
Matt Clay: It does not work for collections.
02:12:57.267,02:13:00.267
Jeff Geerling: @rich - it's more aware of the things role authors want to test (e.g. idempotence, isolated environment, check mode tests, dependencies, and a lot more)
02:12:59.217,02:13:02.217
Sorin Sbarnea: aka test vs tests folders... a perfect source of confusions
02:13:31.135,02:13:34.135
Jeff Geerling: and plugs into tons of different backends (not locked into very strictly-defined container environments)
02:14:01.960,02:14:04.960
Jeff Geerling: basically I can write a 10-15 line molecule definition in YAML, or a 25+ line shell script to use ansible-test
02:14:09.896,02:14:12.896
Rich Megginson: @jeff - thanks
02:14:15.337,02:14:18.337
Sorin Sbarnea: I will gladly recommend ansible-test for python code, but if you have roles/playbooks, it does not help.
02:14:25.204,02:14:28.204
Jeff Geerling: ^^ this
02:14:36.117,02:14:39.117
Felix Fontein: I'm using ansible-test for roles as well, also works fine :)
02:14:41.321,02:14:44.321
Jeff Geerling: to be clear, I have gotten ansible-test to work with roles and playbooks
02:14:49.907,02:14:52.907
Jeff Geerling: but it does not do much, and the things it does requires more overhead/setup
02:14:50.361,02:14:53.361
Felix Fontein: (and for me a lot easier to use than molecule, which I would have to learn first)
02:14:58.406,02:15:01.406
Gundalow Barker: The other carrot is we render the module & plugin docs on docs.ansible.com
02:15:16.713,02:15:19.713
Rich Megginson: I would also like to see support for `--podman` in ansible-test sanity, and support for running ansible-test sanity from a `tox` venv
02:15:35.777,02:15:38.777
Brian Coca: PRs welcome!
02:15:48.470,02:15:51.470
Rich Megginson: sure
02:15:54.265,02:15:57.265
Jeff Geerling: I think it's a matter of perspective
02:15:58.066,02:16:01.066
Sorin Sbarnea: Rich: i doubt you will ever see it for older versions of ansible, due to... policy.
02:16:00.632,02:16:03.632
Brian Coca: its not trivial (others have looked into it) since there is no one to one correspondance
02:16:02.743,02:16:05.743
Felix Fontein: Rich: it might already work with the `docker` CLI shim coming (?) with podman
02:16:07.829,02:16:10.829
Jeff Geerling: ansible-test was written by, is maintained by, is improved by 99.9% python-based devs who do python
02:16:09.225,02:16:12.225
Daniel S: @Toshio, @gundalow: I thought so for both.
02:16:12.333,02:16:15.333
Daniel S: thanks a lot
02:16:19.273,02:16:22.273
Matt Davis: Just as a data point- I use podman exclusively with ansible-test, and it works fine except for modules that need httptester
02:16:32.370,02:16:35.370
Sorin Sbarnea: testing tools should be agnostic to ansible version (support a range of versions)
02:16:39.354,02:16:42.354
Rich Megginson: matt++
02:16:41.087,02:16:44.087
Rick Elrod: yeah, what Felix said. ansible-test will work with a docker-like-enough podman that is symlinked to `docker`, in some (most?) cases.
02:16:41.186,02:16:44.186
Felix Fontein: Matt: ah, great to know :)
02:16:48.515,02:16:51.515
Jeff Geerling: molecule is written by / for people who write ansible playbooks / roles / YAML, and are often not at all involved in any Python code
02:17:08.203,02:17:11.203
Rick Elrod: (docker-like-enough depends on podman version)
02:17:08.318,02:17:11.318
Sorin Sbarnea: this will allow us to improve the tools, without being affected by ansible own support policy
02:17:22.746,02:17:25.746
Timothy Appnel: Geerling ++
02:17:24.232,02:17:27.232
Jeff Geerling: anyways, chat aside rant mode off :)
02:17:27.156,02:17:30.156
Matt Davis: There are a couple other little caveats vs docker, but in general, podman + docker shiim works great with ansible-test.
02:17:38.017,02:17:41.017
Jeff Geerling: shiim ooh, that's like a shiny shim
02:17:46.900,02:17:49.900
Matt Davis: lol
02:19:20.759,02:19:23.759
Sorin Sbarnea: Hint: look for tox-ansible, it integrated both molecule and ansible-test, making more human to run them.
02:20:15.518,02:20:18.518
Carol Chen: https://www.eventbrite.com/e/ansible-contributor-summit-202103-registration-141735886853
02:21:45.161,02:21:48.161
Ben Watson: first time lurker here, quite a good experience
02:21:54.006,02:21:57.006
Matt Butch: Guess I missed it but I'd love to help with the Ansible PPA. Will have to rewatch the video.
02:22:01.416,02:22:04.416
Gundalow Barker: Ben Watson Thank you.
02:22:02.189,02:22:05.189
Daniel S: For me, this kind of event can be done for each major release in the future.
02:22:11.530,02:22:14.530
Jeff Geerling: lol
02:22:18.470,02:22:21.470
Timothy Appnel: IRC: not for humans. ;P
02:22:51.079,02:22:54.079
Felix Fontein: At least in IRC, I don't have to wait seconds after typing before my text shows up:D
02:22:53.804,02:22:56.804
Jeff Geerling: lol
02:23:07.446,02:23:10.446
Toshio Kuratomi: Matt Butch, are you on IRC? I can let the person working on that know your irc nick
02:23:19.689,02:23:22.689
Brian Coca: i have a 2015 pr still waiting!
02:23:25.585,02:23:28.585
Deric Crago: Hi Matt Butch - hit me up on IRC @dericcrago
02:23:33.134,02:23:36.134
Matt Butch: Yes I am. Nick is in the hackmd doc
02:23:40.994,02:23:43.994
Jeff Geerling: woah fancy
02:23:55.342,02:23:58.342
Brian Coca: i'll take hoodie!
02:23:56.469,02:23:59.469
Matt Butch: The socks I got for the last one were awesome!
02:23:57.211,02:24:00.211
Anastasios Lisgaras: Yeah!! Very cool!!
02:24:01.104,02:24:04.104
Anastasios Lisgaras: I also want it! ^_^
02:24:06.717,02:24:09.717
Alex Sowitzki: waaaant!
02:24:11.183,02:24:14.183
Anastasios Lisgaras: very nice!!
02:24:15.519,02:24:18.519
James Cammarata: we got more bulls!
02:24:16.045,02:24:19.045
Sorin Sbarnea: a bull or cow?
02:24:16.439,02:24:19.439
Brian Coca: <= is wearing socks right now
02:24:16.921,02:24:19.921
Jeff Geerling: ooh invisi-bulls
02:24:22.937,02:24:25.937
Anastasios Lisgaras: xxax
02:24:23.774,02:24:26.774
Brian Coca: ansi bull
02:24:35.655,02:24:38.655
Brian Coca: though it has gone to the vet ...
02:24:36.554,02:24:39.554
Sorin Sbarnea: if is a bull, we need proof
02:24:45.593,02:24:48.593
Alicia Cozine: it's the antsi-bull
02:25:05.265,02:25:08.265
Rich Megginson: Antsy Bull
02:25:07.923,02:25:10.923
Jacob Evans: haha, thanks for all your hard work everyone
02:25:08.452,02:25:11.452
Jeff Geerling: toshi-bull
02:25:11.600,02:25:14.600
Rich Megginson: don't let it in the china shop
02:25:11.631,02:25:14.631
Felix Fontein: :D
02:25:30.986,02:25:33.986
Brian Coca: cowsay + durham bulls
02:25:33.407,02:25:36.407
James Cammarata: durham is a variety of bull
02:25:37.696,02:25:40.696
James Cammarata: or cow
02:25:43.321,02:25:46.321
Rich Megginson: Bull Durham
02:25:51.555,02:25:54.555
Daniel S: One little question, since I have to drop of. Where can we expect to see the records and material uploads?
02:26:04.576,02:26:07.576
Brian Scholer: hm. I thought it was just an alternative pronunciation of the '-ble' in ansible
02:26:09.267,02:26:12.267
David Moreau Simard: @Daniel on Youtube, eventually
02:26:17.137,02:26:20.137
Jeff Geerling: @Daniel also https://hackmd.io/uZDSLOOdS1Kx0xfZVIATmQ
02:26:25.322,02:26:28.322
Jeff Geerling: looks like it is being updated to link to slides and such
02:26:25.699,02:26:28.699
Felix Fontein: Brian S: me too!
02:26:32.474,02:26:35.474
James Cassell (cyberpear): glad to hear the enders game reference wasn't an accident
02:26:50.788,02:26:53.788
Brian Coca: ansi bull vs asci cowsay, pun has many depths
02:26:54.891,02:26:57.891
Jeff Geerling: fun fact: I read ender's game after discovering Ansible
02:27:04.244,02:27:07.244
James Cassell (cyberpear): likewise
02:27:09.128,02:27:12.128
Brian Scholer: ohhhhh
02:27:10.523,02:27:13.523
Matt Davis: Hit Bull Win Steak
02:27:20.927,02:27:23.927
James Cammarata: ^^^
02:27:25.902,02:27:28.902
Brian Coca: no bull!
02:27:32.386,02:27:35.386
Sorin Sbarnea: jeff: entire trilogy? the other two are even better.
02:27:36.216,02:27:39.216
Rich Megginson: noble
02:27:41.166,02:27:44.166
Toshio Kuratomi: geerlingguy: Have you read the short story?
02:27:41.354,02:27:44.354
Brian Scholer: relevant: my initials 😏
02:27:42.948,02:27:45.948
Rich Megginson: abominable
02:27:46.557,02:27:49.557
Daniel S: Thanks everybody. This was a very very interesting event for me. I would relly love to see this more often and see you over in IRC, twitter and whatnot :)
02:28:04.933,02:28:07.933
James Cassell (cyberpear): recordings from today will be on YouTube?
02:28:08.598,02:28:11.598
Toshio Kuratomi: Daniel S: See you in IRC!
02:28:11.866,02:28:14.866
David Moreau Simard: @James yes, eventually
02:28:15.915,02:28:18.915
Carol Chen: Thanks everyone!
02:28:28.533,02:28:31.533
Rich Megginson: Thanks!
02:28:33.579,02:28:36.579
Anastasios Lisgaras: Thank you everyone!!
02:28:34.371,02:28:37.371
Brian Scholer: bye!
02:28:37.271,02:28:40.271
Andrei Klychkov: thanks all!
02:28:38.903,02:28:41.903
Ben Watson: bye
02:28:39.110,02:28:42.110
James Cammarata: o/
02:28:39.310,02:28:42.310
Cruz Pitre: Thanks!!
02:28:39.970,02:28:42.970
Gundalow Barker: Thanks all
02:28:40.521,02:28:43.521
Matt Butch: Bye bye!
02:28:46.761,02:28:49.761
Amin Vakil: Thanks!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment