21:01:41 <ttx> #startmeeting project
21:01:42 <openstack> Meeting started Tue Jan  8 21:01:41 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:45 <openstack> The meeting name has been set to 'project'
21:01:52 <ttx> Agenda @ http://wiki.openstack.org/Meetings/ProjectMeeting
21:01:58 <mordred> annegentle-itsme: I'll go dig itup
21:02:04 <ttx> #topic General announcements
21:02:13 <ttx> #info Next OpenStack Summit will happen in Portland, OR the week of April 15
21:02:17 <bcwaldon> ttx: yes
21:02:23 <ttx> yay west coast again
21:02:26 <ttx> Note that it leaves only one full week between release and summit week.
21:02:34 * heckj wishes it was Seattle
21:02:35 <danwent> ttx: yup yup
21:02:42 <ttx> tried to avoid that but wasn't very successful as you can see
21:02:44 <bcwaldon> ttx: is there a conflict with the Open Networking Summit?
21:02:51 <ttx> bcwaldon: yes
21:02:53 <bcwaldon> yay
21:02:58 <heckj> derp
21:03:14 <annegentle-itsme> spring is busy for conferences :)
21:03:18 <notmyname> yup
21:03:30 <ttx> markmc, mordred, annegentle, davidkranz: Anything to report from Stable/CI/QA/Docs land ?
21:03:35 <annegentle-itsme> o/
21:03:39 <ttx> annegentle-itsme: shoot
21:03:43 <annegentle-itsme> we held our monthly meeting this morning
21:03:46 <annegentle-itsme> #http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-01-08-13.42.html
21:03:57 <annegentle-itsme> wanted to ask about the wiki migration, should we re-plan the plan?
21:04:02 <annegentle-itsme> #link http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-01-08-13.42.html
21:04:18 <ttx> It was mentioned during the CI meeting...
21:04:31 <ttx> clarkb, mordred: ?
21:04:58 <ttx> or jeblair ?
21:05:25 <annegentle-itsme> #link http://eavesdrop.openstack.org/meetings/ci/2013/ci.2013-01-08-19.03.log.html
21:05:28 <mordred> aroo?
21:05:31 <ttx> <jeblair> so maybe we'll check back next week and see if we're at the point of scheduling a cutover date/sprint?
21:05:31 <ttx> <Ryan_Lane> sounds good
21:05:33 <annegentle-itsme> Looks like we need the updated skin for the wiki
21:05:50 <annegentle-itsme> I can send a mailing list update that we're rescheduling the cutover date
21:06:01 <annegentle-itsme> ok that was all for me
21:06:06 <ttx> annegentle-itsme: sounds safe. Coordinate with Ryan, he leads this
21:06:15 <annegentle-itsme> ttx: ok, on it
21:06:19 <jeblair> o/
21:06:38 <ttx> jeblair: is my summary of the wiki situation fair ?
21:06:44 <jeblair> ttx: lgtm
21:06:55 <ttx> Anything to add before we move to project-specific topics ?
21:07:00 <markmc> #info 2012.2.3 scheduled for January 31st
21:07:43 <ttx> #topic Oslo status
21:07:48 <ttx> #link https://launchpad.net/oslo/+milestone/grizzly-2
21:07:58 <ttx> markmc: Looking good, only oslo-config-package left
21:08:04 <ttx> And it's fine to be released post-g2 anyway... defer ?
21:08:09 <markmc> right, sadly
21:08:20 <ttx> I'll let you postpone it
21:08:22 <markmc> I should have chased down more what needs doing for that release
21:08:27 <markmc> will do that after g2
21:08:31 <ttx> We'll look at them next week, but your grizzly-3 goals look realistic given the velocity you achieved in the first two milestones
21:08:38 <markmc> and aim to have all projects switched over to it for g3
21:08:49 <ttx> Agreed. Anything else on the oslo topic ?
21:08:55 <markmc> yeah
21:09:05 <markmc> thoughts on tagging a commit at g2 release time ?
21:09:18 <markmc> i.e. if we're closing bugs as fixed in g2
21:09:28 <markmc> there should be a g2 tag to correspond to that, I guess
21:09:36 <ttx> hmm, maybe at milestone-proposed cut time
21:09:45 <ttx> that's when I move bugs to FixReleased
21:09:49 <markmc> sounds good
21:09:56 <ttx> that would be early tomorrow morning
21:10:01 <ttx> would that work for you ?
21:10:12 <markmc> yep
21:10:13 <ttx> (we wouldn't cut any branch, obviously, just the tag)
21:10:30 <markmc> I'll let you know if I think there's a late breaking issue
21:10:37 <ttx> ok
21:10:52 <ttx> markmc: anything else ?
21:11:00 <markmc> nope, thanks
21:11:03 <ttx> #topic Keystone status
21:11:07 <ttx> heckj: hi!
21:11:12 <ttx> #link https://launchpad.net/keystone/+milestone/grizzly-2
21:11:30 <ttx> All remaining are now implemented
21:11:33 <heckj> hey
21:11:40 <heckj> yep, last one merged in earlier today
21:11:46 <ttx> OK if I cut the milestone-proposed branch tomorrow morning ?
21:12:01 <heckj> yep, I believe we're ready to go for a milestone branch
21:12:12 <ttx> Cool. My main concern here is more how much was deferred
21:12:17 <ttx> Next week we'll review your G3 objectives...
21:12:24 <ttx> ...which sound a bit optimistic given the velocity you achieved in the first two milestones :)
21:12:36 <heckj> significantly more than I would have liked - we're going to have to really trim down on expected output
21:12:56 <ttx> will do that next week
21:13:03 <heckj> side note re: Keystone
21:13:07 <ttx> Anything more about Keystone ?
21:13:15 <heckj> want to welcome gyee and henrynash to keystone-core as of today
21:13:22 <ttx> yay
21:13:38 <dolphm> heckj: gyee: grats & welcome
21:13:44 <dolphm> henrynash: ^ ;)
21:14:08 <ttx> heckj: anything else ?
21:14:27 <heckj> that's the big stuff
21:14:36 <ttx> ok, thx
21:14:37 <ttx> #topic Swift status
21:14:41 <notmyname> hi
21:14:41 <ttx> notmyname: o/
21:14:45 <ttx> #link https://launchpad.net/swift/+milestone/1.7.6
21:14:54 <ttx> You still need to update that with a feature list :)
21:15:03 <notmyname> indeed
21:15:03 <ttx> Do you have a date in mind now ?
21:15:21 <notmyname> no, not yet, but I should have a better idea tomorrow after our swift meeting
21:15:27 <notmyname> which brings me to...
21:15:29 <ttx> ack
21:15:32 <notmyname> we now have a swift meeting
21:15:48 <notmyname> every other wednesday at 1900 UTC starting tomorrow
21:15:53 <notmyname> in #openstack-meeting
21:16:22 <ttx> notmyname: Also don't forget to let me know what you think of my email on the proposed RC process
21:16:32 <notmyname> ya, I've still got it flagged
21:16:33 <ttx> (from last year)
21:16:43 <ttx> Anything more on Swift ?
21:16:52 <notmyname> just the meeting. that's all I have
21:16:57 <ttx> thanks!
21:17:05 <ttx> #topic Glance status
21:17:11 <ttx> bcwaldon: o/
21:17:15 <ttx> #link https://launchpad.net/glance/+milestone/grizzly-2
21:17:19 <bcwaldon> ttx: hey
21:17:22 * ttx refreshes and prays for a miracle
21:17:36 <bcwaldon> no miracles here
21:17:39 <ttx> Nope, it still doesn't look very good. Is there anything likely to make it today ?
21:17:53 <bcwaldon> pushed off two BPs to g-3
21:18:01 <bcwaldon> I did have a chance to start multiple image locations
21:18:12 <bcwaldon> and I'm triaging open bugs right now
21:18:33 <bcwaldon> to answer your question: dont know yet
21:18:43 <ttx> should we just postpone all blueprints ? i suspect it's unlikely something will get merged before the end of the day ?
21:18:51 <bcwaldon> fair enough
21:19:03 <ttx> I'm happy to wait if you think there is a chance
21:19:05 <bcwaldon> man, the holidays really took a toll on the glance developers
21:19:16 <bcwaldon> I'll postpone them
21:19:26 <ttx> I tried to warn you but you kept on being optimistic
21:19:34 <bcwaldon> fine! I'll start being more of a jerk
21:19:42 <ttx> The glasses ARE ALL HALF-EMPTY
21:19:54 <bcwaldon> no blueprints for you
21:20:03 * ttx cries
21:20:10 <bcwaldon> I will have some bugfixes up for review today
21:20:16 <bcwaldon> don't worry about us
21:20:37 <ttx> bcwaldon: shoudl I cut milestone-proposed with the state of master tomorrow morning ?
21:20:49 <bcwaldon> sure, I'll email you with any blockers (which I don't expect to find)
21:20:53 <ttx> and then we'll backport the remaining milestone-critical issues ?
21:20:57 <ttx> ack
21:21:00 <bcwaldon> bar
21:21:36 <ttx> ..and I fear we'll have to reset goals and priorities for g3 because that will make too much
21:21:41 <ttx> (next week)
21:21:54 <bcwaldon> ok, we can chat about it
21:22:00 <bcwaldon> nothing else from me for release meeting
21:22:11 <ttx> Any question on Glance ?
21:22:48 <ttx> #topic Quantum status
21:22:53 <ttx> danwent: hi!
21:22:54 <danwent> g'day sir
21:23:00 <ttx> #link https://launchpad.net/quantum/+milestone/grizzly-2
21:23:10 <ttx> One left in review
21:23:13 <danwent> last BP is approved, just not merged
21:23:20 <danwent> in the queue for merge
21:23:26 <ttx> oh, great
21:23:41 <ttx> Then I'll cut milestone-proposed tomorrow morning, should be merged by then
21:23:43 <danwent> no known bugs that we plan to fix for G-2
21:23:59 <danwent> yes, cut away
21:24:41 <ttx> sounds good
21:24:46 <ttx> Anything else on Quantum ?
21:24:50 <danwent> not from me
21:25:19 <ttx> #topic Cinder status
21:25:24 <ttx> jgriffith: hi!
21:25:27 <ttx> #link https://launchpad.net/cinder/+milestone/grizzly-2
21:25:33 <jgriffith> yo
21:25:36 <ttx> 3 still in progress:
21:25:41 <jgriffith> :(
21:25:44 <ttx> volume-type-scheduler: https://review.openstack.org/#/c/14132/
21:25:56 <jgriffith> they're all in review
21:26:14 <jgriffith> ttx: type-scheduler is having problems getting through gating
21:26:19 <ttx> hp3par-volume-driver: https://review.openstack.org/#/c/18351/
21:26:30 <ttx> update-vol-metadata: https://review.openstack.org/#/c/19015/
21:26:36 <jgriffith> I've got a fix for him that should put him in business and get merged today/tonight
21:27:13 <ttx> OK.. let me know if for any reason I should defer cutting milestone-proposed by a few hours to let something else in
21:27:33 <ttx> by default I'll assume I can cut and should defer what's not in yet
21:27:42 <jgriffith> ttx: You're shooting what time?
21:28:02 <ttx> jgriffith: 09:00 UTC tomorrow
21:28:05 <jgriffith> ttx: K
21:28:09 <ttx> but can wait for you to get up
21:28:15 <ttx> just shoot me an email
21:28:19 <jgriffith> alright
21:28:31 <jgriffith> if they don't get reviewed they don't get reviewed
21:28:41 <ttx> but deferring is OK. You had a busy milestone already, and your G3 is not really overcrowded
21:28:55 <jgriffith> It's pride :)
21:29:22 <ttx> jgriffith: Anything else you wanted to mention ?
21:29:29 <jgriffith> no thanks
21:30:01 <ttx> jgriffith: what about your two g2-targeted bugs...
21:30:12 <ttx> bug 1083540
21:30:13 <uvirtbot> Launchpad bug 1083540 in cinder "RBD driver option rbd_user is confusing" [High,In progress] https://launchpad.net/bugs/1083540
21:30:17 <ttx> bug 1083684
21:30:18 <uvirtbot> Launchpad bug 1083684 in cinder "No api parameter validation. " [High,Incomplete] https://launchpad.net/bugs/1083684
21:30:28 <ttx> if they are not milestone-critical you should postpone them as well
21:30:39 <jgriffith> No api paramter val is invalid, I'll untarget it
21:30:51 <ttx> which makes me think...
21:30:55 <jgriffith> I haven't heard what Florian wants to do so we'll move that one out too
21:30:57 <ttx> bcwaldon: still around ?
21:31:11 <bcwaldon> ttx: yes
21:31:24 <ttx> bcwaldon: should we keep bug 1020749 on the grizzly-2 list ?
21:31:25 <uvirtbot> Launchpad bug 1020749 in glance "Use Openstack-Common notifier" [Wishlist,Triaged] https://launchpad.net/bugs/1020749
21:31:35 <ttx> i.e. do we want to backport it ?
21:31:46 <bcwaldon> ttx: already moved it to g3
21:32:12 <bcwaldon> ttx: its technical debt
21:32:20 <ttx> bcwaldon: ok
21:32:22 <ttx> thx
21:32:52 <ttx> heckj: would be good to push https://review.openstack.org/#/c/19091/ -- that's the fix for your only grizzly-2 targeted bug
21:33:03 <ttx> dolphm, keystone-core: ^
21:33:17 <ttx> Sorry about that interlude
21:33:23 <ttx> back to our regular programme
21:33:25 <dolphm> ttx: reviewing
21:33:34 <ttx> Anything more in Cinder ?
21:34:15 <ttx> #topic Nova status
21:34:20 <ttx> vishy: o/
21:34:25 <ttx> #link https://launchpad.net/nova/+milestone/grizzly-2
21:35:03 <ttx> A *lot* is under review here, let's see what could make it:
21:35:21 <ttx> vishy: around ?
21:35:54 * russellb is around too fwiw
21:36:07 <vishy> hi
21:36:09 <vishy> sorry
21:36:27 <ttx> nova-compute-cells: 9 reviews left @ https://review.openstack.org/#/q/topic:bp/nova-compute-cells,n,z
21:36:34 <ttx> I'd really have liked to complete this before G2. How close is it ?
21:36:50 <russellb> no reviews posted on almost all of those yet
21:36:59 <russellb> not likely to make it unless we rubber stamp
21:37:30 <russellb> (which i'll admit is tempting sometimes...)
21:37:40 <ttx> beh, looks like it will be deferred then
21:37:48 <ttx> vishy: ?
21:38:00 <ttx> and maybe concentrate on easier targets
21:38:02 <vishy> agreed
21:38:05 <russellb> to clarify, deadline is tonight right?
21:38:09 <vishy> the good news is the main part of the code went in
21:38:19 <vishy> so now it is just cleanup and fixes
21:38:22 <russellb> yeah, so confidence for grizzly-3 for *all* of it is very high
21:38:25 <ttx> yes, I can wait a few hours if it helps, but it seems a bit farther away
21:38:37 <russellb> vishy: some more feature bits, but smaller ... API extension and such
21:38:38 <vishy> + we decided to make it very clear that cells is experimental for grizzly
21:39:26 <ttx> ok
21:39:28 <russellb> aggregate based availability zones could make it
21:39:29 <ttx> aggregate-based-availability-zones: 2 reviews left @ https://review.openstack.org/#/q/topic:bp/aggregate-based-availability-zones,n,z
21:39:43 <russellb> 1 has been approved
21:39:48 <ttx> ok let's keep it in scope then
21:40:02 <ttx> i'd like to refine the list so that you can apply review priority on it
21:40:19 <ttx> version-rpc-messages: missing https://review.openstack.org/#/c/17965/
21:40:23 <vishy> russellb: yes I think that will make it. A competing patch broke a couple of the tests but i think jog0 will have it fixed
21:40:31 <ttx> hmmm
21:40:34 <russellb> vishy: awesome
21:40:36 <vishy> that merged
21:40:36 <jog0> working on it now
21:40:38 <russellb> version-rpc-messages should be done
21:40:53 <ttx> missing https://review.openstack.org/19229
21:41:07 <russellb> ah yes, good point
21:41:10 <russellb> has 2 +2s
21:41:19 <russellb> vishy: want to hit approved?  :)
21:41:24 <vishy> just did
21:41:28 <russellb> thx
21:41:37 <ttx> hyper-v-testing-serialization-improvements: 3 reviews left @ https://review.openstack.org/#/q/topic:bp/hyper-v-testing-serialization-improvements,n,z
21:41:45 <russellb> defer that one IMO
21:42:06 <ttx> russellb: ok, please do
21:42:12 <russellb> dansmith gave him a lot of feedback, i think he's redoing it now
21:42:17 <ttx> scope-config-opts: looks a bit far away, defer ?
21:42:18 <russellb> ttx: k, i'll do so
21:42:55 <russellb> how many patches left
21:43:03 <russellb> whiteboard says it's all up for review
21:43:09 <ttx> 18
21:43:17 <russellb> oh.  well then.
21:43:18 <russellb> :)
21:43:28 <vishy> hehe
21:43:36 <ttx> general-bare-metal-provisioning-framework: I see 5 reviews left @ https://review.openstack.org/#/q/topic:bp/general-bare-metal-provisioning-framework,n,z
21:43:43 <russellb> i set it to needs code review at least, i'll defer it
21:44:22 <ttx> with a few -1s
21:44:33 <ttx> looks like a defer to me
21:44:50 <russellb> yeah..
21:45:05 <ttx> vishy: is get-password implemented now ?
21:45:12 <russellb> deferred baremetal
21:45:35 <vishy> yes
21:45:43 <vishy> in nova at least
21:45:50 <vishy> the rest is python-novaclient
21:45:52 <vishy> :)
21:46:10 <vishy> and cloud-init
21:46:18 <ttx> The rest (quota-instance-resource, vmware-compute-driver, rebuild-for-ha, libvirt-volume-multipath-iscsi) look a bit far away. All defer ?
21:46:26 <ttx> Marking get-password implemented
21:47:01 <vishy> i think so
21:47:05 <vishy> rebuild-for-ha is close
21:47:05 <russellb> defer the rest is good with me ... i can mark them
21:47:20 <ttx> So the focus should be on "host aggregate based availability zones" for the rest of the day
21:47:47 <ttx> Unless oen of you tell me otherwise before the end of the day, i'll cut ML based off master tomorrow morning
21:48:08 <ttx> if you see something that just needs a couple hours, flag me
21:48:14 <russellb> vishy: i haven't looked at rebuild-for-ha lately, think it could make it?
21:48:23 <vishy> yes
21:48:28 <vishy> in fact most of them are going in now
21:48:29 <ttx> russellb: 6 reviews in
21:48:37 <russellb> nice, i'll leave that in g-2 then
21:48:47 <ttx> awesome
21:48:58 <ttx> Anything more on Nova ?
21:49:00 <russellb> should be all updated
21:49:06 <russellb> all implemented, 2 left needing review
21:49:19 <ttx> russellb, vishy: there are 3 g2-targeted bugs
21:49:39 <ttx> please review them and postpone any that you think we can't fix and backport by Thursday
21:49:44 <vishy> ok
21:49:54 <ttx> Thanks!
21:50:10 <ttx> #topic Horizon status
21:50:18 <ttx> gabrielhurley: still around ?
21:50:22 <gabrielhurley> yep
21:50:23 <ttx> #link https://launchpad.net/horizon/+milestone/grizzly-2
21:50:33 <ttx> 2 still in progress:
21:50:48 <gabrielhurley> File uploads is gonna be deferred
21:50:49 <ttx> don't look like they have code proposed yet ? Defer ?
21:50:50 <gabrielhurley> just talked to david
21:51:08 <gabrielhurley> the other one I may get up this afternoon, if not I'll defer along with the associated bug down in the bugs section
21:51:19 <ttx> gabrielhurley: sounds good.
21:51:20 <gabrielhurley> neither are critical as long as they're close
21:51:37 <gabrielhurley> I need to check in with a bunch of people about G3 blueprints they've committed to though
21:51:39 <ttx> Will cut MP tomorrow morning unless you raise your arms and scream
21:51:43 <gabrielhurley> sounds good
21:52:04 <ttx> yes, G3 scoping should be a fun game to play now
21:52:07 <gabrielhurley> yeah
21:52:27 <gabrielhurley> it's not looking awful since there's a broader spectrum of people assigned to the G3 blueprints
21:52:32 <ttx> last months meetings were kinda boring, but this is getting quickly more interesting
21:52:33 <gabrielhurley> but some stuff will undoubtedly go
21:52:47 <gabrielhurley> lol
21:52:48 <gabrielhurley> indeed
21:53:06 <ttx> nothing like a good cliff to raise the tension
21:53:21 <gabrielhurley> always
21:53:36 <gabrielhurley> side note:
21:53:37 <ttx> shoudl I defer the file upload thing ?
21:53:40 <gabrielhurley> oh
21:53:44 <gabrielhurley> I'll get it momentarily
21:53:56 <ttx> done
21:54:00 <ttx> Anything more on Horizon ?
21:54:03 <gabrielhurley> or that
21:54:04 <gabrielhurley> lol
21:54:05 <gabrielhurley> yeah
21:54:05 <ttx> any side note ?
21:54:06 <gabrielhurley> one thing
21:54:09 <gabrielhurley> I'd like to welcome mrunge as the newest member of horizon-core
21:54:39 <ttx> awesome
21:54:46 <gabrielhurley> that's it for me
21:54:49 <ttx> thx!
21:54:51 <ttx> #topic Incubated projects
21:54:55 <ttx> Anyone from Ceilometer team ?
21:54:56 * nijaba waves
21:55:01 <ttx> #link https://launchpad.net/ceilometer/+milestone/grizzly-2
21:55:07 <nijaba> #link https://launchpad.net/ceilometer/+milestone/grizzly-2
21:55:07 <nijaba> We have one oustanding bp, for which the review is stuck on a minor disagreement between a couple of our core devs.   I am not sure we are going to get resolution before the eod.  If that's the latest acceptable time, I'll retarget it for g3.
21:55:07 <nijaba> #link https://blueprints.launchpad.net/ceilometer/+spec/provide-meter-units
21:55:07 <nijaba> #link https://review.openstack.org/#/c/18413/
21:55:24 <ttx> sounds good
21:55:29 <ttx> OK if I cut a milestone-proposed branch for you tomorrow morning ?
21:55:37 <nijaba> ok for us
21:55:56 <nijaba> no outstnading known bugs
21:56:06 <ttx> that's all I had. We'll see if everything works when I push the big red button
21:56:12 <nijaba> :)
21:56:18 * nijaba crosses his fingers
21:56:18 <ttx> I know where to ask if it doesn't
21:56:22 <nijaba> hehe
21:56:24 <ttx> Anyone from Heat team ?
21:56:28 <sdake> yar
21:56:31 <shardy> o/
21:56:33 <ttx> #link https://launchpad.net/heat/+milestone/grizzly-2
21:56:43 <ttx> All done -- do I have your green light to cut a milestone-proposed branch from master tomorrow morning ?
21:56:50 <sdake> g2 good to go for a branch
21:56:54 <ttx> Awesome.
21:57:03 <ttx> Questions about the whole shebang ?
21:57:13 <stevebake> ttx: could we get a rundown of the release process at some point? Maybe in #heat is better
21:57:34 <ttx> sure, if we can make it quick
21:57:39 <ttx> i'll close here first
21:57:40 <sdake> ya - can guess based upon last experiences but more detail would help
21:58:06 <ttx> so if nobody has anything to add...
21:58:09 <stevebake> I suspect a lot of our old release instructions will need updating
21:58:23 <ttx> #endmeeting