21:01:08 <ttx> #startmeeting project
21:01:09 <openstack> Meeting started Tue Jun 25 21:01:08 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:11 <mordred> o/
21:01:13 <openstack> The meeting name has been set to 'project'
21:01:19 <ttx> #link http://wiki.openstack.org/Meetings/ProjectMeeting
21:01:31 <ttx> 3 weeks left to H2. Most work should now be started, and a good half should be merged or under review already
21:01:41 <ttx> We'll spend a bit extra time on Swift (1.9.0) and Neutron (renaming plan).
21:01:52 <ttx> and Swift will go right after the general stuff
21:01:55 <notmyname> thanks
21:01:58 <ttx> #topic General stuff
21:02:17 <ttx> Nothing on my side
21:02:21 <ttx> sdague, annegentle, jeblair/mordred: news from QA/Docs/Infra teams ?
21:02:29 <jeblair> yes
21:02:31 <ttx> soon-to-be-programs ?
21:02:34 <annegentle> #link http://lists.openstack.org/pipermail/openstack-docs/2013-June/002014.html
21:02:43 <ttx> shoot
21:03:00 <jeblair> we're planning on doing the quantum->neutron rename on saturday july 6 at 1600utc
21:03:01 <annegentle> that's the latest from doc land -- Shaun McCance started as a contractor for Cisco last week to sort through install docs.
21:03:20 <jeblair> we would like to have core reviewers from as many openstack projects as possible on hand during that time
21:03:44 <mordred> seriously. this one _could_ break in weird places
21:03:53 <jeblair> in case we find that there is something in some project that needs fixing in order for gating to work
21:03:55 <markmc> annegentle, awesome, shaun rocks
21:04:10 <ttx> jeblair: do we have a wiki page to track the transition details ?
21:04:14 <mordred> also - infra team is all going to be offsite in nyc thursday or friday of this week - so if people could try to not break everything, that would be neat
21:04:31 <markmc> jeblair, ah, interesting - ok
21:04:39 * markmc wonders how he's going to remember that
21:04:55 <jeblair> ttx: no, but that's a good idea... perhaps if there was one with a sign-up sheet for each affected project
21:05:10 <jeblair> we'd know what kind of representation we can expect
21:05:16 <markmcclain> ttx: I'm working on a wiki for the transition
21:05:17 <jeblair> i will set that up and link to it in the email announcement
21:05:23 <ttx> jeblair: +1
21:05:28 <jeblair> i will add that to markmcclain's wiki page
21:05:45 <jeblair> ttx: [end]
21:05:59 <ttx> annegentle, jeblair: thx
21:06:36 <ttx> #topic Swift status
21:06:40 <ttx> notmyname: o/
21:06:40 <notmyname> hi
21:06:43 <ttx> #link https://launchpad.net/swift/+milestone/1.9.0
21:06:50 <ttx> Got your email about cutting a candidate today for release on July 2
21:07:00 <notmyname> yes, we are very close
21:07:02 <ttx> How is that plan going so far ?
21:07:05 <ttx> with your conference and stuff
21:07:12 <ttx> I see bug 1180680 on the 1.9.0-critical list, is that the blocker ?
21:07:22 <notmyname> is that the dispersion report?
21:07:25 <ttx> oh, you fixed it
21:07:32 <ttx> who broke the bot
21:07:42 <ttx> yes dispersion report
21:07:44 <notmyname> if so, yes. it's got one +2. just needs one more.
21:07:55 <notmyname> and we need one more test run for the write affinity
21:08:03 <ttx> NothingDone: merged one hour ago
21:08:05 <ttx> ow
21:08:11 <ttx> notmyname:  merged one hour ago
21:08:16 <notmyname> ah, cool
21:08:21 <ttx> OK, well, send me an email or an IRC ping with the SHA to cut milestone-proposed from, when you have it.
21:08:37 <ttx> with changelog in
21:08:37 <notmyname> will do. I've also got a little LP work to finish with it
21:08:46 <ttx> and bump to next version on master
21:08:47 <notmyname> ya, authors/changelog/affinity
21:08:54 <notmyname> the normal dance
21:08:59 <ttx> ack
21:09:11 <ttx> On the page linked above, "Multi region replication" and "Proxy affinity (writes)" are still marked in progress. Should they be considered "Implemented" ?
21:09:15 <notmyname> I've quite excited about this release. lots of good features, not the least of which is full global cluster support
21:09:26 <notmyname> ttx: when the write affinity lands
21:09:35 <ttx> heh, fair enough
21:10:08 <ttx> missed your mention of it above
21:10:12 <ttx> notmyname: anything else you wanted to raise ?
21:10:22 <notmyname> ttx: I'm good
21:11:26 <ttx> #topic Oslo status
21:11:35 <ttx> markmc: hi!
21:11:36 <markmc> yo
21:11:38 <ttx> #link https://launchpad.net/oslo/+milestone/havana-2
21:11:55 <markmc> so, I knocked a few bps out to havana-3
21:12:01 <markmc> still seems optimistic
21:12:15 <markmc> like a few of those probably won't make it, but I can't quite predict which yet
21:12:28 * ttx refreshes
21:12:39 <ttx> Looks on track to me...
21:12:47 <ttx> review review review
21:12:50 <markmc> yeah
21:12:53 <jd__> too good to be true
21:12:55 <markmc> http://russellbryant.net/openstack-stats/oslo-openreviews.txt
21:13:03 <markmc> we've got plenty of reviewing to be done
21:13:03 <ttx> you can't really defer more though
21:13:05 <jd__> https://review.openstack.org/#/c/32445/ looks weird btw
21:13:13 <markmc> ttx, can't really defer more?
21:13:49 <markmc> jd__, yeah, I can't remember the details, but danpb did persuade me this would be useful in all projects
21:13:51 <ttx> well, you already have 9 blueprints in h3 so given your velocity I'd say that deferring them means deferring again at the end of H3
21:14:05 <markmc> ttx, ah, got it
21:14:17 <ttx> it's not as if you had an empty h3 still :)
21:14:23 <ttx> markmc: anything you wanted to raise ?
21:14:26 <jd__> markmc: I actually meant the status of the review, it's like the commiter didn't notice the test failed and he's waiting on something
21:14:33 <markmc> nothing huge, but ...
21:14:42 <markmc> I'll do oslo-config-1.2.0a3 snapshot this week
21:14:55 <markmc> main change is ordering of priority of CLI args
21:15:05 <markmc> also, monty is putting integration testing in place for pbr
21:15:14 <markmc> and we'll have a slew of changes landing once that's in place
21:15:20 <markmc> so expect another pbr release
21:15:24 <ttx> ack. Questions about Oslo ?
21:15:30 <markmc> and we should be doing hacking 0.5.6 soon too
21:16:08 * ttx needs to work on streamlining library release announcements
21:16:10 <markmc> jd__, ah, thanks
21:16:18 <markmc> ttx, with release notes
21:16:27 * markmc started doing release notes for oslo.config
21:16:46 <ttx> yeah, implement what we discussed at the summit about automatically building those announces
21:17:03 <ttx> because currently it's a bit of an unpredictable mess
21:17:07 <markmc> from git log?
21:17:15 <markmc> human editing is preferable IMHO
21:17:27 <markmc> anyway, digression
21:17:29 <ttx> markmc: ok, will discuss off-meeting
21:17:35 <ttx> #topic Keystone status
21:17:50 <ttx> ayoung: representing keystone ?
21:17:59 <ayoung> Here
21:18:02 <ttx> or is jcannava proxying here as well ?
21:18:07 <ttx> #link https://launchpad.net/keystone/+milestone/havana-2
21:18:08 <ayoung> Keystone H2 Blueprints:
21:18:21 <ayoung> For the most part looking good.  A couple questions
21:18:26 <ayoung> jaypipes still planning on doing Region support?
21:18:57 <ttx> Looks like you're a bit behind, yes
21:19:01 <ttx> inherited-domain-goals in particular looks more likely to hit by havana-3 at that point ?
21:19:05 <jaypipes> ayoung: last I checked, termie still has the review blocked.
21:19:20 <ayoung> jaypipes, and I think we need to override that
21:19:42 <ttx> jaypipes: so that work is started ?
21:19:58 <ttx> jaypipes: shoudl I set "Needs code review" as status ?
21:20:11 <ayoung> Allow project roles to be inherited from owning domain probably underway, but Henry Nash off this week.
21:20:25 <ttx> ayoung: so it could still make h2 ?
21:20:30 <ayoung> ttx it was just the api doc that had gotten posted
21:20:35 <ayoung> ttx, unlikely
21:20:35 <jaypipes> ttx: dolphm asked me to make a proposed change to the API spec first, which I did. termie poo-poo'd it and -2 the review.
21:20:43 <ayoung> jaypipes, link?
21:21:03 <ttx> jaypipes: so I'll mark it "started".
21:21:18 <ttx> (or "Blocked"
21:21:19 <ttx> )
21:21:46 <ttx> ayoung: please look into it and unblock it if you can
21:21:50 <ttx> shardy: any progress on https://blueprints.launchpad.net/python-keystoneclient/+spec/delegation-impersonation-support ?
21:21:54 <ayoung> ttx, We'll make it happen
21:21:56 <jaypipes> ayoung: https://review.openstack.org/#/c/27563/
21:22:11 <ttx> adding review link and marking it blocked
21:22:19 <shardy> ttx: not yet, been gated on too many heat task
21:22:41 <shardy> tasks, planning to look at it later this week
21:22:48 <ttx> ok, we'll discuss the impact on heat-trusts later in the meeting
21:22:55 <ttx> ayoung: Anything more about Keystone ?
21:22:59 <ayoung> other H2 tasks seem to be on target
21:23:00 <ayoung> yes
21:23:08 <ayoung> Horizon wants updated client for V3 Auth. according to lcheng
21:23:10 <gabrielhurley> Is anyone else able to cut a python-keystoneclient release while Dolph is gone? Horizon needs a new release now that the v3 auth code is finally done and merged. It's currently a blocker for us.
21:23:13 <gabrielhurley> lol
21:23:39 <gabrielhurley> mordred: I'm looking at you...
21:23:41 <ttx> gabrielhurley: I /could/. But dolphm should be back very soon, so maybe it can wait tomorrow
21:23:52 <gabrielhurley> is he back that soon?
21:23:52 <mordred> I did not do it
21:23:55 <ayoung> also
21:23:59 <gabrielhurley> if it's one day that's fine
21:24:03 <ayoung> Unified auth.  Projects are all over the place.  Would liketo make keystone client the libary of choice there, but sort of competes with the common cli effort.
21:24:08 <gabrielhurley> if it's a week it'd be good to have someone do it sooner
21:24:24 <ttx> gabrielhurley: if he is not back tomorrow ping me and I'll tag
21:24:32 <mordred> ayoung: does it?
21:24:32 <ayoung> He's gone this week and next, IIRC
21:24:33 <gabrielhurley> can anyone confirm when he's back?
21:24:54 <ttx> ayoung: uh
21:25:00 <ayoung> sorry, I am confusing the issue.  Lets finish the cut new client discussion first
21:25:04 <mordred> ayoung: Ithought unified CLI was still using underlying libs - so it would also consume keystoneclient for auth, no?
21:25:09 * mordred shuts up
21:25:11 <russellb> mordred: i hope so.
21:25:26 <ayoung> so, yeah, we should cut a new client.
21:25:31 <gabrielhurley> +1
21:25:49 <ttx> gabrielhurley: fire an email, cc dolph, ayoung and me. If he is not around, I'll push the tag for you
21:25:53 <gabrielhurley> k
21:25:56 <gabrielhurley> doing now
21:25:56 <ayoung> Sounds good
21:25:59 <ttx> just want to give him an oppty to complain about the idea
21:25:59 <mordred> ttx: can't ayoung do it?
21:26:00 <ayoung> OK, back to the auth thing
21:26:06 <mordred> ttx: it's anyone in core isn't it?
21:26:10 <ayoung> right now, not all of the other CLIs use keystoneclient
21:26:17 <ttx> in -drivers I think.
21:26:20 <mordred> ah
21:26:37 <mordred> ayoung: I just discovered that in troveclient, in fact. I was angry
21:26:43 <ayoung> jamielennox just sent me an email with a list of the status
21:26:54 <ayoung> So for example...
21:26:56 <ttx> ayoung: could you push that to -dev ?
21:27:02 <ttx> (status)
21:27:10 <ayoung> Cinder:
21:27:10 <ayoung> - Uses requests
21:27:10 <ayoung> - Does not use keystoneclient
21:27:10 <ayoung> - Uses sleep f
21:27:18 <ayoung> Yes, will do so
21:27:30 <ttx> then we can come up with a cleanup plan
21:27:36 <ayoung> wanted to make sure there was nothing of a security nature in it first
21:27:38 <mordred> ayoung: I am strongly in favor of fixing that
21:27:49 <ttx> ayoung: sure
21:27:54 * mordred will gladly sit on the sidelines and cheer on the effort
21:27:59 <ttx> ok, we need to move on
21:28:04 <ayoung> but  are we OK with saying that all of the current clients change over to using keystoneclient as a dependency for auth?
21:28:20 <ttx> ayoung: I think that would be a sane statement
21:28:25 <mordred> ++
21:28:42 <ayoung> [end]
21:28:46 <ttx> #topic Ceilometer status
21:28:50 * ttx runs
21:28:51 <annegentle> o/
21:28:55 <ttx> jd__: hey
21:28:56 <annegentle> oh I had a keystone Q
21:29:01 <jd__> o/
21:29:09 <annegentle> ayoung: I'd also like to know when it's ok to publish a v3 WADL to api.openstack.org/api-ref.html? I didn't realize Dolph was out that long.
21:29:10 <ttx> annegentle: ah!
21:29:12 <ttx> #undo
21:29:12 <annegentle> (sorry)
21:29:13 <openstack> Removing item from minutes: <ircmeeting.items.Topic object at 0x3360590>
21:29:14 <jd__> rollback;
21:29:20 <annegentle> jd__: hee
21:29:20 <ttx> annegentle: shot
21:29:35 <ttx> annegentle: ask your question :)
21:29:54 <annegentle> ayoung: mostly a timing thing, when is it "correct" to document v3
21:30:09 <annegentle> ayoung: I think now's ok but wanted to confirm
21:30:19 <annegentle> man maybe I missed him... I'll email
21:30:22 <ayoung> annegentle, I haven't thought about it.  I will have to get back to you.  There is a V3 API doc, of course, so the answer seems to be "now"
21:30:33 <annegentle> ayoung: ok, sure.
21:30:44 <ttx> #topic Ceilometer status
21:30:51 <ttx> #link https://launchpad.net/ceilometer/+milestone/havana-2
21:31:02 <ttx> Slightly behind schedule, I'd say
21:31:15 <ttx> eglynn and dhellmann in particular look like they are late
21:31:22 <ttx> and you can't defer that much to havana-3
21:31:24 <jd__> I agree
21:31:46 <ttx> did they give you any signs that they would catch up by working 24-h shifts ?
21:31:47 <eglynn> ttx: I'm catching up, nose to grindstone ...
21:31:51 <jd__> I will pull their ears
21:32:06 <jd__> ttx: dhellmann is supposed to start this week
21:32:13 <eglynn> jd__: consider mine pulled :)
21:32:20 <ttx> I'm fine with stuff not making it... but I prefer to have those roadmaps reflecting reality as much as they can
21:32:40 <ttx> eglynn: if you think you can still make it, then I'm fine
21:32:48 <ttx> jd__: anything you wanted to mention ?
21:32:50 <eglynn> ttx: cool
21:32:55 <jd__> ttx: nop
21:33:00 <ttx> Questions on Ceilometer ?
21:33:18 <ttx> #topic Glance status
21:33:24 <ttx> markwash: o/
21:33:25 <markwash> #undo
21:33:30 <ttx> nice try.
21:33:30 <markwash> darnit
21:33:32 <ttx> #link https://launchpad.net/glance/+milestone/havana-2
21:33:38 <markwash> refresh please. . .
21:33:49 <ttx> refreshed.
21:34:14 <ttx> Look slightly behind, but not too bad
21:34:24 <markwash> yeah, we had a bit of a culling
21:34:28 <ttx> How is async-glance-workers going so far ?
21:34:46 <markwash> ttx: I have had to push that off somewhat, and need to reflect that change in the assignee
21:34:57 <markwash> but it has active work
21:35:06 <ttx> markwash: still likely to hit h2 ?
21:35:13 <markwash> ttx: as far as we can tell now, yes
21:35:25 <ttx> Iccha didn't start working on api-v2-property-protection yet ?
21:35:34 <ttx> looks like it will be deferred again
21:35:40 <markwash> not that I've seen, but it is scheduled for h2 timeframe
21:35:44 <ttx> There is not a lot of room left for deferring to h3.
21:36:04 <markwash> things in h3 might get pushed to I, to make room for higher priority h2 misses
21:36:08 <iccha> will start working on it week hopefully once the design is approved
21:36:16 <iccha> *next
21:36:18 * markwash approves design
21:36:22 <markwash> :-)
21:36:36 <ttx> markwash: shall set up the next/ongoing stuff as soon as I can beat LP into submission
21:36:47 * markwash cheers
21:36:50 <ttx> markwash: anything you wanted to mention ?
21:36:55 <markwash> yes
21:37:01 <ttx> (for the record, the API does not expose series goal at all)
21:37:01 <markwash> "Add sheepdog store"
21:37:14 <markwash> this is all ready, except we're having a bear of a time getting it to pass py26 tests in jenkins
21:37:24 <markwash> zhi yan has narrowed it down to an eventlet issue
21:37:48 <markwash> basically I need some help from infra folks to get me oriented on jenkins boxes
21:37:50 <markwash> #help :-)
21:38:01 <markwash> that is all
21:38:10 <ttx> mordred/jeblair ^
21:38:16 <ttx> Questions on Glance ?
21:38:28 <ttx> #topic Neutron status
21:38:32 <ttx> markmcclain: hi!
21:38:37 <ttx> #link https://launchpad.net/quantum/+milestone/havana-2
21:38:37 <markmcclain> hi
21:38:57 <ttx> Slightly behind, but nothing too big
21:39:02 <ttx> And you have plenty of room to defer to h3
21:39:12 <markmcclain> yeah.. I expect a few will defer
21:39:28 <markmcclain> also the rename will be disruptive
21:39:32 <ttx> do you have a URL set up for the renaming plan ?
21:39:47 <ttx> which we could add to the minutes of the meeting ?
21:40:05 <markmcclain> not yet.. I'll push to -dev list
21:40:40 <ttx> ok, everything else seems to be under control
21:40:42 <ttx> markmcclain: anything you wanted to raise ?
21:40:59 <markmcclain> #link https://wiki.openstack.org/wiki/Network/neutron-renaming
21:41:08 <markmcclain> nothing else to raise
21:41:11 <ttx> cool, thx
21:41:18 <ttx> Questions on Neutron ?
21:41:33 <ttx> #topic Cinder status
21:41:38 <ttx> jgriffith: hola!
21:41:42 <ttx> #link https://launchpad.net/cinder/+milestone/havana-2
21:41:42 <jgriffith> Howdy!!
21:42:00 <ttx> Still a bit slow progress overall... but then you have room in h3 to defer
21:42:04 <jgriffith> I've got requests out for Huaweii fellows and one of the DB guys
21:42:11 <jgriffith> Tons o'room :)
21:42:14 <jeblair> markwash: can you drop by #openstack-infra tomorrow?  i'm about to head out to dinner.
21:42:23 <ttx> Should https://blueprints.launchpad.net/cinder/+spec/netapp-unified-driver be considered 'implemented' since https://review.openstack.org/#/c/33168/ was merged ?
21:42:26 <jgriffith> I think most of these are going to make it
21:42:39 <jgriffith> Umm...yup
21:42:46 <ttx> will fix
21:43:03 <ttx> Still have 4 blueprints proposed @ https://blueprints.launchpad.net/cinder/havana/+setgoals
21:43:12 <ttx> can't wait until we don't have to care for that anymore
21:43:17 <ttx> jgriffith: anything on your mind ?
21:43:30 <jgriffith> you and I both.. everybody keeps sneaking stuff in there
21:43:38 <jgriffith> Nope, just the note about pecan to the ML
21:43:43 <jgriffith> other than that we're rollign along
21:43:48 <ttx> Questions on Cinder ?
21:44:08 <markwash> jeblair: sure, thanks!
21:44:11 <ttx> #topic Nova status
21:44:14 <ttx> russellb: hey
21:44:17 <ttx> #link https://launchpad.net/nova/+milestone/havana-2
21:44:30 <russellb> hey
21:44:44 <ttx> A slight bit behind, I'd say, from a 10,000 feet viewpoint
21:44:45 <russellb> mountain of code reviews to do
21:44:48 <russellb> yeah.
21:44:57 <russellb> i'm starting to move stuff "Not Started" to havana-3
21:45:00 <ttx> Critical point being Christopher Yeoh's 10 High blueprints. Could you give us an update on that ?
21:45:26 <russellb> Yeah, so those are all subsets of the v3 API work, which he broke up.  More than just him are working on them
21:45:30 <russellb> and they've made lots of good progress
21:45:44 <ttx> russellb: so that's still on track
21:45:47 <russellb> yeah
21:46:00 <ttx> russellb/vishy: about deprecate-nova-network, should that work start early so that it's completed by h3 ?
21:46:02 <russellb> reviewers probably need to do a better job at giving their reviews attention
21:46:20 <russellb> yeah, i haven't heard anything about that
21:46:28 <russellb> vishy and garyk were going to work on it
21:46:35 <vishy> russellb: I haven't made much progress on that side
21:46:36 * ttx doesn't like Essential/h3 stuff
21:46:41 <russellb> vishy: figured
21:46:53 <russellb> another thing was full tempest support, which i'm not sure we're even tracking
21:47:13 <ttx> vishy: what's your plan ? Start soon ? Doesn't sound like a no-brainer to me ;)
21:47:26 <vishy> ttx: well we don't have one obv!
21:47:28 <ttx> or do it all within h3 ?
21:47:39 <ttx> obv?
21:47:42 <russellb> obviously?
21:47:51 <vishy> ttx: garyk was investigating trying to move from nova network to quantum via live migration
21:47:51 <ttx> obviously.
21:48:00 <vishy> and i was going to look at moving without live migration
21:48:22 <vishy> I have managed to replicate a few different forms of nova-network in quantum
21:48:31 <vishy> one of them is pretty much a no-go
21:48:45 <ttx> vishy: "essential" says we really need to have a plan though. whereas "high" says we really want to have a plan :)
21:48:46 <vishy> but i haven't tested the actuall unplug and plug
21:48:46 <russellb> ah interesting ... would be good to have a write-up on those
21:49:03 <vishy> russellb: i will put something together
21:49:03 <russellb> ttx: probably should downgrade to High at this point.
21:49:06 <russellb> vishy: awesome
21:49:16 * markmcclain is interested in what you've found
21:49:24 <ttx> russellb: tat would mean go for another release with nova-network not deprecated, right ?
21:49:33 <ttx> (if we miss it)
21:49:36 <russellb> ttx: it would ... and i guess i'd really rather not
21:49:38 <vishy> russellb: the multi-host network (not merged yet) stuff is required to get really close
21:50:06 <vishy> russellb: I will write up some stuff and try to the unplug plug stufff
21:50:12 <russellb> ok cool
21:50:12 <ttx> russellb, vishy: ok
21:50:27 <ttx> we'll track progress on that on future meetings
21:50:37 <russellb> sounds good
21:50:46 <ttx> and maybe downgrade to High if it starts to smell funny
21:50:49 <ttx> russellb: anything else you wanted to mention ?
21:51:15 <russellb> don't think so
21:51:17 <ttx> Any question on Nova ?
21:51:22 <russellb> we're running behind on reviews, hoping we can improve tht
21:51:30 <ttx> #topic Heat status
21:51:35 <ttx> shardy: o/
21:51:37 <shardy> o/
21:51:40 <ttx> #link https://launchpad.net/heat/+milestone/havana-2
21:51:56 <ttx> Good progress, still slightly behind, I'd say
21:52:16 <shardy> moved a couple of BPs to h3 that were not started or blocked
21:52:18 <ttx> we shoudl have a better view next week
21:52:28 <ttx> yes, h3 is filling up fast
21:52:34 <shardy> otherwise, think we should be OK with what is there
21:52:44 <ttx> you moved heat-trusts to h3, right ?
21:52:45 <shardy> the problem recently is review overhead
21:53:16 <ttx> Was wondering if https://blueprints.launchpad.net/heat/+spec/provider-upload was not completed already with https://review.openstack.org/#/c/33008/
21:53:28 <shardy> ttx: yes, it's taken, way, way longer than I expected to get the suspend/resume code merged, so the keystoneclient and heat-trusts stuff has slipped
21:54:04 <shardy> ttx: Possibly, I need to check with asalkeld at our meeting tomorrow if there are more patches coming
21:54:11 <ttx> shardy: anything else you want to raise ?
21:54:32 <shardy> ttx: don't think so, no, thanks
21:54:32 <ttx> Questions about Heat ?
21:54:48 <ttx> #topic Horizon status
21:54:51 <ttx> gabrielhurley: o/
21:54:54 <ttx> #link https://launchpad.net/horizon/+milestone/havana-2
21:55:10 <ttx> A bit late at this point, and not so much room to defer to h3
21:55:53 <gabrielhurley> \o
21:56:08 <gabrielhurley> yeah, some things are gonna fall off
21:56:11 <ttx> The "igh" in particular are not in a very good shape
21:56:15 <ttx> high
21:56:36 <gabrielhurley> I'll rearrange whatever's not started by next week (including knocking a few off of H3 most likely)
21:56:46 <ttx> gabrielhurley: +1
21:56:53 <ttx> Two blueprints proposed @ https://blueprints.launchpad.net/horizon/havana/+setgoals fwiw
21:56:59 <ttx> gabrielhurley: anything you wanted to mention ?
21:57:24 <gabrielhurley> not particularly. you can have the last minutes for the other projects
21:57:54 <ttx> Questions on Horizon ?
21:58:07 <ttx> #topic Incubated projects
21:58:18 <devananda> Hi!
21:58:23 <ttx> devananda: o/
21:58:30 <devananda> just one thing for today
21:58:31 <ttx> Looks like we don't have hub_cap around
21:58:37 <devananda> A key feature for Ironic being feature-complete (and thus reaching an RC) is porting the PXE driver, which is currently blocked on porting image tools into glanceclient. Specifically, these two patches:
21:58:41 <devananda> https://review.openstack.org/#/c/34320/1 and https://review.openstack.org/#/c/33327/
21:58:54 <devananda> so I'd like to raise awareness and hope some reviewers can come look at those :)
21:59:10 <devananda> it's not the only thing on our plates -- but it's a big one
21:59:30 <ttx> #help markwash: devananda needs glance-core help on https://review.openstack.org/#/c/34320/1 and https://review.openstack.org/#/c/33327/
21:59:46 <devananda> thanks much :)
21:59:52 <ttx> devananda: are you likely to have something ready by the h2 milestone ?
21:59:57 <devananda> nope
22:00:00 <devananda> h3 is also unlikely
22:00:38 <ttx> devananda: note that it affects the chnaces of proper graduation
22:00:49 <devananda> indeed.
22:01:04 <ttx> we'll cover that in a future meeting
22:01:20 <ttx> i.e. progress or not progress :)
22:01:26 <ttx> our time is up
22:01:30 <ttx> #endmeeting