16:00:28 #startmeeting oslo 16:00:30 Meeting started Mon Mar 7 16:00:28 2016 UTC and is due to finish in 60 minutes. The chair is haypo. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:33 The meeting name has been set to 'oslo' 16:00:37 o/ 16:00:39 courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo, 16:00:42 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps 16:00:44 yo yo 16:00:45 courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb 16:00:48 courtesy ping for dukhlov, lxsli, rbradfor, mikal, nakato, tcammann1, browne, 16:00:51 _o/ 16:00:55 \o 16:00:55 o/ 16:00:55 yay! 16:00:58 hi 16:00:59 hi 16:01:01 o/ 16:01:04 o/ 16:01:05 dims asked me to organize the meeting today, i will follow https://etherpad.openstack.org/p/oslo-meeting-agenda 16:01:08 let's roll 16:01:18 o/ 16:01:41 #topic Red flags for/from liaisons 16:01:47 Nothing to report 16:01:53 none for keystone that I'm aware of 16:02:06 nothing major from neutron side 16:02:12 o/ 16:02:14 good, good :) 16:03:17 hum, it looks too easy. i just wait one more minute to ensure that everybody joined :) 16:03:21 :) 16:03:52 hello from rbradfor and dims from NYC - we are not really here :) 16:04:11 hi 16:04:14 #topic Any stop-ship Bugs needed to be fixed for Mitaka 16:04:20 o/ 16:04:39 dims, lol 16:05:38 o/ 16:05:59 strange, no blocker bug on oslo? :) no recent eventlet storm? :) 16:06:42 :-P 16:06:55 they did a release for some security thing right haypo ? 16:06:58 haypo: Don't look at gift horse in the mouth. 16:07:23 it's early, we may have some bugs filed this week as the other projects work on hardening 16:07:25 harlowja_at_home: i recall an email about a "funny" ssl bug 16:07:38 ya, haypo i sorta remember that one to, lol 16:07:42 *that email 16:07:52 harlowja_at_home: https://pypi.python.org/pypi/eventlet/0.18.4 was released at 2016-02-17, it looks like the security fix was not released yet? 16:08:00 oh 16:08:07 * harlowja_at_home finds that email 16:08:14 ok, let's move on 16:08:16 https://pypi.python.org/pypi/eventlet/0.18.4 16:08:18 oops 16:08:21 #topic Any bumps needed in global requirements? 16:08:30 i read "the minimum version of dogpile.cache was updated and only oslo.cache controls which version is used, so dims and dhellmann discussed an oslo.cache release this week to update that minimum" in the agenda 16:08:41 dhellmann: ^^ 16:08:59 dhellmann: is there something to do on oslo.cache? 16:09:00 yeah, I haven't looked to see if oslo.cache uses the latest dogpile, yet, but it should just be a requirements patch 16:09:10 when we have that, we need a new oslo.cache release to enforce the minimum everywhere 16:09:35 does someone want to volunteer to handle that? I can provide guidance but I have something else I have to do this week 16:09:37 rossella_s: I'm not sure how to download and implement the path.. I have problems running run_tests.sh because of that 16:10:30 dhellmann: https://github.com/openstack/oslo.cache/blob/master/requirements.txt#L6 dogpile.cache>=0.5.7 # BSD 16:10:58 ok, so we just need the release request 16:10:58 https://pypi.python.org/pypi/dogpile.cache latest release: 0.5.7 16:11:21 dims : were you going to handle the release, or are you busy squashing bugs? :-) ^^ 16:11:40 i see dogpile.cache===0.5.7 in upper-constraints.txt and dogpile.cache>=0.5.7 # BSD in global requirements 16:12:22 haypo : right, but only oslo.cache actually has a direct dependency on it iiuc, so we need to release oslo.cache to ensure that the >=0.5.7 is honored for installations outside of the gate 16:12:31 dhellmann: >=0.5.7 in oslo.cache is a recent change? we only need an oslo.cache release? 16:12:43 that is my understanding, from dims, yes 16:12:57 dhellmann: i can do the oslo.cache release 16:13:10 haypo : ok, if you submit the request I'll process it asap 16:13:13 #topic master branch is open for business 16:13:25 oh it is?? 16:13:25 lol 16:13:44 we haven't cut stable branches, yet, but we'll cut them from the most recent releases 16:13:47 kk 16:13:52 i didn't know, i copy/paste what's written in https://etherpad.openstack.org/p/oslo-meeting-agenda :-D 16:13:55 :) 16:14:06 * harlowja_at_home just checking 16:14:19 I expect to do the branching tomorrow, or late today when dims has time to coordinate 16:14:23 cool 16:14:31 sounds good 16:14:35 should we remove the -2 from "all oslo issues"? 16:14:49 +1 16:15:05 thought there was a script that did all those 16:15:10 probably script can undo all them, ha 16:15:17 harlowja_at_home : use the bknudson bot 16:15:21 bknudson: you put the -2 on "all olso issues", right? will you be able to remove these votes? 16:15:33 dhellmann: ah, bknudson is a bot? :-D 16:15:36 lol 16:15:38 just tell me when the stable branches are created and I'll remove the -2s 16:15:40 i'm a bot to 16:15:49 harlowja_at_home: i knew it! 16:15:51 hello! 16:16:11 :) 16:16:16 is there a script for this? otherwise I could put one together 16:16:28 it's easy enough to do it through the gui 16:16:40 if anyone has a script, they've kept it to themselves 16:17:03 bknudson : maybe put whatever you write in the release-tools repo? 16:17:21 ok, I'll take a stab at it 16:18:03 ok, more exciting stuff next: 16:18:05 #topic Gather session ideas for Austin 16:18:14 #link https://etherpad.openstack.org/p/newton-oslo-summit-planning 16:18:43 by the way, i understood that we are looking for a new Oslo PTL for the next cycle 16:18:56 seems like that's the case, ha 16:19:00 yes, I hope we have a few candidates 16:19:33 if anyone is considering running and wants to talk privately, I'd be happy to share my experiences and I'm sure dims would, too 16:19:53 just don't build a wall around mexico, thx, lol 16:20:17 i already see a few items for the oslo sessions 16:20:28 what's the deadline to propose new ideas? 16:20:44 I will get hats made that say "Make OSLO great again". 16:20:47 I'm not sure that's set, yet. Usually the new PTL is responsible for the planning. 16:20:55 the summi is in ~1 month 1/2 16:20:58 amrith : LOL 16:21:01 dhellmann : +1 16:21:08 amrith: lol 16:21:15 amrith: but will the hat be made in china? :0 16:21:29 kgiusti, of course! 16:21:35 dhellmann: oh, so we need a new PTL quickly :) at least before the summit :) 16:21:35 amrith, +1 :) 16:21:59 haypo : yes, nominations should open on the 11th and elections will happen about a week after that, I think 16:22:32 dhellmann, the election email said the appointment would be 3/24 16:22:43 #link https://wiki.openstack.org/wiki/PTL_Elections_March_2016 16:23:05 amrith : yes, that's when they close 16:23:12 should we kill https://github.com/openstack/oslo-incubator ? 16:23:25 or does it still contain anything useful? 16:23:51 it contains memories 16:24:02 harlowja_at_home : <3 16:24:07 harlowja_at_home: the lovely oslo namespace... 16:24:09 :) 16:24:25 https://github.com/openstack/oslo-incubator/blob/master/pypi/oslo/__init__.py 16:24:35 seems like its mostly tools/scripts now 16:24:38 and dashboards 16:24:46 ah yes 16:24:52 maybe rename ---> oslo_tools 16:24:54 or something 16:25:04 but i see no code anymore, so it's ok for me to keep it 16:25:06 #topic apply for stable:follows-policy tag 16:25:11 I saw on hound that a few projects still have copies of incubator in them, are we helping them clear those up? 16:25:12 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088592.html 16:25:12 yeah, renaming repos requires taking gerrit down so unless it's a really high priority I'd just leave it 16:25:16 looks like it no longer works. I recognized that some projects use still i.e. openstack/common/apiclient/ but that's gone and there is no olso.apiclient or so. 16:25:16 k 16:25:26 lxsli : we should make that a priority for the next cycle 16:25:30 lxsli: i sent some patches to solum 16:25:47 lxsli : see "Oslo Libraries Adoption" in the summit etherpad, line ~48 16:25:52 I have a todo this week to look at what Cinder is still using from incubator and try to clean things up. 16:25:54 dhellmann: cool, thanks 16:26:02 lxsli: but it looks non trivial to upgrade to oslo libraries :-/ i had to wait 1 month or more to get a review and then the patch doesn't apply... 16:26:14 :( 16:26:34 haypo : yeah, we will need to work with projects that have fallen behind to prioritize the reviews because the patch will be somewhat big 16:26:40 for the state:follows-policy tag, should all of oslo libraries have said tag? 16:26:43 I think at this point they have to adopt all of the libraries at once 16:26:50 *stable:follows-policy 16:27:07 harlowja_at_home : pbr does not, and mox3 probably shouldn't be counted as following 16:27:10 k 16:27:21 stable:follows-policy-a-little 16:27:22 harlowja_at_home : but most will, yeah -- we need to review the list and see what makes sense 16:27:23 dhellmann: hum, it's not easy to produce reviewable patches that fix everything at once 16:27:33 harlowja_at_home : stable:only-a-bit-wobbly 16:27:37 :) 16:27:43 my latest solum change: https://review.openstack.org/#/c/273566/ 16:27:54 haypo : yes, an incremental change modifying incubated files may be another approach 16:28:20 dhellmann: sounds better 16:28:26 for solum, my "Use oslo_serialization library" change was already merged 16:28:42 dhellmann: it's a compromise yes 16:29:23 toabctl: apiclient was declared dead and must be replaced with keystoneauth and cliff no? 16:29:24 in the past we didn't want to do that because it meant drift between projects and the incubator, but since the incubator is empty now... 16:30:22 harlowja_at_home, dhellmann : sorry i didn't follow, is there anything to do for stable:follows-policy ? 16:30:46 haypo : someone needs to figure out which libs should have the tag, and propose a patch to the governance repo to apply them 16:31:05 maybe dims and some of our PTL candidates can consult on that 16:31:25 ok 16:31:35 sounds good 16:31:41 since that's the sort of thing a PTL would need to do... 16:31:51 #topic Open discussion 16:31:52 Any stuck reviews? 16:32:36 would you mind to review this simple backport to liberty? https://review.openstack.org/#/c/277160/ oslo.log & Add ISO8601/RFC3339 timestamp to ContextFormatter 16:32:38 https://review.openstack.org/#/c/287470/ simple one (with a real bug associated) 16:33:01 haypo : that's a feature, isn't it? 16:33:50 dhellmann: it's unclear to me if isotime is something new or not :-p 16:34:27 I'd call it a feature tbh 16:34:55 adds a var to the format 16:35:01 haypo : yeah, it also adds a new requirement and that's forbidden 16:35:21 dhellmann: yeah, it adds a dep to python-dateutil 16:35:40 yeah, unfortunately we can't take that change 16:35:55 what we could do is test the mitaka release of oslo.log with liberty to see if they could use that instead 16:35:55 dhellmann: i don't recall the rationale, it's to respect a standard for logs 16:36:24 dhellmann: if it doesn't occur upstream, we may backport the change downstream ;) 16:36:46 that's a downstream distributor's choice 16:37:39 dhellmann: i don't think that we use an oslo version of a more recent openstack, we usually backport changes downstream. but yeah, it's our problem :) 16:37:53 harlowja_at_home: i should take a look, but it's non trivial at the first look :) 16:38:02 I do see this as useful and important, it just doesn't fit our backport policy 16:38:16 dhellmann: sure, i understand the policy :) 16:38:29 anything else? 16:38:35 i have to leave :) 16:38:46 nothing from me 16:38:51 thanks for running the meeting, haypo 16:38:54 #endmeeting