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