08:00:13 #startmeeting vitrage 08:00:14 Meeting started Wed Nov 16 08:00:13 2016 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:17 The meeting name has been set to 'vitrage' 08:00:22 Hi everyone! 08:00:27 hi 08:02:14 Hi all :) 08:03:48 hi 08:05:16 I 08:06:11 many vitrage developers are out of office today, so the meeting might be shorter 08:06:21 #topic Status and Updates 08:07:14 Hi all 08:07:47 I’m still trying to arrange vitrage documentation. I’ll be happy if someone can review my change for vitrage-specs 08:07:53 #link https://review.openstack.org/#/c/394550/ 08:08:03 This is how the page looks like at the moment, with only Mitaka blueprints: 08:08:16 #link http://specs.openstack.org/openstack/vitrage-specs/ 08:08:24 Maybe I can help 08:08:37 I did some work for docs in js-generator-openstack project 08:08:48 and I’m waiting for openstack-infra approval for my change of adding the official vitrage documentation 08:08:56 hi 08:08:57 #link https://review.openstack.org/#/c/394181/ 08:10:10 It seems already +2ed 08:10:12 As part of Ocata goals, all project teams are requested to remove Oslo incubated code. I checked it, and didn’t seem to find anything in vitrage. let me know if you think there is something we do need to do 08:10:40 yujunz: are you talking about the infra change? I need another +2 and workflow+1 08:10:50 Yes 08:10:52 the infra 08:11:15 I’ll ask for another review in the infra IRC channel later today 08:12:24 these are my updates 08:12:30 any other updates? 08:12:40 I have three 08:13:14 First the skeleton 08:13:14 #link https://review.openstack.org/396974 08:13:19 Hi guys. 08:13:30 It is initiated during my creation of static datasource 08:14:27 It seems we need more than a skeleton to copy 08:14:42 But a generator to create one with specified name 08:14:48 I saw you suggested a generator. any idea how it can be done? 08:14:54 Maybe rendering from a jinja2 template 08:15:13 I am not familiar with it 08:15:33 vitrage-dashboard developer should be familiar with it 08:15:53 Put some tags in the template and replace them with real variable value 08:16:30 I'll update the details in blueprint 08:16:52 The original patchset is open for comments on what should be included in the skeleton 08:17:30 Next static datasource 08:17:32 #link https://review.openstack.org/#/c/397494/ 08:17:32 yujunz: how is it related to vitrage-dashboard? 08:17:59 yujunz: I am familiar with the vitrage-dashboard, but have no idea what is jinja2 08:18:04 Let me know how can I help 08:18:37 jinja2 is the default template in django, I think 08:19:11 Our vitrage-dashboard is written with Angular, and is just a plugin in the Horizon django code 08:19:19 I see 08:19:29 Then it is similar to yeoman generator 08:19:59 #link http://yeoman.io/ 08:20:14 But not that complex 08:20:24 ok. but yeoman is usually just for bootstrap your app. You are talking about service or something, not ? 08:20:45 No, we just want to create a skeleton of new data source 08:21:24 So provide a group of template and render the required source file to bootstrap the creation of a new data source 08:21:29 but how is it related to UI? 08:21:46 yujunz: Django use Django template language by default. Jinja2 is default template of Flask. 08:21:54 Ah, yes 08:21:55 do you think a new datasource can be created out of templates? isn’t it more complex than that? 08:22:06 No 08:22:12 A skeleton can be created from that 08:22:46 and how will this skeleton be different than the one you already created? 08:23:14 s/Skeleton/your_sourcename/g 08:23:14 Things like that 08:23:36 Save your effort from replacing every occurence of placehodler 08:23:37 the thing is, that I don’t think the datasources code is that trivial. for example, the code of the monitors (nagios/zabbix/aodh) is very different than the code of openstack datasources (nova, cinder…) 08:23:52 oh, this could help indeed 08:24:01 but the implementation part will simply remain empty? 08:24:08 Yes 08:24:19 ok, sounds good 08:24:28 Sorry, it sounds like something big 08:24:37 why sorry? 08:24:54 Made some misunderstanding 08:25:25 I mean it sounded 08:25:25 no problem, maybe I should have waited to the blueprint to better understand 08:25:36 Sure 08:26:16 Next static datasource 08:26:24 #link https://review.openstack.org/#/c/397494/ 08:26:56 Most things have be clarified. I will move on to method implementation if no further question 08:27:07 I just read your last comment 08:27:34 how can the parser tell if this is an old format or a new format? 08:27:41 if they are both on the same folder 08:28:15 The new format has a `meta` attribute as it is in the evaluator 08:28:29 ok 08:28:59 Next file utils 08:29:14 #link https://review.openstack.org/#/c/397572/ 08:29:30 Any further comments? 08:29:33 so I basically agreed with your last comment 08:29:57 That's the best compromise I could think of for now 08:30:18 alexey_weyl is on vacation, he can only see your comment on Sunday. but I think we can approve your code, and if Alexey insists we can change these two lines later 08:30:29 No problem 08:30:36 That's all from my side 08:31:06 on the other hand, someone else should also +2, and I’m not sure who can do it today (like I said, many core developers are OOO) 08:31:17 anyone else has updates? 08:33:31 ok, I’ll update on behalf of other people… I noticed the dwj fixed a bug in ceilometer in favor of vitrage, so we will be able to parse event-alarms correctly 08:34:28 I know that eyalb is progressing with RedHat regarding the RDO specs 08:35:19 another general issue: I assume you’ve heard about the PTG – the Project Team Gathering, AKA the design summit. It was split from the main summit, and will happen in Atlanta in February 2017. The main summit will be in Boston in May. 08:35:52 I was asked whether the Vitrage team will join the PTG. I don’t really see a need to go. We are doing our designs using the mailing lists, gerrit and IRC, and it seems to work well. Having two days in Atlanta is not necessarily productive, plus none of us (as far as I know) comes from this area. 08:36:01 Anyway, I’ll be happy to hear your thoughts about it. Anyone feels that we should be there? 08:37:51 and while we were speaking, my infra change was approved. I’ll send an email once we have our docs finallized 08:38:03 I think that’s all for now, unless anyone else has something to discuss 08:39:24 goodbye then :-) 08:39:34 by 08:39:56 #endmeeting