08:00:16 #startmeeting vitrage 08:00:17 Meeting started Wed Jan 30 08:00:16 2019 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:21 The meeting name has been set to 'vitrage' 08:00:21 Hi :-) 08:00:31 \o 08:01:15 Hello 08:01:44 hi 08:01:51 #topic Status and updates 08:02:02 I have no general updates today 08:02:08 Vitrage board in StoryBoard: 08:02:13 #link https://storyboard.openstack.org/#!/board/90 08:02:22 Lot of things are in done already :-) 08:02:37 My updates: I pushed the implementation of templates with parameters 08:02:56 Got some more work to do… including a big merge with template version 3 by idan_hefetz, documentation and tempest tests 08:03:05 #link https://storyboard.openstack.org/#!/story/2004056 08:03:10 That’s it for me 08:03:30 I want to add a new api for vitrage service list 08:03:42 something that was added to other projects also 08:04:12 in a ha scenario you need to know the status of your services and where they are located 08:04:20 so this is a begining 08:04:38 also we could laverge it later for leader election in HA 08:05:03 i will write a spec later in the day 08:05:23 eyalb: +1 on such API 08:05:33 do we really need a spec for it? 08:05:38 eyalb: there were also dicsussions in the self-healing SIG about knowing the services health. I think there is an open gerrit issue about it. Many people responded but I think the discussion is still on going 08:06:13 there are some issues need to consider like containers 08:07:04 eyalb: what do you mean? 08:07:54 well if it run in a container then I suppose I need to print the host that contains the container 08:08:34 we can't do it 08:08:37 and if it is not in a container then I shouled print the hostname 08:09:17 and what happens if we are in k8s ? 08:09:35 just things I thought about now 08:09:54 eyalb: we should not care about it 08:10:05 we should just return hostname and that's all 08:10:20 part of the api is to print if it is up or not 08:10:32 because we can't know if we're running our code i container or not 08:10:49 in k8s we know 08:10:58 where it is running 08:11:30 is sounds strange 08:11:59 we should not allow our services to know how they are ruing 08:12:02 i will write a spec with all my thoughts 08:12:30 eyalb: ok 08:14:02 Any other issue for today’s meeting? 08:15:05 just for the note for react in horizon plugin for vitrage 08:15:41 i was working mostly on internal things last week, but I've found a good (I hope:) ) solution 08:16:14 I'll try to post my code somewhere this week 08:16:18 I'm sorry for the delay( 08:16:30 I had to deal with internal release:( 08:17:17 e0ne: no problem, it actually sounds great that you may have found a solution 08:17:51 I've got some issues with react-router but I think it could be resolved later 08:18:00 that's all from me for this week 08:18:19 e0ne: sounds good, thanks 08:18:42 I’ll tell Alon what you said, of course 08:19:04 I guess we are done for today, have a great day :-) 08:19:23 bye 08:19:48 #endmeeting