Community: The Bullhorn - contribute content for developer newsletter

Created on 15 Jul 2020  Â·  135Comments  Â·  Source: ansible/community

image

The Bullhorn is a Newsletter for the Ansible Developer Community!

You can find the list of past issues here.

Subscribe --> here. <--

Currently the Ansible Community Team is editing and putting together the newsletter for release approximately once every 2 weeks. We welcome content contributions and suggestions! And if someone is willing to help out with editing, even better :smile:

Please make your suggestions in comments, and also let us know what you'd like to see more/less of, etc.

:cow: :postal_horn:

news

Most helpful comment

Draft for Bullhorn 16: https://hackmd.io/XCxf16SITcyYSD-5zyzxwA

Please feel free to comment or edit.

@evgeni @dmsimard @abadger @felixfontein @goneri @jillr @tadeboro @gundalow

All 135 comments

The Bullhorn, Issue 7

OUTLINE

Deadline for Content: Friday, July 24
Edit Day: Monday, July 27
Preview Day: Tuesday, July 28
Publication Date: Wednesday, July 29

Community content suggestion by @evgeni on June 15: using Ansible Molecule to test roles in monorepos

EDITOR: Accepted for issue 7, thanks!

Ansible Collections build automation. I'm working on that in my repo. If you want I can work on writing something.

@imjoseangel sure, that will be great!

Cool! I will prepare everything and I will get back to you when ready :)

this is a more global subject, and I don't know if it could be interesting for the target audience, but I'd like an article on the different teams working on Ansible (core, network, doc, ...) and how they work together

this is a more global subject, and I don't know if it could be interesting for the target audience, but I'd like an article on the different teams working on Ansible (core, network, doc, ...) and how they work together

that could be of interest, indeed. @gregdek what do you think?

The Pulp team have just announced Pulp Squeezer - an Ansible collection to manage Pulp. Read more at:

https://pulpproject.org/2020/07/16/pulp-squeezer-0.0.1-available/

EDITOR: accepted for issue 7, thanks!

Seems a good information that worth to be spread but could it be nice to
have some explanation about what is pulp (I never heard until yesterday)
and what does ansible bring to it to provide in the news ?
Do you have a blog post with some asciinema / video to demonstrate so we
can put a link to ?

Best

On Fri, 17 Jul 2020 at 17:35, Melanie Corr notifications@github.com wrote:

The Pulp team have just announced Pulp Squeezer - an Ansible collection to
manage Pulp. Read more at:

https://pulpproject.org/2020/07/16/pulp-squeezer-0.0.1-available/

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ansible/community/issues/546#issuecomment-660174169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAACDA2B5KQ3UBZZEDY3UBDR4BVTVANCNFSM4O2ZOYPQ
.

--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés
[w] https://log.damnpeople.fr

Seems a good information that worth to be spread but could it be nice to have some explanation about what is pulp (I never heard until yesterday) and what does ansible bring to it to provide in the news ? Do you have a blog post with some asciinema / video to demonstrate so we can put a link to ? Best
…

Of course. That makes sense!

Pulp is a platform for managing repositories of software packages and making them available to a large number of consumers. Pulp can locally mirror all or part of a repository, host your own software packages in repositories, and manage many types of content from multiple sources in one place. If you’re an Ansible user who does not want to host your private content on Ansible Galaxy, you can add the Pulp Ansible plugin, mirror the public Ansible content that you require, and use Pulp as an on-premise platform to manage and distribute a scalable blend of public and private Ansible roles and collections across your organization. You can do this also for content types like Debian packages, RPMs, Containers, and Python content - to name but a few. With Pulp Squeezer, you can now manage your Pulp deployment with Ansible modules. For more information, see https://pulpproject.org/

Would this be OK?

Edit: I will try and also get an asciinema!

@melcorr out of curiosity, what's the relation to the pulp_repo module (https://docs.ansible.com/ansible/latest/modules/pulp_repo_module.html)? (Or do they just happen to share a name?)

@melcorr out of curiosity, what's the relation to the pulp_repo module (https://docs.ansible.com/ansible/latest/modules/pulp_repo_module.html)? (Or do they just happen to share a name?)

Hey @felixfontein

From what I can tell, this is a community contribution for an earlier version of Pulp - Pulp 2. The latest release - Pulp 3 - has brought many changes: https://pulpproject.org/about-pulp-3/

So it is the same Pulp, but an earlier release :)

I couldn't resist writing more ;)

Building and publishing documentation for Ansible Collections

EDITOR: Accepted for issue 7, thanks!

@evgeni btw, ansible-community/antsibull#55 is already partially implemented - for the special case that the colletion has been installed locally (or is otherwise made available with the ANSIBLE_COLLECTIONS_PATH env variable).

@melcorr thanks for the explanation!

@felixfontein oh? Can you show me an example? The only thing I could get to work was antsibull-docs current and that took ages on my laptop as it built everything in Ansible.

Edit: ah, using --current! I'll try that. Thanks!

I should have a link to the job spec by Fri/Mon

The Ansible 2.10 docs with collection-level module docs are available for review. Thinking of something like the following for the bullhorn -

