08:00:17 #startmeeting vitrage 08:00:18 Meeting started Wed Feb 20 08:00:17 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:22 The meeting name has been set to 'vitrage' 08:00:25 Hi :-) 08:00:33 \o/ 08:00:59 hi 08:01:12 hi 08:02:27 Hi 08:02:31 #topic Status and updates 08:02:37 The Stein feature freeze is in two weeks. Stein release dates: 08:02:43 Feature freeze: March 8 08:03:01 This is also the final release of client libraries (including python-vitrageclient) and requirements freeze 08:03:08 Stein first release candidate: March 22 08:03:13 Stein final release candidate: April 5 08:03:18 Stein release: April 12 08:03:32 I asked for new releases of all Vitrage deliverables, so I can add python-vitrageclient to Heat. It wasn’t approved yet. 08:03:36 #link https://review.openstack.org/#/c/637623/ 08:03:57 My updates: I’m back to working on adding VitrageTemplate resource to Heat 08:04:07 I’m about to update the spec, code and template examples later today 08:04:18 The new code will use Vitrage template with parameters, so it will be much more straight forward. 08:04:23 #link https://review.openstack.org/578786 08:04:27 #link https://review.openstack.org/584863 08:04:31 #link https://review.openstack.org/583217 08:04:35 #link https://review.openstack.org/583951 08:04:51 All of them are about the be updated. The spec is more or less updated already 08:05:00 That’s it for me 08:05:29 few items from me 08:05:37 #link https://review.openstack.org/#/c/634487/ 08:05:50 ^^ it's vitrage-dashboard integration tests 08:06:11 these tests verify that plugin works with the latest horizon 08:06:35 I proposed similar patches to few other plugins 08:07:05 we can extend tests in the future because I proposed only a very basic checks 08:07:24 Nice! 08:07:32 e0ne: It looks great, such tests were missing 08:07:32 idan_hefetz: thanks 08:07:42 also, I finished a big part vitrage-tempest-plugin 08:07:51 #link https://review.openstack.org/#/q/project:openstack/vitrage-tempest-plugin+owner:%22Ivan+Kolodyazhny+%253Ce0ne%2540e0ne.info%253E%22+status:open 08:08:04 all patches are in one chain 08:08:23 there're tests results: #link https://review.openstack.org/#/c/612652/ 08:09:08 once they will be merged, I will be unblocked to work on DB migrations for vitrage 08:09:31 Great, thanks! 08:09:38 I didn't remove few vitrage usages from tempest plugin, so any help is welcome 08:10:23 according to react in horizon plugin - I've got working PoC and will share docs and the code later today 08:11:06 I think, that's all from me 08:11:17 e0ne = O:3 08:11:18 e0ne: do you have a list of changes in the tempest plugin - what was done and what’s left to do? so if one of us has some free time, they can take one of the tasks 08:12:05 ifat_afek: just grep 'from vitrage.' in the plugin 08:12:18 Ok :-) 08:12:19 there are some things like 'from vitrage.graph import Vertex' 08:12:42 mnajjar: sorry, didn't get what you mean 08:13:43 sory... it is an emoji of Angel 08:14:03 mnajjar: :) 08:14:18 i mean that all is great 08:14:32 my update: 08:15:12 i didn't work on getting Kubernetes pods in Vitrage 08:15:48 because of lack in env resources 08:16:15 i hope to get back to it soon 08:16:29 that's from my side 08:17:23 for me i worked on displaying v3 template https://review.openstack.org/637521/ 08:18:05 and for the react in horizon 08:18:43 i currently Integrating the xstatic packages into Horizon 08:19:14 that's all form me :) 08:20:03 nooryameen: we just thought of something… there is no way to add a template with parameters via the UI. Because it requires adding new input - the parameters. How complicated it is to add new input to the Add template dialog? 08:20:19 when I asked you to check several template types, I forgot about it :-( 08:21:00 It should be optional. Few templates have parameters, but most templates don’t have them 08:23:32 i dont think it would be so difficult to add it to UI 08:23:47 but i need to check it first 08:24:02 Ok, I’ll send you examples and how to use it, so you can check 08:24:04 Thanks! 08:24:16 good to be optimistic :D 08:24:27 :-) 08:24:27 After about two versions end messages were not used in datasources, i removed the relevant code. 08:24:33 e0ne: That's why i wrote Rocky in the deprecation, it hasn't been supported for a while. 08:24:41 #link https://review.openstack.org/#/c/637553/ 08:24:49 Also, helping out with parameters in version 3: 08:24:59 #link https://review.openstack.org/#/c/638097/ 08:25:16 idan_hefetz: I understand the reason, but it's confusing 08:25:56 e0ne: Ok, i'll fix it 08:26:04 idan_hefetz: thanks 08:26:04 That's me 08:26:29 Thanks. Anything else or we’re done? 08:28:18 Bye everyone :-) 08:28:25 bye 08:28:26 bye 08:28:50 #endmeeting