13:59:30 <mburned> #startmeeting RDO weekly meeting
13:59:30 <zodbot> Meeting started Tue Mar  4 13:59:30 2014 UTC.  The chair is mburned. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:30 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:59:34 <mburned> #topic Agenda
13:59:39 <mburned> #chair kashyap rbowen
13:59:39 <zodbot> Current chairs: kashyap mburned rbowen
13:59:47 <mburned> #link https://etherpad.openstack.org/p/rdo_community_manager_sync
14:00:29 <mburned> #topic Test Day
14:00:43 <mburned> #info set for March 19-20
14:00:53 <mburned> that's 2 weeks from now...
14:01:10 <mburned> #link https://fedoraproject.org/wiki/Test_Day:2014-03-19_RDO
14:01:30 <mburned> #link https://fedoraproject.org/wiki/Test_Day:2014-03-19_RDOMetadata
14:01:45 <rbowen> I started working with the Fedora test day wiki tools yesterday, and there are links there to the wiki page (general information) and the metadata page (which the test day app uses to generate test forms)
14:01:49 <mburned> #info based on OpenStack IceHouse M3
14:02:15 <mburned> #info M3 is March 6
14:02:19 <rbowen> So over the coming weeks we need to try to convert our existing list of tests to that metadata page. I *think* we can just link to our existing test cases.
14:02:26 <rbowen> But if not, it's going to be a lot of work.
14:02:34 <mburned> #info Feature Freeze for IceHouse is today (March 4)
14:02:46 <rbowen> Then once we have the metadata page we regenerate the test app, and people can easily indicate what they did.
14:02:48 <kashyap> rbowen, Yes, I noticed the page here --
14:03:04 <mburned> #info those links to the wiki page for general info and metadata page which the Fedora Test Day app uses to create test forms
14:03:18 <rbowen> Obviously most of the info there isn't valid yet. Hopefully I'll fix that today and tomorrow.
14:03:29 <mburned> #info need to import current list of tests to metadata page
14:03:33 <kashyap> http://testdays.qa.fedoraproject.org/testdays/show_event?event_id=16
14:03:58 <mburned> #info rbowen working on correcting/updating the information
14:04:05 <rbowen> Yeah, that's generated from the metadata page. And you can regenerate it every time you add/modify a test.
14:04:14 <rbowen> And then anyone logged into that wiki can enter their results.
14:04:30 <kashyap> rbowen, Folks in #fedora-admin are helpful, if you need any w/ the test day app
14:04:30 <rbowen> It looks like it'll be really useful once we do the bootstrap work.
14:04:54 <rbowen> Yeah, they've been helpful so far with beginner questions. I expect I'll be asking them a lot. Thanks for the reminder.
14:04:55 <mburned> very nice
14:05:11 <kashyap> I added IceHouse M3 and other release dates on the etherpad above
14:05:40 <mburned> anything else we need to discuss with the test day?
14:05:53 <kashyap> Yes
14:05:53 <mburned> #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule
14:06:05 <rbowen> Just that once I get the existing test stuff over there, I'll be asking folks here to help bring it up to the present.
14:06:36 <kashyap> Still have to decide if we plan to make a test day with IceHouse M3, packages as it'll be feature freeze by then
14:06:37 <mburned> #action rbowen to ask for help updating test info once existing stuff is added
14:06:57 <mburned> kashyap: plan was always to use M3, i thought...
14:07:17 <rbowen> That's what I understood also.
14:07:22 <mburned> basically, M3 closes, 2 weeks for packages to be generated and smoke tested, then test day...
14:07:38 <rbowen> That is how I understood the timing, yes.
14:07:48 <kashyap> mburned, Do you know for certain it takes 2 weeks for  packages?
14:07:54 <kashyap> Or is that just a guesstimate?
14:08:08 <rbowen> pixelb suggested that would be reasonable timing.
14:08:09 <mburned> kashyap: that's the feedback that pixelb gave with the M2 test day
14:08:09 <kashyap> jruzicka_wfh, and pixelb may shed more light on M3 packaging status
14:08:22 <rbowen> If it's not, we need to push it out an extra week. Now would be the time to do that.
14:08:25 <kashyap> Alright
14:08:43 <pixelb> M3 for M19 is fine if that's the question
14:08:53 <mburned> pixelb: thanks!
14:08:59 <rbowen> That's the question - can we have packages by March 19
14:09:14 <mburned> #info pixelb confirms packages for M3 should be ready for March 19 Test Day
14:09:27 <mburned> anything else for test day?
14:10:01 <rbowen> Nope
14:10:01 <mburned> #topic Hangouts
14:10:16 <pixelb> Would like to include marconi packages and ensure more test savanna for M3 test day
14:10:39 <mburned> #topic Test Day (revisited)
14:10:53 <rbowen> I was looking for the URL for the hangout.
14:11:11 <mburned> pixelb: sure, is there someone rbowen can reach out to to fill in those tests?
14:11:22 <rbowen> pixelb: I guess I didn't realize Marconi was to that point yet. Cool
14:11:33 <rbowen> mburned: Perhaps Flavio, which leads right into the next hangout. :-)
14:11:48 <mburned> OFI might be something to target in testing, but not sure if it will be ready yet...
14:12:11 <pixelb> mburned, upstream savanna basic tests are already linked from the RDO wiki
14:12:11 <mburned> #info pixelb would like additional coverage of marconi and savanna
14:12:38 <mburned> #info marconi basic tests already linked on the RDO wiki
14:12:45 <rbowen> ok.
14:12:53 <pixelb> 2 seconds
14:13:06 <pixelb> #info savanna basic tests already linked on the RDO wiki
14:13:20 <pixelb> # info hope to have marconi packaged for test day
14:13:37 <mburned> #chair pixelb
14:13:37 <zodbot> Current chairs: kashyap mburned pixelb rbowen
14:13:42 <mburned> #info savanna basic tests already linked on the RDO wiki
14:13:46 <mburned> #info hope to have marconi packaged for test day
14:13:58 * mburned not sure if infos work if you're not a chair...
14:14:09 <kashyap> They don't, IIRC
14:14:24 <pixelb> flaper87, Just in case you're not aware, initial marconi packages are already prepared
14:14:39 <mburned> #info would also be good to have testing for the OFI stuff, but unclear if that will be ready in time
14:15:15 <mburned> ok, on to hangouts
14:15:20 <mburned> #topic Hangouts
14:15:27 <mburned> #link http://openstack.redhat.com/Hangouts
14:15:36 <rbowen> ok, we had a hangout last week, which was attended by somewhere around 30 people live.
14:15:45 <mburned> #info larsks did a hangout on the 27th
14:15:53 <rbowen> larsks: Can you look at your Hangout page and tell me how many folks have watched the video since?
14:16:08 <mburned> #link https://plus.google.com/events/cm9ff549vmsim737lj7hopk4gao
14:16:17 <mburned> #info ~30 people watched live
14:16:17 <rbowen> So one lesson learned is that I need to to create the hangout myself, ahead of time, so that it's not so complicated to gather stats afterwards.
14:16:29 <rbowen> It also makes it easier to gather those hangouts into one YouTube channel afterwards.
14:16:49 <mburned> lessons learned are good
14:17:19 <rbowen> And we've got flaper87 giving a talk on Marconi on March 27th.
14:17:34 <rbowen> #info Flavio Percoco will give a hangout on Marconi March 27, 10am EST
14:17:46 <rbowen> #link https://plus.google.com/events/ckjhm8rggnqvrnspftna845kubk
14:18:28 <rbowen> You can now schedule On Air Hangouts, which is a new feature in the last month or two. That makes it a lot easier to promote an event like this.
14:19:02 <larsks> ...and I think that when you schedule them like this they also show up on your Google Calendar.
14:19:14 <mburned> #info rbowen has learned a lot about scheduling Hangouts and organizing them ahead of time which will improve statistics and organizing all hangouts afterwards
14:19:19 <rbowen> Oh, also, larsks discovered that as the host of a hangout, there's a "download the video as mp4" link, so that folks can watch it offline.
14:19:35 <rbowen> So we're going to get those and host them on the RDO site as well.
14:19:42 <mburned> nice
14:19:47 <rbowen> No idea how large a hour mp4 is. Probably ... big.
14:20:02 <rbowen> But someone asked for that so they can watch it offline.
14:20:06 <mburned> #info also, we will investigate hosting the recordings on the rdo site as well
14:20:34 <larsks> rbowen: I think the video for my hangout was < 300MB.
14:20:43 <mburned> #info to enable offline viewing
14:20:44 <rbowen> ok.
14:21:11 <larsks> Hmm, checking if that's actually a video or just the audio track.
14:21:33 <rbowen> an hour of audio should be around 60-100M I'd expect.
14:21:39 <rbowen> I usually figure 1M per minute.
14:21:45 <rbowen> Video I don't have much experience with.
14:21:56 <mburned> #info if you're interested in hosting a Hangout, please get in touch with rbowen or check out the hangouts etherpad
14:21:58 <mburned> #link https://etherpad.openstack.org/p/rdo_hangouts
14:22:11 <larsks> Nope, that's the video.
14:22:26 <rbowen> So, yeah, I need to start looking for April.
14:22:46 <rbowen> ok, that's all I've got on hangouts.
14:23:16 <mburned> #info Newsletter
14:23:51 <rbowen> March newsletter going out today. Thanks for folks who helped me proofread that. April newsletter not yet started, but will mostly focus on the OpenStack Summit.
14:24:12 <mburned> #info March Newsletter to go out today
14:24:29 <mburned> #info looking for topics for April Newsletter now
14:24:38 <mburned> #link https://etherpad.openstack.org/p/rdo_apr_2014_newsletter
14:25:02 <mburned> #info focus of April's newsletter will likely be on OpenStack Summit
14:25:21 <mburned> #info please let rbowen know if you have topics
14:25:53 <kashyap> pixelb, An unrelated side note, python-gerrit-view is now in Rawhide and EPEL7 branches
14:26:29 <mburned> #topic Events
14:26:43 <rbowen> March is blissfully quiet, as is April
14:26:46 <mburned> #info we're not scheduled to be at anything in March
14:26:59 <rbowen> I'm chairing an unrelated conference in April - ApacheCon in Denver.
14:27:13 <rbowen> Oh, wait, RedHat summit is in April.
14:27:16 <mburned> #info in April, the only really relevant conference is Red Hat Summit
14:27:41 <rbowen> I believe that starts on April 16?
14:27:44 <mburned> #info numerous demos planned around OpenStack (primarily RHELOSP, I think)
14:27:56 <rbowen> 14-17
14:27:58 <mburned> april 14-17
14:28:19 <mburned> #info there is supposed to be an RDO booth as well
14:28:29 <rbowen> Six engineers have volunteered to provide demos to do in the booth.
14:29:04 <rbowen> I don't yet know exactly what those demos will be, but I hope to have some details on them pretty soon so that we can start promoting them, perhaps some video teasers and the like.
14:29:21 <mburned> woot!
14:29:28 <mburned> #info 6 different demos planned for the RDO booth
14:29:35 <mburned> #info more details to follow
14:30:07 <rbowen> Those names are in the agenda. Not sure I want to embarrass them in the minutes. :-)
14:30:29 <rbowen> But the hope is that some or all of those demos will also be usable at the OpenStack Summit.
14:30:44 <mburned> let's wait til we have the topics and confirmation, and we can put it here next week
14:30:49 <mburned> #info Openstack Summit takes place in May (12-16)
14:31:12 <rbowen> At the OpenStack Summit we have a table with a demo screen, which we will need to staff for the entire time.
14:31:20 <mburned> #info we will have a booth with demo screen
14:31:41 <mburned> #info schedule of talks are still being finalized
14:31:44 <rbowen> We've also got a fancy pull-up banner for the booth. That's getting printed right now, so I haven't seen it yet, but the mockup looked very sweet.
14:31:54 <mburned> awesome
14:31:57 <larsks> rbowen: Are you looking for booth volunteers?
14:31:59 <rbowen> And I've been asked to be a track chair for the "Getting Started" track.
14:32:25 <rbowen> Yes, we are looking for booth volunteers, although that's still very preliminary. But if you're interested I'll put your name on the list.
14:32:27 * mburned likely to be there for booth time
14:32:39 <mburned> (same for RH summit)
14:33:11 <rbowen> I will *not* be at RH summit, so I want to be sure that we have all that stuff clearly planned ahead of time.
14:33:23 <rbowen> But since you're going to be there, I'll rely on you to keep it in line. :-)
14:33:34 <mburned> ;-)
14:33:39 * larsks will also not be at RH summit, but will be at OpenStack.
14:34:09 <mburned> rbowen: are there plans for LC-Tokyo?
14:34:14 <rbowen> There's also FISL, in Porto Alegre Brazil, the week before OpenStack Summit, but I don't think that we'll hvae a presence there.
14:34:51 <rbowen> mburned: I just this morning received a request to keynote at LC-Tokyo on behalf of the Apache Software Foundation. I don't know yet if I'm going to go. But if I do, I'll try to wrangle an RDO booth there, I think.
14:35:02 <mburned> #info currently no plans to be at FISL (week before Openstack Summit)
14:35:10 <mburned> rbowen: ok
14:35:17 <rbowen> Not sure I want that mentioned in the minutes (the keynote possibility)
14:35:23 <rbowen> Still in shock that they asked.
14:35:34 <mburned> #info LinuxCon Japan (May 20-22) is a possibility for an RDO booth, but not decided yet
14:35:52 * mburned doesn't add note about the keynote...
14:35:53 <rbowen> I need to talk to DV about that and see if that's even a possibility.
14:36:16 <DV> hum
14:36:18 <rbowen> So it feels like there's a flurry of events coming up.
14:37:00 <rbowen> In that flurry, I don't want to overlook local/regional events.
14:37:01 <kashyap> Yes, anything further on events?
14:37:18 <rbowen> So if you know of hangouts, meetups, or local conferences, please mention them on the mailing list.
14:37:33 <rbowen> Other than that, no, nothing further on events.
14:37:51 <rbowen> I have nothing on the next to agenda items, unless someone else does.
14:38:20 <kashyap> rbowen, mburned Just a note --
14:38:32 <kashyap> When you send the meeting minutes, please copy/paste the plain text summary content in the mail to the list, and not just URLs.
14:38:43 <rbowen> Ok, will do.
14:38:52 <kashyap> Thanks.
14:39:03 <mburned> ack
14:39:08 <DV> mburned: we had miniconfs for gluster and ovirt in LC-Japan 2 years ago, but i don't know this year
14:39:39 <mburned> #info if you know of any local meetups/hangouts/local conferences, please mention on the rdo mailing list
14:39:49 <DV> mburned: we met there IIRC
14:39:55 <mburned> DV: yep
14:40:13 <rbowen> ok, anything on the CentOS cloud SIG? I haven't seen anything in the last week.
14:40:18 <mburned> DV: we determined (i think) that the mini-confs weren't all that valuable, but a booth might be
14:40:27 <mburned> rbowen: nothing new this week
14:40:29 <DV> okay
14:40:32 <mburned> should have updates next week
14:40:33 * kashyap planned to submit a talk at LC-Japan, but refrained due to other commitments
14:40:56 <rbowen> Bug triage is a standing item, but we're between two of them. I expect there's nothing there?
14:41:14 <kashyap> rbowen, There's just 16-17 at the moment,
14:41:41 <mburned> DV: rbowen and i still have to sync on some of these upcoming events to see what we should target, so we'll follow up
14:41:49 <kashyap> and, we try to triage periodically in between weeks too.
14:41:57 <mburned> #topic Bug Triage/CentOS Cloud SIG
14:42:01 <DV> mburned: okay :-)
14:42:14 <mburned> #info not much new here, SIG is quiet
14:42:18 <kashyap> mburned, But Triage and CentOS Cloud SIG are two different topics, no? :-)
14:42:28 <mburned> #info bug triage happening consistently, but we're between meetings at the moment
14:42:30 * kashyap stops nit-picking
14:42:32 <mburned> kashyap: technically, yes...
14:42:39 <mburned> but that's all we really have to say
14:42:49 <mburned> #topic Forum
14:43:14 <rbowen> Getting further and further behind on the forum. We're at 47 unanswered this morning.
14:43:31 <mburned> #info we're at 47 unanswered this morning
14:43:43 <mburned> rbowen: did you tag the abandoned ones?
14:44:02 <rbowen> I spent quite a bit of time yesterday on it, and folks were helpful , but there's some new overnight.,
14:44:38 <rbowen> No, I am not able to tag articles.
14:45:11 <rbowen> So I need to follow up with a list to someone who can. I was supposed to do that last week.
14:46:01 <mburned> #action need to get abandoned ones closed
14:46:08 <rbowen> Sorry. Parenting crisis. One of the hazards of working from home and having snow days.
14:46:15 <rbowen> I'm back.
14:46:16 <larsks> rbowen: I can retag posts on a.o.o.  Is that what you're looking for?
14:46:37 <rbowen> larsks: Yes. I just need to collate a list of ones that need to be.
14:46:50 <rbowen> There's maybe as many as half of those that are clearly abandoned and it would be nice to have them off the list.
14:47:04 <mburned> #info rbowen and larsks will work on closing the abandoned posts
14:47:56 <mburned> rbowen: anything else with the forum?
14:48:09 <rbowen> Also, I asked on the (internal) list for folks to update the subject matter expert list, but it would probably be a good idea to have such a list in a more public place.
14:48:21 <rbowen> I've been reluctant to do that due to the spam potential. Thoughts?
14:48:49 <mburned> rbowen: a protected wiki page might make sense
14:48:49 <rbowen> The obvious advantage is that we could include folks who are more part of the upstream community and not limit it to Red Hat folks.
14:49:08 <mburned> something only wiki admins could edit
14:49:12 <kashyap> IMHO,  for community questions, engineers mostly would answer on best effort basis
14:49:13 <mburned> and list only irc nicks
14:49:28 <larsks> mburned: +1 for only irc nicks :)
14:49:39 <rbowen> Ok, I'll do that.
14:50:02 <rbowen> #action rbowen to start wiki page of "subject matter experts" who are willing to have ask.openstack.org questions assigned to them.
14:50:38 <mburned> #info and only list IRC nicks there to minimize spam for the SMEs
14:50:40 <larsks> rbowen: "assigned to them" in what sense?
14:51:05 <rbowen> Yeah, perhaps wrong word. Mostly it's just that I email/IRC-ping them and say "would you please look at this issue"
14:51:07 <kashyap> Yeah, I doubt if you could really "assign" things
14:51:26 <mburned> larsks: i would think something like a table with subjects like "Nova Networking, Glance, etc"
14:51:26 <rbowen> Sure. "assign". More like request.
14:51:37 <mburned> and a column with people who are experts in that area
14:51:46 <rbowen> Exactly. It's "I'm willing to field questions on these topics".
14:52:42 <rbowen> Ok, I believe that's all. Thanks everyone for your time.
14:52:52 <rbowen> Any other topics?
14:52:58 <mburned> #topic Other Topics
14:53:10 <mburned> SME list should have been here, but oh well....
14:53:56 <kashyap> Nothing from me. Just chased down a nested virt upstream regression last week :)
14:54:08 <mburned> ok, then lets close the meeting
14:54:10 <mburned> thanks all
14:54:12 <mburned> #endmeeting