Collection module documentation available now on docs.ansible.com for review

After significant months of effort, we have now restored the module-level documentation on docs.ansible.com! This effort required coordination between the Ansible docs team and the community team and developers to pull the module documentation from the collections on Galaxy and publish them on our docsite again. While there's more work to do, we'd like all collection maintainers to take a look at your respective collections and let us know where you see problems:

  1. Go to https://docs.ansible.com/ansible/2.10/collections/index.html
  2. Verify your collection module and plugin documentation looks valid.
  3. See https://github.com/ansible-community/antsibull/issues for a list of known issues and enhancements we are already tracking. Before you open an issue, please drop into the #ansible-docs IRC channel to discuss/troubleshoot any problems you are seeing.

Known issues and Important Caveats

  • The documentation reflect the version of each collection that is in the current Ansible 2.10 Alpha. We will update after each alpha release to pick up whatever collection version is in that release.
  • On 2.10 official release, the documentation will stay fixed at the collection version in that release. We will not be able to update until the next Ansible release (2.10.1 for example).
  • Boolean default is showing 0. This is fixed and will be updated in the docs soon.
  • community.general module docs are not present yet. This should be fixed soon as well.

Thanks to @felixfontein, I was able to use antisbull now, so here is another post: https://www.die-welt.net/2020/07/building-documentation-for-ansible-collections-using-antsibull/

@cybette / @gregdek you probably want to link up both for the "building documentation" topic :)

@cybette @gregdek I promised the community an "explainer blog post" for the bubbleplot in issue 6. I've got that written up now: https://emeraldreverie.org/2020/07/24/faq-on-ansible-community-collections-bubbleplot.en-us/

Happy for that to just go in the general round up of blogs, or you can put it in the body as we have with other stats updates - don't mind either way. Suggested copy (but I really don't mind if you write something entirely different):

"As promised in his [tweet] (https://twitter.com/Gwmngilfen/status/1283682301440937984) Greg Sutcliffe has [gone into more detail] (https://emeraldreverie.org/2020/07/24/faq-on-ansible-community-collections-bubbleplot.en-us/) on what the bubble plot from the last issue represents, and what else we could do with such graphics."

Ansible-2.10.0-alpha4 is now available for testing: https://groups.google.com/forum/#!topic/ansible-devel/psB-lnsPrmY

OK, folks. Draft copy for Issue 7 is on Google docs here:

https://docs.google.com/document/d/1JCc87HeCE40dFm_4N2UcEotou8v7t8Ckp7pvbmLtwnI/edit

We've got a couple of things to fill in, but the edit team should be able to carry to the finish line from here. Thanks for everyone's input!

@gregdek posted the collection docs to ansible-devel email at https://groups.google.com/forum/#!topic/ansible-devel/ugrPk9AG7Co

Edit: modified url to one that's accessible without logging in

The Bullhorn, Issue 8

OUTLINE

NOTE: Delaying one week, new dates follow
Deadline for Content: Friday, August 14
Edit Day: Monday, August 17
Preview Day: Tuesday, August 18
Publication Date: Wednesday, August 19

@cybette would it make sense to have one issue per issue (lol)? otherwise it seems like it gets too crowded over time?

@evgeni there are content and suggestions that did not make it to issue 7 (e.g. article on Ansible Collections build automation, the job opportunity info etc.) and we can keep them for issue 8 or future newsletter issues instead of copying them over to new github issues every time. We can easily hide comments that are outdated or have been resolved (included in newsletter) :)

but yes, we should reset it once a while, maybe every quarter or 6 months. Let's see.

article on Ansible Collections build automation

I'm almost done with it :stuck_out_tongue_winking_eye:

@cybette I'd like to add comments about Ansible Podman modules updates:

Ansible Podman collection has been updated recently with new Podman modules:
podman_volume to manage Podman container volumes on the host, podman_pod and podman_pod_info - for management Podman pods. Podman and Buildah connection plugins now support non-root users connections. All modules and plugins support Podman both versions v1 and v2. A few bugs of idempotency for podman_container module have been fixed.
You can find updated documentation here: https://docs.ansible.com/ansible/2.10/collections/containers/podman/index.html#plugins-in-containers-podman

The Bullhorn, Issue 8

OUTLINE

Deadline for Content: Friday, August 7
Edit Day: Monday, August 10
Preview Day: Tuesday, August 11
Publication Date: Wednesday, August 12

@cybette I'm writing the instructions to publish a Collection to Galaxy using GitHub actions. Can I post to medium and then reference it from the Newsletter?

Thank you!

@cybette I'm writing the instructions to publish a Collection to Galaxy using GitHub actions. Can I post to medium and then reference it from the Newsletter?

Thank you!

@imjoseangel yep we can do that, please share the medium article link here and we'll see about adding it to the Bullhorn. Thanks!

@cybette I'm writing the instructions to publish a Collection to Galaxy using GitHub actions. Can I post to medium and then reference it from the Newsletter?
Thank you!

