redhatgov/ansible-workshop

RedHatGov Ansible Workshop

ansible-workshop's Issues

lab run results - 20161025

I just ran through an abbreviated version of the lab, and there were a few issues that popped up after deploying the gold image.

• we had some connectivity issues, but they turned out to be the DNS servers at the site being overloaded. Nothing we could do about that.
• setting mass permissions (known issue)
• cloud credential - the gold image doesn't have one configured. we should figure that out.
• job templates - for example the motd template, when i went to look at it, it didn't have anything actually configured. it wasn't associated with a project. which makes since since i bootstrapped the project, but the job templates were in the image already.

instead of a gold image i think we need to work out a soup>nuts deployment/bootstrap playbook.

lab run results - 20161027

Location - San Diego, CA
Duration: 8:30-1:30
People in Lab - 43 (yes, 43)

Positives - the 101 level stuff went really well. I used http://redhat.slides.com/jduncan/ansible-20161027# for the intro slide deck. We wrapped up the 101 stuff (through http://people.redhat.com/~jduncan/san-diego.html#_job_templates) by 11:30 right as lunch showed up.

Needs Improvement - The inventories still don't work quite right. Since each user has an inventory, but they are tied back to the same AWS region using the same cloud credential, when you drill into the inventory to investigate tags, each person can see all of the instances.

TODO - test if unique IAM roles make this go away.

We also bumped up against the per-user quota for instances in AWS. Again, if unique IAM roles remedy the first situation it would remedy this as well.

How should PRs be handled?

Not sure how many eyes are watching the project. Having @wtcross, @bhirsch70, @jduncan-rva and team self-ACK seems appropriate -- or you guys planning to monitor each others PRs?

permissions API calls

tower-cli can't currently handle setting permissions for projects / inventories / etc.
we need to figure out the API calls to handle this and get it into the bootstrap script.