At 11:55 there seems to be an editing glitch. The video talks about the changing the CentOS and Ubuntu values to 6 and 15, then you discuss Jinja turning things into an int for a second time. I suspect that you did multiple takes and someone made a mistake when it was edited together. Enjoying the videos

PS: This same thing happened in an earlier video, but I do not know which.

Hello James,

I have given rave reviews and 5 stars on your Mastering Ansible course in Udemy.

You have section on AWS and Ansible. However, I'm an Microsoft Azure person and I was wondering if you have created any videos on Azure and Ansible? If not, could you recommend any course on Azure and Ansible?

Thanks

Carlton

Hi All,

Raising this issue for FYI purposes only. This repository is now considered legacy and out of date. The course relating to this repository has recently been updated to a new version known as Dive Into Ansible.

The new course code repository is available at - https://github.com/spurin/diveintoansible

The new lab setup (where Ansible runs from your browser) is available at - https://github.com/spurin/diveintoansible-lab

Updates

• All of the course, has been updated to the very latest version of Ansible, which at this time is 2.10

• Python 3, is used as standard throughout the course

• The lab experience has been enhanced significantly. We've moved away from the Virtualbox based Virtual Machines and the lab runs entirely as containers in Docker! The lab can be launched with a single command and all systems, are now also accessible from your web browser!

• Hands on exercises

• Quizzes

• A playbook project where we launch a website with a special easter egg, an Ansible themed game known as 'Playbook Stacker'

• Improved Audio & Visuals

At present the course is available on Udemy at https://www.udemy.com/course/diveintoansible and will be published by Packt on other platforms like O'Reilly towards the end of December 2020 or January 2021.

Thanks for all your previous support and I hope you very much enjoy the new version. If you're interested, I also welcome all LinkedIn connections where I will be sending out future updates - https://www.linkedin.com/in/jamesspurin

Tagging the following who have previously Starred/Watched/Forked this, or the Packt equivalent of the repository - @81sai @AA90416 @Abhijit-Jamble @Alex-SBK @AnanaMJ @AshokBungatavula @Ashwinsurendar @BasicGrowth @Bhawan23 @Bhrath @CloudNartiveProjects @Cornel71 @Dina-Ula @Dineshkumarramaraj @Dwatkins4782 @El-Coder @EricZhou0815 @FlatBushZombie @Ganesha44 @GoCool2k19 @Indu-sharma @Javedfaruquee @JavierSplvd @Johaik @K8sDevOpsCloud @KSHRD-8th-Gen-DevOps-Learning @Lenz-devops @Llewellin @LoupX @MDSTECH @Mahal4ever @MaheshYalamanchili @ManojKumarDash @MartinMiddleton @MohitArora1 @MonitK @NetDevAutomate @NidaRe @NigamRout @NiharBiswal @ORG-dev18 @Quackers71 @ROBINSINGH0210 @Raghavendralad @RameshEY @Raynman727 @RoberMB @SK3343 @SLClayton @SNET-ARCH

The virtual machines supplied with the lab enviroment are configured by default with a UK keyboard. To change the keyboard for a specific locale, follow the instructions below based on whether or not it is a centos or ubuntu installed system -

CentOS based Virtual Machines

Check the existing keyboard configuration with the command -

# localectl

Use the following command to search for available keymaps -

# localectl list-keymaps

Given the multitude of keymaps, you may wish to narrow the list down to a specific country, for example, for the US, you could use -

# localectl list-keymaps | grep ^us

Once you have identified a keymap, use the following command to set -

# localectl set-keymap us

Ubuntu based Virtual Machines

Use the configuration wizard to change the keyboard, by issuing the command

$ sudo dpkg-reconfigure keyboard-configuration

however in this lecture
around 9 mins in, I cannot resolve the hosts
https://www.udemy.com/mastering-ansible-x/learn/v4/t/lecture/9300276?st
art=834

https://www.udemy.com/mastering-ansible-x

I get the error

[user@workstation ansible]$ ansible all -m ping
centos1 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: ssh: Could not
resolve hostname centos1: Name or service not known\r\n",
"unreachable": true
}

I suspect that a step is not defined here we we probably have to
configure dns somehow, but I don't think this step happenned.

I'm using RHEL 7.6, and I have mapped the alias to the ip addresses for
my NIC with
sudo ifconfig eno1:0 192.168.0.48

Hi,

will it be possible to provide a Vagrantfile to spin up and down the whole infrastructure without downloading the VirtualBox-Zips?

Would be nice, as I also have problems with these machines (Ubuntu-c e.g. don't want to update itself)

Hello sir , I have purchased your "Mastering ansible " udemy course. I am facing problem with installing nginx server using nginx_playbook.yml file. I have attached screenshot of problem. kindly resolve it.

Hi James. There is nothing really wrong in the content of the video referenced here. I am just pointing out to you to reconsider to avoid using Jinja keywords for use in either Variable or Value. Please take a loot at Section-4 Video#16 : Example script 05 @ minute 3:55.

Please review my previous post as shown below.

ansible@ubuntu-c[05]-> $ cat Jinja2_playbook.yaml

---
-
hosts: all
tasks:
- name: Ansible Jinja2 if variable is defined ( where variable is defined )
debug:
msg: >
--== Ansible Jinja2 if variable is defined ( where variable is defined ) ==--
{% set example_variable = 'monkey' -%} # I replaced 'defined' to 'monkey'
{% if example_variable is defined -%} # !!! 'defined' is a keyword
example_variable is defined
{% else -%}
example_variable is not defined
{% endif %}
...
 

Following pull request is created for merge.

#2

when setting up this tutorial in your os, its assumed that the current user name is packt. The problem is, most of us wont go to the trouble of making a new user to do the tutorial, and then you'll find that if you try to ssh in around here it wont work, because you wont be sshing into the other hosts as the user packt with ansible.
https://www.udemy.com/mastering-ansible-x/learn/v4/t/lecture/9300276?start=834

the solution is the ansible hosts file needs to use strings like this
[all]
centos1 ansible_user=packt

So that ssh will function correctly.