@imjoseangel yep we can do that, please share the medium article link here and we'll see about adding it to the Bullhorn. Thanks!

Hi, GitHub Actions article publish in Dev.to finallly: https://dev.to/imjoseangel/release-and-deploy-ansible-collection-with-github-actions-4a62

I have used the ansibull as header image. Hopefully you like both the article and the style. Ideas and change requests are welcomed.

Thanks!

The Bullhorn, Issue 9

OUTLINE

Deadline for Content: Friday, August 28
Edit Day: Monday, August 31
Preview Day: Tuesday, September 1
Publication Date: Wednesday, September 2

@imjoseangel @sshnaidm thanks for contributing content to Bullhorn 8

@imjoseangel @sshnaidm thanks for contributing content to Bullhorn 8

Proud to contribute with you guys!!! Let me know if you need extra content:

For instance:

  • Module development
  • Molecule
  • Ansible-Lint on pre-commit and CI

Thank you!

Can we add this for the next edition please:

https://pulpproject.org/2020/08/19/pulp-ansible-0.2.0-is-generally-available/

Let me know if you need anything else.

There was a recent tweet about it but I'd like to gather feedback and use cases for ara through this meta user survey issue: https://github.com/ansible-community/ara/issues/103

It would be a great help if we could include a mention of it :)

In other news, I'm excited about the new features in the upcoming version 1.5 for ara and I will write content for it but I'm not confident it'd be ready in time for the next edition.

We would like to add a reminder for collection owners to provide changelogs to collections included in Ansible 2.10. Something like:
Please update your collections with appropriate changelogs by Monday September 7. See Generating Changelogs for a collection for details on using the Ansible-provided tool. You can also link directly to your own changelogs or release notes by adding the link to an issue at https://github.com/ansible-community/ansible-build-data/ by that same date.

Please also add a note that we're looking for a Technical Writer to join the Ansible documentation team:

Ansible is hiring a technical writer: https://us-redhat.icims.com/jobs/77049/technical-writer/job?hub=7. The job is listed in Raleigh, NC, but we will consider remote applicants. If you're interested or have any questions, reach out on the ansible-docs channel on freenode IRC. We've had a lot of applicants already, so act fast!

vmware.vmware_rest collection 0.1.0 has been released. It's a new VMware collection that is build on top of the vSphere REST API. They modules focus on the guest management and can be mixed with the ones from community.vmware.

Note: a blog post should be publish soon, I will update this comment to add the URL.

@melcorr @dmsimard @samccann @acozine @goneri thanks for your contributions to Bullhorn 9! They have been added.

https://mailchi.mp/redhat/the-bullhorn-9

The Bullhorn, Issue 10

OUTLINE

Deadline for Content: Friday, September 11
Edit Day: Monday, September 14
Preview Day: Tuesday, September 15
Publication Date: Wednesday, September 16

  • Add publication date to newsletter
  • [ ] ALWAYS: Key dates at the top of every Bullhorn (@gundalow)
  • [ ] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Link to Ansible 2.10 release schedule
  • adjustment of ansible-2.10.0 release dates
  • [x] ALWAYS: New/updated Community Collections
  • Ansible Podman collection got a new module podman_network for management of Podman networking.
  • [ ] ALWAYS: Proposals
  • [x] Events
  • Contributor Summit Oct 12 & 15, 2020
  • Open Source Automation Days Oct 19-21, 2020 https://osad-munich.org/en/
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [ ] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • [x] MAYBE: Community content review (@cybette)
  • https://vincent.bernat.ch/en/blog/2020-custom-ansible-module
  • https://willtham.es/2020/09/09/ansible-inventory-diff-github-action.html
  • new features in ARA v1.5?
  • blog post about vmware collection?
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces (@thaumos)
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [ ] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: Red Hat Summit Recap (only if there’s a direct link to good content)

@cybette for Bullhorn:
Ansible Podman collection got a new module podman_network for management of Podman networking.

Suggestion from 2.10 planning meeting

The pre-release dates for ansible-2.10.0 have changed a little. No change to the final release:
https://groups.google.com/forum/#!topic/ansible-devel/618bSHJ7K64

The new dates, which can correspond with having key dates would be:

* 08-Sep-2020: ansible-2.10.0b2
* 15-Sep-2020: ansible-2.10.0rc1 (moved from 10-Sep)

* 17-Sep-2020: IRC meeting where any blockers should be proposed and discussed.
    * Add blockers to the agenda: https://github.com/ansible/community/issues/539
    * If at all possible, if you propose a blocker attend the meeting itself at 18:00UTC in the #ansible-community channel on irc.freenode.net.

* 22-Sep-2020: If no blockers are found, ansible-2.10.0 final will
release as previously scheduled.

ansible-2.10.0b2 went out on time today: https://groups.google.com/forum/#!topic/ansible-devel/93ymbTaUwl4

rc1 should be coming out on the Bullhorn Preview day, September 15th. Not sure how we want to word that. Maybe something like:

The ansible-2.10.0 prereleases continue to be updated for testing purposes. ansible-2.10.0b2 was uploaded to pypi last week: https://groups.google.com/forum/#!topic/ansible-devel/93ymbTaUwl4 and ansible-2.10.0rc1 should be available on pypi by the time you read this.

