foreman VS Ansible

I was confused because there is https://github.com/ddollar/foreman and https://github.com/theforeman/foreman

In case you're unable to use intune, a free approach might be https://theforeman.org/ That works well for provisioning baremetal windows (with discovery image or pxe boot) once you've set it up. It supports script access as well as a nice hierarchy for configurations. But it's really not as well documented as it should be.

I use the foreman with puppet and pxe/kickstart scripts to automate VM/baremetal provisioning etc.

It comes from the remote execution user snippet: https://github.com/theforeman/foreman/blob/develop/app/views/unattended/provisioning_templates/snippet/remote_execution_ssh_keys.erb

KVM & Foreman

Might want to look into https://theforeman.org/ if it's not too complex for you

The iso images are typically locked at a certain verison. The update repositories sounds like what you are looking for to cache updates. Look into theforeman.org and specifically the plugin Katello. This is an upstream for Red Hat's Satellite product. Another option would be Canonical's MAAS. Both of these options Sound like what you are headed for unless you really just mean synchronize into a folder and store the images in which case yeah.....just use rsync.

Alternatively, you can use Foreman+Katello, the upstream base of Satellite, to get started in learning the platform. You can also use the component matrix to use the versions that most closely resemble Satellite.

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.

Ansible-Core ↗