Getting started with Ansible 13 - Adding Users & Bootstrapping

preview_player
Показать описание
Ansible is an incredible configuration management and provisioning utility that enables you to automate all the things. In this series, you'll learn everything you need to know in order to use Ansible for your day-to-day administration duties. In video 13, we'll look at adding a user, and then we'll set up Ansible to use a specific user for running tasks. Also, we'll walk through creating a bootstrap playbook specifically for adding new nodes.

Full series:
Part 13 (Adding Users): This video

☁️ Get $100 in credit toward deploying your very own Linux servers on Linode!

🙌 Support me on Patreon and get early access to new content!

Wiki article for this video:

🛒 Affiliate store for Linux compatible hardware/accessories (commission earned):

💻 Check out the Tiny Pilot KVM for your Homelab (commission earned):

🐦 Follow me on Twitter!

📖 Check out jay's latest book, Mastering Ubuntu Server 3rd Edition. Available now!

👨 More about me:

💽 How to create a bootable flash drive for installing Linux:

🐧 Which distro do I use?

🔐 How to better secure OpenSSH:

☁️ How to create a cloud Linux server with Linode:

#DevOps #Automation #Ansible
Рекомендации по теме
Комментарии
Автор

Thank you for doing these tutorials, i find them very informative and simple to understand.

Y.S.
Автор

Wow Jay. You did an awesome effort to learn us Ansible. I really appreciate this. Amazing. Thank you so much.

zachsandvik
Автор

very cool course thank you so very much. it was cool updating a couple of machines, but things started to stink when i had six. now i push one command and every server is done. what a time and pain saver! thank you again for taking the time to make this and all of your videos. you have taught me so much and i really appreciate it .

raymondfb
Автор

Thank you, Jay. This series is really great!

jgranahan
Автор

I just read you can use the 'content:' argument to directly put sudoers content into the file. Just a one line change and doesn't require an external file.
These tutorials are very helpful - thanks!

petergoodall
Автор

You did a fantastic job! Thank you very much.

fabrice
Автор

Thanks for the content, its great.
bottom title at 0:37 says "Part 12 - Managing Services", should be "13- Adding Users & Bootstrapping". :)

feiloose
Автор

... and thank you for movie advice 😉, , i will take a look.. and for sure for whole ansible series.. very very cool

peterpekny_goo
Автор

very cool, loved your included sim one

Cyko
Автор

for anybody following along today Ansible changed the way you can add sudoers files

- name: Copy a new "sudoers" file into place, after passing validation with visudo
copy:
src: /mine/sudoers
dest: /etc/sudoers
validate: /usr/sbin/visudo -csf %s

This format is the only way I got it to work for me

gold
Автор

"0440 because we want to keep it locked down"
As we give simone ALL=(ALL) NOPASSWD

XD

Just thought that was really funny. Thank you so much for putting this series together. It's excellent.

bamhm
Автор

Hey Jay, your videos are awesome!
I wanted to let you know this video has the title card from Part 12.

nbnommer
Автор

Thanks for great videos!

I have ran into a issue with the bootstrap playbook: When in your case the ansible.cfg has "remote_user" set to simone, Ansible will try to use that user when the bootstrap playbook is executed. But in fact the servers default user, such as root, ubuntu or whatever should be used for the bootstrap.
This can be solved by adding the argument "-u default_user_on_server" to the ansible-playbook command.

davidandersson
Автор

Thank you for such a great video. I have tried to create users with bash scrip, csv list. It worked well. I wanted to verify the users with a custom module and csv new list of random users against a python ansible module. I have ran into tons of syntaxes issues. I wanted my script give me a printout of users that exist and and others who doesn't exist. How would you do that? Is there a better way to verify large amount of users with custom module?

Yanahamm
Автор

You forgot to explain the sudoers file. A little research on visudo helped me understand though.

fabrice
Автор

WOW i got to watch that film love your they way you explain bro

weniweedeewiki.
Автор

This series is super great and extremely helpful! One question from this lesson: is it "safe"/"best practice" to leave the simone user (and their sudoer file) on the systems after we're done running all of our ansible scripts, or should there also be a "teardown" file that we run at the end which removes her?

duffyscottc
Автор

Hi Jay, I have a question. When I build a Ubuntu VM or server I ofcourse create a linux user and I already pull down the SSH keys from github with the option in the installer. So I dont want to make an other user: simone for example but I want to use my already made user: user_example. Is this possible with the config you made?

djvincon
Автор

16:54 I'm not sure what 'update_only/update_cache' really does..
following along I added one centos server vm when you did. everything worked for some time but I started to receive 'unknown error' or something similar. error was gone after 'yum update' directly over centos terminal, centos downloaded 800mb of updates..

dzonsmit
Автор

what is best only have 1 BIG file with all the servers in (in my case around 140) or more files ... we don't really got any servers with the same packages on ???

zeocamo