20:01:46 #startmeeting horizon 20:01:47 Meeting started Wed Jul 26 20:01:46 2017 UTC and is due to finish in 60 minutes. The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:01:51 The meeting name has been set to 'horizon' 20:01:59 o/ 20:02:05 o/ 20:02:12 o/ 20:02:28 \o/ 20:02:30 o/ 20:02:32 o/ 20:02:35 o/ 20:02:44 Hjkjj 20:02:51 nice (vi command) 20:03:04 gary-smith: Ah, I thought you just fell asleep on the keyboard 20:03:19 iNope 20:03:34 right, lets get started 20:03:38 #topic Notices 20:04:07 Only quick thing I have to mention is that I'll be tagging Pike-3 tomorrow, which is feature freeze 20:04:46 After this point I'll be -2ing all the blueprint patches until we have our first release candidate on Aug 10, 2 weeks time. 20:05:17 After that point master opens for Queens, iirc. 20:05:35 Oh I really need a better way of starting sentences it seems :) 20:06:09 If you think something is ready to merge, you've got about 24 hours to ping me, or you'll need to send an email to dev mailer requesting an FFE. 20:06:24 Thats Feature Freeze Exception, for those new to the process 20:07:18 I know there's a couple of big Neutron features which look like they will miss the deadline, which is unfortunate. 20:07:37 Anyway, thats all from me 20:07:41 #topic Open Discussion 20:07:48 * rdopiera is late again, sorry 20:08:11 Open discussion time, feel free to raise any bugs, blueprints, patches, or just ask questions. We have several cores about to answer :) 20:08:33 I'll leave the meeting running for a while, so there's no rush if you're struggling to phrase a question 20:08:45 Well, i'd have a few points to discuss 20:08:59 pboutin: Sure, fire away 20:09:11 I also have a question about incomplete blueprint stuff 20:09:40 I'm working to fix the bug 1703708, I found the issue, and I'm able to show the proper error in the modal, do we still want the toast to be shown behind the modal (i assume not) 20:09:40 bug 1703708 in OpenStack Dashboard (Horizon) "Horizon image upload with bad Glance CORS config fails with "[object Object]"" [Undecided,New] https://launchpad.net/bugs/1703708 - Assigned to Alok Kumar (rajalokan) 20:09:50 shall we create a tiny patch to enable/disable from config the incomplete panel? 20:10:19 pboutin: Ideally it should be a little alert box inside the modal 20:10:32 that's what I have now, will remove the toast then 20:10:40 the review should follow shortly 20:10:56 rubasov_: Yeah, if you check how angular panels have done it previously, we have an ANGULAR_FEATURES setting 20:11:17 rubasov_: Which is this related to? Trunks? 20:11:28 pboutin: Great, sounds good to me 20:11:34 robcresswell: yes it is about the trunks panel 20:11:52 rubasov_: In that case, because its a new panel, you could also just disable it in the enable/ file 20:12:13 I believe that works 20:12:17 * robcresswell would have to check 20:12:24 Either of those options is viable 20:12:25 I think enable/ would be cleaner 20:12:38 the code is there already 20:12:42 robcresswell: okay, and I guess the default should be to disable it, right? 20:13:07 rubasov_: If its incomplete, yes, unfortunately. I'm happy for it to be mentioned in release notes though. 20:13:15 rubasov_: Then we can just land it during Queens 20:14:19 For the bug 1609777, since there's no longer a tab for "security stuff" and only one for the key pairs. What would be the best place to display those fields 20:14:19 bug 1609777 in OpenStack Dashboard (Horizon) "'can_set_password' ignored in the new launch instance experience" [Medium,Confirmed] https://launchpad.net/bugs/1609777 20:14:20 robcresswell: okay, then I will write a patch for the enable/disable of trunks tomorrow 20:15:13 rubasov_: Thanks; just do it ASAP please, I'm not sure what your tz is, but mines UTC and I'd prefer not to have to stay at my PC all night :) 20:15:22 robcresswell: we only have a release note currently in the details patch (not yet merged), shall I move that to this new enable/disable patch then? 20:15:42 rubasov_: I'll likely merge that tomorrow; I think I only had small nits on it, right? 20:15:47 It was all just visual comments 20:15:57 robcresswell: I'm in UTC+2 and will start tomorrow morning with this 20:15:59 pboutin: Looking 20:16:06 rubasov_: Ah, perfect, thanks 20:16:38 robcresswell: yes, I think the details patch could be merged tomorrow 20:16:58 pboutin: Oh, honestly, I don't know. Possibly the keypairs tab. I can't recall the naming of them off the top of my head. 20:17:10 We could rename it to Security and make it more generic if it has other options. 20:17:26 Yeah, for this tab is already pretty loaded 20:19:14 pboutin: How is it handled in the old launch instance? 20:19:23 Makes me sad having to ask that... 20:19:46 I think it's just security, but the UI for handling the key pair was less overkill than it is now i think 20:20:13 Yup 20:21:05 One moment, let me spin up my dev server... 20:23:14 robcresswell: for me that was all, thank you 20:23:14 pboutin: I'd probably just go with the keypair tab 20:23:33 rubasov_: You're welcome :) 20:23:33 robcresswell: will ping you when done with the enable/disable patch 20:23:39 coolio, will take a look 20:23:41 rubasov_: Sounds good, thanks 20:23:48 robcresswell: and sorry for leaving for the last moment 20:24:33 and for the quick ones, I've noticed that the karma conf files are hardcoded to look for python2.7 xstatic packages. On my computed, they are located under python3.4, so to be able to run my tests, I have to change the karma files.... dunno if it's a problem on my own or if the karma files should be more flexible... 20:24:50 I'm off to sleep, bye everyone 20:24:55 rubasov_: \o 20:24:56 my computer* 20:25:03 bye rubasov_ :) 20:25:07 pboutin: They should be more flexible 20:25:24 pboutin: Tbh they just shouldnt even be using this xstatic nightmare :p 20:25:41 I couldn't agree more 20:25:58 JS libs belongs in that package.json :) 20:25:59 pboutin: But yes, probably should be something in there that checks for a valid version path or something :/ 20:26:09 pboutin: Yeah, nobody likes xstatic. 20:26:20 fiewwww, glad to hear that 20:26:38 Well, its there because of packaging restrictions supposedly 20:26:54 I'm still not entirely sure what the value is over just pulling the upstream package :D 20:27:27 well, if i find a somewhat cool workarround for this, i'ill propose it 20:28:05 (this being the version problems) i'm not confortable enough with all this to mess with packaging stuff 20:28:20 haha, I understood 20:28:54 Yeah, the packaging thing is something I'd have to sort probably, I'm not sure how many active people are about that have good-ish knowledge of the background 20:28:57 and my last point, I worked on the step readiness review that my colleague pushed a few days ago 20:29:38 I think i could be ready 20:29:38 Yep, I saw the reviews popping up in the horizon channel 20:29:45 sorry for the spam :P 20:29:46 Cool, I'll take a look tomorrow 20:29:54 it's good spam tho' :) 20:29:58 No not at all, I'm just glad the work is getting done 20:30:07 Thanks for the contributions :) 20:30:51 good, i'm done with my questions 20:31:12 Awesome. Anyone else? 20:34:00 good, see you all next week then o/ 20:34:46 Yep, I think we can end here 20:34:51 Thanks everyone :) 20:34:53 #endmeeting