16:00:23 #startmeeting oslo 16:00:23 courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo, 16:00:23 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, 16:00:25 courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek 16:00:25 o/ 16:00:27 o/ 16:00:28 Meeting started Mon Jul 27 16:00:23 2015 UTC and is due to finish in 60 minutes. The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:28 o/ 16:00:28 hi 16:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:31 The meeting name has been set to 'oslo' 16:00:31 o/ 16:00:32 o/ 16:00:45 o/ 16:00:52 o/ 16:01:03 o/ 16:01:03 o/ 16:01:05 yo yo 16:02:01 #topic actions from last week 16:02:18 i have to find a good time for virtual sprint for documentation 16:02:38 google hangout is acceptable? 16:02:46 whats google, lol 16:03:13 o/ 16:03:14 harlowja_at_home: they won't let u use google stuff? :) 16:03:18 :-P 16:03:28 nah, google hangout is fine 16:03:45 +1 16:03:51 i'll send out a doodle poll to gauge interest 16:03:58 and time 16:04:08 #topic Red flags for/from liaisons 16:04:26 no red flags for keystone 16:04:34 o/ Here now. 16:04:51 nothing from neutron, though I'm dug under other stuff so can be out of sync 16:04:54 We had some folks that had a problem with the python version strings in the requirements file 16:05:07 No red flags from Cinder. 16:05:10 johnsom: i think there was a pbr relesae 16:05:14 Not sure which package they needed. 16:05:16 release 16:05:19 looks like oslo.cache will have python3 support, so that's good. 16:05:35 nothing's up in glanceland 16:05:58 bknudson: yes, python-memcached version got released over weeked (i had email the maintainer) 16:06:11 oh, websockify release as well 16:06:15 needs a reqs bump then 16:06:24 bknudson: already filed for both 16:06:41 got merged too 16:07:06 #link https://review.openstack.org/#/c/205851/ -- reqs update ? 16:07:32 right 16:07:42 dhellmann: can you please bless that one? 16:07:49 * dhellmann clicks 16:07:58 thanks 16:08:02 #topic Releases for this week 16:08:02 Releases for this week. Here are the unreleased changes 16:08:02 #link https://etherpad.openstack.org/p/library-releases 16:08:20 dims, bknudson : approved 16:08:34 thanks dhellmann~ 16:09:18 anyone spot anything fishy which may affect the L2 timeline in the releases for this week? 16:09:23 please holler 16:09:47 dims: can we add https://review.openstack.org/#/c/205646/ to oslo.db release? 16:10:07 nothing critical, just nice to have 16:10:11 rpodolyaka1: will have to wait till next week 16:10:17 dims: ok, np 16:10:30 * harlowja_at_home doesn't see to many fish 16:10:55 rpodolyaka1: i run the master of all the oslo projects against a handful of projects on sun night / mon morning and the SHA's are from there - https://travis-ci.org/dims/glance 16:11:16 rpodolyaka1: so if we need something, we should try to merge it by friday 16:11:25 or sat 16:11:26 dims: cool! thank you for clarifications! 16:11:37 hope the timeline helps in planning 16:11:45 it does! 16:12:06 dims: cool stuff ) 16:12:30 so next week will be big bang release of all projects since many have been accumulating global requirements syncs and not much code changes 16:12:57 cool 16:13:09 more big bang for the buck 16:13:34 (or whatever that statement is) 16:13:35 lol 16:13:47 :) 16:13:53 #topic oslo.privsep project spec 16:13:53 #link https://review.openstack.org/#/c/204073 16:14:11 uh ohes, lol, angus around? 16:14:24 there's been a bunch of discussion and revisions to that spec, just want to be sure folks get a look at it and provide feedback 16:14:27 rootwrap is in oslo already? 16:14:30 harlowja_at_home: 2 AM his time 16:14:42 dims, ah, k 16:14:43 bknudson: oslo.rootwrap...yes 16:15:36 so please take a look and let's get Angus going 16:15:46 +1 16:15:47 so this is phasing out rootwrap 16:16:12 hopefully developers won't abuse it the same way they abused rootwrap 16:16:25 since developers just do whatever's convenient 16:17:00 bknudson: don't know yet. please tell other keystone folks to look as well 16:17:12 keystone doesn't use rootwrap 16:17:16 lol, i have a feeling all the things will get abused, but as long as u try to provide good examples and such of not abusing it, and peer reviews, then not much else u can do, there will always be abusers :-P 16:17:34 ^ wise words of wisdom, ha 16:17:41 bknudson: i know, you all are the closest to security stuff :) 16:17:58 there's an OSSG (security group) 16:18:05 I'll bring it up a the meeting 16:18:11 bknudson: awesome thanks 16:18:16 since we discussed this at the last meeup 16:18:35 cool. switching topics 16:18:38 #topic New libraries and drivers - how is it going? 16:18:39 #link specs - http://specs.openstack.org/openstack/oslo-specs/ 16:18:39 #link library audit - https://docs.google.com/spreadsheets/d/1eTR-pN2GD5cK_tHIMyKNL5vh4N8JtXTptcE1bLd2G3E/edit#gid=0 16:18:50 dims: we had some progress with rpc functional tests https://review.openstack.org/#/c/205117 16:19:00 dims: notifier and devstack next 16:19:13 ozamiatin: very cool 16:19:45 hoping we will get more folks to kick tires when we get devstack going 16:19:45 dims: patches available for kerberos and python3 support WIP until proton 0.10 is released 16:20:07 kgiusti: ah. any ETA? 16:20:26 dims: proton 0.10 in beta now - two blockers outstanding. 16:20:52 sounds close. thanks kgiusti 16:21:10 dims: no 'hard' eta - just pending those blockers. 16:21:18 right 16:22:03 there's a patch in nova for oslo.cache too 16:22:34 #topic Ongoing work & Review priorities 16:22:34 #link https://etherpad.openstack.org/p/liberty-oslo-priorities-tracking 16:22:34 Any stuck reviews? or specs? 16:23:20 it'd be nice to have https://review.openstack.org/#/c/196338/ in before doing a debtcollector release dims 16:23:45 if anyone else wants to look over that 16:23:55 * harlowja_at_home added note in https://etherpad.openstack.org/p/library-releases 16:24:35 harlowja_at_home: the keystone folks mentioned that debtcollector was not working for them in some scenarios..recall anything? 16:25:08 hmmm, don't recall that 16:25:33 I was looking to use it in keystoneclient since a bunch of stuff wasn't deprecated correctly 16:25:51 any idea what wasn't working? 16:25:54 and most scenarios it didn't apply or I couldn't find documentation that showed that it worked. 16:26:02 I can put together a list if you'd like 16:26:14 the reviews will show what I wanted to deprecate 16:26:17 ok 16:26:21 bknudson: thanks! lets work it as a bug 16:26:27 ' couldn't find documentation that showed that it worked' means more docs or something? 16:26:31 ok, I'll open bug 16:26:51 so in the nova mid-cycle this came up - https://review.openstack.org/#/c/205779/ - TRACE logging level 16:26:52 docs might be required or maybe the code needs to be updated so that it works. 16:26:58 bknudson, ok 16:27:07 I don't know if the library supports it since I was looking at the docs 16:27:08 this was a recommendation from the log WG i believe 16:27:36 bknudson, okie dokie 16:27:40 dims, +1 16:27:46 although, TRACE = int((logging.DEBUG + logging.NOTSET) / 2) lol 16:27:56 TRACE = 5 imho better, ha 16:28:03 sputnik13, https://review.openstack.org/#/c/205779/ - TRACE logging level 16:28:16 did they ever get rid of logging stacktraces at TRACE? 16:28:22 did not know how static they were...frozen forever? 16:28:24 I thought that was the first step 16:28:34 dims, pretty sure frozen forever 16:28:35 bknudson: yes, i already did 16:29:00 harlowja_at_home: ack 16:29:06 dims, https://github.com/openstack/taskflow/blob/master/taskflow/logging.py#L24 if u want other usages of it 16:29:16 for reference purposes, others use 5 to 16:29:36 thanks 16:29:46 #topic Open discussion 16:29:51 Sheesh. I thought they were joking about it being halfway between the two levels but they actually do the math. 16:30:04 jungleboyj: that was me...not them :) 16:30:44 dims: Ok. 16:30:46 :-) 16:31:39 anything else to discuss? 16:32:13 so in glance, we were talking a little about having an oslo.rbd library 16:32:44 common code between cinder + glance? 16:32:52 yep 16:32:53 yeah 16:33:15 anyone else likely to use? 16:33:15 is this something people from cinder would be interested in? 16:34:13 jungleboyj: ^^ 16:34:20 I think we should ask e0ne 16:34:40 e0ne would be good to ask. 16:34:47 okay 16:34:51 kragniz: What code would you be moving there? 16:35:07 kragniz: glance_rbd (like glance_store) is not a possibility? 16:35:30 you can always have the ACL with the right set of folks from both glance and cinder 16:36:40 jungleboyj: mostly the connection stuff and helper functions 16:37:02 I pinged e0ne, but his is afk 16:37:13 jungleboyj: no real plan, someone just mentioned it and we thought it could be something others would be interested in 16:37:38 kragniz: Are you familiar with os.brick? 16:38:15 jungleboyj: a little, it's sort of what glance_store tries to be but for cinder? 16:38:19 originally it was sigmavirus24 idea 16:38:35 heh, well I had heard the words "borrowing from cinder" so 16:38:59 kragniz: Not sure about glance_store but it is where we have all the functions that need to be shared between nova and cinder. 16:39:31 I would want to maybe look and see if that is something that could be used before starting another library. That would be my $0.02 there. 16:40:02 okay, we should have a look 16:40:02 Otherwise, I am all about reducing code duplication. :-) 16:40:16 ++ to check before starting a new one 16:40:42 so let's wrap up this meeting then 16:40:44 thanks everyone 16:40:46 kragniz: https://github.com/openstack/os-brick 16:40:46 thanks 16:41:00 jungleboyj: thanks 16:41:03 kragniz: Let me know if you want to talka bout it more. 16:41:07 will do 16:41:08 dims: Thanks! 16:41:20 see you all next week 16:41:23 #endmeeting