I wrote a brief blog post about ansible-inventory-diff now being available as a github action

https://willtham.es/2020/09/09/ansible-inventory-diff-github-action.html

Changes to ansible-galaxy login for role/collection publishers

If you use the ansible-galaxy CLI to publish roles or collections to Galaxy, you may care about this. The GitHub API that underlies the ansible-galaxy login command is being removed in November. Without it, users doing role or collection publish operations via the Galaxy CLI will need to find their Galaxy token interactively in a browser and pass it to the CLI with --token (as the ability to generate a token from the CLI will no longer function). We're not sure what people do today or how much this option is used out in the world, so please read and weigh in at https://github.com/ansible/ansible/pull/71628 in the next few days if you have an opinion.

@nitzmahone Note: We might not want to tell people to use --token. Passing secrets over the command line is insecure. If we can point them to putting that into a config file, it would probably be better.

The ansible-2.10.0rc1 release announcement: https://groups.google.com/forum/#!topic/ansible-devel/hgXx7CEugt0

@sshnaidm @gundalow @abadger @willthames @nitzmahone thanks for your contributions to Bullhorn 10! They have been added.

https://mailchi.mp/redhat/the-bullhorn-10

The Bullhorn, Issue 11

OUTLINE

Deadline for Content: Friday, September 25
Edit Day: Monday, September 28
Preview Day: Tuesday, September 29
Publication Date: Wednesday, September 30

  • Add publication date to newsletter
  • [x] ALWAYS: Key dates at the top of every Bullhorn (@gundalow)
  • [ ] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Link to Ansible 2.10 release schedule
  • [x] ALWAYS: New/updated Community Collections
  • Foreman collection 1.3.0 released
  • [ ] ALWAYS: Proposals
  • [x] Events
  • Contributor Summit Oct 12 & 15, 2020
  • Open Source Automation Days Oct 19-21, 2020 https://osad-munich.org/en/
  • [x] [NETDEVOPS Survey 2020](https://github.com/ansible/community/issues/546#issuecomment-699108318)
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [ ] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • [x] MAYBE: Community content review (@cybette)
  • ARA 1.5.0 has been released, blog post
  • z/OS User Management With Ansible
  • blog post about vmware collection?
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [x] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: Red Hat Summit Recap (only if there’s a direct link to good content)

Hi @cybette o/

ara 1.5.0 has been released -- there's a blog post about it here: https://ara.recordsansible.org/blog/2020/09/23/announcing-the-release-of-ara-1.5.0/ and it's been tweeted here: https://twitter.com/RecordsAnsible/status/1308842386450198528

@cybette Stats update for the next issue. Screenshot available if you want it / have space :)


