16:02:24 #startmeeting oslo 16:02:25 Meeting started Fri May 9 16:02:24 2014 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:28 The meeting name has been set to 'oslo' 16:02:34 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 16:02:51 today should be a pretty quick meeting 16:03:04 #topic action items from last meeting 16:03:31 I have a review up to create the oslo-specs 16:03:32 #link https://review.openstack.org/92614 16:03:44 cool 16:03:46 thanks to bnemec for giving the inputs a quick sanity check 16:04:03 we may want to think about tweaking the template, but we can do that using gerrit 16:04:17 +1 16:04:35 dhellmann: It means that I'll have to rewrite rootwrap blueprint there, right? 16:04:49 I'll bug the infra team a bit later today to see if they can merge that before the summit 16:05:07 YorikSar: yes, it would be good to do that 16:05:16 dhellmann: ok 16:05:17 I also need to write up the oslo.i18n graduation blueprint 16:05:47 dhellmann: Will there be subdirs for every project in oslo? 16:06:02 YorikSar: we talked about that, but I don't know if we really need to go that far 16:06:11 so I haven't created them, yet 16:06:26 if the group thinks having separate directories is really needed, we can add them as we add blueprints 16:06:38 Are the oslo* blueprints segregated on launchpad? 16:06:42 dhellmann: Ok. I guess we can create them if the number of specs in all projects combined becomes too big. 16:06:55 bnemec: it depends on the library, at this point 16:07:39 I'm not too worried about it yet. I'm sure there will be some iteration on the process as we get going. 16:07:40 we have oslo.messaging, taskflow, stevedore, and cliff in separate launchpad projects 16:07:45 the others are all in the oslo project 16:07:52 bnemec: exactly 16:08:04 does anyone else feel strongly one way or the other? 16:08:20 nope, I'm up for giving it a shot and evolving 16:08:22 nope 16:08:30 such an easy-going crowd :-) 16:08:37 #topic Red flags from liaisons 16:09:19 are there any blocking issues with adopting existing oslo libs in any projects? 16:09:35 what are the libs? 16:09:56 bknudson: excellent question! 16:09:58 #link https://wiki.openstack.org/wiki/Oslo#Libraries 16:10:19 everything on that list except oslo.db and oslo.i18n should be ready to be used, if appropriate 16:10:51 I think keystone is using all the ones that we can 16:11:23 we should be able to use oslo.db and oslo.i18n when they're ready 16:11:24 bknudson: I need to update my patch to make keystone use stevedore for plugins. At this point, that'll have to wait until after the summit, I think. 16:11:33 excellent 16:11:49 dhellmann: talk to ayoung at the summit! 16:11:56 ok, if there are no serious new issues, let's move on 16:12:02 #topic oslotest adoption status 16:12:37 keystone is using oslotest -- we've got the base test class and a couple fixtures 16:12:38 as we push out new libs, I want to focus on each for a couple of weeks, in addition to asking about the general red-flags 16:13:02 so I'll try to keep up with which ones need to stay on the agenda 16:13:03 I think we're still using the config fixture from oslo-incubator... maybe we need a new release of oslo.config? 16:13:31 Yeah, that should be graduated in git now. 16:13:32 bknudson: yes, bnemec weren't you working on graduating that? did the change land? 16:13:34 cool 16:13:52 https://review.openstack.org/91397 16:14:04 I can tag a new release, though I'm tempted to wait until we decide on the pre-release testing strategy at the summit 16:14:37 #action dhellmann look into tagging oslo.config release 16:14:47 yeah, tagging a new release now would expose it immediately to icehouse users - the thing I've always been skeptical about 16:14:56 markmc: right 16:16:07 I'll look into what changes would be included in the release 16:16:21 #topic oslo.messaging adoption status 16:16:42 I think keystone has been using this for a while 16:16:59 I'm not sure what hasn't adopted it at this point 16:17:07 e.g. I know ceilometer and ironic patches recently landed 16:17:11 is cinder done? I know they ran into some issues 16:17:12 * markmc starts to check 16:18:32 while markmc does that, we can move on and come back to this in a few minutes 16:18:42 #topic summit prep 16:18:49 #link https://wiki.openstack.org/wiki/Summit/Juno/Etherpads#Oslo 16:19:00 we have etherpads for most of our sessions already 16:19:24 are there sessions that you especially expect the liasons to show up at? 16:20:08 bknudson: there's a cross-project session Tues 14:00-14:40 "New Oslo Library Releases and Your Project" 16:20:25 and then the opening session for oslo: Wed 9:00 - 9:40 Release Plan for Low-level Libraries 16:20:31 I'll get an oslo.messaging etherpad up tomorrow 16:20:40 you may also be interested in Thu 9:50 - 10:30 Testing pre-releases of Oslo libs with apps 16:20:43 markmc: thanks! 16:21:18 a lot of the other sessions are more "internal" work, and may be of interest, but those 3 are probably the most important ones 16:21:26 ok, I don't have conflicts with those. 16:21:28 for liaisons, that is :-) 16:21:30 excellent 16:22:44 I think we're ready for the summit, other than those missing etherpads, but let me know if you spot something I've missed 16:23:12 is everyone going to be in town for the whole week? 16:24:09 Yep 16:25:14 good -- I'm looking forward to this one :-) 16:25:28 #topic Review status for graduating libs 16:26:00 we have 2 graduations in progress now (funny, since it's graduation day here in Athens for the local university, too) 16:26:38 the repo for oslo.i18n has been created, and I have a series of patches up for review for a few minor cleanup issues spotted in the code that was imported 16:26:40 #link https://review.openstack.org/#/c/92678/ 16:26:44 that's the first review in the series 16:27:20 there are quite a few in progress for oslo.db as well 16:27:21 #link https://review.openstack.org/#/q/project:openstack/oslo.db+status:open,n,z 16:28:09 let's prioritize these reviews so we can get both of those libraries into shape and create an initial release soon after the summit 16:28:51 for both, I think we ought to be focusing on cleanup for "librarification" and bug fixes over new features, to start, does that seem reasonable? 16:29:16 +1 16:29:28 They have to work before we can add more stuff. 16:30:46 right 16:31:07 that's all we have on the official agenda today 16:31:11 #topic open discussion 16:31:19 does anyone have anything else they would like to bring up? 16:31:41 ok, got oslo.messaging status 16:31:49 ported: nova, glance, keystone, cinder, ceilometer, ironic, barbican 16:31:49 not ported: neutron (https://review.openstack.org/75861), heat (https://review.openstack.org/70633), trove 16:31:49 n/a: swift, marconi, sahara 16:31:59 the neutron and heat ports were abandoned 16:32:16 haven't found a trove one yet 16:32:16 I was told that my work on rootwrap will be tracked in oslo instead of Neutron. 16:32:45 So I guess after summit we'll have it in the agenda here, right? 16:32:51 YorikSar: Yes, that makes sense 16:33:13 YorikSar: yes, if there's anything you need to discuss we can add it to the agenda 16:33:18 dhellmann, ok, no review I can find for trove 16:33:35 markmc: ok, I'll poke the trove liaison 16:33:35 so, need to poke neutron and heat again, find someone to do the trove port 16:33:50 dhellmann: Well. I mostly just reported status there 16:33:56 #action dhellmann contact neutron, heat, and trove liaisons about oslo.messaging adoption 16:34:57 YorikSar: ok, that makes sense 16:35:11 dhellmann: If that's not needed here I think there won't be much to discuss after summit 16:35:21 other observation - I see ceilometer using a whole bunch of internal oslo.messaging config options 16:35:46 YorikSar: let's see how things go, and adjust as needed 16:35:47 rpc_backend, notification_topics, transport_url, control_exchange 16:35:57 dhellmann: Sure. 16:36:27 markmc: are they using those for subscribing to all of the notifications? 16:36:41 dhellmann, don't know yet 16:37:05 dhellmann, whatever the reason, they're not part of the public API - need to examine the use case and add APIs 16:37:46 markmc: right, maybe we can chat with jd__ at the summit 16:38:07 sileht more likely 16:38:15 one of those usages he's been working on a new API for 16:38:24 adding retry param to rpc client 16:38:25 ah, ok, jd__ is listed as our liaison 16:39:16 ah 16:39:48 if sileht is already working in this area, that's fine, but this is an example of why I wanted a contact for each project :-) 16:41:38 I think that about covers it for this week, so unless there's anything else to discuss we can stop a little early. 16:41:52 About https://review.openstack.org/#/c/86930/ 16:42:11 We're basically treating incubator db code as a stable branch now, so to backport to Icehouse he'll need to go oslo.db -> incubator -> incubator icehouse 16:42:39 yes, that's right 16:42:44 Should I leave the -2 until the oslo.db change merges, or drop it and mark it WIP? Or a third option I'm not considering? :-) 16:42:52 and we need to make sure we approve the patches in that order 16:43:49 I'm not sure which is the better way to ensure that, the -2 or the WIP. Maybe the -2? 16:44:29 -2 is the definitely won't merge option. WIP can be changed. 16:44:46 I guess I can just leave a comment for him to ping me when the oslo.db change merges and I can drop it then. 16:44:46 ok, let's stick with that until the oslo.db change merges 16:44:53 that sounds good 16:45:09 Okay, that's all I had. Thanks. 16:45:52 ok, let's all go enjoy a few minutes of free time then :-) 16:46:05 thanks, everyone, and I'll see you next week at the summit! 16:46:23 Until then! 16:46:33 dhellmann: "pretty quick meeting", aha :) 16:46:42 later :) 16:46:51 YorikSar: hey, we're getting out in < 1hr :-) 16:46:59 safe travels, everyone 16:47:01 #endmeeting