docsite VS Ansible

Before we add the redirect we'd like to get your feedback. Please leave a comment on the pull request or head over to the docs channel on Matrix and let us know your thoughts.

Hopefully you've noticed that the "docs.ansible.com" landing page has a different navigation. We've updated it to focus on user journeys so users can find support from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see any content gaps? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us keep building better content journeys for the community.

We've just refreshed the layout on docs.ansible.com to include quick and easy links for most visited doc pages. You can find the new "Quicklinks" section on the index, user, developer, and maintainer pages. We want to hear from you, especially if you have a killer suggestion for a quicklink, so open an issue in the ansible/docsite repo.

You might have noticed that "docs.ansible.com" has a different layout. That's because we've revamped it to focus on user journeys so that users find what they need from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see anything missing from the new docsite? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us make it even better.

Come join us and help build a new docsite! The community team has been working to update the Ansible documentation landing page based on a set of user journeys. Right now we're working on a prototype docsite to improve the navigation and user experience.

The community engineering team has put together a first set of user journeys for Ansible docsite personas and would like your feedback. You can find the user journeys in GitHub.

The ansible/docsite repo is now public, giving the Ansible community full access to all the html and navigation assets that go into docs.ansible.com. Fork the repo and start hacking.

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.