08:00:26 #startmeeting vitrage 08:00:27 Meeting started Wed Jun 8 08:00:26 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:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:30 The meeting name has been set to 'vitrage' 08:00:34 hi 08:00:43 o/ 08:01:28 Hello there :) 08:01:30 Hi all :) 08:01:35 Hi everyone! 08:01:39 Good to see ya all :) 08:01:57 Hi 08:02:53 hi 08:03:41 Our agenda today: 08:03:47 * Vitrage POC Demo in OPNFV Berlin summit 08:03:52 * Status and Updates 08:03:57 * Open Discussion 08:04:07 #topic Vitrage POC Demo in OPNFV Berlin summit 08:04:13 Hi :) 08:04:29 Hi 08:04:44 We are preparing Vitrage demo for OPNF Berlin summit. 08:05:02 The purpose is to show how Vitrage can be used for Doctor use cases 08:05:08 Demo outline: 08:05:14 - We will have two hosts: one green and one yellow (CPU/memory alarm) 08:05:25 - We will show deduced alarms, deduced states and RCA on the yellow host 08:05:26 Hi guys 08:05:37 hi 08:05:39 - We will simulate, using nagios or zabbix, host NIC failure on the green host 08:05:54 - This will cause, eventually, calling nova force-down API, which will evacuate all instances from the red host and move them to the yellow host 08:06:14 - We still need to determine the best way to call nova force-down 08:06:31 Either we raise aodh alarm, or maybe there will be a script to listen to vitrage alarm and call nova API. We will consult Doctor team about it 08:06:47 In the coming week we should make sure everything works, and also prepare a few slides about Vitrage architecture and demo structure 08:07:10 Sounds like a cool demo! 08:07:24 Note that there will be a parallel Congress POC demo in another booth. 08:07:42 Any comments or questions regarding the demo? 08:08:37 #topic Status and Updates 08:08:47 I'm still working on supporting vitrage in liberty 08:09:24 Almost everything works, with slight changes in vitrage code. There is one problem with our cli commands, show topology returns html instead of json. I'm checking it 08:09:32 Who else wants to update? 08:09:39 i will 08:10:07 I'm currently manually installing vitrage on the demo setup, with redhat liberty distribution, with good progress. 08:10:40 Except for OPNFV perp, I'm working to write a blueprint for aodh, support for custom alarms, that will allow vitrage-evaluator to create aodh alarms. 08:10:56 Thats that 08:11:09 idan_hefetz: cool 08:11:25 I will update 08:11:45 I built the vitrage rpms and checked them and they look ok 08:12:16 I also asked for a package review for rdo so the rpms will be added to RDO 08:12:57 and I continue pushing code to puppet-vitrage 08:13:16 #link https://bugzilla.redhat.com/show_bug.cgi?id=1342987 08:13:16 bugzilla.redhat.com bug 1342987 in Package Review "Review Request: openstack-vitrage - OpenStack RCA (Root Cause Analysis) Engine" [Unspecified,New] - Assigned to hguemar 08:13:32 no response yet :-( 08:13:36 thats it 08:14:19 I will update 08:14:40 I have finished to write the zabbix data source and tests. 08:14:47 I will push it all today. 08:15:10 at the moment it works with get_all and get_changes. 08:15:52 We plan to do the notifications for zabbix soon, but we still need to understand exactly how we won't to send and receive the notifications from zabbix 08:16:23 should we send to oslo bus if it is possible from bash or python 08:16:40 and i am working on the installation of zabbix still. 08:17:00 at the moment we know how to install the server 08:17:37 and still need to understand exactly how to install with agent, and how to install it on environments that doesn't have a connection to the internet 08:17:40 thats it 08:17:44 alexey_weyl: great news about Zabbix datasource. We hope we can use it for Berlin POC 08:18:28 I have some updates to 08:18:39 So finally I added our new API – template validate 08:18:43 :) 08:18:52 It is available through CLI and URL 08:19:07 You can find more info about in Vitrage documentation : https://github.com/openstack/vitrage/blob/master/doc/source/vitrage-api.rst 08:19:34 #link https://github.com/openstack/vitrage/blob/master/doc/source/vitrage-api.rst 08:19:40 Also, we have a list of validation status messages and codes – I will add it to Vitrage docs by the end of this week 08:20:01 This week I’m gonna start to work on the template list API 08:20:31 It will show a list of all loaded templates and their status (validation failed or success) 08:20:52 In addition, I started to think how to show this list in GUI 08:21:12 That’s all for now 08:21:22 lhartal: sounds great, thanks 08:22:06 I'll update 08:22:08 sorry for the duplicated link - I'm not familiar with IRC 08:22:27 lhartal: no problem ;-) 08:23:19 The support for overlapping templates has been pushed. A small fix will be hopefully merged today. 08:23:43 I've also updated the RST with documentation on this feature, which also will hopefully be merged today 08:25:25 this feature makes it safe to add templates without concern about possible overlap or contradiction with others, in the sense that the evaluator now has a determinstic behavior in such cases. For more info, check the doc. 08:25:35 thats it 08:25:43 elisha_r: cool, thanks 08:26:11 Who else wants to update? 08:27:53 Moving on 08:28:00 #topic Open Discussion 08:28:09 Anyone would like to discuss anything? 08:28:17 Hi,everyone,i'm dongwenjuan 08:28:27 Could you please help me to add the workflow+1 for these reviews? Thanks 08:28:34 #link https://review.openstack.org/#/c/324371/ 08:28:35 Hi dongwenjuan :-) 08:28:42 #link https://review.openstack.org/#/c/324377/ 08:29:08 שפפרםהקג 08:29:10 approved 08:29:12 First link - will soon be approved 08:29:43 OK, thanks. :) 08:29:53 Also the second one 08:30:15 Although in general, we should think again about which info and debug messages we would like to have in vitrage 08:30:38 Any other issue? 08:32:48 A reminder - we are looking for new contributors :-) whoever is interested is welcome to contact us 08:33:03 #link https://wiki.openstack.org/wiki/Vitrage 08:33:44 I we really need some more power here, because we have plenty of things to do 08:34:07 in vitrage itself, the UI needs to be approved 08:34:49 *improved 08:36:21 alexey_weyl: exactly 08:36:34 Any other topic to discuss, or should we close the meeting? 08:37:17 hi, I have found Vitrage this morning, I'm doing some investigate, hopping I can do some help in the future 08:37:44 great - welcome 08:37:45 We would love to help 08:37:58 gtt116: great! 08:38:13 :) cool, thanks guys! 08:38:14 gtt116: you are welcome to come with any question you have 08:39:14 gtt116: any specific areas you are interested in? 08:39:35 maybe sensu datasource 08:40:21 first of all, I think I need to learn how it works 08:40:54 gtt116: We wanted to add sensu datasource, but as a first stage we are adding zabbix. So if you want to write it you are more than welcome :-) 08:41:25 Anyway, take your time and learn. Let us know if you need any help 08:41:40 yeah, a sensu datasource would be great 08:41:49 OK, I will, thanks 08:42:16 I also like zabbix, too 08:43:01 I know zabbix, and have wrote a tool to back up zabbix configuration throught zabbix HTTP api. does this help? 08:43:50 I have just pushed the zabbix datasource 08:44:03 I am planning to push the tests in an hour 08:44:11 https://review.openstack.org/#/c/326575/ 08:44:22 #https://review.openstack.org/#/c/326575/ 08:44:31 #link https://review.openstack.org/#/c/326575/ 08:44:48 but i am still a neweby in zabbix 08:45:00 alexey_weyl, cool 08:45:02 and if you could help me with some more, it will be great. 08:46:32 yeah, that's great, I'm a newby in Vitrage, give me some time to learn it :) 08:46:50 no problem :) 08:47:09 How can I maybe contact you? 08:47:49 my email: gtt116@gmail.com, also IRC is OK 08:48:35 Any other issue someone would like to discuss? 08:50:38 So goodbye everyone, see you next week 08:50:42 bye bye 08:50:47 bye 08:50:49 bye 08:50:50 bye bye 08:51:01 #endmeeting