Hi folks! We're currently still discussing adjusting the release criteria to explicitly require Fedora releases to boot in EC2. Someone pointed out that if we're going to require that, it would be good if we had an account allowing EC2 access for testing, so individual Fedora testers don't have to potentially pay out-of-pocket just to test Fedora works in EC2. Does anyone know if we have an existing arrangement with Amazon for this? Thanks!
On 9/13/19 3:44 PM, Adam Williamson wrote:
Hi folks! We're currently still discussing adjusting the release criteria to explicitly require Fedora releases to boot in EC2. Someone pointed out that if we're going to require that, it would be good if we had an account allowing EC2 access for testing, so individual Fedora testers don't have to potentially pay out-of-pocket just to test Fedora works in EC2. Does anyone know if we have an existing arrangement with Amazon for this? Thanks!
cc Paul Frields
I have access to an account I think we use explicitly for testing Fedora in AWS. Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
Dusty
On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
On 9/13/19 3:44 PM, Adam Williamson wrote:
Hi folks! We're currently still discussing adjusting the release criteria to explicitly require Fedora releases to boot in EC2. Someone pointed out that if we're going to require that, it would be good if we had an account allowing EC2 access for testing, so individual Fedora testers don't have to potentially pay out-of-pocket just to test Fedora works in EC2. Does anyone know if we have an existing arrangement with Amazon for this? Thanks!
cc Paul Frields
I have access to an account I think we use explicitly for testing Fedora in AWS. Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
It'd be better for it to be something more robust and 'team-accessible' than just people emailing each other passwords, ideally :)
On 9/13/19 4:51 PM, Adam Williamson wrote:
On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
On 9/13/19 3:44 PM, Adam Williamson wrote:
Hi folks! We're currently still discussing adjusting the release criteria to explicitly require Fedora releases to boot in EC2. Someone pointed out that if we're going to require that, it would be good if we had an account allowing EC2 access for testing, so individual Fedora testers don't have to potentially pay out-of-pocket just to test Fedora works in EC2. Does anyone know if we have an existing arrangement with Amazon for this? Thanks!
cc Paul Frields
I have access to an account I think we use explicitly for testing Fedora in AWS. Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
It'd be better for it to be something more robust and 'team-accessible' than just people emailing each other passwords, ideally :)
Encrypted of course :-P
It would be better to have it be something more managed but I don't have anything more robust that I can offer right now. Maybe fedora infra does.
Dusty
Actually, I'd prefer we not expand use of that second "community-cloud" account, Dusty. Especially since we seem to be in an uncertain state for it pretty much constantly as our friends at AWS try to work out how to get it into their community umbrella.
Instead, Adam should make use of the existing Fedora AWS account where we can delegate access via IAM and using roles. Check in with the infra team -- they can follow an SOP https://docs.pagure.org/infra-docs/sysadmin-guide/sops/aws-access.html to make roles, but you'll still need to work with them to tag some resources and set up a policy so you can play in the right sandbox.
I have been using Amazon's "Free Tier" cloud machines to test EC2 images since 2016. Anyone with an Amazon account (which is free) can spin up a "free tier" machine to run the tests on. With access so easy, is it Fedora's job to provide users/testers with an account with which to test these images?
Geoff Marr IRC: coremodule
On Fri, Sep 13, 2019 at 3:18 PM Paul Frields pfrields@redhat.com wrote:
Actually, I'd prefer we not expand use of that second "community-cloud" account, Dusty. Especially since we seem to be in an uncertain state for it pretty much constantly as our friends at AWS try to work out how to get it into their community umbrella.
Instead, Adam should make use of the existing Fedora AWS account where we can delegate access via IAM and using roles. Check in with the infra team -- they can follow an SOP https://docs.pagure.org/infra-docs/sysadmin-guide/sops/aws-access.html to make roles, but you'll still need to work with them to tag some resources and set up a policy so you can play in the right sandbox.
--
Paul W. Frields
He / Him / His
Sr. Engineering Manager, Platform - Red Hat https://www.redhat.com/
314 Littleton Rd, Westford, MA 01886
pfrields@redhat.com / T: 9783921014 / GPG ID: 0xBD113717 https://www.redhat.com/
On Fri, Sep 13, 2019 at 4:56 PM Dusty Mabe dusty@dustymabe.com wrote:
On 9/13/19 4:51 PM, Adam Williamson wrote:
On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
On 9/13/19 3:44 PM, Adam Williamson wrote:
Hi folks! We're currently still discussing adjusting the release criteria to explicitly require Fedora releases to boot in EC2. Someone pointed out that if we're going to require that, it would be good if
we
had an account allowing EC2 access for testing, so individual Fedora testers don't have to potentially pay out-of-pocket just to test
Fedora
works in EC2. Does anyone know if we have an existing arrangement with Amazon for this? Thanks!
cc Paul Frields
I have access to an account I think we use explicitly for testing
Fedora in AWS.
Adam, if Paul doesn't point out any reason not to I can hand you some
credentials.
It'd be better for it to be something more robust and 'team-accessible' than just people emailing each other passwords, ideally :)
Encrypted of course :-P
It would be better to have it be something more managed but I don't have anything more robust that I can offer right now. Maybe fedora infra does.
Dusty
cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org 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/cloud@lists.fedoraproject.org
On Fri, 2019-09-13 at 16:02 -0600, Geoffrey Marr wrote:
I have been using Amazon's "Free Tier" cloud machines to test EC2 images since 2016. Anyone with an Amazon account (which is free) can spin up a "free tier" machine to run the tests on. With access so easy, is it Fedora's job to provide users/testers with an account with which to test these images?
There are limits on that, right? If you use more than the limits you get charged?
Yeah, you get 750 hours per month total for free, within the confines of the small amount of disk, RAM, and bandwidth you get. I always make sure to terminate any machines I spin up once I'm done testing so I don't get charged for going over that (which is hard to do, you have to run multiple machines). There's also a bandwidth cap, I think it's around 20gb total, then you start getting charged. 20gb is more than enough when running the five tests we have that are blocking for cloud; as long as the machines are terminated once tested, it's really hard to have an overage.
Geoff Marr IRC: coremodule
On Fri, Sep 13, 2019 at 7:49 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Fri, 2019-09-13 at 16:02 -0600, Geoffrey Marr wrote:
I have been using Amazon's "Free Tier" cloud machines to test EC2 images since 2016. Anyone with an Amazon account (which is free) can spin up a "free tier" machine to run the tests on. With access so easy, is it Fedora's job to provide users/testers with an account with which to test these images?
There are limits on that, right? If you use more than the limits you get charged? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org 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/cloud@lists.fedoraproject.org
On Fri, Sep 13, 2019 at 04:02:29PM -0600, Geoffrey Marr wrote:
I have been using Amazon's "Free Tier" cloud machines to test EC2 images since 2016. Anyone with an Amazon account (which is free) can spin up a "free tier" machine to run the tests on. With access so easy, is it Fedora's job to provide users/testers with an account with which to test these images?
Amazon is generously sponsoring the Fedora AWS account exactly to help us better provide Fedora OS images in their cloud. So, I don't think whether it's our job or not is the right question. It's something we're able to make available.
On Fri, Sep 13, 2019, at 5:17 PM, Paul Frields wrote:
Actually, I'd prefer we not expand use of that second "community-cloud" account, Dusty. Especially since we seem to be in an uncertain state for it pretty much constantly as our friends at AWS try to work out how to get it into their community umbrella.
Instead, Adam should make use of the existing Fedora AWS account where we can delegate access via IAM and using roles. Check in with the infra team -- they can follow an SOP https://docs.pagure.org/infra-docs/sysadmin-guide/sops/aws-access.html to make roles, but you'll still need to work with them to tag some resources and set up a policy so you can play in the right sandbox.
I think a related best practice here is to hand out credentials via STS: https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/prog-services-st... Particularly for things like "I just want to test this cloud-init package interactively"; no need to have a long-term credential there.
cloud@lists.stg.fedoraproject.org