Ansible VS cloudinit

Ansible-Core ↗

IBM -> RedHat -> Ansible (https://docs.ansible.com/platform.html)

I think the new ansible docs are opaque, and the new "everything is an ansible collection" scheme makes troubleshooting any issues reported by users hundreds of times harder than "the old days"

I keep this (https://github.com/ansible-community/ansible-build-data/blob...) bookmarked because it's the only way to match up what "ansible 8.1.0" (https://pypi.org/project/ansible/8.1.0/) even means since it for damn sure not any of this: https://github.com/ansible/ansible/releases (they used to have a 'release' pinned on that releases tab saying "these are not the droids you are looking for"). I believe I tried asking for them to update the completely erroneous pypi "source code" link to point to that repo and ... well, one can see how well that turned out

On Monday, July 10, 2023, all RST source for Ansible community documentation will move from ansible/docs/docsite to the ansible/ansible-documentation repository. If you want to find out more or have any concerns, come let us know in the docs channel on Matrix.

I created an ansible role for i2pd. Basically, this allows system administrators who want to take part in the I2P network to automate i2pd deployment.

This change will take place on July 10, 2023. As a result, all RST source for Ansible community documentation will move from ansible/docs/docsite to the ansible/ansible-documentation repository. If you have any comments or concerns, please join us in the docs channel on Matrix and give us your feedback.

Other popular DevOps tools include Docker, Jenkins, and Ansible. Docker is a platform that allows developers to package applications and their dependencies into containers that can be easily deployed to any environment. Jenkins is an open-source automation server that enables developers to automate the building, testing, and deployment of software. Ansible is an open-source automation tool that enables developers to automate the configuration and management of IT infrastructure.

This might be a good start: https://github.com/ansible/ansible

We've been around a while, and while automation is clearly central, we have a variety of statements like "a radically simple IT automation system", "Automation for everyone", or "open-source automation that is simple, flexible, and powerful". We called out "fragmentation" in the community strategy, and this is a great example of it in action - we're not being consistent in our message.

Newer versions of OS use cloud init -> https://cloud-init.io/

Yup. There are several options.

https://github.com/vmware-archive/cloud-init-vmware-guestinfo .. looks like it's part of cloud-init now. https://github.com/canonical/cloud-init/pull/953

This indicates that we probably have an upstream issue with the new data source type. Reviewing the change log we see several fixes applied to this data source.

Cloud-Init is a standardized way to configure your Images without having to write shell scripts. It is a set of YAML files that tells the image what needs to be done on the first-boot of the OS. We will use Cloud-Init to create the following:

"It's a standardized configuration file where you can tell a supported OS how to set up the system on first boot. So things like hostname, packages, logins, ssh keys can be automatically applied and you don't have to go through a manual install process. " https://cloud-init.io/

Before starting to cover anything in this section, all options require uploading a new image at some point. Let's first get this ready with ready-made images from popular distributions. OpenStack provides a list of popular options that can be supported. A big consideration for future automation is the inclusion of cloud-init in the base package. There's ways to do this automatically (via DevStack's local.conf file) when we first set up our instance.