21:00:35 #startmeeting project 21:00:36 Meeting started Tue Feb 26 21:00:35 2013 UTC. The chair is markmc. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:40 The meeting name has been set to 'project' 21:00:46 agenda @ https://wiki.openstack.org/wiki/Meetings/ProjectMeeting 21:00:51 ttx is away, so you're stuck with me 21:00:59 who do we have? 21:01:06 hey hey 21:01:14 hi 21:01:16 o/ 21:01:26 present 21:01:27 here 21:01:29 o/ 21:01:30 o/ 21:01:35 hidy 21:01:36 hi 21:01:49 danwent , gabrielhurley, sdake, nijaba ? 21:01:54 o/ 21:02:02 yo 21:02:02 #topic General announcements 21:02:05 anyone got anything interesting to share? 21:02:12 docs, QA, stable, etc. ? 21:02:46 #link https://wiki.openstack.org/wiki/GrizzlyReleaseSchedule 21:02:59 we'll start considering doing an rc1 in 3 weeks, I guess 21:03:04 time is flying by 21:03:06 note on stable, there was some breakage with unit tests in nova stable/essex ... shout out to fungi for jumping on it and having it fixed quickly :-) 21:03:07 * heckj nods 21:03:24 russellb, hmm, nice one fungi 21:03:33 ok, moving on 21:03:37 #topic Oslo status 21:03:39 hi markmc 21:03:41 hi markmc 21:03:48 #link https://launchpad.net/oslo/+milestone/grizzly-rc1 21:03:49 oh god, I see where this is going 21:04:04 looks like advanced-matchmaking isn't going to make it 21:04:11 hasn't really attracted enough reviews 21:04:18 (partly my bad) 21:04:27 ewindisch, any objection to that? 21:04:42 Obviously, I'd really like to see it through still. I've been working on zeromq docs and having that feature would make it *much* easier to configure 21:05:04 but I can't do much about others not reviewing the code :( 21:05:10 what it does have going for it is that it only risks breaking the zmq driver 21:05:17 I'll see if I can get to it this week 21:05:23 no other FFEs that I know of 21:05:33 we need to start drawing up a list of potential blockers for rc1 21:05:45 #topic Keystone status 21:05:48 heckj! 21:05:56 #link https://launchpad.net/keystone/+milestone/grizzly-rc1 21:05:58 o_O 21:06:07 trusts first 21:06:10 how goes it? 21:06:25 we're blastin' through reviews on trusts - looks like it's coming together well after a rocky week of back and forth 21:06:41 dolph and ayoung are dominating the #dev channel with back and forth onit 21:07:04 we're close 21:07:10 pluggable identity is likewise very close, doing final tweaks on code reviews mostly 21:07:17 so what's going to use trusts btw 21:07:28 Heat is the primary first consumer 21:07:29 how risky is trusts wrt regressions ? 21:07:36 heckj: ack, thx 21:07:55 markmc: it's new API and functionality that's not backwards impacting in any significant way 21:08:07 but in terms of invasiveness? 21:08:20 there's new AuthN and structures with V3 API where it's all incuded - V2 runs alongside without issue 21:08:44 the call is basically whether a feature is worthwhile enough to warrant the risk to release quality 21:08:48 markmc: there was a lot of underlying code churn getting it there, but the internal structures and APIs extended well to support it 21:08:51 ok, so sounds reasonable well self-contained 21:09:07 russellb: markmc: thanks! 21:09:08 yeah, I think so 21:09:24 ok, let's hope they can get in this week 21:09:31 any other features needing exceptions? 21:09:37 markmc: nope 21:09:46 cool 21:09:47 we've also started identifying a bunch of bugs from the dev churn and side issues that have popped out 21:09:50 blocker bugs 21:10:16 there's a few unprioritized in there 21:10:17 continuing to ID those and them we'll triage them into blocker/critical/etc. Have a couple blockers in there now, more detail as the week closes out 21:10:27 great 21:10:44 ttx reckons approx 25% of potential blockers should be fixed at this point 21:10:56 so, prolly a little behind ... but maybe aren't all real candidate blockers 21:11:02 frankly, we're probably behind - yeah 21:11:14 anything else? 21:11:22 not from me 21:11:26 thankie 21:11:33 #topic Swift status 21:11:36 hi 21:11:37 hey notmyname 21:11:42 #link https://launchpad.net/swift/+milestone/1.8.0 21:11:53 so 1.8.0 is planned to come out around the same time as grizzly rcs? 21:11:57 yes 21:12:05 and how goes it? 21:12:27 there's not much progress info on the multi-region bp or the bps it depends on 21:12:29 we've got a ton of reviews, and can always use more reviews :-) 21:12:50 actually, there is. patches have been merged and are currently under review 21:13:00 the last part (region tier) is being worked on now 21:13:27 dedicated-replication-network has reviews linked, but not the others? 21:13:46 oh adjustable-replica-counts too 21:13:55 perhaps not 21:14:00 so these are all likely to land in time? 21:14:08 that's the plan :-) 21:14:15 cool 21:14:27 identified any blocker bugs for 1.8.0 ? 21:14:55 there's a handful of high bugs 21:15:12 are some of them likely to be 1.8.0 blockers? 21:15:25 checking... 21:15:33 one of them is there since july, so I guess not 21:15:39 no critical bugs, so that's promising 21:16:08 I see 4. no worries on them 21:16:32 great 21:16:35 anything else? 21:16:39 swift questions from anyone? 21:17:04 moving along 21:17:05 thanks 21:17:10 #topic Glance status 21:17:16 bcwaldon, the man of the gold stars 21:17:20 #link https://launchpad.net/glance/+milestone/grizzly-rc1 21:17:29 3 bps not marked implemented 21:17:29 hello! 21:17:33 but they've all been merged? 21:17:36 check yourself 21:17:43 2 bps not implemented 21:17:46 both very much in progress 21:18:00 I checked all the reviews linked and they're all merged 21:18:05 what needs doing on those 2? 21:18:24 undocumented things - image sharing needs store ACls and a JSON Schema 21:18:38 multiple image locations needs to be integrated into the API - the data is already there 21:18:42 so both landing this week 21:18:49 hmm, ok 21:18:56 maybe add a not about what's remaining to the bps? 21:18:58 markwash and I went through all of the open bugs and targeted a bunch at rc1 - we could use some help tackling those 21:19:00 a note 21:19:01 markmc: sure 21:19:20 cool 21:19:24 so 5 critical? 21:19:32 how scary is the status overall? 21:19:43 looking good, that list is optimistic 21:19:50 actively working on the Critical ones 21:20:02 ok 21:20:14 so, is v2 complete after all this work? 21:20:19 or more v2 remaining in havana? 21:20:21 yep - we'll rev it to v2.1 21:20:38 ok 21:20:48 anything else? questions from the floor? 21:21:02 just a general request for help on bugs! 21:21:21 indeed :) 21:21:30 we should have said that at the start 21:21:41 everyone should be doing what they can to squash bugs at this point 21:21:46 thanks bcwaldon 21:21:48 absolutely 21:21:50 thank you 21:21:50 #topic Quantum status 21:21:56 danwent! 21:22:02 #link https://launchpad.net/quantum/+milestone/grizzly-rc1 21:22:16 2 bps in progress 21:22:17 hi 21:22:31 I can't access https://review.openstack.org/22444 21:22:35 is it marked as a draft? 21:23:06 ah, that is not the active review for the BP 21:23:10 we switched owners 21:23:19 let me make sure the right one is linked 21:23:39 https://review.openstack.org/#/c/22794/ 21:23:39 thanks 21:24:09 done 21:24:12 hmm, only uploaded yesterday 21:24:32 yeah, its actualy a very of a different branch, which is no longer active 21:24:40 seems like a pretty big new feature 21:24:47 does it really need to be rushed in? 21:25:07 that's what i'm talking to mark mcclain about. 21:25:10 its entirely self-contained 21:25:25 so the risk is more about resources being distracted from solidifying + bug fixes 21:25:49 ok 21:25:56 we've actually cut the patch down by about 3x 21:26:12 the original version in G-3 was huge and too much for us to handle in grizzly 21:26:14 it depends on https://review.openstack.org/22279 - is that also self-contained? 21:26:40 yes, those are changes to previous loadbalancer patches that went in 21:26:52 ok 21:26:53 basically, loadbalancer API and DB were merged in G-1 & G-2 21:27:05 G-3 was supposed to do the driver portion of it, but was too big. 21:27:13 so hope is to have it merged for next week? 21:27:15 so we've tried to pare it down to its most base components 21:27:22 hope is to have it in two days actually 21:27:27 ok, great 21:27:31 how about quantum-scheduler? 21:27:39 if we even get close to next week, i'll drop it like a bad habit 21:27:56 mainly b/c i want the resources focused more on bug fixes 21:28:11 quantum-scheduler or lbaas agent? 21:28:12 but this is a grizzly deliverable that is important to many people, so i want to give them a fair chance. 21:28:13 or both 21:28:15 both 21:28:28 ok, sounds good 21:28:32 bugs, then 21:28:37 that's a big list, but a bunch fixed 21:28:40 nice work 21:28:49 anything you're particularly concerned about? 21:28:55 yeah, there are a lot of people on the team focused entirely on bugs already 21:29:02 that's great 21:29:09 we're targeting an early RC1, on March 12th 21:29:21 which is focusing minds 21:29:40 no major worries, other than the fact that the two FFEs are done yet 21:29:47 are not 21:30:02 ok, great 21:30:06 anything else? questions from anyone? 21:30:26 not from me 21:30:28 thanks danwent 21:30:34 #topic Cinder status 21:30:34 later 21:30:38 #link https://launchpad.net/cinder/+milestone/grizzly-rc1 21:30:41 hey jgriffith 21:30:42 :) 21:30:54 the only bp seems to be about docs 21:31:01 Yup 21:31:06 We had no exceptions 21:31:06 which probably technically doesn't need tracking as a FFE, right? 21:31:08 cool 21:31:11 correct 21:31:14 I'll remove it 21:31:15 and one poor lonely bug 21:31:27 haha.. yeah, but that's going to be growing shortly 21:31:39 anything you're particularly concerned about? 21:31:57 gate stuff, nothing identified specific in Cinder yet though 21:32:06 gate stuff? 21:32:19 High count of screen with no data init 21:32:27 or no screen process launched at all 21:32:37 uggh 21:32:46 is there a bug filed? 21:32:56 Yeah 21:33:08 take me a moment to find it again though 21:33:16 ok 21:33:24 so, no critical bugs, a bunch high 21:33:28 15 triaged 21:33:35 seems like you're in pretty reasonable shape? 21:33:47 15 untriaged, rather 21:33:57 Yeah, I need to go through and clean triaging up tonight/tomorrow 21:34:03 Should be in good shape though 21:34:12 anything else? questions? 21:34:15 TBH Cinder's biggest problem is going to be docs if we don't get it addressed soon 21:34:18 Nope 21:34:23 OH! 21:34:25 yes... 21:34:36 one other thing... back to my email about unit tests 21:34:47 The cinder unit tests are horribly broken 21:34:54 when trying to run in a venv 21:35:03 The version code doesn't work 21:35:22 hmm, the latest version code from oslo? 21:35:25 got a link to a bug? 21:35:36 you can probably corner mordred into helping 21:35:39 yeah... 21:35:44 uhoh 21:36:01 ok, moving along to nova 21:36:01 markmc: it's unable to find the version string 21:36:04 mordred: knows :) 21:36:09 jgriffith, happy to look at a traceback or whatever 21:36:12 jgriffith: I don't believe you - but I'm happy to help figure it out :) 21:36:18 #topic Nova status 21:36:24 markmc: I'll send one your way in a bit 21:36:24 #link https://launchpad.net/nova/+milestone/grizzly-rc1 21:36:27 vishy 21:36:29 mordred: :) 21:36:49 4 bps not completed 21:37:01 backportable-db-migrations ... Beta available :) 21:37:10 hi 21:37:26 how goes it? 21:37:40 oh, nothing needed for backportable-db-migrations 21:37:41 got it 21:37:42 yeah 21:37:43 nova-api-samples? 21:37:57 waiting to make sure more dbs aren't needed 21:38:00 lots of reviews, questions is when do we say it's done? 21:38:24 ideally when all extensions are covered 21:38:33 doesn't seem like adding more api-samples is a quality risk, I guess 21:38:40 i think there are 3 under review for api-samples 21:38:58 migration-testing-with-data ? 21:39:12 https://blueprints.launchpad.net/nova/+spec/server-count-for-nova-flavors shouldn't be targetted 21:39:18 there's a list in the code of extensions without tests, master just shows 2 21:39:18 migration testing should be close 21:39:22 sdague: ^^ 21:40:01 yeah, was about to say - russellb nixed server-count-for-nova-flavors 21:40:06 #openstack-101 21:40:14 ok, so the only bps open are about testing basically 21:40:26 more tests probably don't need a FFE 21:40:45 any features under review not on the grizzly-rc1 list? 21:41:39 not that i have seen 21:41:44 same 21:41:46 ok 21:41:48 bugs ... 21:41:58 big list, but only one critical and a bunch already fixed 21:42:02 looks promising 21:42:14 there are 3 other critical bugs, not targeted to rc1 21:42:18 I'm getting back to this one with quotas 21:42:23 not really critical, or should be targeted? 21:42:37 comstud, https://bugs.launchpad.net/nova/+bug/1098380 ? 21:42:38 Launchpad bug 1098380 in nova "Quotas showing in use when no VMs are running" [Critical,In progress] 21:42:39 #link https://bugs.launchpad.net/nova/+bug/1098380 21:42:40 Yeah 21:42:45 i'm just going through triaging and targetting today 21:42:47 I'll be working on that the next couple of days 21:42:52 so there are probably a bunch of unassigned ones 21:43:05 i'm just putting everything that seems like it is worth fixing on the list 21:43:17 only 26 untriaged, w00t! 21:43:21 nice work guys 21:43:37 looks in pretty good shape 21:43:42 anything else to be concerned about? 21:43:52 we have a bunch of untriaged in python-novaclient 21:44:20 indeed 21:44:37 different release cycle, though, so I guess slightly different concern 21:44:40 and we have a whole bunch of open bugs that are not in progress 21:44:54 which it would be nice to knock down 21:44:56 604, wow 21:45:11 is there a bug squashing day scheduled? 21:45:41 anything else? questions from folks on nova? 21:45:41 we should have bug squash fridays until RC, heh 21:45:56 russellb, sounds like a nice idea 21:46:05 casual nickname and bug squash Friday 21:46:12 yes! 21:46:22 * markmc doesn't approve of casual nick friday 21:46:27 lol 21:46:29 because rustlebee always wins 21:46:29 rustlebee gonna sting some bugs 21:46:38 meh, moving along 21:46:40 thanks guys :) 21:46:52 #topic Horizon status 21:47:02 gabrielhurley ... you get to wait an awful long time :( 21:47:08 yo 21:47:12 that I do 21:47:12 #link https://launchpad.net/horizon/+milestone/grizzly-rc1 21:47:33 quantum-lbaas still under review 21:47:42 is it likely to make it? 21:47:46 yep, that one's entirely dependent on the quantum team 21:47:59 if they land the LBaaS stuff and sort it all out then this goes in too 21:48:14 sounded like they were confident during their section earlier 21:48:14 ok, got it 21:48:23 they're hoping to merge it in the next couple of days 21:48:26 so that all sounds good 21:48:35 no other features wanting to creep in ? 21:48:58 nope, none 21:49:06 bugs ... nice list 21:49:10 and the bugs list is currently short 21:49:13 will grow some I'm sure 21:49:16 but nothing too abd 21:49:19 *bad 21:49:26 ok, 15 is short for horizon at this point? 21:49:34 confident of getting them all fixed? 21:49:43 nothing marked critical there, so that's reassuring 21:50:09 yep 21:50:15 many/most are already under code review 21:50:21 great 21:50:28 anything else? questions from anyone? 21:50:47 thanks gabrielhurley 21:50:53 #topic Incubated projects status 21:51:02 sdake, nijaba - fight for who goes first :) 21:51:09 hi 21:51:22 cool 21:51:26 #link https://launchpad.net/heat/+milestone/grizzly-rc1 21:51:32 no FFEs, great 21:51:41 bugs being worked on 21:51:42 30 bugs, but a whole bunch fixed already 21:51:59 going to do a group triage wednesday on remaining open bugs 21:52:06 see if any can be bounced 21:52:10 cool 21:52:19 the only critical one is https://bugs.launchpad.net/heat/grizzly/+bug/1072949 21:52:20 Launchpad bug 1072949 in heat/grizzly "Reset DB migrations" [Critical,Triaged] 21:52:32 you're dropping folsom->grizzly DB upgrade ? 21:52:48 i think the intent was for zane to send a message to the list and see if people care 21:52:53 but ya drop upgrade 21:52:57 ok, that's probably fair 21:53:03 since folsom requires oslo-config 21:53:08 makes hard to use on folsom in any regard 21:53:17 sorry since heat requires oslo-config 21:53:25 and it will get worse as time passes with more modules 21:53:38 hmm, no - that's not what I was getting at 21:53:51 people won't be able to take their DB from folsom-era heat and migrate it to grizzly? 21:54:01 separate from using grizzly heat with folsom openstack 21:54:09 what we do in nova to stop migrations building up is to compact them after release 21:54:12 your correct got those mixed up 21:54:24 markmc that was discussed in our meeting last week (compacting) 21:54:25 and only support e.g. folsom->grizzly upgrade 21:54:28 not essex->grizzly 21:54:36 i'll find out more about what zaneb is planning there 21:54:40 coolness 21:54:46 looks like you're in good shape, anyway 21:54:50 anything else? 21:54:56 congrats again on graduation 21:55:01 nope we are in good shape thanks for the congrats :) 21:55:15 cool 21:55:18 nijaba! 21:55:25 #link https://launchpad.net/ceilometer/+milestone/grizzly-rc1 21:55:50 hbase-storage-backend and publisher-counters-frequency seem like the FFEs 21:56:04 rpc-qpid seems to be about tests? 21:56:27 no nijaba 21:56:36 how about dhellmann, eglynn, jd__ ? 21:57:05 if the qpid thing is about unit tests, qpid is in pypi now 21:57:13 russellb, saw that, nice one 21:57:33 russellb forked qpid! 21:57:33 markmc: and handed over to the qpid project 21:57:38 * markmc gets on the twatter about that 21:57:50 i did! for a day or less 21:58:03 qpid folks took it over quickly once I told them about it :-p 21:58:07 heh 21:58:14 ok, no ceilometer folks :( 21:58:29 only 1 critical bug about the nova notifier 21:58:43 which it sounds like dhellmann has a plan for 21:58:46 ok, moving along 21:58:51 #topic Any Other Business 21:58:57 questions, comments, whatever? 21:59:13 Point of order - ttx shouldn't be allowed vacations 21:59:35 markmc: question you know when the results of talks will be up ? 21:59:49