21:03:59 #startmeeting 21:04:00 Meeting started Tue Nov 1 21:03:59 2011 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:04:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 21:04:08 Welcome everyone to the weekly general meeting... Today's agenda is at: 21:04:18 #link http://wiki.openstack.org/Meetings/TeamMeeting 21:04:22 So today I'd like to focus project status topics on essex-1 21:04:43 ...since we have only one week left before that milestone 21:04:44 #topic Keystone status 21:04:56 network is actually better here than at home. 21:05:05 zns: Looking at: 21:05:11 #link https://launchpad.net/keystone/+milestone/essex-1 21:05:22 zns: I'd like to review the status of the 5 blueprints in there 21:05:29 Action items from last week I think closed. Did we miss anything? 21:05:32 making sure they are all relevant to essex-1 and their status correct ? 21:05:58 zns: yes, action items were covered 21:06:01 Yes. 21:06:04 https://blueprints.launchpad.net/keystone/+spec/keystone-documentation 21:06:22 is that actually something that can be "completed" ? 21:06:40 i.e. is there a clear target ? 21:06:42 I just got off the phone with some of the team working on the docs. We are making good progress and will continue driving this to support adopters and intewgrators. 21:07:03 zns: does it make sense to target it to a specific milestone, though ? 21:07:06 I think it can be completed, but there is no clear target. 21:07:18 hmm, ok. 21:07:31 might need to push to some other milestone then 21:07:33 I believe that the cleanup and segmentation can be called completed but yes it is ongoing work 21:07:35 The intention is that we are focusing much of our energies in this milestone on it. 21:07:42 https://blueprints.launchpad.net/keystone/+spec/2-way-ssl 21:08:10 is that one close to be completed, you think ? 21:08:11 Submitted and worked on by HP. THey've done a nice job. We've validating the testing and will approve soon. 21:08:18 Code complete. 21:08:27 ok 21:08:32 https://blueprints.launchpad.net/keystone/+spec/support-multiple-credentials 21:08:46 (I'll adjust statuses where needed) 21:08:53 In progress and on track. 21:09:03 so the code should land any time now ? 21:09:10 Yes. 21:09:17 zns: ideally we would branch miletsone-proposed next Tuesday 21:09:22 https://blueprints.launchpad.net/keystone/+spec/keystone-swift-acls 21:09:32 For the previous one: https://review.openstack.org/#change,1221 21:09:38 ack 21:10:05 update, keystone swift acls will likely hit essex 2 21:10:08 On ACLs, I don't know status yet. I'll have to check with HP (unless Liem or Jason are here?) 21:10:17 ok, will adjust 21:10:17 just chimed in 21:10:22 https://blueprints.launchpad.net/keystone/+spec/database-migrations 21:10:30 jrouault: Hi! Thanks. 21:10:45 https://review.openstack.org/#change,1200 21:10:49 cool. 21:10:53 zns: Anything else ? 21:10:59 ttx: that's for database-migrations. Under review. 21:11:19 Did you make progress on the stable/diablo branch lots of people have asked for ? 21:11:34 One quick note; we've heard from people they need help with integration. Let us know or post bugs! We're here to help. 21:11:55 Raise your hand if you have questions on Keystone... 21:11:59 zns: i thought chmouel had acls working 21:11:59 zns: I'll have Mandell ping you, we've had issues 21:12:09 Also, ttx, if we want to backport bug fixes into Diablo, is there a tag or release naming convention to go by? 21:12:31 jmckenty: please do! Tx 21:12:34 zns: I'll connect you with the stable updates team 21:12:41 zns: I'm not sure of their conventions 21:12:48 ping daviey, zul or markmc 21:13:08 vishy: I'll reach out to him. 21:13:20 ok, switching to swift in 10 seconds 21:13:29 jrouault: have you connected or collaborated with chmouel? 21:13:40 no 21:13:54 You guys might be able to help each other out on swift ACLs... 21:14:07 I'll email-hook-you-up. 21:14:12 cool. 21:14:15 #topic Swift status 21:14:19 ttx: Thanks. On to swift... 21:14:22 notmyname: o/ 21:14:27 howdy 21:14:33 Looking at https://launchpad.net/swift/+milestone/1.4.4 21:14:44 If that page is current, looks like you have two things left to complete (self-destructing files and man pages) 21:14:53 Is that accurate ? 21:15:04 that page is current with the work that has been done and is currently under review 21:15:13 Any ETA for 1.4.4 based on that ? 21:15:44 nothing official. just "when it's done" or "when it's needed" 21:15:53 ok... 21:15:56 notmyname: Anything else ? 21:15:57 I think we're getting close 21:16:20 I expect to have a swift release in the next week or two (maybe three) 21:16:30 Questions on Swift ? 21:17:01 #topic Glance status 21:17:09 Looks like jaypipes is not around 21:17:16 bcwaldon: can you step up ? 21:17:21 ttx: sure 21:17:31 should be easy 21:17:33 As many of you have seen, there is an RFC out on api v2.0 21:17:42 would *love* any comments anybody has 21:17:52 it should be up to date from all of the comments already made 21:18:00 other than that, nothing to report 21:18:03 #link https://launchpad.net/glance/+milestone/essex-1 21:18:08 Your blueprints look very much on track. 21:18:16 You have a lot of targeted bugs though... Do you think they can all be fixed by next week ? 21:18:16 yep, I think we're pretty well targeted at this point 21:18:28 ttx: doubtful, I'll take a look and work with Jay 21:18:41 probably better to keep the list reasonable and doable 21:18:52 we should see some more blueprints created for the v2.0 stuff, too 21:19:11 ok. Questions on Glance ? 21:19:50 bcwaldon: better to keep that bug list down to things you *need* to fix for a milestone, rather than random targets of opportnuity 21:19:57 Ok, I'll talk to Jay 21:20:04 otherwise you keep on carrying it on from milestone to milestone 21:20:11 #topic Nova status 21:20:11 which we have been doing ;) 21:20:17 vishy: yo 21:20:28 * ttx waves at vishy physically 21:20:35 heh 21:20:38 hi 21:20:48 #link https://launchpad.net/nova/+milestone/essex-1 21:21:03 quick status check 21:21:12 https://blueprints.launchpad.net/nova/+spec/quantum-dhcp-parity 21:21:23 this one is not "accepted for essex" 21:21:54 yeah i don't recognize that one 21:22:01 that is from quantum team 21:22:02 filed that recently -- I should've filed it earlier, sorry 21:22:06 we created it kind of late.... 21:22:12 but its been done and in review for a while 21:22:15 if it comes with code it's ok :) 21:22:29 vishy: ok, could you prioritize it ? 21:22:31 yeah, code is ready for review https://review.openstack.org/#change,916 21:22:38 hopefully will raise awareness 21:22:44 got it 21:22:55 thanks guys. will do a better job of surfacing this stuff earlier in the future 21:23:05 the other 3 i nprogress looks very much on track I think 21:23:18 danwent: if you reference the blueprint in the commit message it will link automatically 21:23:24 I mean, the other "needs code review" look on track 21:23:32 In progress, in jeopardy: 21:23:37 https://blueprints.launchpad.net/nova/+spec/melange-network-info-svcs 21:23:46 vishy: will do. 21:23:52 vishy: think that one can still hit ? 21:23:57 (missing priority too) 21:24:12 ttx: we decided that it would be best to move melange to an incubated project 21:24:25 I have the todo to put that in motion. we will not merge into nova 21:24:27 yes 21:24:27 ah ? Changing every week :) 21:24:36 we had an offline discussion after last week 21:24:42 ok, will remove that one from Nova essex plans then 21:24:46 decided incubated was better since it has its own api 21:24:56 ack 21:24:59 https://blueprints.launchpad.net/nova/+spec/xenapi-sm-support 21:25:28 that one is close 21:25:39 vishy: ok 21:25:43 https://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi 21:25:50 that one has the first step proposed 21:26:01 but I don't know how much more work there is 21:26:02 xenapi-sm is here: https://review.openstack.org/#change,897 21:26:29 everyone: please mention blueprint name in commit message or topic name. Sets up the magic links 21:27:08 i think the admin api refactor will hit 21:27:17 i don't know if that will count as "complete" or not 21:27:20 #info please mention blueprint name in commit message or topic name. Autosets up the magic LP/Gerrit links 21:27:28 vishy: the bp I'm working on? 21:27:30 we'll see 21:27:34 bcwaldon: yes 21:27:52 I could see that waiting for essex-2, just because of the immense amount that needs to be done 21:27:59 vishy: did we care about the doc request for the xen volume stuff? 21:28:00 ok lets retarget then 21:28:09 ack 21:28:11 pvo: there is a separate bug and proposal for docs 21:28:23 vishy: Anything else ? 21:28:29 I saw the separate bug, but I didn't know if we'd hold the branch up for docs 21:28:33 vishy pvo two doc bugs actually since they go into different projects 21:28:38 pvo: no 21:28:44 pvo: testing is just as important 21:28:45 vishy: did the subteams pick up their respectively-assigned blueprints yet ? 21:28:55 ttx: to varying degrees 21:29:02 pvo: but we also need to hold the line against large merges with no docs at all 21:29:12 api team seems fine, network team, and block storage teams are making progress 21:29:18 orchestration is underway 21:29:28 scaling is stalled at the moment 21:29:43 vishy: I think the security team won't have anything for Essex except the rootwrap stuff 21:29:44 the other ones i haven't heard much from 21:29:57 ttx: ok, I was hoping for some planning at least 21:30:00 no code though 21:30:03 sure 21:30:12 Questions on Nova ? 21:30:53 (vishy: the idea is to produce BPs but not necessarily for Essex) 21:31:16 going for the horizon in 10 seconds 21:31:24 (and beyond) 21:31:45 #topic Horizon status 21:31:50 devcamcar: o/ 21:31:54 o/ 21:31:56 #link https://launchpad.net/horizon/+milestone/essex-1 21:32:10 You still have 6 incomplete blueprints there -- do you think they will all be complete by next week? 21:32:29 so everything is tracking well for essex-1, though the javascript unit test framework may slip: https://blueprints.launchpad.net/horizon/+spec/javascript-unit-tests 21:32:39 everything else should be there for next week 21:33:01 devcamcar: so ideally we branch to milestone-propsoed late on Tuesday evening 21:33:25 and live it there to bake for two days 21:33:35 (backporting any critical last-minute thing) 21:33:40 the 8th? 21:33:48 should be fine 21:33:55 yes. Actually I do the branching very early on the 9th 21:34:09 if you give me the goahead on the EOD before 21:34:19 sounds good 21:34:24 cool 21:34:25 only other update i have is that we are fully converted to gerrit workflow now 21:35:02 https://blueprints.launchpad.net/horizon/+spec/improve-dev-documentation is marked slow progress -- is it in jeopardy as well ? 21:35:15 or is that another of those uncompletable things ? 21:35:45 good question 21:35:50 i suppose it is a bit of an ongoing item 21:36:05 BP are good t otrack things tha tcan be completed -- but a bit wrong to tack ongoing efforts 21:36:12 track* 21:36:26 fair enough 21:36:36 I'll have to think about how to track that better 21:36:43 btw I'm working on release automation with jeblair this week so that horizon CI toolchain is ready for essex-1 21:36:58 i think i can rephrase the BP to have a specific scope 21:37:07 specific items that need documentation 21:37:33 devcamcar: the best way I found so far is to have a generic blueprint "improve doc" and then have it depend on lots of smaller, targeted efforts 21:37:45 so that you can find the relationship 21:37:53 sounds good, i'll follow that pattern 21:38:00 but still having "things that can be completed" in your essex plans 21:38:36 so onc ethe toolchain is ready we'll have tarballs generated for every commit, from trunk and milestone-proposed 21:38:53 devcamcar: I might ping you so that we can the versioning code right 21:39:04 devcamcar: will look into it soon. 21:39:08 ok 21:39:24 (basically copy what we have for nova/swift/glance) 21:39:30 if it's not there already 21:39:41 devcamcar: Anything else ? 21:39:46 nope 21:39:50 Questions on Dashboard ? 21:39:52 arh 21:39:57 on Horizon ? 21:39:58 :) 21:40:09 late renaming is difficult ! 21:40:13 for real 21:40:37 #topic Incubated projects and other Team reports 21:40:42 danwent: o/ 21:40:46 hello. 21:40:54 #info: quantum essex-1 filling out nicely: https://launchpad.net/quantum/+milestone/essex-1 21:41:04 major focus now is just reviews. 21:41:12 we need to help with two external reviews: 21:41:25 nova networking dhcp changes: https://review.openstack.org/#change,916 21:41:40 python-novaclient changes: https://github.com/rackspace/python-novaclient/pull/137 21:41:51 that is pretty much it 21:41:59 who can help wit hthat second one ? 21:42:05 danwent: Am I right in assuming Quantum will depend on Melange (if not already) ? 21:42:25 ttx: quantum can run in two modes, one that uses the traditional nova IPAM, one that uses melange 21:42:39 long-term, we will require melange as more advanced features will probably rely on melange 21:42:47 and we don't back-port them to work with old nova IPAM> 21:42:51 danwent: ok. Just trying to see how urgent it is for Melange to be proposed in incubation 21:43:05 we definitely have people using it already... 21:43:10 so sooner is better 21:43:19 yep 21:43:47 that's everything on my end, unless folks have questions 21:43:52 #help with two external reviews https://review.openstack.org/#change,916 and https://github.com/rackspace/python-novaclient/pull/137 21:44:08 Other team leads with a status report ? 21:44:22 looks like that first review has a couple dependencies as well 21:45:05 I can always reorder the commits if that becomes an issue 21:45:52 CI / doc / QA ? 21:46:15 if not, moving on 21:46:18 #topic Open discussion 21:46:25 Anything, anyone ? 21:46:26 can i replug for keystone stable branch asap 21:46:32 Was going to talk about the wiki maintenance work in Open discussion. 21:46:38 i think a lot of the frustration is because people are trying to track keystone trunk 21:46:59 (and ec2 at the very least doesn't work with keystone diablo tag) 21:47:04 vishy: we're working on it. We'll be backporting these https://bugs.launchpad.net/keystone/+bugs?field.tag=diablo-backport 21:47:08 Sent an email to the mailing list - summary is, we're testing single sign on with Launchpad IDs for the OpenStack wiki. 21:47:18 but… can you let us know what issues you are experiencing in particular? 21:47:31 vishy: we should talk to Daviey and make sure zns has everything he needs to work on that branch 21:47:57 I'd like to add a plug for installing the gerrit trival rebase hook: https://bugs.launchpad.net/openstack-ci/+bug/881184 21:47:58 Launchpad bug 881184 in openstack-ci "consider trivial rebase hook for gerrit" [Wishlist,Confirmed] 21:48:08 zns: i think the holdup is just getting the branch made in the repo and it should be editable via reviw by the backports team 21:48:12 vishy: so getting EC2 working on Diablo/stable would stop people from tracking trunk? 21:48:25 zns: that is the only show-stopping bug i know about 21:48:35 zns: otherwise it is education and perhaps some admin apis 21:48:44 vishy: OK! Good to know. Actionable data 21:48:57 there have been some comments in the openstack channel about frustration becasue they can't create and delete tenants 21:49:02 (except through keystone-manage) 21:49:45 OK. 21:49:45 bhall: will try to attract jeblair attention on it 21:49:51 * is on it * 21:49:52 zns: the main thing is having a std config and install, and people with enough expertise to be able to respond to questions 21:49:54 ttx: thanks :) 21:50:08 devstack will help in this regard i think once we have swift included in the mix 21:50:40 vishy: I read that as people with expertise available on IRC? 21:50:45 For anyone at UDS, join us for Rackspace-sponsored OpenStack-themed happy hour 21:50:49 correct 21:51:09 zns: there was a while with nova where it was just me answering the same questions over and over 21:51:11 OK. openstack-dev, right? 21:51:22 eventually there are more people that can help 21:51:27 both openstack and openstack-dev 21:51:47 zns: but the main thing is expertise in configuring it to work with everything 21:51:57 and operate it 21:52:05 as opposed to code-specific expertise 21:52:22 vishy: thank you for answering the questions! I don't want to put the onus on you, but pls feel free to reach out to me if you need help. We'll also work on bolstering our IRC presence. 21:53:01 ok, we'll close this meeting unless someone has anything to add 21:53:44 ok then 21:53:48 #endmeeting