ok, a bit more info:

• What OS do you want? I assume rhel7?

• Any cpu needs? just a pair ?

• Memory needs? 4gb ok?

• Disk needs? Our "default" I think is a 20GB / and thats it. Will they need bigger space?

• We have a 'retrace' fas group, should we use that for access to these + privs to run the ansible playbooks? Or would you prefer a new 'sysadmin-retrace' group that has a different set of folks?

Finally, the plan is to access these via our fedoraproject.org proxy setup right? (ie, move them into the way we are doing most of the rest of our applications).

I can create them and setup a basic playbook, then you all can modify and run the playbook from batcave01 once I have the above info. :)

Replying to [comment:1 kevin]:

ok, a bit more info:

• What OS do you want? I assume rhel7?

Yup.

• Any cpu needs? just a pair ?

Pair is fine.

• Memory needs? 4gb ok?

• Disk needs? Our "default" I think is a 20GB / and thats it. Will they need bigger space?

• We have a 'retrace' fas group, should we use that for access to these + privs to run the ansible playbooks? Or would you prefer a new 'sysadmin-retrace' group that has a different set of folks?
  

All good, retrace group is fine.

Finally, the plan is to access these via our fedoraproject.org proxy setup right? (ie, move them into the way we are doing most of the rest of our applications).

Correct.

I can create them and setup a basic playbook, then you all can modify and run the playbook from batcave01 once I have the above info. :)

Sounds good. We do have standalone ansible roles for both projects: https://github.com/abrt/ansible-role-retrace-server https://github.com/abrt/ansible-role-faf

They currently depend on few other things (httpd/postgres) that I'm trying to isolate as standalone roles so in the end we can just include these from fedora-infra-ansible repo.

ok. I have created retrace01.stg.phx2.fedoraproject.org and faf01.stg.phx2.fedoraproject.org.

Everyone in the retrace group should have access to them (via basion.fedoraproject.org or bastion-comm) as well as ability to run ansible against them (run on batcave01: sudo rbac-playbook groups/retrace.yml).

The playbooks now are very simple and just have our base stuff in them. I added it to the same playbook that controls your retrace01 prod instance (ansible/playbooks/groups/retrace.yml on batcave01).
So, while you are working on this you may want to add another play there that only goes to the stg machines and add your roles to that until we are ready for production.

We can close this ticket now, or keep it open for next steps? Which ever you prefer...

Thank you! I can successfully access both machines and run ansible against them. Closing.