Following productive discussions in recent community meetings (see working group minutes around https://github.com/ansible/community/issues/539#issuecomment-670386710) I've put together an alpha version of a Collections Dashboard. Eventually it will have summary stats across our community, but for now you can query a given collection and get some useful data.

I'll be pre-recording a talk on this for the upcoming Contributor Summit, but for now you can play with it here and the source code (along with the list of collections to index) is here. Please do raise issues & feature requests!

Thanks @GregSutcliffe! I'll ping you early next week when I have the shared doc with draft so you can drop your screenshot there :)

Proposed addition for Volume 11:

NETDEVOPS SURVEY 2020 NOW OPEN!
The NetDevOps Survey 2020 is now live, and looking for respondents! The goal of this survey is to collect information to understand how network operators and engineers are using automation to operate their network today. The survey has been designed to be vendor neutral, collaborative, and community-focused. All network professionals are welcome to participate in the survey, please complete the survey at http://bit.ly/netdevops-survey-2020 by October 23.

@evgeni @dmsimard @GregSutcliffe @abenokraitis thanks for your contributions to Bullhorn 11! They have been added.

https://mailchi.mp/redhat/the-bullhorn-11

community.general 1.2.0 and community.network 1.2.0 have been released today.

The Bullhorn, Issue 12

OUTLINE

Deadline for Content: Friday, October 16
Edit Day: Monday, October 19
Preview Day: Tuesday, October 20
Publication Date: Wednesday, October 21 (skipping a week due to AnsibleFest)

Not sure this is interesting outside the Foreman community, but here is a post how to write Ansible modules for Foreman: https://theforeman.org/2020/10/how-to-write-a-new-foreman-ansible-module-in-20-lines-of-code.html

@cybette Automating CentOS installation using Ansible and Kickstart file in VMware infrastructure - https://medium.com/@AbhijeetKasurde/automating-centos-7-installation-using-ansible-and-kickstart-483807a3774c

@cybette Automating Windows Server 2012 r2 installation using Ansible in VMware infrastructure - https://medium.com/@AbhijeetKasurde/ansible-automating-windows-server-2012-r2-installation-in-vcenter-227577f5917c

@cybette Ansible Podman collection released 1.3.1 version, which include bugfixes and enhancements for podman_container, podman_network, podman_volume and other modules. Finally removed dependency on PyYAML python package from all podman modules, so now the collection doesn't require anything but Podman installed on the host.

Some more collection releases:

  • community.crypto 1.2.0 (fixes CVE-2020-25646)
  • community.mysql 1.1.0
  • cloudscale_ch.cloud 1.2.0

@cybette Ansible Openstack cloud collection released the newest 1.2.0 version. Modules for management of Openstack volumes and snapshots were added: volume_snapshot_info, volume_backup, volume_snapshot_info.

Hey @cybette ,
Foreman community member @Thulium-Drake wrote a blog about how he has used the Foreman Ansible Collection to apply Infrastructure as Code principles to Foreman https://theforeman.org/2020/10/foreman-config-as-code.html

Hi everyone,

Thanks for suggesting content. Here's the draft for Bullhorn 12: https://docs.google.com/document/d/1WVU4eHM9UalWmpONteNg8-cHRTFUPHJvXElrDwfBHqk/edit?usp=sharing

(feel free to edit the document directly)

@sshnaidm I assume you wanted to include volume_backup_info instead of volume_snapshot_info twice!

For lucky number 13:

The Foreman Ansible Collection v1.4.0 was released (Tweet, Toot).

Most notable changes include:

full changelog

I'll probably follow up with a blog post too.

Hi o/

ara 1.5.2 has been released with significant performance improvements.

The Bullhorn, Issue 13

OUTLINE

Deadline for Content: Friday, October 30
Edit Day: Monday, November 2
Preview Day: Tuesday, November 3
Publication Date: Wednesday, November 4

community.sops 0.1.0 has been released. It helps decrpyting and encrypting data with Mozilla sops, which allows to encrypt YAML values (and not keys), and allows to use multiple keys at once and keys from different sources. If you find ansible-vault too constricted for your use-case, this might be better suited for you! (It's a bit harder to use in Ansible though, since there are no vault plugins.)

And here is the Foreman Ansible Collection 1.4.0 blogpost: https://theforeman.org/2020/10/foreman-ansible-modules-v140-released.html

Ansible utilities collection ansible.utils that includes a variety of plugins that aid in the management, manipulation and visibility of data for the Ansible playbook developer. It is currently under active development and the 1.0.0 version will be released in the first week of December 2020. Contribution to the collection in form of PR's/issues are welcomed :-)

Some content will get moved out of community.general and community.network for versions 2.0.0, which will be included in Ansible 2.11. Some of this moving has already been done and initial versions of the new collections have been released. After some testing and once they reach 1.0.0, they will get included in Ansible 2.10.

  1. community.postgresql 0.1.0: contains the postgres_* modules from community.general.
  2. community.routeros 0.1.0: contains the routeros* plugins and modules from community.network.
  3. community.docker 0.1.0: contains the docker* plugins and modules from community.general. Please note that all deprecations planned for removal in community.general 2.0.0 have already been applied. See the changelog for details.

See here for a description of the content move.

Hi everyone,

Thanks for suggesting content. Here's the draft for Bullhorn 13: https://hackmd.io/4NXq-fkFQeybOCwGszLo6w?view

Feel free to edit the document directly (ctrl-alt-e) if you spot any mistakes or if I missed something.

Edit: now published - https://bit.ly/thebullhorn13

The Bullhorn, Issue 14

OUTLINE

Deadline for Content: Friday, November 13
Edit Day: Monday, November 16
Preview Day: Tuesday, November 17
Publication Date: Wednesday, November 18

  • Add publication date to newsletter
  • [x] ALWAYS: Key dates at the top of every Bullhorn (@cybette)
  • PR days Tuesday Dec 1 & Thursday Dec 17 @ 15:00 UTC
  • [ ] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Proposed Schedule for Ansible-2.11
  • [x] ALWAYS: New/updated Community Collections
  • community.postgresql 1.0.0 has been released
  • community.docker 1.0.0 and community.routeros 1.0.0 also have been released
  • [ ] ALWAYS: Proposals
  • [ ] Ansible Contributor Summit Recap (@cybette)
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [x] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • Upcoming changes to the AWX Project
  • [x] Other working group updates
  • doodle for D&I WG meeting https://doodle.com/poll/vz5354kqyhvqvcs5
  • [x] ALWAYS: Community content review (@cybette)
  • Migrating our Ansible roles to a collection by Sebastian Gumprich
  • post about modern Ansible usage by Tadej BorovÅ¡ak
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [ ] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: AnsibleFest Recap (only if there’s a direct link to good content)

I'd like to suggest our blog-post for inclusion into the newsletter. It talks about how we moved our ansible roles (https://github.com/dev-sec/?q=ansible-&type=&language=) into a collection, how we did it and what challenges we faced. Thanks! :)

community.postgresql 1.0.0 has been released!:)

community.docker 1.0.0 and community.routeros 1.0.0 also have been released.

Draft for Bullhorn 14: https://hackmd.io/Y9HqiSfKTvKry3IcHGMOyg

Please feel free to comment or edit.

Edit: now published - https://bit.ly/thebullhorn14

I added a note about community.google and community.kubevirt, there might also be community.hashi_vault but the repo hasn't been created yet.

Should we have someone explain the ansible-base to ansible-core rename ?

Good point @dmsimard

@sivel could you add a short paragraph explaining the name change on hackmd - line 21 in edit mode. Alternatively you can comment here in this issue and I'll add it. Thanks!

I added and will be contained in the next Ansible 2.10 release. to the 1.0.0 announcement for the thee collections named above. (@gundalow yesterday merged the PRs which added the collections to ansible.in.)

@cybette we're not quite ready for public messaging around the name change. I'll make sure that myself or someone from PM reaches back out once we are.

@sivel noted, thanks!

The Bullhorn, Issue 15

OUTLINE

Deadline for Content: Monday, November 30
Edit and preview day: Tuesday, December 1
Publication Date: Wednesday, December 2

Could we please get a mention of community.okd 1.0 in the next release?

I have created my first python based Ansible Collection / modules for the upcoming Veaam RestAPI

https://mycloudrevolution.com/en/2020/11/11/veeam-backup-replication-restapi-ansible-collection/

community.hrobot 1.0.0 has been released and will be included in the next Ansible 2.10 release. It contains the hetzner_* modules from community.general.

community.crypto 1.3.0 has been released. It has new modules for operating on private keys, CSRs and X.509 certificates without having to operate on files.

community.network 1.3.0 has been released. This is the last 1.x.0 minor release, the next releases will be patch releases (if needed). Version 2.0.0 will be released at the end of January 2021 for inclusion in Ansible 3.0.0.

We wrote a blog post that explains why and when one should develop an Ansible collection. It is basically a summary of our decision process and implementation work on the NGINX Unit Ansible Collection that we developed.

https://steampunk.si/blog/why-and-how-of-the-nginx-unit-ansible-collection/

Maybe that could be interesting for the Bullhorn audience?

I wrote an article for VMware Tag management - https://medium.com/@AbhijeetKasurde/ansible-create-a-tag-category-in-vcenter-416a2bc8ca5

A (sort) blog post about the impact of the Python version on Ansible performance (community.kubernetes): https://goneri.lebouder.net/2020/11/26/ansible-performance-impact-of-the-python-version/

Not sure whether this would belong here or not, but we have been doing a cleanup work on the ignore lines for sanity tests in the community.general repository. We have gone from 3608 ignored failures in 1.2.0 down to 1952 ignored lines in 1.3.0, and currently 1547 in main. The top 5 ignored validations being:

    309 validate-modules:parameter-type-not-in-doc
    289 validate-modules:doc-missing-type
    258 validate-modules:parameter-list-no-elements
    161 validate-modules:undocumented-parameter
     90 validate-modules:doc-default-does-not-match-spec

while the top 5 offenders (2-level breakdown) being from:

   238 net_tools/nios
   180 cloud/ovirt
   104 remote_management/oneview
    60 cloud/scaleway
    52 cloud/google

Ansible 2.10.4 has been released :tada:

Announcement: https://groups.google.com/u/1/g/ansible-announce/c/dkCg1TElDZw

Draft for Bullhorn 15: https://hackmd.io/1e3Qs9PHTsCPxcR6x-n3Eg

Please feel free to comment or edit.

@felixfontein @russoz @acozine @dmsimard @gundalow

Edit: now published - https://bit.ly/thebullhorn15

The Bullhorn, Issue 16
(This will be the last issue for 2020! Thanks for your contributions through the year!)

OUTLINE

Deadline for Content: Monday, December 14
Edit and preview day: Tuesday, December 15
Publication Date: Wednesday, December 16

  • Add publication date to newsletter
  • Add link to past issues
  • [x] ALWAYS: Key dates at the top of every Bullhorn (@cybette)
  • PR review day Thursday Dec 17 @ 15:00 UTC
  • Date on which new collections must be reviewed and approved for inclusion in ansible-3.0.0: 2021-01-27
  • [x] [Criteria for accepting new collections for ansible 3.0.0](https://github.com/ansible/community/issues/546#issuecomment-743358625)
  • [ ] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Ansible-3.0.0 Schedule and Preview of 4.0.0 Schedule
  • [x] ALWAYS: New/updated Community Collections
  • Foreman Ansible Collection 1.5.0 was released
  • theforeman.foreman 1.5.1 was released, fixing a bug that got introduced in 1.5.0.
  • community.hrobot 1.1.0 has been released with an inventory plugin.
  • Collection release: sensu.sensu_go 1.7.0 cannot wait to install monitoring on your Amazon Linux and Windows hosts ;)
  • community.hashi_vault?
  • [x] Diversity Working group
  • Diversity WG meetings will begin on 2021/01/07 at 19:00 UTC in IRC channel #ansible-diversity and take place every other week. Submit agenda items at #577.
  • [ ] ALWAYS: Proposals
  • [ ] Ansible Contributor Summit Recap (@cybette)
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [ ] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • [x] ALWAYS: Community content review (@cybette)
  • Ansible: How we prepare the vSphere instances of the VMware CI
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [ ] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: AnsibleFest Recap (only if there’s a direct link to good content)

@cybette would it be possible to add a link to the past issues in the template we send out by email ?

For example in the email we have:
Screenshot from 2020-12-04 11-35-47

But when we click to see in the browser we have:
Screenshot from 2020-12-04 11-36-12

For me right now this links to: https://us19.campaign-archive.com/home/?u=56d874e027110e35dea0e03c1&id=d6635f5420
Screenshot from 2020-12-04 11-37-11

Key date:

  • Date on which new collections must be reviewed and approved for inclusion in ansible-3.0.0: 2021-01-27

    • Please submit your new collections for review as early as possible because we have limited reviewers. Submissions made close to the deadline may not have time to be reviewed and approved in time for inclusion.

Longer announcement:

  • The criteria for accepting new collections for ansible 3.0.0 (releasing in February) have been approved: https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst
  • If you would like your new collection to be in ansible-3.0.0, please try to make your collection conform to the requirements and then submit it as a discussion on https://github.com/ansible-collections/ansible-inclusion/discussions/new

    • When you start the discussion, please include a link to the collection on galaxy, a link to the source code repository, a link to the issue tracker, and the github ids of collection owners that we should contact if there's a problem with the collection later.

    • We will review the new collection requests that have been submitted on a first-come, first-served basis. The earlier you submit your collection, the more likely you are to get into 3.0.0.

    • The review may turn up things that need to be fixed which would delay acceptance.

    • 2021-01-27 is the date by which new collections must be reviewed and accepted so get your collection in as early as possible! Submitting it close to the deadline may mean that there is not enough time for us to review and approve it and then it won't get in.

  • The procedure for getting new collections in is highly likely to change for the 4.0.0 release (including who reviews, whether it remains first-come first-served, and so forth).

community.hrobot 1.1.0 has been released with an inventory plugin.

theforeman.foreman 1.5.1 was released, fixing a bug that got introduced in 1.5.0.

blog post: Ansible: How we prepare the vSphere instances of the VMware CI - https://goneri.lebouder.net/2020/12/14/ansible-how-we-prepare-the-vsphere-instance-for-the-vmware-ci/

Diversity WG meetings will begin on 2021/01/07 at 19:00 UTC in IRC channel #ansible-diversity and take place every other week. Submit agenda items at https://github.com/ansible/community/issues/577.

Collection release: sensu.sensu_go 1.7.0 cannot wait to install monitoring on your Amazon Linux and Windows hosts ;)

