search

ansible / community

This repository is being archived. See https://github.com/ansible-community/presentations and https://github.com/ansible-community/meetings for the new locations
Apache License 2.0
489 stars 144 forks source link

The Bullhorn - contribute content for developer newsletter #546

Closed cybette closed 2 years ago

cybette commented 3 years ago

image

The Bullhorn is a Newsletter for the Ansible Developer Community!

New method of reporting news!

We're trying out a new way to report news! If you have anything to share about what you've been up to with Ansible lately, at any time, simply hop into #social:ansible.com (the Ansible Social room on Matrix) and leave a message, tagging newsbot. Your update will then be included in the next edition of the Bullhorn (pending editor approval, of course).

You can find the list of past issues here and join the forum to get notifications on future posts!

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:

cybette commented 3 years ago

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

cybette commented 3 years ago

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

EDITOR: Accepted for issue 7, thanks!

imjoseangel commented 3 years ago

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

cybette commented 3 years ago

@imjoseangel sure, that will be great!

imjoseangel commented 3 years ago

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

bmillemathias commented 3 years ago

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

cybette commented 3 years ago

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?

melcorr commented 3 years ago

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!

bmillemathias commented 3 years ago

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

melcorr commented 3 years ago

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!

felixfontein commented 3 years ago

@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 commented 3 years ago

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

evgeni commented 3 years ago

I couldn't resist writing more ;)

Building and publishing documentation for Ansible Collections

EDITOR: Accepted for issue 7, thanks!

felixfontein commented 3 years ago

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

felixfontein commented 3 years ago

@melcorr thanks for the explanation!

evgeni commented 3 years ago

@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!

gundalow commented 3 years ago

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

samccann commented 3 years ago

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

evgeni commented 3 years ago

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

GregSutcliffe commented 3 years ago

@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."

abadger commented 3 years ago

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

gregdek commented 3 years ago

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!

samccann commented 3 years ago

@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

cybette commented 3 years ago

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

evgeni commented 3 years ago

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

cybette commented 3 years ago

@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.

imjoseangel commented 3 years ago

article on Ansible Collections build automation

I'm almost done with it :stuck_out_tongue_winking_eye:

gundalow commented 3 years ago
felixfontein commented 3 years ago
sshnaidm commented 3 years ago

@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

imjoseangel commented 3 years ago

@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 commented 3 years ago

@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!

imjoseangel commented 3 years ago

@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!

cybette commented 3 years ago

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

cybette commented 3 years ago

@imjoseangel @sshnaidm thanks for contributing content to Bullhorn 8

imjoseangel commented 3 years ago

@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:

Thank you!

melcorr commented 3 years ago

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.

dmsimard commented 3 years ago

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.

samccann commented 3 years ago

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.

acozine commented 3 years ago

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!

goneri commented 3 years ago

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.

cybette commented 3 years ago

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

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

cybette commented 3 years ago

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

sshnaidm commented 3 years ago

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

gundalow commented 3 years ago

Suggestion from 2.10 planning meeting

abadger commented 3 years ago

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.
abadger commented 3 years ago

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.

willthames commented 3 years ago

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

nitzmahone commented 3 years ago

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.

abadger commented 3 years ago

@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.