02:31:21 <ekcs> #startmeeting congressteammeeting
02:31:22 <openstack> Meeting started Fri Dec  1 02:31:21 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:31:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
02:31:25 <openstack> The meeting name has been set to 'congressteammeeting'
02:31:49 <ekcs> hi all!
02:32:00 <ekcs> living list of topics here: https://etherpad.openstack.org/p/congress-meeting-topics
02:32:09 <ekcs> please read/comment/add =)
02:34:23 <ramineni_> ekcs: hi
02:34:40 <ekcs> hi ramineni_ !
02:38:33 <ekcs> ok shall we dive in?
02:38:48 <ekcs> #topic queens-2
02:39:02 <ekcs> again, queens-2 is due next week.
02:39:32 <ekcs> I added to the meeting topics etherpad the open patches I’m thinking we can merge for queens-2.
02:39:44 <ekcs> do they make sense? anything to add/remove/discuss?
02:41:52 <ramineni_> ekcs: looks good
02:42:22 <ekcs> ok then =)
02:43:39 <ekcs> the error on removing that one line of transitional code is kind of strange. hopefully i can figure it out soon.
02:43:46 <ekcs> anyway.
02:43:55 <ramineni_> Ya
02:44:01 <ramineni_> Great .. Thanks
02:44:15 <ekcs> #topic patches
02:44:24 <ekcs> anything else to discuss on patches?
02:44:50 <ramineni_> Nothing from my side
02:45:31 <ekcs> haha great. should be a short meeting then =)
02:45:48 <ekcs> #topic bumping congressclient version
02:46:45 <ekcs> I realized now that dashboard is going to depend on new client code, we should probbaly bump the congressclient version in requirements and global requirements.
02:47:16 <ekcs> we need to think a bit about how to stage that. because first we need to release that client. then update requirements.
02:48:13 <ramineni_> Ya .. we can bump the version after feature freeze?
02:49:36 <ekcs> ramineni_: yea or basically at feature freeze. I think feature freeze and requirement freeze take place at the same time.
02:49:54 <ramineni_> Ah , ok
02:50:22 <ekcs> So we’ll need to think about that carefully in queens-3 to have plenty of time to stage everything.
02:50:46 <ramineni_> Ya , ok
02:50:53 <ekcs> for queens-2 I’m thinking about it a bit as well. I need to find out whether we need to do a client release at queens-2 week.
02:51:09 <ekcs> previously we didin’t, but last cycle they asked us to do a release.
02:51:55 <ekcs> if we do a client release, then it’d be a good idea to bump the requirements for dashbroad queens-2 release too.
02:51:55 <ramineni_> Ok
02:51:55 <masahito> hi, sorry to be late.
02:52:18 <ekcs> though if we’re not going to do a client release, then we can probably just wait.
02:52:25 <ekcs> hi masahito !
02:52:42 <ekcs> masahito: topics here as usual: https://etherpad.openstack.org/p/congress-meeting-topics
02:53:36 <ekcs> ok guess we’re done with the client version discussion.
02:54:07 <ekcs> #topic open discussion
02:54:30 <ekcs> done with the etherpad topics. anything else we’d like to talk about?
02:54:45 <ekcs> or revisiting any topics?
02:55:26 <ramineni_> Ekcs: saw your mail .. thanks for digging up on Oslo messaging drivers
02:55:50 <ekcs> yea. np. glad we figured out what we needed.
02:56:26 <ramineni_> Ya
02:56:28 <ekcs> and great that you brought up the issue of whether we should rely on the in-memory transport. I wouldn’t even have known to look.
02:57:02 <ramineni_> :)
02:57:52 <ekcs> so. I have something I’m stuck on.
02:58:16 <ekcs> I’ll mention it real quick and maybe one of you would have an idea about it.
02:59:15 <ekcs> In this patch, it’s been basically done for a long time I just haven’t beeen able to get the tempest test setup right.
02:59:22 <ekcs> now I’m running into a weird issue.
02:59:23 <ekcs> https://review.openstack.org/#/c/508657/9
02:59:31 <ekcs> http://logs.openstack.org/57/508657/9/check/openstack-tox-pep8/f76d300/job-output.txt.gz#_2017-11-30_01_21_00_830976
03:01:29 <ekcs> it says test in undefined on this line. https://review.openstack.org/#/c/508657/9/congress_tempest_tests/tests/scenario/congress_datasources/test_neutronv2.py@396
03:01:55 <ekcs> but I have no idea why. it’s the same as all the other tests in the same class.
03:02:07 <ekcs> I also don’t get the same pep8 error locally.
03:03:53 <ramineni_> Ya , looks ok to me too on first look ..I'll check more on this once I reach office
03:04:07 <ekcs> but it’s a real error. because the same thing is found in the tempest tests.
03:04:08 <ekcs> http://logs.openstack.org/57/508657/9/check/congress-devstack-api-mysql/a48f02d/job-output.txt.gz#_2017-11-30_01_50_28_996709
03:04:37 <ekcs> so anyway kind of stuck on it.
03:04:57 <ekcs> if you find something that’d be great. I can also just remove that line and see what happens, but wanted to show you guys before I did that.
03:05:24 <ekcs> anyway that’s all from me then.
03:05:24 <masahito> it looks ok to me too.
03:05:39 <ekcs> thanks masahito !
03:06:10 <ekcs> well anything else we’d like to talk about? or we can end meeting early.
03:08:06 <masahito> nothing from my side.
03:09:15 <ramineni_> Nothing from my side too
03:09:23 <ekcs> ok then =)
03:09:34 <ekcs> more next week then!
03:10:30 <ekcs> bye all.
03:10:31 <masahito> thanks!
03:10:34 <masahito> bye
03:10:44 <ekcs> #endmeeting