#fedora-meeting: Fedora QA meeting

Meeting started by adamw at 14:31:02 UTC (full logs).

Meeting summary

  1. Roll Call (adamw, 14:31:11)
  2. ARM release criteria / test matrix adjustments (adamw, 14:37:22)
  3. ARM: Which images will we build for which milestones? (adamw, 14:39:50)
    1. plan is to build all ARM images for all milestones (same set as F19, plus Desktop) - dgilmore (adamw, 14:41:49)

  4. ARM: Which of the images will be release-blocking? (adamw, 14:43:03)
    1. AGREED: release blocking image set for ARM will consist of minimal and KDE images for F20 (adamw, 14:49:21)
    2. vfat image will work on all hardware, so doing the vfat tests is the most important thing (adamw, 14:50:07)

  5. ARM: What requirements do we want to apply to the images? (adamw, 14:50:23)
    1. some criteria are just irrelevant: installer and Xen/cloud stuff (adamw, 14:51:56)
    2. dual boot with windows is irrelevant (adamw, 14:52:09)
    3. https://fedoraproject.org/wiki/Fedora_Release_Criteria?rd=QA:ReleaseCriteria (handsome_pirate, 14:52:18)
    4. calxeda is an important platform that requires anaconda for deployment, so we do want to block on anaconda at least for a standard singel disk partitioning setup (adamw, 14:59:25)

  6. ARM: Do we need to add or revise any test cases to cover this? (adamw, 15:02:13)
    1. https://fedoraproject.org/wiki/Test_Results:Fedora_19_Final_RC3_Install (adamw, 15:02:31)
    2. https://fedoraproject.org/wiki/Test_Results:Fedora_19_Final_RC3_Base (adamw, 15:06:56)
    3. https://fedoraproject.org/wiki/QA:Base_validation_results_template (adamw, 15:07:41)
    4. looks like https://fedoraproject.org/wiki/QA:Testcase_base_initial_setup will need adjustment (adamw, 15:09:22)
    5. on a quick overview it looks like what we have to do is edit initial-setup test case, check for install test cases that simply don't apply, but other than that we're good (adamw, 15:11:14)

  7. ARM: How should we express the requirements in the criteria and validation test pages? (adamw, 15:11:46)
    1. we're mostly wrapped up on ARM but mattdm has popped out (adamw, 15:12:41)

  8. ARM: Any other business? (adamw, 15:12:53)
    1. ARM folks will try to do some dry runs through the validation process before we hit TC1 to catch any missing coverage (adamw, 15:16:38)

  9. Visible Cloud release criteria / test matrix adjustments (adamw, 15:17:39)
  10. Cloud: What precisely are the configurations we are requested to test? (adamw, 15:19:18)
    1. you can test cloud images locally (adamw, 15:21:18)
    2. we have a fedora infrastructure openstack environment, and mattdm believes that working in that cloud env is a must (adamw, 15:21:49)
    3. working on a local test system is NOT a release requirement - it's just a convenience for testing. we can ship if that doesn't work. (adamw, 15:23:35)
    4. working on EC2 is also a release requirement (adamw, 15:24:20)
    5. fedora infra openstack cloud and ec2 are the two environments which matt sees as being 'release requirements' (adamw, 15:26:57)

  11. ARM: Do we have the necessary accounts, systems, knowledge to do this testing? (adamw, 15:27:16)
  12. Cloud: Do we have the necessary accounts, systems, knowledge to do this testing? (adamw, 15:27:52)
    1. we can have cloud folks manually grant access to the fedora infra cloud to sufficiently trusted people, and use trystack to 'gate' that (if you want to be an openstack tester, you can start out on trystack and we'll give you privs later) (adamw, 15:30:48)
    2. there is a community account for EC2 which some people have access to: Robyn is the gatekeeper (adamw, 15:33:14)
    3. cloud-init is sounding like the major bit of the process that is likely to be breaking: the rest of the cloud stuff is very similar to a typical minimal deployment (adamw, 15:35:05)
    4. we are going to want to develop some more specific requirements around cloud-init configuration magic, but that's for post-f20 (adamw, 15:36:58)

  13. Cloud: What precise functionality do we require from the tested configurations? (adamw, 15:37:37)
  14. Cloud: What precise functionality do we require from the tested configurations that is particular to cloud images? (adamw, 15:38:08)
    1. ssh key injection, logging into fedora account with ssh key, resizing of root filesystem (adamw, 15:39:40)
    2. there is an idea of pulling updates from s3 rather than public mirrors to save people's external transfer costs, but that is turned off for now as it was costing RH a lot of money to populate the s3 server (adamw, 15:40:12)
    3. AGREED: we care about "installation" (deployment) and base matrices for cloud. we do not care about desktop. (adamw, 15:41:52)
    4. AGREED: badge proposal: use of 'the s word' in a QA meeting (adamw, 15:43:10)

  15. Cloud: What changes are needed to the release criteria and test matrices to reflect this? (adamw, 15:43:26)
    1. overview plan: we need the same 'direct deployment' tests as we need for ARM, the initial-setup test is a no-go for cloud, and we add a (set of) cloud-init test(s) which basically cover initial-setup territory for cloud (adamw, 15:45:50)
    2. regularly updated cloud images are something that's of interest but probably down the road a ways (adamw, 15:48:57)
    3. ACTION: adamw to talk to mattdm and rbergeron about getting people access to the testing platforms (adamw, 15:51:00)
    4. viking-ice and gholms may be interested in helping with testing and need access (adamw, 15:51:55)
    5. ACTION: adamw to send call for cloud testers to the list (adamw, 15:52:40)

  16. Open floor (adamw, 15:57:27)
    1. tflink will try setting up a mumble server for us to use for stuff and see how that goes (adamw, 15:58:42)
    2. https://badges.fedoraproject.org/ (mattdm, 16:00:47)
    3. https://fedoraproject.org/wiki/User:Johannbg/Systemd/cgroup-changes (Viking-Ice, 16:01:34)
    4. this shouldn't break anything too crazily but we should keep an eye on it for alpha (adamw, 16:02:35)
    5. So we have backward incompatible systemd cgroup changes in rawhide which will break units that take advantage of the old controller stuff (adamw, 16:02:44)
    6. http://coreos.com/ (adamw, 16:06:50)


Meeting ended at 16:10:55 UTC (full logs).

Action items

  1. adamw to talk to mattdm and rbergeron about getting people access to the testing platforms
  2. adamw to send call for cloud testers to the list


Action items, by person

  1. adamw
    1. adamw to talk to mattdm and rbergeron about getting people access to the testing platforms
    2. adamw to send call for cloud testers to the list
  2. mattdm
    1. adamw to talk to mattdm and rbergeron about getting people access to the testing platforms


People present (lines said)

  1. adamw (140)
  2. handsome_pirate (23)
  3. dgilmore (19)
  4. zodbot (14)
  5. kparal (14)
  6. red_trela (13)
  7. akshayvyas (11)
  8. kashyap_ (10)
  9. tflink (9)
  10. Cerlyn (8)
  11. Viking-Ice (7)
  12. jsmith (6)
  13. mattdm (6)
  14. pbrobinson (4)
  15. jskladan (3)
  16. pwhalen (3)
  17. ctyler (2)
  18. halfline (2)
  19. fossjon (2)
  20. sgallagh (1)
  21. pschindl (1)


Generated by MeetBot 0.1.4.