21:03:30 <ttx>#startmeeting project21:03:31 <openstack> Meeting started Tue Nov 6 21:03:30 2012 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:03:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:03:33 <openstack> The meeting name has been set to 'project'
21:03:38 <ttx> Agenda @ http://wiki.openstack.org/Meetings/ProjectMeeting
21:03:46 <ttx>#topic Actions from previous meeting21:03:52 <ttx> All done except
21:03:57 <ttx> * ttx to discuss oslo versioning with mordred and markmc
21:04:03 <ttx> We still need to have that discussion, delayed by ETOOMUCHTRAVEL
21:04:09 <markmc> oh, versioning
21:04:20 <markmc> hmm, it's not top of my list to figure out with oslo
21:04:35 <vishy> o/
21:04:36 <markmc> thinking it'll be a week or two more before it becomes really important
21:04:44 <markmc> i.e. when we go to release oslo-config
21:04:46 <ttx>markmc: still something we need to find a solution for, early enough
21:04:50 <markmc> (blocked on argparse re-write)
21:04:55 <markmc> ttx, yep, totally
21:04:56 <ttx>#topic Oslo status21:05:07 <jgriffith> 0/
21:05:13 <eglynn_> o/ (covering for nijaba on ceilo)
21:05:14 <markmc> so, I've begun the renaming from openstack-common
21:05:16 <ttx>#action markmc/ttx/mordred to discuss oslo versioning21:05:28 <markmc> project and teams created, bugs and blueprints moved over
21:05:33 <ttx>#link https://blueprints.launchpad.net/oslo/grizzly21:05:39 <markmc> I've mostly gone over the blueprints apart from ttx's latest ones
21:05:42 <markmc> which I'm sure are fine
21:05:54 <ttx> Looks like a pretty good plan... is it complete from your perspective ?
21:06:00 <markmc> last renaming task is moving openstack-common.git to oslo-incubator.git
21:06:08 <markmc> ttx, yeah, I think it's pretty complete
21:06:17 <markmc> ttx, will double check against design summit decisions
21:06:17 <ttx> Would be good to get people to indicate which milestone they intend to see their stuff drop
21:06:29 <markmc> ttx, yep, that's next on my list to chase down
21:06:33 <ttx> Looking into grizzly-1 now (which is two weeks from now)
21:06:38 <ttx>#link https://launchpad.net/oslo/+milestone/grizzly-121:06:41 <markmc>#action markmc get milestone targets for oslo blueprints21:06:46 <ttx> Only cfg-argparse is on the map, which sounds pretty conservative to me
21:07:02 <ttx> (in the good sense of conservative, I know it's election day somewhere)
21:07:03 <markmc> true
21:07:09 <markmc> and some of them are pretty much done
21:07:13 <markmc> service-infrastructure at least
21:07:37 <ttx>markmc: ok, just target the ones that are likely to hit, helps setting expectations right
21:07:40 <markmc> election day? somewhere interesting?
21:07:47 <bcwaldon> only America
21:07:54 * markmcchuckles21:07:57 <ttx>markmc: Anything you wanted to mention ?
21:07:58 <markmc> ttx, yep, will do
21:08:04 <markmc> I think that's it
21:08:08 <bcwaldon>markmc: what is 'oslo-incubator'?
21:08:08 <ttx> Questions on Oslo ?
21:08:12 <markmc> will send out an email when the renaming is complete
21:08:22 <markmc> bcwaldon, where APIs go on the way to being ready for a library release
21:08:34 <markmc> bcwaldon, https://etherpad.openstack.org/grizzly-oslo
21:08:36 <bcwaldon> okay
21:08:41 <bcwaldon> thanks
21:08:43 <markmc> bcwaldon, i.e. what the current openstack-common repo is
21:08:45 <markmc> np
21:08:48 <ttx> clarifies that it's only temporary
21:09:00 <ttx> Other questions ?
21:09:24 <ttx>#topic Keystone status21:09:29 <ttx>heckj: o/
21:09:35 <ttx>#link https://blueprints.launchpad.net/keystone/grizzly21:09:53 <heckj> getting stuff written up based on those status - just cleaned them up in the past few hours
21:09:56 <ttx>heckj: is that a complete plan from where you sit ?
21:10:07 <heckj>ttx: at this point, best estimate - yep
21:10:39 <ttx> Looking at recently-targeted grizzly-1 stuff...
21:10:52 <ttx>#link https://launchpad.net/keystone/+milestone/grizzly-121:11:09 <ttx> Sounds reasonable and on track to me
21:11:23 <ttx>heckj: anything else ?
21:11:30 <heckj> email coming soon summarizing all that
21:11:34 <ttx> awesome
21:11:40 <ttx> Questions about Keystone ?
21:12:05 <ttx>#topic Swift status21:12:10 <ttx>notmyname: hi!
21:12:12 <notmyname> hi
21:12:15 <ttx>#link https://launchpad.net/swift/+milestone/1.7.521:12:21 <ttx> Original plan was to QA-cut on November 5 and release on November 8
21:12:29 <ttx> any update on that ?
21:12:32 <notmyname> yes
21:12:56 <notmyname> I was told yesterday that the QA env was being phsically moved and therefore QA wouldn't be ready until at least tomorrow
21:13:09 <notmyname> all patches required for 1.7.5 have been merged
21:13:16 <notmyname> we may have one more land this afternoon
21:13:34 <notmyname> and the 1.7.5 release should be cut either tonight or tomorrow
21:13:54 <ttx>notmyname: ok, just ping me when I can cut milestone-proposed
21:13:54 <notmyname> tentative changelog update is https://github.com/notmyname/swift/commit/cd4ede501f7c616bf80264a9f3e1a9d9d8e99839
21:14:00 <notmyname> tons of good stuff in this release
21:14:09 <notmyname>ttx: I will let you know as soon as I know
21:14:11 <ttx> Is the milestone page reflecting the major changes in Swift 1.7.5 ? Or could it use a bit more work ?
21:14:46 <notmyname> it could probably use a bit more work, but I did spend some time on LP bugs and blueprints this morning.
21:14:52 <ttx>notmyname: Final release is still tentative to Nov 8 or should we already move it back ?
21:14:54 <notmyname> I didn't change any targeting, though
21:15:00 <notmyname>ttx: probably need to move it back
21:15:14 <ttx> Nov 9 ? Nov 12 ?
21:15:16 <notmyname> how about next tuesday (Nov 13)?
21:15:22 <ttx> Works for me
21:15:38 <ttx> we can adjust if we know better soon
21:16:01 <ttx>notmyname: anything else ?
21:16:20 <notmyname> I don't have anything else
21:16:26 <ttx> updated to Nov 13
21:16:32 <ttx> Questions on Swift ?
21:16:57 <ttx>#topic Glance status21:17:01 <ttx>bcwaldon: o/
21:17:05 <bcwaldon>ttx: hey
21:17:06 <ttx>#link https://blueprints.launchpad.net/glance/grizzly21:17:26 <ttx> Looks good to me
21:17:33 <ttx> You should set a priority to streaming-server
21:17:44 <bcwaldon> why thank you
21:17:56 <bcwaldon>ttx: I'm not sure if streaming-server will happen, but I'll figure that out this week
21:18:27 <ttx> You should still be able to say how critical it is for a successful grizzly cycle though
21:18:38 <bcwaldon> sure
21:18:42 <ttx> oh. "if"
21:18:44 <ttx> not "when"
21:18:57 <ttx> ok, sure, keep it as it is until you know
21:19:08 <ttx> In general would be good to get a better indication of what milestone each feature is likely to land
21:19:43 <ttx> i.e. grizzly-2, grizzly-3 etc
21:19:45 <ttx>#link https://launchpad.net/glance/+milestone/grizzly-121:20:01 <ttx> All implemented, anything else that will probably land in the next two weeks that we could target to grizzly-1 ?
21:20:41 <bcwaldon> possibly
21:20:51 <bcwaldon> glance-domain-logic-layer
21:20:57 <bcwaldon> I'll talk with markwash about that
21:21:02 <ttx> ok, adjust-at-will
21:21:06 <bcwaldon> ep
21:21:06 <ttx>bcwaldon: Anything else ?
21:21:14 <bcwaldon> and I just sent out my grizzly planning email that you requested
21:21:30 <bcwaldon> subject 'Glance Grizzly Planning'
21:21:31 <ttx> cool, haven't had time to read it yet, but I will soon
21:21:34 <bcwaldon> well, Planing
21:21:36 <bcwaldon> that's great
21:21:49 <ttx> Questions on Glance ?
21:22:16 <ttx>#topic Quantum status21:22:23 <danwent> o/
21:22:23 <ttx>danwent: hey
21:22:29 <ttx>#link https://blueprints.launchpad.net/quantum/grizzly21:22:40 <danwent> btw, am about to send out note to ML about quantum in grizzly
21:22:42 <ttx> yay 38 blueprints
21:22:51 <danwent> hehe… quantum team is always BP happy
21:22:54 <ttx>danwent: would be great to prioritize the "undefined priority" blueprints soon
21:23:06 <ttx>danwent: How complete is that list from your perspective ?
21:23:30 <danwent> nearly everything we covered at the summit is there, with one possible exception
21:23:44 <ttx> You have A proposed @ https://blueprints.launchpad.net/quantum/grizzly/+setgoals
21:23:48 <ttx> s/A/1/
21:24:17 <ttx> Looking into grizzly-1 targets now
21:24:23 <ttx>#link https://launchpad.net/quantum/+milestone/grizzly-121:24:24 <danwent> yeah, i actually just updated the whiteboard of that BP indicating that I didn't want to target for grizzly until i had a better understanding of what it meant
21:24:47 <ttx> OK, with two weeks left, this looks even more unlikely than usual...
21:24:53 <ttx> Feeling lucky ? Or have secret plans to start deferring stuff to grizzly-2 ?
21:25:02 <danwent> we've sunk a lot of cycles into sevice insertion + LBaaS design review
21:25:17 <danwent> work on those will start in G-1, but will definitely not land
21:25:35 <danwent> I expect about 1/3 of BPs to be deferred
21:25:43 <danwent> I'm just not sure which 1/3 :-/
21:25:43 <ttx>danwent: you can target them to g2 while starting on them on g1
21:26:06 <ttx> the idea is to give an indication on when feature land... being pessimistic is better than optimistic
21:26:08 <danwent>ttx: sure. by next meeting, they will either be likely, or moved out.
21:26:13 <ttx> ok
21:27:05 <danwent> hello?
21:27:25 <danwent> i guess i bored ttx to sleep
21:27:33 <ttx> cisco-plugin-enhancements is in grizzly-1 but not in grizzly series goal
21:27:40 <ttx> no just a script that took too long to run
21:27:47 <danwent> hehe, will clean that up.
21:27:53 <ttx>danwent: Anything else ?
21:28:09 <danwent> nope. just trying to push the team to finish talking and start coding :)
21:28:21 <ttx> Questions on Quantum ?
21:28:44 <ttx>#topic Cinder status21:28:49 <ttx>jgriffith: o/
21:28:54 <jgriffith> yo
21:28:57 <ttx>#link https://blueprints.launchpad.net/cinder/grizzly21:29:11 <jgriffith>ttx: getting there
21:29:25 <jgriffith>ttx: awaiting a few things from chuck and from the folks at HP
21:29:27 <ttx> Yes, I see. Would be great to set a priority on each of those
21:29:38 <jgriffith>ttx: yeah, I've started that
21:29:54 <jgriffith>ttx: been a bit distracted past couple days :)
21:29:57 <ttx>jgriffith: so it's almost complete as far as you can tell ?
21:30:04 <jgriffith>ttx: Yes
21:30:22 <ttx> You have two proposed at https://blueprints.launchpad.net/cinder/grizzly/+setgoals
21:30:22 <jgriffith>ttx: I don't know of any large additions coming in other than those I mentioned
21:30:37 <ttx> probably worth going through them too
21:30:45 <ttx>#link https://launchpad.net/cinder/+milestone/grizzly-121:31:04 <ttx> Not looking good with only two weeks left... and some blocked
21:31:10 <ttx>jgriffith: Could you set an explicit status on the "unknown" ones ?
21:31:22 <jgriffith> Yep, I'll update
21:31:31 <ttx> I suspect they are "not started" which makes me pessimistic :)
21:31:43 <jgriffith>ttx: non-believer!
21:31:43 <ttx>jgriffith: maybe adjust g1 goals by next week ?
21:32:18 <ttx> Also one of them is unassigned, and therefore a bit unlikely to land in this milestone
21:32:39 <ttx> (volume-type-scheduler)
21:32:44 <jgriffith>ttx: actually that one is about done
21:32:54 <ttx> ah! an unknwon almost done
21:32:56 <jgriffith>ttx: There was some flopping in who was working on it
21:33:26 <ttx> iscsi-chap and cinder-protocol-enhancements should have their series goal set to grizzly, too, if you intend to include the min the general plan
21:33:33 <jgriffith>ttx: You'll notice some of those aren't approved
21:33:48 <jgriffith>ttx: for a reason :)
21:34:08 <ttx> hmkay, maybe remove the milestone target on them so that they don't pollute your g1 roadmap then
21:34:18 <jgriffith> gotya
21:34:21 <ttx> cool
21:34:28 <ttx> it's actually not looking that bad now
21:34:33 <ttx>jgriffith: Anything else ?
21:34:51 <jgriffith> Just trying to get the gate tests to work again :)
21:34:59 <ttx> aw.
21:35:11 <markmc> was about to ask - is that all down to cinder?
21:35:16 <markmc> or just the likely culprit?
21:35:17 <ttx>jgriffith: how is that going ?
21:35:20 <jgriffith>markmc: no
21:35:29 <jgriffith>ttx: markmc I don't think it's cinder TBH
21:35:37 <ttx>markmc: it's actually a kernel issue fwiw
21:35:40 <markmc> jgriffith, ok, good to know
21:35:45 <markmc> oh
21:35:51 <jgriffith>ttx: markmc it's not that either I don't believe
21:35:52 * markmccan offer a decent kernel to try :)21:35:53 <ttx> but jgriffith is helping narrowing it down
21:35:59 <jgriffith> this is something *new*
21:36:02 <markmc> (sorry)
21:36:07 <ttx>jgriffith: a mutant ?
21:36:08 <jgriffith> and I believe it's keystone issue
21:36:22 <ttx>jgriffith: oh, it's not the thing I think it is then
21:36:29 <jgriffith> a patch was merged that was hoped to fix it, but doesn't look like it
21:36:35 <jgriffith>ttx: nope
21:36:41 <ttx>jgriffith: any bug reference where the action is happening ?
21:36:51 <jgriffith>ttx: but I have a patch in to quit messing with that stupid thing too
21:37:13 <jgriffith>ttx: Not yet, it's been more trying to get to root than anything else
21:37:34 <jgriffith>ttx: In other words not even sure what to log it against :(
21:37:41 <dolphm> https://bugs.launchpad.net/devstack/+bug/1075630 ?
21:37:43 <uvirtbot`> Launchpad bug 1075630 in devstack "Keystone 'invalid user token' on default devstack installation" [Undecided,New]
21:37:52 <ttx>jgriffith: ok, when you have a bug ref, sent it my way so that I follow progress there
21:38:08 <jgriffith>dolphm: to the rescue
21:38:14 <ttx> Other questions on Cinder ?
21:38:14 <dolphm>jgriffith: same issue?
21:38:33 <jgriffith> yep, pretty much
21:38:40 <ttx> ok cool
21:38:49 <jgriffith> but there's all sorts of interesting details in jenkins
21:39:02 <jgriffith> I should sync up with dolphm after this
21:40:14 <ttx>#topic Nova status21:40:14 <ttx>vishy: o/
21:40:14 <ttx>#link https://blueprints.launchpad.net/nova/grizzly21:40:15 <ttx>vishy: That looks quite good... is it near-complete ?
21:40:28 <ttx> oops lag again
21:40:28 <vishy> ttx yeah
21:40:51 <vishy> I suspect a few things might be missing
21:40:58 <ttx> One left @ https://blueprints.launchpad.net/nova/grizzly/+setgoals
21:41:03 <ttx> user-configurable-rbac is marked obsolete, can I remove it from list ?
21:41:19 <vishy> but there is a lot in there already
21:41:21 <vishy> yes
21:41:25 <ttx> You should encourage assignees to set a milestone target too.
21:41:45 <ttx>#link https://launchpad.net/nova/+milestone/grizzly-121:42:14 <ttx> Would be great to have updated status on grizzly-hyper-v-nova-compute
21:42:54 <ttx> About server-count-for-nova-flavors...
21:43:08 <ttx> it's se tto grizzly-1 but not formally approved for grizzly series goal
21:43:18 <ttx> you might want to fix it one way or another
21:43:29 <ttx> Otherwise this milestone looks in pretty good shape.
21:43:39 <vishy> yeah just got it
21:44:11 <ttx> Oh, and nova-v2-api-audit needs an updated status too (sdague)
21:44:29 <ttx>vishy: Anything else ?
21:44:47 <vishy>ttx: no. Update coming soon
21:44:50 <sdague>ttx: yeh, sure, I just moved to grizzly-1 today, it may be tight for that, but wanted to set myself something agressive
21:45:02 <ttx> Cool. Questions on Nova ?
21:45:30 <ttx>sdague: just set to anoything but "unknown" which means we lost contact with the assignee
21:45:38 <sdague> sure
21:45:41 <sdague> set to started
21:45:48 <ttx>sdague: thx!
21:46:05 <ttx>#topic Horizon status21:46:11 <ttx>gabrielhurley: hey
21:46:16 <ttx>#link https://blueprints.launchpad.net/horizon/grizzly21:46:18 <gabrielhurley> hey
21:46:42 <ttx> Looks good, is it complete from where you stand ?
21:47:02 <gabrielhurley> it is, as far as I know
21:47:09 <ttx>#link https://launchpad.net/horizon/+milestone/grizzly-121:47:09 <gabrielhurley> might see one or two blueprints come out fo the quantum team
21:47:14 <gabrielhurley> but that'll be at their discretion
21:47:21 <gabrielhurley> G1 is coming along
21:47:28 <gabrielhurley> I'll roll most of the bugs into the next milestone
21:47:33 <ttx>gabrielhurley: sure, that's ok, just need to reflect the current knowledge, which is sometimes hard to do after the summit :)
21:47:34 <gabrielhurley> but the high priority stuff is done
21:48:00 <ttx> Would be good to set status on define-flavor-for-project, otherwise looks on track to me
21:48:08 <gabrielhurley> 'will do
21:48:09 <ttx>gabrielhurley: anything else ?
21:48:18 <gabrielhurley> nope, just keep up the good work
21:48:19 <ttx> Questions for Horizon ?
21:48:42 <ttx>#topic Incubated projects21:48:48 <ttx> Anyone to talk Ceilometer ?
21:48:52 <eglynn_> o/
21:48:54 <jd__> o/
21:48:57 <ttx> here you are :)
21:49:04 <eglynn_> so the team is still working on distilling outputs from summit discussion into roadmap items
21:49:16 <eglynn_> and prioritizing according to needs/interests
21:49:18 <ttx> Yes, I'd recommend you start working on a Grizzly plan here
21:49:23 <ttx> Creating milestones, and targeting blueprints there
21:49:52 <ttx> We are planning on trying to be release-managed by me for G2 ?
21:49:53 <eglynn_> yep, that work is in train
21:49:54 <eglynn_>#link http://wiki.openstack.org/EfficientMetering/RoadMap21:50:00 <eglynn_> (still a WIP)
21:50:08 <eglynn_> plan is to get in train with the milestone releases by G-3, latest
21:50:27 <ttx>#action ttx to look into what's missing in CI to support integrated releases21:50:35 <ttx> (for ceilometer)
21:50:55 <ttx>eglynn_: anything else on your mind ?
21:50:56 <eglynn_> also awaiting a gerrit reboot to reflect renaming (stackforge/ceilo -> openstack/ceilo)
21:51:04 <eglynn_> IIUC to be batched up with the common -> oslo renaming
21:51:08 <ttx> right, any eta on that ?
21:51:27 <jd__> depends on -infra I guess?
21:51:34 <eglynn_> not a concrete ETA as yet
21:51:40 <ttx> sure, wondering if they gave you one
21:51:43 <fungi> any idea who in ci you were working with on that?
21:52:01 <ttx>fungi: jeblair methinks
21:52:09 <eglynn_> yep jeblair
21:52:21 <fungi> okay, i'll ping him but he's somewhat out of pocket
21:52:22 <ttx>eglynn_: anything else you wanted to mention ?
21:52:32 <eglynn_> still some unknowns we need to clarify, e.g. requirements for detailed instrumentation
21:52:41 <eglynn_> also I'm working on getting my hands around Synaps
21:52:55 <eglynn_> (a big ol' beast with some awkward dependencies)
21:53:19 <eglynn_> that's about it ...
21:53:21 <ttx> Will include Heat in that slot for next week
21:53:53 <ttx> (since it was just accepoted for incubation as well)
21:54:00 <ttx>#topic Other Team reports21:54:06 <ttx> QA, Docs, CI: anyone ?
21:54:15 <fungi> just one quick item for ci
21:54:16 * annegentle__sent my updates to the mailing list21:54:27 <fungi> annegentle__ can go first
21:55:05 <ttx>annegentle: anything to add on top of your email update ?
21:55:11 <annegentle__> nope, go ahead fungi
21:55:18 <fungi> okay
21:55:47 <fungi> mordred and jeblair just wanted me to raise visibility for the issue jgriffith was discussing above
21:56:02 <fungi> basically to note that it's resulting in some nondeterminism in the devstack gate
21:56:03 <ttx> hte keystone one, not the kernel one, right ?
21:56:09 <fungi> right
21:56:33 <ttx> yes, it's a high priority to fix that one
21:56:37 <fungi> so if volume creation results in a "ERROR: n/a (HTTP 401)" it's that issue
21:56:45 <fungi> a recheck *may* get you back on track
21:57:05 <fungi> anyway, that was all for us as far as i know
21:57:35 <ttx> jgriffith should ping us all if he's blocked on progress on that issue
21:57:47 <ttx> Any other team lead with a status report ?
21:57:55 <fungi> seems to be #link https://bugs.launchpad.net/devstack/+bug/1075630 as dolphm said earlier
21:57:56 <uvirtbot`> Launchpad bug 1075630 in devstack "Keystone 'invalid user token' on default devstack installation" [Undecided,New]
21:58:11 <ttx>#link https://bugs.launchpad.net/devstack/+bug/107563021:58:29 <ttx>#info CI borked by above bug, top prio to fix21:58:41 <ttx>#topic Open discussion21:58:46 <ttx> Anything else, anyone ?
21:59:11 * ttxwonders if with the addition of oslo and new incubated projects we should reorganize this meeting to have more time21:59:40 <ttx> maybe have release guys participate to inclubated projects meetings rather than the other way around
21:59:55 <ttx> it's getting harder to fit in one hour
22:00:37 <ttx>#action ttx to look into ways to fit all projects in the release meeting22:00:50 <eglynn_> good to have the incubated projects involved at the big boy's table tho'
22:00:56 <eglynn_> (IMO)
22:01:07 <ttx> yeah, maybe we hsould just say the meeting lasts 75 min
22:01:23 <eglynn_> yep, that could work
22:01:48 <ttx> ok well, not this time
22:01:51 <ttx>#endmeeting