Thank you for explaining the variables in Ansible - it has been a mystery to me how they apply in playbooks and how they are written out. I have a better understanding now. Love this whole series! Thank you!
You're a gifted teacher :). Seriously appreciate these videos. Note: Wiki page for Ansible 15 has "Template" functionality listed in it (should be in Anisble 16). I was a little confused because I thought it was directly related to host_vars, but the video itself clarifies it beautifully. Sorry for sounding nit-picky. I just thought it might help.
Thanks a lot, your videos are awesome, great way for learning. i'm starting to create a raspberry pi kubernetes cluster, are you planning to create a "Getting started with kubernetes" video series? That would be awesome. Thanks again for sharing your knowledge. Cheers from Argentina
I've been thinking about it, but I'm not sure yet. I'm torn between stand-alone videos and doing a series. I'm experimenting right now to see which one people generally like better. I've done some stand-alone Kubernetes videos (including how to set up a cluster on Raspberry Pi) so I'm still trying to gauge how to best set up that content.
We don't need to add the sudoer_simone file to roles/base/files/ since the bootstrap script already takes care of copying this file to the server. Am I wrong?
nice series! I didnt't understand what is the content of the .yml files in host_vars? thank you for your time investment in this, it is really helpful as i'm starting from zero.
The content of the host_vars yaml files are variables to use in your playbooks. At a basic level it lets you rename a thing and refer to it as a different thing. The easiest way to understand this is to use it for something you want to change between computers or groups of machines. For example, in the host_vars YAML file I can make more than just a variable, I can make a whole list. So you can make one named whatever works for you such as packages or sys_packes as such: sys_packages: ['curl', 'ufw', 'iotop', 'iftop', 'python 3-pip'] Then in the actual playbooks to install a whole list of software you can reference this such as: - name: Install packages apt: name={{ sys_packages }} state= latest By splitting things up like this you may create as many lists of software for as many machines as you would like. And always install them on every machine using the same Ansible play, but a different host_vars list per host or group. You can split all sorts of things this way, like users to create or software to install. It's really just a way of letting you use the same plays to create different outcomes by splitting your instruction specifics across more than one file.
@@boxedowl It did got clearer in the next video, I understood what it was supposed to do, but not the lines itself we were using in this exercise. Thank you for your explanation, it did help me to have a better understanding.
you are blessed, we also have four seasons rainy and stormy, cold, rainy and hot
You have made fantastic videos in this series. Exactly what I was looking for. Kudos to you for the knowledge you possess 👍👌
Glad it was helpful!
Thank you for explaining the variables in Ansible - it has been a mystery to me how they apply in playbooks and how they are written out. I have a better understanding now. Love this whole series! Thank you!
You're a gifted teacher :). Seriously appreciate these videos.
Note: Wiki page for Ansible 15 has "Template" functionality listed in it (should be in Anisble 16). I was a little confused because I thought it was directly related to host_vars, but the video itself clarifies it beautifully.
Sorry for sounding nit-picky. I just thought it might help.
good to have clean and structural playbook, nice vid
Another great video. Merci Jay !
Thanks a lot for the awesome tutorial.
You have been very helpful, thank you sir.
I wish to learn Jenkins from you too, someday.
Where are you at in MI? I'm just outside of Ann Arbor.
Thanks a lot, your videos are awesome, great way for learning. i'm starting to create a raspberry pi kubernetes cluster, are you planning to create a "Getting started with kubernetes" video series? That would be awesome. Thanks again for sharing your knowledge. Cheers from Argentina
I've been thinking about it, but I'm not sure yet. I'm torn between stand-alone videos and doing a series. I'm experimenting right now to see which one people generally like better. I've done some stand-alone Kubernetes videos (including how to set up a cluster on Raspberry Pi) so I'm still trying to gauge how to best set up that content.
Thanks for sharing
Thank you
Well, it is at least better than Canada. We only have two seasons - i.e., winter and winter is coming. BTW, thanks for the videos.
We don't need to add the sudoer_simone file to roles/base/files/ since the bootstrap script already takes care of copying this file to the server.
Am I wrong?
Where can I find the Git repo of this course?
files folder is still necessary, since the simone sudoers file which is used by Bootstrap isn't in a role.. unless I screwed up somewhere
nice series!
I didnt't understand what is the content of the .yml files in host_vars?
thank you for your time investment in this, it is really helpful as i'm starting from zero.
The content of the host_vars yaml files are variables to use in your playbooks. At a basic level it lets you rename a thing and refer to it as a different thing.
The easiest way to understand this is to use it for something you want to change between computers or groups of machines.
For example, in the host_vars YAML file I can make more than just a variable, I can make a whole list.
So you can make one named whatever works for you such as packages or sys_packes as such:
sys_packages: ['curl', 'ufw', 'iotop', 'iftop', 'python 3-pip']
Then in the actual playbooks to install a whole list of software you can reference this such as:
- name: Install packages
apt: name={{ sys_packages }} state= latest
By splitting things up like this you may create as many lists of software for as many machines as you would like. And always install them on every machine using the same Ansible play, but a different host_vars list per host or group.
You can split all sorts of things this way, like users to create or software to install. It's really just a way of letting you use the same plays to create different outcomes by splitting your instruction specifics across more than one file.
@@boxedowl It did got clearer in the next video, I understood what it was supposed to do, but not the lines itself we were using in this exercise. Thank you for your explanation, it did help me to have a better understanding.
Good videos
I love your work
If the video was from 2023 i would definetly say it's in AI voice 😂
Cool