Man, what a Rabbit trail that one is !!
Anyway, I’m back to @Jay Ansible video’s. On part-8 now.
Man, what a Rabbit trail that one is !!
Anyway, I’m back to @Jay Ansible video’s. On part-8 now.
Ansible-9 Video Update: AlmaLinux v.s. CentOS
I used AlmaLinux rather than CentOS as @Jay used in the video’s (I don’t think AlmaLinux was out yet). Everything is the same (or seems to be) for AlmaLinux as it normally is for CentOS. However, I did get warning message when I ran the install httpd
and php
the first time.
[WARNING]: Platform linux on host 192.168.1.254 is using the discovered Python interpreter at /usr/libexec/platform-python, but future installation of another Python interpreter could change
the meaning of that path. See https://docs.ansible.com/ansible/2.11/reference_appendices/interpreter_discovery.html for more information
A few things to I had to do for AlmaLinux v.s Ubuntu. @Jay mentioned this early in the video series when he added his CentOS server
# Note: Ansible Section 12 discusses using Ansible for this.
# SSH to the instance, then
# Check the State
firewall-cmd --state
# Add the Zones
firewall-cmd --zone=public --add-service=http
firewall-cmd --zone=public --add-service=https
firewall-cmd --zone=public --permanent --add-service=http
firewall-cmd --zone=public --permanent --add-service=https
# Reload and Check
firewall-cmd --reload
firewall-cmd --list-all
# Enable the httpd Server
sudo systemctl start httpd
sudo systemctl enable httpd
sudo systemctl status httpd
# Test the default site at /var/www/html/*
curl localhost
I added
interpreter_python = auto_silent
to ansible.cfg to quiet down the interpreter warning.
Finished Ansible 1 through 16
I didn’t add the workstation sections, but the server stuff is all functioning as expected. Also, as indicated above I used AlmaLinux, but it was the same as CentOS. I want to look at doing the same for Nginx as well as I need that for the K3S build.
I’m gonna check out AnsibleVault next.