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