02:31:57 #startmeeting congressteammeeting 02:31:57 Meeting started Fri Jun 22 02:31:57 2018 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:31:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:32:00 The meeting name has been set to 'congressteammeeting' 02:32:21 hello all. topics here as usual. please add/comment! 02:32:23 https://etherpad.openstack.org/p/congress-meeting-topics 02:33:19 ekcs: hello! 02:34:55 hi akhil_jain ! 02:37:26 ok let’s dive in then. 02:37:27 No major topics from me. 02:37:31 #topic gate 02:38:09 Just a quick update that gate was blocked for a few days because of 1. sphinx upgrade to 1.7.5 causing errors in building doc from docstring 02:38:40 and 2. because for some reason nova-compute host now takes longer than the default 60 seconds wait time to start up on the main dsvm job. 02:39:01 both should be fixed by this patch: https://review.openstack.org/#/c/576601/ being merged now. 02:39:02 patch 576601 - congress - Unblock gate 02:41:22 #topic open discussion 02:41:23 other than that I don’t have much to talk about today. 02:41:39 akhil_jain: I saw that you pinged my yesterday but I didn’t see it until much later. 02:42:06 ekcs: ya, i have question regarding push driver only! 02:42:35 cool you wanna talk about that now? 02:42:48 can we issue POST req driretly to datasource manualy instead of installing that project? 02:44:04 akhil_jain: for what purpose? 02:44:14 just for testing 02:44:15 gate testing? 02:44:21 testing during development? 02:44:26 yes 02:45:24 got it. 02:45:27 its ok we can discuss about it later on mail chain. 02:45:41 either way yes that’s what we already do for doctor driver: https://github.com/openstack/congress-tempest-plugin/blob/master/congress_tempest_plugin/tests/scenario/congress_datasources/test_doctor.py 02:46:04 like here: https://github.com/openstack/congress-tempest-plugin/blob/master/congress_tempest_plugin/tests/scenario/congress_datasources/test_doctor.py#L77 02:46:24 thanks for reference i will look into same and get back to you 02:46:47 better reference could be what I did for vitrage. 02:46:48 https://review.openstack.org/#/c/574902/6/congress_tempest_plugin/tests/scenario/congress_datasources/test_vitrage.py@78 02:46:49 patch 574902 - congress-tempest-plugin - Test webhook to congress vitrage data source 02:47:21 if this gets merged or you make a patch depending on it, you can easily use the same method to send webhook. 02:47:35 yes for vitrage i have been try lately. but maybe i was missing something and getting error 02:48:37 ultimately we’d probably want a fully integrated test at gate to make sure the projects don’t drift out of sync, but for now the best we can do is simulated webhook before vitrage and monasca merge authenticated webhooks. 02:48:48 I see we can work through that together if you like. 02:49:01 how are you testing vitrage/ 02:49:03 ? 02:49:44 using your PS and issuing POST request manually after creating datasources 02:50:39 was checking if data gets added to alarms table but was unable to do that 02:51:05 I see what error / failure do you get? 02:51:43 I was internal server server error. 02:52:15 but i will look into same as link shared by you. 02:52:25 hmmm. could you paste the exact POST command somewhere? maybe in the topics etherpad or wherever else you want 02:52:53 thanks for testing it out btw 02:54:13 yes, i was study code flow. and your vitrage driver is helping me out. thanks to you 02:54:39 i have pasted in etherpad topics POST request 02:54:50 tell me if i am wrong somewhere 02:56:23 i’m looking.... 02:56:53 thanks 02:59:34 that’s strange. not sure why. seems to be exactly the same thing my tempest test is doing... 02:59:51 either way though maybe better error message in my code would be helpful. 03:00:54 ok i will share it. after generating error again 03:01:10 thanks for your time looking into it 03:03:01 yea. well if it says internal server error there probbaly wasn’t much more info. i meant maybe I could include more error reporting. 03:03:10 anyways yea I’m stumped for now. 03:03:40 maybe look at the log files if you produce it again. 03:04:50 appreciate your help! 03:05:01 i will look more into it 03:06:33 ok yea i’ll look some more. 03:06:52 wrap up meeting then for now? 03:07:12 yes nothing from my side 03:08:53 alrigh then talk to you later! happy friday 03:08:56 #endmeeting