17:00:12 #startmeeting murano 17:00:13 Meeting started Tue Mar 14 17:00:12 2017 UTC and is due to finish in 60 minutes. The chair is felipemonteiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:16 The meeting name has been set to 'murano' 17:00:33 #topic Roll Call 17:00:34 o/ 17:00:41 hello 17:00:59 pbourke: Hi 17:01:08 o/ 17:01:25 tovin07_: Hello 17:03:05 o/ 17:03:39 learnmore: Hi 17:04:45 #topic Open Discussion 17:05:45 o/ 17:06:05 kzaitsev_mb: I thought you were asleep :) 17:07:22 its 8PM in here, so no a bit too early for sleep =) 17:07:28 sorry for missing previous 2 meetings 17:07:40 Ah, I read "sleep me" in #murano. 17:07:44 sleepy* 17:08:35 Anyway, you've probably seen that zhurong and I have been updating Murano installation/API docs, the former of which will increase Murano maturity. 17:10:07 sure, seen the patches. would read through them ) 17:10:59 Hello, I asked a question on #murano yesterday about support for the widgetMedia support. I wanted to follow up -- I do not see it being used by any murano apps today, and I was not able to get it working in devstack. So was wondering about the statrus. Thanks! 17:12:21 I meant the widgetMedia attribute. 17:13:21 devray: Have you grepped through Murano to find usages of it? 17:13:40 "widgetMedia sets some custom CSS and JavaScript used for the field's widget rendering. Note, that files should be placed to Django static folder in advance. Mostly they are used to do some client-side field enabling/disabling, hiding/unhiding etc." 17:13:46 #link https://github.com/openstack/murano/blob/c47623f8bb77e162a6f2e0c0b0147f6f00dc0f55/doc/source/appdev-guide/muranopackages/dynamic_ui.rst 17:13:48 Yes, I've grepped the code. 17:15:07 Right I saw it in the docs. And I noticed that some of the murano-apps from kilo(?) were using it, but it has been removed from all the murano-apps in devstack. 17:16:07 I've found this informatin also: 17:16:10 "This is a temporary field which will be 17:16:10 dropped once Version 3 of Dynamic UI is implemented (since it will transparently translate YAQL expressions 17:16:10 into the appropriate JavaScript)." 17:16:16 #link https://media.readthedocs.org/pdf/muranotest/latest/muranotest.pdf 17:17:17 Yes, I saw that, too, which is why I was not sure it was still supported. I am interested in being able to hide/show or enable/disable parts of the UI. 17:18:38 devray: The new dynamic-ui specification wasn't fully implemented client-side. Maybe it's an old artifact that someone forgot to remove. 17:20:44 felipemonteiro: please could you clarify - do you mean that the note about it being removed is incorrect? And that widgetMedia should continue to work? 17:21:48 hm 17:22:06 I think it was added to provide some custom js validation for the fields 17:22:09 but 17:22:22 murano-dashboard does not allow adding custom js in the app itself 17:22:33 so I doubt it's usefull anymore 17:22:37 the field I mean 17:23:08 devray: Which parts of the UI are you trying to hide/show enable/disable? Fields? 17:23:42 Yes, I want to enable/disable or show/hide some fields 17:24:20 Is there some other way to achieve this? 17:24:25 Are you using hidden: true? 17:25:24 felipemonteiro: Yes. But that that hides the field 'permanently' AFAICT 17:25:52 devray: I don't think there is a way to do what you want currently 17:26:39 From what I can see in the murano-apps today, hidden fields are only used to display text 17:28:12 kzaitsev_mb: Oh. So there is no way to even enable/disable a field? 17:28:16 you want some dynamic behaviour in UI, like be able to show/hide fields based on the users choice. You should be able to workaround it if you use different steps, but generally current UI wouldn't allow that kind of behavioue 17:28:31 devray: define 'enable/disable' 17:29:05 you can use 'hidden: true' and probably 'enabled: false' or smth 17:29:12 but I think that's not what you want ) 17:29:39 the new UI was supposed to fix this request, but frankly nobody is working on it at the moment 17:30:38 kzaitsev_mb: Right that is not quite what I want. I want to show (or enable) say a text field based on a user selecting some other value from, say a choice (dropdown menu) field 17:31:14 devray: and that is not possible with the current UI system, yep 17:32:06 kzaitsec_mb: Ok, thank you for the information. 17:34:45 kzaitsev_mb: But it looks like I could do this with widgetMedia - if I provide my own javascript to hide/show. So if widetMedia support was not removed intentionally, then I just need to figure out why it's not working in Ocata? 17:35:58 devray: where would the js file come from? 17:37:06 kzaitsev_mb: I would provide it. My own custom js for my application? 17:39:13 kszitsev_mb: Per the documentation: I would need to add the custom js to the Django static folder, prior to deploying the app. 17:39:21 so you would modify your murano-dashboard & horizon installation? 17:39:25 yep 17:39:31 that should work 17:39:48 your apps would become non-portable, but it should work 17:40:00 the code for the widgetMedia in dashboard is still there 17:40:02 I would not modify the murano-dashboard (I think). Only horizon. 17:40:18 and hasn't been changed for a couple of years 17:40:29 kzaitsev_mb: that is great news. I will try it. Thank you! 17:41:33 kzaitsev_mb: Ah yes, the app would be non-portable. I did not think of that. But yes, that is a limitation. 17:42:07 What do you mean by non-portable? 17:42:14 although horizon's (or maybe djangos) system of serving staic files might have changed 17:43:21 since no one executed the code in question for some time — smth might have gone wrong 17:44:14 learnmore: i don't even know how to answer that +))) 17:44:19 kzaitsev_mb: Yes, that is what I am thinking, too - that it may have been broken unintentionall since no one is using it and there are no tests for it. 17:45:07 kzaitsev_mb: We discussed at the ptg potential enhancement to murano to support additional clouds. I've spoken to my management about this and they're very interested in basically using murano to set up an environment with tiller, tied to a network, allowing for helm API requests. 17:45:19 learnmore: I mean if you modify your murano installation and write apps that depend on your modifications — they become non-portable 17:45:42 kzaitsev_mb: Understood. 17:46:07 devray: there actually is at least 1 test ) 17:46:16 but its probably a unit one 17:47:00 kzaitsev_mb: oh, my apoligies. I thought I grepped the test code, too. I will take a look. 17:47:22 felipemonteiro: honestly you'd need to ping StanLagun or alextivelkov for a verion of CoreLibrary they've been developing that supported the idea 17:47:57 kzaitsev_mb: Will do, I know Stan mentions he works with Kubernetes now. 17:54:16 kzaitsev_mb: Yes, I see the unit test. Thank you. I will investigate further. 17:54:30 kaitsev_mb: Were you still looking into adding glare v2 support? Otherwise, we should remove our non-voting glare gates. 17:54:44 v1* 17:58:07 felipemonteiro: yeah, I was thinking about removing the joba alltogether 17:58:29 but I don't have a definitive idea what should we do 17:58:40 remove and add later when the code is there 17:58:53 or keep the jobs and update the cude untill they're green again 17:59:08 I briefly went over the v1 changes and it looks like it might require more work than I initially realized -- to add v1 support I mean 17:59:12 might ask #infra folks on that 17:59:28 Ask infra to remove the jobs? 17:59:41 after all we're wasting a bunch of their resources here 17:59:43 yep 17:59:59 interesting what they would have to say on that 18:00:25 I could manually do it, if necessary. But I doubt they would be excited about maintaing gates that do nothing but break within 5 minutes. 18:00:46 no, we'll remove them ourselves anyway ) 18:01:00 I was just thinking to aks for advice 18:01:25 seems we're overtime ) 18:04:29 #endmeeting