These videos are gold, they'll make launching testing environments so much easier and faster. Thank you for making these!
@carloslizarralde49203 жыл бұрын
so far this is the best series adds all the missing parts needed to really understand the tools that will help.
@mysticjoe2953 жыл бұрын
While this is good, check out Jeff Geerlings ansible 101 series - far more comprehensive and supports an excellent book.
@jagd16913 ай бұрын
Excellent Explanation. Best Video about Ansible on KZbin
@farkhodazizov4199 Жыл бұрын
Thank you so much. God bless you and your family.
@UnknownSend3r3 жыл бұрын
Brilliant explanation , imo you're the jay z of config management tutorials.
@MarkusEicher702 жыл бұрын
Thanks a lot Jay, that was pretty exciting. One thing I hope we will see later on in this series is how to use elevated privileges when the servers have different passwords for sudo. Great lessons so far! 👍
@similoluwaokunowo5127 Жыл бұрын
I am currently on the 6th video in this series, and I must say you are a very incredible teacher. It takes a lot of effort and kindness to design such a structured course and publish it for free. Thank you very much 💗
@LearnLinuxTV Жыл бұрын
Wow, thank you! I really appreciate that.
@RakeshShivayyaGuttedar Жыл бұрын
This tutorial is absolutely more valuable than paid courses out there.Thank you for all your efforts !!
@isaacmaag12943 жыл бұрын
Love the tutorial. Could you make a terraform series as well?
@davidraymond74204 жыл бұрын
Nice video Jay, I’m totally new at Ansible, and I can see the potential to help me as sysadmin for my linux farm I need to managed. Thanks for sharing this 👍👌
@mathewkargarzadeh31583 жыл бұрын
Very Nice Jay. Thanks a million !!. Mat.
@Awas792 жыл бұрын
Absolutely love this series :D
@brodierobson44902 жыл бұрын
This is amazing content.
@michaelfisher2821 Жыл бұрын
Great series so far, really easy to follow along in a lab. Also, does anyone else think Jay has a 'Better Call Saul' voice?
@vialomur__vialomur5682 Жыл бұрын
such a great tutorial!
@dzonsmit10 ай бұрын
9:51 same here but I didn't install tmux previously, I guess it came preinstalled with my ubuntu servers 22.04. btw I would like to see Kubernetes series on your channel!
@beydoin3 жыл бұрын
Great video! Thank you!
@mlskksl3 ай бұрын
At 3mins you said it should have returned with error but mine has the same success output with "- - become - -ask-become-pass" and without the longoptions
@luistheitguy2 жыл бұрын
Great ! Awesome teacher !
@andromachirozaki57533 ай бұрын
amazing
@asaf1584 жыл бұрын
Great Ansible tutorial
@jeffreyhiggason40042 жыл бұрын
At 15:22 you show the command sudo apt dist-upgrade. Wouldn't the command be sudo apt-get dist-upgrade or sudo apt full-upgrade???? I didn't think that apt dist-upgrade would even work but obviously in your video it is...??
@portiseremacunix Жыл бұрын
Does your book cover this series?
@brishavkuikel6846 ай бұрын
Hi Jay !! I am using my main machine (wsl ubuntu on Win 11 ) as the workstation and using virtual box I have created a host VM. In my case without specifying -u i cannot connect to host, but you are not specifying any particular user and it is still able to connect to the host why is that ? pls help someone
@davetweens76875 ай бұрын
Jay is the user he used on all 4 hosts. The default user in ssh is the current user .
@davetweens76875 ай бұрын
You can use ~/ssh/config to set helpful defaults
@grahammccann85543 жыл бұрын
Thank you Jay, :-)
@PS34563 жыл бұрын
Jay- Great video and simple explanation. Question: Where do you get various -a parameters?
@mysticjoe2953 жыл бұрын
Check the ansible docs. What he doesn’t explicitly show or explain is the -a params are the param: from the docs look at 6:50
@harunaadoga Жыл бұрын
Thank you!
@kiki-vu9if2 жыл бұрын
great teacher!
@quidquopro11856 ай бұрын
Is it not better to setup an ansible user on the servers that are allowed to run escalated commands?
@DrazenMarjanovic Жыл бұрын
Thanks a lot
@glmchn4 жыл бұрын
Still awesome
@omarshararhussein7705 Жыл бұрын
when I run ansible all -m apt -a update_cache=true --become --ask-become-pass i get WARNING updating cache and auto-installing missing dependency python apt followed by a failed error? any ideas anyone?
@paragb20082 жыл бұрын
Good video
@CodeCraftedByLucasАй бұрын
Hi everyone I decided to make adduser server1, server2 and server3 with the same ip address on same ubuntu setup I think. When you run the "ansible all -m apt -a upgrade=dist --become --ask-become-pass" on the main UNIX user it cannot do that for all because the apt-get update is already running for one server so it will only run for server1 but not for the other server2 and 3 since only one dist update can be installed at once. You could run separately "ansible server1@192.168.x.x -m apt -a upgrade=dist --become --ask-become-pass". I wanted to share this for those who are interested.
@mihai65642 жыл бұрын
nice video
@DavidBenOtto Жыл бұрын
What's the name of the tool you're using to navigate between servers?
@davetweens76875 ай бұрын
Tmux
@abibatadesina44122 жыл бұрын
Thank you for the wonderful video series. what is sudo password please?
@osada96 Жыл бұрын
I wonder if there is any way to run that ad-hoc commands by using cron with -- become --become-ask-pass? In other words, how to cron all these commands without manual entering passwords?
@davetweens76875 ай бұрын
Yes but you can use an ssh key with no passphrase direct to the root user and not use becomes or sudo at all which is a security risk.
@davetweens76875 ай бұрын
I'm sure that you can use some sort of credentials on ansible too but I'm not an ansible expert. Which is why I'm watching these videos 😊
@davetweens76875 ай бұрын
I think the link above is what you eant
@NameCallingIsWeak3 жыл бұрын
Great series, thank you. Minor quibble, if you can pronounce the Phil Collins hit "Sussudio" you can also pronounce "sudo" correctly.
@NameCallingIsWeak3 жыл бұрын
su-DO, "doh" like Homer Simpson
@GC-qe8vc3 жыл бұрын
It's supposed to stand for "superuser do" so it's pronounced with "do" as do in doing something.
@miyalys2 жыл бұрын
As G C says, here from the inventor: kzbin.info/www/bejne/gpKkqJ9pfbNomtU
@jantje01k4 жыл бұрын
what if your servers have different pass ?
@praecorloth4 жыл бұрын
A couple of things you might consider: 1. A service account with a single password across your servers 2. If you do ansible --help, there are options for a vault password file. Jay might go into this in a later video. Not sure, still making my way through the series now. But this option might let you specify usernames, passwords, and hosts.
@jantje01k4 жыл бұрын
@@praecorloth He did make a video about Ansible Vault, but not with multiple passwords for different hosts
@praecorloth4 жыл бұрын
Hrm. Well, I'm not an Ansible expert. So without knowing all of the tools available with Ansible right now, the best tools to I can think of for this issue would be defining hosts in multiple groups based on any servers that have a common password, and then have your playbooks look at the facts variables to identify which modules need to be used based on maybe what OS is installed, or what software is installed, etc. Looking at some of the documentation for Ansible vault, it looks like you can call up some of those secrets with a variable. If that's the case, then maybe you can pass that secret in the playbook, and have one password for revealing those secrets. I don't know, though, haven't had a chance to play with it yet.
@alphabasic1759 Жыл бұрын
The command is sudo, … not suooooo
@MrSandshadow Жыл бұрын
0:10 I would belive you if your face wasnt as emotionless as your voice was dead inside. xD I know we engineers are not best performers...
@jannahiaali56065 ай бұрын
bloody wasted time, just directly use sudo, and follow Ansible documents to work quickly!!
@robothtml5 ай бұрын
Ubuntu 22.04 Cloud Init VM running inside of ProxMox I ran into some confusion following this video. Running the following command did not require the become password. ansible all -m apt -a name=tmux --become I can even add "--ask-become-pass" and type in the incorrect password and it's still working. The cause: # cat /etc/sudoers.d/90-cloud-init-users # Created by cloud-init v. 24.1.3-0ubuntu3.3 on Fri, 19 Jul 2024 19:38:22 +0000 # User rules for username username ALL=(ALL) NOPASSWD:ALL I commented out the line and rebooted the VM. It appears to have resolved the issue.