21:02:24 #startmeeting project 21:02:25 Meeting started Tue Dec 11 21:02:24 2012 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:02:28 The meeting name has been set to 'project' 21:02:33 Agenda @ http://wiki.openstack.org/Meetings/ProjectMeeting 21:02:46 We are 10 days away from the end of the world, and 4 weeks away from grizzly-2 21:02:57 *snort* 21:02:57 #topic Swift status 21:03:04 notmyname: o/ 21:03:06 ttx: thanks 21:03:08 #link https://launchpad.net/swift/+milestone/1.7.6 21:03:22 heh. that's rather empty :-) 21:03:22 one of these two things is substantially more likely than the other... 21:03:24 List is still a bit empty, anything you want to communicate should land / be fixed in that version ? 21:03:45 I'll work on updating it this week. 1.7.6 is going to be mostly bug fixes 21:03:45 or that's still a bit early for that 21:03:54 but we do have some interesting patches (at least proposed) 21:03:55 o/ 21:04:08 * vishy requests going early since I have to leave soon 21:04:10 #action notmyname to update https://launchpad.net/swift/+milestone/1.7.6 with 1.7.6 objectives 21:04:28 in talking with some contributors, I know there are some interesting features being worked on. 21:04:28 vishy: going on the same plane as John ? 21:04:47 nope :-) 21:04:47 notmyname: Still shooting for mid-January ? 21:05:05 yes. 1.7.6 should be mid-january. no date yet 21:05:10 Sounds good. 21:05:13 Anything more on Swift ? 21:05:18 I hope to have one or 2 more releases before grizzly 21:05:21 after 1.7.6 21:05:33 but if that happens or not depends on the state of the code 21:05:33 ack 21:05:44 goal is 2 21:05:49 1.8 and 1.8.1 21:06:03 notmyname: I'll talk to you another day on the possibility to use RCs for the "final" grizzly one 21:06:04 but that's not official at all. just goals 21:06:11 ack 21:06:14 that's all I have 21:06:34 vishy: wanna go now or after general announcements ? 21:07:24 let's do general announcements first, Nova next 21:07:27 #topic General announcements 21:07:36 #info Bug squash day coming this Thursday 21:07:41 #link http://wiki.openstack.org/BugDays/20121213BugSquashing 21:07:41 k 21:07:50 o/ 21:07:53 If you're available, join the crowd on #openstack-bugsquash to help with advice/review 21:08:02 #info Nova 2012.2.2 scheduled for Thursday December 13 21:08:04 #link https://launchpad.net/nova/+milestone/2012.2.2 21:08:15 annegentle_: was the doc bug squash day any successful ? 21:08:23 markmc: Will also include the recent security fix that just landed on stable/folsom 21:08:26 yes, nearly 20 doc bugs squashed in a day 21:08:30 ttx, yep 21:08:33 now we are back porting to folsom as needed 21:08:35 #info Outreach Program for Women accepted candidates announced today 21:08:42 #link https://live.gnome.org/OutreachProgramForWomen#OpenStack 21:08:53 thanks to the stable team for backporting the nova floating ip with quantum stuff! 21:08:58 Welcome to Laura, Anita, Victora. 21:09:11 annegentle_, nice on both counts :) 21:09:12 Welcome! 21:09:20 markmc: did you analyze why automated testing didn't catch the stable/folsom regressions ? 21:09:24 annegentle_, irc nicks for them? 21:09:35 ttx, yes 21:09:39 so, 2 bugs 21:09:43 markmc: any corrective actions ? 21:09:48 https://bugs.launchpad.net/nova/folsom/+bug/1083944 21:09:56 that one came after the release 21:09:56 Anita is anteaya_i, not sure about Laura and Victoria off the top of my head. 21:09:58 Launchpad bug 1083944 in quantum/folsom "RPC exchange name defaults to 'openstack'" [Critical,In progress] 21:10:05 blog entry forthcoming, I'll include that info 21:10:16 basically, unless we were testing notification consumption in the gate, it's unlikely the gate would have caught it 21:10:25 and https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1081836 21:10:27 Launchpad bug 1081836 in nova "nova-compute (folsom) fails to start, compute_driver is None" [Undecided,Confirmed] 21:10:38 that wasn't caught because it was an issue with the default value of a config option 21:10:46 but devstack explicitly sets the value of it 21:10:59 so, no - don't really have suggestions for either 21:11:11 food for thoughts for QA folks 21:11:19 mordred, annegentle, davidkranz: Anything to report from CI/QA/Docs land ? 21:11:40 (clear 21:11:57 * annegentle_ is in training all week, off IRC mostly 21:12:10 Everyone ready to go project-specific ? 21:12:32 yes sir 21:12:33 #topic Nova status 21:12:37 vishy: o/ 21:12:42 #link https://launchpad.net/nova/+milestone/grizzly-2 21:12:46 hi 21:13:05 not that much visible progress since last week 21:13:09 Mostly due to a growing review queue, apparently ? 21:13:29 * Vek is intending to do a pile of reviews tomorrow, fyi 21:13:51 i have been too busy to do my normal 70 reviews /wk 21:13:56 i've been down on my review amounts lately, too 21:14:03 hope to have some time to get to some over the next couple weeks 21:14:13 #info Focus on review for nova-core 21:14:22 nova-compute-cells: how are we doing there ? 21:14:34 i've been sick for a week, i'm back at it today 21:14:50 reworked a lot.. mostly have tests left 21:14:53 and whatever typos i made 21:15:01 then the reviews will be updated 21:15:26 vishy/nova-core: it's your feeling that it's relatively close now ? 21:15:54 there's not been a lot of new input/comments, holding off for my latest 21:16:10 russellb: how is version-rpc-messages doing ? 21:16:20 patch is up in oslo-incubator 21:16:39 I think it's pretty close ... i need to get it running though all the nova tests too 21:16:49 ok 21:16:49 yeah, it's very close 21:16:56 In other news, I've been chasing down a number of assignees to get milestone targets from them 21:17:11 Got answers from mostof them 21:17:24 devananda mentioned that some of the DB blueprints might just not hit grizzly 21:17:35 since he is focusing on baremetal stuff now 21:17:43 boo :( 21:18:09 vishy: he is supposed to communicate that to you while bumping some off Grizzly series goal 21:18:21 sad 21:18:23 I did not get answers (or updates) at all from Phil Day and TianTian Gao 21:18:27 ok that makes sense 21:18:51 all in all fishing for updartes was successful 21:18:57 updates* 21:19:34 That's all I had on the Nova front. We need to make good progress over the next week 21:19:47 cool 21:19:59 because I expect a slowdown at the end of December, somehow 21:20:07 Any question on Nova before we move on ? 21:20:30 #action devananda to defer Db blueprints he won't have time to cover 21:20:59 #topic Oslo status 21:21:03 #link https://launchpad.net/oslo/+milestone/grizzly-2 21:21:14 markmc: Almost on track... 21:21:26 markmc: About oslo-versioning, unfortunately mordred was nowhere to be seen today 21:21:27 yep, we're looking pretty good 21:21:33 yeah 21:21:34 I'll set up a meeting with him asap 21:21:40 I'm not really letting it block me 21:21:44 #action ttx to set up a meeting with mordred and markmc to make quick progress on oslo-versioning 21:21:53 AFAICT, we have a plan and it should just work 21:22:05 so it's really down to me to push ahead with oslo-config 21:22:23 but confirming with mordred would be good 21:22:28 markmc: yeah, I just want that plan outlined so that I can tell if I'm fine with it :) 21:22:37 ttx, cool 21:22:40 markmc: aroo? 21:22:42 reading 21:22:47 here he is 21:22:51 markmc: In other news, I'm waiting on https://review.openstack.org/#/c/17672/ to start common-rootwrap 21:22:56 Would appreciate your review on that 21:23:10 ttx, yep, nova-core are slackers 21:23:10 oh wait, that's me too :( 21:23:26 markmc: yes, I believe we're in good shape in our plans - I would like to sync up with you to verify that my impl thoughts for it will work for you 21:23:31 nova-core is overwhelmed, that's what 21:23:39 mordred: maybe we can push that discussion offmeeting, just after this one ? 21:23:49 if markmc is still around 21:24:03 nah, I've got to disparu 21:24:20 mordred, quick summary ? 21:24:21 that doesn't sound right in any language 21:24:36 disparoo? 21:25:33 * ttx parallelizes -- do we have someone from keystone crew to represent ? 21:26:41 mordred: if you push your thoughts to ML right now, markmc might be able to confirm and me to read it today 21:26:59 mordred: or if it's short and quick you can do it now 21:27:42 ... ok, let's do Glance in the interlude 21:27:49 #topic Glance status 21:27:55 bcwaldon: o/ 21:28:00 ttx: hey 21:28:05 This is a chaotic agenda 21:28:09 #link https://launchpad.net/glance/+milestone/grizzly-2 21:28:21 * ttx refreshes 21:28:28 Not a lot of visible progress recently 21:28:33 unfortunately little progress lately 21:28:41 api-v2-property-protection and glance-api-v2-image-sharing are still not started ? 21:29:04 we've had a few design discussions 21:29:14 but have been blocked on external things to actually work on them 21:29:26 I'm still not worried about finishing them for g-2 21:29:36 ok 21:29:41 glance-domain-logic-layer: will it be complete once that last review lands ? 21:29:49 review @ https://review.openstack.org/#/c/17512/ 21:29:50 that's a question for markwash 21:30:13 just poked him 21:30:20 ttx: not entirely 21:30:30 bcwaldon: will you have time to make good progress by next week ? Or intend to work during the holidays ? 21:30:42 markwash: ack 21:30:47 ttx: holi-day? 21:30:58 yes I will be working ;) 21:31:01 ttx: but it is very close, only two easier patches left 21:31:16 apparently some sort of evening, lasting a bit longer 21:31:48 ok then, I don't sense panic in you yet, so probably fine 21:31:51 Anything more on Glance ? 21:32:26 not from me 21:32:40 Still no keystone folk ? dolphm, ayoung ? 21:32:46 #topic Quantum status 21:32:53 ttx I can fill in 21:32:53 danwent: hi! 21:32:55 ttx: guess you're going to have to talk to me :) 21:32:59 ayoung, cool, you're next 21:33:06 #link https://launchpad.net/quantum/+milestone/grizzly-2 21:33:23 Looks on track to me... just needs some serious review work 21:33:28 as a general update, things are moving a bit slowly, as it seems like a lot of folks have pre-holiday internal deadlines that they are trying to hit 21:33:45 yeah, we are cranking. 21:33:48 yes, key focus need to be on clearly several big reviews a week from here on out 21:34:06 quantum-db-upgrades: how is that going ? 21:34:07 overally, seems managable, as long as we don't fall off a holiday cliff :) 21:34:42 ttx: its been "about to be posted for review" for over a week now. this is one of the items stalled due to other internal projects. I'm confident mark will have it up soon. 21:34:57 ok 21:34:58 and his stuff is always super high quality when it hits the review 21:35:07 danwent: There was also this question for vishy and you about nova-network deprecation 21:35:10 so it tends to get reviewed and merged quickly. 21:35:14 on the ML @ http://lists.openstack.org/pipermail/openstack-dev/2012-December/003860.html 21:35:22 Is the idea still *not* to mark nova-net deprecated in Grizzly ? 21:35:46 ttx: yes, nova-network will be fully supported in grizzly 21:36:03 sorry, if it doesn't have quantum in the subject-line, i tend to miss things on the ML 21:36:07 danwent: ok, maybe drop a quick note on that thread 21:36:14 sure 21:36:23 danwent: yes, that's why I mention it 21:36:48 That's all I had. Anything else on Quantum, anyone ? 21:36:51 maybe i'll update my filter to include "network" :) 21:37:07 sounds risky 21:37:13 :) 21:37:32 #topic Keystone status 21:37:37 ayoung: o/ 21:37:41 Thanks for filling in 21:37:49 No problem. 21:37:52 #link https://launchpad.net/keystone/+milestone/grizzly-2 21:38:17 We had a pretty long discussion over the groups implementation earlier today. 21:38:26 #link https://blueprints.launchpad.net/keystone/+spec/user-groups 21:38:45 We should have a proof of concept/reference implementation posted shortly 21:38:50 Yeah, some progress since last week, but I'd say this is falling a bit behind due to impl discussions 21:39:01 around user-groups and trusts 21:39:13 about trusts: is that making progress ? It looks like it's still on the drawing table (which is not necessarily a bad thing) 21:39:27 but maybe that means it's more likely to land in g3 ? 21:39:35 (trying to set expectations right) 21:39:35 I think we are ok. I have an Impl of trusts, but need to rebase it on the code review... 21:39:50 #link https://review.openstack.org/#/c/17782/ 21:40:22 ayoung: so that lengthy thread converged to a solution that was acceptable for everyone ? 21:40:28 ayoung: or that covers something else ? 21:40:57 Trusts are not that hard. They are just another way to generate tokens. Getting them in required working out a circular dependency issue. I still need to get dolph's blessing. That is on the short list for this week 21:41:06 long thread? You mean about groups? 21:41:34 ayoung: the one on preauthed tokens 21:41:45 ttx, yes, we are OK with the approach 21:42:00 some quibbling over naming, but I think we are going to keep the name trusts 21:42:09 eh, ok 21:42:13 Anything more about Keystone ? 21:42:43 we still need to finish the V3 api.. 21:43:01 ayoung: is that covered by a blueprint somewhere ? 21:43:06 Oh, and the Keyring support. We are going to document clearly what the intention is with that 21:43:11 ttx, V3? Yes. 21:43:49 ayoung: not sure it appears as clearly though 21:44:09 ayoung: if you have a pointer to it, I could use that 21:44:19 ok, got to move on 21:44:24 #topic Cinder status 21:44:27 jgriffith: hi! 21:44:29 howdy 21:44:32 #link https://launchpad.net/cinder/+milestone/grizzly-2 21:44:54 getting there, expect a few more to close in the next couple of days 21:44:57 Not too bad, but not much progress since last week 21:45:03 ok, great 21:45:17 ttx: yeah, it became earily quiet after Friday :) 21:45:18 About local-storage: still no news ? 21:45:47 No... I've got that and volume_backups targetted for removal tomorrow 21:45:50 pending the cinder meeting 21:45:58 ok, sounds good 21:46:06 That's all I had for you 21:46:13 Anything more in Cinder ? 21:46:55 #topic Horizon status 21:47:00 gabrielhurley: hey 21:47:04 hi 21:47:06 #link https://launchpad.net/horizon/+milestone/grizzly-2 21:47:21 Same as others, slow progress overall 21:47:31 some progress on blueprints from me, and one bumped out (the implementor doesn't think it'll be done by the close of G2) 21:47:45 lots of good bugfixes in review, though, and only one or two new bugs 21:48:25 I'm gonna coordinate with the quantum team more closely to figure out what's happening with Quantum + Horizon in G2/G3 21:48:42 sounds good 21:48:57 If nthing else G2 may be a les feature rich but more bugfix-y milestone 21:49:07 I still have hopes that I'll be able to hack a bunch later this month 21:49:13 yes, that's a decent buglist 21:49:24 eh, I just roll the bugs I think are important from release to release 21:49:24 Anything more on Horizon ? 21:49:47 gabrielhurley: suggestion: work on them this Thursday ! 21:49:53 indeed 21:49:54 yay for bug squashing day ! 21:50:19 #topic Incubated projects 21:50:23 Anyone from Ceilometer team ? 21:50:47 stevebake: still around ? 21:50:51 yop 21:50:56 #link https://launchpad.net/heat/+milestone/grizzly-2 21:51:06 ttx.py ran cleanly 21:51:16 If I read this correctly you're feature-complete for g2 already ? 21:51:35 yes, focusing on testing, bugs, docs, packaging 21:51:35 or that's incomplete :) 21:51:41 ok, great 21:51:51 You still don't have a heat-tarball Jenkins job set up so I can't integrate you to common release management yet 21:51:58 resourcing will be messy until g-2 thanks to holidays 21:51:59 Did you push that request to the CI team ? 21:52:16 ttx: just yesterday, waiting for a review 21:52:32 stevebake: link ? 21:52:59 hmm, actually that was only for python-heatclient https://review.openstack.org/#/c/17811/ 21:53:36 I'll look into heat-tarball stuff 21:53:55 ok, don't hesitate to ping CI folk on #openstack-infra for help/guidance 21:54:07 I might have to set a milestoen code to g2 at some point to support that 21:54:17 https://blueprints.launchpad.net/heat/grizzly looks good to me 21:54:31 stevebake: your team is one of the ones with docs on the wiki, is that right? Wanted to be sure you saw the email about the wiki migration. 21:54:43 Does anyone have suggestion for first steps in getting heat into ppa:openstack-ubuntu-testing/grizzly-trunk-testing ? 21:55:05 stevebake: we can work on a "doc plan" more to get out of the wiki as you keep moving forward 21:55:14 annegentle_: yes, mostly reachable from http://wiki.openstack.org/Heat 21:55:33 that would be very much appreciated 21:55:42 stevebake: contacting jamespage would be a start. Not sure they would cover non-core stuff just yet. Do they have ceilometer in ? 21:55:54 ceilometer is in 21:56:14 * nijaba confirms 21:56:14 stevebake: ok, then I guess they could consider heat as well. Ask jamespage 21:56:25 annegentle_: I saw ceilo has some docs action happening too 21:56:38 nijaba: rady to talk Ceilometer ? 21:56:41 ready* 21:56:41 #action annegentle_ to reach out to Heat (stevebake) via email re: doc plan 21:56:43 ttx: I just got heat packaged in debian, could help 21:56:52 ttx: sure 21:56:55 #link https://launchpad.net/ceilometer/+milestone/grizzly-2 21:57:02 * jamespage hears his nick 21:57:08 Looks on track to me. Who is planning to work on provide-meter-units ? 21:57:20 guillaume pernot is on it 21:57:20 jamespage: see stevebake request above 21:57:26 ttx: ack 21:57:36 nijaba: maybe add him as assignee then 21:57:45 nijaba: Your CI jobs are now up to par afaict, ready for me to handle your g2 milestone if you wish 21:57:54 will do as soon as the bp is finished and approved 21:57:56 To do that I'll need some of your time on that milestone week, as described in: 21:58:04 #link http://wiki.openstack.org/PTLguide#Special_actions_on_Milestone_delivery_week 21:58:12 (should be no issue given that we share a timezone) 21:58:17 ack 21:58:22 I would push it after the core projects release, and ping you so that you can make the announcement yourself 21:58:34 great, thanks a lot 21:58:39 Looking at Ceilometer general grizzly plan now: 21:58:43 #link https://blueprints.launchpad.net/ceilometer/grizzly 21:59:05 Still a few "unknown" status and missing priorities 21:59:19 yes, we have been concrentrating on g2 21:59:22 Also don't forget to set the series goal to "grizzly" for stuff that is targeted (for example, multi-publisher) 21:59:38 otherwise the per-series and per-milestone views are not coherent 21:59:49 k 21:59:57 nijaba, stevebake: any quick question before we wrap up ? 22:00:03 all good 22:00:07 all good here 22:00:12 cool 22:00:15 #endmeeting