08:14:21 #startmeeting ptl_sync 08:14:22 Meeting started Tue Apr 14 08:14:21 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:14:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:14:25 The meeting name has been set to 'ptl_sync' 08:14:29 #topic Nova 08:14:51 #Info RC1 was out last Friday 08:15:14 #link https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential 08:15:31 yes, thats a sorry list, there are a good few we will want for RC2 08:15:38 I see a critical bug fixcommitted there, probably a good reason to trigger a RC2 soon 08:15:52 yes, some of the high ones are probably required too 08:16:09 At this point I'd like to keep the RC1 up for a couple more days, so best to pile up the fices on master ? 08:16:16 fixes* 08:16:20 I think so 08:16:26 lol, I like the typo... 08:16:54 When we'll open the RC2 we'll consider all the fixcommitted stuff on that list 08:17:04 so that we can open and close it fast 08:17:19 OK, thats sounds good, I don't think I will loose sleep over any of the non-fixcommitted ones at this point 08:17:28 But givne the critical bug I think we should target end of week for Nova RC2 08:17:50 yes, that sounds good, we will want folks testing it out 08:18:02 so ideally we would have all the showstoppers fix committed in master by Thursday or so 08:18:18 open then, backport all, and tag on Friday ? 08:18:27 yeah, right now, I think we are already there, assuming we don't find any more 08:18:33 yes, that should work 08:18:40 #info Likely RC2 by end of week due to https://bugs.launchpad.net/nova/+bug/1442656 08:18:42 Launchpad bug 1442656 in OpenStack Compute (nova) "live migration fails, because incorrect arguments order passed to method" [Critical,Fix committed] - Assigned to Timofey Durakov (tdurakov) 08:19:20 (looking forward to two host devstack gate...) 08:19:20 On the lib side, you don't have any critical bug to ship in python-novaclient, right ? 08:19:38 good question, I haven't seen any crop up 08:19:56 we'll cut the stable branch there asap after RC1 08:19:58 it would have been good to support v2.1 at release, but thats a good way off at this point 08:20:26 Ok, my last topic would be the design summit space allocation 08:20:43 I've seen people in #nova discussing the choice of 18 fishbowl sessions 08:21:00 yes 08:21:14 that will be hard to change at this point, given that I allocated most of the slots so not a lot of wiggle room 08:21:14 I think it was the feeling of being "left" out of having the project room things 08:21:46 but honestly, we never really used the pod when we had one before, so thats probably fine 08:21:49 Note that it doesn't actually prevent you from disguising a fishbowl into a work session 08:21:59 by using the right titles 08:22:04 yes, thats fair 08:22:33 The only difference is the rooms size / setup and how it looks like on the schedule. For the latter, disguise is possible. 08:22:52 cool, thats a good point, will pass the message on when we pick sessions 08:23:30 OK, that's all I had. I'll be in touch Thursday/Friday so that we open/close that RC2 then 08:23:45 I'll be traveling those two days so I may not be very available 08:23:49 yes, that sounds good, I am around normal times Thursday and Friday 08:23:57 but I'll make sure I'm here for the critical steps 08:24:13 ah, gotcha, understood 08:24:21 safe travels! 08:25:15 cheers! 08:25:22 stevebaker: around ? 11:49:57 ttx: knock, knock ... if you've the flexibility to start a few mins early, just shout 11:50:20 eglynn: I do 11:50:28 #topic Ceilometer 11:50:35 cool 11:50:43 thanks for getting kilo-rc1 cut 11:50:54 do we need an explicit kilo-rc2 milstone in LP? 11:50:59 or created on demand? 11:51:14 (i.e. if we a blocker we want to get on proposed/kilo) 11:51:23 if we *have a ... 11:52:04 actually we only open the milestone once we decide a respin is warranted 11:52:19 otherwise it detrracts testers from giving rc1 a spin 11:52:27 a-ha, cool, so on-demand 11:52:31 makes sense 11:52:39 yeah, so we should review the kilo-rc-potential list now 11:52:53 https://bugs.launchpad.net/ceilometer/+bugs?field.tag=kilo-rc-potential 11:53:27 #info Ceilometer RC1 was published last Thursday 11:53:36 nada as yet on that tag 11:53:46 The list being empty, I'd say there isn't much on your radar yet ? 11:54:04 nope, but I'll keep an eye on it ... as is gordc obviously 11:54:09 Note that we'll proabbly do a RC2 anyway to clean up translatiosna nd import the last requirements pins 11:54:14 (once everyone has done a RC1) 11:54:19 cool 11:54:30 * ttx has a quick look to FixCommitted bugs 11:54:44 (which means they are fixed on master but not backported yet 11:55:03 https://bugs.launchpad.net/ceilometer/+bugs?field.status%3Alist=FIXCOMMITTED 11:55:44 https://bugs.launchpad.net/ceilometer/+bug/1403024 is probably fixreleased and not fixcommitted 11:55:45 Launchpad bug 1403024 in Ceilometer "Ceilometer upgrade is coupled to other projects" [High,Fix committed] - Assigned to gordon chung (chungg) 11:56:18 https://bugs.launchpad.net/ceilometer/+bug/1408248 is not really backport material 11:56:20 Launchpad bug 1408248 in Ceilometer "Alarm action should be checked when create alarm" [Undecided,Fix committed] - Assigned to ZhiQiang Fan (aji-zqfan) 11:56:34 So at this point, I would say we are good 11:56:34 agreed 11:56:51 speaking of gordc, just wanted to clarify the timing on the transition 11:57:00 le PTL est mort, vivre le PTL! ;) 11:57:09 You handle kilo he handles liberty 11:57:44 yeap, so I'll continue with these 1:1s until kilo is finalized 11:57:46 You don't have anything coming up on the library side until release ? 11:57:48 but Gordon will be coming to the cross-proj meetings for summit planning etc. 11:58:14 This is more for gordc, but any issue with your summit space allocation ? 11:58:27 I think we could grant what you asked for 11:58:32 is there any flexibility to increase that slightly? 11:58:43 I ask because we'll be sharing with gnocchi 11:59:02 not a big issue, just wondering if any wiggle room 11:59:03 not really, as I explained in my email. We have free room but it comes with constraint 11:59:11 cool enough 11:59:18 like runs at the same time as cross-project sessions 11:59:27 yeap, non ideal 11:59:34 I have one extra fishbowl slot, I can add you on the ballot 11:59:42 cool, thanks 11:59:43 Already have two teams asking for it :) 11:59:48 k 12:00:03 Alright, that is all I had 12:00:14 me too, thanks for your time :) 12:00:23 ok, ping me if something critical comes up 12:00:27 will do 12:00:35 so that we do the RC2 soon rather than late 12:14:05 ttx: I'm not sure we have much to cover today, but I'm around if you want to chat 12:14:13 dhellmann: I do want to chat. 12:14:23 * dhellmann feels warm and fuzzy 12:14:25 #topic Oslo 12:14:34 I don't think I have any Osloic stuff to cover 12:14:45 k 12:14:51 ttx, good morning, ready when you are 12:14:54 but I wanted to ask if you would be available / interested in chairing the cross-project meeting tonight 12:15:05 since I'll be busy cutting the last RCs at that time 12:15:07 sure, I can do that 12:15:19 dhellmann: i'll be around but probably multiplexing 12:15:31 so I prefer to let someone else drive the discussion 12:15:33 Thx! 12:15:35 * dhellmann checks the agenda 12:16:39 ok, is there anything special about either of the specs topics you wanted to make sure we covered? 12:17:05 not really. Just get the discussion moving. The first one was added by the proposer, I added the second one to pad the agenda 12:17:14 ok 12:17:33 and are we ready to open up cross-project submissions (I may have missed an email about that if you've already sent it) 12:17:40 The other topic is playing with caps tomorrow. We expect the last RCs today / early europe tomorrow, so that means we should be able to cut the requirements stable/kilo branch in your morning 12:17:47 what sort of "brainstorming" were you looking for? 12:17:48 dhellmann: already opened 12:18:01 ok, I'll find that email to provide links for folks 12:18:06 dhellmann: like see what's on the list and what else is missing, and who volunteers to post it 12:18:15 got it 12:18:36 So I was wondering if you would have some time in your tomorrow morning to help me run through that 12:18:42 (the requirements kilo stuff 12:18:43 ) 12:18:56 yes, definitely, let me make sure I don't have anything scheduled 12:19:07 since I'd prefer to have people to peert review what I do 12:19:31 I'm wide open tomorrow 12:19:32 try to avoid blatant missteps while we fumble our way through this 12:20:00 yep, we can share the blame :-) 12:20:16 OK, I'll etherpad the plan how I see it, so we can prep a bit 12:20:42 sounds good 12:20:57 dhellmann: thanks a lot! I'm traveling Thursday morning so I'd rather have that past us on Wednesday. 12:21:10 so your help is mucho appreciated. 12:21:12 no problem, I'm happy to help 12:22:06 that is all I had for today. Focus for today is to get all RC1s done but there isn't much to do to help there 12:22:20 I'm already barking up all the trees 12:22:39 dhellmann: ttyl! 12:22:42 SergeyLukjanov: around? 12:22:43 ok, I'll let you get on with SergeyLukjanov then 12:22:46 ttx: thanks 12:22:47 #topic Sahara 12:22:52 ttx, yup 12:23:11 #info Sahara RC1 was out last Thursday 12:23:21 no critical issues right now 12:23:26 to be fixed in Kilo 12:23:27 #link https://bugs.launchpad.net/sahara/+bugs?field.tag=kilo-rc-potential 12:23:48 this two marked with a tag on other projects (launchpad sucks) 12:24:00 yep, we are good. I don't think https://bugs.launchpad.net/sahara/+bug/1435439 is worth a respin 12:24:02 Launchpad bug 1435439 in Sahara "Long name of templates in scenario yaml files leads to validation failures" [Medium,Fix committed] - Assigned to Evgeny Sikachev (esikachev) 12:24:12 for Sahara we've marked them to be fixed in Liberty 12:24:34 yeah, it's a minor issue with tests 12:24:38 SergeyLukjanov: note that we'll probably do a RC2 anyway to clean up translations and import the stable/kilo requirements, but no hurry 12:24:55 If you don't have anything critical up, no reason to rush it this week 12:25:08 ttx, great, we'll probably want to fix a few issues in docs 12:25:13 No last-minute surprise lib upgrade ? 12:25:18 ttx, nope 12:25:41 How about your Design Summit space allocation ? Let me know if you have too much :) 12:26:26 ttx, we'll discuss it on the irc meeting this week, but I think that it's ok, it ~ the same as in Paris + half day meetup 12:26:50 ack 12:26:58 in Paris time was fully used, so, I think that we'll consume more time this summit 12:27:22 Well, if everything works -- you can also spend some time on https://wiki.openstack.org/wiki/ReleaseNotes/Kilo already :) 12:27:44 ttx, ack 12:27:52 SergeyLukjanov: let me know if anything critical comes up. Talk to you later! 12:28:02 ttx, yup, thank you! 13:39:04 ttx: Here when you're ready 13:40:30 just a sec 13:41:25 Sure, no problem 13:44:33 mestery: o/ 13:44:37 #topic Neutron 13:44:41 ttx: o/ 13:45:07 #info Neutron RC1 was published last Thursday 13:45:12 yay! 13:45:16 ;) 13:45:26 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=kilo-rc-potential 13:45:36 I see a critical fixcommitted thing there 13:45:43 Yes: https://bugs.launchpad.net/neutron/+bug/1440183 13:45:44 Launchpad bug 1440183 in neutron "DBDeadlock on subnet allocation" [Critical,Fix committed] - Assigned to Dane LeBlanc (leblancd) 13:45:53 But the real fix isn't committed yet 13:46:03 The committed thing is a partial 13:46:06 The real one is here: https://review.openstack.org/#/c/172092 13:46:20 Should we turn that bug back to InProgress ? 13:46:25 YEs 13:46:34 Don 13:46:35 Done 13:46:40 OK 13:46:51 So it looks like you'd rather want an early RC2 than a late one 13:47:01 I'd like to keep RC1 up for testing for a couple days more 13:47:02 Let me sync with armax and HenryG on that fix 13:47:07 if only so that all RC1s are done first 13:47:12 Right 13:47:13 Agreed 13:47:27 We could open a RC2 window at the end of the week and backport all RC stuff then 13:47:30 It's likely we'll want that fix in our RC1 13:47:32 RC2 13:47:32 sorry 13:47:34 In the mean time, just pile up fixes on master 13:47:37 Makes sense 13:47:39 Got it 13:47:56 I'll be in touch toward the end of the week to do the RC2 window 13:47:58 Once we open it, I'll backport all the ones we need into the RC branch in preparation for RC2 13:48:01 Cool 13:48:12 although I'll be traveling and seeing some users, so probably not very available 13:48:23 OK, email works too, we can do this async 13:48:23 worst case scenario we'll close it next Monday 13:48:30 That works too 13:49:00 What else.. no suprise last-minute library bump ? 13:49:14 Heh, nothing planned now. 13:49:19 ok :) 13:49:21 OUr library plan is this: 13:49:29 2.3.x for Juno, 2.4.x for Kilo, and 2.5.x for Liberty 13:49:51 ideally that would follow semv er rather than cycle, but if you can make that work, why not 13:50:14 I think that does follow semver, right? 13:50:37 Sure, but basically if you want to do multiple releases that change API in the same cycle you could bump Y twice in the same cycle 13:50:54 Ah, got it! 13:50:57 That makes sense 13:51:02 better than not doing it and breaking semver 13:51:10 Yes 13:51:18 On the design summit side, saw your space allocation ? 13:51:54 YEs, looks like we got what we wanted I believe. Do you hve that link handy by chance? 13:51:54 I gave you an extra fishbowl compared to what you asked. If you don't need it, let me know 13:52:16 http://lists.openstack.org/pipermail/openstack-dev/2015-April/061167.html 13:52:31 OK, I'll let you know, and thanks! 13:52:37 I had missed the extra fishbowl for some reason 13:52:40 Good of you to point it out 13:52:59 I try to fix the most blatant activity / allocation mismatches 13:53:21 :) 13:53:25 Just worked on a room layout that avoids conflicts across the board. Not my idea of fun 13:53:34 So I don't look forward making adjustment 13:53:41 oh wow 13:53:44 no kidding 13:53:51 Thanks for all your work here! Brutal I bet. 13:54:17 Will publish the proposed layout at end of week, so you can all point to mistakes I made :) 13:54:22 lol 13:54:38 it's tricky because most teams would prefer to have fishbowl sessions before their work sessions 13:54:55 but well, spacetime doesn't bend that well 13:55:09 :) 13:55:21 We'll make do with whatever you decide on 13:55:22 anyway, that's all I has. Run to your next meeting 13:55:29 had* 13:55:51 :) 13:55:51 You too! ;) 13:55:54 And thanks! 13:56:13 Although, neutron meeting was yesterday, we rotate, today I get to do actual work after our 1:1! :) 13:57:11 oooooh 13:57:21 lol 14:19:08 hi 14:19:14 nikhil_k: o/ 14:19:18 #topic Glance 14:19:46 #info Glance published its RC1 last Friday 14:20:00 #link https://bugs.launchpad.net/glance/+bugs?field.tag=kilo-rc-potential 14:20:17 There are a few bugs in there, but nothing fixed yet 14:20:24 so nothing to backport 14:20:36 yes, not yet 14:20:43 Anything aboslutely critical that you'd definitely include in a RC2 ? 14:21:14 there's one thing breaking in the client 14:21:20 https://trello.com/b/GFXMXxsP/openstack-glance 14:21:27 https://trello.com/c/ta4znZq9/43-no-ssl-breakage-https-bugs-launchpad-net-python-glanceclient-bug-1442664 14:21:37 https://trello.com/c/sT073qbx/44-re-enable-the-juno-and-kilo-check-runs-for-the-client-https-review-openstack-org-c-172999 is related 14:22:44 ttx: this one for kilo https://bugs.launchpad.net/glance/+bug/1436877 14:22:45 Launchpad bug 1436877 in Glance "metadef JSON files need updating for the Kilo release" [Medium,In progress] - Assigned to Wayne (wayne-okuma) 14:23:41 ttx: also https://bugs.launchpad.net/glance/+bug/1432701 14:23:41 Launchpad bug 1432701 in Glance "Glance API fail to list 'deleted' images" [Medium,In progress] - Assigned to Fei Long Wang (flwang) 14:24:04 nikhil_k: ok, you should get those fixes in master ASAP so that they are ready to backport 14:24:34 We could open a RC2 window once those two are fixed in master 14:24:43 ideally at the end of the week 14:25:18 ttx: one more that I'm still trying to find if it's in RC1 or not https://bugs.launchpad.net/glance/+bug/1434237 14:25:19 Launchpad bug 1434237 in Glance "glance-manage db_export_metadefs fails with NoSuchColumnError" [High,Fix released] - Assigned to Ashish (ashish-jain14) 14:25:41 ttx: and thanks, I will look into those 2 for reviews 14:26:07 that last fix is in RC1 14:26:18 https://git.openstack.org/cgit/openstack/glance/commit/?id=da4fb02ad6a190dc8e93b7683c04b1feb5a4c9ea 14:26:42 ttx: yes, found it. thanks 14:27:12 ttx: what can we do about the client? 14:27:25 will a new release be acceptable? 14:27:33 Xdepends how much there is in it 14:27:41 hmm 14:27:54 ok, may be I will discuss about backporting a fix then 14:27:59 We could cut the stable branch before and make a point release in the kilo branch 14:28:10 sure 14:28:13 so that it's a backport and not a master tag 14:28:22 ok 14:28:30 In all cases the fix will have to be in master too 14:28:51 #info Likely to require a glanceclient point release to fix https://bugs.launchpad.net/python-glanceclient/+bug/1442664/ 14:28:53 Launchpad bug 1442664 in python-glanceclient "Since 0.16.1 client breaks nova when using https" [Critical,In progress] - Assigned to Stuart McLaren (stuart-mclaren) 14:29:06 cool 14:29:08 Nothing on the glance_store side right 14:29:26 On the design Summit space allocation, I think I gave you what you requested 14:29:39 Let me know if you have too much. Or if you'd really want more 14:29:55 (I don't have anything to give but some projects might have overcapacity) 14:30:18 about glance_store 14:30:19 (see http://lists.openstack.org/pipermail/openstack-dev/2015-April/061167.html for reference) 14:30:30 some people want glance_store 0.4.0 as stable 14:30:54 that is what you'll have 14:31:08 and about the space allocation, all good for now. And I have discussed with the team and nothing came back for requesting changes 14:31:11 since it's out already 14:31:15 ttx: thanks! 14:31:38 Alright. I'll be in touch at the end of the week to open this RC2 14:31:47 In the mean time... get those fixed in master 14:31:56 ttx: I've been a little out of sync with lib stable release structure but thanks for the pointer 14:31:58 otherwise I'll stay with the RC1 :P 14:32:09 and yeah, I will look into those 2 for backports 14:32:24 thingee: around? 14:33:23 ttx: o/ 14:33:28 #topic Cinder 14:33:45 #info Cinder RC1 was out last Thursday 14:33:57 #link https://bugs.launchpad.net/cinder/+bugs?field.tag=kilo-rc-potential 14:34:13 One fix ready for backport on the list... how critical is it ? 14:34:35 not critical 14:34:41 * thingee removes tag 14:35:29 ok, so nothing RC yet ? Let's keep the RC1 up at least until Monday then 14:35:42 We have to do a RC2 to sync translations and requirements one last time anyway 14:35:56 we should see then what we have fixed in master and available for backports 14:36:22 Sounds good? 14:36:47 oh well if that's the case, we could probably have this fix ready. It just has some nits in the change. Maybe admin adjusting quotas is a bit important :) 14:37:13 right, we usually have a look at all FixCommitted to see which are safe fixes to include once the window is open 14:37:14 I've already tested the patch. just has some nits on test assert order :) 14:37:29 so the best thing to do is just to get them fixed in master 14:37:31 In the mean time you can start working on https://wiki.openstack.org/wiki/ReleaseNotes/Kilo 14:37:53 Anything critical coming up on the library side ? 14:38:19 nope, but I was traveling all of monday. so I might be a little out of date 14:38:28 Haven't heard anything :) 14:38:33 I will triage today and ping you if there is anything added in the tag 14:38:51 I sent an email to the list last week with proposed space allocation for design summit 14:39:02 you should doublecheck I got you something you can work with 14:39:04 yes saw that 14:39:10 sure 14:39:40 * thingee notices etherpad appears to be down to check current sessions 14:39:47 oh there we go 14:39:56 https://etherpad.openstack.org/p/cinder-liberty-proposed-sessions 14:39:57 needs a full reload, changed servers 14:40:00 mostly work sessions 14:40:43 Note that you can turn a fishbowl into a work session by choosing an obscure title. The other way around is more difficult since workrooms are so small 14:40:53 I might balance things to be in the fish bowl 14:41:17 gotcha 14:41:23 sure, as soon as you want non-Cinder-core to notice, should be a fishbowl 14:41:50 Alright that is all I had 14:42:01 I'll talk to you at end of week or early next 14:42:07 david-lyle: around? 14:42:40 thanks 15:17:56 ttx: o/ 15:17:57 david-lyle: around? 15:18:00 #topic Horizon 15:18:43 So, we still have to produce a RC1, and ideally that would hjappen today, since Horizon will be the last to hit RC1 and therefore the only reason why we are still freezing requirements 15:19:04 What are we waiting on at this point ? 15:19:06 django_openstack_auth 1.2.0 has been released 15:19:14 https://review.openstack.org/#/c/173162/ ? 15:19:44 https://review.openstack.org/#/c/173161/ maybe 15:19:56 well there's an open questoin 15:20:00 *question 15:20:19 we could potentially leave the requirements cap open and not require 1.2.0 15:20:22 but allow it 15:20:39 but only 1.2.0 will allow Django 1.7 15:20:49 but the older versions are backward compatible 15:21:02 err, newer versions 15:21:17 other than python 2.6 support being removed in 1.2.0 15:21:28 Hmm, let me think 15:21:39 I would like to make a stable branch with 1.2.0 15:21:39 Kilo requires Django 1.7 ? 15:21:45 or not 15:21:46 does not require 15:21:56 1.4 - 1.7 are supported 15:22:05 1.4 because it was the last LTE 15:22:23 But to run django 1.7 you need doa 1.2.0 15:22:29 yes 15:22:40 does doa 1.2.0 require django 1.7 ? 15:22:46 or just support it ? 15:22:51 supports it 15:23:06 hmm, then I don't see the point in forcing people to use it 15:23:10 We need it out for sure 15:23:22 I feel like the d-o-a release we enough 15:23:23 but only people running django 1.7 need it 15:23:28 exactly 15:23:29 yeah, sounds like it 15:23:36 ok, let tag horizon then 15:24:00 and I'll abandon my other patches, the question is about stable branch of d-o-a for Kilo 15:24:20 can we just make that from 1.2.0 ? 15:24:25 yes 15:24:33 will be <1.3.0 15:24:44 ok, that works 15:24:50 next doa on liberty will have to be 1.3.0, and we keep 1.2.x for backports in case of need 15:24:57 oslo-style 15:25:07 will be less risky for horizon plugins in the eco-system too to not bump the requirements version 15:25:15 * ttx just has a mental picture of Doug dancing Gangnam style 15:25:32 that works for me 15:25:53 and makes an immediate RC possible 15:25:53 david-lyle: anythign else we should wait on ? 15:25:58 no 15:26:07 that was the last thing 15:26:30 Should we clear the 4 bugs on https://launchpad.net/horizon/+milestone/kilo-rc1 ? 15:26:40 (if they happen to make it I'll catch them up anyway 15:26:42 ) 15:27:38 we can defer those, the medium would be the nicest to have, but it came lat 15:27:39 e 15:28:06 Horizon will require an RC-2 for finalized translations 15:28:08 david-lyle: we can always include it in a RC2 if that merges by then 15:28:14 sure 15:28:31 low risk change, and much better behavior 15:28:42 maybe make a quick check of the outstanding reviews, then approve open-liberty 15:28:53 sure will do 15:29:02 and I'l lpush the tag once that lands (hopefully later today) 15:29:19 Let me know when it's in the queue, I'll recheck it as needed 15:29:37 there's no horizon jobs in the gate 15:30:02 and I don't know of any critical issues, will double check though and approve the liberty patch 15:30:07 ack 15:45:29 ttx: https://review.openstack.org/#/c/171241/ is approved and making way through gate, the last two bugs in RC1 would be low risk and high gain RC2 possibilities 15:45:50 I don't have an RC2 milestone yet, so left them in RC1, moved the others to L-1 15:45:54 OK, we should probably tag them kilo-rc-potential then 15:46:03 that's how we tarck RC2 high gain stuff 15:46:08 Let me do that 15:46:22 both are 15:46:45 OK, I'll add them to my list so that I don't forget about them 15:46:53 apparently a lot of items are, I'll remove it from the others 15:47:17 yes, you can clean that list up a bit 15:50:59 morganfainberg: o/ 15:51:11 Yep 15:51:16 Here! :) 15:51:18 #topic Keystone 15:51:33 #info RC1 up since last Tuesday 15:51:41 #link https://bugs.launchpad.net/keystone/+bugs?field.tag=kilo-rc-potential 15:51:47 We have a couple critical fixes 15:52:33 I expect at most 1 more. 15:52:42 But that list looks accurate. 15:53:11 morganfainberg: do we have a security fix too ? Or is that in the libs ? 15:53:51 morganfainberg: we could open the RC2 window tomorrow, unless you prefer to wait for more testing ? 15:53:55 The security fix was still "OSSN or ossa" 15:54:02 Not sure what was decided. 15:54:09 I'll have a look 15:54:14 I think rc2 window would be good. 15:54:26 probably OSSN but since it discloses the other one we can't open it until later today 15:54:45 rigth, I'd like to finish up RC1s and unfreeze reqs first 15:54:54 but we can open one tomorrow and get the backports in 15:54:56 Whichever we go with that can be backported post release or in rc 15:55:06 ++ ok tomorrow rc2 works for me. 15:55:39 I'll ping you tomorrow aruond that time for that 15:55:56 Cool. 15:56:02 Thnx 15:56:04 In other news, sent the email about design summit space allocation last week 15:56:16 let me know if you have too much, or desperately need more. 15:56:20 We also might be moving keystonemiddleware under the normal release cycle. 15:56:30 kind of makes sense 15:56:50 I might want 1 more fishbowl. Will confirm with the team at the meeting today 15:57:00 But for the most part, I'm happy with the allocation. 15:57:07 I should auction that last one and be rich 15:57:11 The big win for us is the 2x working days. 15:57:27 s/days/sessions on Friday. 15:57:41 ack, we'll see how that goes 15:57:50 That is all . Talk to you tomorrow. 15:58:22 notmyname: ready when you are 15:58:27 here 15:58:32 #topic Swift 15:58:36 TONS going on!! 15:58:38 I think your patchseries landed 15:58:39 SO EXCITING 15:58:47 (also, not much sleep) 15:58:56 #link https://review.openstack.org/#/c/173398/ 15:59:04 #info EC merge to master happening right now 15:59:21 #info CVE-2015-1856 disclosed and patches pushed this morning 15:59:57 other patches queue for master will be pushed later today 16:00:25 they were pending because of the ec-related freeze on master 16:00:32 notmyname: ok, by your EOD before you fall asleep send me either a SHA or the url of the last patch 16:00:37 summary is that I expect to have a SHA later today 16:00:39 yes 16:01:04 I'll be around 5 hours from now due to meetings, we can check the status then 16:01:18 ok 16:01:22 If not ready yet I can tag first thing tomorrow morning instead 16:01:37 ok. I think the limiter will be the gate 16:01:56 notmyname: ack 16:02:35 On the design Summit side, you end up with 6 fishbowl and 10 work room sessions + full day meetup 16:03:00 I don't have more work rooms, except on Tuesday where they conflict with cross-project & ops stuff 16:03:20 I think we're good for now 16:03:33 honestly we haven't spend a lot of time on that part yet. all ec, all the time so far 16:03:40 fair enough 16:03:41 I expect to have more summit planning later this week 16:04:02 OK, I'll be in touch later today. Have a great busy day 16:04:08 I'm having a great busy day myself 16:04:12 :-) 16:04:14 good times 16:04:35 devananda: ready when you are 16:05:30 ttx: hi! 16:05:34 #topic Ironic 16:05:50 devananda: I don't think we have much to discuss given how recent your RC1 is 16:06:01 three things on my mind today 16:06:07 - translations 16:06:08 devananda: any red flag already ? I see https://bugs.launchpad.net/ironic/+bugs?field.tag=kilo-rc-potential is still empty 16:06:13 - client 16:06:21 - summit timing 16:06:46 what's up with translations? 16:06:53 nothing. just chekcing that that's ok :) 16:07:15 we're still under 20% for any non-english language 16:07:15 we'll do a last sync/ delete of the incomplete ones at RC2 stage 16:07:24 so likely to delete all 16:07:36 ok, sounds good. 16:07:50 what about client? 16:07:54 on the client, we had a very serious issue in the 0.5.0 release, which is still the current one on PIP 16:08:29 it refuses to connect with older servers, eventhough it's perfectly capable of doing so 16:08:32 How much extra stuff would a 0.5.1 happen to include if you tagged it now ? 16:08:44 should be just the fix for that issue... let me check 16:09:10 then it's fine to push it now. Alternative is to fix in a 0.6.0 and wait until stable/kilo is cut to issue a 0.5.1 16:09:30 If the only diff between 0.5.0 and 0.5.1 is the critical issue fix, no reason to delay imho 16:09:43 one other fix for cmdline arg parsing 16:09:47 so yes, it's just 2 bug fixes 16:09:54 i'll gladly push that today, then :) 16:10:05 If you think they are safe, please do 16:10:05 was holding off only because of the global library freeze 16:10:21 right, as you should :) We mostly want to prevent gratuitous changes 16:10:27 :) 16:10:34 so, lastly, summit planning 16:10:56 saw your email with our slot count, but not anything yet about slot timing 16:10:58 as long as you don't bump requirements the library point release should be fine 16:11:37 right, I can't really work on that until the slot allocation is final 16:11:48 which is why I sent it first to see comments 16:11:52 oh. looks like someone snuck in a change to the requirements line for hacking :-/ 16:11:55 -hacking>=0.9.2,<0.10 16:11:58 +hacking>=0.10.0,<0.11 16:12:23 since there are no comments so far , I started working on a strawman today 16:12:23 ah, test-requirements 16:12:59 I plan to post the proposed layout at the end of the week / early next week. Anything you need to know ASAP ? 16:13:05 ahh, I see. no worries then. 16:13:44 nope. I'm happy to tell folks they need to wait a little longer to find out 16:13:44 Ijn my strawman Ironic is mostly Thursday. 16:14:05 (and the meetup Friday morning) 16:14:19 (still highly subject to change at this point though) 16:14:21 friday morning? thought we had 2 slots == all day friday ? 16:14:28 oh, you do 16:14:39 :) 16:14:44 sorry misread my spreadsheet. Full day Friday 16:14:48 cool 16:15:35 devananda: ok, I'll be in touch later this week -- just let me know if somethign urgent surfaces 16:15:44 ttx: will do. cheers! 16:21:23 flaper87: all set @ https://launchpad.net/zaqar/+milestone/kilo-rc1 -- master on liberty now. Feel free to announce on ML 16:21:27 SlickNik: around? 16:21:40 ttx: o/ 16:21:43 ttx: danke, sir! 16:21:57 #topic Trove 16:22:05 #info Trove did its RC1 on Friday 16:22:12 #link https://bugs.launchpad.net/trove/+bugs?field.tag=kilo-rc-potential 16:22:18 One bug there, not fixed in master yet 16:22:28 Not sure how critical it is 16:22:48 So far there's one bug — not very critical for us. 16:23:01 SlickNik: feels like we can wait until the end of the week or the start of the next and see what we have then 16:23:15 So I'm not inclined to cut a new RC just for that. 16:23:24 ttx: sounds good. 16:23:29 We'll likely respin the RC with a translations and requirements refresh next week anyway, so let's wait for the moment 16:23:44 in the mean time if you find a bug just get it fixed on master ASAP 16:23:56 I'll be in touch end of week / early next week to see the status then 16:24:14 Okay, sounds good. 16:24:23 What else.. let me know if you have any issue with your space allocation as posted on the -dev ML last week 16:24:29 I'll drop you a note in case we find something as well. 16:24:35 I'll work on, the room layout this week 16:24:44 Took a look at that, and it looks good. 16:24:53 alright, that is all I had. Anything on your side ? 16:25:06 Working on session planning this week. 16:25:15 sounds good 16:25:29 That's all I had on my side as well. 16:25:42 Cool, ttyl! 16:25:48 #endmeeting