-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
admin training GCC2019 notes #1436
Comments
Documenting the second method for ansible connection is because it is quite normal. I personally encourage admins to run the playooks from their local computers, but this is a huge issue during training: people have windows/etc, and installing ansible does not work. We have the "one true galaxy path", but not the "one true ansible path"
Yes, this is why I encourage people to keep their ansible setups locally/in git. It is not disaster proof to have it on the machine. But this again does not work easily with training.
You're right, that's not mentioned. It used to be. |
I agree. But it might be better to choose a single path for the training (might be sufficient to mention it in the training), because I'm sure that in every training there is someone like me that chooses the other option and will get lost. |
That could be, always resisted removing that because it's the wrong way to do things in production, but I think you're right in the end, too confusing for no benefit. |
I'm definitely pro keeping it as well. Would be sufficient to:
|
|
Implemented all things in PR #1445, closing this now so I won't forget. |
Feel free to add your comments here:
You are installing ansible on a machine that will manage a second, remote machine
Swap examples for localhost vs remote machine #1437Having a second path here seems to violate the one true path rule...
Also if you shutdown/reset these machines then the motivation from the beginning would not work.
When choosing to run ansible on a remote host, login should be mentioned, ie set up ssh loging w/o password or store the password somewhere.
Or:
ansible-playbook -i hosts playbook.yml -k
api_key = {{ my_role_key }}
this might be a good place to mention/introduce the vaultThe text was updated successfully, but these errors were encountered: