13:02:07 #startmeeting RDO weekly sync 13:02:07 Meeting started Tue Mar 11 13:02:07 2014 UTC. The chair is mburned. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:02:11 #chair rbowen 13:02:11 Current chairs: mburned rbowen 13:02:24 #link https://etherpad.openstack.org/p/rdo_community_manager_sync 13:03:17 #topic Test Day 13:03:47 I copied all of our test cases over to the Fedora Test Day app. kashyap did you have a chance to look at that? 13:03:52 rbowen: back in 2 min... 13:04:02 Did I do it right, in your opinion, or do I need to tweak it any? 13:04:15 rbowen, No, haven't. Been buried in bugzilla and other issues. Will take a look this week 13:04:30 rbowen, Can you post a URL here, please for reference 13:04:32 #info Test day stuff in the Fedora Test Day app for easier test reporting 13:04:34 #link http://testdays.qa.fedoraproject.org/testdays/show_event?event_id=16 13:04:43 #info metadata can be edited there too 13:04:52 #link https://fedoraproject.org/wiki/Test_Day:2014-03-19_RDOMetadata 13:05:28 So what we're lacking there is some test instructions on some of them, and also any new test cases that need to be added for M3 13:05:38 * rbowen waits for mburned 13:06:17 rbowen, From a quick look, it looks cool 13:06:24 cool = useful 13:06:30 Ok, good. 13:06:40 I also see you've added the URLs where appropriate 13:06:43 and some still need them 13:06:54 Yes, there are several placeholder ones that I need to go back and hunt down content for. 13:08:02 Great. 13:08:06 * mburned back 13:08:47 Re: packages for test day 13:09:15 mburned: So, were were just talking about having test cases in the Fedora Test Day app. 13:09:24 But, yes, packages ... 13:09:39 I was trying to find what's available for Fedora (Rawhide/F21) at the moment 13:09:42 #info test day scheduled for March 10-20 13:09:54 I think a little more consistency would be good, i.e. always call it either RHEL 7.0 or 7 and always use the some ordering for the different OSes 13:10:13 Ah. Sorry, I thought I had done. I'll run back through and verify. 13:10:17 rbowen, I see that, at a minimum - Nova, Neutron, Keystone have Milestone-3 packages for Rawhide/F20. Glance still needs to be updated. 13:10:40 #info rbowen has added a lot of test cases to the test day app 13:11:01 #info some cleanup still needed (consistent naming, consistent order for different OSes, etc) 13:11:08 #info some need some additional content 13:11:29 #info some packages exist already for rawhide/f21 13:11:40 mburned, Packages for Milestone-3 13:11:47 #undo 13:11:47 Removing item from minutes: INFO by mburned at 13:11:29 : some packages exist already for rawhide/f21 13:11:54 #info some packages for milestone 3 exist already for rawhide/f21 13:12:03 Yeah, I haven't mentioned F21 at all in the test list. 13:12:20 EPEL-7 is in progress (pixelb and co are hard at work) 13:12:21 rbowen, Better not to mention F21 yet 13:12:26 #info EPEL-7 is WIP 13:12:28 I'd consider testing on rawhide a waste of time 13:12:37 rbowen, Since there's a lot of changes going on upstream Fedora, F21 will be very late 13:12:52 Ok, just making sure. It didn't seem like something we'd want to spend energy on. 13:13:01 red_trela, Hmm, I don't. It depends _what_ you're trying to do 13:13:17 "testing" is a loaded term 13:14:04 kashyap: by the time F21 is released, we want to test Juno, not Icehouse... 13:14:16 kashyap, I think red_trela raises a valid point though. It is fine for the exceptionally bold and thick skinned to go after F21, but really I think rdo gets more value having folks test on platforms we expect to work.... 13:14:30 red_trela, Yep, that's why I mentioned the upstream changes in Fedora land. We don't know _when_ F21 will come 13:14:36 i would concentrate on f20/epel6/epel7 13:14:40 +1 13:14:45 morazi, Sure, F21 is not valid at this point 13:15:01 morazi, I meant to say only _current_ "stable", i.e - F20 13:15:06 f21 feedback might be useful, but probably less so than the others 13:15:13 kashyap: we know it will be 2014/10/14 or later 13:15:41 yea, priority wise, I suspect we'll go after fixes that impact epel7/epeal6/f20 in likely that order 13:16:38 weshay, how are you feeling about the ability to have some CI going in advance of the 20th? 13:16:43 #agreed we should concentrate on epel7/epel6/f20 in that order (fedora rawhide not a priority at this time) 13:17:13 morazi, Yep, that ordering sounds good 13:18:29 Any thing else on packages here? 13:18:35 #action mburns to produce icehouse livecds as soon as packages are ready 13:18:42 on at least epel6 13:18:46 Ok, so, we need to send some reminders and make sure folks are planning to set aside a little time for this. 13:19:01 rbowen: you want to handle that? 13:19:04 Yes. 13:19:10 #action rbowen to send reminders of the test day 13:19:24 #chair kashyap 13:19:24 Current chairs: kashyap mburned rbowen 13:20:04 We can skip ahead if you have stuff you need to get back to. There's a few things I wanted to mention. 13:20:05 So, test days are 19, 20 March, right? 13:20:09 Yes, that's right. 13:20:35 rbowen: let's go through, if i need to drop, i'll let you know and you can add notes... 13:20:43 ok, sounds good. 13:21:00 #topic Hangout 13:21:13 #info next hangout set for March 27 13:21:29 #info topic is Marconi, host is flaper87 13:21:49 #link https://plus.google.com/events/ckjhm8rggnqvrnspftna845kubk 13:21:54 o/ 13:22:18 flaper87: We should do a test hangout the day before to be sure that everything works, you can share your screen, and so on 13:22:29 Unless you've already done all that before. 13:22:41 rbowen: I have but I'd like to do the test anyway 13:22:48 ok, great. 13:23:13 next ... 13:23:22 #topic April Newsletter 13:23:34 #link https://etherpad.openstack.org/p/rdo_apr_2014_newsletter 13:23:34 #info Looking for topics if there's anything you want to say in that. 13:23:52 Haven't got anything there. 13:24:21 ;-) 13:24:32 next? 13:24:35 #topic Engineer interviews 13:24:50 #info interview with ohadlevy should be posted later today 13:24:58 I did an interview with Ohad yesterday, and got it all edited and produced yesterday. He just signed off on it, and I'll be posting that on the RDO site today. 13:25:05 #info other interviews in the works 13:25:12 The audio quality isn't great, but it's a good interview. 13:25:17 #info if interested, please contact rbowen 13:25:29 So, if you like to talk ... :-) 13:25:46 If you ahve a listen to Ohad's interview, later today, you can get an idea of kind of what I'm looking for. 13:26:11 #topic Upcoming Events 13:26:24 #info April: RH Summit -- booth 13:26:35 #info mburns will be in attendance 13:26:41 #info multiple presentations lined up 13:26:48 #undo 13:26:48 Removing item from minutes: INFO by mburned at 13:26:41 : multiple presentations lined up 13:26:51 #info multiple demos lined up 13:26:58 We've got some nice demos in the works for RH Summit, and mburned will be coordinating the booth and demo schedule. 13:27:18 Kinda sorry to miss it, but I'll be still on the way back from another event. 13:27:32 And then some/most of those demos will get used again at the OpenStack Summit 13:27:44 #info OpenStack summit in May 13:27:45 But if you're going to be at the OpenStack summit, and would like to demo something, please let me know. 13:28:02 #info RDO will have a booth 13:28:14 #info rbowen is a track chair for "Getting Started" 13:28:30 * kashyap has a quick note on next topic -- Bug Triage 13:28:46 #info will likely reuse some of the same demos from RH Summit at Openstack Summit 13:28:46 I don't know how long it takes to make the schedule. I got done yesterday, but I presume other tracks are somewhat harder to put together. 13:29:13 #info LinuxCon Japan also in May 13:29:20 #info RDO will have a booth/table 13:29:24 And then later in May seems I'll be going to Tokyo, which I'm really stoked about. 13:29:37 rbowen: and red_trela will be in attendance at the booth 13:29:39 And red_trela said he'd try to show up and help answer RDO questions. 13:29:47 #info rbowen and red_trela will be in attendance at the booth 13:30:22 There will probably be a CentOS dojo, which is kind of an informal unconference sort of format. 13:30:39 #info a CentOS dojo will likely also happen and LinuxCon Japan 13:30:57 So I don't really know what kind of sessions there will be in that. But the cloud SIG was a popular topic at the CentOS gathering at SCaLE, so I expect htat'll be part of it. 13:31:06 cool 13:31:16 * mburned has no news on cloud sig this week again 13:31:29 so moving ahead... 13:31:35 #topic Bug triage 13:31:36 ok. 13:31:37 kashyap: ? 13:31:52 Current status, we have around - 16 bugs (as of a few hours ago) 13:32:00 NEW, i.e. 13:32:14 3 of them are CVEs (SecurityTracking bugs) -- that will be handled by SRT 13:32:29 #info 16 open bugs as of a few hours ago 13:33:35 red_trela, Just a quick clarification (from reading scroll): I misread your Rawhide as F20 :-) Sorry about that. 13:34:26 #info 3 are security related, being handled by security experts 13:34:36 kashyap: any other updates on the other 13? 13:34:47 or just normal triage 13:35:42 mburned, Normal triage of components I have expertise on. Some bugs just need exotic storage 13:35:59 #info other bugs going through normal triage 13:36:13 #topic Forum 13:36:24 rbowen: still 38 unanswered? 13:36:32 I got a lot of help last week, both marking topics as abandoned, and answering open ones. 13:36:42 Yes, 38 as of right now. 13:36:56 I wish there was a better way to track volume. 13:37:13 #info 38 open questions 13:37:15 Because we closed about 20 last week, and had almost that many new opened, but we're not capturing those stats anywhere. 13:37:35 s/closed/answered/ 13:37:50 #info lot of work done last week answering and closing abandoned questions 13:37:59 #info closed about 20 last week 13:38:09 #info approx 20 more opened during that time 13:38:18 #info need some better stat tracking 13:38:33 So I'm tracking how many unanswered there are every week, but it's a really unhelpful statstistic, because it doesn't really reflect traffic. 13:38:56 I need to figure something out there. 13:39:07 rbowen: can we track "new" and unanswered? 13:39:36 I'll see what the API offers. I'm not sure. 13:39:53 #info rbowen to investigate what else we can track 13:39:58 #topic other topics 13:40:01 anything else? 13:40:05 Nothing from me. 13:40:23 Nothing here either 13:40:29 ok, thanks all 13:40:31 #endmeeting