14:03:03 #startmeeting 14:03:03 Meeting started Tue Jan 21 14:03:03 2014 UTC. The chair is DrBacchus. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:11 #chair mburned 14:03:11 Current chairs: DrBacchus mburned 14:03:14 yay! 14:03:19 ;-) 14:03:26 #help 14:03:40 #meetingname RDO Community Sync 14:03:40 The meeting name has been set to 'rdo_community_sync' 14:03:46 That's what I was looking for. :) 14:04:15 #link https://etherpad.openstack.org/p/rdo_community_manager_sync 14:04:29 Ok, not very much on the list for today. 14:04:35 #topic Test Day 14:04:35 #topic agenda 14:04:41 oops. 14:04:50 ok, we can jump in... 14:04:55 talk about the test day 14:05:26 We'll be doing a test day on Feb 4-5. It sounds like people are in agreement that we can have packages by then. 14:05:36 summary of new stuff for then 14:05:52 Icehouse Milestone 2 on el6 14:05:57 Icehouse Milestone 2 on el7 (new) 14:06:03 #info test day planned for Feb 4-5 14:06:10 Icehouse Milestone 2 on Fedora 20 14:06:16 #info should have the following available for Test Day: 14:06:36 #info Icehouse Milestone 2 for el6, Fedora 20, and el7 (new) 14:06:37 Hopefully some new test cases 14:07:13 --- 14:07:26 * kashyap is lurking briefly. He's just back from a long flight & still adjusting to a 4 1/2 hours timezone skew. 14:08:23 DrBacchus: anything else we need to cover for the test day? 14:08:40 I don't think so. Sorry. Distracted by my daughter for a moment. 14:08:57 I think that's it for that topic. 14:09:10 Next topic is hangouts, which I have still kind of dropped the ball on. 14:09:11 #topic Next Community Hangout 14:09:21 I have a quick question 14:09:21 #info plan for after test day 14:09:40 So it's there mostly as a reminder to me to go looking for some content. Unless someone else wants to volunteer now. :) 14:09:48 But, yes, probably after test day, and after FOSDEM would be good. 14:09:50 pixelb - Will *EL7 be targeted for this test-day? /me hasn't checked in the build system for packages 14:09:51 #action DrBacchus to ask for volunteers on mailing list and seek topics 14:10:10 kashyap, that's the plan (don't go looking for anything yet :)) 14:10:14 pixelb, Disregard me, it's in the scroll, you've already answered 14:10:57 If folks have suggestions for hangout topics, there should be a thread about it on rdo-list today. 14:11:23 Next topic: February newsletter. 14:11:40 #topic February Newsleter 14:11:44 #topic February Newsletter 14:11:54 I hope to have a draft this week. Some folks suggested some topics. I think we've got some good content there. 14:12:26 Looks like the link in the etherpad is broken. 14:12:35 DrBacchus: did the etherpad for the newsletter move to a public location? 14:12:49 or is it still an internal link 14:12:50 No. I did't do that. I'll do that now. 14:13:08 #info draft should be ready this week 14:13:12 #info current topics: 14:13:16 #info IRC meetings 14:13:20 #info FOSDEM 14:13:23 https://etherpad.openstack.org/p/rdo_feb_2014_newsletter 14:13:25 #info Infrastructure.Next 14:13:30 #info SCALE 14:13:40 #info CentOS and Cloud SIG effort 14:13:43 kashyap, I think there is an important piece of information w/r/t EL7 -- which is to say that the CI around EL7 is still underway, so the resulting install steps might be more error-prone/we may very well be uncovering rather fundamental issues that are blockers early in the process. 14:13:52 $info Bug triage meeting 14:13:55 #info Bug triage meeting 14:14:03 #info OpenStack Foundation elections 14:14:25 So, if anybody has anything else they'd like to see covered in a newsletter, or would like to write something, just let me know. 14:14:26 mburned, DrBacchus ^^ so I would say -- any thoughts on best ways to mitigate that so the broader community experience around test day for EL7 is a reasonable one or at least folks come in with reasonable expectations? 14:14:39 For reference, we have about 250 people on rdo-list, and about 2000 on rdo-newsletter 14:15:03 morazi, I see, noted. /me is currently up-to neck already keeping track of Fedora (since that's where all the newest changes land). 14:15:59 morazi: is the CI work going to be done ahead of the test day? or still going to be ongoing? 14:16:01 morazi: we'll have more lead time this time around, so hopefully QE will have some better idea of what to expect. 14:17:25 Lost the etherpad browser tab for a moment. 14:17:30 mburned, I'm hoping something in CI will exist and can at least give a very high level pass at the packages, but I think it is a little early to say what the level of completion will be. 14:17:57 Anything else on that? 14:18:19 DrBacchus, mburned kashyap I was bringing it up in that regardless we might want a belt & suspenders type approach around EL7 where we at least have a few of us actively trying to packages manually prior to test day to augment any automation we have in place 14:18:19 Do you have time to pursue that test results app for this time around? https://fedoraproject.org/wiki/QA/SOP_Test_Day_management 14:18:40 morazi: +1 14:18:42 morazi: was just about to suggest that we have a few people try it out in a pre-testday 14:19:03 kashyap: Yes, I believe I will have time to that this week, as soon as I'm done with FOSDEM stuff. 14:19:11 I have another potential topic, but not sure if it is of general interest. 14:19:19 kashyap: Should just be a matter of putting stuff in the Fedora wiki rather than (or as well as) ours. 14:19:31 DrBacchus, Cool. Also, don't hesitate to reach out to the friendly folks in #fedora-admin 14:19:34 (and/or it may overlap with the discussion re: Triage) 14:19:40 Yes, will do. They were helpful. 14:20:08 Would it be worthwhile to try to get default owners in bz for the RDO components? 14:20:47 morazi: on my list for today 14:21:06 * morazi cheers! 14:21:15 * mburned will get wiki page posted and email sent out by EOD 14:21:35 ok, next topic 14:21:37 #topic FOSDEM 14:21:47 FOSDEM is next weekend. 14:21:52 #info occurring on Feb 1-2 14:22:00 Then after FOSDEM there's the Infrastructure.next event in Ghent. 14:22:03 mburned, apols if that was on an etherpad or the agena already. I joined directly from a couple of back-to-back meetings and did not have as much prep time as I would have liked 14:22:22 I'm giving a presentation on using Ceilometer, so as a result I've learned a heck of a lot about ceilometer in the last two weeks! 14:23:08 There's a lot of good content in the IaaS track. 14:23:14 morazi: it's not, just something i had on my radar from talking to you last week... 14:23:33 #info there is also Infrastructure.Next event after FOSDEM in Ghent 14:23:44 https://fosdem.org/2014/schedule/track/virtualisation_and_iaas/ 14:23:51 #info DrBacchus is giving a resentation on ceilometer 14:24:09 #info also good content on the IaaS track ( https://fosdem.org/2014/schedule/track/virtualisation_and_iaas/ ) 14:25:04 So I'll actually be in Ghent during the test day. Hopefully I'll have everything done that I need to do before then. 14:25:12 DrBacchus: do you have engineer interviews setup? 14:25:23 or still trying to organize them 14:25:33 I don't have any specifically scheduled, but several people have said that they'd be willing. 14:25:42 DrBacchus: you can off load test day stuff to me if you need to 14:25:52 I've got a portable recorder thing, so I'll be able to just corner people and chat for 10 minutes. 14:26:06 And a number of people have said that they're willing. 14:26:15 So we shoul dhave some good content by the end of that. 14:26:25 #info DrBacchus will be conducting engineer interviews during FOSDEM 14:26:35 #info contact him if interested 14:26:59 that's always fun. 14:27:24 anything else for FOSDEM/Infrastructure.Next? 14:27:27 But other than trying to get ceilometer to do stuff, I don't have much more to say about that. 14:27:41 Next topic 14:27:48 CentOS Cloud SIG. 14:27:52 mmagr: any suggestions as to how I could go about fixing support for nested virt, kvm||qemu? 14:27:54 #topic CentOS Cloud SIG 14:28:13 After an initial burst of activity, the cloud sig threads have died down a little bit. 14:28:23 #info organizational/kickoff meeting scheduled for Thursday Jan 23 14:28:38 mburned: @ what time? 14:28:39 DrBacchus: i think everyone is waiting for the hangout on Thursday 14:28:45 But, yes, there's the meeting on Thursday, and I think folks are mostly waiting for that. 14:29:03 Looking at calendar for time. 14:29:08 larsks: 11 EDT 14:29:12 EST 14:30:20 http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140123T16&am=30 14:30:25 beddari, What do you mean "fixing support"? (Just to note: there's a meeting in progress here). Your question can be discussed after that, or please bring it up on rdo-list, so people can answer async. 14:30:30 So if there's anything you feel strongly should be mentioned in that meeting/hangout, please make sure we have discussed it by then, so that we can adequately represent what RDO wants to see happen there. 14:31:16 DrBacchus: we should probably sync up on what to talk about before that meeting 14:31:19 Are there things people feel strongly about that should be mentioned there? 14:31:25 If you haven't caught up on the conversation so far, it's on centos-devel starting about two weeks ago. 14:31:25 ...yeah, what mburned said. 14:31:56 mburned: Did you have in mind doing that with a small group, or all of rdo-list, or what? 14:32:43 DrBacchus: we can solicit topics from the large group, but i think they want each group to do a mini presentation... 14:32:59 so i'll request feedback from rdo-list today 14:33:09 Sounds good 14:33:23 and maybe we can meet briefly on thursday to make sure we have everything in order 14:33:45 #action mburned to talk with rdo-list about the CentOS Cloud SIG hangout, to be sure we are representing the view of the community in that meeting. 14:33:47 #action mburns to send request for RDO goals of Cloud SIG today 14:33:50 :) 14:33:55 #undo 14:33:55 Removing item from minutes: 14:34:01 you said it better... 14:34:17 ok, next item? 14:34:24 #topic Bug Triage 14:34:47 We have the bug triage in the agenda, but I'm not sure what we need to say, other than that we have a regularly schedule IRC bug triage tomorrow, right? 14:34:47 #info bug triage meeting is happening on a once or twice monthly basis 14:35:06 Oh, right, it's not every week. 14:35:16 Right. 14:35:17 #info there is some work being done by kashyap and mburned to improve the process 14:35:31 On that note, it was suggested that we create an RDO google calendar, and that's on my list to do today. 14:35:42 To list this meeting, and that meeting, and other community events. 14:35:53 #info last week's meeting was successful in triaging about half of the open bugs 14:36:07 thanks to kashyap for heading that up. 14:36:29 Also to larsks (for major contrib) & others who participated. 14:36:35 #info DrBacchus will be creating a google calendar to list this meeting, the bug triage meeting and any other community events 14:37:03 DrBacchus: probably should add things like FOSDEM as well... 14:37:12 Last item on the list, I didn't get done in time because I was fighting with the ceilometer API all day yesterday. :/ 14:37:28 #topic RDO forum questions 14:37:42 #info not prepared for today, so DrBacchus will handle this off-meeting 14:37:49 #info other topics 14:38:02 if anyone has other stuff to mention, now is the time 14:38:03 However, we have 28 unanswered questions on ask.openstack, so we're falling kind of far behind there. 14:38:04 beddari, well some vmx|svm checking logic (new fact probably) will have to be implemented IMHO 14:38:19 #topic other topics 14:38:30 * larsks is planning on tackling some ask.o.o later today. 14:38:43 #info a centos 6.5 guest-image has been posted to the RDO yum repo 14:39:07 I linked that to the images page. 14:39:10 #link http://repos.fedorapeople.org/repos/openstack/guest-images/ 14:39:29 #info thanks to jboggs for putting that together 14:39:43 larsks: thanks for working on the forum questions 14:40:33 Any other topics? Anyone? 14:40:41 #info plan to have some people do pre-test-day testing with EL7 packages 14:40:47 (just to capture that from earlier) 14:41:26 last call for topics 14:41:49 Ok, all done, then. 14:41:49 ok, i think we're done 14:42:01 Thank you all for your participation and patience. 14:42:01 #endmeeting