Draft for Bullhorn 16: https://hackmd.io/XCxf16SITcyYSD-5zyzxwA

Please feel free to comment or edit.

@evgeni @dmsimard @abadger @felixfontein @goneri @jillr @tadeboro @gundalow

community.mysql 1.1.2 has been released

The Bullhorn, Issue 17
(First Bullhorn issue of 2021... time to create a new GitHub issue?)

OUTLINE

Deadline for Content: Monday, January 4
Edit and preview day: Tuesday, January 5
Publication Date: Wednesday, January 6

  • Add publication date to newsletter + link to past issues
  • [x] ALWAYS: Key dates at the top of every Bullhorn (@cybette)
  • 2021-01-06: community IRC meeting, 19:00 UTC
  • 2021-01-07: D&I working group meeting, 19:00 UTC
  • 2021-01-18: ETA for ansible-base 2.10.5 release
  • Date on which new collections must be reviewed and approved for inclusion in ansible-3.0.0: 2021-01-27
  • [x] [Criteria for accepting new collections for ansible 3.0.0](https://github.com/ansible/community/issues/546#issuecomment-743358625)
  • [ ] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Ansible 2.10.5 release
  • Ansible-3.0.0 release schedule
  • [x] ALWAYS: New/updated Community Collections
  • community.mysql 1.1.2 has been released
  • Big update to Ansible Podman collections 1.4.0 and 1.4.1 releases
  • [ ] ALWAYS: Proposals
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [ ] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • [x] ALWAYS: Community content review (@cybette)
  • ara 1.5.4 has been released: https://twitter.com/RecordsAnsible/status/1341120795691655169
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [ ] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: AnsibleFest Recap (only if there’s a direct link to good content)

Ansible Podman collections had a big update to 1.4.0 and 1.4.1 releases. There were added new modules for login management - podman_logout, podman_login_info. A new module podman_containers allows you to run multiple Podman containers at once, which saves time and performs faster if you need to run multiple containers in a row. Also we added a few network related features like IPv6, MAC addresses, MTU and VLAN configs, etc.

community.hashi_vault version 1.0.0 was released on 2020-12-30
https://github.com/ansible-collections/community.hashi_vault/releases/tag/1.0.0

The hashi_vault lookup plugin will be removed/redirected from community.general:
https://github.com/ansible-collections/community.general/pull/1566
https://github.com/ansible-community/ansible-build-data/pull/47

cc @felixfontein

The redirect will happen for community.general 2.0.0, i.e. for Ansible 3.0.0.

community.docker 1.1.0 has been released with a few new plugins and modules and other new features.

Ansible Openstack collection released 1.2.1 version, where there is a lot of bug fixes and improvements.

community.vmware collection 1.6.0 released with a lot of improvements, fixes and a new module https://galaxy.ansible.com/community/vmware

The Ansible Network Engineering Team is cordially welcoming comments from the Ansible Network community for the following proposal: BGP Global and AF Context Resource Model. The enablement of BGP as network resource modules for supported platforms has long been requested, and is now being scoped and planned for implementing this year. Please provide feedback in the next few weeks!

community.kubevirt 1.0.0 has been released and will be contained in Ansible 2.10.5 (next to the new collections cisco.nso, community.google, and community.hashi_vault). Note that cisco.nso contains modules that will be removed from community.network 2.0.0, the other mentioned collections (community.kubevirt, community.google, community.hashi_vault) contain modules and plugins that will be removed from community.general 2.0.0.

Draft for Bullhorn 17: https://hackmd.io/8jJ5opBuQXSG4lldElqKMg

Please feel free to comment or edit.

@Andersson007 @sshnaidm @dmsimard @briantist @felixfontein @goneri @abenokraitis @gundalow

Edit: now published https://bit.ly/thebullhorn17

The Ansible Content Team is looking for an engineer who has Python programming experience. The location is remote India. Please feel free to reach out to me directly if you are interested.
Job description: https://global-redhat.icims.com/jobs/81956/senior-software-engineer/job.

We had 3 jobs available as technical marketing managers (individual contributors, managing content, not people) at Red Hat that will focus on Red Hat Ansible Automation Platform

Technical Marketing Manager
https://us-redhat.icims.com/jobs/82006/technical-marketing-manager/job?hub=7

Senior Technical Marketing Manager
https://us-redhat.icims.com/jobs/82005/senior-technical-marketing-manager/job?hub=7

Principal Technical Marketing Manager
https://us-redhat.icims.com/jobs/82004/principal-technical-marketing-manager/job?hub=7

Hello, https://github.com/ansible-collections/community.sops collection version 1.0.2 has been released. This is our first 1.x release.

community.postgresql 1.1.0 has been released (bug fixes + new option)

community.mysql 1.2.0 has been released (bug fixes + code refactoring)

The Bullhorn, Issue 18

Deadline for Content: Monday, January 18
Publication Date: Wednesday, January 20

Draft for Bullhorn 18: https://hackmd.io/e3glXvIVRAaPfS6S0H01OA

Please feel free to comment or edit.

@trishnaguha @IPvSean @endorama @Andersson007 @tima @gundalow

Edit: now published https://bit.ly/thebullhorn18

The Bullhorn, Issue 19

Deadline for Content: Tuesday, February 2
Edit + updates from Community meeting: Wednesday, February 3
Publication Date: Thursday, February 4

OUTLINE

  • Add publication date to newsletter + link to past issues
  • [ ] ALWAYS: Key dates at the top of every Bullhorn (@cybette)
  • [x] ALWAYS: Summary of recent IRC meetings (@gundalow)
  • new collection criteria has been added
  • [ ] ALWAYS: Reminder of upcoming IRC meetings (@gundalow)
  • [x] ALWAYS: Releases
  • Ansible-2.10.6 has been released.
  • [x] ALWAYS: New/updated Community Collections
  • community.general, community.network, community.docker, community.crypto
  • [ ] ALWAYS: Proposals
  • [ ] ALWAYS: Reminder of upcoming meetups (@cybette)
  • [ ] ALWAYS: AWX / molecule / ansible-lint / Documentation updates
  • [ ] ALWAYS: Community content review (@cybette)
  • [ ] MAYBE: Tweet of the week (idea via https://github.com/ansible/community/issues/210)
  • [ ] MAYBE: Something about the Molecule project (@gundalow)
  • [ ] MAYBE: an introduction to namespaces
  • [ ] MAYBE: Ansible Community Collection: Open for Business? Call to Action?
  • [ ] MAYBE: Key metric by @GregSutcliffe
  • [ ] LATER: Something about security automation
  • [ ] LATER: An intro to Execution Environments
  • [ ] LATER: AnsibleFest Recap (only if there’s a direct link to good content)

A new collection criteria has been added: Collections are only allowed to use specific directories in the plugins/ directory which correspond to recognized plugin types: https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst#modules-plugins

Ansible-2.10.6 has been released. Important notes:

  • This is the last ansible-2.10.x release. The next version, ansible-3.0.0, is planned for February 16, 2021.
  • This release fixes CVE-2021-20178 and CVE-2021-20180 in the community.general.bitbucket_pipeline_variable and community.general.snmp_facts modules.
  • Full release announcement for this release: https://groups.google.com/g/ansible-announce/c/6_AmfDp2fCw
Was this page helpful?
0 / 5 - 0 ratings

Related issues

mscherer picture mscherer  Â·  6Comments

dagwieers picture dagwieers  Â·  10Comments

nitzmahone picture nitzmahone  Â·  13Comments

dagwieers picture dagwieers  Â·  26Comments

dagwieers picture dagwieers  Â·  26Comments