22:01:49 <gabrielhurley> #startmeeting horizon
22:01:50 <openstack> Meeting started Tue Jan 29 22:01:49 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:53 <openstack> The meeting name has been set to 'horizon'
22:02:31 <gabrielhurley> #topic General updates
22:03:07 <gabrielhurley> The main thing I want to convey this week is simply to get first passes of code up for review as soon as possible
22:03:39 <gabrielhurley> Ideally we'd have something to look at for allthe BPs by this time next week.
22:03:53 <gabrielhurley> For folks that have more than one BP assigned, I'd like to see at least one of them.
22:04:09 <mrunge> well, that could become a bit tough
22:04:12 <gabrielhurley> whether on github or on gerrit (gerrit is preferrable for visibility)
22:04:44 <mrunge> there's fosdem at the weekend here, kicking persons out of business for 4 days (like me)
22:05:06 <gabrielhurley> for folks who can't do that this week, I totally understand and would like to suggest that you at least put forth some indication of where you're at
22:05:06 <mrunge> let's see, what I can do
22:05:18 <gabrielhurley> that could be laying out where things are on the BP whiteboard
22:05:29 <gabrielhurley> or a visual mockup
22:05:31 <gabrielhurley> etc
22:05:35 <gabrielhurley> some indication of progress
22:05:36 <mrunge> yeah, should be good
22:05:47 <mrunge> I agree
22:05:51 <gabrielhurley> 'cuz I'd like to do a real evaluation of what (if anything) needs to be bumped out of the milestone next week
22:06:27 <gabrielhurley> with that said...
22:06:32 <gabrielhurley> #topic Blueprints and Bugs
22:07:00 <gabrielhurley> Two new blueprints came up this week which may impact G3
22:07:03 <gabrielhurley> https://blueprints.launchpad.net/horizon/+spec/quantum-lbaas
22:07:21 <gabrielhurley> Which is under active dev by the quantum team, but it sounds like there's some flux about the API capabilities, etc.
22:07:29 <zykes-> gabrielhurley: yo!
22:07:29 <gabrielhurley> so I'm reserving judgment on inclusion so far
22:07:33 <zykes-> question on blueprint gabrielhurley
22:07:33 <gabrielhurley> hi zykes
22:07:36 <gabrielhurley> sure
22:07:59 <zykes-> I asked you regarding some stuff to make a integration for other things like reddwarf and you gave me a link to a BP earlier and told me to wait for it
22:08:30 <gabrielhurley> was it the BP about doing better intrsopection to be more DRY?
22:08:58 <gabrielhurley> or something else?
22:09:49 <gabrielhurley> if it *was* that BP, it ended up not being doable in Grizzly, so if you want to proceed on building bits for RedDwarf then I'd say go for it
22:10:56 <gabrielhurley> okay, dunno what happened to zykes there
22:10:57 <gabrielhurley> anyhow
22:11:14 <gabrielhurley> the other BP I wanted to mention is https://blueprints.launchpad.net/horizon/+spec/swift-folder-prefix
22:11:52 <gabrielhurley> apparently the implementation of pseudo-folders horizon is using was based on outdated Swift documentation, which they've now corrected, so some of the Nebula folks are going to get us into line with current Swift best practices.
22:12:19 <annegentle> gabrielhurley: eek. Is there a doc bug?
22:12:30 <annegentle> gabrielhurley: oh "now corrected" -- carry on :)
22:12:57 <gabrielhurley> annegentle: yeah, they cleaned things up. not sure when or where. I wasn't tracking that part. bcwaldon had more to do with it.
22:13:22 <gabrielhurley> as I understand it everything is in consensus on the right way now
22:13:29 <gabrielhurley> so it's just a matter of catching up the code
22:14:42 <gabrielhurley> In terms of bugs, I'm a little behind in my usual triage so far, so if other folks want to help triage (meaning verify the bug, comment on it, and mark it's confirmed/incomplete/etc. status) that'd be awesome
22:14:52 <gabrielhurley> It's not a terribly long list but the more the merrier
22:15:04 <gabrielhurley> I use this query saved as a bookmark: https://bugs.launchpad.net/horizon/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_bra
22:15:08 <gabrielhurley> wow that's long and ugly
22:15:17 <gabrielhurley> but it gives you all the "new" bugs for the project
22:15:20 <mrunge> yes, indeed
22:15:26 <jpich> Cool, thanks for the query
22:15:31 <gabrielhurley> totally
22:15:41 <gabrielhurley> #topic Open Discussion
22:15:45 <mrunge> yepp, very cool
22:15:47 <gabrielhurley> the floor is yours!
22:16:10 <mrunge> regarding: https://blueprints.launchpad.net/horizon/+spec/theme-support
22:16:18 <gabrielhurley> yep
22:16:26 <mrunge> I hope I can present some code before the next meeting
22:16:42 <mrunge> maybe it requires some discussion
22:16:51 <mrunge> we'll see
22:17:09 <gabrielhurley> if you can bring something forward that'd be great, whether it's a POC, or identifying what further discussion needs to happen and getting that going.
22:17:23 <gabrielhurley> that's one that I don't mind seeing come through a little later, but it does need momentum
22:17:25 <mrunge> I have a pretty good idea, what to do, and how
22:17:29 <gabrielhurley> cool
22:17:51 <kspear> just a question on
22:17:52 <kspear> https://blueprints.launchpad.net/horizon/+spec/add-security-group-to-instance
22:18:01 <kspear> i got a bit preempted here
22:18:18 <kspear> i was in the middle of coding a different approach
22:18:19 <gabrielhurley> go ahead, what's the question?
22:18:27 <mrunge> kspear: that code is not your proposal?
22:18:34 <kspear> nope
22:18:38 <mrunge> I see
22:18:42 <jpich> Taking on an assigned blueprint without asking (?) isn't great...
22:18:49 <gabrielhurley> https://review.openstack.org/#/c/20446/
22:18:50 <gabrielhurley> lol
22:18:52 <kspear> i was working on reusing the admin/projects code
22:18:53 <gabrielhurley> I didn't even notice
22:18:56 <kspear> http://i.imgur.com/kjY8myj.png
22:19:04 <kspear> ^ that's was where i was at
22:19:06 <uvirtbot> kspear: Error: "that's" is not a valid command.
22:19:20 <mrunge> yes, I remember that
22:19:35 <gabrielhurley> oh uvirtbot, when will you learn ;-)
22:19:40 <kspear> haha
22:19:42 <mrunge> hahaha
22:19:48 <kspear> i'm not against accepting the existing review
22:20:01 <kspear> but i guess i wanted to ask people's thoughts on which approach is better
22:20:10 <gabrielhurley> UX-wise I like the approach you've got going
22:20:41 <gabrielhurley> moreover, there are some ways I think the code for that component could be improved and I'd like to see how your usage of it affects things
22:20:57 <kspear> the changes are fairly minimal at the moment
22:21:03 <kspear> so all the naming no longer makes sense
22:21:03 <gabrielhurley> glad to hear it
22:21:07 <kspear> projects/users etc
22:21:30 <kspear> i can push what i have so far to gerrit and let you guys take a look
22:21:38 <kspear> just needs tests really
22:21:54 <gabrielhurley> If you're ready to do that that's cool, if not, take your time with it
22:21:59 <mrunge> I'd say, go ahead
22:22:09 <gabrielhurley> however, if you could post that screenshot to the BP whiteboard that'd be good
22:22:29 <kspear> sure
22:22:32 <gabrielhurley> and then we can follow up with Brooklyn Chen to make sure the efforts get aligned.
22:22:43 <kspear> sounds good
22:22:51 <gabrielhurley> awesome
22:23:12 <gabrielhurley> other topics?
22:24:19 <gabrielhurley> vkmc: if you have concerns about showing code by next week I've been following your comments on the whiteboard and everything looks good on Tenant Deletion plan-wise. So consider yourself to have a little bit more breathing room.
22:24:56 <vkmc> gabrielhurley, I was going to ask for comments about that bp https://blueprints.launchpad.net/horizon/+spec/tenant-deletion
22:25:22 <vkmc> gabrielhurley, As you saw, I updated the whiteboard, but I'm still looking for affected services
22:25:53 <vkmc> I'd love everyone suggestions on that
22:26:09 <vkmc> I hope I'll finish with that tomorrow and start with UX mockup
22:26:27 <gabrielhurley> awesome. and yeah, anyone who wants to contribute on that whiteboard, there's lots there
22:26:29 <vkmc> And, with some luck, I'll start coding it on Friday
22:27:08 <jpich> vkmc: I don't see any missing services, great whiteboard :)
22:27:17 <gabrielhurley> yeah, well done
22:27:22 <vkmc> I'm afraid I'm still not familiar with other components ifaces, so I may miss something
22:27:41 <vkmc> Thanks guys
22:28:29 <gabrielhurley> anything else before we wrap?
22:28:56 <kspear> oh just one thing
22:29:12 <gabrielhurley> go for it
22:29:13 <kspear> the bug regarding editing flavor ids you mentioned in last weeks meeting
22:29:18 <gabrielhurley> ah yes
22:29:30 <kspear> i tried to follow that up with nova but didn't get very far
22:29:43 <gabrielhurley> https://bugs.launchpad.net/horizon/+bug/1100444
22:29:45 <uvirtbot> Launchpad bug 1100444 in horizon "Edit Flavor Window Displays Details of Deleted Flavors" [High,Confirmed]
22:30:14 <gabrielhurley> (reading now)
22:31:12 <gabrielhurley> so it looks like this isn't a bug in Horizon in master, but we may want to look into what the right solution for a Folsom backport would be?
22:31:33 <kspear> yeah i'd say so
22:31:48 <gabrielhurley> okay
22:31:54 <gabrielhurley> I'll make the approriate adjustments on the bg
22:31:54 <kspear> although
22:32:04 <gabrielhurley> ?
22:32:27 <kspear> if you set a flavor id manually through novaclient cli you can trigger the bug even on master
22:33:02 <kspear> because nova always sends back the deleted flavor when we "get" it
22:33:04 <gabrielhurley> yeah
22:33:18 <gabrielhurley> that's probably a separate issue for nova though
22:33:28 <kspear> yep
22:33:31 <gabrielhurley> although I'm curious, if you try to update that "deleted" flavor, does it let you?
22:33:36 <gabrielhurley> oh
22:33:37 <gabrielhurley> no
22:33:39 <gabrielhurley> it can't
22:33:42 <gabrielhurley> there's no API route for that
22:33:53 <kspear> yeah
22:33:56 <gabrielhurley> it allows the get, and that's actually useful for various reasons
22:34:01 <gabrielhurley> so I wouldn't call that a bug
22:34:04 <gabrielhurley> it's just misunderstood
22:34:06 <gabrielhurley> ;-)
22:34:23 <kspear> yeah
22:34:30 <gabrielhurley> cool
22:34:37 <kspear> except when you want to edit a flavor with overlapping ids :)
22:35:14 <gabrielhurley> the bigger problem is that flavors have both a UUID and an "id", and the two confuse people constantly
22:35:25 <gabrielhurley> the internal database ID isn't generally exposed anywhere
22:35:40 <gabrielhurley> they're separate records with the same user-facing "id"
22:35:59 <kspear> i think the problem is that nova allows you to reuse a flavor id
22:35:59 <gabrielhurley> took me a while to get myself clear on how (and why) it's like that
22:36:06 <gabrielhurley> it's intentional
22:36:18 <gabrielhurley> ::shrug::
22:36:26 <gabrielhurley> can debate it offline sometime ;-)
22:36:28 <kspear> oh well
22:36:30 <kspear> sure :)
22:36:46 <gabrielhurley> anyhow, with that, I'm gonna call this meeting adjourned.
22:36:55 <gabrielhurley> thank you all and see you next week!
22:37:06 <gabrielhurley> #endmeeting