21:01:26 <ttx> #startmeeting project
21:01:27 <openstack> Meeting started Tue Aug 20 21:01:26 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:30 <openstack> The meeting name has been set to 'project'
21:01:33 <ttx> #link http://wiki.openstack.org/Meetings/ProjectMeeting
21:01:38 <ttx> #topic General stuff
21:01:47 <ttx> Some FeatureProposalFreezes hit this week:
21:01:55 <ttx> Nova and Cinder on Aug 21, Neutron and Heat on Aug 23
21:02:17 <ttx> that's all I had
21:02:20 <gabrielhurley> \o
21:02:23 <ttx> sdague, annegentle, mordred: news from QA/Docs/Infra programs ?
21:03:15 <ttx> Or anything newsworthy before we dive into project-specific stuff ?
21:04:03 <ttx> well, I guess not
21:04:13 <ttx> #topic Oslo status
21:04:19 <markmc> hey
21:04:21 <ttx> markmc: hi!
21:04:33 <ttx> #link https://launchpad.net/oslo/+milestone/havana-3
21:04:56 <markmc> so, the main thing on my mind is the patch set to port nova to oslo.messaging: https://review.openstack.org/39929
21:05:02 <markmc> it's in pretty good shape
21:05:03 <ttx> 100% done, 0% under review, 0% in progress, 0% not started
21:05:16 <markmc> also, we deferred secure messaging to icehouse
21:05:31 <ttx> You mentioned freezing oslo-incubator's features ahead of projects FeatureProposalFreeze so that the relevant syncs can be proposed in time...
21:05:32 <markmc> there's a few low priority bps close to being merged
21:05:47 <markmc> yeah, I consider us feature frozen apart from those three
21:05:48 <ttx> There are 3 "Low" blueprints under review, and at least some of them look like they will end up in the incubator code ?
21:05:56 <markmc> giving them another week or so
21:06:21 <markmc> none of them should be a big regression risk for projects
21:06:25 <markmc> they're all net-new
21:06:40 <ttx> We should just make sure the consuming projects are fine for syncs after their FeatureProposalFreezes
21:07:05 <ttx> corner case
21:07:15 <markmc> yeah, I don't think it'll apply for any of these three
21:07:26 <markmc> I'm not sure any projects will start using them in havan
21:07:26 <ttx> ok
21:07:35 <markmc> which obviously begs the question, why merge them :)
21:07:42 <markmc> but, since they're close ... :)
21:08:00 <russellb> markmc: mainly to let someone have it checked off their todo list
21:08:02 <ttx> which begs the question, should Oslo feature-freeze around h2 ?
21:08:24 <markmc> nah, it's just specifically those three
21:08:27 <ttx> to let the consuming project catch up in making use of that stuff
21:08:37 <markmc> very plausible that stuff merging today could be picked up by other projects
21:08:48 <markmc> and that the per-project bps could have been approved ages ago
21:09:02 <ttx> markmc: I was just trolling you. anything else you wanted to raise ?
21:09:20 <markmc> yeah, setting a date for releasing oslo.config and oslo.messaging 1.2.0
21:09:25 <markwash> yeah that
21:09:28 <markmc> I'm figuring after havana-3
21:09:53 <markmc> it's all just about having time to update the requirements.txt of projects to not point to tarballs.openstack.org
21:09:59 <ttx> markmc: I suspect it's only bugfixes compares to current versions ?
21:10:04 <markmc> right, exactly
21:10:11 <markwash> is it an issue for packagers for us to depend on an alpha release in glance? sorry if I'm not remembering things I ought to
21:10:21 <ttx> markmc: can be a post-h3 pre-rc1 thing
21:10:41 <markmc> markwash, https://wiki.openstack.org/wiki/Oslo#Why_aren.27t_alpha_releases_of_oslo.config_published_to_PyPI.3F :)
21:10:51 <markmc> markwash, it's not an issue for packagers, no
21:10:56 <ttx> Other questions about Oslo ?
21:11:01 <markwash> I looked there, and couldn't find what I wanted, but I am lazy
21:11:30 <ttx> #topic Keystone status
21:11:33 <dolphm_> o/
21:11:36 <ttx> dolphm: hi
21:11:40 <ttx> #link https://launchpad.net/keystone/+milestone/havana-3
21:11:46 <ttx> 54% done, 18% under review, 27% in progress, 0% not started
21:11:57 <ttx> Looks good to me
21:12:00 <dolphm_> i think we managed to go from 0% done to 54% since last week :P
21:12:09 <ttx> dolphm_: About key-distribution-server, did we settle on merging it early in icehouse ?
21:12:15 <ttx> And concentrate on moving the other projects to fully use trusted-messaging within that cycle ?
21:12:59 <dolphm_> ttx: i haven't had a chance to talk to simo about it yet, but that's certainly what i'm leaning towards after the ML discussion
21:13:27 <ttx> dolphm_: looks like that's what markmc understood too
21:13:54 <markwash> has the security team been involved in this plan, and I just missed it? this is a case where sometimes audits are comforting
21:14:10 <ttx> dolphm_: please update blueprint accordingly when you get it confirmed
21:14:20 <dolphm_> ttx: will do, i'll also poke the list in that thread
21:14:22 <dolphm_> markwash: not that i'm aware of
21:14:26 <ttx> markwash: They are summoned using SecurityImpact tag
21:14:38 <ttx> although that doesn't work all the time
21:15:03 <ttx> dolphm_: store-quota-data and pagination-backend-support are marked "Slow progress", could you elaborate on that ?
21:15:32 <ttx> Both getting unlikely to make it ?
21:15:46 <dolphm_> they're raising red flags for me..
21:16:14 <dolphm_> store-quote-data has just had a slow code review cycle thus far, but hopefully we can start dedicating more review bandwidth to it
21:16:30 <ttx> does that mean you're pretty confident for the 'Caching layer implementation around driver calls' thing ?
21:16:35 <dolphm_> pagination has expanded in scope and is being split into a second blueprint to focus on filtering
21:16:52 <dolphm_> we'll likely target filtering to havana-m3 and pagination will be dependent on that
21:17:05 <ttx> dolphm_: Within the remaining features, is there anything that the consuming projects need changes to take advantage of the feature (like the KDS) or is it all internal ?
21:17:26 <ttx> trying to make sure they have enough turnaround to make it useful
21:18:02 <dolphm_> store-quota-data and KDS would both be disabled by default, but expose new API's when explicitly included in the wsgi pipeline
21:18:25 <ttx> ok
21:18:27 <dolphm_> the same goes for endpoint-filtering
21:18:28 <ttx> dolphm: anything you wanted to raise ?
21:18:37 <dolphm_> i think we covered it all!
21:18:39 <ttx> Questions anyone ?
21:19:03 <ttx> #topic Ceilometer status
21:19:07 <ttx> jd__: hey
21:19:10 <ttx> #link https://launchpad.net/ceilometer/+milestone/havana-3
21:19:11 <jd__> o/
21:19:16 <ttx> 25% done, 25% under review, 50% in progress, 0% not started
21:19:21 <ttx> Still a bit behind, but looking better with only 8 blueprints left :)
21:19:45 <jd__> we are à fond les ballons
21:19:49 <ttx> jd__: Is there more to alarming-logical-combination than the two reviews already proposed ?
21:20:10 <jd__> ttx: not sure, but I think it's at least 80% of the bp
21:20:27 <jd__> I didn't check with sileht yet, he sent the working patches today
21:20:33 <ttx> What's the status of eglynn "High" blueprints (alarm-audit-api and alarm-service-partitioner) ?
21:20:41 <jd__> eglynn has been on vacation but he's going to finish RSN
21:20:57 <jd__> he has patches almost ready to be sent
21:20:57 <ttx> cool
21:21:16 <jd__> and I'm still working with terriyu on the group by one
21:21:26 <ttx> jd__: anything else you wanted to mention ?
21:21:35 <jd__> nop
21:21:40 <ttx> Questions on Ceilometer ?
21:22:08 <ttx> #topic Swift status
21:22:11 <notmyname> hi
21:22:12 <ttx> notmyname: o/
21:22:16 <ttx> notmyname: what news ?
21:22:34 <notmyname> we got 1.9.1 released, and so now the next thing is moving to pbr
21:22:44 <notmyname> I'll be working with mordred on this this week
21:22:58 <notmyname> that will necessitate some versioning dances, and it will affect packagers
21:22:59 <ttx> He completed the merge-tags thing
21:23:04 <mordred> notmyname: I may need to have you work with clarkb or someone else
21:23:08 <mordred> I'm out starting tomorrow morning
21:23:13 <notmyname> right, but we have a migration phase to do
21:23:14 <notmyname> mordred: ok
21:23:21 <mordred> or, wait two weeks until I'm back
21:23:24 <mordred> I'm fine either way
21:23:35 <notmyname> sooner the better since it affects every packager out there
21:23:40 <mordred> kk
21:23:42 <ttx> notmyname: ok, keep me in the loop, I'll have to adjust release process accordingly
21:23:49 <notmyname> ttx: will do
21:23:51 <notmyname> in other news..
21:24:04 <notmyname> erasure coding discussions and progress is coming along
21:24:13 <notmyname> https://trello.com/b/LlvIFIQs/swift-erasure-codes
21:24:34 <notmyname> and the local file system work is going well also
21:24:42 <ttx> notmyname: Can you confirm the next Swift release should probably be the Havana coordinated one ?
21:25:04 <notmyname> yes, it should, unless there is something major that comes up, like a security issue
21:25:17 <notmyname> I'm not sure yet if these will be completed before havana, but they are major features we're tracking
21:25:20 <ttx> Any major feature on your roadmap for this one ? I suspect erasure codes won't make it ?
21:25:35 <notmyname> EC likely won't
21:25:50 <ttx> notmyname: anything else you wanted to raise ?
21:25:53 <notmyname> I hope the LFS things will
21:26:07 <notmyname> hotel block for the swift hackathon has been set
21:26:13 <notmyname> http://swifthackathon.eventbrite.com
21:26:46 <notmyname> that's what I have
21:26:47 <ttx> Questions about Swift ?
21:27:15 <ttx> #topic Glance status
21:27:20 <ttx> markwash: o/
21:27:22 <markwash> hi
21:27:27 <ttx> #link https://launchpad.net/glance/+milestone/havana-3
21:27:34 <ttx> 50% done, 0% under review, 50% in progress, 0% not started
21:27:39 <ttx> round numbers
21:27:44 <markwash> that's the goal
21:27:45 <ttx> Looks good, though more code proposed wouldn't hurt
21:28:05 <ttx> markwash: Should configurable-formats be considered "Needs Code Review" with https://review.openstack.org/#/c/42535/ ?
21:28:11 <markwash> a fair amount is proposed, and just needs some more review and rework, so maybe I haven't been updating the formats correctly
21:28:15 <markwash> yes
21:28:28 <markwash> so should basic quotas
21:28:33 <markwash> and scrubber refactoring
21:28:46 <ttx> markwash: ok, I'll let you update them all
21:28:59 <ttx> How is api-v2-property-protection looking at this point ?
21:29:06 <ttx> You know how much I like this one.
21:29:10 <markwash> I know
21:29:20 <markwash> we should probably keep it around for icehouse, for your sake
21:29:25 <ttx> I'll be sad to see it go, but otoh...
21:29:42 <markwash> I'll be doubleplusgood and resolve that one for next week
21:30:10 <markwash> we've also had some important bugs pop up
21:30:10 <ttx> plusgood
21:30:20 <markwash> so those will take some priority for me
21:30:30 <markwash> though they are mostly also in review
21:30:32 <ttx> markwash: please target them t oh3 so that we keep them on hte milstone radar
21:30:37 <ttx> markwash: anything you wanted to mention ?
21:30:48 <markwash> nope
21:30:59 <markwash> what does a fond les ballons mean?
21:31:07 <markwash> so I don't spend all next week puzzling over it
21:31:10 <markmc> found of balloons
21:31:13 <ttx> very quickly
21:31:28 <ttx> like "� fond la caisse".
21:31:37 <markwash> oh yes, like that
21:31:39 <ttx> Questions on Glance ?
21:31:43 <markwash> . . .
21:31:55 <ttx> means "very quickly"
21:32:07 <ttx> #topic Neutron status
21:32:15 <markmcclain> hi
21:32:18 <ttx> markmcclain: hi!
21:32:23 <ttx> #info Neutron feature code needs to be up for review by Friday
21:32:30 <ttx> #link https://launchpad.net/neutron/+milestone/havana-3
21:32:38 <ttx> 41% done, 51% under review, 7% in progress, 0% not started
21:32:49 <ttx> So it's that 7% in progress that needs to be solved this week
21:33:12 <ttx> sounds more than doable
21:33:31 <ttx> How are ipv6-feature-parity and configurable-ip-allocation looking so far ?
21:33:45 <markmcclain> configurable ip allocations is still good
21:34:00 <ttx> and ipv6-feature-parity still in jeopardy ?
21:34:24 <markmcclain> ipv6 will be close
21:34:48 <ttx> well, you can give you an exception quite eaily
21:34:53 <ttx> easily*
21:35:11 <markmcclain> yeah.. there's a good chance that will happen
21:35:15 <ttx> You have two Low blueprints without a status set: nec-port-binding and nvp-vpnaas-plugin
21:35:35 <ttx> would be cool to ask their assignees to give us an idea of where they are
21:35:48 <ttx> Also two blueprints in the triaging queue: multi-workers-for-api-server and neutron-fwaas-explicit-commit
21:35:55 <markmcclain> ah.. missed those earlier.. I'll follow up
21:36:07 <ttx> oh, and a third one just added
21:36:13 <ttx> https://blueprints.launchpad.net/neutron/+spec/vcns-driver
21:36:20 <ttx> Unless they come with code proposed my suggestion would be to defer them :)
21:36:21 <markmcclain> so mulitworkers has 3 code proposals that we're sorting out
21:36:46 <ttx> You have a lot of Low blueprints that shall go down the drain at the end of the week. Hope you communicated that FeatureProposalFreeze well :)
21:37:02 <markmcclain> explicit commit has code proposed, but still trying to develop a team consensus
21:37:10 <ttx> but it should really help to focus review activity
21:37:23 <markmcclain> I have, but I get the feeling reality will set in when they move out of havana
21:37:43 <ttx> indeed
21:37:50 <ttx> markmcclain: anything else you wanted to raise ?
21:38:09 <markmcclain> no.. we've covered it
21:38:21 <ttx> Questions on Neutron ?
21:38:30 <ttx> #topic Cinder status
21:38:35 <ttx> jgriffith: hola!
21:38:38 <ttx> #info Cinder feature code needs to be up for review by tomorrow
21:38:42 <ttx> #link https://launchpad.net/cinder/+milestone/havana-3
21:38:50 <ttx> 35% done, 29% under review, 23% in progress, 11% not started
21:39:31 <ttx> is jgriffith around ?
21:40:17 <ttx> I guess not, let's skip
21:40:29 <ttx> #topic Nova status
21:40:32 <russellb> hey
21:40:36 <ttx> russellb: hey
21:40:41 <ttx> #info Nova feature code needs to be up for review by tomorrow
21:40:47 <ttx> #link https://launchpad.net/nova/+milestone/havana-3
21:40:49 <russellb> i sent out a review call to arms to nova-core yesterday :-)
21:41:07 <russellb> going to be an intense couple of weeks getting in what we can
21:41:24 <russellb> most stuff is ready for review, or super close ... lots in "Low" that will get deferred i suspect
21:41:28 <ttx> Last time I looked this was lacking a bit in the %done department...
21:41:29 <russellb> i haven't been watching that stuff very closely
21:41:33 <russellb> yeah.
21:41:41 <russellb> hence the call to arms to reviewers
21:41:42 <ttx> But my main concern is those %inprogress with one day left
21:41:48 <ttx> 25% done, 57% under review, 17% in progress, 0% not started
21:42:04 <russellb> all the ones left in progress are ones people have told me will be ready on time
21:42:05 <russellb> we'll see
21:42:15 <russellb> but i have no problems deferring any of them if not
21:42:17 <ttx> Especially the 4 "High" ones
21:42:34 <russellb> i think they'll make it
21:42:39 <ttx> Would be great to properly complete compute-api-objects
21:42:49 <ttx> and graceful-shutdown
21:42:55 <russellb> i haven't gotten a libvirt console logging update this week though
21:43:02 <russellb> graceful shutdown was deferred
21:43:06 <russellb> ( a few minutes ago)
21:43:09 <ttx> ah.
21:43:12 <russellb> was able to confirm it won't make it
21:43:43 <russellb> compute api objects has a ton of patches up for review or already merged
21:43:45 <ttx> mikal might be a bit busy with newkid
21:43:48 <russellb> yeah
21:43:56 <russellb> so that one may not make it ... :-/
21:44:04 <russellb> the issue that we just can't ever make go away
21:44:08 <ttx> it's amlready a miracle so many made it, tbh
21:44:18 <ttx> russellb: anything else you wanted to mention ?
21:44:38 <russellb> dpm
21:44:40 <russellb> err.
21:44:42 <russellb> don't think so
21:44:42 <ttx> Any question on Nova ?
21:44:43 <russellb> thanks!
21:44:52 <ttx> #topic Heat status
21:44:57 <ttx> shardy: o/
21:45:03 <ttx> #info Heat feature code needs to be up for review by Friday
21:45:05 <shardy> ttx: hi
21:45:12 <ttx> #link https://launchpad.net/heat/+milestone/havana-3
21:45:18 <ttx> 61% done, 19% under review, 19% in progress, 0% not started
21:45:28 <ttx> Looking good, just need to convert those 19% to "under review" before eow
21:45:47 <shardy> Think we're looking OK apart from the two blocked ones
21:45:57 <shardy> trusts and vpnaas
21:46:14 <ttx> About heat-trusts - looks like it might need to be deferred or granted an exception to deal with lateness on the python-keystoneclient side...
21:46:37 <shardy> yeah, I have a feeling some of the in-progress are already under review, but need to check with the assignees
21:46:52 <shardy> Well the keystoneclient patch is up just needs review
21:46:55 <ttx> Do you expect that to move before the end of the week ?
21:47:09 <shardy> dolphm_: ^^
21:47:12 <ttx> maybe hunt down some keystone reviewers :)
21:47:13 <dolphm_> i can get some eyes on it :)
21:47:20 <ttx> dolphm_: thx
21:47:29 <ttx> shardy: anything else you want to raise ?
21:47:41 <shardy> I'm hoping to post the heat part of the patch tomorrow, but we can't merge it without the keystoneclient patch, and a keystoneclient release I guess
21:47:58 <shardy> ttx: no think that's it, thanks!
21:48:09 <ttx> shardy: you can post it so that it gets early reviews
21:48:15 <ttx> and passes FPF
21:48:20 <ttx> Questions about Heat ?
21:48:40 <shardy> ttx: yeah, just been battling with various trusts issues for a few days, nearly there now ;)
21:49:01 <ttx> #topic Horizon status
21:49:06 <gabrielhurley> \o
21:49:06 <ttx> gabrielhurley: o/
21:49:11 <ttx> #link https://launchpad.net/horizon/+milestone/havana-3
21:49:16 <ttx> 35% done, 42% under review, 21% in progress, 0% not started
21:49:24 <ttx> Looks very much on track to me
21:49:36 <ttx> No further comment.
21:49:39 <gabrielhurley> The review status is actually mostly waiting on gerrit/jenkins. we've had a lot of merge issues lately. note the 11 reviews which are approved but not merged here: https://review.openstack.org/#/q/status:open+project:openstack/horizon,n,z
21:50:09 <gabrielhurley> but yeah, I'd say on track
21:50:30 <ttx> gabrielhurley: is it just general slowness, or exceptional recent slowness ?
21:50:38 * ttx checks queue
21:50:40 <gabrielhurley> today's been slower than usual
21:50:57 <ttx> gate is 40-changes deep
21:50:59 <gabrielhurley> and recently we just incidentally had a bunch of merge conflicts that required rebases
21:51:10 <ttx> will take some time
21:51:13 <gabrielhurley> so we've had to run some of these repeatedly
21:51:15 <gabrielhurley> yeah
21:51:22 <gabrielhurley> I figure give it a day or two and those'll all get through
21:51:28 <gabrielhurley> not ideal
21:51:30 <gabrielhurley> but not terrible
21:51:48 <ttx> that's why it's better to not rely on it being usable in the last week(s). There will always be too much load
21:51:54 <gabrielhurley> yep
21:51:57 <ttx> and merge the key stuff before
21:52:07 <ttx> gabrielhurley: anything else you wanted to mention ?
21:52:13 <gabrielhurley> I added https://blueprints.launchpad.net/horizon/+spec/add-trove-panels-unit-tests-coverage to the H3 targets... I may or may not keep it there. Gonna discuss more at the Horizon meeting next.
21:52:37 <hub_cap> :D
21:52:47 <gabrielhurley> that's all I've got
21:52:53 <ttx> https://blueprints.launchpad.net/horizon/+spec/swift-display-metadata could use a status other than unknown
21:52:55 <hub_cap> gabrielhurley: do the guys working on the trove stuff know about it?
21:53:20 <hub_cap> *do they know u are discussing in next meeting
21:53:25 <gabrielhurley> ttx: it's needs code review. fixed. I got distracted on that one
21:53:31 <ttx> Other questions on Horizon ?
21:53:43 <ttx> Is jgriffith in the house ?
21:53:49 <gabrielhurley> hub_cap: no, I only added it an hour ago. but it's not about the code. it's more of a principle decision
21:54:04 <hub_cap> okey! im sure they'd like to listen, i know i will ;)
21:54:10 <hub_cap> ill tell them not to interject too much heh
21:54:16 <gabrielhurley> sounds good
21:54:19 <hub_cap> <3
21:54:50 <ttx> Looks like we don't have jgriffith today.
21:54:57 <ttx> I'll catch up with him tomorrow
21:55:07 <ttx> #topic Incubated projects
21:55:17 <NobodyCam> o/
21:55:30 <ttx> NobodyCam: hola!
21:55:36 <ttx> devananda, hub_cap: howdy
21:55:36 <hub_cap> \*/
21:55:40 <ttx> Any question ?
21:55:48 <hub_cap> nope. just fnishing heat
21:55:48 <NobodyCam> hola ! it's /me for devananda
21:55:55 <hub_cap> in a mountain in NC lol
21:55:59 <NobodyCam> We are down a couple of contributors, out on vacation. Deva is off in the desert burning things for the next two weeks, but we are moving forward slowly.
21:56:25 <ttx> hub_cap: still on track for integrating heat in h3 ?
21:56:38 <hub_cap> as of now most def
21:56:38 <ttx> NobodyCam: ack
21:56:47 <ttx> awesome
21:56:48 <hub_cap> ill know more next wk
21:56:56 <hub_cap> im sure ill have bugs but thats what RC1 is for ;)
21:57:19 <ttx> no that's what integration tests are for :)
21:57:30 <hub_cap> touché
21:57:36 <ttx> next on the todo list I gather :)
21:58:01 <hub_cap> its #2 good sir
21:58:09 <ttx> ok, well unless you have more questions, or we see the last minute return of jgriffith...
21:58:17 <ttx> We'll close now
21:58:18 <hub_cap> lol im good
21:58:20 <hub_cap> hugs
21:58:38 <med_> heh
21:58:45 * ttx hugs back
21:58:48 <hub_cap> :D
21:58:48 <ttx> #endmeeting