09:01:35 <ttx> #startmeeting ptl_sync
09:01:36 <openstack> Meeting started Tue Jul 15 09:01:35 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:01:37 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:37 <johnthetubaguy> ttx: sure
09:01:39 <openstack> The meeting name has been set to 'ptl_sync'
09:01:42 <ttx> #topic Nova
09:01:52 <ttx> #link https://launchpad.net/nova/+milestone/juno-2
09:02:24 <ttx> About 2 thirds of it is under review
09:02:37 <johnthetubaguy> yeah, lots needs code review I guess, which is good and bad :)
09:03:02 <johnthetubaguy> I guess we should start punting stuff to juno-3 soon
09:03:11 <ttx> server-count-api is marked Not started, sounds like a good candidate for punting
09:03:35 <ttx> johnthetubaguy: yes, punt early... and try to convert those that are 99% there
09:03:35 <johnthetubaguy> yeah, the slow and not-started should probably all get punted
09:03:58 <johnthetubaguy> yeah, how long do we have now its just over a week I guess?
09:04:29 <ttx> yeah, about one week left, +0..2 days
09:04:52 <ttx> but it's better to let that 0..2 handle unexpected gate delays
09:05:09 <ttx> so I'd expect anything not approved in one week to be deferred
09:05:17 <johnthetubaguy> right, good point
09:05:48 <ttx> #info Punt early, especially Not started / Slow progress
09:06:12 <ttx> #info Concentrate on those that are almost there, to increase completion rate
09:06:34 <johnthetubaguy> sounds good
09:06:41 <johnthetubaguy> thanks, will try sort that out
09:06:45 <ttx> johnthetubaguy, mikal: note that russellb will be handling the J2 tag -- please communicate with him next week
09:06:49 <johnthetubaguy> and will send a rallying call around reviews
09:07:07 <johnthetubaguy> ttx: ah, cool, thanks for the heads up
09:07:19 <ttx> He will probably skip the 1:1 usual times and just talk to you
09:07:37 <johnthetubaguy> yeah, I guess we need a more US friendly slot next week
09:07:53 <johnthetubaguy> I will try seek out mikal and chat to him about that
09:08:04 <ttx> #info spec backlog at 105
09:08:27 <ttx> johnthetubaguy: remind me when is your SPD/SAD ?
09:08:29 <johnthetubaguy> yeah, so in theory we should −2 all of those now
09:08:50 <johnthetubaguy> the date has passed, but I feel bad about the review backlog, so haven't really closed it off as such yet
09:09:02 <johnthetubaguy> we had a communication issue someone
09:09:22 <ttx> johnthetubaguy: right... trick is, until it's clearly closed, people will continue to spend time on them, which kind of defeats the purpose of those deadlines
09:09:37 <johnthetubaguy> lots of reviewers seemed to have thought the proposal freeze date was the merge freeze date, despite all emails saying the opposite
09:09:56 <johnthetubaguy> ttx: yeah, I have been trying to catch up with mikal but failing so far
09:10:41 <johnthetubaguy> really I want to understand what we are delaying, and go through that backlog, but not had chance since the freeze date, so there is an action on me too there
09:10:50 <ttx> ok
09:11:16 <ttx> Do you have anything for the cross-project meetign agenda later today?
09:11:26 <johnthetubaguy> in the nova meeting, there was push back on the freeze before we decide about J, and we decided to discuss that at the midcycle, so I kinda punted that
09:11:35 <johnthetubaguy> I don't think anything major has come up
09:11:52 <ttx> ok
09:12:02 <johnthetubaguy> I would like to get more discussion of blueprints we are doing for "consistency" there, like the tagging API, just for visibility
09:12:19 <johnthetubaguy> but not really chased down a list of those things, that might be the only one so far
09:12:29 <johnthetubaguy> the big elephant in the room is the API.NEXT work
09:12:37 <johnthetubaguy> we still haven't actually agreed on a plan
09:12:44 <ttx> johnthetubaguy: ok.. we should probably talk again before the end of the week, when the j2 list will have been... sanitized
09:12:49 <johnthetubaguy> mikal is trying to chase down some agreement
09:12:54 <johnthetubaguy> ttx: cool, sounds good
09:12:57 <johnthetubaguy> thats all from me really
09:13:04 <ttx> ack, talk to you later
09:13:09 <johnthetubaguy> thanks
11:45:44 <eglynn> ttx: ready when you are
11:45:47 <ttx> eglynn: o/
11:45:51 <ttx> #topic Ceilometer
11:46:13 <ttx> #link https://launchpad.net/ceilometer/+milestone/juno-2
11:46:29 <ttx> Still a long way to go in one week
11:46:45 <ttx> do you think all of those are still likely to make it?
11:46:52 <eglynn> yeah, I've actually got 3 more specs that look likely to land
11:47:02 <eglynn> VPNaaS: https://review.openstack.org/95781
11:47:04 <eglynn> FWaaS: https://review.openstack.org/95779
11:47:05 <eglynn> SNMP++: https://review.openstack.org/104113
11:47:19 <eglynn> VPNaaS and FWaaS patches should land
11:47:38 <eglynn> on SNMP, Lianhao isn't sure but is striving to get it in
11:47:41 <ttx> the code review has been going on in parallel ?
11:47:46 <eglynn> yep
11:48:04 <eglynn> the other question mark is on the grenade resource surviviability
11:48:25 <eglynn> the javelin2 stuff in tempest is looking like a non-solid basis for that
11:48:34 <ttx> hmm. I feel like we are not getting the clarity we expected from the specs process, if specs fly below radar and blueprints just appear on the final week
11:48:35 <eglynn> mtreinish characterizes it a WIP
11:49:12 <ttx> eglynn: do you think this late appearance is just due to spec backlog, or more a permanent feature of using -specs?
11:49:18 <eglynn> yeap, BTW the specs process is being "subverted" somewhat by folks just coding in parallel
11:49:40 <eglynn> I think it's partially due to the process still being bedded in
11:50:00 <eglynn> we will have to strictly prioritize reviewing efforts next time round
11:50:23 <eglynn> i.e. don't go off reviewing loads of code patches if there are pending reviews in the specs repo
11:50:46 <eglynn> ttx: are you seeing similar patterns on other projects?
11:50:46 <ttx> ok -- if that trends is also present in other projects we might have to have a discussion about that
11:50:55 <ttx> I'll see by the end of the day
11:50:58 <eglynn> OK
11:51:06 <ttx> Nova and Neutron kind of avoid that with the specs freezes
11:51:44 <ttx> eglynn: so you may have 3 more specs appearing on that page
11:51:46 <eglynn> yeah, for ceilo I feel that'll have to be more a specs slush this time round
11:51:58 <eglynn> yes, two at the very least, most likely 3
11:52:10 <ttx> and you think everything can make it in one week?
11:52:19 <ttx> the 5 already there + 3
11:52:33 <ttx> or are you likely to defer some of those 5?
11:52:51 <eglynn> everything should land I think except possibly SNMP++ and grenade
11:53:01 <eglynn> grenade is the first one I'll bump
11:53:13 <eglynn> probably by EoD tmrw
11:53:25 <ttx> ok
11:53:34 <eglynn> other big concern on my radar is this test timeout that I mentioned before ... https://bugs.launchpad.net/bugs/1336193
11:53:52 <eglynn> sileht is not yet back, so I've asked nsaje to look at it
11:54:13 <eglynn> (nsaje just started as a short-term contractor with Red Hat)
11:54:25 <ttx> You also have https://bugs.launchpad.net/bugs/1327076 targeted, with no assignee
11:54:29 <eglynn> Nejc has a definite line of inquiry on the oslo-messaging side
11:54:34 <ttx> is anyone working on that?
11:55:03 <eglynn> meant to assign that to myself
11:55:07 <eglynn> done so now
11:55:32 <ttx> #info 3 more blueprints expected to appear on the j2 plans as their specs get approved (code been developed in parallel)
11:55:34 <ttx> eglynn: in other news, note that russellb will be doing the tag next week
11:56:19 <eglynn> and in other other news, I'll be taking some half days off next week for family reasons
11:56:34 <ttx> #info Spec backlog: 27
11:56:36 <eglynn> but will be contactable and making all my scheduled meetings
11:57:16 <ttx> ok
11:57:36 <ttx> there won't be 1:1s next week, at least not at usual times, and without me
11:57:48 <eglynn> ttx: so same process as j1, declare to russellb when ready to tag?
11:57:52 <russellb> we just need to sync on when you think j2 is ready
11:57:54 <russellb> yep :)
11:58:00 <eglynn> russellb: cool :)
11:58:10 <ttx> eglynn: yes, he will probably chase you down to make sure the blueprints are aligned
11:58:25 * eglynn prepares to be chased ... ;)
11:58:45 <russellb> gold stars awarded if no chasing required
11:58:45 <ttx> eglynn: anything you wanted to add to project meeting agenda for today?
11:59:00 <ttx> russellb: o/
11:59:08 <eglynn> ttx: nope that's all from me
11:59:11 <russellb> \o
11:59:20 <ttx> eglynn: cool, thx!
11:59:25 <eglynn> laters :)
11:59:26 <ttx> SergeyLukjanov: around?
12:01:33 <ttx> dhellmann: if you're already available, you can steal Sergey's slot
12:02:09 <dhellmann> ttx: here
12:02:20 <ttx> ok, let's do this
12:02:21 <ttx> #topic Oslo
12:02:36 <ttx> https://launchpad.net/oslo/+milestone/juno-2
12:02:58 <dhellmann> you might want to hit reload, I've been updating bps this morning
12:03:12 <ttx> dhellmann: I no longer look in advance :)
12:03:16 <dhellmann> heh
12:03:28 <ttx> this looks good
12:03:41 <ttx> The last 3 are still likely to land ?
12:04:12 <dhellmann> we have a few reviews for oslo.utils, so it might be tight but none of that work is really big
12:04:38 <dhellmann> the infra team is in germany at their sprint, so I don't know about the test job changes, that might have to wait for after j2
12:05:00 <ttx> Anything j2-worthy flying below radar, like a specs almost there with code reviewed in parallel?
12:05:02 <dhellmann> I think the configfilter wrapper is actually done, but I want to check with markmc before closing that one
12:06:03 <ttx> https://launchpad.net/oslo.messaging/+milestone/juno-2 doesn't have blueprints in it anymore
12:06:11 <dhellmann> odd
12:06:34 <ttx> 2 in j3
12:06:46 <dhellmann> those are new approvals
12:06:51 <dhellmann> I wonder what happened to the others in j2
12:07:35 <ttx> dhellmann: russellb will push the tag for oslo-incubator and mark the milestone "released" for oslo.messaging next week, so he wil be your point of contact that week
12:07:45 <dhellmann> ok
12:07:53 <ttx> russellb: fwiw I usually do oslo when everything else is out of the way
12:08:05 <ttx> since it's not really blocking the j2 announcements
12:08:08 <russellb> dhellmann: o/
12:08:13 <russellb> ttx: makes sense
12:08:16 <dhellmann> russellb: o/
12:08:37 <ttx> dhellmann: the release scripts now should know how to handle oslo, so it will be a lot less manual
12:08:56 <dhellmann> cool
12:09:39 <ttx> and thanks for tagging that rootwrap alpha
12:10:07 <dhellmann> no trouble at all
12:10:15 <dhellmann> I need to automate the email step from that process :-)
12:10:31 <ttx> #info spec backlog: 10
12:10:37 <dhellmann> maybe I could write a script for infra to do it
12:10:48 <dhellmann> I can't find those missing oslo.messaging blueprints :-/
12:11:06 <ttx> dhellmann: yeah, we need to work on streamlining library announcements
12:11:26 <ttx> have a clear source to find them
12:11:37 <dhellmann> I'll bring it up at the meeting this week and see if anyone wants to take that on
12:12:00 <dhellmann> a clear source to find the release notices, or the libraries?
12:12:04 <ttx> dhellmann: it's not just oslo, client libs should follow it as well
12:12:10 <ttx> release notices
12:12:21 <ttx> dhellmann: only trick is.. raw git changelog really fails to highlight stuff
12:12:28 <dhellmann> yeah, the client library announcements should go to python-announce, too
12:12:30 <SergeyLukjanov> ttx, I'm sorry, /me been on internal meeting, now ready
12:12:33 <dhellmann> yeah, true
12:13:16 <ttx> dhellmann: I've been thinking about it from a Storyboard perspective. and the role of Launchpad in building "release pages"
12:13:38 <dhellmann> looking at the open specs, I really only anticipate the oslo.cache work and service-status-interface to have a high likelihood of seeing any real work this cycle
12:13:43 <ttx> We can replicate that "feature" in Storyboard, but it's a bit out of the pure "task tracking" function
12:14:24 <ttx> we could use smarter commit messages and leverage git changelog to build a list of features and bugs
12:14:31 <ttx> and security fixes
12:14:57 <dhellmann> yeah, it seems like we will have the information available between git, specs, and blueprints, but we have to tie it all together
12:15:01 <ttx> but not sure everyone would follow the rules
12:15:27 <dhellmann> a couple of jobs back we had a special field in the bug tracker for "release note" that could be updated after the ticket was closed so the doc team could generate notes automatically
12:15:36 <ttx> so if we can build something good for oslo libraries, we are likely to reuse that for releases and milestones
12:15:42 <russellb> if there's enough obvious benefit to the rules (awesome auto release summary) then that would provide motivation
12:16:15 <ttx> russellb: it's just that in LP, the milestone field actually has two purposes
12:16:17 <dhellmann> maybe a field like that in storyboard would work, and the person doing the release could update it before generating the release?
12:16:26 <ttx> it's when you want to deliver it, then it's when you did deliver it
12:16:36 * russellb nods
12:16:46 <ttx> and we have plenty of scripts to try to gover for that slight gap in meaning
12:16:49 <ttx> cover*
12:17:14 <ttx> the ultimate source of what's IN the release is really the git thing, not what LP or Storyboard thinks is in there
12:17:37 <dhellmann> won't storyboard have the git commit ids?
12:18:08 <ttx> dhellmann: it will probably have some, but just like LP it will miss some work
12:18:17 <ttx> that just landed without ref
12:18:23 <ttx> anyway, separate discussion
12:18:31 <dhellmann> oh, I thought we were going to add items to storyboard automatically
12:18:39 <dhellmann> maybe that was nixed
12:19:08 <ttx> dhellmann: no, it's still a possibility... but that also requires people to ref a storyboard ID in the commit message
12:19:20 <dhellmann> ah, true
12:19:29 <ttx> so if you add rules to commit messages...
12:19:57 <ttx> anyway, offtopic
12:20:04 <dhellmann> yeah, sorry :-)
12:20:10 <ttx> dhellmann: anything you wanted to add to meeting agenda for today?
12:20:21 <dhellmann> not today
12:20:26 <ttx> SergeyLukjanov: still around?
12:20:29 <ttx> dhellmann: ok, ttyl
12:20:31 <SergeyLukjanov> ttx, yup
12:20:38 <ttx> #topic Sahara
12:20:43 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/juno-2
12:20:57 <ttx> Looks pretty good
12:21:00 <SergeyLukjanov> so, everything looks good
12:21:14 <ttx> At this point, it's good if targeted bugs have assignees
12:21:43 <SergeyLukjanov> ttx, ok, I'll ask folks to grab the issues
12:21:50 <SergeyLukjanov> ttx, there is some good progress on merging sahara-dashboard to horizon
12:21:57 <SergeyLukjanov> ttx, only 4 changes left
12:21:57 <ttx> SergeyLukjanov: is that blueprint list complete, or do you have things to add there ?
12:22:10 <ttx> SergeyLukjanov: how many were there originally?
12:22:21 <SergeyLukjanov> ttx, it depends on specs review, probable +1-2
12:22:52 <SergeyLukjanov> ttx, and I
12:23:08 <SergeyLukjanov> ttx, and I'll check that we're not missed some already done work
12:23:18 <ttx> ok, good
12:23:39 <ttx> So you have code that has been developed in parallel with specs and is rady for review as soon as the spec is approved?
12:24:03 <SergeyLukjanov> ttx, yup, we have several such specs
12:24:09 <ttx> ok
12:24:17 <ttx> SergeyLukjanov: russellb will be handling the tag next week
12:24:26 <SergeyLukjanov> ttx, ack
12:24:28 <ttx> there won't be formal 1:1s at the usual times
12:24:56 <ttx> #info spec backlog: 4
12:25:24 <ttx> #info maybe one or two blueprints will be added in j2
12:25:25 <russellb> SergeyLukjanov: so let's just stay in touch, and just let me know when you feel j2 is ready to go
12:25:50 <SergeyLukjanov> russellb, okay, I think it'll be July 22-24
12:25:53 <ttx> and russellb will chase you down if it appears you are missing the launch window
12:26:25 <SergeyLukjanov> russellb, for sahara we're usually ready in -1..-2 days before the dev milestone
12:26:32 <russellb> perfect
12:26:40 <russellb> that's when i'll start looking at projects and tagging when ready
12:27:13 <ttx> russellb: so yeah, most of the job is to maximize the chances that everything happens in the same time window, be aligning the milestone page content with what is still likely to make it in time
12:27:41 <ttx> by*
12:28:21 <ttx> if you just check on Tuesday you get a very long list and it's hard to cut. By removing things that have no chance of making it, you actually increase the chances that the rest will make it
12:28:43 <SergeyLukjanov> ttx, I'd like to add just reminder for today's meeting re merging -dashboard to horizon
12:28:51 <SergeyLukjanov> ttx, nothing specific to discuss
12:28:54 <ttx> but it's hard, because nobody really knows what will make it or miss
12:29:14 <ttx> SergeyLukjanov: ok
12:29:19 <SergeyLukjanov> ttx, thx
12:29:41 <SergeyLukjanov> ttx, I'm usually moving all < High to the next milestone on Tue
12:30:22 <ttx> SergeyLukjanov: good :)
12:30:45 <ttx> SergeyLukjanov: that's all I had, thanks!
12:30:52 <SergeyLukjanov> ttx, thank you
13:04:15 <jgriffith> ttx: lemme know if you have time to go early
13:04:23 <ttx> jgriffith: I do
13:04:30 <ttx> #topic Cinder
13:04:50 <ttx> https://launchpad.net/cinder/+milestone/juno-2
13:05:06 <jgriffith> sweet
13:05:27 <ttx> jgriffith: I suspect a few of those definitely won't make it in one week
13:05:42 <jgriffith> ttx: Nope, probably not
13:05:43 <ttx> jgriffith: so defer as soon as you're relatively sure they won't make it
13:05:50 <jgriffith> ttx: will do
13:06:04 <ttx> on the other hand, is theer anything that might get added at the last minute?
13:06:08 <jgriffith> ttx: I don't plan on adding anything that doesn't have a review ready/complete at this point
13:06:39 <ttx> jgriffith: but nothing comes to mind?
13:06:45 <jgriffith> There is likely to be a few specs pop up, but they're J3 or untargetted until I have completed code
13:06:48 <jgriffith> ummm....
13:06:58 <ttx> #info Spec backlog: 28
13:07:01 <jgriffith> ttx: well, boat load of drivers
13:07:30 <ttx> ok
13:07:31 <jgriffith> ttx: problem is I don't see anybody with anything "close"
13:07:53 <ttx> jgriffith: keep on refining. russellb will be your host for J2 tagging
13:08:04 <jgriffith> ttx: k
13:08:08 <jgriffith> lucky russellb
13:08:09 <jgriffith> :)
13:08:21 <russellb> :)
13:08:51 <ttx> jgriffith: did you have anything for the meeting today?
13:08:59 <jgriffith> russellb: that was only two... you don't appear until three
13:09:02 <jgriffith> ttx: nope
13:09:11 <jgriffith> ttx: just need to get these features buttoned up
13:09:31 <ttx> jgriffith: we'll skip 1:1s next week, since I won't be arond
13:09:33 <ttx> +u
13:09:40 <russellb> jgriffith: i'll be in touch early next week to identify when j2 is ready
13:09:42 <jgriffith> ttx: yeah... see ya in Portland
13:09:59 <ttx> ah cool, see you there!
13:10:07 <jgriffith> russellb: I'll be on and off IRC but I'll be sure to synch up with you
13:10:19 <russellb> jgriffith: perfect.  feel free to drop an email if that's easier for you
13:10:28 <jgriffith> russellb: sounds good
13:10:30 <ttx> russellb: i can physically push him to connect if needed
13:10:33 <russellb> jgriffith: you've been through this several times, so i know you know the drill :)
13:10:38 <russellb> ttx: wooo
13:10:39 <jgriffith> ttx: haha!!  Literally even
13:11:10 <jgriffith> russellb: should be smooth, just getting everything through
13:11:17 <russellb> sounds good
13:11:53 <ttx> jgriffith: ok, ttyl!
13:12:19 <jgriffith> ttx: cya.. thanks
13:12:26 <russellb> cya!
13:12:43 <ttx> russellb: the autokick script dramatically reduced the need for those 1:1s
13:13:07 <ttx> although I guess talking once a week with people can't hurt
13:13:25 <russellb> ttx: yep, i think it's good to make sure these things stay top of mind week to week
14:15:38 <ttx> dolphm: around?
14:15:41 <dolphm> ttx: o/
14:15:45 <ttx> #topic Keystone
14:16:00 <ttx> https://launchpad.net/keystone/+milestone/juno-2
14:16:06 <ttx> Looks reasonable
14:16:41 <ttx> dolphm: any possible last-minute addition, fresh from -specs approval?
14:17:33 <dolphm> we did approve ~5 specs last week at our hackathon - i don't *think* any of them will be implemented in j2 though
14:17:38 <ttx> #info spec backlog: 18
14:17:42 <ttx> ok
14:17:55 <ttx> dolphm: russellb will handle J2 tagging
14:18:10 <ttx> and we'll skip the usual 1:1s next week
14:18:26 <russellb> i'll be in touch next week to confirm when J2 is ready
14:18:32 <russellb> feel free to ping me anytime to discuss
14:19:02 <dolphm> json-home is a spec we approved last week & has an implementation available - if it's close to being ready, that one would be an easy j2 target
14:19:08 <dolphm> but that looks like the only one
14:19:14 <dolphm> ttx: russellb: tagging sounds good
14:19:34 <ttx> dolphm: any agenda addition for the meeting today?
14:19:55 <dolphm> ttx: a quick announcement regarding keystoneclient.middleware.auth_token -> keystonemiddleware.auth_token
14:20:14 <dolphm> let me do an #info here..
14:20:48 <ttx> yes, #info it and feel free to insist on it when we go over the 1:1s notes at the meeting
14:21:11 <dolphm> #info keystoneclient.middleware.auth_token has been split into a new package, keystonemiddleware.auth_token - we'll need to update every project's default pipeline to adopt the new middleware
14:21:45 <ttx> dolphm: you could use a bug number to track all corresponding tasks
14:21:58 <dolphm> #info keystoneclient.middleware.auth_token will continue to receive security updates
14:22:04 <ttx> that will facilitate making sure all bases are covered
14:22:25 <dolphm> morganfainberg: do we have a bug number to track the above change? ^
14:22:56 <ttx> dolphm: ok, that's all I had
14:23:27 <dolphm> me too - i'll make sure there's a bug if not
14:24:19 <ttx> dolphm: ok, ttyl
14:25:07 <dolphm> o/
14:30:56 <russellb> dolphm: doing something to enable backwards compat for that change?
14:31:20 <dolphm> russellb: yes, we're leaving keystoneclient.middlware.auth_token alone :)
14:31:33 <ttx> david-lyle: o/
14:31:35 <dolphm> russellb: we can't import from keystonemiddleware.auth_token because that would create a circular dep
14:31:38 <russellb> dolphm: cool.  could eventually make it a trivial import of the new thing.
14:31:39 <david-lyle> ttx: o/
14:31:41 <russellb> dolphm: ah.
14:31:49 * russellb shuts up to clear the room for david-lyle's time
14:31:56 <ttx> #topic Horizon
14:32:08 <ttx> https://launchpad.net/horizon/+milestone/juno-2
14:32:14 <ttx> 37 blueprints left
14:32:38 <ttx> Lots of them in review
14:32:48 <david-lyle> almost all are up for review
14:33:02 <david-lyle> someone added another after I cleaned up yesterday
14:33:09 <david-lyle> I'll boot that
14:33:45 <ttx> david-lyle: i would suggest focusing on those that are almost there, to maximize the number of completed blueprints
14:34:16 <ttx> also merging early is a good idea as I expect the load on gate to ramp up pretty soon
14:34:19 <david-lyle> we have been, the Sahara one has been the top priority and eating up a lot of review bandwidth
14:34:30 <david-lyle> a lot
14:34:34 <ttx> david-lyle: yes, Sergey was mentioning good progress on that front
14:34:57 <david-lyle> we have several more of the Sahara patches that are very close
14:35:02 <ttx> also don't hesitate to defer stuff that's unlikely to make it, that can help in prioritizing as well
14:35:28 <SergeyLukjanov> david-lyle, thank you for bumping the sahara reviews prio!
14:35:29 <ttx> yes, https://blueprints.launchpad.net/horizon/+spec/mac-learning-knobs was just added
14:35:43 <ttx> russellb: Nb: Horizon is not using autokick.py yet
14:35:44 <david-lyle> sure, I did some paring yesterday and will get more status in the Horizon team meeting
14:35:51 <russellb> ttx: why not?
14:35:57 <ttx> russellb: so it is vulnerable to random additions by bystanders
14:36:05 <ttx> russellb: it's not using -specs
14:36:15 <russellb> ah
14:36:18 <ttx> russellb: so the blueprint is still the correct way to propose a feature
14:36:23 <russellb> and actually i think i missed what autokick.py was ...
14:36:50 <ttx> russellb: it's a script I have running (in the cloud!) that removes milestone targts for blueprints without a priority
14:37:02 <russellb> ttx: ah, cool.
14:37:16 <ttx> so that we can use the priority field to also mean "approved"
14:37:20 <russellb> ttx: and that includes also checking for an approved spec or something?
14:37:25 <david-lyle> now I want to move to a specs repo just for that
14:37:26 <ttx> since it's one of the very few LP restricts
14:37:33 <russellb> or just that projects with specs repos have less people doing random LP edits
14:37:58 <ttx> russellb: no, random people just can't set the priority field. So when a spec is approved, you set priority and target milestone
14:38:16 <ttx> if random people just set target milestone, the script will boot them off
14:38:29 <russellb> gotcha
14:38:35 <ttx> (it's a workaround the fact that LP just lets anyone set the target milestone)
14:38:39 <russellb> but people could do that for a specs using project too presumably ..
14:39:04 <ttx> russellb: they could, but then there is no way for people to "propose" a feature
14:39:31 <ttx> the workflow for proposing features is to file a blueprint and set the target milestone. Then the PTL just triages all the undefined-priority BPs
14:39:39 <russellb> right
14:39:49 <ttx> russellb: pretty sure you remember how much that is
14:39:54 <russellb> yes.
14:39:58 <ttx> how much fun that is, I mean
14:40:08 <russellb> oh yes.
14:40:19 <russellb> david-lyle: so the reason i'm around today is that i'm handling the J2 tag next week
14:40:37 <david-lyle> russellb: excellent
14:40:38 <russellb> david-lyle: so we'll need to stay in touch early next week to confirm when your J2 is ready to go
14:40:49 <david-lyle> sounds good
14:40:54 <ttx> david-lyle: so yes, keep on refining the list
14:41:13 <david-lyle> will do
14:41:26 <ttx> david-lyle: any specific topic you wanted to discuss at meeting today?
14:41:42 <david-lyle> ttx: no, I think we're set
14:41:51 <ttx> david-lyle: ok, back to reviewing then :)
14:42:02 <ttx> that's a pretty impressive list of BPs
14:42:05 <david-lyle> ttx: it's an honest living
14:42:12 <david-lyle> reviewing all day
14:42:21 <ttx> mestery: ready when you are
14:42:34 <mestery> ttx: o/
14:43:13 <ttx> #topic Neutron
14:43:22 <ttx> https://launchpad.net/neutron/+milestone/juno-2
14:43:48 <mestery> I spent yesterday and this morning pruning this list a bit.
14:43:54 <ttx> a bit late, but not completely crazy
14:43:58 <mestery> We have a LOT of things in flight at the moment.
14:44:03 <mestery> ttx: ++
14:44:04 <ttx> there are two "unknown" in there
14:44:22 <mestery> Yes, I need to move one out to J3 and the other one I need to talk to the committer
14:44:28 <mestery> Expect those to be resolved within the hour
14:45:20 <ttx> mestery: ok, just keep on refining, and merge those taht are nearly complete as soon as possible...
14:45:38 <mestery> ttx: Yes sir, that's the plan, been working with the other cores on that this week.
14:46:02 <ttx> mestery: as previously said, russellb will handle j2 tagging next week
14:46:16 <mestery> OK, cool!
14:46:34 <mestery> Will keep in contact with you over the next week russellb.
14:46:39 <russellb> mestery: great
14:46:46 <ttx> mestery: how is the SPD deadline working for you ?
14:47:03 <mestery> ttx: SPD worked quite well, SAD also is going ok.
14:47:12 <mestery> I've spent hours pouring over specs, moving some to K, etc.
14:47:15 <ttx> oh, you're past SAD now?
14:47:24 * ttx checks
14:47:27 <mestery> SAD is this weekend, almost quite literally
14:47:29 <mestery> 7-20
14:47:33 <ttx> ah ok
14:47:40 <mestery> But, I'm premptively working to close out things before that.
14:47:44 <mestery> And narrowing thigns down.
14:48:02 <mestery> Overall, I've been happy with SPD/SAD, and would recommend it to other projects that are looking at the same sort of thing.
14:48:19 <ttx> mestery: when do you plan to reopen specs for K? after feature freeze ? or at RC1 ?
14:48:46 <mestery> ttx: I think closer to RC1 to try to focus people on J3 issues and bugs near the end of J.
14:49:37 <ttx> mestery: do you still expect some late approvals to sneak into j2, or that would be definitely j3 material ?
14:49:55 <mestery> ttx: I don't expect anything else to be added to J2.
14:49:59 <mestery> It's all J3 from here on out.
14:50:04 <ttx> #info no addition expected to j2
14:50:37 <ttx> #info spec backlog: 140
14:51:20 <ttx> mestery: so we won't have our usual 1:1 discussion next week
14:51:27 <mestery> ttx: Got it, have fun at OSCON!
14:51:33 <ttx> will try!
14:51:57 <ttx> mestery: anything to add to meeting agenda for today?
14:52:21 <mestery> ttx: Not much, if you want, I could talk about SPD/SAD since there weren't many projects which did this to my knowledge.
14:52:25 <mestery> Other than that, I'm good.
14:52:52 <ttx> mestery: I already added a topic to discuss if specs is increasing or decreasing the predictability of features
14:53:02 <mestery> ttx: perfect
14:53:06 <ttx> and SPD/SAD definitely helps in that area, so on topic :)
14:53:13 <mestery> :)
14:53:22 <ttx> mestery: ok, talk to you then
14:53:26 <mestery> ttx: later!
15:05:46 <notmyname> ttx: ready whenever you are
15:23:00 <ttx> notmyname: on a call, will ping you as soon as I'm out of it
15:23:22 <notmyname> ok
15:27:18 <ttx> notmyname: readynow
15:27:30 <notmyname> ttx: good morning
15:27:32 <ttx> #topic Swift
15:27:58 <notmyname> ttx: I think all I've got is the gap analysis
15:28:04 <notmyname> for the TC
15:28:09 <ttx> notmyname: good reception for Swift 2.0.0 so far?
15:28:54 <notmyname> ttx: yes, I think so. several articles written. even had a new deployer come to us (swiftstack) with a specific use case for storage policies
15:29:42 <ttx> notmyname: we'll likely have that gap analysis on July 29 or August 5, unless the meeting is not cancelled next week
15:29:52 * notmyname checks calendar
15:30:02 <ttx> but I expect OSCON will make us cancel it
15:30:19 <ttx> We'll see better when we discuss it today
15:30:44 <notmyname> ttx: the 29th I have an on-site customer meeting. unlikely to be available by meeting time (1pm pacific). the 5th I'm free
15:31:05 <notmyname> also, next week is good for me too, if the meeting happens
15:31:26 <ttx> Sounds good to me -- on Jul 29 we need to go through progress on the existing gap coverage plans anyway
15:31:30 <ttx> (post-j2)
15:31:52 <ttx> notmyname: so next week if that's happening, or August 5th
15:32:00 <notmyname> correct
15:32:27 <notmyname> I took the doc you sent me an filled out short answers (mostly "done" or "N/A")
15:33:07 <ttx> notmyname: ack
15:33:31 <notmyname> should I send my draft to you first to review? would that help anything go smoother in the meeting?
15:33:42 <ttx> notmyname: do you think you'll have one or two more juno releases ?
15:34:03 <ttx> notmyname: we can post the link to the etherpad in advance of that TC meeting
15:34:12 <notmyname> ok
15:34:30 <ttx> notmyname: discussion usually quickly focuses on a few key points
15:34:32 <notmyname> does juno RC start in september or october?
15:34:42 <ttx> notmyname: the etherpad lets us go fast on obvious stuff
15:34:52 <ttx> Final release October 16
15:35:22 <ttx> RCs start last week of Sept
15:36:09 <ttx> so an intermediary release would be ~ end of August
15:36:20 <notmyname> ok, I'll shoot for 2 releases then...ya, exactly that :-)
15:36:36 <notmyname> ie in about a month, and then another right at the RC
15:36:37 <ttx> ok
15:36:43 <notmyname> https://etherpad.openstack.org/p/swift_gap_analysis
15:37:35 <ttx> notmyname: ack
15:37:41 <ttx> notmyname: that's all I had
15:37:50 <ttx> anything you want to talk about at meeting today?
15:38:23 <notmyname> great. me too. if you look over the etherpad, you'll see that there is one section with ??? as the answer
15:38:36 <notmyname> * The lifecycle of resources managed by the project should be externalized
15:38:36 <notmyname> via notifications so that they can be consumed by other integrated
15:38:36 <notmyname> projects
15:38:42 <notmyname> I don't know what that means
15:38:55 <notmyname> (no I don't have anything to bring up in the meeting)
15:40:35 <ttx> it might be a n/a in your case
15:40:56 <ttx> I think what it's calling for is integration with ceilometer
15:41:26 <ttx> but you'll be able to raise it at that meeting
15:41:33 <notmyname> ok. that was covered in another question ("done"), but it almost sounds like some sort of queue/message bus/notification system
15:41:34 <ttx> ok, that's all I had
15:43:06 <notmyname> me too
15:43:24 <ttx> #info current plan is to shoot for another release before the final synced one, rough eta end of August
15:43:37 <ttx> notmyname: thanks!
15:43:48 <ttx> zaneb: ready when you are
15:43:55 <zaneb> hey
15:44:07 <ttx> #topic Heat
15:44:14 <ttx> https://launchpad.net/heat/+milestone/juno-2
15:45:18 <ttx> zaneb: is that current ? makes it look like the bottleneck is development and not review in heat
15:45:51 <ttx> (other projects have much more "needs code review" at this stage
15:45:53 <ttx> )
15:45:54 <zaneb> the bottleneck is that everyone is too busy reviewing to develop :D
15:46:25 <zaneb> I just changed the status on Randall's bp to 'needs code review'
15:46:31 <ttx> zaneb: ok -- are all those still likely to get completed this week? Or is it time for early deferrals ?
15:47:18 <zaneb> mine probably should be deferred
15:47:32 <ttx> zaneb: any last minute surprise likely to be added, or is that plan final?
15:47:40 <ttx> #info spec backlog: 17
15:48:06 <zaneb> I can't imagine any additions at this stage
15:48:20 <ttx> #info no last minute addition expected to j2
15:48:47 <ttx> you ahve a number of unassigned bugs on the j2 target. I fear that if they are not assigned very soon, they will likely miss
15:49:06 <ttx> so maybe use the next Heat meeting to get them assigned or deferred
15:49:36 <ttx> zaneb: note that russellb will be handling next week juno-2 tagging
15:49:47 <russellb> zaneb: o/
15:49:57 <zaneb> russellb: \o
15:50:25 <russellb> zaneb: so, i'll be in touch next week to confirm when you're ready to go with j2
15:50:35 <ttx> so when you're happy with a tag, communicate that to him. And he will be the one chasing you down so that you fall in the launch window
15:50:42 <zaneb> russellb: ok, cool
15:51:03 <zaneb> I will follow up on the unassigned high priority bugs
15:51:09 <ttx> zaneb: any topic you want to discuss at the cross-project meeting later ?
15:51:11 <zaneb> and make sure someone is on them
15:51:25 <zaneb> ttx: nope
15:51:43 <ttx> ok then, talk to you later!
15:51:57 <zaneb> thanks, see you later!
16:09:20 <ttx> SlickNik: o/
16:10:21 <SlickNik> Hey ttx
16:10:24 <ttx> #topic Trove
16:10:32 <ttx> #link https://launchpad.net/trove/+milestone/juno-2
16:10:40 <ttx> markwash: missed your turn :)
16:11:01 <ttx> SlickNik: status looks good, although one week from juno-2 you can probably start to defer things
16:11:08 <markwash> brb
16:11:24 <SlickNik> ttx: Lots of BPs in review. Trying to get those done and implemented.
16:11:50 <ttx> SlickNik: try to push those that are 99% there in priority. that will maximize the number of them you get "implemented"
16:12:02 <ttx> will also help with gate load next week
16:12:28 <ttx> talkign abot next week, russellb will be handling the juno-2 milestone release process, so he will be your point of contact
16:12:30 <SlickNik> ttx: Yes. Also, I need to defer some of the unstarted bugs to juno-3.
16:12:38 <SlickNik> ttx: will do that today.
16:12:48 <russellb> SlickNik: o/
16:12:55 <ttx> goal is still to tag sometimes between Tuesday and Thursday
16:12:57 <russellb> i'll be in touch next week to confirm when juno-2 is wrapped up
16:13:17 <SlickNik> Awesome, thanks for the help with the tagging russellb
16:13:22 <russellb> yep np
16:13:51 <russellb> as long as things get deferred, my job is super easy :)
16:14:02 <russellb> completed or deferred, rather
16:14:10 <ttx> SlickNik: that's allk I had -- any topic for the meeting today ?
16:15:03 <SlickNik> ttx: nope, that's all I had as well. Just chugging along towards juno-2. :)
16:15:17 <ttx> yay, that's the spirit
16:15:22 <ttx> markwash: ready?
16:15:43 <markwash> ttx: yup!
16:15:44 <SlickNik> ttx: Thanks. see you in a bit!
16:15:46 <ttx> #topic Glance
16:16:05 <ttx> #link https://launchpad.net/glance/+milestone/juno-2
16:16:18 <ttx> Looks a bit... late
16:16:45 <markwash> yes it does
16:16:55 <ttx> Still think they can all make it ?
16:17:08 <markwash> we can probably land gpfs and bump the other two
16:17:29 <ttx> markwash: well, better have 1 done than try to land the 3 and get nothing
16:17:51 <ttx> so feel free to defer early
16:18:03 <markwash> sounds about right
16:18:09 <ttx> #info spec backlog: 12
16:18:39 <ttx> anything is there likely to make a surprise last-minute rush to j2 ?
16:18:45 <ttx> in*
16:19:13 <markwash> no I don't think so
16:19:35 <ttx> markwash: ok. Note that russellb will be your host for j2 tagging next week
16:19:40 <russellb> markwash: o/
16:19:51 <markwash> cool
16:19:55 <ttx> so he will be the one chasing you down and deferring all your missed blueprints
16:19:56 <markwash> hmm
16:20:11 <markwash> we'll be aiming to tag on tuesday?
16:20:17 <markwash> or thursday?
16:20:38 * ttx steps back and lets russellb answer
16:20:45 <markwash> glance mini summit is thursday and friday
16:20:45 <russellb> the earlier the better
16:20:52 <russellb> if you can be ready tuesday, that'd be great
16:21:00 <markwash> I'll aim for that
16:21:03 <russellb> perfect
16:21:26 <ttx> markwash: ok, anything to add to the meeting agenda ?
16:21:35 <markwash> nothing from me
16:21:39 <ttx> markwash: we'll skip the 1:1s next week, btw
16:21:46 <ttx> SlickNik: ^ same
16:21:49 <markwash> okay
16:22:04 <SlickNik> ttx: got it
16:22:09 <ttx> notmyname: ^ same
16:22:17 * ttx realizes he missed a few notifications
16:22:18 <notmyname> ack
16:22:36 <ttx> markwash: that's all I had
16:22:45 <markwash> ttx: thanks! sorry I was late
16:23:00 <ttx> markwash: no problem, SlickNik was early ;)
16:23:16 <ttx> that concludes the syncs for today, thanks everyone
16:23:19 <ttx> #endmeeting