Greetings. Mark and I have talked in the past about moving some of the aws provisioning we are doing into ansible, and it came up again this morning in #fedora-admin. We have many (but not all) maintainer-test instances, a bunch of proxies and all the copr machines in aws that are currently in ansible. I think we could do something similar to tasks/virt_instance_create.yml (which we have for using virt-install and installing libvirt vms). We do have a tasks/aws_cloud.yml that copr instances use, but it doesn't provision the instance, just sets up things for ansible. Copr folks: if we expand aws_cloud.yml to provision also (if the host is not up/reachable on it's dns name/ip) would you be ok using that as well? Or should we seperate out copr from maintainer-test/proxies? Also, there's the question of auth. batcave01 will need creds for those things. Sadly, I think this means making a user and getting a token, but if there's some better way to handle auth there that might be nice. Finally, we are using ansible-2.9.x currently. We would need any solution to be able to work with that and newer ansible, which we likely will be switching to before long. Any other ideas or thoughts around this? Thanks, kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
