08:00:18 <ifat_afek> #startmeeting vitrage
08:00:19 <openstack> Meeting started Wed Dec 13 08:00:18 2017 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:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:22 <openstack> The meeting name has been set to 'vitrage'
08:00:33 <idan_hefetz> Hi!
08:00:33 <eyalb> hi
08:00:38 <ifat_afek> Hi :-)
08:03:06 <_adary> mornin'
08:03:45 <ifat_afek> Today’s agenda:
08:03:50 <ifat_afek> •	Status and Updates
08:03:55 <ifat_afek> •	Open Discussion
08:04:02 <ifat_afek> #topic Status and Updates
08:04:11 <ifat_afek> No general updates this time.
08:04:28 <ifat_afek> My update: I am working on the execute-mistral refactoring.
08:04:38 <ifat_afek> Specifically, I’m about to push a change that allows different template validation and loading per-version.
08:04:54 <ifat_afek> It will also modify the execute-mistral action (as an example for the different validation and loading).
08:05:02 <ifat_afek> That’s it for me
08:05:48 <idan_hefetz> I'll update
08:05:57 <idan_hefetz> I've been working to test this commit:
08:06:10 <idan_hefetz> https://review.openstack.org/#/c/527608/
08:07:45 <idan_hefetz> eventlet for rpc enforces using eventlet.monkey_patch caused all
08:07:45 <idan_hefetz> So far we have been using the eventlet monkey patch for rpc, enforces using this caused vitrage to effectively use a single thread
08:08:25 <idan_hefetz> This commit removed the monkey patch and changes rpc to threading
08:08:34 <idan_hefetz> so vitrage may use actual threads
08:09:24 <idan_hefetz> That's it
08:09:36 <ifat_afek> Thanks
08:09:52 <ifat_afek> Anyone else wants to update?
08:11:30 <ifat_afek> Seems like we are very few today… so let’s move on to the open discussion
08:11:38 <ifat_afek> #topic Open Discussion
08:11:51 <ifat_afek> Someone named Minwook contacted me and asked about adding in Vitrage the capability to perform performance tests.
08:12:05 <ifat_afek> His idea is to right-click on a VM, and select “execute Rally test” or “execute Yardstick tests”. The result of the execution will be inserted as additional information on the VM.
08:12:19 <ifat_afek> After talking about it with some of you, let me share our initial thoughts, and feel free to comment.
08:12:42 <ifat_afek> Should this feature be used in production? Does it make sense to execute benchmarks in a production environment?
08:13:12 <ifat_afek> Regarding the ability to run external actions from Vitrage entity graph: This could be is a great idea.
08:13:22 <ifat_afek> In addition to performance tests, we could also think of other actions like ‘execute Mistral workflow’.
08:13:32 <ifat_afek> The list of actions should be configurable, and upon selection an action-specific UI should be opened with the needed parameters.
08:14:30 <ifat_afek> At first I thought that Rally/Yardstick datasources should be added, but in his latest mail Minwook suggested to add lightweight performance test functionality in Vitrage itself.
08:14:56 <ifat_afek> Personally, I don’t think that Vitrage was meant for it, but I’ll be happy to hear other people
08:15:16 <ifat_afek> Another requirement is the ability to add performance test output as properties to an existing resource.
08:15:28 <ifat_afek> It requires the ‘merge datasource / datasource equivalence’ feature that we didn’t implement yet.
08:15:46 <eyalb> I don't think that vitrage should do it he can write a tool that queries vitrage and do what ever he wants
08:15:50 <ifat_afek> That’s it
08:16:19 <ifat_afek> I think you are right. His tool will probably query the system and then send the output to Vitrage
08:16:51 <eyalb> but why should vitrage show his output ?
08:16:59 <ifat_afek> BTW, I asked his permission to continue the discussion on the openstack-dev mailing list
08:17:31 <ifat_afek> Vitrage could show the performance properties on top of an instance, this could give more information to the user
08:17:50 <ifat_afek> And it will happen upon demand
08:18:01 <eyalb> but vitrage is not a tool for performance tests
08:19:07 <ifat_afek> Although I have a feeling that he mixes tests for the integration phase with Vitrage that is used for production. Doing benchmarks on top of Vitrage doesn’t make sense, it will affect the runtime environment
08:19:25 <ifat_afek> Vitrage could trigger perfromance tests, but should not execute them itself
08:20:23 <ifat_afek> That’s it for me. Any other open issues?
08:22:50 <ifat_afek> An update from Muhamad Najjar: he has made changes in the database, so for existing devstacks you need to pull the latest code and run ‘vitrage dbsync’
08:23:35 <ifat_afek> Bye, see you next week :-)
08:23:44 <eyalb> bye
08:23:59 <idan_hefetz> cheers
08:24:06 <ifat_afek> #endmeeting