I completely forgot about this with all the other F18 stuff going on but has anyone been testing the F18 AMIs? If so, are they working? If not, are there bugs filed about the parts that aren't working?
Tim
On Thu, Jan 03, 2013 at 04:55:59PM -0700, Tim Flink wrote:
I completely forgot about this with all the other F18 stuff going on but has anyone been testing the F18 AMIs? If so, are they working? If not, are there bugs filed about the parts that aren't working?
I have been, although with a lot of packages changing underneath right up to the last minute they have not been given a thorough workout.
The AMI ID of the TC3 build is ami-3d2fa254, and you can definitely look at that, but Release Engineering should be cooking up a newer version based on RC1 any minute now and it'd obviously be more useful to test that. Will post (or Dennis will) when they're available.
Not coincidentally at all, I'm working on a proposal for doing nightly images in a more automated fashion for F18, and getting those images tested in a more regular way. Your suggestions welcome. (Rough idea: automatically build in koji either nightly or weekly. Automatically push to Fedora local cloud and run unit tests. Also, AMIs available in Amazon at alpha and beta.)
On Fri, 4 Jan 2013 14:33:56 -0500 Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Jan 03, 2013 at 04:55:59PM -0700, Tim Flink wrote:
I completely forgot about this with all the other F18 stuff going on but has anyone been testing the F18 AMIs? If so, are they working? If not, are there bugs filed about the parts that aren't working?
I have been, although with a lot of packages changing underneath right up to the last minute they have not been given a thorough workout.
I ask because xen cloud image issues have the potential to block release. I know that I haven't been paying much attention to the cloud images for F18 and I suspect that most of the QA regulars are in a similar boat - consumed with other F18 testing stuff. I just wanted to make sure that there weren't major issues lurking in the AMIs.
The AMI ID of the TC3 build is ami-3d2fa254, and you can definitely look at that, but Release Engineering should be cooking up a newer version based on RC1 any minute now and it'd obviously be more useful to test that. Will post (or Dennis will) when they're available.
Not coincidentally at all, I'm working on a proposal for doing nightly images in a more automated fashion for F18, and getting those images tested in a more regular way. Your suggestions welcome. (Rough idea: automatically build in koji either nightly or weekly. Automatically push to Fedora local cloud and run unit tests. Also, AMIs available in Amazon at alpha and beta.)
Does that mean that we'll have more instance store images or are we keeping with the EBS-only images that we have been producing?
I'm curious what you have in mind for how the tests would be run (framework, runner, language etc.), how you'd store the results, how the results would be analyzed and what kinds of tests you were interested in running.
Tim
On Fri, Jan 04, 2013 at 01:31:40PM -0700, Tim Flink wrote:
Does that mean that we'll have more instance store images or are we keeping with the EBS-only images that we have been producing?
I don't have a strong opinion. Anyone?
The Amazon Marketplace images, once we get that approved, will be EBS-backed.
I'm curious what you have in mind for how the tests would be run (framework, runner, language etc.), how you'd store the results, how the results would be analyzed and what kinds of tests you were interested in running.
I expect we'd launch them from Jenkins. But we could start with something more ad hoc if that's easier.
For initial tests, "does it boot and can I log in" is a good start. Next, it'd be cool to script up as many of the blocker criteria as can be tested in that way. (Many can't, as they mostly involve the install process itself.) Then, we could start adding basic tests for core packages. Probably all that would be handled by the QA group.