15:00:55 #startmeeting Fedora QA meeting 15:00:55 Meeting started Mon Aug 19 15:00:55 2013 UTC. The chair is handsome_pirate. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:55 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:06 well now it's not :P 15:01:11 #chair adamw 15:01:11 Current chairs: adamw handsome_pirate 15:01:13 ha! 15:01:15 thansk 15:01:16 #chair tflink 15:01:16 Current chairs: adamw handsome_pirate tflink 15:01:20 #meetingname fedora-qa 15:01:20 The meeting name has been set to 'fedora-qa' 15:01:24 #topic Roll call 15:01:27 * threebean is here! 15:01:27 #chair randomuser 15:01:27 Current chairs: adamw handsome_pirate randomuser tflink 15:01:37 * pwhalen is here 15:01:38 ahoyhoy folks, who's around to A some Q? 15:01:40 * jskladan lurks 15:01:43 * mkrizek is here 15:01:48 #topic roll call 15:01:56 handsome_pirate, I'm not staying :( 15:01:58 * handsome_pirate waves from his crows nest 15:02:07 * pschindl is here 15:02:08 * Cerlyn is here 15:02:14 * threebean is still here 15:02:19 * nirik is lurking 15:03:26 threebean: i'm afraid I *probably* won't be able to derail this meeting onto the topic of badges 15:03:30 though i will of course try my hardest 15:03:39 adamw: LOL 15:03:47 * threebean is here to help ;) 15:04:12 speaking of, if you haven't seen badges yet, go to https://badges.fedoraproject.org ! 15:05:41 alrighty, looks like that's everyone 15:05:54 #topic ARM and Visible Cloud validation process change review 15:06:32 so if you check the meeting page at https://fedoraproject.org/wiki/QA/Meetings/20130819 i've included more detail on this 15:06:51 as we're scheduled to do TC1 tomorrow (though...we may not get there...but that's for later) it'd be good to get the process changes for ARM and Cloud in ASAP 15:07:12 so i thought i'd throw a spot on the schedule for anyone to air any concerns over the general approach or implementation in 'real time' 15:07:28 did people manage to take a look at the proposals when I sent them in? or not had time yet? 15:07:30 adamw: Shall I spew about what I'm working on? 15:07:41 handsome_pirate: not for now, let's focus on f20 15:07:48 adamw: You saw my concerns 15:07:50 this is all about gettin' to tc1 15:07:52 adamw: Roger 15:08:42 I have one thing to note... 15:09:31 note ahead 15:09:31 the cloud validation mentions the fedora infra private cloud. I'm not sure I fully like that, as it means we need to freeze it and always keep it production ready for testing. ;) 15:09:46 could we make it more general 'openstack cloud' or something/ 15:10:06 in case people want to test it in their own clouds or in case ours is busted 15:10:30 nirik: the downside to doing that is we wind up with a problem if it doesn't run in one openstack instance but does in another, or something 15:10:35 we wind up having to make hand-wavy judgement calls 15:10:38 is that at all likely? 15:10:58 true. It also brings up: should version matter? 15:11:13 ie, our cloud is openstack folsom, but thats no longer current... 15:11:20 I mean it should work in any of them, but... 15:11:59 perhaps ask cloud sig folks for their thoughts on what should be used to test/block? 15:12:29 that sounds like a reasonable plan 15:12:38 mattdm: do you happen to be around? 15:13:05 for initial Alpha purposes we can just say 'an OpenStack cloud' and refine the definition later, maybe? 15:13:14 wfm 15:13:19 +1 15:13:25 However 15:13:45 It may be good to have a benchmark 15:14:06 ie, "We know it works under this setup" 15:15:19 * handsome_pirate wonders by the crickets if he is making sense 15:15:28 handsome_pirate: that would be the fedora cloud most likely, which was what we discussed at the meeting last week i think 15:15:49 * nirik really needs to upgrade our cloud. 15:16:02 * nirik really also needs an extra 12 hours in each day 15:16:23 =) don't we all 15:16:37 heh 15:16:46 any other notes on the proposals as currently designed/written? 15:17:13 None here 15:17:46 First day of calculus 15:17:55 Calc 2 15:19:14 everyone else still reading, no problems, or bored? :) 15:21:01 adamw, I think the arm changes look good. Do we need to make any changes on the initial-setup test case, I think you like the unified version 15:21:02 * jskladan is bored, since he has not seen a problem to brag about... 15:21:36 pwhalen: i thought the i-s combined case looked good, nice work 15:21:44 was just planning to go ahead and pull that in 15:21:58 +1 15:22:05 adamw, I have yet to go over the matrix in detail to look at what doesnt apply, I can do that today 15:22:14 that'd be a great help 15:22:24 i think base and desktop should apply, only install needs review 15:22:30 right, will do 15:22:50 ok, so it sounds like we're almost done for a first cut for ARM 15:23:30 we still need to catch up a bit for cloud. i guess we need an 'initial deployment' test case for cloud with a little matrix like the arm one (it'll be smaller, though - just EC2 and OpenStack) and the base matrix would also apply, install and desktop would not 15:23:32 sound sane? 15:27:03 * adamw talks to himself some more 15:27:32 * nirik nods. sounds good to me. 15:27:43 * adamw bursts with gratitude 15:28:00 sigh, where's a viking when you need one 15:28:48 alright then, let's move it along 15:28:59 #action adamw to draft the final Cloud changes today 15:29:35 proposed #agreed changes proposed so far for Cloud and ARM are accepted with the change to just mentioning OpenStack rather than the specific Fedora OS instance, and will be pushed out 15:29:45 ack/nack/WHATTHEHELLAREYOUTHINKING 15:30:17 ack 15:30:26 ack 15:30:30 ack 15:30:36 WHATTHEHELLAREYOUTHINKING 15:30:40 :P hi drago 15:30:44 ;) 15:31:37 alrighty, thanks folks - let's pull the giant lever 15:31:41 #agreed changes proposed so far for Cloud and ARM are accepted with the change to just mentioning OpenStack rather than the specific Fedora OS instance, and will be pushed out 15:32:57 #topic Fedora 20 Planning 15:33:08 sooo, here's where we are with F20: not looking great 15:33:09 * handsome_pirate comes in with a late ack 15:33:19 * handsome_pirate was distracted by class 15:33:31 thanks pirate 15:34:01 if sirs and madams would care to examine the current blocker list at https://qa.fedoraproject.org/blockerbugs/milestone/20/alpha/buglist , you will notice a heaping pile of showstoppers 15:34:18 well, at least two of them, 983319 and 997690 15:34:32 #info there are two anaconda showstoppers for F20 Alpha at present 15:34:38 of course, we could still roll ARM and cloud images, I guess :P 15:34:45 Aye 15:35:14 but no, seriously, i'd plan to hold alpha tc1 until we can get those fixed and at least get through anaconda somehow in a smoke test - sound sane? 15:35:27 Indeed 15:35:48 * jskladan is +1 for the idea of somewhat-working-anaconda-to-start-with 15:36:07 Sane idea, indeed 15:36:26 #agreed we'll hold off on doing Alpha TC1 until the known anaconda showstoppers are fixed 15:36:34 #action adamw and pschindl to work with anaconda team on that 15:36:50 is anyone aware of any other screaming issues for Alpha that aren't being tracked on the blocker list? 15:37:02 the Bluez stuff sounds fun but should at least not be preventing any images from composing, i think 15:37:24 * handsome_pirate doesn't see how it would 15:37:39 Are lives booting right now? 15:37:46 * handsome_pirate doesn't have a way to test 'em 15:37:51 I can try and look at that livecd thing... but if someone else can before me that would be lovely. 15:38:07 last live I composed booted fine, even with enforcing on 15:38:16 that was friday iirc 15:38:23 nirik: Livecd thing? 15:38:30 nirik: same question? 15:38:34 * nirik almost ignored that bug due to unrelated commentary 15:38:40 the initial setup running on lives. 15:38:46 998083 15:38:48 oh, that 15:38:53 it should be an easyfix in spin-kickstarts 15:39:09 i just didn't get around to it over the weekend. when you move that bit, make sure it stays within the bounds of the livesys script :P 15:39:11 yeah, just needs someone to look at where to move the config done thing to correctly 15:39:15 yep. 15:41:22 #action nirik or adamw to fix spin-kickstarts user creation bug 15:41:44 alrighty 15:41:48 sounds like we have some plans 15:42:37 * handsome_pirate wonders if Viking is still recovering from Flock 15:43:20 possibly :) 15:43:25 or he's out shooting something 15:43:35 welp, in that case, let's move on to: 15:43:38 #topic Open Floor 15:43:42 anyone got anything to discuss? 15:43:48 oh! 15:43:49 WOW viking came to FLOCK damn 15:44:16 we talked at flock about measuring fedmsg reliability by checking the number of taskbot tasks run against the number of koji builds completed. 15:44:27 adamw: RE: Tracker app, I opened a thread on design, EOF 15:44:37 yeah i saw it, thanks 15:44:50 I was wondering if someone could point me at taskbot, especially some place where I could query the number of tasks run (and the list of all tasks too, if possible). 15:44:54 Southern_Gentlem: yeah, we met him at last! he's very nice in person 15:45:03 threebean: Hold one 15:45:08 is there a tflink or a kparal in the house? 15:45:40 threebean: It's on tflink's personal boxen, so I don't know if you can query from your end 15:45:47 i'm not sure taskbot is actually at the point of running tasks yet. so far the link i've been pointing to is simply tflink's blog: http://tirfa.com/an-initial-idea-for-taskbot.html 15:45:50 adamw: kparal is on PTO, AFAIK 15:45:54 oh yeah, i forgot 15:46:02 oh and tflink told me he'd be out today 15:46:24 threebean: i'm afraid you're stuck with the monkey :) if you want to test out your idea and it's not too much work you could do it against autoqa, which is the system we actually have in production 15:46:29 threebean: adamw: once again AFAIK - taskbot is not running, it's in a proof-of-concept design state 15:46:32 taskbot is the proposed replacement for/rewrite of autoqa 15:46:38 ok.. i guess I'll correspond with tflink later when he's around :) 15:46:41 jskladan: yeah, that's my understanding too 15:46:43 threebean: and tflink has some code running on his private machines 15:46:45 maybe he and I can cook up a script to run on his end. 15:46:51 threebean: for autoqa, see http://autoqa.fedoraproject.org/ 15:47:10 cool, cool. thanks all :) 15:47:11 threebean: autoqa should be running at least one test on every koji build, afaik 15:47:19 threebean: http://taskbot.tirfa.net/ 15:47:20 some it only runs on bodhi submissions 15:47:26 handsome_pirate: aha, nice. 15:47:38 * handsome_pirate had to take a moment to find it 15:47:55 threebean: I also have a local instance I can get going 15:48:25 threebean: So, ping me this afternoon, say three hours from now, and we'll chat 15:48:33 * threebean nods 15:48:34 and tflink should be in tomorrow or later today 15:48:38 * threebean will be around 15:48:39 threebean: I will be AFK for an hour or so 15:49:11 oh, hey, one thing I should note for anyone who hasn't heard of it somehow or other: 15:49:20 #info adamw will be on vacation from August 25 to September 16 15:49:32 prepare for the dark days! 15:49:33 i'll be checking in via laptop every so often but i really will aim to be not working most of that time 15:50:07 currently the plan is for pschindl to try and handle the compose requests, i'm sure he'd welcome any help in keeping up to date with those and in touch with anaconda team and fpl and fpm (which is what i usually do) 15:50:24 er, fpm=program manager=jreznik 15:50:48 i'm sure andre will be on top of sending out announces and setting up matrices as usual 15:51:11 everything else should grind along just as/more smoothly without me in the way :P 15:51:17 I guess we'll be able to handle some of the anaconda devs in Brno - hopefully they won't be able to catch and strangle us before we tame them :) 15:51:21 hehe 15:51:29 for f20 we do have a bug on arm that may be considered a blocker, it only affects tegra2(trimslice) from our supported list 15:51:39 https://bugzilla.redhat.com/show_bug.cgi?id=985342 15:51:44 pwhalen: i believe that's going to be one of our blocking platforms, isn't it? if so, throw it on the list 15:51:49 be good to have a test case 15:52:03 oh right, that one. someone warned me not to run rawhide on my trimslice indeed. 15:52:17 adamw, we have yet to finalize that list 15:52:31 looks like it's in needinfo atm waiting for something from the reporters' side 15:52:55 #info https://bugzilla.redhat.com/show_bug.cgi?id=985342 may be our first ARM release blocking bug 15:53:04 I pinged Kyle about it, he hasnt had a chance yet 15:53:06 pwhalen: you know how to put it on the alpha blocker list, right? 15:53:38 I think so, I'll figure it out 15:54:58 added 15:55:05 awesome 15:55:15 * adamw sad there is no fedmsg event 15:55:24 * adamw sneaks an entry on tflink's todo 15:55:49 we should definitely run blocker review this week, if only to put the obvious ones on the accepted list 15:58:37 adamw, sure, when would that be held? 15:58:40 wednesday 15:58:53 time? 15:59:53 er 16:00:23 16:00 UTC 16:01:04 adamw, wfm 16:01:16 thanks 16:01:22 alrighty then folks 16:01:31 thanks everyone for coming! looks like our project needs us 16:02:49 thanks adamw et al 16:03:28 * adamw sets Quantum Fuse 16:04:14 oh yeah, will there be a release name? 16:05:04 http://devopsreactions.tumblr.com/post/47609397208/on-call-saturday-morning-phone-rings-situation 16:05:09 belimsf: not our department! 16:05:17 got it 16:05:50 alrighty 16:05:51 not a criterion ;-) 16:05:52 #endmeeting