Thank you so much for putting this up on youtube. I am getting so much out of this. All of the other YT tutorials on Ansible I watched where very short and skipped over so much detail I was continually lost, but your videos explain everything, and I greatly appreciate that.
0:02 For reference, I was trying to start the live stream for 10 minutes or so, and TH-cam kept displaying "Live streaming isn't available right now" - I had to restart my browser, OBS, and stop and start the stream in TH-cam's site a couple times, and somehow it started working after all that :)
I haven't worked as a Sysadmin role in well over a decade. Back then, I automated many tasks locally with Perl and remotely using expect. Since then, I have just been building boxes to support my work as I go and not thought about scaling. The last three episodes of this made ansible look like a pretty neat tool that might be helpful. This video shows why people talk about it. Wow, this is truly scalable automation. I can see a lot of things coming up like testing for the latest and auto populating those variables to be sure that when you use it next year you build the current solr. I am going to go pop some corn and run episode 5!
Regarding single and double quotes - the one place I HAVE seen a difference is in the regexp: line in lineinfile and replace modules. I’ve seen the regular expression characters behave differently with double quotes, and as a result I always use single quotes in a regal entry. Oh, also the mode: directive in the various modules that set permissions like copy, file, and template. The instructions recommend using single quotes for that. I for one would LOVE examples of molecule use. I tried to use it, but I had a VERY hard time doing so; unlike the Ansible project, the molecule documentation is VERY difficult to understand, perhaps because I never see any examples other than via docker...
Thanks for the vids and the free books. It sure is easier to follow with a video, where you discuss things more in details, than with the books, where i spend my time thinking "wait, where do i write what?", or "why does he do that?". For instance, with "ansible for kubernetes", i gave up trying to install solr, as i was completely lost. But thanks to this vid, it's running. Anyway, I'm learning a lot, thanks.
And watching the stream with great interest, learning a lot, and looking forward to putting it into practice with a larger farm, from Guyana by way of New York and Oakland, CA. VAGRANT ROCKS! No more PowerEdge 1950 III test server for testing!
42:57 Can you also run it on your local machine? You mentioned earlier you had ansible playbooks to setup your mac. Do you run them from an other machine and ssh into the mac, or how does that work?
Yes! You can run Ansible playbooks against a local machine using the 'local' connection plugin (add `connection: local` to a play, or add `-c local` on the command line). This bypasses the SSH connection entirely.
@@JeffGeerling Thank you! I've been going through these episodes, and they're super informative. Thanks for making (or having made) the time to make these!
I’ve been using Ansible professionally a ton an I follow this series to check what I missed. The creates option is unfortunately one of them. Saves a ton of registering vars with stat. Thanks.
Another great video! Only thing I take issue with (as a Server Admin) is unpacking everything in /tmp .. when the server gets patched and rebooted, all of that goes away and your ansible code will re-download and unpack everythinig again into /tmp. Much better to have an agreed-upon disk, mount, etc, that doesn't go away on a reboot.
Quite true, and that does technically break idempotence between reboots. The main reason I stick with /tmp as a default (and especially when teaching) is it's the only location I know I can rely on and write to in almost any situation. But I should probably mention that using a different directory for 'scratch' files (even /opt, or /var) would be a good idea, especially if you rely on those files for installation.
@@JeffGeerling That's totally fair! Yes, I think mentioning that would be good. Mention tmp is fine for teaching or Dev, or something you don't expect to run over and over (ad-hoc run). Thank you Jeff for all you do!
@@JeffGeerling Hi Jeff. I'm a bit late to this discussion, but I think /var/tmp would work well in these examples. /tmp is sometimes setup as a small RAM disk (e.g. only 100MB) which you could potentially fill with a large download, while /var/tmp should be backed by proper storage. And to Supr Chrgd's indempotence point, /var/tmp shouldn't be cleared on reboot. See the entry for /var/tmp in the FHS: en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standard. And cheers for this video series Jeff, it's superb.
Love this, very practical and detailed. Found it yesterday, just bought the book, looking fwd to more quality content, keep it up. Any plans on doing same for Ansible for Kubernetes??
I have one question about the playbooks, Is it better to have all playbooks in one ansible playbook as roles, or make different playbook for each role?
... it was DNS... was me this past week, tying to build something in AWS. kept on thinking, Security Groups, maybe it is NatGW, no... it's Route Tables... nope, it was DNS...
Thanks!
Thank you so much for putting this up on youtube. I am getting so much out of this. All of the other YT tutorials on Ansible I watched where very short and skipped over so much detail I was continually lost, but your videos explain everything, and I greatly appreciate that.
I'm glad I could help! I hope you can continue watching and learning more!
@@JeffGeerling I definitely will!
this is the best ansible tutorial available on youtube. thanks for explaining everything in detail.
0:02 For reference, I was trying to start the live stream for 10 minutes or so, and TH-cam kept displaying "Live streaming isn't available right now" - I had to restart my browser, OBS, and stop and start the stream in TH-cam's site a couple times, and somehow it started working after all that :)
Thank you for sharing the complete demo and covered all the good stuff. Where i can get to reference those config ,playbook..etc.
I haven't worked as a Sysadmin role in well over a decade. Back then, I automated many tasks locally with Perl and remotely using expect. Since then, I have just been building boxes to support my work as I go and not thought about scaling. The last three episodes of this made ansible look like a pretty neat tool that might be helpful. This video shows why people talk about it. Wow, this is truly scalable automation.
I can see a lot of things coming up like testing for the latest and auto populating those variables to be sure that when you use it next year you build the current solr. I am going to go pop some corn and run episode 5!
Świetny film! Dostał ode mnie aplauz za 10,00 zł 👏
Going slowly through the book and this series Jeff, many many thanks. Keep up the great work!
Regarding single and double quotes - the one place I HAVE seen a difference is in the regexp: line in lineinfile and replace modules. I’ve seen the regular expression characters behave differently with double quotes, and as a result I always use single quotes in a regal entry.
Oh, also the mode: directive in the various modules that set permissions like copy, file, and template. The instructions recommend using single quotes for that.
I for one would LOVE examples of molecule use. I tried to use it, but I had a VERY hard time doing so; unlike the Ansible project, the molecule documentation is VERY difficult to understand, perhaps because I never see any examples other than via docker...
Thanks for the vids and the free books. It sure is easier to follow with a video, where you discuss things more in details, than with the books, where i spend my time thinking "wait, where do i write what?", or "why does he do that?". For instance, with "ansible for kubernetes", i gave up trying to install solr, as i was completely lost. But thanks to this vid, it's running. Anyway, I'm learning a lot, thanks.
I found this series the other day. I have a pi I am reimagining, and I figured it would be a good time to learn Ansible.
And watching the stream with great interest, learning a lot, and looking forward to putting it into practice with a larger farm, from Guyana by way of New York and Oakland, CA. VAGRANT ROCKS! No more PowerEdge 1950 III test server for testing!
I finally got my playbook working with my docker solution :D
Thank you again for the awesome video!
42:57 Can you also run it on your local machine? You mentioned earlier you had ansible playbooks to setup your mac. Do you run them from an other machine and ssh into the mac, or how does that work?
Yes! You can run Ansible playbooks against a local machine using the 'local' connection plugin (add `connection: local` to a play, or add `-c local` on the command line). This bypasses the SSH connection entirely.
@@JeffGeerling Thank you! I've been going through these episodes, and they're super informative. Thanks for making (or having made) the time to make these!
Thank you so much for this series! I've managed my servers for the longest time now. It's time for something better
You're the man ! Awesome content...
I’ve been using Ansible professionally a ton an I follow this series to check what I missed. The creates option is unfortunately one of them. Saves a ton of registering vars with stat. Thanks.
thanks for this series
Jeff, this Episode was perfect
34:40 If you specify one specific file, you might still miss all the other stuff. Is that really clever to do that?
Found you from the reddit while searching ansible-linter for VS code. & watched this video. waiting for live stream today. Amazing. :)
Thank you for these videos! They are of great help when starting out in Ansible! Cheers :D
Another great video! Only thing I take issue with (as a Server Admin) is unpacking everything in /tmp .. when the server gets patched and rebooted, all of that goes away and your ansible code will re-download and unpack everythinig again into /tmp. Much better to have an agreed-upon disk, mount, etc, that doesn't go away on a reboot.
Quite true, and that does technically break idempotence between reboots. The main reason I stick with /tmp as a default (and especially when teaching) is it's the only location I know I can rely on and write to in almost any situation.
But I should probably mention that using a different directory for 'scratch' files (even /opt, or /var) would be a good idea, especially if you rely on those files for installation.
@@JeffGeerling That's totally fair! Yes, I think mentioning that would be good. Mention tmp is fine for teaching or Dev, or something you don't expect to run over and over (ad-hoc run). Thank you Jeff for all you do!
@@JeffGeerling Hi Jeff. I'm a bit late to this discussion, but I think /var/tmp would work well in these examples. /tmp is sometimes setup as a small RAM disk (e.g. only 100MB) which you could potentially fill with a large download, while /var/tmp should be backed by proper storage. And to Supr Chrgd's indempotence point, /var/tmp shouldn't be cleared on reboot. See the entry for /var/tmp in the FHS: en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standard.
And cheers for this video series Jeff, it's superb.
Good job! Thanks for lessons
Love this, very practical and detailed. Found it yesterday, just bought the book, looking fwd to more quality content, keep it up. Any plans on doing same for Ansible for Kubernetes??
Yes; just make sure you're subscribed! I am planning on a 'Kubernetes 101' series soon.
great content, i am liking your videos
"Ansible Journey" - Gandalf the Grey
The bottom 3 lines at the bottom of the editor window gets covered.
Thanks
I have one question about the playbooks,
Is it better to have all playbooks in one ansible playbook as roles, or make different playbook for each role?
We'll get to roles in episode 6, I hope; there are a lot of different ways you can manage roles and playbooks for easier maintenance.
... it was DNS... was me this past week, tying to build something in AWS. kept on thinking, Security Groups, maybe it is NatGW, no... it's Route Tables... nope, it was DNS...
it's always DNS
difference between ' and " is this: "
" != '
'
18:00
he doesn't start talking about the real-world playbook until 14min in
Molecule Molecule :)
USA< Illinois, TURKMENISTAN