Skip to content
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

Closed
3 tasks done
bernt-matthias opened this issue Jul 1, 2019 · 6 comments
Closed
3 tasks done

admin training GCC2019 notes #1436

bernt-matthias opened this issue Jul 1, 2019 · 6 comments

Comments

@bernt-matthias
Copy link
Contributor

bernt-matthias commented Jul 1, 2019

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 #1437

    Having 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 vault

@hexylena
Copy link
Member

hexylena commented Jul 1, 2019

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"

if you shutdown/reset these machines

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.

mention how to connect

You're right, that's not mentioned. It used to be.

@bernt-matthias
Copy link
Contributor Author

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.

@hexylena
Copy link
Member

hexylena commented Jul 1, 2019

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.

@bernt-matthias
Copy link
Contributor Author

I'm definitely pro keeping it as well. Would be sufficient to:

  • the trainer should just mention which path should be followed and
  • docs for the remote path should be completed

@hexylena
Copy link
Member

hexylena commented Jul 1, 2019

  • lockout on wiping out directories if playbook is currently running. pgrep ||
  • kill galaxy during the apocalypse

hexylena added a commit to natefoo/training-material that referenced this issue Jul 6, 2019
@hexylena
Copy link
Member

Implemented all things in PR #1445, closing this now so I won't forget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants