22:00:45 #startmeeting horizon 22:00:46 Meeting started Tue Aug 20 22:00:45 2013 UTC and is due to finish in 60 minutes. The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:00:49 The meeting name has been set to 'horizon' 22:01:10 #topic overview 22:01:20 Hello folks! 22:01:27 hey all! 22:01:28 Hello! 22:01:34 howdy 22:01:35 hi ^) 22:01:35 Hello! 22:01:40 I've got more "general" business than usual today. Shocking, I know. 22:01:42 Hello 22:02:12 Hello 22:02:21 hi 22:02:27 First off, I'd like to let everyone know that Liz Blanchard and Jaromir Coufal were granted ATC status by the technical committee earlier today for the contributions in the UX arena. So congrats to them! 22:02:51 Congrats! 22:02:58 woo hoooo! And thanks to gabrielhurley for the nomination :) Happy to be an ATC! 22:02:58 Congratulations :) 22:03:00 conratulations! 22:03:18 Next up, I've got a big item I'd like to get some group feedback on... 22:03:20 :) Congratz! 22:03:22 Congrats! 22:03:39 The Trove team put up a review for adding panels to manage Trove databases and backups: https://blueprints.launchpad.net/horizon/+spec/add-trove-panels-unit-tests-coverage 22:04:02 hello, that is my doing :) 22:04:19 Normally my policy is not to include projects into the OpenStack Dashboard repo until they graduate from incubation (due to pains with Quantum a few years back) 22:04:48 I see 22:04:49 however Trove is in very stable shape, all the TC feedback has been positive, the API seems stable, and it's properly filtered behind the service being in the service catalog. 22:05:10 thanks gabrielhurley! 22:05:26 Since I think there are gonna be a lot of folks interested in Trove sooner rather than later, I could see it being a significant boon to them to have an optional inclusion in the dashboard in the final H release while they prepare for an official release in I. 22:05:43 +1 22:05:45 That would be great 22:05:49 + <3 22:05:50 +1 for Trove 22:05:50 Perhaps it'd also encourage them not to mess with their APIs too much ;-) 22:05:55 +1! 22:06:01 +1 22:06:16 so I mostly wanted to see if any of the Horizon core folks had objections to the inclusion in H 22:06:21 gabrielhurley: oh besides the entire api rewrite once we go incubated (jk) ;) 22:06:32 gabrielhurley: there seems to be 2 Blueprints 22:06:34 haha. yeah 22:06:34 https://blueprints.launchpad.net/horizon/+spec/trove-support 22:07:11 robertmyers: so there are. I think that one can be closed as a duplicate in favor of the one I linked/you've been working on. 22:07:25 or 22:07:26 wait 22:07:29 now I'm confused 22:07:47 I had that backwards 22:07:48 the one I just sent was the one the review is attached to 22:07:50 yeah 22:07:56 so the other should be closed 22:08:01 I'll fix that 22:08:07 we only need one BP 22:08:18 I think the other assumes the trove panels were added 22:08:26 as we do need tests 22:08:39 gotcha 22:08:48 they both seem valid 22:08:50 let's get some tests into the current review before it merges, please 22:09:11 sounds reasonable 22:09:30 I wanted eyes on it first to see if it was on the right path 22:09:32 usually having a basic suite of tests is part of the bar for feature inclusion 22:09:35 totally understandable 22:09:39 let's just add the tests before merging it 22:09:42 but I haven't heard any objections so let's go ahead with the review and aim to merge it in H3! 22:09:50 nice! 22:09:52 robertmyers: would you post some screenshots in the blueprint? 22:09:55 thanks for stepping up robertmyers and hub_cap :-) 22:10:09 lblanchard: sure I can 22:10:21 gabrielhurley: your welcome 22:10:24 gabrielhurley: thx for the approval on the bp and the overall support! 22:10:30 itll be great to have in dashboard 22:10:35 robertmyers: awesome, thanks…will definitely have a look 22:10:36 :-) 22:10:57 Let's see... next item: I still haven't heard any new news about design summit talk submissions, will continue to let y'all know when there's news. 22:11:56 Next, also important: We really ought to fix https://bugs.launchpad.net/horizon/+bug/1179526 so our source language is correct in transifex 22:11:58 Launchpad bug 1179526 in horizon "source_lang in Horizon repo is overwritten by Transifex" [High,Confirmed] 22:12:09 nice ! 22:12:14 we've been stalling on this for a while, and I'd rather not let Havana get released without fixing it 22:12:19 yep, I saw you there, Daisy ;-) 22:12:47 I'm afraid it's gonna mean manually re-uploading a bunch of the translation files, but it needs to happen 22:12:49 Are we going to go the deletion + recreation way? 22:12:53 I want to help but I'm not the maintainer so I cannot fix it. My plan is to delete the old resource and upload the new version. 22:13:16 I can add whoever wants to fix it as an admin on the Horizon transifex project. 22:13:27 If I could get a volunteer to work with Daisy that'd be fantastic. 22:13:43 Then please add me. And please tell me where is the latest POT file? 22:13:56 I'd like to become more familiar with Transifex so I can try and help 22:14:10 Daisy: will do, though it'll probably be easier if one of the Horizon core folks works with you too 22:14:11 We can try and fix https://bugs.launchpad.net/horizon/+bug/1182011 at the same time 22:14:13 Launchpad bug 1182011 in horizon "djangojs.po not available on Transifex" [High,Confirmed] 22:14:14 jpich: perfect 22:14:22 I'll get you both set up 22:14:45 all I can really say is "preserve as much as possible of the existing translation work, but getting the job done is more important" 22:15:06 Yes, I came here to discuss about these with you. 22:15:50 First, I think we need the latest POT file on Transifex with source language as en. 22:16:02 jpich: you're already added as a transifex admin, so that's good to go 22:16:20 Then I need to understand when is the string frozen date. 22:16:27 From Havana release plan, Sep 4 will be the string frozen date. Does that mean, after Sep 4, there won't be any string change? 22:16:51 that's the idea 22:17:28 Daisy: I just added you as a maintainer on the Horizon transifex project as well 22:17:47 Let's say this way, our translation team can focus on Horzion translation after string frozen. When finishing translation, we can also run Horzion in different langauge setting, which is called Translation Verification Test. 22:18:11 Yep. That's perfect. We'll do our best to enforce the string freeze. 22:18:15 We may find bugs during TVT and we will report. 22:18:55 We hope we can get latest POT file update before Sep 4 so that we can spend some time on translation in order to get enough time after string frozen. 22:19:06 definitely 22:19:27 As I know, the Horizon in Transifex is not updated automatically by Jenkins job. Can I know when and how you update them in Transifex? 22:19:33 things shouldn't change *significantly* in the next few weeks, so the sooner you can get the source language issue fixed the sooner you can start working 22:20:04 oh, did that never get set up? that's lame... 22:20:24 maybe I'm wrong... 22:20:39 I used to have it linked to the github repo so that it would get the changes when the files changed in the repository 22:20:39 not sure if that's been broken subsequently 22:20:39 if y'all can investigate that too, that'd be good 22:20:57 or if the infra team wants to get things working that's good too. updating manually with the transifex client is easy, but automated is better 22:21:15 ok. let me do the investigation then. 22:21:32 where is the link to PoT file in repo? 22:21:32 So we push pot files out to Transifex automatically, but pull translations manually, is that correct? 22:22:01 that's the idea, yeah 22:22:39 do you generate PoT file manually? 22:22:42 I think many of the projects pull automatically, should we consider doing this too so translators see their contributions included earlier? 22:24:01 jpich: it'd be nice to get that working, it didn't happen originally 'cuz the infra folks didn't want to write a second code path to work with django's particularities vs. babel. 22:24:15 Daisy: I think we have 3 pot files to upload, though they may not be up to date at the moment in the repository 22:24:20 I'm fine with that being an Ichouse target unless you want to work on it 22:24:36 gabrielhurley: I see, that makes sense 22:25:01 anyhow, I'll let you two work on it. Email me if you get stuck. 22:25:18 got it. Thank you, gabrielhurley and jpich . 22:25:27 let's jump over to blueprints now 22:25:29 Not sure it'll be possible for me now, but a Icehouse target would be nice 22:25:29 #topic blueprints 22:25:44 Overall the blueprint progress is looking really good 22:25:57 Blueprint: https://blueprints.launchpad.net/horizon/+spec/improved-boot-from-volume I'd like to discuss screen-shots https://docs.google.com/document/d/1Zg5PS3-s4OJtSoYGttI13OMHEtragDPYv63GUl4zpF4/edit for patch: https://review.openstack.org/#/c/41728/ I need more opinions about implementation of planning changes in the pop-up "Launch Instance". 22:27:15 vasiliy: did you have specific questions? I reviewed that this morning and thought it seemed reasonable. 22:27:53 no specific question - just would like to hear opinion from core-developers 22:28:38 looks good to me, just need to finish reviewing the code 22:29:00 although, now that I look at the screenshots, I realize that this has the downside of moving a required field off the first tab... 22:30:11 we will combine all needed options in one tab "Storage Backend" 22:30:11 that's already been the case though (key) 22:30:38 personally i'd prefer to merge the entire storage backend tab with the details tab 22:30:51 david-lyle: keypair isn't technically required, though that does catch people out. 22:31:27 In the short term I think I'm with kspear_... in the long term, I think we may want to investigate a two-step form like when launching things through Heat 22:31:43 can't create an instance without one or network 22:32:31 by which I mean you'd have a first form where you select the source of the instance (image, volume, etc.) and submit that, then from you'd get the approriate set of other options in a second form. This would also simplify some of the work we're doing with tailoring flavor options to image sizes, etc. 22:32:43 I agree that long term we can revisit this form to organize mostly everything on one clean page 22:32:48 just throwing thoughts out there for long-term 22:33:09 For now though I do think keeping image selection on the first tab would be best 22:33:36 it's a place where there's no sane default, and you'll just get an error if you try to submit (unlike keypair, network, etc) 22:34:17 (we should work on improving the sane defaults of those fields, btw, but that has nthing to do with this patch) 22:34:25 vasiliy: does that make sense? 22:34:41 hi 22:35:03 make sense - but it's better to understand what do we need to make to complete current work on this blueprint 22:35:32 in any cases user can select only one option: image, volume, snapshot etc/ 22:36:08 so, i don't see any reasons, why this options should be on the different tabs 22:37:19 correct, it should only be on one, but I'm pretty sure it should be on the first tab, 'cuz it's fundamental to launching the instance. I would almost say it is the most fudamental aspect of choosing what instance you're going to launch. 22:37:47 i think it is good idea 22:38:09 so let's combine options from "storag backend" with first tab? 22:38:21 correct 22:38:28 good - thanks 22:38:31 great 22:38:37 If all fundamental options are placed on the one tab 22:39:39 So, on other blueprints... 22:39:41 thanks 22:39:41 I did hear from bradjones about https://blueprints.launchpad.net/horizon/+spec/network-quotas and he's gonna look at it this week. If nothing's up by next week I'm gonna bump that. 22:39:52 Oh 22:40:02 This kind of looks like what I did to fix a bug 22:40:07 https://bugs.launchpad.net/horizon/+bug/1109140 22:40:09 Launchpad bug 1109140 in horizon "Floating IP quota not coming from Quantum" [Medium,In progress] 22:40:27 similar 22:40:35 I think the BP encompasses more 22:40:41 but I'm glad you fixed that 22:40:41 can I bring up the cisco blueprint :) 22:40:48 absubram_: sure 22:41:24 thanks.. I have my diffs out on review but it failed Jenkins a few times already.. thanks to jpich and david-lyle for pointing out my commit message error 22:41:49 but it still looks like Jenkins is arbitarily failing different tests for me each time.. it passes once fails the next without any changes to my diffs 22:42:07 I have actually as of now sent my diffs for the new dashboard with it turned off by default 22:42:27 yeah, I see some LOST jobs on there. Jenkins hasn't been great lately. 22:42:31 there are some changes to the cisco plugin that if it goes into H3 will need corresponding changes to Horizon too 22:42:50 I don't know that I can offer much except to say "keep trying" as far as Jenkins goes. 22:43:10 so I felt having it turned off for the moment was better but that I could at least get the infrastructure up so that I could get some review comments 22:43:11 it would be good to know if those plugin changes are going to happen ASAP 22:43:16 plus I also need to add test cases 22:43:27 and fix some existing tests when the dashboard is turned om 22:43:29 on* 22:43:30 yep, definitely need those 22:43:49 will get the testcases fixed and new ones added by this week 22:44:13 but I wouldn't mind feedback about the rest of the code in the meantime given that this is my first attempt :) 22:44:23 I think people are aware of it... I'll try and take a look. Perhaps you could offer up some advice on how to test your patch since I don't think most folks know how to simulate a Cisco N1K... 22:44:28 there's a blueprint in neutron for the plugin changes 22:44:37 I believe the review will be up in a day or so 22:45:02 ah of course.. as I mentioned though I have actually tuend the dashboard off 22:45:05 turned* 22:45:09 The Neutron BP is all well and good, but this is why we try not to land features on our side that aren't done by early H3 at the very latest... these last minute changes to plugins mean we end up with unstable code. 22:45:18 so there should be no change to horizon functionally with my diffs right now 22:45:39 okay. we'll see how the changes in Neutron go 22:46:22 I see ok.. I'll put up instructions on how to work with the cisco n1k in the bklueprint so people can try it out 22:46:27 I'll also add screenshots 22:46:35 that would be good, thanks. 22:46:40 Anybody else have blueprints they want to bring up or that they're concerned about? 22:46:45 can I bring up my topology view bp? 22:46:46 I spent almost all day reviewing today, and feel like I know where things are at. 22:46:52 Toshi: definitely 22:46:55 https://blueprints.launchpad.net/horizon/+spec/editable-network-topology-view 22:47:06 I think this implememtation is not so much different from the previous version, and no impact to other component, so If you could review and it would be merged to habana, that would be great. 22:47:31 yep. for a while there I wasn't sure we'd see code for it, but now that it's up I see no reason not to include it 22:47:38 I'll retarget that now 22:48:06 blueprint is back in H3 22:48:33 Toshi: UI design looks great at first glance, I will add more specific feedback in the BP tomorrow. 22:48:39 gabrielhurley:Thank you very much! 22:48:46 You're welcome 22:48:51 Anybody else got BPs to discuss? 22:49:17 lblanchard:Thanks, any coments are welcome :-) 22:50:25 Just as a general FYI, Jenkins is really backed up currently, so things are taking a very long time to merge. There have also been a lot of merge conflicts unfortunately, so if you see a review that didn't merge cleanly but is otherwise ready to go, try and be proactive in updating it and getting the merge job kicked again. I'd like to shrink our review queue drastically this week. 22:50:59 There are 11 reviews that are approved but unmerged currently, and another 5-10 that need a second review. We can get 2/3 of what's open merged this week, easily. 22:51:23 #topic open discussion 22:51:46 I think I've covered all of what I had. I just encourage everyone to keep diligent on the reviews 22:52:00 We've got ten minutes if anyone has any other topics they care about currently. 22:52:05 Does anyone have an idea on this: https://answers.launchpad.net/horizon/+question/233742 ? 22:52:34 lcheng: https://bugs.launchpad.net/horizon/+bug/1210253 has some debugging information 22:52:36 I wonder if the issue is on the debian packaging. 22:52:37 Launchpad bug 1210253 in horizon "With Havana 2 installed, Launching horizon UI results in the error " NameError: name 'Dashboard' is not defined"" [Undecided,Triaged] 22:52:42 no clue, personally 22:52:46 and surfaced another bug with assert 22:53:04 lcheng: circular import maybe? 22:53:31 lcheng: (that's a wild guess) 22:53:37 jpich: thanks didn't notice there was updates on the ubg 22:54:12 Are there plans to add an openstack-auth launchpad page? Defects associated with that repo don't seem to sync with gerrit. Case in point https://review.openstack.org/#/c/42219/ isn't reflected in https://bugs.launchpad.net/horizon/+bug/1212748 or is there a way to get them to sync? 22:54:14 Launchpad bug 1212748 in horizon "log in for user with first project disabled fails" [High,Confirmed] 22:54:15 kspear: maybe, I'll try to dig around when I get the chance. 22:54:20 I noticed something strange when setting Debug to False with Django 1.5.2 while trying to debug this, maybe someone can reproduce it and get a stack trace (nothing showed in the log, but the home page showed an error 500 page instead of the login screen, while it's fine with Django 1.4.5) 22:55:59 david-lyle: probably a good idea. could you email the ML or ping monty about that? 22:56:09 sure 22:58:02 we're just about out of time here. any last minute items? 22:58:21 when is our exact freeze date? 22:58:22 jpich: If there is an error in the Auth middleware in django, it just fails silently. It might be the version of openstack_auth causing the issue. It requires at least 1.0.9 to run in django 1.5. 22:58:58 Sept 4th or end of this week? 22:59:00 lcheng: Ah, good one. I'll try that in the morning! Thanks 22:59:21 absubram_: there's no *hard* feature freeze before the RC cut, but as it gets closer I use heavier discretion on the risk associated with the change. 22:59:37 got it.. thanks :) 23:00:34 okay, that's it folks! 23:00:39 thanks, and have a great week! 23:00:39 Thanks 23:00:40 btw, for the reviewers you need to add django_openstack_auth to your watched projects to get notifications. 23:00:42 #endmeeting