#ansible-community: Ansible Contrib Summit 2020 - main stream @ https://bluejeans.com/228187643
Meeting started by gundalow at 10:50:33 UTC
(full logs).
Meeting summary
-
- Join via Bluejeans
https://bluejeans.com/228187643 (cybette,
10:52:12)
- Welcome and intros (gundalow, 11:06:16)
- Welcome to the 8th Ansible Contributors
Summit (gundalow,
11:07:55)
- We know the world has become a bit crazy
recently, we really appreciate you taking the time to join us today,
which is a real testament to the Ansible Community (gundalow,
11:08:44)
- We are now going round the virtual room doing
introductions and 1) saying who we are Real & GitHub/IRC names
2) What our interest in Ansible is 3) What we'd like to get from
today (gundalow,
11:09:58)
- Contributor summit attendance + info for
swag: https://forms.gle/Uv9Zdaz7aTAAwtsQ8 (cybette,
11:31:44)
- Collection Overview (gregdek, 11:35:22)
- Ansible was a single repo, but Ansible module
growth has made a single repo less sustainable over time
(gregdek,
11:36:40)
- Collections What/why/how overview
https://github.com/ansible-collections/overview/blob/master/README.rst#where-we-ve-come-from-and-where-we-are-going
(gundalow,
11:37:17)
- Collections user guide:
https://docs.ansible.com/ansible/latest/user_guide/collections_using.html
(gundalow,
11:37:56)
- Collections development guide:
https://docs.ansible.com/ansible/latest/dev_guide/developing_collections.html
(gundalow,
11:38:09)
- collections allow developers to move at their
own speed, but users just want a simple way to consume content
without worrying about collection release cycles (gregdek,
11:38:37)
- with collections, there is no longer a single
global namespace for modules, now each collection has its own
namespace (gregdek,
11:40:10)
- Fully Qualified Collection Name (FQCN) = The
full definition of a module, plugin, or role hosted within a
collection, in the form namespace.collection.content_name. For
example `ansible.windows.win_command` (gundalow,
11:41:06)
- See
https://github.com/ansible-collections/overview/blob/master/README.rst#terminology
for a full list of Collection Terminology
https://github.com/ansible-collections/overview/blob/master/README.rst#terminology
(gundalow,
11:41:32)
- `ansible/ansible:devel` is now `ansible-base`
(ie without most modules) (gundalow,
11:44:41)
- With collections, we will introduce the idea of
"execution environments", which are container-based virtual
environments using ansible-base + ansible-runner + particular
collection requirements, and that's what awx/tower will use to run
content in the future (gregdek,
11:47:06)
- Execution environments allow for different
environments for different users/use cases (gregdek,
11:47:27)
- Docs on the existing Ansible Tower and
collections (not including "execution Environments")
https://docs.ansible.com/ansible-tower/latest/html/userguide/projects.html#collections-support
(gundalow,
11:47:51)
- q: with having namespaces, module names might
not be unique different collection might have the same name. In a
play we could define all namespaces, what would haben if you add 2
namespaces with a module named identically? (gundalow,
11:49:04)
- module and plugins operate a first found. You
can always use the FQCN (Fully Qualified Collection Name) ie rather
than just using `ping` you could use `cisco.ios.ping` or
`ansible.windows.ping` (gundalow,
11:50:30)
- Molecule (gundalow, 11:53:34)
- zbr (The Molecule Maintainer) is doing a short
presentation on Molecule (gundalow,
11:54:39)
- https://sbarnea.com/slides/molecule/#/
(gregdek,
11:54:56)
- Molecule project is designed to aid in the
development and testing of Ansible roles. Molecule provides support
for testing with multiple instances, operating systems and
distributions, virtualization providers, test frameworks and testing
scenarios. (gundalow,
11:55:22)
- Molecule documentation
https://molecule.readthedocs.io/en/latest/ (gundalow,
11:55:34)
- Slides which zbr is going through
https://sbarnea.com/slides/molecule/#/ (gundalow,
11:56:22)
- If you are interested in Molecule feel free to
join #ansible-molecule on IRC (gundalow,
11:56:41)
- Molecule has many drivers they can be found at
https://github.com/ansible-community?q=molec&type=&language=
(gundalow,
11:58:56)
- We are looking for people to help with
Molecule, and especially the drivers (above URL) (gundalow,
11:59:22)
- Q: Can anyone create drivers A: Yes, only needs
the Python entry point. If you think the driver maybe useful for
others please ask in #ansible-molecule and we can host it (and
provide CI) along side the existing drivers in
https://github.com/ansible-community?q=molec&type=&language=
(gundalow,
12:16:16)
- Community Data (gundalow, 12:21:55)
- gwmngilfen is now presenting how the Community
Team uses data to make decisions (gundalow,
12:23:07)
- https://stats.eng.ansible.com/apps/meetups/
then click on `meetup maps` (gundalow,
12:26:31)
- https://stats.eng.ansible.com/apps/
(gregdek,
12:26:39)
- https://www.stackalytics.com/
(dmellado,
12:33:25)
- ACTION: gundalow to
add community.network to Collection stats (gundalow,
12:35:13)
- ACTION: ikhan to
privide gwmngilfen with lists of other repos to add to
https://stats.eng.ansible.com/apps/collections/contributors/
(gundalow,
12:35:34)
- git tag `pre-ansible-base` in ansible/ansible
is the commit before most of the modules got `git rm`'ed
(gundalow,
12:44:38)
- 15m break, back @ 14:10 UTC (nitzmahone, 12:55:30)
- https://stats.eng.ansible.com/apps/collections/contributors/
is the url for the contributor stuff, if anyone missed it
above (gwmngilfen,
13:03:49)
- Intros part 2 (gundalow, 13:12:23)
- Just doing another round of intros for people
that have joined the call since we started earlier (gundalow,
13:12:47)
- ansible-lint (gundalow, 13:19:46)
- zbr is giving an presentation on
ansible-lint (gundalow,
13:20:08)
- ansible-lint docs:
https://docs.ansible.com/ansible-lint/ (gundalow,
13:25:06)
- ansible-lint repo:
https://github.com/ansible/ansible-lint (gundalow,
13:25:25)
- Collections: User Experience (gundalow, 13:41:28)
- nitzmahone is now explaining about how we ended
up with `ansible-base` (gundalow,
13:41:52)
- Definition of ansible-base
https://github.com/ansible-collections/overview/blob/master/README.rst#q-what-exactly-is-ansible-base-for-and-what-does-it-contain
(gundalow,
13:44:15)
- https://github.com/ansible-community/molecule/pull/2620/files
(zbr,
13:52:07)
- https://github.com/ansible-collections/overview/blob/master/README.rst#terminology
(gundalow,
13:54:33)
- ACTION: DOCS: "if i
used to x to install ansible and do y with it, now i should do z"
(install everything; use everything and one new collection; Use a
new module in a collection; I don't care about collections I just
want to do my day job) (gundalow,
14:18:47)
- ACTION: DOCS: Need
some diagrams (gundalow,
14:19:00)
- ACTION: gundalow to
tidyup Collections content migration & ACD (gundalow,
14:27:42)
- AGREED: ansible-galaxy cli needs a clear mechanism to install
collections via source if the provider makes the source
available (gregdek,
14:31:27)
- ACTION: extend
user-facing documentation of how to install collections (include
options beyond ACD) (acozine,
14:33:14)
- ACTION: belfast77 /
nitzmahone to connect with product management around downstream
packaging needs (nitzmahone,
14:34:04)
- ACTION: overhaul
https://docs.ansible.com/ansible/devel/community/maintainers.html to
be a Collection Maintainers page (acozine,
14:34:27)
- AGREED: collections
changelogs can use any solution maintainers prefer, however, we will
develop a procedure for amalgamating them based on one
solution (acozine,
14:36:16)
- Collections: Development and Contributor (gundalow, 14:37:14)
- webknjaz is now explaining how the migration
happened from a technical perspective (gundalow,
14:37:50)
- 15 minute break (gundalow, 14:46:08)
- related issue regarding collection installation
https://github.com/ansible/ansible/issues/61680 (shertel,
15:01:11)
- new join intros (nitzmahone, 15:03:52)
- Collections development status (gundalow, 15:05:45)
- Collection Status
https://github.com/ansible-collections/overview/blob/master/status.rst
(gundalow,
15:08:14)
- ACTION: gundalow
status.rst update aws repo names (gundalow,
15:09:43)
- Most Collections can be found at
https://github.com/ansible-collections/ (gundalow,
15:13:47)
- https://github.com/ansible-collections/grafana/blob/master/galaxy.yml
(gundalow,
15:14:12)
- ACTION: gwmngilfen to
work on tracking which parts of community.general are getting
large (gwmngilfen,
15:17:43)
- https://www.ansible.com/logos
- > Community vs Red Hat logos (cybette,
15:19:36)
- routing/redirection in 2.10 (nitzmahone, 15:21:46)
- https://github.com/ansible/ansible/pull/67684
(nitzmahone,
15:21:48)
- nitzmahone is now talking about how 2.9
playbooks will still work out of the box when people install Ansible
2.10 (gundalow,
15:22:47)
- Collection docs (gundalow, 15:33:37)
- acozine is now talking about how Collection
documentation will be generated (gundalow,
15:34:06)
- 2.9 module index
https://docs.ansible.com/ansible/latest/modules/modules_by_category.html
<- Based on the directory structure under `lib/ansible/modules/`
(before modules were deleted) (gundalow,
15:35:16)
- 2.9 Module URL
https://docs.ansible.com/ansible/latest/modules/dnsimple_module.html
(gundalow,
15:35:52)
- Example Collection doc
http://docs.testing.ansible.com/collections/purestorage.flasharray/purefa_user_module.html
(gundalow,
15:39:59)
- Collection level (plugin index)
http://docs.testing.ansible.com/collections/purestorage.flasharray/index.html#plugins-in-purestorage-flasharray
(gundalow,
15:42:17)
- ACTION: DOCS: Table
showing old and new URLs (gundalow,
15:42:29)
- 2.9 Porting Guides
https://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html
(gundalow,
15:50:45)
- ACTION: Document
(best case separate tool chain) that allows people to build module
docs outside of Ansible. Or perhaps Collection Explorer. Link to
this from dev_guide.
https://opendev.org/openstack/tripleo-ansible/src/branch/master/doc/source/_exts/ansible-autodoc.py
https://docs.openstack.org/tripleo-ansible/latest/
https://github.com/ansible-community/collection-explorer
(gundalow,
15:54:06)
- There is a tool that allows you to view locally
installed Collection documentation
https://github.com/ansible-community/collection-explorer
(gundalow,
15:54:32)
- https://sensu.github.io/sensu-go-ansible/
(tadeboro,
15:55:01)
- ACTION: gundalow
Summit (and hackathon) writeup to Reddit (gundalow,
15:58:17)
- 15 minute break (gundalow, 16:01:22)
- 15min break, back at 16:15UTC (nitzmahone, 16:01:53)
- ACD (nitzmahone, 16:17:53)
- ACD (the ansible package) bulid process (gundalow, 16:18:06)
- https://toshio.fedorapeople.org/ansible/acd/ansible-2.10-file-layout.png
(abadger1999,
16:18:50)
- abadger1999 is now talking about how the new
`ansible` package will be built (gundalow,
16:19:30)
- https://toshio.fedorapeople.org/ansible/acd/ansible-2.10-file-layout.png
shows what `ansible` package will look like on disk (gundalow,
16:19:47)
- ACTION: DOCS: "How do
I X" what happens if ansible.posix exists in 2 different
directories? (gundalow,
16:22:15)
- https://gist.github.com/abadger/1f14caded92117fbd3036842c875701c
(abadger1999,
16:23:31)
- possible ACD Build process
https://gist.github.com/abadger/1f14caded92117fbd3036842c875701c
(gundalow,
16:25:21)
- https://github.com/abadger/misc-work/tree/master/ansible/build_acd
(abadger1999,
16:31:50)
- ACD build scripts (work in progress)
https://github.com/abadger/misc-work/tree/master/ansible/build_acd
(gundalow,
16:32:27)
- ACD parse_args (gundalow,
16:33:14)
- https://toshio.fedorapeople.org/ansible/acd/acd.in
(abadger1999,
16:33:23)
- https://toshio.fedorapeople.org/ansible/acd/acd-2.10.build
(abadger1999,
16:34:27)
- https://toshio.fedorapeople.org/ansible/acd/acd-2.10.0.deps
(abadger1999,
16:37:37)
- https://toshio.fedorapeople.org/ansible/acd/
(abadger1999,
16:38:42)
- ACTION: ACD Testing:
testing would be required because without it, someone would break
the acd with their own reqs (gundalow,
16:48:10)
- Cloud Collections (gundalow, 16:53:24)
- jillr now explains how the different Cloud
Collections are setup (gundalow,
16:55:16)
- Ansible Cloud Team: AWS, VMware (gundalow,
16:55:36)
- https://github.com/openstack/ansible-collections-openstack
(sshnaidm,
16:59:17)
- Release notes & Changelog fragments
https://github.com/ansible-collections/overview/issues/18
(gundalow,
16:59:46)
- ACTION: jillr check
where inventory scripts (not plugins) are (gundalow,
17:04:04)
- ACTION: DOCS: search
for `contrib` as that directory no longer exist (gundalow,
17:05:56)
- ACTION: DOCS: search
for `contrib/inventory` in docs to point people to the new
individual repos (and new directory structure) (gundalow,
17:07:09)
- Community Process for Collections (gundalow, 17:09:38)
- https://github.com/ansible-collections/community.general/tree/master/plugins/modules/cloud/misc/
(felixfontein,
17:10:24)
- Contributor Collection status
https://github.com/ansible-collections/overview/blob/master/status.rst
(gundalow,
17:10:25)
- Survey link:
https://forms.gle/Uv9Zdaz7aTAAwtsQ8 (cybette,
17:18:13)
Meeting ended at 17:20:12 UTC
(full logs).
Action items
- gundalow to add community.network to Collection stats
- ikhan to privide gwmngilfen with lists of other repos to add to https://stats.eng.ansible.com/apps/collections/contributors/
- DOCS: "if i used to x to install ansible and do y with it, now i should do z" (install everything; use everything and one new collection; Use a new module in a collection; I don't care about collections I just want to do my day job)
- DOCS: Need some diagrams
- gundalow to tidyup Collections content migration & ACD
- extend user-facing documentation of how to install collections (include options beyond ACD)
- belfast77 / nitzmahone to connect with product management around downstream packaging needs
- overhaul https://docs.ansible.com/ansible/devel/community/maintainers.html to be a Collection Maintainers page
- gundalow status.rst update aws repo names
- gwmngilfen to work on tracking which parts of community.general are getting large
- DOCS: Table showing old and new URLs
- Document (best case separate tool chain) that allows people to build module docs outside of Ansible. Or perhaps Collection Explorer. Link to this from dev_guide. https://opendev.org/openstack/tripleo-ansible/src/branch/master/doc/source/_exts/ansible-autodoc.py https://docs.openstack.org/tripleo-ansible/latest/ https://github.com/ansible-community/collection-explorer
- gundalow Summit (and hackathon) writeup to Reddit
- DOCS: "How do I X" what happens if ansible.posix exists in 2 different directories?
- ACD Testing: testing would be required because without it, someone would break the acd with their own reqs
- jillr check where inventory scripts (not plugins) are
- DOCS: search for `contrib` as that directory no longer exist
- DOCS: search for `contrib/inventory` in docs to point people to the new individual repos (and new directory structure)
Action items, by person
- belfast77
- belfast77 / nitzmahone to connect with product management around downstream packaging needs
- gundalow
- gundalow to add community.network to Collection stats
- gundalow to tidyup Collections content migration & ACD
- gundalow status.rst update aws repo names
- gundalow Summit (and hackathon) writeup to Reddit
- gwmngilfen
- ikhan to privide gwmngilfen with lists of other repos to add to https://stats.eng.ansible.com/apps/collections/contributors/
- gwmngilfen to work on tracking which parts of community.general are getting large
- ikhan
- ikhan to privide gwmngilfen with lists of other repos to add to https://stats.eng.ansible.com/apps/collections/contributors/
- jillr
- jillr check where inventory scripts (not plugins) are
- nitzmahone
- belfast77 / nitzmahone to connect with product management around downstream packaging needs
- UNASSIGNED
- DOCS: "if i used to x to install ansible and do y with it, now i should do z" (install everything; use everything and one new collection; Use a new module in a collection; I don't care about collections I just want to do my day job)
- DOCS: Need some diagrams
- extend user-facing documentation of how to install collections (include options beyond ACD)
- overhaul https://docs.ansible.com/ansible/devel/community/maintainers.html to be a Collection Maintainers page
- DOCS: Table showing old and new URLs
- Document (best case separate tool chain) that allows people to build module docs outside of Ansible. Or perhaps Collection Explorer. Link to this from dev_guide. https://opendev.org/openstack/tripleo-ansible/src/branch/master/doc/source/_exts/ansible-autodoc.py https://docs.openstack.org/tripleo-ansible/latest/ https://github.com/ansible-community/collection-explorer
- DOCS: "How do I X" what happens if ansible.posix exists in 2 different directories?
- ACD Testing: testing would be required because without it, someone would break the acd with their own reqs
- DOCS: search for `contrib` as that directory no longer exist
- DOCS: search for `contrib/inventory` in docs to point people to the new individual repos (and new directory structure)
People present (lines said)
- gundalow (155)
- gregdek (73)
- felixfontein (68)
- nitzmahone (53)
- abadger1999 (44)
- zbr (40)
- jpmens (39)
- sshnaidm (36)
- gwmngilfen (36)
- resmo (28)
- jtanner (28)
- shaps (27)
- cybette (26)
- rrey (23)
- acozine (23)
- odyssey4me (22)
- dmellado (21)
- madonius (20)
- fobhep (19)
- tadeboro (16)
- belfast77 (15)
- jimi|ansible (14)
- rbergeron (14)
- TKersten (13)
- zodbot (11)
- webknjaz (10)
- jillr (7)
- ikhan (6)
- digigrate_ (5)
- mohitmkspy (5)
- agaffney (3)
- leogallego (3)
- misc (3)
- mattclay (2)
- sshnaidm|off (1)
- jhawkesworth (1)
- shertel (1)
- Goneri (1)
- Pilou (0)
- digigrate (0)
- ganeshrn (0)
- phips (0)
Generated by MeetBot 0.1.4.