----- Original Message -----
From: "Robyn Bergeron" <rbergero(a)redhat.com>
To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>
Sent: Wednesday, June 19, 2013 3:09:37 PM
Subject: Re: Test Results for F19 EC2 AMIs
----- Original Message -----
> From: "Sam Kottler" <skottler(a)redhat.com>
> To: "Fedora Cloud SIG" <cloud(a)lists.fedoraproject.org>
> Sent: Wednesday, June 19, 2013 3:02:05 PM
> Subject: Re: Test Results for F19 EC2 AMIs
>
>
>
> ----- Original Message -----
> > From: "Tim Flink" <tflink(a)redhat.com>
> > To: cloud(a)lists.fedoraproject.org
> > Sent: Wednesday, June 19, 2013 2:46:22 PM
> > Subject: Test Results for F19 EC2 AMIs
> >
> > We have a little over a week until the first F19 final go/no-go meeting
> > (where we decide whether or not the release is done) and there are no
> > posted results for F19 final AMI tests yet.
> >
> > If you have been testing the AMIs, please report your results. If you
> > haven't been testing them but are interested in doing so - please do.
> > Show stoppers for the AMIs are likely to be release blocking and the
> > sooner that those issues are discovered, the less likely that we'll
> > slip the F19 final release.
>
> In my opinion there should be an account for people to use to test the
> images. Access could be granted via IAM and resources could be limited that
> way.
Why go that route vs. simply publishing the images for anyone to test?
The advantage I see to what you're saying is that people don't have to
basically spend their own money to test images - but by the same token I
don't think we want to limit it only to that group.
Right, I think it'd be cool for us to cover the cost of testing our images. Even if
each person just got to create a m1.small or another type of small (cheap) instance,
it'd be great not to ask people to test beta software on their own dime.
I've set up stuff on the community-cloud account for usage with IAM before -
it's been a while but I seem to recall it was slightly tedious but
reasonable enough for one-off events (having test accounts for an event, for
example) - but if we started doling out access with every TC/RC I'd probably
want to figure out how to get that scripted into being part of releng
processes. I could probably write it but at some point I have to imagine
that what would take me a week would probably take someone else very very
little time :)
Thoughts? Garrett - since you're the one who helped me with the IAM stuff and
wrote the wiki instructions and whatnot - do you think that could somehow be
tied into FAS groups or something?
FAS integration would be excellent. I can do some research about external auth options
they have if someone else doesn't beat me to it.
-r
>
> >
> > To report results or to find test cases, please visit:
> >
> >
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
> >
> > This will redirect to the most recent spin (TC5 at the time of this
> > email).
> >
> > The relevant test cases are:
> > - QA:Testcase_EC2_AMI_Validation
> > - QA:Testcase_Boot_Methods_Xen_Para_Virt
> >
> > There are links to the specific test cases from the test matrices and
> > result reporting is just editing the wiki page (there are example
> > result formats on the page as well).
> >
> > Thanks,
> >
> > Tim
> >
> > _______________________________________________
> > cloud mailing list
> > cloud(a)lists.fedoraproject.org
> >
https://admin.fedoraproject.org/mailman/listinfo/cloud
> >
> _______________________________________________
> cloud mailing list
> cloud(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/cloud
>
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud