21:02:19 <ttx> #startmeeting project
21:02:20 <openstack> Meeting started Tue Jan 22 21:02:19 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:23 <openstack> The meeting name has been set to 'project'
21:02:25 <ttx> Agenda @ http://wiki.openstack.org/Meetings/ProjectMeeting
21:02:30 <ttx> #topic General announcements
21:02:36 <ttx> I had nothing specific
21:02:41 <ttx> markmc, mordred, annegentle, davidkranz: Anything from Stable/CI/QA/Docs teams ?
21:02:54 <mordred> nope
21:02:55 <markmc> #info 2012.2.3 scheduled for Jan 31, RC Jan 24
21:03:01 <markmc> latest status posted earlier
21:03:03 <markmc> #link http://lists.openstack.org/pipermail/openstack-stable-maint/2013-January/000282.html
21:03:10 <markmc> summary is we're looking pretty good
21:03:16 <markmc> may see some more nova backports
21:03:24 <markmc> and a couple of security fixes in the work
21:03:27 <markmc> s
21:03:29 <davidkranz> We are getting close to being able to have more tempest gating turned on for other projects.
21:03:39 <russellb> notmyname: pretty picture indeed ... that can have my #2 spot.
21:03:51 <davidkranz> I will post a proposal soon.
21:04:40 <ttx> OK, let's go project-specific now
21:04:44 <ttx> #topic Oslo status
21:04:48 <ttx> #link https://launchpad.net/oslo/+milestone/grizzly-3
21:04:56 <ttx> markmc: Nice progress
21:05:08 <markmc> oslo-config is inching it's way forward
21:05:15 <markmc> #link https://review.openstack.org/#/c/20117/
21:05:24 <markmc> that's for importing oslo-config into gerrit etc.
21:05:37 <markmc> apart from that, I'm a bit behind on how the other features are going
21:05:51 <ttx> markmc: The idea would be to switch to bugfixing ASAP so that the common libs are pretty stable around g3 publication time ?
21:06:22 <markmc> ttx, yes, that sounds about right
21:06:26 <ttx> Still have oslo-build, wsgi-common, no-kombu-default, rpc-api-review with series set to grizzly at https://blueprints.launchpad.net/oslo/grizzly
21:06:32 <markmc> oh
21:06:40 <markmc> I'll drop them all
21:06:42 <markmc> thanks again
21:06:44 <ttx> ok
21:06:47 <ttx> Anything else on the oslo topic ?
21:06:58 <markmc> nope
21:07:24 * ttx keeps keystone for the end just in case heckj shows up late
21:07:50 <ttx> dolphm_: can you replace him if he isn't available ?
21:07:57 <ttx> #topic Swift status
21:08:01 <ttx> notmyname: o/
21:08:03 <notmyname> hi
21:08:05 <ttx> #link https://launchpad.net/swift/+milestone/1.7.6
21:08:14 <ttx> Release branch is still under testing...
21:08:20 <ttx> Going well so far ? Still targeting Thursday for the release ?
21:08:26 <notmyname> things look good AFAIK for 1.7.6 release on thursday
21:08:51 <notmyname> I'll also tag a new python-swiftclient on thursday too
21:08:57 <ttx> I just prepared a FINAL=True change for milestone-proposed, for your approval pleasure when everything is ready for release:
21:09:11 <ttx> https://review.openstack.org/#/c/20276/
21:09:35 <ttx> You might want to -2 that temporarily to make sure nobody accidentally accepts it :)
21:09:45 <notmyname> ya, was doing that now :-)
21:10:06 <ttx> Anything more on Swift ?
21:10:32 <notmyname> not this week
21:10:40 <ttx> ok then
21:10:44 <ttx> #topic Glance status
21:10:51 <ttx> bcwaldon: o/
21:10:55 <ttx> #link https://launchpad.net/glance/+milestone/grizzly-3
21:11:22 <bcwaldon> ttx: hello!
21:11:23 <ttx> You said you would lock down glance-notifications-deux assignee this week... Any candidate ?
21:11:36 <bcwaldon> yes, Andrew melton
21:12:10 <ttx> bcwaldon: ok, can you assign him ? or should I ?
21:12:20 <bcwaldon> go right ahead
21:12:26 <ttx> bcwaldon, iccha: how is glance-api-v2-image-sharing going so far ?
21:12:49 <ttx> (assigned)
21:12:51 <bcwaldon> several emails about implementation at this point - path forward is clear at this point
21:13:56 <ttx> ok, we'll be keeping an eye on this one to make sure code is proposed early
21:14:01 <ttx> Anything more on Glance ?
21:14:42 <bcwaldon> not from me :)
21:14:55 <ttx> bcwaldon: markwash is finalizing glance-domain-logic-layer before starting api-v2-property-protection ?
21:15:05 <bcwaldon> yes
21:15:09 <ttx> ack
21:15:14 <ttx> #topic Quantum status
21:15:19 <ttx> danwent: hi!
21:15:25 <danwent> hello :)
21:15:26 <ttx> #link https://launchpad.net/quantum/+milestone/grizzly-3
21:15:33 <danwent> more BPs, not less :(
21:15:38 * ttx refreshes
21:15:46 <danwent> we talked about this at our team meeting yesterday
21:16:01 <ttx> Script reports new stuff targeted to grizzly-3 but not approved in series goal:
21:16:16 <danwent> basicaly, the core devs are going to focus on making sure that the 6 'high' items get merged.  everything else is "best effort"
21:16:25 <danwent> ttx: yes, people get adding more
21:16:29 <ttx> brocade-quantum-plugin, cisco-plugin-exception-handling, cisco-plugin-n1k-support, nvp-qos-extension, quantum-floodlight-bigswitch-l3
21:17:00 <danwent> ok, two of those are in, (recently updated after you ran the script). two of those I need to talk to the devs about.
21:17:02 <ttx> danwent: I still fear too many reviews might distract core team from fixing key bugs
21:17:41 <ttx> but it's difficult to refuse before feature freeze ;)
21:17:47 <danwent> if core devs are following priorities, I don't think that needs to be the case.
21:17:58 <ttx> I see you have 6 "High" priority blueprints now. Progressing nicely ?
21:18:04 <danwent> yes.
21:18:17 <ttx> https://blueprints.launchpad.net/quantum/+spec/vif-plugging-improvements is marked "Implemented" but has https://review.openstack.org/19714 in progress
21:18:17 <danwent> two are not yet in review
21:18:50 <danwent> that's a bad tag in the commit message.  the core functionality is in, which is what the bps was tracking
21:19:02 <ttx> ok, will clean that up
21:19:04 <danwent> that commit you reference should really be its own bug, i will talk to akihiro
21:19:20 <ttx> danwent: do you have an assignee for auto-associate-floating-ip ?
21:19:25 <danwent> of the two 'high' that are not in review, once is expected to be posted end of this week, and another the week after that.
21:20:10 <danwent> ttx: no.  i'm going to an openstack meetup tomorrow were we will be talking about quantum and people who are looking for things to work on will supposedly be there, that is one of the items on the that "any takers?" list
21:20:19 <ttx> ok
21:20:21 <danwent> if we don't, we'll bump it (its already out of g-3, no?)
21:20:27 <danwent> ah, my mistake
21:20:42 <danwent> will remove it from g-3, but keep assigned to grizzly at least for a few more days
21:20:55 <ttx> No that would be quantum-v2-euca-compat & load-plugin-supported-extensions (still in G but not in G3)
21:21:08 <danwent> ok, changed
21:21:10 <ttx> Anything else on Quantum ?
21:21:18 <danwent> nope
21:21:35 <ttx> You seem to have your enormous goals under control. Thanks!
21:21:40 <ttx> #topic Cinder status
21:21:49 <ttx> jgriffith: hi!
21:21:55 <ttx> #link https://launchpad.net/cinder/+milestone/grizzly-3
21:22:15 <jgriffith> howdy
21:22:38 <ttx> You still have 6 blueprints that were targeted to g3 but not approved in the series goal (or prioritized) yet:
21:22:46 <ttx> huawei-volume-driver, xenapinfs-snapshots, xenapinfs-glance-integration, emc-fibre-channel-volume-driver, emc-isilon-iscsi-volume-driver, scality-volume-driver
21:22:51 <jgriffith> I think I just fixed them... try refresh?
21:23:08 <ttx> I ran my script like 5 seconds ago... maybe a cache issue
21:23:43 <ttx> Code for update-vol-metadata was merged, should it be marked Implemented now ?
21:24:20 <jgriffith> yes
21:24:37 <ttx> jgriffith: the abovementioned blueprints are still "proposed" for grizzly
21:24:51 <ttx> https://blueprints.launchpad.net/cinder/grizzly/+setgoals
21:25:13 * ttx updates update-vol-metadata
21:25:29 <jgriffith> ttx looking
21:25:40 <jgriffith> regardless, my intent is to approve them for G3 as low pri
21:25:59 <ttx> When will work start on https://blueprints.launchpad.net/cinder/+spec/local-storage-volume ?
21:26:00 <jgriffith> doh... direction versus def
21:26:20 <jgriffith> I need to check with rongze
21:26:30 <jgriffith> If he has no update tomorrow I boot it back out
21:26:40 <ttx> it's been pushed back a bit already, so if it's no longer a grizzly prio, its priority should be downgraded
21:26:46 <jgriffith> agreed
21:26:57 <ttx> btw did you come to a decision for del-vols-with-snaps ? Remove from grizzly goal ?
21:27:09 <jgriffith> I'm dropping it
21:27:18 <ttx> ok
21:27:23 <ttx> Anything more in Cinder ?
21:27:42 <jgriffith> I'll be adding a BP or two later today Aggregates and AZ's
21:27:49 <jgriffith> Other than that no, not really
21:28:05 <jgriffith> Although that could actually be a bug as opposed to a BP
21:28:18 <ttx> bugs are good too.
21:28:31 <ttx> if properly targeted/prioritized
21:28:43 <ttx> #topic Nova status
21:28:51 <ttx> vishy, russellb: o/
21:28:58 <vishy> hi
21:28:59 <ttx> #link https://launchpad.net/nova/+milestone/grizzly-3
21:29:03 <russellb> hi
21:29:10 <ttx> So before cleanup we had 46 blueprints targeted... and after we have 47 ;)
21:29:18 <ttx> Or is the cleanup still in progress ?
21:29:37 <vishy> i cleaned up the untargeted ones
21:29:43 <vishy> and untargetted a few i know won't make it
21:29:50 <russellb> i've been going through some
21:29:58 <russellb> it's still "early" enough that lots of people are still optimistic, heh
21:30:24 <russellb> man down!
21:30:37 <sdake_z> rage exit
21:30:42 <ttx> beh
21:30:51 <ttx> You have 3 blueprints targeted to g3 but not in series goal (and without priority):
21:30:58 <ttx> migrate-volume-block-migration, cpu-entitlement, multi-tenancy-aggregates
21:31:21 <ttx> looks like they should be reviewed, and series-set/prioritized if liikely
21:31:23 <vishy> i'm still going through the other ones that are definitely gone
21:31:44 <ttx> On the positive side, had a few blueprints that might be completed already:
21:31:57 <ttx> https://blueprints.launchpad.net/nova/+spec/db-session-cleanup
21:32:01 <ttx> https://blueprints.launchpad.net/nova/+spec/libvirt-spice
21:32:08 <russellb> spice is done pretty sure
21:32:12 <ttx> https://blueprints.launchpad.net/nova/+spec/direct-file-copy
21:32:14 * russellb updates
21:32:16 <ttx> https://blueprints.launchpad.net/nova/+spec/trusted-filter-cache
21:32:34 <russellb> and direct-file-copy, that's done too pretty sure ...
21:32:51 <vishy> db-session is not done
21:32:57 <vishy> trusted-filter is done
21:33:02 <ttx> the comit message on trusted-filter-cache is also pretty definitive
21:33:04 <ttx> yeah
21:33:05 <russellb> k, will update trusted filter
21:33:12 <ttx> Was also wondering about the non-started "High" priority blueprints:
21:33:34 <russellb> I tried to ping arosen earlier today on the quantum one not started
21:33:38 <russellb> no response yet
21:33:40 <ttx> but only one is left now
21:33:43 <ttx> ok
21:33:51 <ttx> might be blocked by some quantum work
21:34:00 <ttx> russellb: should rpc-based-servicegroup-driver be removed from no-db-compute deps ?
21:34:08 <russellb> ttx: yes
21:34:12 <ttx> will do
21:34:18 <russellb> thanks
21:34:28 <vishy> ttx: cleaned up the 3 without series goal
21:34:43 <vishy> russellb: i pinged him
21:34:49 <ttx> vishy: nice cleanup on https://blueprints.launchpad.net/nova/grizzly
21:34:52 <vishy> he said that he will have a merge prop next week
21:35:09 <vishy> ttx: i left https://blueprints.launchpad.net/nova/+spec/multi-boot-instance-naming
21:35:19 <russellb> vishy: k
21:35:23 <vishy> because I was hoping to try and get a volunteer to implemnt someting there
21:35:47 <ttx> sure, that's ok
21:36:08 <ttx> I think the current view represents what we know
21:36:17 <ttx> Just need to keep adjusting it over the coming weeks
21:36:26 <ttx> when we learn of stuff that won't make it
21:36:38 <ttx> Any question on Nova ?
21:37:06 <nijaba> whatś the expected date for cell completioon? g3 or before?
21:37:18 <russellb> it's really close
21:37:38 <nijaba> great!  jd__ can't wait :)
21:37:43 <ttx> yeah, i've been getting optimistic for this one. Looked like it would never make it completely, but it's really getting close now
21:37:48 <russellb> comstud said we may be able to call it done already
21:37:55 <russellb> there's always going to be some updates in the queue
21:38:11 <russellb> the stuff left is just a few additional features that aren't necessarily required IIRC
21:38:14 <ttx> That's fine, at some point we need to consider known bugs as bugs
21:38:33 <russellb> yeah, we have some cells stuff that needs to go into release notes
21:38:36 <russellb> do we have a place to start writing that stuff done?
21:38:49 <ttx> http://wiki.openstack.org/ReleaseNotes/Grizzly
21:38:56 <russellb> perfect
21:39:10 <ttx> Any other question on Nova ?
21:39:32 <ttx> #topic Horizon status
21:39:39 <ttx> gabrielhurley: hi!
21:39:44 <ttx> #link https://launchpad.net/horizon/+milestone/grizzly-3
21:39:46 <gabrielhurley> hi
21:40:02 <gabrielhurley> ahead of schedule today, eh ttx?
21:40:08 <gabrielhurley> usually it's another ten minutes
21:40:15 <ttx> I skipped keystone
21:40:16 <comstud> i think it can be considered done
21:40:25 <comstud> the patches up enable further support
21:40:27 <ttx> gabrielhurley: blame heckj, we all do
21:40:29 <gabrielhurley> comstud: I hope you're referring to keystone. ;-)
21:40:30 <comstud> and that'll be ongoing
21:40:40 <comstud> :x
21:40:46 <ttx> gabrielhurley: Plan looks good, slow progress overrall though
21:41:05 <russellb> comstud: omg, awesome, i'll update it
21:41:10 <gabrielhurley> the blueprints are distributed across a lot of people, so 10 people working slowly isn't so bad.
21:41:16 <gabrielhurley> we've had a lot of bugs fixed this week though
21:41:19 <gabrielhurley> so that's awesome
21:41:34 <ttx> Is https://blueprints.launchpad.net/horizon/+spec/file-upload-redux in good shape ?
21:41:34 <gabrielhurley> people's energy has been on those, I think
21:41:52 <gabrielhurley> davidlenwell: has his team working on it
21:42:04 <cody-somerville> I've started helping David work on file-upload-redux
21:42:04 <gabrielhurley> but he's had some delays. I'm communicating with him regularly on it
21:42:07 <gabrielhurley> he's stil lconfident
21:42:32 <ttx> good
21:42:33 <ttx> Anything more on Horizon ?
21:42:45 <gabrielhurley> not off the top of my head
21:42:48 <gabrielhurley> I'm a little scattered today
21:43:06 <ttx> heh
21:43:07 <arosen> hey russellb in progress hopefully i'll  have something soon to put on review in the next day or so.
21:43:16 <arosen> russellb: just started this morning though.
21:43:31 <ttx> arosen: could you update the blueprint status ?
21:43:42 <arosen> ttx:  sorry up let me do that now.
21:43:46 <ttx> thx!
21:43:47 <arosen> yup*
21:43:54 <ttx> #topic Keystone status
21:44:01 <ttx> dolphm_: around ?
21:44:04 <dolphm_> ttx: o/
21:44:09 <ttx> #link https://launchpad.net/keystone/+milestone/grizzly-3
21:44:15 <russellb> arosen: great thanks!
21:44:33 <ttx> dolphm_: let me check what questions I had, and if you can do anything abot it without heckj
21:45:02 <dolphm_> ttx: i just updated the status of a few bp's
21:45:17 <ttx> I saw https://blueprints.launchpad.net/keystone/+spec/replace-tenant-user-membership which was not targeted to grizzly but is being worked on
21:45:31 <ttx> I am a bit confused as to how it relates to https://blueprints.launchpad.net/keystone/+spec/trusts
21:45:49 <ttx> That's more for ayoung I guess
21:45:56 <dolphm_> ttx: i'm not the best person to explain, but it is a pre-requisite for implementing trusts
21:46:22 <dolphm_> ttx: trusts has a long line of blockers at this point
21:46:29 <ttx> dolphm_: ok, so it should be added as a dependency to trusts and added to the g3 plan
21:46:39 <ayoung> ttx, I can;'t tests trusts without it
21:46:50 <ttx> I'll try to get Joe to clarify all that
21:46:56 <ttx> dolphm: How is default-domain going so far ?
21:46:59 <ayoung> the problem is basically the v3 api needs https://blueprints.launchpad.net/keystone/+spec/replace-tenant-user-membership in order to work properly
21:47:00 <dolphm_> ttx: yes, i'm struggling with launchpad's Add Dependency feature and probably butchering it more than anything else
21:47:06 <ayoung> and trusts just kindof exposes it
21:47:28 <ttx> ayoung: yeahn should probably have series goal and target milestone set
21:47:38 <dolphm_> ttx: good progress, there's two of us working on it
21:47:51 <ttx> I see code proposed, I suspect more is coming ?
21:47:53 <dolphm_> ttx: we've got 2/4 major pieces in code review
21:48:18 <ayoung> trusts are based on the idea that you can limit the roles, and then a user gets a token with that limited set of roles.   Thus the definition of tenant membership needs to be scoped down to "the user has some role in a tenant"
21:48:34 <dolphm_> ttx: schema + data migrations, and then revising v2 API calls to assume that default domain
21:48:50 <ttx> ayoung: you also have the delegation blueprint on your plate, do you think you can complete all those ?
21:49:14 <ttx> or should we start adjusting priorities ?
21:50:47 <dolphm_> ayoung: i'd vote to bump delegation to the next milestone
21:50:56 <ttx> dolphm_: that would be H.
21:51:06 <dolphm_> ttx: correct
21:51:39 <dolphm_> trusts has more immediate utility and it's what ayoung is spending more time on, at the moment :)
21:52:00 <ttx> yeah, i'm all for realistic goals
21:52:27 <ttx> anyway, i'll try to get hold of heckj and get all those adjusted. I may show up at next keystone meeting to help
21:52:33 <dolphm_> ttx: thanks
21:52:39 <ttx> though the timing is a bit horrible for me
21:52:53 <ttx> dolphm_: any question you had ?
21:52:59 <dolphm_> ttx: nope
21:53:10 <dolphm_> (when will heckj be back?)
21:53:27 <ttx> I'll track him down with a harpoon
21:53:31 <ttx> #topic Incubated projects
21:53:36 <nijaba> o/
21:53:43 <ttx> yay Ceilometer
21:53:45 <ttx> #link https://launchpad.net/ceilometer/+milestone/grizzly-3
21:53:59 <ttx> Looks good, slow progress overrall
21:54:12 <ttx> You should probably review the 22 blueprints you have with series goal = grizzly
21:54:17 <ttx> And remove the series goal for those which won't make it
21:54:31 <nijaba> ttx: yes, but I am confident for what is targeted for g3.  less so for grizzly in general
21:54:44 <ttx> Looks like https://blueprints.launchpad.net/ceilometer/+spec/meters-discovery was completed in G2. Should I fix that for you ?
21:54:53 <ttx> (it's not targeted to grizzly-2)
21:54:58 <nijaba> ttx: will start the cleanup campaign at the next meeting
21:55:28 <nijaba> ttx: I just targeted it for g3 as g2 is not avail anymore in my pop up
21:55:48 <ttx> yes, that's because the milestone is inactive. LP subtleties, let me fix it
21:55:56 <nijaba> thanks
21:55:56 <ttx> nijaba: questions ?
21:56:01 <nijaba> nope
21:56:20 <ttx> Anyone from Heat team ?
21:56:26 <sdake_z> yup hi
21:56:41 <ttx> sdake: I heard you are going to elect a PTL...
21:56:48 <ttx> FYI if you apply for integration in the common release for H (before the end of this cycle) you'll have elections again in March like all other projects...
21:56:53 <ttx> nijaba: fixed
21:56:54 <sdake_z> yes
21:57:02 <sdake_z> thats the plan
21:57:08 <nijaba> ttx: thanks
21:57:10 <ttx> ok, just made sure you knew that :)
21:57:13 <ttx> #link https://launchpad.net/heat/+milestone/grizzly-3
21:57:25 <sdake_z> yes, not sure why ppl didn't hold an election - but can't change past:)
21:57:34 <sdake_z> this week we focused on bugs
21:57:37 <sdake_z> fixed ~10 or so
21:57:50 <ttx> Should all 'unknown' status on that page actually mean 'not started' ?
21:58:02 <sdake_z> our moniker integration was deferred because the moniker client is broken
21:58:10 <sdake_z> yup i'll adjust that thinks ttx - still learning way around launchpad
21:58:19 <sdake_z> thinks/thanks ;)
21:58:42 <sdake_z> i expect some of those work has started though
21:59:01 <sdake_z> our meeting is tomorrow 2000 UTC i'll get the states set straight then - but set to not started in the meantime
21:59:06 * ttx will remove the grizzly-3 milestone target from moniker-resource since it's deferred
21:59:23 <ttx> ok that's all I had
21:59:27 <sdake_z> i did that - series goal "none" ?
21:59:29 <ttx> sdake: questions ?
21:59:49 <ttx> sdague: the milestone was still set. That's two separate but linked concepts
21:59:51 <sdake_z> ya question about the moniker bp - series goal doesn't seem to remove it from the seriess
21:59:55 <ttx> sdake: ^
21:59:58 <sdake_z> got it thanks
22:00:16 <ttx> the problem is that to have consistent views we have to sync them a bit manually
22:00:32 <sdake_z> where is the other button located?
22:00:37 <ttx> (one is controlled by the drivers (the series goal) while the other is set by the blueprint assignee (the milestone target)
22:00:53 <ttx> Seach for "Milestone target:"
22:00:54 <sdake_z> ok got it
22:00:59 <sdake_z> yup thanks!
22:01:04 <ttx> ok, we are done
22:01:07 <ttx> Thanks!
22:01:10 <ttx> #endmeeting