21:02:53 <ttx> #startmeeting
21:02:54 <openstack> Meeting started Tue Jul 31 21:02:53 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:56 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:03:05 <ttx> Agenda @ http://wiki.openstack.org/Meetings/ProjectMeeting
21:03:17 <ttx> #info Two weeks left for Folsom features! Propose code now or it will wait for Grizzly.
21:03:28 <ttx> #topic Actions from previous meeting
21:03:38 <ttx> * notmyname to retroactively create some blueprints to cover 1.6.0 main features: DONE
21:03:46 <ttx> * vishy to defer trusted messaging and user configurable rbac to Grizzly: DONE
21:03:58 <vishy> o/
21:04:00 <ttx> * gabrielhurley/devcamcar to clarify droppage of ext-roles due to lack of RBAC support
21:04:07 <ttx> gabrielhurley: Now marked "Slow progress", so it's still relevant ?
21:04:14 <gabrielhurley> ttx: it is still relevant, yes
21:04:19 <ttx> but unlikely.
21:04:32 <gabrielhurley> ttx: it's a stretch goal, but we're working on it
21:04:43 <ttx> gabrielhurley: ok, thx
21:04:45 <gabrielhurley> ttx: it's actually not hard for horizon, it's just dependent on keystone
21:04:46 <ttx> * ttx to confirm green light to nova and keystone 2012.1.2
21:04:59 <ttx> ...let's discuss that in the next topic.
21:05:27 <bcwaldon> ttx: here
21:05:31 <ttx> gabrielhurley: anything specific you are waiting on in Keystone ?
21:05:44 <gabrielhurley> ttx: like you said, we can discuss that during the keystone topic ;-)
21:06:05 <ttx> Well, I was actually speaking of 2012.1.2, but let's do that yes
21:06:11 <ttx> #topic 2012.1.2 stable release
21:06:41 <ttx> markmc: So we are now aiming for August 9 for 2012.1.2 ?
21:07:04 <markmc> ttx, yes, pushing out by a week because of a fix in the pipeline
21:07:15 <ttx> Does that mean there is still room for more last-minute fix backports in Keystone/Nova ?
21:07:21 <markmc> ttx, still looking good, had a nice bunch of nova fixes
21:07:22 <ttx> or you'd rather not ?
21:07:36 <markmc> happy to take some more, looks like there's some in the queue for keystone
21:07:50 <heckj> markmc: yeah, apevec has been busy there
21:07:51 <markmc> haven't re-checked horizon and glance since last week
21:08:08 <ttx> sounds good. Anything more on that topic ?
21:08:13 <markmc> not from me
21:09:10 <ttx> #topic Keystone status
21:09:14 <ttx> heckj: o/
21:09:18 <ttx> #link https://launchpad.net/keystone/+milestone/folsom-3
21:09:32 <heckj> (refresh if you haven't recently)
21:09:32 <ttx> heckj: Not much visible progress since last week ?
21:09:39 * ttx refreshes
21:09:44 <heckj> PKI getting landed and bugs on it
21:09:54 <heckj> Some no-progress elements removed from F3 milestone goals
21:10:04 <ttx> VERY recently :)
21:10:20 <heckj> that's why I suggested you refresh. Wanted to be more like bcwaldon
21:10:40 <ttx> He's alreday tainting you, I see
21:11:04 <bcwaldon> AoE
21:11:17 <ttx> Looks good now
21:11:27 <ttx> heckj: Quick priority sanity-check: Can you confirm you're fine with deferring to Grizzly all those features if they are not merged in by August 14 ?
21:11:58 <heckj> ttx: I really wanted to get more done, but yeah - I'd prefer stability and consistency over last-minute change to just shove something in the door
21:12:16 <ttx> right, obviously all the "High" are very much wanted
21:12:29 <heckj> still hoping to have parts of the V3 API stubbed out and "draft" or "beta" available for F3
21:12:48 <heckj> yep
21:12:52 <ttx> heckj: anything else ?
21:13:03 <heckj> not from me - question time
21:13:05 <ttx> gabrielhurley: what is it you're depending on in Keystone ?
21:13:09 <gabrielhurley> ttx: perhaps heckj can comment on his thinking about the policy consolidation and CRUD in keystone (which is the main dependency for horizon's RBAC blueprint)
21:13:21 <ttx> gabrielhurley: perhaps he can.
21:13:23 <gabrielhurley> (he and I have spoken about it, but probably best to share...)
21:13:52 <heckj> There's a slow-progress blueprint about consolidating all the various policy.json files and suggesting a best-practice/small-deployment setup for those and assocaited roles.
21:14:14 <heckj> That's really the key piece there - just getting some intended consistency to deployments
21:14:29 <heckj> there's also some V3 API around letting keystone host those policy files,
21:14:50 <gabrielhurley> if there's consistency and we an API to query the policy, then horizon has trivial work to do to support it in the UI
21:14:51 <heckj> but that's after we get a basic around the roles across projects, etc.
21:15:49 <ttx> gabrielhurley: you'd need document-deployment-suggestions-policy complete ASAP to be unblocked ?
21:15:58 <heckj> that's the gist of it all - horizon's UI would require the V3 Policy crud API and conventions around how to read those files
21:16:08 <gabrielhurley> ^^^that
21:16:08 <uvirtbot> gabrielhurley: Error: "^^that" is not a valid command.
21:16:17 * heckj loves the uvirtbot
21:16:21 <gabrielhurley> lol
21:16:29 <gabrielhurley> if it all falls through we haven't lost much... we're just still stuck with the two roles (admin and member)
21:16:55 <ttx> heckj: do you think it would be reasonable for Horizon to use a part of the V3 API ?
21:17:51 <heckj> that portion, yes - it's totally new and independent of the other API elements
21:17:55 <ttx> OK. Other questions about Keystone ?
21:17:58 <gabrielhurley> ttx heckj: since I thoroughly vetted the v3 API I'm pretty comfortable with using it, particularly that bit. we can adjust over time if necessary.
21:18:31 <ttx> #topic Swift status
21:18:37 <ttx> #link https://launchpad.net/swift/+milestone/1.6.0
21:18:42 <ttx> notmyname: hey
21:18:47 <notmyname> howdy
21:18:49 <ttx> 1.6.0 still being QA'ed ?
21:19:01 <notmyname> ya
21:19:29 <ttx> notmyname: more fixes coming up, or just more time to complete the QA round ?
21:20:00 <notmyname> there was a slow start to getting them tested, and a couple of issues came up. so both :-)
21:20:22 <ttx> notmyname: OK. just push the Final=True thing onto milestone-proposed when you're fine with it
21:20:28 <notmyname> I will
21:20:29 <ttx> It will be our secret signal
21:20:35 <notmyname> don't tell
21:21:13 <ttx> notmyname: ideally the bugs we are waiting on should be visible on the milestone page (targeted to 1.6.0)
21:21:25 <ttx> so that everyone knows what we are blocking on
21:21:41 <ttx> notmyname: anything else ?
21:21:56 <notmyname> the page is up to date. the most recent was actually a regression. it broke old functionality (the bug would be "everything is the same as it was")
21:22:38 <ttx> Ack. Questions on Swift ?
21:22:38 <notmyname> there are no known blockers right now. simply waiting for QA to be done
21:23:21 <ttx> #topic Glance status
21:23:28 <ttx> bcwaldon: o/
21:23:32 <ttx> #link https://launchpad.net/glance/+milestone/folsom-3
21:23:36 * ttx refreshes
21:23:40 <bcwaldon> hey
21:24:00 <ttx> Good progress overall, still a bit worried about essential stuff...
21:24:08 <bcwaldon> you don't trust me!?
21:24:14 <ttx> bcwaldon: When worried I go from being a weekly PITA to being a daily PITA :P
21:24:29 <ttx> Let's see where we stand...
21:24:35 <ttx> * https://blueprints.launchpad.net/glance/+spec/api-v2-store-access
21:24:50 <ttx> Still not started ? But short enough ?
21:25:07 <bcwaldon> I have someone who will do it over the next week
21:25:12 <bcwaldon> if its not done, I'm gonna do it
21:25:41 <ttx> heh
21:25:56 <bcwaldon> thats how a lot of things get done
21:26:09 <bcwaldon> markwash has been super helpful in the v2 implementation
21:26:11 <ttx> if not done next week, that will just leave you with the weekend to do it :)
21:26:17 <bcwaldon> and he's wrapping up his remaining blueprints as we speak
21:26:29 <bcwaldon> ttx: thats enough time, I just have other things to do right now
21:26:56 <ttx> So api-v2-links is close to completion once part 1 is merged ?
21:27:11 <bcwaldon> ttx: I think the review up now is all that needs to be done
21:27:21 <ttx> OK, so that leaves us with https://blueprints.launchpad.net/glance/+spec/separate-client
21:27:32 <ttx> Blocked on https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient and https://blueprints.launchpad.net/python-glanceclient/+spec/glance-client-parity
21:27:48 <bcwaldon> yep, I have code for integrate-python-glanceclient
21:27:54 <bcwaldon> got that working last night
21:27:59 <ttx> vishy: OK to raise priority of integrate-python-glanceclient to "Essential" to match ?
21:28:20 <bcwaldon> and glance-client parity has one thing left - porting ssl code from legacy client
21:28:27 <vishy> sure
21:28:44 <bcwaldon> which someone else could do!
21:29:54 <ttx> #help Volunteer needed to port ssl code from legacy client in glance-client-parity
21:30:19 <ttx> Needed for some Folsom-essential stuff ^
21:30:41 <ttx> bcwaldon: About https://blueprints.launchpad.net/glance/+spec/api-v2-property-protection -- is that part of the API v2 stuff ? Should that be Essential ?
21:30:46 <bcwaldon> sounds like someone who cares about using glanceclient over ssl could step up
21:31:08 <bcwaldon> ttx: we might get a really dumb version of that implemented, but it might get bumped to grizzly
21:31:29 <ttx> (it's also a good occasion to focus on something that is important for the release success, rather than some pet itch)
21:31:47 <ttx> bcwaldon: so it's not an integral part of API v2 ?
21:31:56 <bcwaldon> ttx: no, its a nice-to-have
21:32:13 <bcwaldon> ttx: its something that will make the v2 api more powerful, but its a behind-the-scenes feature
21:32:20 <bcwaldon> its not built into the spec
21:32:26 <ttx> bcwaldon: last question, apart from the already-marked-Essential stuff, you're fine with deferring to Grizzly anything not merged by Aug 14 ?
21:32:56 <bcwaldon> ttx: I want to make sure dprince's tenant-specific storage stuff gets in
21:32:56 <ttx> just checking we are not forgetting some essential stuff.
21:33:01 <bcwaldon> ttx: he has code in review already
21:33:10 <bcwaldon> ttx: I hope to get those in shortly
21:33:55 <ttx> bcwaldon: should we set that to Essential to reflect that you'd not release folsom without it ?
21:34:28 <bcwaldon> ttx: yes
21:34:34 <ttx> bcwaldon: will do. Anything else ?
21:34:52 <bcwaldon> ttx: I'll go over it again but nothing to bring up now
21:34:59 <ttx> Questions on Glance ?
21:35:26 <ttx> #topic Quantum status
21:35:29 <ttx> danwent: yo
21:35:31 <danwent> hi
21:35:32 <ttx> #link https://launchpad.net/quantum/+milestone/folsom-3
21:35:43 <ttx> Good progress on High/Essential stuff... let's see the Essential ones in more detail
21:35:49 <ttx> * https://blueprints.launchpad.net/quantum/+spec/provider-networks
21:35:55 <ttx> One more small part still needed, right ?
21:35:58 <danwent> been promised a review by monday
21:36:04 <danwent> yes, patch 3 of 4
21:36:10 <danwent> or rather, 4 of 4
21:36:16 <danwent> 3 of 4 are in
21:36:19 <ttx> * https://blueprints.launchpad.net/quantum/+spec/quantum-v2-public-networks
21:36:25 <ttx> Code proposed at https://review.openstack.org/#/c/9845/, could benefit from some reviewing activity ?
21:37:09 <danwent> its actually been through a decent amount of review, given that salvatore puts together good code to start with
21:37:20 <danwent> but one of the two core devs reviewing the patch is now on vacation, so we need to find another one
21:37:30 <ttx> * https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat
21:37:37 <ttx> Status on that ?
21:37:41 <danwent> finally making good progress on that.
21:37:49 <danwent> have committed to a review by monday
21:37:49 <ttx> You mentioned splitting that one in two, did you abandon the idea ?
21:37:57 <danwent> am hoping to have a WIP done sooner than that.
21:38:17 <danwent> I'm actually going to do the bulk of it myself, but slice a few pieces off.
21:38:25 <danwent> nati_ueno also will be helping
21:38:52 <ttx> ok, looks like we should be mostly set in a week
21:38:58 <ttx> (for the essential stuff)
21:39:09 <ttx> Do you agree to un-folsom3-target the (unassigned) expose-dhcp-server-ip and api-rate-limiting ?
21:39:10 <danwent> yeah, essential and high should all be in for review by tuesday
21:39:20 <ttx> Will still be in folsom map but out of F3 since nobody is signed up yet for them
21:39:27 <danwent> expose-dhcp-server-ip is trivial, and i'm going to try and hand it to someone
21:39:32 <danwent> very small patch
21:39:38 <danwent> rate-limiting will be bumped
21:39:44 <ttx> ok
21:39:45 <danwent> i'm also planning on moving anything in slow progress out as well
21:39:58 <ttx> Same priority-sanity-check, apart from the stuff marked Essential, you're fine with deferring to Grizzly anything that doesn't make it to master by Aug 14 ?
21:40:28 <danwent> feature-wise, yes
21:40:31 <ttx> danwent: Anything else ?
21:40:41 <ttx> Questions on Quantum ?
21:40:56 <danwent> i'm a bit worried we may have an 'oh crap' of something possible in nova network that we didn't handle in quantum, but i've done my best to cover the core use cases.
21:41:26 <danwent> btw, multi-host stuff probably won't make it unless someone steps up.
21:41:26 <ttx> danwent: we could cover them as bugs/exceptions if they are not too intrusive
21:41:35 <danwent> ttx: ok.
21:41:59 <ttx> #topic Cinder status
21:42:05 <ttx> jgriffith: around ?
21:42:36 <ttx> Hmm, let's do Nova first
21:42:41 <ttx> #topic Nova status
21:42:46 <ttx> vishy: hey
21:42:55 <vishy> hi
21:42:56 <ttx> #link https://launchpad.net/nova/+milestone/folsom-3
21:43:07 <ttx> Let's see progress on essential stuff:
21:43:23 <ttx> * https://blueprints.launchpad.net/nova/+spec/general-host-aggregates (jog0)
21:43:34 <ttx> Still waiting to get step 2/5 merged ?
21:43:37 <jog0> ttx: needs code review
21:44:01 <ttx> #help Review needed on https://review.openstack.org/#/c/10256/
21:44:40 <ttx> jog0: How complex are the remaining steps ?
21:45:45 <ttx> vishy: please mention that review during your meeting if it's not covered by then, looks like the one most likely to spillover
21:46:10 <jog0> ttx: fairly easy, besides moving AZs to aggregates internally
21:46:34 <ttx> * https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient
21:46:39 <ttx> We mentioned this earlier when we discussed Glance...
21:47:15 <ttx> bcwaldon has working code, should be proposed soon
21:47:35 <bcwaldon> ttx: code is up, just getting testing to work
21:48:06 <vishy> i will
21:48:06 <ttx> Also wanted to look into a few "High" ones:
21:48:11 <ttx> * https://blueprints.launchpad.net/nova/+spec/extract-nova-volumes
21:48:17 <ttx> vishy: how is this one looking ?
21:48:35 <vishy> ttx: the nova side is done barring potential export code in nova-manage
21:48:41 <vishy> jgriffith is looking at that now
21:48:58 <ttx> * https://blueprints.launchpad.net/nova/+spec/no-db-messaging
21:49:12 <ttx> Lots of changes were merged for this... any indication of how much more there will be ?
21:49:29 <ttx> (are the last 4 proposed the last ones ?)
21:50:36 <vishy> ttx: down to a few
21:50:41 <ttx> Minor cleanups now, those two blueprints look completed to me, please confirm:
21:50:44 <ttx> * https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value
21:50:47 <ttx> * https://blueprints.launchpad.net/nova/+spec/xenstore-metadata
21:50:53 <vishy> ttx: russelb just found a couple more spots in the scheduler he needs to fix
21:51:09 <ttx> (no need to look at them now, just set to Implemented after meeting if appropriate)
21:51:15 <ttx> And this one looks like it could be targeted to F3:
21:51:17 <vishy> k
21:51:18 <ttx> * https://blueprints.launchpad.net/nova/+spec/xenapi-live-block-migration
21:51:27 <vishy> yes should be targeted
21:51:28 <ttx> vishy: Same question as the other projects, apart from Essential stuff, you're fine with deferring to Grizzly anything that doesn't make it by Aug 14 ?
21:51:33 <ttx> targeting...
21:51:36 <vishy> yes
21:51:42 <ttx> vishy: Anything else ?
21:51:55 <vishy> we are going to check those key blueprints in the thursday meeting
21:52:05 <vishy> I will let you know next week if there is anything that comes up there as a blocker
21:52:38 <ttx> sounds good
21:52:43 <ttx> Questions on Nova ?
21:53:16 <ttx> #topic Horizon status
21:53:21 <ttx> gabrielhurley: hey
21:53:26 <gabrielhurley> ttx: hi
21:53:28 <ttx> #link https://launchpad.net/horizon/+milestone/folsom-3
21:53:45 <gabrielhurley> not as much progress since last week as I'd have liked, but not time to cut things quite yet
21:53:48 <ttx> We clarified ext-roles earlier...
21:53:56 <ttx> had a question for https://blueprints.launchpad.net/horizon/+spec/swiftclient -- is that blocked on Swift 1.6.0 release ? Or just work in the pipe ?
21:54:04 <gabrielhurley> just work in the pipe
21:54:21 <ttx> Finally about https://blueprints.launchpad.net/horizon/+spec/readd-quantum-support
21:54:24 <ttx> This looks pretty high-prio... how is that going ?
21:54:51 <gabrielhurley> going well. Akihiro and company have been pushing new revisions of the code regularly and it's definitely gonna land.
21:55:06 <ttx> Finally same question than for the others... you're fine with deferring all those features if they are not merged in by August 14 ?
21:55:44 <gabrielhurley> all the ones that aren't started yet are fine to defer if they don't land
21:55:49 <gabrielhurley> the ones that are started I'd be sad about
21:55:53 <gabrielhurley> but still not blockers
21:55:59 <ttx> gabrielhurley: anything else you wanted to mention ?
21:56:14 <gabrielhurley> I think I got my mentioning done earlier. ;-)
21:56:19 <ttx> Questions for Horizon ?
21:56:47 <ttx> #topic Cinder status try 2
21:56:51 <ttx> jgriffith: howdy!
21:56:52 <jgriffith> howdy :)
21:56:55 <ttx> #link https://launchpad.net/cinder/+milestone/folsom-3
21:57:08 <ttx> * https://blueprints.launchpad.net/cinder/+spec/migrate-nova-volumes-to-cinder
21:57:12 <ttx> Any progress on that ?
21:57:24 <jgriffith> little, as Vishy mentioned that's my next list item
21:57:37 <jgriffith> I plan to have a first pass thrown out tomorrow afternoon hopefully
21:57:41 <ttx> Was wondering if you'd consider it's OK to release Cinder/Folsom if this is not completed.
21:57:47 <jgriffith> meh
21:57:54 <jgriffith> I don't think it will come to that
21:57:59 <ttx> i.e. shouldn't it be "essential" rather than "high"
21:58:16 <jgriffith> given the tone of the ML responses I think it's essential
21:58:23 <jgriffith> Just my opinoin
21:58:26 <jgriffith> opinion
21:58:35 <jgriffith> I'm happy to change it, but I'll have it for F3
21:58:40 <jgriffith> guaranteed
21:58:48 <ttx> jgriffith: that's the spirit :)
21:58:53 <ttx> Will mark it essential
21:58:57 <ttx> * https://blueprints.launchpad.net/cinder/+spec/cinder-notifications
21:58:59 * jgriffith has sucker on his forehead
21:59:01 <ttx> Any news from cp16net ?
21:59:15 <jgriffith> ttx: Yea, he said he's going to finish it
21:59:20 <jgriffith> ttx: The only question is when
21:59:28 <ttx> So it's started, low priority ?
21:59:28 <jgriffith> ttx: He did say in the next week or so (that was last week)
21:59:46 <jgriffith> ttx: yes, started low pri
21:59:50 <ttx> jgriffith: Anything else ?
22:00:02 <jgriffith> ttx: The only thing that keeps me hanging on to it is that it's in nova now
22:00:22 <ttx> Questions on Cinder ?
22:00:25 <jgriffith> Ummm.... lots but nothing anybody cares about likely
22:00:42 <jgriffith> :)
22:00:55 <ttx> #topic Other Team reports
22:01:00 <ttx> Any other team lead with a status report ?
22:01:34 <ttx> #topic Open discussion
22:01:38 <ttx> Anything else, anyone ?
22:02:17 <ttx> #endmeeting