16:00:45 #startmeeting Fedora QA meeting 16:00:45 Meeting started Mon Jan 9 16:00:45 2012 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:51 #meetingname fedora-qa 16:00:51 The meeting name has been set to 'fedora-qa' 16:00:59 #topic Roll Call 16:01:18 Who's ready for some meeting fun time? 16:01:25 #chair adamw 16:01:25 Current chairs: adamw tflink 16:01:36 huh 16:01:40 darn xchat and suspend/resume. 16:01:41 * jsmith lurks (during another conference call) 16:01:41 * kparal opts in for fun time 16:01:42 i already started the meeting, in my own private bubble. :) 16:01:48 * jskladan is in 16:02:14 adamw: a meeting of one! 16:03:19 * brunowolff is here 16:03:39 tflink: keeps the riff-raff out! 16:04:06 adamw: and I opened the flood gates :) 16:06:21 alright, so - let's get going 16:06:27 #topic f16 retrospective task update 16:06:49 this is just my excuse to bug everyone about the stuff that came from the f16 retrospective, and remind us all it still needs doing :) 16:07:02 https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective#Recommendations 16:07:09 I haven't updated the 'closed' statuses there, btw. 16:08:08 do you want to go through the individual tickets or just have us pipe up on status? 16:08:33 no need to review each one i don't think 16:08:42 just note that out of nine qa tickets, two are closed 16:09:27 most of the others look like they have some activity; #151 (pschindl) and #259 (twu) don't 16:09:29 I'm thinking that the Xen ticket can be closed, I should have looked at the first proposal more closely 16:09:34 anyone know where they're at? 16:09:51 tflink: that's fine, if the current test is complete and comprehensive 16:10:26 I pinged pschindl 16:10:27 jskladan: kparal: any idea of pschindl's status on his ticket? 16:10:30 ah, thanks 16:10:49 I don't 16:10:54 know 16:11:55 let's come back to it when he responds 16:12:28 yup 16:12:52 overall looks like we're doing okay on those tasks, so that's good. remember, we have until alpha starts up in earnest to get them done. 16:13:22 #info two tickets are closed already and most of the others are being worked on actively 16:13:35 #topic FUDCon Blacksburg notes 16:13:48 hey, jay 16:13:53 * j_dulaney appologizes for tardiness 16:13:58 that's all good 16:14:05 we've just been over the retrospective tickets so far 16:14:12 anything you wanted to add on that topic? 16:14:25 I'll check the logs and comment on the ML 16:15:07 okay 16:15:18 so, for fudcon: doesn't look like there are any big issues 16:15:21 What's been said so far on FUDCon 16:15:31 nothing, i'd just set the topic when you waltzed in :) 16:15:40 good lord, the tflinks are spawning 16:15:46 i think he's got us surrounded 16:16:11 LOL 16:16:25 woah, that's strange 16:16:36 * j_dulaney is reminded of the British being attacked by Zulu 16:17:07 ah, a classic pincer movement 16:17:12 watch out for tflink__ on the right flank 16:17:24 LOL 16:17:47 :) 16:17:50 so as i was saying... 16:17:58 looks like there's no problems with fudcon NA 16:18:20 for those playing along at home, it's happening this weekend in blacksburg, which is in virginia (at least i hope it is, or i'm going to the wrong darn airport) 16:18:23 adamw: If only all of us could say that :-) 16:18:48 tflink and I will be on hand to ruin QA's reputation and create gigantic bar bills for jsmith 16:18:56 LOL 16:19:01 red_alert will also be there 16:19:08 * j_dulaney is going to be there 16:19:19 and j_dulaney...yep 16:19:28 I'll try to run a bit of an AutoQA hackfest on Friday 16:19:38 awesome 16:19:49 i guess tflink may be able to help out there 16:19:54 * j_dulaney needs to get new headphones; these temp cheapos suck 16:19:55 i thought sunday was for hackfests and such 16:19:56 ? 16:20:01 j_dulaney: what's the agenda of that hackfest? 16:20:05 Friday, too 16:20:12 kparal: Self testing 16:20:25 okay 16:20:27 * j_dulaney keeps meaning to blog about it 16:20:33 yeah, blog is always a good idea 16:20:37 I'll be looking out for it 16:20:38 thanks 16:20:41 i also need to remember to blog about it :) 16:21:09 so aside from that, we have the anaconda ui testing hackfest planned for monday, red_alert is taking care of that 16:21:23 Sunday 16:21:27 erf. yeah. 16:21:35 it would be a lonely hackfest on monday... 16:21:48 Well, probably be some students there 16:21:51 and i think various of us have presentations to propose. 16:22:12 yeah, wondering where the Major Battles of the Zulu Wars class went wrong ;) 16:22:22 yeah, the barcamp proposal list looked a bit sparce last night 16:22:41 tflink_: usually a lot of people don't bother listing talks ahead of time. 16:22:51 or writing them ahead of time, in some cases (koff koff) :P 16:23:32 but looks like we more or less have our plans in order, so that's good. 16:23:49 i recommend making sure to eat with jsmith as much as possible so that red hat pays for your food. protip! 16:24:08 Indeed, especially as broke as I am 16:24:42 awesome. so, any outstanding issues / questions on fudcon? 16:25:16 Where/how/when should we meet up? 16:25:23 QA party 16:25:48 With hot dogs 16:26:01 adamw: Thanks man :-) 16:26:18 j_dulaney: good question...maybe we should aim to do a group lunch on one of the days? 16:26:46 Indeed 16:27:01 i'm going to try and get a t-mobile prepaid sim this time, so i should have phone comms 16:27:03 * j_dulaney admits that he doesn't know what y'all look like 16:27:30 j_dulaney: tflink and I and red_alert all know each other 16:27:34 So, find one, find all? 16:27:41 yeah 16:27:49 I am off to a work meeting. 16:27:50 and usually it's not THAT hard to find people at fudcon; it's not so big 16:27:57 alrighty bruno, cya later 16:28:12 (just hang out at the bar... people will come to you. ;) 16:28:24 pretty much everyone will be in one place during the initial keynote and meeting proposal period for e.g 16:28:49 Indeed 16:28:50 we could aim to try and at least identify each other then, and then meet up again for lunch after the first session of talks, perhaps. 16:29:40 sound good? 16:29:47 sounds like a plan to me 16:29:47 Indeed 16:30:02 * j_dulaney notes that it is likely he'll be the biggest there 16:30:08 With a beard 16:30:40 ah, that'll make you stand RIGHT out in a meeting of *nix geeks ;) 16:30:50 LOL 16:31:11 alright, we'll go with that plan. i'm sure it'll work out somehow. 16:31:33 Too bad there won't be any jlaska 16:31:37 * j_dulaney knows him 16:31:54 yeah, it would've been good if james was there 16:32:29 wwoods will be there, though. with an awesome badge. 16:33:13 alrighty, moving on 16:33:16 #topic AutoQA update 16:33:36 kparal, tflink - what's the news? remember it's been like a month since the last meeting. dec 11th, I think. 16:33:51 I have some summary 16:33:56 * kparal taking the mic 16:34:08 The last meeting was a long time ago, so I'll include also some items that happened before Christmas. 16:34:23 1. I added support for caching proxy inside AutoQA. This is useful mainly in devel environments where we don't have too much of bandwidth. Subsequent test executions are very fast. We can also share these files between multiple developers in an office by deploying the proxy on a shared computer. 16:34:47 #chair kparal 16:34:47 Current chairs: adamw kparal tflink 16:34:51 2. There has been several problems in sending out (optin and regular) emails from our test clients. Hopefully I corrected all of them and optin email should be flowing once again. 16:35:06 big thanks to jlaska here 16:35:08 #info kparal added caching proxy support inside AutoQA 16:35:30 #info kparal fixed several issues with sending out opt-out and opt-in emails 16:35:32 3. autoqa-results mailing list is revived. I cut down the amount of traffic substantialy by only sending full logs from test results. Currenly only emails from staging server are routed there. Production server still generates too much traffic, I'm working on it. I'll probably implement a configurable blacklist on these emails. 16:36:15 4. After re-enabling autoqa-results I spotted (too many) problems. Most of them should be reported as Hot issues in our Trac, free to take :) 16:36:17 #info autoqa-results list is back, now with fewer messages! 16:36:32 my mail client can open that folder again! 16:36:38 :) 16:36:57 for some reason, it doesn't handle folders with >10k messages all that well 16:37:10 sounds like a productive period, thanks kparal 16:37:14 tflink_: weak! 16:37:14 very weird email client 16:37:20 5. AutoQA logo changed to Marvin the Paranoid Android, yay! 16:37:31 #link http://www.iconfinder.com/icondetails/6392/128/automator_marvin_robot_icon 16:37:36 It was about time for some optimistic imagery! 16:37:47 Win 16:38:15 did we address the, er, legal concerns there? 16:38:24 it's GPL icon 16:38:25 * tflink_ is still a little concerned about copyright on that one 16:38:42 tflink_: shoot 16:38:58 kparal: true but I don't think that means we can use a copyrighted character from a secondary source 16:39:14 I sincerely doubt that the person who uploaded that icon had the rights to assign copyright 16:39:26 even if the person who drew the image licenses it GPL or whatever, if it resembles the movie Marvin too much, the movie studio would have rights. 16:39:28 I assumed it was uploaded by the author 16:39:45 meaning I can't draw _my own_ mickey mouse? 16:39:48 we couldn't use Mickey Mouse as the logo just because we used a drawing that wasn't actually by Disney - if it looks too much like Mickey, Disney has the rights. 16:39:53 kparal: ..exactly. 16:40:01 you can *draw* it 16:40:04 kparal: probably not 16:40:14 is this the correct universe I live in? 16:40:17 but using it 'commercially' (which is a very broad stroke) is troublesome. 16:40:21 alright, I'll ask spot about it 16:40:44 he's the license guru in Fedora, right? 16:40:49 Indeed 16:40:50 he's our fake lawyer, yeah. 16:41:02 and he knows how to talk to real lawyers :) 16:41:15 it was such a pretty logo! :/ 16:41:19 life sucks, huh 16:41:21 alright, moving on 16:41:30 6. Upgradepath displayed wrong results for multi-build updates. The fix is comitted but not deployed yet. 16:41:43 and that's all the news I know of 16:42:00 #info kparal proposed using an icon that rather resembles the version of Marvin from the recent H2G2 movie as AutoQA's icon, tflink and adamw raised legal concerns 16:42:17 #action kparal to follow up with spot on the legal questions around the marvin logo 16:42:27 kparal: cool, thanks 16:42:32 tflink_: any news to add? 16:42:43 is remote_install autoqa related? 16:42:52 nope 16:43:02 it should have its own section I believe 16:43:08 then nope, nothing to add - I've been spending most of my time on that 16:43:09 no, but we can talk about it in open discussion 16:44:01 anyone else have any autoqa news / qs? 16:44:48 okay then 16:44:56 #topic open floor 16:45:11 sounds like tflink would like to update us on remote_install progress? 16:45:19 sure 16:45:26 #topic open floor - remote_install 16:45:31 take it away! 16:45:49 I've been working on a demo for the remote installation system proposed last year 16:45:54 #link https://fedoraproject.org/wiki/User:Tflink/remote_installation_testing_proposal 16:46:24 the demo system is mostly ready - I've been trying to figure out hosting details for a public demo 16:46:36 #link http://supermegawaffle.com/remote_install/index.html 16:46:45 #link https://github.com/tflink/remote_install 16:46:46 right now it's running behind the RH firewall, as it was easy for us to find resources there. 16:47:25 the current plan is to run a demo using public cloud infra once I write code to interface with the cloud we're going to use 16:47:50 You might could check with rbergeron 16:47:51 if we go forward with the idea as more of a demo, we'll work out something using fedora infra 16:48:10 Maybe figure out something using ec2 or the like 16:48:20 j_dulaney: yup, that's 'public cloud' 16:48:25 j_dulaney: ec2 is too expensive for this 16:48:32 Ah 16:48:43 their billing and infra setup doesn't lend well to installation testing 16:49:09 ohi is a KVM based public cloud that is ~ 50% cheaper and less hacky 16:49:21 50% cheaper for this use case, anyways 16:49:57 that and I really didn't want to estimate iops for EBS 16:50:00 :) 16:50:18 Cheaper sounds better 16:50:27 EC2 billing is complicated :-/ 16:50:37 will it be possible to do size and checksum tests on the ISOs? (handy for avoiding download, especially for large spins) 16:51:04 robatino: with the remote_install system? not sure, to be honest 16:51:16 I don't know what would be needed for that off the top of my head 16:51:44 but my instinct says that it would be a sub-optimal way of doing things 16:51:56 and that AutoQA would be a better way to do that 16:52:30 but I'll be sending out an announcement when we have timing more solid for the demo 16:52:43 coolbeans. 16:52:44 right now i can do checksum tests using my account on secondary01 without downloading, AutoQA plans to just download them last i heard 16:52:54 if you have access to the RH VPN and want to try it out, let me know 16:53:01 is there anywhere you could do with help, or is it rolling along nicely? 16:53:32 I think that things are going well, I just need to get the cloud interface written 16:54:10 * tflink_ wishes that there was a python interface for the elastichosts API 16:54:25 please don't get sidetracked into writing one. :) 16:54:49 a compete one? no. Just as much as I need for the demo 16:54:57 cool. 16:55:00 I've already spent more time on this than I'd like for a demo 16:55:03 tflink_: you might ping skvidal... he has some scripts to build/tear down/run things on cloud instances. 16:55:14 nirik: will do, thanks 16:55:19 * pschindl is finaly here (sry, I stuck on diploma thesis and forgot to join) 16:55:49 What's up, pschindl 16:56:19 I think that's it for remote_install, though 16:56:35 tflink_: Maybe, for long term, could we hook this to AutoQA somehow? 16:56:50 j_dulaney: let's cross that bridge if/when we get there 16:56:57 Righteo 16:57:02 for now, it's just a demo and may not live past the initial trial 16:57:10 j_dulaney: deadline of thesis is this week and it's not done 16:57:39 okay, back to... 16:57:41 #topic open floor 16:57:51 do we have any other open floor topics? anything anyone's concerned about? 16:58:26 * j_dulaney is good 16:59:30 okey dokey 17:00:37 setting the fuse for one minute... 17:02:33 thanks for coming, all! 17:02:38 Go QA! 17:02:45 man, these lousy defective ACME fuses... 17:02:48 #endmeeting