overview VS Ansible

As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).

cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.

The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.

The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.

We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!

How? Copy the Review checklist into a discussion and go through it. See the complete example.

We've recently signed off on that process, which you can review here.

Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.

Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)

We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details

Ansible is an open-source IT automation tool that simplifies application deployment, cloud provisioning, and configuration management across diverse environments. It uses a declarative language to describe the desired state of the system, and then takes the necessary actions to achieve that state. Ansible has become incredibly popular due to its simplicity, agentless architecture, and extensive community support. Document: ansible.com, ansible basics

Ansible v2.16

Ansible is a tool used to help manage software automation processes, configuration management across machines, deployment as well as remote execution of commands and scripts. In sports, Ansible operates as the coach of your team by providing strategies (playbooks), and actions, and ensuring the smooth execution of tasks across your infrastructure, just like a coach guides and directs players (Servers)during a game.

They support for-if from python, too: https://jinja.palletsprojects.com/en/3.1.x/templates/#loop-f... but I haven't tried the "recursive" keyword to know if ansible supports that. I say "ansible supports that" because they don't just drop jinja2 into ansible and call it a draw, they have a bunch of custom execution integrations: https://github.com/ansible/ansible/blob/v2.16.3/lib/ansible/...

To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck

In this article's context, it is simply a tool that provides a declarative way to automate your machine/OS to configure the development machine as you want (install package, modify the configuration, etc). Examples of these tools are Ansible, Puppet, etc.

Now we're getting more tangential, but for years, Ansible releases were named for Van Halen songs (see old Changelog here: https://github.com/ansible/ansible/blob/v1.8.4/CHANGELOG.md)

In the lab to follow, we'll quickly provision a 3-node kubeadm cluster (1 master, 2 workers) on the cloud provider of your choice using an automation stack comprised of OpenTofu and Ansible, then deploy Rook Ceph using the official Helm charts and confirm that we are now able to successfully create CSI volume snapshots from PVCs by reusing the MinIO example from our last article.