We have some active directory test cases which are blocking for Fedora Server (https://fedoraproject.org/wiki/Test_Results:Fedora_34_RC_1.2_Server#Domain_joining_tests:_Active_Directory) and it turns out that there is one person who has access to a windows server and can run the tests. We've had multiple releases where we need to go find that one person to run the tests so that we can release.
My idea is to spin up a few AWS instances (one windows server, one or more fedora instances for testing) as needed to do the testing and then destroy them when the testing is done. This way, anyone with AWS credentials can run the tests and we avoid the situation we're currently in.
Instead of worrying about whether using windows server trial licenses indefinitely is ok with legal or getting a windows server license which would be more-or-less tied to a small number of people, running the tests in AWS seems like a more sustainable idea in the long run.
I'm requesting the ability to spin up instances on demand to do the AD testing.
It'd be great to be able to do the testing before Final freeze (2022/04/05) but this is more of a long term project so 2022/08/01 (in time for F37 testing) would be fine.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
I have created a group in fas and made @tflink the sponsor so feel free to add whoever is needed.
I have also created a role in AWS which will give you access to EC2 resources. All resources should be tagged FedoraGroup:qa on creation or you will lose access to them (If you forget to tag just reach out and we can fix it so it won't be left behind)
FedoraGroup:qa
This PR will need to be merged and a playbook run next week when the freeze is over and then the access should be live: https://pagure.io/fedora-infra/ipsilon-fedora/pull-request/6 I will comment here after its run
This is web console access only. If programmatic access is needed in future we can look at adding it. If you need any help getting set up when the access is working let me know and I will help where I can.
Metadata Update from @mobrien: - Issue assigned to mobrien
I merged the PR and ran the playbook. :)
Can you confirm it's working as expected now?
I'm able to login to aws and launch an instance, I'd say everything is working. Thanks for getting this taken care of.
Metadata Update from @tflink: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.