I've started and stopped with Ansible videos before because they just didn't explain everything I needed to know. I'm so happy I found this series because I am finally getting all the info I need to get it working. I appreciate how you explain everything and make it so easy to understand. Thank you!
I finally found the time to sit down and set this up on my homelab. Not only does it feel great to have ansible/automation working, but this also has been a great way to truly understand how ssh keys and git work from the command line. Top notch content. Thank you so much for enabling all of us noobs to upskill and do cool stuff!!
Excelent tutorials. I´m down in the south of Brazil. In Porto Alegre. As I have been trying to self train in network automation, and searching a lot around, I came across this series of videos. Finally the fog is beginning to clear, thanks to the clarity of your tutorials.
I have to say, your videos are perfect! At first I saw other shorter tutorials about ansible on youtube but I had many questions that werent answered there. Then followed your tutorial and I am not even half your course yet but I can say that your course is great. It is as if you know what is in my head becouse you always explain everything I have in mind watching your tutorial. Perfectly organized and it just all makes sense . Great job and thank you for your work!
Great introduction to Ansible. The depth and pace you adopt are just right. The section on ssh, git was very useful to have a great start in doing things the right way.
Thanks for the great series. Though I am not new to ansible, one can always learn something from others so I decided to watch them all. I know it may sound trivial, but I think it is an important correction, or at least something that should be conveyed. You refer to tasks within a play as plays. This may trip folks up if/when they ever test or go to certify on the topic. For example: --- # Simple playbook with two plays - name: name of first play hosts: all tasks: - name: name of first task - name: name of second task - name: name of second play - name: name of first task - name: name of second task In all honesty, most of us simply execute all of our items within a single play but as individual tasks... however I think its fairly important to distinguish the differences between plays and tasks. Another way to look at it is that the first, non-tabbed column are individual plays, everything indented underneath them is part of that play. I hope this just came through as a suggestion for completeness and not a nitpick. :) Thanks again for taking the time to film, edit, and share your videos.
Jay, great series on Ansible! Just to let you know, I created three identical Ubuntu 20.04 LTS Server VMs in Virtual Box (by creating one and cloning the other two), then changed the hostnames on the 2nd and 3rd VM and set all Servers to static IP addresses before following your video series on running ansible playbooks. I performed all of this by setting up the VMs on my FerenOS Main PC allocating 1GB VRAM to the Servers, then did everything else from my Acer Aspire laptop. I was totally successful in running everything that you did in your videos. Being a retired IT guy myself, I found it extremely rewarding to be able to run multiple command executions on multiple servers simultaneously on a Linux (versus Windows) network. Great job!
Just for clarification, @8:40, I am assuming that `ok=2` because there were "two steps" that were performed on the node (including gathering facts) which were successful?
Thank you for this so much. I use Ansible (and the free AWX GUI) to launch and combine playbooks and combines plays at work. While I’m very comfortable on the operational side, I still need this little boost with understanding the core authoring of playbooks. Really, thank you.
@@bashardlaleh2110 I could probably watch the whole thing in 2.0 (I teach Linux system administration at our local university and I'm a tech writer for the Linux Professional Institute). But do I really want to do that? Nope. Chi va piano va sano. :o)
I like how easily you explain the yaml basics, just enough for what we need in this video. Thanks to you I'm getting the hang of git commands and ansible!
Hello Jay @Learn Linux TV . One question, how do I know the exact name of the package I want to install? is there a list I can look up online? I noticed you knew beforehand that it was named "apache2".
Great. One comment: when you changed the state to absent to uninstall Apache, you should have probably change the name of the task (play) as well to read something like "Uninstall apache2 package"
Your videos are the best on youtube! Thanks for all your efforts - I am learning lots. How about somrthing about password management? I have been usin Lastpass for many years but have become frustrated with it as most passwords seem to be associated with usernames. Any suggestions?
I may have misunderstood how Ansible works, but, still..., what's behind the ansible module? In playbooks we can use modules with their respective parameters, but what makes that module execute whatever it says it will execute on an agentless machine? What made the apt module do its job it there is nothing on the targeted machines to interpret that module and do whatever the module is intended to do, in this case to install a package using apt?
The modules are written in Python. So when you call a module, there is a Python script that makes the OS calls, most likely using the os library in Python. So nothing is being installed on the remote machine, it is actually establishing an SSH connection and then running Python commands to do the work.
Sir the writing format you are using in writing the playbook its a bit confusing as the alignments of sentences are having long spaces or hyphens is this standard change when writing long playbooks. I am new to this sort of thing i don't have any developer/coder background
how to use ansible in the non interactive way? / how to use become without being asked for password but rather feed it throught var / env-var / stdio ?
i got this error when running the install_apache.yml: ERROR! 'task' is not a valid attribute for a Play The error appears to have been in '/home/mojo/ansible_test/install_apache.yml': line 3, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - hosts: all ^ here
@@JamesGaither11 well using shall commands like echo and sed is better to change text files then Emacs so ... well ... emacs is not design to be good for any thing, it is design to do everything and do a really bad job of it because of this
@@zeocamo emacs is an old style text editor. Some people still prefer it. I am not one of those. I was just highlighting to you that it is a text editor since you said it was an OS.
his knowledge and explanation is great but both beginning and end of the video is too long which is not related content. Hopefully, he will take care this concern for upcoming series...
How dare you sir! Emacs is clearly superior. Sure, I had to have my left hand amputated due to crippling arthritis, but is is a small price to pay for the privilege of using the superior text editor.
It does seem really janky. I played around with it at my last job and it seemed like I got constant errors about the config file and lining things up. I have no issue in Python or in other languages with indentation, but for some reason yaml just never felt all that intuitive to me. I'd probably get it if I spent more time with it, but this is the only time I've ever come across that markup language.
this guy is amazing, even better than the videos that i pay on udemy
right? they are really well done.. I love that he went over basics like SSH keys prior to doing any Ansible content.
Couldn't agree more. He's an excellent teacher and doesn't gloss over the issues that other instructors just take for granted are already known.
😝 I totally agree!
are you buy mumshad's course ?
I've started and stopped with Ansible videos before because they just didn't explain everything I needed to know. I'm so happy I found this series because I am finally getting all the info I need to get it working. I appreciate how you explain everything and make it so easy to understand. Thank you!
I m really glad you found value and thank u for the kind comment
For the amount of videos that I have been watching, none is better than Jay's. Bless you and your family.
I wish there were more youtubers like you... This Ansible series is fantastic!
the pace of the explanation is awesome. just what I needed. thank you for sharing your knowledge with us.
Thanks! I’m enjoying this Ansible series with Git also!
I finally found the time to sit down and set this up on my homelab. Not only does it feel great to have ansible/automation working, but this also has been a great way to truly understand how ssh keys and git work from the command line. Top notch content. Thank you so much for enabling all of us noobs to upskill and do cool stuff!!
this is a really great series. i never thought i could get this kind of quality instruction on youtube.
You are an amazing tutor. Am now a pro in ansible and git just by watching your tutorial
Bro you're not lying at all 💯
One of the finest technical presentation series I've seen. Well done ! thank you
Excelent tutorials. I´m down in the south of Brazil. In Porto Alegre. As I have been trying to self train in network automation, and searching a lot around, I came across this series of videos. Finally the fog is beginning to clear, thanks to the clarity of your tutorials.
I have to say, your videos are perfect! At first I saw other shorter tutorials about ansible on youtube but I had many questions that werent answered there. Then followed your tutorial and I am not even half your course yet but I can say that your course is great. It is as if you know what is in my head becouse you always explain everything I have in mind watching your tutorial. Perfectly organized and it just all makes sense . Great job and thank you for your work!
Great introduction to Ansible. The depth and pace you adopt are just right. The section on ssh, git was very useful to have a great start in doing things the right way.
Thanks for the great series. Though I am not new to ansible, one can always learn something from others so I decided to watch them all.
I know it may sound trivial, but I think it is an important correction, or at least something that should be conveyed.
You refer to tasks within a play as plays. This may trip folks up if/when they ever test or go to certify on the topic.
For example:
---
# Simple playbook with two plays
- name: name of first play
hosts: all
tasks:
- name: name of first task
- name: name of second task
- name: name of second play
- name: name of first task
- name: name of second task
In all honesty, most of us simply execute all of our items within a single play but as individual tasks... however I think its fairly important to distinguish the differences between plays and tasks. Another way to look at it is that the first, non-tabbed column are individual plays, everything indented underneath them is part of that play.
I hope this just came through as a suggestion for completeness and not a nitpick. :) Thanks again for taking the time to film, edit, and share your videos.
"I won't judge you even if it's emacs", lol, you killed me
Thank you so much for your work. Know that it helps a lot demystifying Ansible.
He got the "sick burn" in ... nice!
Thanks!
so great content on ansible, easy to understand and follow
A good series, thank you. I look forward to the next episodes.
Jay, great series on Ansible! Just to let you know, I created three identical Ubuntu 20.04 LTS Server VMs in Virtual Box (by creating one and cloning the other two), then changed the hostnames on the 2nd and 3rd VM and set all Servers to static IP addresses before following your video series on running ansible playbooks. I performed all of this by setting up the VMs on my FerenOS Main PC allocating 1GB VRAM to the Servers, then did everything else from my Acer Aspire laptop. I was totally successful in running everything that you did in your videos. Being a retired IT guy myself, I found it extremely rewarding to be able to run multiple command executions on multiple servers simultaneously on a Linux (versus Windows) network. Great job!
Just for clarification, @8:40, I am assuming that `ok=2` because there were "two steps" that were performed on the node (including gathering facts) which were successful?
Great stuff, Jay. Thank you. Playbooks are bringing a lot of fun and efficiency into this. That's what I'm here for. Very helpful playlist so far. 🤝
Thank you soo much for this series and all the other ones you do.
Dear Jay, your illustration of the first playbook was amazing. I loved it. Thank you again !!. Mat.
Thank you for this so much. I use Ansible (and the free AWX GUI) to launch and combine playbooks and combines plays at work. While I’m very comfortable on the operational side, I still need this little boost with understanding the core authoring of playbooks. Really, thank you.
playing your videos in 1.25 speed is perfect
I just tried that, and my blood pressure instantly went up a notch. Nah, 1.00 is fine.
@@nikikovacs1923 depends on your English and Tech skills 😉
@@bashardlaleh2110 I could probably watch the whole thing in 2.0 (I teach Linux system administration at our local university and I'm a tech writer for the Linux Professional Institute). But do I really want to do that? Nope. Chi va piano va sano. :o)
Good for you! Well done. Thank you very much for your work.
what a nice tutorial.. starting from the foundation practices.
you are so awesome _ great topic plus easy explanation ever seen
I like how easily you explain the yaml basics, just enough for what we need in this video. Thanks to you I'm getting the hang of git commands and ansible!
Excellent idea to use apache as example here !
Amazing series Jay! It's highly recommended! Thanks a lot for share!
Just another great video from Jay. Thanks a lot!
Thanks a lot for this great Ansible course ! much appreciated 🙂
Great content, looking forward to the next video
This playlist is amazing!
Thanks for this course dude, this is gold content
Going through the series. And have to say ... Love ya work chap.
Hello Jay @Learn Linux TV . One question, how do I know the exact name of the package I want to install? is there a list I can look up online? I noticed you knew beforehand that it was named "apache2".
Thanks
Thanks Jay
Man, you are seriously amazing. Thank you!
Thanks for sharing such amazing contents, very helpful to learn ansible.
Great. One comment: when you changed the state to absent to uninstall Apache, you should have probably change the name of the task (play) as well to read something like "Uninstall apache2 package"
8:40 ok equals two, what does number two mean ?
p/s :I understood, number two is the tasks
Someone should make a package called chocobo, just to troll Jay....jk Great video! I'm learning a lot.
legit content - well done and well presented
Your videos are the best on youtube! Thanks for all your efforts - I am learning lots. How about somrthing about password management? I have been usin Lastpass for many years but have become frustrated with it as most passwords seem to be associated with usernames. Any suggestions?
Youre amazing! Thanks for the good content man
You are amazing Jay " keep going "
You are so awesome. Thanks for the video
Great series 👍🏻
I may have misunderstood how Ansible works, but, still..., what's behind the ansible module? In playbooks we can use modules with their respective parameters, but what makes that module execute whatever it says it will execute on an agentless machine? What made the apt module do its job it there is nothing on the targeted machines to interpret that module and do whatever the module is intended to do, in this case to install a package using apt?
The modules are written in Python. So when you call a module, there is a Python script that makes the OS calls, most likely using the os library in Python. So nothing is being installed on the remote machine, it is actually establishing an SSH connection and then running Python commands to do the work.
Sir the writing format you are using in writing the playbook its a bit confusing as the alignments of sentences are having long spaces or hyphens is this standard change when writing long playbooks. I am new to this sort of thing i don't have any developer/coder background
god video, do you do make video for playbook installing a dns service on each server
Awesome! Thanks!
Thank you!
thanks a lot for the tutorial
at 12:30 he says 'let's add another play', but he should have said 'let's add another task'.
Awesome course . Thank You !
What is the name of the bar at the bottom of tmux?
ESC :q! yourself! vim user! :D Enjoyed the series.
how to use ansible in the non interactive way? / how to use become without being asked for password but rather feed it throught var / env-var / stdio ?
Great Job! Thank you so very much
hi sir,
permission to ask there are tools such as ansible to manage mobile apps?? thanks
i got this error when running the install_apache.yml:
ERROR! 'task' is not a valid attribute for a Play
The error appears to have been in '/home/mojo/ansible_test/install_apache.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- hosts: all
^ here
did you fix this error?
that would be the - name, either not alligned correctly to above or no space between the - and name, ansible is super fussy about spacing
the content is pretty good and demos are awesome, kinda giving good competition to the pluralsight lectures...by Wes Higbee.
Awesome
Awsome! Thank you
what is the become password
3:06 Did you add `become = True` to `ansible.cfg` like this:
[privilege_escalation]
become = True
Why not add `become_ask_pass = True` there too?
Awesome videos for free
I need more assistance learning ansible
why compare nano and vim with emacs ... nano and vim is text editors and emacs is a OS ... how can you compare this ?
Emacs is a text editor as well.
@@JamesGaither11 well using shall commands like echo and sed is better to change text files then Emacs so ... well ... emacs is not design to be good for any thing, it is design to do everything and do a really bad job of it because of this
@@zeocamo emacs is an old style text editor. Some people still prefer it. I am not one of those. I was just highlighting to you that it is a text editor since you said it was an OS.
@@JamesGaither11 yea ok i can see that, notepad is a text editor too .. for someone ...
@@zeocamo yes it is?
What is this become password?
It is the password to use the sudo command on the remote server
His user is jay on all of them and he set all passwords to be the same
his knowledge and explanation is great but both beginning and end of the video is too long which is not related content. Hopefully, he will take care this concern for upcoming series...
"even if it's emacs". Suspicious. :-)
I made the mistake of having cowsay installed while following this tutorial
How dare you sir! Emacs is clearly superior. Sure, I had to have my left hand amputated due to crippling arthritis, but is is a small price to pay for the privilege of using the superior text editor.
"I won't judge you, even if its emacs" 😂
"I won't judge you even if it's Emacs" ==> HA HA HA HA HA HA HA !!!!
The indentation requirements makes my blood boil.
It does seem really janky. I played around with it at my last job and it seemed like I got constant errors about the config file and lining things up. I have no issue in Python or in other languages with indentation, but for some reason yaml just never felt all that intuitive to me. I'd probably get it if I spent more time with it, but this is the only time I've ever come across that markup language.
i will judge you if it is emacs ..lol
Thanks!