#### Future of the ansible package ##### John Barker, Community Engineering Manager, @gundalow ##### Andrei Klychov, Senior Engineer, @andersson007_ --- ## Discussion * We **need** your feedback * Realtime * Matrix `#summit:ansible.com` * https://matrix.to/#/#summit:ansible.com * IRC Libera.Chat `#ansible-conf` * [community-topics#82](htps://github.com/ansible-community/community-topics/issues/82) * [Reddit topic](https://www.reddit.com/r/ansible/comments/tjfbqx/future_of_ansible_package/) --- ## History * Previously * `Ansible <=2.9` one package including all modules * One repo * Now * `ansible-core` main program and few modules * New `ansible` package exists to allow seamless upgrade * Many collection repos --- ## Proposals * Keep the process as-is * continue to include new collections as we do * New collections are not allowed to get in * with possible future deprecation of the package * Keep the possibility to get a collection included but "narrow the door" * ie introducing new requirements (for example, to be generic) --- ## Summary of feedback so far, 1 Some of mentioned pros of keeping things as-is: * Batteries included is more friendly - especially to new users * Motivation to create new collections which can become a part of Ansible package * Motivation to create content satisfying the collection requirements * "more collections = more maintainers" to expand the SC" * ansible-core + manually installed collections and the ansible package are not mutually exclusive; they serve the different needs of our users --- ## Summary of feedback so far, 2 A few interesting things mentioned on Reddit: * fox_inti said that > for me the biggest PRO of ansible package is what we list under CONS, the fact that the Steering committee spends a lot of time to review collections, to discuss what to do with unmaintained collections; package maintenance burden. > Without the ansible package, he said, every ansible user has to do this... * Important for airgaped installs --- ## Inclusion process To get into the package, a collection [submitted](https://github.com/ansible-collections/ansible-inclusion/discussions/categories/new-collection-reviews) for inclusion: 1. has to satisfy the [collection requirements](https://github.com/ansible-collections/overview) 2. is reviewed and approved by two [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) members The inclusion process: * is pretty time consuming * usually requires several rounds of review * lack of volunteers * special thanks to **felixfontein** and **tadeboro** who reviewed most of newly included collections --- ## Concerns - More collection = increased install time - Fixed by shipping Python Wheels - exclude unneeded files (ie tests) from package - Remove deprecated collections - Time to review inclusion requests - Expand Steering Committee - Can we automte parts of checklist? --- ## Call to action * Help with [inclusion reviews](https://github.com/ansible-collections/ansible-inclusion/discussions/categories/new-collection-reviews) * How can we improve (clarify) the [requirements](https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst)? * How can we imporve the [inclusion workflow](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html#collection-inclusion-requests-workflow)? * How can we automate [checks](https://github.com/ansible-collections/overview/blob/main/collection_checklist.md)? Create issues in the corresponding repositories if you need help --- ## Thanks! [@gundalow:ansible.im](matrix:u/gundalow:ansible.im) \-- [#space:ansible.com](matrix:r/#space:ansible.com) (Find me in [#social:ansible.com](matrix:r/#social:ansible.com)!) \-- Discussion [community-topics#82](htps://github.com/ansible-community/community-topics/issues/82) \-- [These slides](https://hackmd.io/rVxRji9vS2Ks_DD2kB2cIg)