12:02:17 #startmeeting Horizon 12:02:18 Meeting started Wed Jun 24 12:02:17 2015 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:02:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:02:22 The meeting name has been set to 'horizon' 12:02:33 o/ 12:02:36 Hello, who's here 12:02:43 hi 12:03:38 o/ 12:03:40 o/ 12:04:24 not as crowded as alternate-time meeting it seems. ) 12:04:27 o/ 12:04:42 kzaitsev_mb: not usually 12:04:43 all the sensible americans are asleep ;) 12:05:18 all the non-sensible aussies are here; some came prepared with whiskey 12:05:19 * david-lyle feels there's an implication there 12:05:22 Lol it's 10pm here and I'm sitting in a park because I forgot the meeting and went for a walk 12:05:31 ha! 12:05:52 Whiskey! That's what this walk needs! 12:05:56 Ok bookkeeping stuff first 12:06:13 Liberty-1 was tagged yesterday 12:06:34 #link https://launchpad.net/horizon/liberty/liberty-1 12:06:42 Nice 12:06:56 ... which included a bunch of file renaming in horizon, mostly ;) 12:07:07 3 bps and 153 bug fixes 12:07:26 huh, not bad 12:07:33 less bps than usual 12:08:04 which I blame on the endless quagmire of coding style changes 12:08:13 yeah :/ 12:08:15 amongst other things 12:08:41 There was a lot of progress on other items that just haven't landed yet too 12:09:20 there's *ten* "JSCS Cleanup" patches in flight at the moment 12:09:37 er, twelve 12:09:45 I wish gerrit had a search function 12:09:56 13 12:10:02 lol 12:10:06 for the love of ... 12:10:06 r1chardj0n3s, spawning right now? 12:10:08 and that's not all of them 12:10:30 though it's hard to guage the size of the problem because no-one doing the work is communicating about it grrrr 12:10:57 This needs an etherpad or mailer thread 12:11:18 I feel like cleanup is something you do after the fact, not to block all other things 12:11:24 I think it's just cindy's big plan to be the #1 committer in Liberty ;) 12:11:41 I think some people must get paid by the line 12:11:46 ...or you pick a style before you write thousands of lines of code 12:11:50 I think the JSCS stuff *should* be able to be done while we do other things, yes 12:12:03 robcresswell: yeah, nice idea, but ... 12:12:05 ;) 12:12:10 there are downsides to having great contribution tracking 12:12:24 Problem is that JSCS has been merged with "reorganise everything into components" 12:12:32 for the record: I totally did not mean that thing I said about cindy 12:12:39 JP style guide stuff, right? Seems to be a lot of crossover 12:12:45 yeah 12:12:45 haha 12:13:32 I think a large part of the current efforts is acknowledgment that there's significant tech debt in the codebase, and trying to address some of that 12:14:19 I'll try and get on top of reviewing those faster, so we can move on from just moving code around 12:14:52 I've been focusing on sean's patch chain, but I will try to throw some +1s at the jscs cleanups as well 12:15:26 so looking at the priority list for liberty 12:15:40 #link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities 12:16:22 most of the top priority items are in progress, not done 12:16:46 translation appears to be close 12:16:54 couple of patches to review 12:17:04 Yep. Getting very close I think 12:17:22 I'm still slugging it out with plugins 12:17:37 testing config is my biggest holdup at this point 12:17:47 I had a question actually, about that 12:17:56 sure 12:18:07 Do we want plugins to live under Horizon, like with Neutron? 12:18:22 So Neutron actually covers all of the vendor plugins 12:18:51 I think there is a difference 12:18:58 and I think we cover some, but not all right now? Like manila and tuskar 12:19:15 I was curious where -ui should live. 12:19:27 in Horizon we're supporting services that exist in the ecosystem already 12:20:05 unlike neutron where the plugin is their only tie to the ecosystem 12:20:20 I've left it up to the service teams 12:20:32 they can own or Horizon can 12:20:51 The issue being we need the reviewers for the plugin 12:21:03 we can't handle all of that 12:21:09 That stands for the component uis, but not for vendor extensions, I'd have thought. 12:21:17 david-lyle, is it possible to grant people with per-directory +2 review rights? 12:21:24 tsufiev: no 12:21:34 gerrit is not that sophisticated 12:21:38 :( 12:21:56 So currently we have 3 arrangements 12:22:07 or are working toward 12:22:16 1) plugin lives in contrib 12:22:42 with that the service team members support and 1 horizon core could merge code 12:23:13 2) plugin is owned by horizon team but lives out of tree, like tuskar-ui and manila-ui 12:23:37 3) plugin is owned by the service team 12:23:52 2 and 3 aren't very different IMO 12:24:19 and in both you can have a mixed core between service team and horizon 12:25:07 the model we are shooting for is more like devstack, qa and docs than neutron 12:25:56 where a vendor specific plugin to horizon lives is up for debate 12:26:28 I don't think Horizon owns it though 12:27:21 How does this tie into the governance/projects? Does a ui owned by a service team, count as its own project? 12:27:49 Or does it have its own repo and cores, but still lives under horizon? or the original project, say trove-ui under trove 12:28:10 Just trying to wrap my head around the organisation of it all 12:28:23 you can have completely independant projects under the stadium of another 12:28:29 the gerrit ACLs can be set per repo 12:28:54 so regardless of whether it lives in Horizon or service team the core is what you make of it 12:29:07 it's ultimately up to who runs the show 12:29:26 and we want to let the service teams do that where possible 12:29:27 robcresswell: david-lyle: We in murano are comfortable with our current murano-dashboard plugin for horizon. Currently it lives under murano, has murano cores and plugs in by 1 file drop-in. 12:30:16 we can't keep scaling to support all the things 12:30:26 No, absolutely 12:30:51 kzaitsev_mb, the only drawback of this approach is that you don't know in advance which horizon commit would break murano-dashboard 12:31:39 we could possibly set up non-voting plugin test jobs as well 12:31:59 tsufiev: that's true for dashboard, and heat and nova and oslo. and dozens of things, that's why we have gate jobs and stuff pointed at master horizon =) 12:31:59 How its looking is that we'll end up with a Cisco extension in its own repo, with me as a core, but just wondering how to define that within openstack as a whole 12:32:23 yet putting every possible test job against every plugin into horizon repo - I wander how long then will it took for the horizon commits to pass all checks? 12:32:23 the vendor repos in neutron are under neutron in the goverance big tent scheme even though they are managed completely indepentantly, just so that their relationship to neutron is documented 12:32:46 tsufiev: good point 12:32:52 sambetts: Right, which is what I'd like to do with our cisco dashboard stuff 12:33:11 Just trying to understand if that link is acceptable, or they should be unrelated 12:33:21 david-lyle, I saw a typical commit into Cinder repo, they said it takes ~6 hours for all vendor-specific jobs to pass 12:33:27 I think it's acceptable 12:33:32 robcresswell: ^^ 12:34:05 david-lyle: Ah, great. I'll link patches etc. when they're up 12:34:33 Will make sure nothing merges without your approval. 12:34:51 what about putting jobs, that can be launched by comment? like run plugin-foo? Although I'm not sure if anyone would ever run them in that case... 12:35:46 kzaitsev_mb, or run nightly jobs - i.e. on a time periodic basis - inside every standalone plugin repo 12:36:04 tsufiev: That doesn't really solve the issue though, just gives you a faster warning of breakages 12:36:12 rather than prevent them 12:36:17 robcresswell, agree 12:36:55 let's solve that, but not right now 12:36:57 :) 12:37:02 =) 12:37:22 moving on.. 12:37:40 Midcycle is July 21-23 in Fort Collins, CO, USA 12:37:51 there was an email to the mailing list 12:38:07 it would be nice to get a preliminary head count 12:38:21 trying to figure out where would be best 12:38:30 probably on the etherpad TravT set up 12:38:40 Perhaps one of the existng etherpads? 12:38:42 yep 12:38:44 * david-lyle now has to find that link 12:38:59 I can't make it. No approval :( 12:39:08 https://etherpad.openstack.org/p/horizon-liberty-midcycle 12:39:19 robcresswell :( 12:39:25 :( 12:40:08 yeah, same here. 12:40:19 3000 $US for 3 days is a bit expensive 12:40:46 etherpads aren't loading for me 12:40:54 david-lyle: The indecisiveness on how to phrase that made me laugh. "Attendies" ... "Planned attendies" .... "Who's coming" 12:42:17 I'm here to amuse 12:42:19 It'd be great if someone could leave a hangout on air running, or similar 12:42:37 We will try to do that 12:42:46 shouldn't be a problem 12:43:34 Cheers 12:44:01 There was no official agenda items posted, so 12:44:09 #topic Open Discussion 12:45:42 there's an open question on neillc's translation thing 12:45:54 so babel really wants its plugins to be pip installed 12:46:21 but he's got a hack in there so we can include the angular plugin we're developing sit inside the horizon codebase 12:46:25 while we develop it 12:46:33 he's also pushed it to pypi 12:46:59 but to keep development pace alive, it was felt better to also keep it in horizon while we polish it off 12:47:22 once it's stable, push to pypi and reference it from requirements.txt instead of vendoring 12:47:24 thoughts? 12:47:39 Yep. My plan is to do just that 12:47:44 that sounds reasonable 12:47:53 neillc: sorry, figured your fingers were frozen ;) 12:48:13 In particular not try to switch to oypi version until plurals working 12:48:13 is the plugin horizon specific or angular/babel specific? 12:48:27 angular-specific 12:48:33 Fingers are a bit frozen! 12:48:38 ok, yeah that makes sense 12:49:10 david-lyle, so far as part of Merlin toolkit evaluation activity Dan has created the page https://wiki.openstack.org/wiki/Horizon/MerlinEval What's the next step here? 12:49:38 I'm not sure if there will be too many other projects that will use it though 12:50:15 neillc: should it need many updates? 12:50:34 Not once plurals are working 12:50:36 trying to decide if it should be a repo in openstack 12:51:02 that can be updated after you come to your senses and find a better gig :) 12:51:25 For use with babel integration with pip is important 12:51:41 So pypi seems to make sense 12:52:29 I seem to be doomed to work on i18n. Don't understand why :p 12:52:46 * doug-fish points and laughs 12:52:54 neillc: no argument on pypi, I guess the question is does the source for that live in a personal github repo or openstack/neillsplugin that openstack can publish too also 12:52:54 Pffff 12:52:56 haha 12:53:25 Ah OK. I don't mind either way. 12:53:50 second one seems more sensible 12:54:28 I think so, but start as your own, and we can source an openstack repo from it 12:54:39 Cool 12:54:44 Isn't that how the xstatic packages are supposed to be updated? Though I'm not sure how many actually are. 12:54:54 yes 12:55:15 turns out there was a missing step in xstatic repo creation by the authors 12:55:52 which was including a tox.ini file which allows for the publish job to run 12:56:06 that should be fixed as of yesterday 12:56:57 tsufiev: I need to look into that more 12:57:12 I don't have a clear next step at the moment 12:57:19 Oh nice fix. 12:57:38 david-lyle, okay, just pinging on that to make sure it wasn't forgot :) 12:58:02 tsufiev: always good to prod with a stick occasionally 12:58:22 Btw, several bugs on launchpad have been marked as fix commited by infra without bug links. Not sure whats going on. 12:58:50 that was the L-1 tagging 12:59:01 Ah, okay 12:59:29 Should I just mark them L-2, or dig up the relevant bugs? 12:59:30 wait committed or released? 12:59:39 commited 12:59:50 wait let me check 12:59:50 do you have an example? 13:00:02 https://bugs.launchpad.net/horizon/+bug/1463838 13:00:03 Launchpad bug 1463838 in OpenStack Dashboard (Horizon) "[data processing] Stack trace for invalid cluster details page" [Medium,Fix committed] - Assigned to Tatiana Ovchinnikova (tmazur) 13:00:24 Also here: 13:00:33 #link https://bugs.launchpad.net/horizon/+bug/1466744 13:00:35 Launchpad bug 1466744 in OpenStack Dashboard (Horizon) "Integration test test_image_register_unregister failing gate" [Undecided,Fix committed] - Assigned to Luigi Toscano (ltoscano) 13:01:18 We can continue this in other channel anyway, hour is up 13:02:06 sure, I think that may be the magic of automation 13:02:13 thanks everyone 13:02:16 #endmeeting