04:00:07 <ekcs> #startmeeting congressteammeeting
04:00:08 <openstack> Meeting started Fri Jan 11 04:00:07 2019 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:11 <openstack> The meeting name has been set to 'congressteammeeting'
04:00:11 <Haunted330> This channel is closed. You will have to leave.
04:00:23 <ekcs> hmm
04:00:42 <Haunted330> please move this to your department's channel
04:00:50 <Haunted330> #openstack-congress
04:01:08 <akhil_jain> ekcs: hi
04:01:35 <ekcs> Ok not sure what’s going on but I guess we can talk on #congress
04:01:45 <Haunted330> well even that you cant do now because it is 10pm CST. Site hours are M-F 6am-10pm CST, Saturday-Sundy 8am-4pm CST. For meeting channels, hours are M-F 8am-4pm CST
04:02:45 <Haunted330> for #openstack hours are M-F 8am-4pm CST
04:02:58 <Haunted330> Weekend hours are followed on major holidays, Christmas Eve, and NEw Years Eve
04:03:08 <Haunted330> The site is closed Easter Sunday, Thanksgiving Day, and Christmas Day
04:03:56 <Haunted330> for all channels other than #openstack and the meeting channels, it is M-F 6am-10pm CST, Saturday-Sundy 8am-4pm CST
04:04:42 <Haunted330> This channel is closed. You will have to leave.
04:05:33 <ekcs> sorry I’m really confused. is there an email or webpage that explains the change?
04:05:45 <Haunted330> This is no change
04:05:49 <Haunted330> this is how it has always been
04:06:04 <Haunted330> but now we are really enforcing this
04:06:15 <Haunted330> The site has asked me to really enforce this rule
04:06:24 <Haunted330> Im just doing what they pay me to do
04:06:27 <ekcs> which site?
04:06:33 <Haunted330> Openstack
04:07:21 <akhil_jain> ekcs: i think you must ignore this user in userslist
04:07:28 <Haunted330> For all meeting channels and #openstack hours are M-F 8am-4pm CST. For all others, it is M-F 6am-10pm CST and Sa-Su 8am-4pm CST
04:07:42 <Haunted330> Weekend hours are followed on major holidays, Christma Eve and NEw Years Eve
04:08:00 <Haunted330> All channels are closed Easter Sunday, Thanksgiving Day, and Christmas Day
04:08:09 <Haunted330> This is all you must remember
04:08:27 <Haunted330> I am the channel security.
04:08:43 <Haunted330> I am in charge of enforcement of any rule.
04:09:44 <Haunted330> so you have to either change the location or the time of your meeting. The time of your meeting wont work in any channel for it is after 10pm CST
04:10:47 <Haunted330> Just come on back at 8am CST which is approximately 10 hours from now
04:15:15 <ekcs> ok sorry about that no idea what that was.
04:15:47 <ekcs> the topics are at the usual place.
04:17:05 <ekcs> feel free to add your topics.
04:17:13 <ekcs> I’ll dive in now.
04:17:29 <ekcs> #topic congress-tempest-plugin stable branch jobs incorrect
04:19:05 <ekcs> A problem came up that very strangely, stable branch zuul jobs on congress-tempest-plugin don’t seem to be doing the right thing.
04:19:25 <ekcs> for example, the new z3 builtin tests should’ve failed, but didn’t.
04:19:51 <ekcs> that’s why this cherrypick is failing: https://review.openstack.org/#/c/629029/
04:20:12 <ekcs> because the new tests in tempest fail.
04:20:51 <ekcs> for whatever reason, the failure doesn’t show up in the stable branch jobs triggered by congress-tempest-plugin patch. I’m guessing it’s some kind of misconfiguration.
04:21:31 <ekcs> I send something to the ML to see if I can get some hints. but just an update on that for now.
04:22:15 <ekcs> any questions or comments?
04:23:51 <ekcs> I’ll add a note to that cherrypick patch not to recheck in the mean time.
04:23:52 <akhil_jain> yes gone through your mail. and tried to dig in logs. but not found anything as of now
04:24:34 <akhil_jain> also gate failing in congress-tempest-plugin stating openstack congress datasource create command not founf
04:24:52 <ekcs> ok can you link to that?
04:25:55 <akhil_jain> http://logs.openstack.org/74/621974/1/check/congress-devstack-py35-api-mysql-queens/ec8cceb/logs/devstacklog.txt.gz
04:26:03 <akhil_jain> last lines of this
04:26:43 <akhil_jain> http://logs.openstack.org/74/621974/1/check/congress-devstack-py35-api-mysql-queens/ec8cceb/logs/devstacklog.txt.gz#_2019-01-11_01_39_03_984
04:27:53 <ekcs> hmm that’s very strange. I guess I’ll investigate it. no idea right now what could be causing that.
04:28:20 <ekcs> I guess we’ll move on for now then.
04:28:48 <akhil_jain> failed in queens
04:28:56 <akhil_jain> passed in rocky http://logs.openstack.org/74/621974/1/check/congress-devstack-py35-api-mysql-rocky/6e59800/logs/devstacklog.txt.gz#_2019-01-11_01_16_34_523
04:30:33 <ekcs> yea…. we’ll need to look into what version of the client is getting used for the queens job.
04:30:54 <akhil_jain> its master for openstackclient everywhere
04:31:32 <akhil_jain> will dig more on my end and let you know
04:32:48 <ekcs> i see. yea that’s very strange. the only thing that’s changed on the client is adding the py36 to classifier. could have something to do with that… but i don’t have any ideas right now.
04:32:50 <ekcs> yea thanks!
04:33:14 <ekcs> well let’s move on then.
04:33:17 <ekcs> #topic api-ref
04:33:26 <ekcs> you added that topic akhil_jain ?
04:34:04 <akhil_jain> yes, just an idea. need your view if we should implement it in congress
04:34:52 <akhil_jain> nova is currently generating sample response files automatically from templates of request by making request
04:35:17 <akhil_jain> plus they are comparing the response with template response
04:36:21 <akhil_jain> that way we can get two benefits. 1. updated docs everytime things changes. 2. functional testing with every api change
04:36:33 <akhil_jain> also link with more details: https://docs.openstack.org/nova/latest/contributor/api.html#functional-tests-and-api-samples
04:37:38 <ekcs> I think it’s very helpful. but also quite a lot of work for a small project. would you like to look into how much work it’d be and whether you feel it’s worth the effort vs other things?
04:38:02 <ekcs> it’s definitely a good thing.
04:38:28 <akhil_jain> ya sure. will have to look into code for that.
04:38:45 <akhil_jain> thanks for input
04:38:53 <ekcs> great!
04:39:38 <ekcs> ok let’s move along then.
04:39:43 <ekcs> #topic patches
04:39:54 <ekcs> anything to discuss here?
04:40:46 <akhil_jain> I have gone through your comments. thanks for detailed review as always. will make nova test changes today itself and working on tacker tests
04:41:15 <ekcs> I’ve submitted a patch for json model. it’s the first piece doing most basic implementation of polling json ingester. more pieces will follow (diferential update, push ingester, etc.). but the first piece is ready for review.
04:41:26 <ekcs> great!
04:42:31 <ekcs> #topic open discussion
04:42:37 <akhil_jain> yes i saw that. didnt got time to understand it completely. will go through it soon enough
04:43:06 <ekcs> yup no rush! thanks!
04:43:25 <ekcs> anything else we want to discuss today?
04:43:33 <akhil_jain> one more thing. do you have any check in mind that can go in upgrade checks
04:44:10 <ekcs> here’s my understanding but correct me if wrong.
04:45:53 <ekcs> basically if we make changes which could cause incompatibility or problem from one version to the next, we’d also add an upgrade check for that.
04:46:11 <ekcs> so far i think the only thing is monasca webhook schema change.
04:46:55 <ekcs> the tc page has a helpful tip which is basically thinghs we’d mention in the upgrade section of the release notes may have a corresponding upgrade check.
04:47:15 <ekcs> so maybe we could check to see whether monasca webhook is used?
04:48:08 <akhil_jain> yes that is valid check for congress upgrade. will try implementing that
04:48:49 <akhil_jain> i will ask for your help when i start working on that
04:51:41 <ekcs> ok great! I’m actually not quite sure how it’d be implemented. to check whether monasca webhook driver is being used. unfortunately it’s not in config. so need to find a way to ether api congress or check the database.
04:52:12 <ekcs> thanks for bringing it up. i didn’t even think about the monasca webhook change. thought there was nothing needed yet.
04:53:17 <ekcs> anyway I’ll think a bit more about how to do it too and we can reconvene when ready.
04:53:53 <akhil_jain> thats great. thanks
04:54:59 <ekcs> probably most straight forward to import congress/db/datasources and use it to check the driver field of all active data sources.
04:56:14 <ekcs> ok time’s almost up for today.
04:56:16 <akhil_jain> hmm that will work
04:56:45 <ekcs> any last things to talk about?
04:57:13 <akhil_jain> i think thats it for m=now
04:57:17 <akhil_jain> now*
04:58:01 <akhil_jain> this now is idle from long https://review.openstack.org/#/c/597110/
04:58:50 <ekcs> right. I’ll take one last look and merge it.
04:59:42 <akhil_jain> ok. anything else from your end?
04:59:54 <ekcs> not at the moment =)
05:00:02 <ekcs> let’s wrap up then cuz time’s up.
05:00:05 <ekcs> happy new year too!
05:00:10 <ekcs> #endmeeting