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)
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 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)
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)
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)
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)
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)
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)
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)
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)
