Tuesday, 2019-02-26

*** diablo_rojo has joined #openstack-meeting00:02
*** macza has quit IRC00:14
*** cheng1 has joined #openstack-meeting00:18
*** hongbin has quit IRC00:19
*** cheng1 has quit IRC00:25
*** _hemna has joined #openstack-meeting00:28
*** markvoelker has joined #openstack-meeting00:31
*** ijw has quit IRC00:46
*** ijw has joined #openstack-meeting00:48
*** ijw has quit IRC00:50
*** ijw has joined #openstack-meeting00:50
*** galstrom_zzz has quit IRC01:00
*** bbowen has quit IRC01:03
*** bbowen has joined #openstack-meeting01:03
*** markvoelker has quit IRC01:04
*** ijw has quit IRC01:04
*** Swami has quit IRC01:04
*** ijw has joined #openstack-meeting01:07
*** cheng1 has joined #openstack-meeting01:09
*** ijw has quit IRC01:10
*** ijw has joined #openstack-meeting01:11
*** eharney has quit IRC01:19
*** jamesmcarthur has joined #openstack-meeting01:23
*** ijw has quit IRC01:24
*** yamamoto has joined #openstack-meeting01:24
*** ijw has joined #openstack-meeting01:25
*** yamamoto has quit IRC01:29
*** bbowen has quit IRC01:32
*** dmacpher_ has joined #openstack-meeting01:33
*** dmacpher has quit IRC01:34
*** tetsuro has joined #openstack-meeting01:35
*** tetsuro has quit IRC01:38
*** tetsuro has joined #openstack-meeting01:39
*** mriedem is now known as mriedem_afk01:39
*** ijw has quit IRC01:39
*** jamesmcarthur has quit IRC01:49
*** tetsuro has quit IRC01:53
*** hongbin has joined #openstack-meeting01:55
*** bbowen has joined #openstack-meeting01:56
*** ijw has joined #openstack-meeting01:56
*** tetsuro has joined #openstack-meeting01:57
*** tetsuro has quit IRC02:00
*** whoami-rajat has joined #openstack-meeting02:01
*** _hemna has quit IRC02:02
*** tetsuro has joined #openstack-meeting02:03
*** artom has joined #openstack-meeting02:04
*** tetsuro has quit IRC02:05
*** tetsuro has joined #openstack-meeting02:10
*** jgriffith has quit IRC02:11
*** ekcs has quit IRC02:16
*** ijw has quit IRC02:16
*** ijw has joined #openstack-meeting02:17
*** ijw has quit IRC02:18
*** ijw has joined #openstack-meeting02:19
*** zhubx007 has quit IRC02:24
*** mriedem_afk has quit IRC02:24
*** zhubx has joined #openstack-meeting02:24
*** zhubx has quit IRC02:25
*** zhubx has joined #openstack-meeting02:25
*** jamesmcarthur has joined #openstack-meeting02:25
*** mriedem has joined #openstack-meeting02:29
*** cheng1 has quit IRC02:35
*** ijw has quit IRC02:35
*** ijw has joined #openstack-meeting02:40
*** lbragstad has quit IRC02:44
*** macza has joined #openstack-meeting02:47
*** cheng1 has joined #openstack-meeting02:47
*** macza has quit IRC02:51
*** psachin has joined #openstack-meeting02:55
*** yamamoto has joined #openstack-meeting03:00
*** markvoelker has joined #openstack-meeting03:01
*** ijw has quit IRC03:03
*** ijw has joined #openstack-meeting03:06
*** ijw has quit IRC03:11
*** mriedem has quit IRC03:12
*** jamesmcarthur has quit IRC03:25
*** jamesmcarthur has joined #openstack-meeting03:28
*** hongbin has quit IRC03:33
*** tetsuro has quit IRC03:34
*** markvoelker has quit IRC03:35
*** jamesmcarthur has quit IRC03:36
*** jamesmcarthur has joined #openstack-meeting03:40
*** ijw has joined #openstack-meeting03:43
*** macza has joined #openstack-meeting03:44
*** jamesmcarthur has quit IRC03:45
*** macza has quit IRC03:48
*** sdake has joined #openstack-meeting03:49
*** sdake has quit IRC03:49
*** tpatil has joined #openstack-meeting03:50
*** imsurit_ofc has joined #openstack-meeting03:54
*** ijw_ has joined #openstack-meeting03:54
*** ShilpaSD has joined #openstack-meeting03:56
*** ijw has quit IRC03:56
*** yamamoto has quit IRC03:57
*** yamamoto has joined #openstack-meeting03:58
*** gyee has quit IRC03:58
*** yamamoto has quit IRC04:00
samP#startmeeting masakari04:01
openstackMeeting started Tue Feb 26 04:01:20 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPHi all for masakari04:01
samPtpatil: hi04:01
ShilpaSDHi all04:01
samP#topic critical bugs and patches04:02
*** openstack changes topic to "critical bugs and patches (Meeting topic: masakari)"04:02
tpatilLP Bug : 181694104:02
tpatil#link : https://bugs.launchpad.net/masakari/+bug/181694104:02
openstackLaunchpad bug 1816941 in masakari "Incorrect service_type passed for parsing micro-version from OpenStack-API-Version request header" [Critical,In progress] - Assigned to Shilpa Devharakar (shilpasd)04:02
tpatilPatch up for review:https://review.openstack.org/#/c/638352/04:03
tpatilbasically sdk and masakariclient doesn't have provision to send x-openstack-api-version request headers04:03
tpatilalso the service type should be instance-ha instead of masakari04:04
tpatilthe above patch fixes this issue04:04
samPtpatil: agree. patch is lgtm04:04
*** cheng1 has quit IRC04:04
samPtpatil: approved04:05
tpatiland patch https://review.openstack.org/#/c/638346/ adds support to send X-OpenStack-API-Version request header04:05
samPtpatil: thanks for bringing that up04:05
tpatilfor notification progress details feature, we want to add a new micro version 1.104:06
*** tashiromt has joined #openstack-meeting04:06
tpatilduring adding this micro version supports , we found out the above problem04:06
*** jamesmcarthur has joined #openstack-meeting04:07
*** sdake has joined #openstack-meeting04:07
samPtpatil: thanks for fixing those.04:07
samPI've just +2 the above patch.04:08
tpatilsamP: Ok, Thanks04:08
tpatil Run all jobs by default using python304:08
tpatil#link : https://review.openstack.org/#/c/637714/04:08
tpatilalready voted +2, need another04:08
tpatiland this one as well :https://review.openstack.org/#/c/637712/04:09
samPtpatil: yep, I already did04:09
samPtpatil: done.04:09
tpatilfor the remaining two patches, we will upload new PS soon04:10
samPtpatil: Thanks04:10
*** sdake has quit IRC04:10
tpatil#link : https://review.openstack.org/#/c/636749/04:11
tpatilThe above patch fails on py3.604:11
tpatilNeha has set above patch as dependent on one of her patch and you can see the py3.6 job is failing04:11
tpatilNeha's patch : https://review.openstack.org/#/c/637711/204:12
tpatilI will look into this issue sometime in this week04:12
*** sdake has joined #openstack-meeting04:12
*** sdake has quit IRC04:13
samPtpatil: I tried this patch in 18.04 and couldn't find a problem.04:13
*** SWDevAngel has quit IRC04:13
samPI will wait for your feedback04:13
tpatilit runs fine on 3.5 but it fails on 3.604:13
tpatilIn review 637711: we have added py3.6 env in tox04:14
tpatilsamP: Ok I will add a comment on the patch04:15
*** sdake has joined #openstack-meeting04:15
*** sridharg has joined #openstack-meeting04:15
samPtpatil: put a remark on the patch04:17
tpatilsamP: doing it right away04:17
tpatilsamP: Done04:18
samPtpatil: thanks04:18
samPThis is a blocker for ubuntu people to do the packaging. We better solve this sooner04:19
samPtpatil: thanks for the support04:20
tpatilsamP: yes04:20
samPany other patches or bugs?04:22
*** jamesmcarthur has quit IRC04:23
samPtpatil: Thanks04:23
samP#topic Stein work Items04:23
*** openstack changes topic to "Stein work Items (Meeting topic: masakari)"04:23
*** sdake has quit IRC04:23
samPAny update on Stein work items04:23
samPI have already approved the 2 spes04:23
tpatilsamP: Thank you04:24
tpatilneed review for patches : https://review.openstack.org/#/q/status:open+project:openstack/masakari+branch:master+topic:bp/notifications-in-masakari04:24
*** yamamoto has joined #openstack-meeting04:25
tpatilFunctional tests in Masakari04:25
samPtpatil: I will do that. sorry for the delay04:25
tpatilsamP: Ok04:26
tpatilFirst patch is up: https://review.openstack.org/#/c/633663/04:26
tpatilsince I have uploaded that patch, not voted +204:26
tpatilrequest other core reviewers to take a look at it04:26
*** yamamoto has quit IRC04:26
samPtpatil: thanks, I will do my review too04:26
tpatilin that patch ,we have added CI jobs and tests for segments04:27
tpatilworking on adding tests for hosts and notifications04:27
samPtpatil: thanks04:27
tpatilfor notifications, we will need tests for process and instance notifications04:28
tpatilhost notification will be done in the next cycle04:28
samPtpatil: got it. thanks04:28
tpatilAdd progress details for recovery workflow04:28
tpatilImplementation is in progress04:29
tpatilmasakari side changes are done but internal review is in progress04:29
tpatilmasakari-dashboard changes are done04:29
samPtpatil: thanks04:30
*** yamamoto has joined #openstack-meeting04:30
tpatilexcept one issue04:30
tpatilsome UI issue that needs to be resolved04:30
tpatilAdd devstack support for masakari-monitors04:32
tpatilpatch is up for review : https://review.openstack.org/#/c/638577/04:32
*** markvoelker has joined #openstack-meeting04:32
tpatilI have updated Neha verbally to fix some issue. I will post those issues on the patch as well04:33
tpatilonce she upload patch , I will review that patch soon04:33
samPtpatil: sure, thanks04:33
tpatilexcept host-monitors, all other monitors will be installed by the masakari devstack plugin04:33
tpatilThat's all update from my side about Stein work items04:34
samPtpatil: thanks. I will do the pending reviews04:35
samP#topic AOB04:35
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:35
samPThis week is the final release for non-client libraries04:36
samP#link https://releases.openstack.org/stein/schedule.html#s-final-lib04:36
samPtpatil: masakari-monitors is cycle-with-rc type04:38
tpatilok, then we don't need to worry about anything in this week, correct?04:38
samPtpatil: correct04:38
samPHowever, next week is the final release for python-masakariclient04:39
tpatilwe will need to add microversion 1.1 in python-masakariclient04:39
samPbefore that or in same time, I would like to release a new version for masakari-dashboard too04:39
tpatilbut we cannot add that support until masakari support 1.104:40
tpatilwe will upload patches by end of this week for notification progress details feature04:40
tpatilchanges are required in masakari, python-masakariclient and masakari-dashboard04:41
samPtpatil: got it.04:42
tpatilso we have only one week for review, will need your support in reviewing those patches04:42
samPtpatil: sure, please push the patches for python-masakariclient at your earliest04:43
tpatilsamP: will do, actually it's one line change04:43
samPtpatil: got it.04:44
tpatilbut I was holding those changes becoz masakari doesn't yet support 1.1 version, in that case it will give an error which I think is right thing to do. So will push that patch today04:45
tpatilI mean if you pass ha-api-version as 1.1 and if it's not supported masakari, it will give an error04:46
tpatilideally once the micro-version is support in services, it should be made available in client04:46
*** cheng1 has joined #openstack-meeting04:47
tpatilwe will set depends-on tag in python-masakariclient patch04:48
samPtpatil: agree. I thought python-masakariclient change is a huge one. That's why I asked to upload it first. However it is not. So we may follow the normal work flow04:48
tpatilbut it's not possible to merge python-masakariclient before masakari patch04:48
tpatilsamP: Ok04:48
samPtpatil: sure04:49
tpatilThat's all from my end04:49
samPtpatil: thanks04:49
samPHere is the release schedule for Stein.04:49
samP#link https://releases.openstack.org/stein/schedule.html04:50
tpatilMAr 04 - Mar 0804:50
samPIf no other items to discuss, we may finish today's meeting04:51
tpatilsamP: Ok04:51
samPOK then. Thank you!04:51
tashiromtthank you04:51
ShilpaSDthank you all04:51
samPplease use #openstack-masakari on IRC @freenode or openstack-discuss@lists.openstack.org for further discussions04:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:53
openstackMeeting ended Tue Feb 26 04:53:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-26-04.01.html04:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-26-04.01.txt04:53
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-26-04.01.log.html04:53
samPthanks all!04:53
*** lbragstad has joined #openstack-meeting04:53
*** _hemna has joined #openstack-meeting04:59
*** _hemna has quit IRC05:04
*** tpatil has quit IRC05:04
*** markvoelker has quit IRC05:05
*** vishalmanchanda has joined #openstack-meeting05:10
*** tashiromt has quit IRC05:23
*** janki has joined #openstack-meeting05:26
*** ijw_ has quit IRC05:57
*** markvoelker has joined #openstack-meeting06:03
*** tetsuro has joined #openstack-meeting06:14
*** igordc has quit IRC06:30
*** tetsuro has quit IRC06:31
*** markvoelker has quit IRC06:35
*** jchhatbar has joined #openstack-meeting06:43
*** janki has quit IRC06:45
*** Luzi has joined #openstack-meeting06:54
*** tetsuro has joined #openstack-meeting07:06
*** kopecmartin|off is now known as kopecmartin07:23
*** joxyuki has joined #openstack-meeting07:25
*** zhubx007 has joined #openstack-meeting07:33
*** zhubx has quit IRC07:33
*** aojea has joined #openstack-meeting07:35
*** zhubx007 has quit IRC07:35
*** zhubx has joined #openstack-meeting07:35
*** dkushwaha has joined #openstack-meeting07:36
*** lbragstad has quit IRC07:44
*** nirajsingh has joined #openstack-meeting07:45
*** rcernin has quit IRC07:56
*** hyunsikyang has joined #openstack-meeting08:01
*** tpatil has joined #openstack-meeting08:02
dkushwaha#startmeeting tacker08:02
openstackMeeting started Tue Feb 26 08:02:22 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
dkushwaha#topic Roll Call08:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:02
dkushwahawho is here for Tacker weekly meeting?08:02
*** bhagyashris has joined #openstack-meeting08:03
nirajsinghdkushwaha: hi08:03
dkushwahanirajsingh, hello08:03
hyunsikyanghell all08:03
dkushwahahi hyunsikyang08:03
hyunsikyangyou can call me hyunsik :)08:04
hyunsikyanghi joxyuki08:04
dkushwahahello joxyuki08:05
dkushwahaok lets start..08:07
nirajsinghdkushwaha: there is one update about https://review.openstack.org/#/c/622888/ patch, i will submitt the functional test patch today itself.08:07
dkushwaha#topic announcement08:07
*** openstack changes topic to "announcement (Meeting topic: tacker)"08:07
dkushwahawe have around 10 days left for stein cycle, so needs to hurry up08:08
dkushwaha#link https://releases.openstack.org/stein/schedule.html08:08
dkushwahai mean, Stein-3 milestone08:09
dkushwaha#topic announcement08:09
*** openstack changes topic to "announcement (Meeting topic: tacker)"08:09
dkushwahaCFP result is opne now08:10
dkushwahaThis time 3 Tacker related sessions are selected08:10
dkushwaha#link https://www.openstack.org/summit/denver-2019/summit-schedule/global-search?t=tacker08:10
dkushwahaHope to see max members in summit from Tacker team08:11
dkushwahamoving next..08:12
dkushwaha#topic BPs08:12
*** openstack changes topic to "BPs (Meeting topic: tacker)"08:12
dkushwahanirajsingh, thanks for the update.08:12
dkushwahawaiting for your patch08:12
nirajsinghdkushwaha: yes, thank you :)08:13
dkushwaha#topic force-delete support08:14
*** openstack changes topic to "force-delete support (Meeting topic: tacker)"08:14
dkushwahahttps://review.openstack.org/#/c/620385/ As it is pending in WIP, I will also start working on that08:15
dkushwahamay be by today08:15
dkushwahamoving next...08:16
dkushwaha#topic python3-first08:17
*** openstack changes topic to "python3-first (Meeting topic: tacker)"08:17
dkushwaha#link https://review.openstack.org/#/c/572984/08:17
*** Luzi has quit IRC08:18
dkushwahaeven after multiple tries, I am getting errors with py35, py3608:18
dkushwahai.e.: TypeError: object() takes no parameters08:18
dkushwahacan somebody help on fixing that?08:19
*** tpatil has quit IRC08:20
dkushwahaplease feel free if someone can look into that08:20
dkushwahamoving next..08:20
dkushwaha#topic Open Discussion08:21
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:21
dkushwahaDo you have something more to discuss?08:22
*** msimonin has quit IRC08:24
hyunsikyangI uploaded blueprint but, now we are busy to close the cycle of stein..08:24
hyunsikyangIf someone can review it, please review it:D08:26
dkushwahahyunsikyang, yea, as of now we have to focus on Stein, so we can prioritize after this08:26
hyunsikyangYes Good.08:26
dkushwahahyunsikyang, that will be great help if you can also contribute on bug fixes and patch review08:27
hyunsikyangOK:) I am testing the tacker now . i found some bugs... anyway.. it can't helps now.08:28
hyunsikyangOk I will try it08:28
dkushwahahyunsik Thanks08:29
dkushwahaOk, Thanks all, Nothing from my side.08:30
*** tssurya has joined #openstack-meeting08:30
dkushwahaIf no one has something more to discuss, we can close this meeting.08:30
dkushwahaok, Closing now08:31
dkushwahaThanks Folks for joining.08:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:32
openstackMeeting ended Tue Feb 26 08:32:08 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-26-08.02.html08:32
*** joxyuki has left #openstack-meeting08:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-26-08.02.txt08:32
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-26-08.02.log.html08:32
*** Luzi has joined #openstack-meeting08:32
*** markvoelker has joined #openstack-meeting08:32
*** pcaruana has joined #openstack-meeting08:35
*** electrofelix has joined #openstack-meeting08:37
*** cheng1 has quit IRC08:49
*** cheng1 has joined #openstack-meeting08:49
*** ttsiouts has joined #openstack-meeting08:49
*** jiaopengju has joined #openstack-meeting08:51
*** tetsuro has quit IRC08:57
*** ralonsoh has joined #openstack-meeting08:57
*** priteau has joined #openstack-meeting08:59
*** markvoelker has quit IRC09:06
*** ttsiouts has quit IRC09:07
*** ttsiouts has joined #openstack-meeting09:08
*** zhubx has quit IRC09:11
*** zhubx has joined #openstack-meeting09:12
*** ttsiouts has quit IRC09:13
*** ttsiouts has joined #openstack-meeting09:14
*** jchhatbar has quit IRC09:16
*** jchhatbar has joined #openstack-meeting09:16
*** cheng1 has quit IRC09:16
*** cheng1 has joined #openstack-meeting09:16
*** jchhatbar has quit IRC09:22
*** jchhatbar has joined #openstack-meeting09:23
jiaopengju#startmeeting karbor09:23
openstackMeeting started Tue Feb 26 09:23:20 2019 UTC and is due to finish in 60 minutes.  The chair is jiaopengju. Information about MeetBot at http://wiki.debian.org/MeetBot.09:23
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:23
*** openstack changes topic to " (Meeting topic: karbor)"09:23
openstackThe meeting name has been set to 'karbor'09:23
*** cheng1 has quit IRC09:23
jiaopengjuhi guys, we do not have any topics today09:24
jiaopengjuanyone here has something to discuss?09:24
jiaopengjuif not, I will end the meeting soon09:24
*** dklyle has quit IRC09:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:25
openstackMeeting ended Tue Feb 26 09:25:26 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-02-26-09.23.html09:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-02-26-09.23.txt09:25
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-02-26-09.23.log.html09:25
*** e0ne has joined #openstack-meeting09:25
*** dklyle has joined #openstack-meeting09:27
*** tbarron has quit IRC09:30
*** tssurya has quit IRC09:30
*** zhubx has quit IRC09:31
*** tssurya has joined #openstack-meeting09:31
*** bhagyashris has quit IRC09:52
*** yamamoto has quit IRC09:53
*** priteau has quit IRC09:57
*** priteau has joined #openstack-meeting09:59
*** markvoelker has joined #openstack-meeting10:03
*** priteau has quit IRC10:06
*** cheng1 has joined #openstack-meeting10:09
*** yamamoto has joined #openstack-meeting10:10
*** yamamoto has quit IRC10:21
*** cheng1 has quit IRC10:24
*** cheng1 has joined #openstack-meeting10:24
*** yamamoto has joined #openstack-meeting10:26
*** markvoelker has quit IRC10:36
*** erlon has joined #openstack-meeting10:48
*** dkushwaha has quit IRC10:54
*** zhubx has joined #openstack-meeting10:54
*** ttsiouts has quit IRC11:07
*** ttsiouts has joined #openstack-meeting11:08
*** ttsiouts has quit IRC11:12
*** yamahata has quit IRC11:25
*** zhubx has quit IRC11:30
*** zhubx has joined #openstack-meeting11:30
*** Adri2000 has quit IRC11:33
*** Adri2000 has joined #openstack-meeting11:34
*** imsurit_ofc has quit IRC11:39
*** psachin has quit IRC11:40
*** jamesmcarthur has joined #openstack-meeting11:44
*** Luzi has quit IRC11:54
*** Luzi has joined #openstack-meeting11:55
*** ttsiouts has joined #openstack-meeting12:08
*** yamamoto has quit IRC12:10
*** rfolco|rover has quit IRC12:11
*** rfolco|rover has joined #openstack-meeting12:11
*** janki has joined #openstack-meeting12:14
*** jchhatbar has quit IRC12:15
*** yamamoto has joined #openstack-meeting12:15
*** raildo has joined #openstack-meeting12:16
*** bbowen has quit IRC12:21
*** zhubx has quit IRC12:21
*** zhubx has joined #openstack-meeting12:21
*** janki has quit IRC12:24
*** janki has joined #openstack-meeting12:24
*** aojeagarcia has joined #openstack-meeting12:25
*** cheng1_ has joined #openstack-meeting12:26
*** cloudran_ has joined #openstack-meeting12:26
*** rf0lc0 has joined #openstack-meeting12:26
*** arne_wiebalck_ has joined #openstack-meeting12:27
*** dmellado_ has joined #openstack-meeting12:28
*** isq_ has joined #openstack-meeting12:28
*** janki has quit IRC12:29
*** beekneemech has joined #openstack-meeting12:29
*** nnsingh has joined #openstack-meeting12:30
*** diablo_rojo_ has joined #openstack-meeting12:30
*** _pewp_ has quit IRC12:30
*** cloudrancher has quit IRC12:30
*** armax has quit IRC12:30
*** gouthamr has quit IRC12:30
*** electrofelix has quit IRC12:30
*** cschwede has quit IRC12:30
*** nirajsingh has quit IRC12:30
*** haleyb has quit IRC12:30
*** kaisers has quit IRC12:30
*** cheng1 has quit IRC12:30
*** isq has quit IRC12:30
*** arne_wiebalck has quit IRC12:30
*** jiaopengju has quit IRC12:30
*** dosaboy has quit IRC12:30
*** dmellado has quit IRC12:30
*** rfolco|rover has quit IRC12:30
*** ralonsoh has quit IRC12:30
*** aojea has quit IRC12:30
*** diablo_rojo has quit IRC12:30
*** bnemec has quit IRC12:30
*** number80 has quit IRC12:30
*** arne_wiebalck_ is now known as arne_wiebalck12:30
*** dmellado_ is now known as dmellado12:30
*** _pewp_ has joined #openstack-meeting12:31
*** kaisers has joined #openstack-meeting12:32
*** gouthamr has joined #openstack-meeting12:33
*** markvoelker has joined #openstack-meeting12:33
*** number80 has joined #openstack-meeting12:33
*** rf0lc0 is now known as rfolco|rover12:33
*** jamesmcarthur has quit IRC12:34
*** jamesmcarthur has joined #openstack-meeting12:34
*** electrofelix has joined #openstack-meeting12:35
*** ralonsoh has joined #openstack-meeting12:36
*** ralonsoh has quit IRC12:41
*** ralonsoh has joined #openstack-meeting12:42
*** mriedem has joined #openstack-meeting12:50
*** ttsiouts has quit IRC12:51
*** ttsiouts has joined #openstack-meeting12:51
*** jamesmcarthur has quit IRC12:52
*** ttsiouts has quit IRC12:56
*** jamesmcarthur has joined #openstack-meeting12:57
*** ttsiouts has joined #openstack-meeting13:03
*** arne_wiebalck has quit IRC13:05
*** markvoelker has quit IRC13:06
*** arne_wiebalck has joined #openstack-meeting13:07
*** Adri2000 has quit IRC13:08
*** sdake has joined #openstack-meeting13:15
*** jrbalderrama has joined #openstack-meeting13:27
*** bbowen has joined #openstack-meeting13:28
*** liuyulong has joined #openstack-meeting13:30
*** jamesmcarthur has quit IRC13:35
*** jamesmcarthur has joined #openstack-meeting13:39
*** liuyulong has quit IRC13:40
*** jamesmcarthur has quit IRC13:40
*** jamesmcarthur has joined #openstack-meeting13:40
*** yamamoto has quit IRC13:40
*** yamamoto has joined #openstack-meeting13:40
*** _hemna has joined #openstack-meeting13:41
*** haleyb has joined #openstack-meeting13:49
*** davidsha has joined #openstack-meeting13:51
*** dosaboy has joined #openstack-meeting13:51
*** enriquetaso has joined #openstack-meeting13:52
*** _hemna has quit IRC13:54
*** mjturek has joined #openstack-meeting13:56
*** lajoskatona has joined #openstack-meeting13:57
*** tidwellr has joined #openstack-meeting13:57
*** boden has joined #openstack-meeting13:58
*** beekneemech is now known as bnemec13:59
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Feb 26 14:00:16 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
mlavalleHow are y'all?14:01
njohnstonmlavalle: Splendid, and you?14:02
mlavallelet's get going14:02
mlavalle#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
mlavalleWe almost made it to the end of the Stein cycle14:03
mlavalleOur Stein-3 milestones is next week14:03
*** zaneb has quit IRC14:04
mlavalleAlso, for those of you planning to attend the Summit in Denver, please remember that this week is the end of the "earlybird" registration period14:05
mlavalleThat includes your contributos discount codes14:05
*** liuyulong has joined #openstack-meeting14:05
mlavalledon't let the price hike catch you by surprise14:05
* mlavalle registered last week and made hotel / air reservations14:05
amotokiprecisely speaking, the deadline is February 27, 2019 at 11:59pm PST14:06
mlavalleso that's tomorrow14:06
* slaweq registered to PTG only already14:06
mlavalleFinally, please remember that there is a TC election going on14:07
mlavallefollow the questions and be ready to cast your votes14:07
*** zaneb has joined #openstack-meeting14:07
mlavalleany other annoucements?14:08
amotokialthough the next week is stein-3, we cut stein beta for neutron stadium.14:08
amotokiI originally thought we can discuss it here, but it has been merged a bit ago14:09
amotokiwe can align our deliverables in Stein together :)14:09
mlavalleso what follows amotoki in terms of deliverables?14:10
mlavallethe final deliverables after feature freeze?14:11
mlavalleamotoki: ^^^^14:11
amotokii think we will also cut Stein-3 next week14:11
amotokithe above patch does not include networking-ovn/odl/bgpvpn/bagpipe14:11
mlavalleok, cool14:11
amotokiI believe we will have stein-3 for all of stadium projects next week14:11
mlavallelet's move on14:12
mlavalle#topic Blueprints14:12
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:12
mlavalleThese are the blueprints that we are tracking https://launchpad.net/neutron/+milestone/stein-314:13
tidwellrmlavalle: subnet onboard is ready to go, thanks goes to Mike Bayer for helping get https://review.openstack.org/#/c/348080/ over the hump with the DB enginefacade issues14:14
mlavalleAs suggested last week by slaweq< i raised the priority of blueprints that require attention14:14
njohnstonFor bulk ports, I think https://review.openstack.org/#/c/624815/ is very very close.  But slaweq noticed that the OVN test job had a few failures, so I am investigating that.14:14
mlavalletidwellr: you had a faulure in a tox job14:15
tidwellrthe lower-contstraints job, which I thought was a widespread thing....14:16
tidwellrI'll rebase and see where it's at14:16
mlavalleadded it to the reviews I have to do over the next couple of days14:16
mlavallenjohnston: I'll also keep an eye on yours14:17
njohnstonmlavalle: thanks!14:17
mlavalleThanks tidwellr and njohnston for your hard work14:17
mlavallelajoskatona: anything to say on https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support?14:18
lajoskatonawe have still a few patches for review, I think the most critical is the batch of rubasov's: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open++owner:%22Bence+Romsics+%253Cbence.romsics%2540ericsson.com%253E%2214:19
*** enriquetaso has quit IRC14:19
lajoskatonamlavalle: and I have a batch in various projects (tempest, novaclient....): https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+status:open++owner:%22Lajos+Katona+%253Clajos.katona%2540ericsson.com%253E%2214:19
mlavallelajoskatona: do we only need review attention? or is there anything else missing?14:20
lajoskatonaThose are not mandatory for the feature (perhaps the one in novaclient is the exception)14:20
lajoskatonamlavalle: yeap that would be good to push the few remaining patch to go in14:20
amotokilajoskatona: how is novaclient related to this blueprint? do we have some change in nova side?14:21
lajoskatonaamotoki: in nova there will be a new compute microversion (2.70 as of now) and to boot VM we have to enable that in novaclient14:21
*** sdake has quit IRC14:21
mlavallethat's what super gibi has been working on14:22
*** _hemna has joined #openstack-meeting14:22
lajoskatonaamotoki: without that you cannot boot from CLI, of course that is nova area, but anyway14:22
lajoskatonamlavalle: exactly14:22
amotokilajoskatona: thanks for clarification!14:22
lajoskatonaamotoki: your welcome14:22
mlavalleIn regards to https://blueprints.launchpad.net/neutron/+spec/network-segment-range-management14:23
*** cheng1_ has quit IRC14:23
*** cheng1_ has joined #openstack-meeting14:23
mlavalleI spent time revieiwing the patches:14:24
mlavallethanks slaweq and liuyulong for merging the last one14:25
mlavalleliuyulong and I made comments on the first two14:25
slaweqthis was the easy one :)14:25
mlavalleIMO, after addressing those comments, they will be ready14:26
mlavalleliuyulong: what do you think?14:26
liuyulongThere are very positive feedback from Kailun Qin, I think it is very close.14:26
mlavalleslaweq: yeah, the first one is massive. I spent a whole Saturday afternoon looking at it14:27
mlavalleok, let's go over them again and approve if they are ready14:28
slaweqI will also go to them this week14:28
mlavallethanks slaweq, liuyulong!14:28
mlavalleI think we are in good shape in the blueprints we are targeting for Stein-314:29
mlavalledavidsha: have you heard of our compadres xubozhang and igor in regards to https://blueprints.launchpad.net/neutron/+spec/openflow-based-dvr?14:30
*** enriquetaso has joined #openstack-meeting14:30
davidshaThey're still working on them, but no update besides that I'm afraid, last time I was talking to them was last Monday.14:31
mlavalledavidsha: can I ask you a favor? Please make sure they realize we have moved the L3 meeting to Wednesday 1400 utc14:32
davidshaI've let Xubo know already, I'll email Igor now.14:32
mlavalledavidsha: thanks!14:32
mlavalleanything else on blueprints?14:32
*** sdake has joined #openstack-meeting14:33
mlavalle#topic Community goals14:34
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:34
mlavalleDo we have anything to say about python3?14:34
slaweqnot too much14:35
slaweqregarding neutron, last job to switch is neutron-tempest-dvr-ha-multinode job14:35
njohnstonI pushed a change to use python 3 for a few jobs for ovsdbapp14:35
slaweqpatch is here https://review.openstack.org/#/c/638626/14:35
njohnstonI will be taking a sweep of stadium projects to look at the state of things.  Obviously the autogenerated mass-push changes took care of unit tests but checking for functiona, fullstack, etc.14:36
mlavalleis it good to go?14:36
slaweqmlavalle: which one? thix https://review.openstack.org/#/c/638626/ ?14:36
mlavalleyes, asking about that one14:37
slaweqyes, it's good to go14:37
mlavallethanks njohnston!14:38
slaweqstill as legacy job but with py314:38
mlavalleok, let's move on14:38
mlavalle#topic Bugs14:38
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:38
*** mjturek has quit IRC14:38
mlavalleLast week, the deputy was zhaobo. I pinged him in WeChat and he responded that he was working on it14:38
mlavalledid anybody see a report from him?14:39
slaweqI didn't14:39
mlavalleI don't find anything in the discuss list14:39
*** cheng1_ has quit IRC14:39
mlavallenor my inboxes14:40
*** lbragstad has joined #openstack-meeting14:40
*** cheng1_ has joined #openstack-meeting14:40
amotokime either14:41
* mlavalle looking at https://bugs.launchpad.net/neutron/+bugs?orderby=-datecreated&start=014:41
mlavalleIt seems that over the past week, evrything High is in progress14:42
mlavalle3 fwaas / octavia bugs that need triaging14:43
amotokiI will take care of them. ocatavia bugs need to be forwarded to storyboard14:44
bodeni also have one bug that may be worth noting if we have time14:44
mlavalleI will triage https://bugs.launchpad.net/neutron/+bug/181721914:44
openstackLaunchpad bug 1817219 in neutron "Failed to list security group tags" [Undecided,New]14:44
mlavalleboden: please go ahead14:44
openstackLaunchpad bug 1816644 in Tricircle "tempest-dsvm jobs don't pull required projects from source" [Undecided,New]14:44
bodenso it seems a handful or consumers that use "required projects" (aka "siblings") with legacy devstack based jobs are broken14:45
bodenlong story short, I have a solution, but IMO it's not a good one... trying to get QA to engauge, but has been slow14:45
bodenthose impacted projects have broken jobs (IIUC) until we resolve this14:46
mlavalleboden: is there anything I / we can help with?14:46
*** eharney has joined #openstack-meeting14:46
bodenmlavalle well if we could get someone from QA to look at https://bugs.launchpad.net/tempest/+bug/1817555 it might help14:46
openstackLaunchpad bug 1817555 in tempest "No way to pull requirements from source in devstack jobs" [Undecided,New]14:46
mlavalleboden: ok, I'll ping them today14:47
bodenmlavalle thanks14:47
amotokiboden: you can ask gmann14:47
bodenamotoki I have14:47
bodenno response yet14:47
amotokihe recently moved to Canada last week, so he might be busy somehow..14:48
gmannboden: i will check, it is legacy job issue ?14:48
bodengmann yes14:48
*** enriquetaso has quit IRC14:48
bodengmann I sent you an email not too long ago :)14:48
gmannamotoki: morning time here so I am ok :)14:48
mlavallegmann: https://bugs.launchpad.net/tempest/+bug/181755514:48
openstackLaunchpad bug 1817555 in tempest "No way to pull requirements from source in devstack jobs" [Undecided,New]14:48
amotokiregarding this, I cut networking-sfc stein b1, so we can change requirements14:49
amotokiit might help us14:49
gmannboden: mlavalle  sure, I will check and get back.14:49
mlavallegmann: thanks!14:49
mlavalleok, our deputy this week is manjeets14:49
mlavallehe sent me an ack in the Neutron channel, so he is aware14:50
mlavallelet's move on14:50
mlavalle#topic neutron-lib14:50
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:50
mlavalleboden: we already covered on of your topics14:50
mlavalleplease go ahead with the second one14:50
*** mjturek has joined #openstack-meeting14:50
bodenwe need to release neutron-lib for stein14:51
bodenlike today :)14:51
slaweq+1 :)14:51
amotokiI just proposed a patch neutron-lib 1.25.0 https://review.openstack.org/#/c/639255/14:51
bodenare there other patches we need?14:51
bodenI was hoping for https://review.openstack.org/#/c/639117/, but no biggie14:51
bodenI also say https://review.openstack.org/#/c/635907/14:51
mlavallewell, I might try to get one in myself14:51
slaweqwhat about this one https://review.openstack.org/#/c/636990/ ?14:52
slaweqshould we get it in also?14:52
slaweqit's related to segments range management14:52
bodenslaweq it depends on neutron patch14:52
bodencould take awhile like that14:52
*** mjturek has quit IRC14:52
slaweqbut now I'm not sure if that depends on is correct14:53
mlavalleboden: what is the absolute drop-dead deadline to release?14:53
mlavalleThursday, like you suggested in your email?14:53
bodenmlavalle I thought tomorrow, but I'm not sure if that's drop-dead14:53
mlavalleamotoki: what do you think?14:53
amotokiIIUC Thursday is the final deadline14:53
mlavalleok, let's the 3 of us touch base at the end of day tomorrow and see where we stand14:54
mlavalleI'll ping you14:54
mlavalleis that ok?14:54
bodenmlavalle ok.. let's try not to push the timeline too much :)14:54
amotokilet's update https://review.openstack.org/#/c/639255/ if we have more commits to be included.14:54
bodenamotoki ack14:54
mlavalleamotoki: ack. Thanks!14:54
bodensorry, but I have to run guys...14:55
*** sdake has quit IRC14:55
*** _hemna has quit IRC14:55
mlavalle#topic On demand agenda14:55
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:55
mlavalleamotoki: we covered what you wanted to discuss, right?14:55
amotokimlavalle: yes14:55
njohnstonWe should probably bring up gmann's mail about the legacy zuul job bionic transition: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003129.html14:56
njohnstonNeutron and neutron-lib are in a good state I thing; the issue here is the stadium14:57
*** awaugama has joined #openstack-meeting14:57
lajoskatonamlavalle: you mentioned few weeks ago a pad for possible update checks, I am not sure if I missed it, and cant find it in my mailbox14:57
gmannnjohnston: thanks, it will be good if someone from neutron team can start testing patches and add those in this etherpad - https://etherpad.openstack.org/p/legacy-job-bionic14:57
slaweqI can work on it14:58
mlavallenjohnston: do we need a volunteer?14:58
mlavalleslaweq: Thanks!14:58
mlavallelajoskatona: I'll ping you later in channel14:58
lajoskatonamlavalle: thanks14:58
mlavalleok, thanks for attending14:59
mlavallehave a great week!14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Tue Feb 26 14:59:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-26-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-26-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-26-14.00.log.html14:59
*** shintaro has joined #openstack-meeting14:59
*** sdake has joined #openstack-meeting15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Feb 26 15:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
ralonsohhello everyone!15:00
mlavalleralonsoh: I won't be able to attend today15:01
ralonsohmlavalle, np15:01
*** mlavalle has left #openstack-meeting15:01
ralonsohok, the quorum is quite low today15:02
ralonsohperfect, one more folk15:02
ralonsohok, let's start15:02
liuyulongI'm here15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:03
*** hongbin has joined #openstack-meeting15:03
*** mjturek has joined #openstack-meeting15:03
ralonsohI would prefer to wait for rubasov or lajoskatona15:03
ralonsohso I'll start with this one15:03
*** mjturek has quit IRC15:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/177762715:03
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:03
ralonsoh#link https://review.openstack.org/#/c/613820/15:03
ralonsohsome comments still pending15:03
ralonsohbecause Miguel is not attending, I'll call him later15:04
ralonsohnext one15:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:04
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:04
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:minimum-bandwidth-allocation-placement-api15:04
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider15:04
ralonsoh#link https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+project:openstack/tempest15:04
ralonsohlet me focus on the Neutron patches15:04
ralonsohmost of them with +W15:05
lajoskatonaralonsoh: yeah as previously I said the most critical ones are from rubasov15:05
*** mjturek has joined #openstack-meeting15:05
ralonsohlajoskatona, in Nova15:05
*** ijw has joined #openstack-meeting15:05
lajoskatonaralonsoh: as I know in nova the patches are progressing, perhaps 5 is still under review to have the basic functionality ready in stein15:06
lajoskatonaralonsoh: that means to boot/delete  VMs and detach interfaces with ports with min bw15:06
ralonsohlajoskatona, I've follow those ones, yes15:07
ralonsohralonsoh, I'm not a Nova reviewer but I'll give a try to those ones15:07
ralonsohto speedup the reviews15:07
*** markvoelker has joined #openstack-meeting15:07
lajoskatonaralonsoh: thanks15:07
ralonsohFor the record: those 2 Neutron patches need reviews15:07
ralonsoh#link https://review.openstack.org/#/c/580672/15:07
ralonsoh#link https://review.openstack.org/#/c/574783/15:08
lajoskatonaralonsoh: exactly, thanks for linking them.15:08
lajoskatonaralonsoh: rubasov started to work on documentation, and I am working on tests15:08
ralonsohlajoskatona, tempest (for the records) https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+project:openstack/tempest15:09
lajoskatonaso I suppose this week there will be patch(es) for documenting the feature15:09
ralonsohlajoskatona, cool, mostly on Neutron, is that right?15:09
*** mjturek has quit IRC15:09
lajoskatonaralonsoh: yeah, I think I will ping QA guys for review.15:09
lajoskatonaralonsoh: yes15:10
slaweqlajoskatona: I will review it too15:10
lajoskatonaslaweq: thanks15:10
ralonsohlajoskatona, any blocker/stopper/something else?15:10
*** jamesmcarthur has quit IRC15:11
lajoskatonaralonsoh: I think nothing. We hoped to be readye much before the stein freeze but hope that it will go through15:11
*** jamesmcarthur has joined #openstack-meeting15:11
davidshaI think tomorrow is the freeze15:11
davidshait was mentioned in the last meeting I think15:12
ralonsohdavidsha, yes, it's tomorrow, but we can always ask for an extension15:12
ralonsohfor specific features15:12
ralonsohlajoskatona, thank you very much (and ruabsov)15:13
*** ttsiouts has quit IRC15:13
*** eharney has quit IRC15:13
ralonsohLast one15:13
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:13
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:13
ralonsoh#link https://review.openstack.org/#/q/topic:bug/1560963+(status:open)15:13
ralonsohmost of the patches are merged15:13
*** ttsiouts has joined #openstack-meeting15:13
ralonsohjust one with +2 for the pyroute changes15:14
ralonsohand, of course, the bug one is still there (without reviews)15:14
ralonsohI'll start, next week, coding the tunnelled interfaces patch15:14
*** eharney has joined #openstack-meeting15:15
ralonsohon top of the big one (for physical bridges)15:15
ralonsohand that's all for me15:15
*** jamesmcarthur has quit IRC15:15
ralonsohany other comment in this topic? RFEs15:15
ralonsohok, let's move15:16
ralonsoh#topic Bugs15:16
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:16
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:16
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Medium,In progress]15:16
ralonsoh#link: https://review.openstack.org/#/c/596637/15:16
*** e0ne has quit IRC15:16
ralonsohAs commented last week, I can't reproduce the problem spotted out in the bug15:16
*** Luzi has quit IRC15:17
ralonsohSo I recommended to abandon this patch, but still waiting15:17
ralonsohI'll remove it from the list of bugs next week15:17
ralonsohnext one15:17
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178400615:17
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:17
*** ttsiouts has quit IRC15:18
ralonsohBecause Miguel is not here, we'll wait until he start the development (or maybe I'll ask him to take this one).15:18
ralonsohI'll ping him later15:18
ralonsoh(or anyone else, if you have time, for sure)15:19
*** rubasov has joined #openstack-meeting15:19
ralonsohlast one15:19
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181561815:19
openstackLaunchpad bug 1815618 in neutron "cannot update qos rule" [High,In progress] - Assigned to Lajos Katona (lajos-katona)15:19
rubasovlate o/15:19
ralonsohrubasov, no problem15:19
ralonsohrubasov, if you have comments on the RFE, you can talk in the open discussion15:19
ralonsoh(in 5 mins)15:20
ralonsohlajoskatona, I wrote a couple of comments on the patch15:20
lajoskatonaralonsoh: for the bug: I will check your comments,15:20
ralonsohIMO (just my opinion), it's cleaner if you just update the check_rules_conflict method15:20
ralonsohbut anyway, the bug is addressed and you found the problem, what is great15:21
lajoskatonaralonsoh: I check it, thanks for reviewing15:21
ralonsohI don't have more bugs in the list15:21
ralonsohAm I missing something?15:22
*** jgriffith has joined #openstack-meeting15:22
ralonsoh#topic Open Discussion15:22
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:22
ralonsohrubasov, do you have any topic?15:23
rubasovralonsoh: no I don't15:23
davidsharalonsoh: ok if I give a quick update on the neutron-classifier qos POC?15:24
ralonsohdavidsha, yes, I was going to ping you15:24
davidshaI got the database base migration script to use the classification-id and the policy-id as a unique key tuple, thanks for linking me to the directional example for bw-limit!15:25
ralonsohhehehe you are welcome15:25
davidshaIt works for classification-id = None as well so it's backwards compatible as well.15:25
*** ijw has quit IRC15:26
davidshaI've also started into propagating the classification to the L2-agent but thats a little less refined at the moment15:26
ralonsohdavidsha, perfect, that was my concern last day15:26
*** jamesmcarthur has joined #openstack-meeting15:27
ralonsohdavidsha, one question, about the RPC modifications15:27
ralonsohdavidsha, how are you going to handle it?15:27
davidshaI should have the next PS up soon, just running pep8 atm, I have the QoS driver listening for the topics at the moment, but was thinking of using the new classifier l2 extension to add the classification to a dict in the agent extensions API15:28
ralonsohdavidsha, you are going to add new RPC callbacks to the mech drivers15:28
ralonsohdavidsha, " I have the QoS driver listening" hahahaha15:28
ralonsohthe point is this should be an extension, only loaded if enabled15:28
ralonsohperfect, just to be aligned15:29
ralonsohbtw, only for L2? or L3 too is needed15:29
*** boden has left #openstack-meeting15:29
davidshaI added it just to make sure it was broadcasting, was already looking into adding it to the extensions API ;P15:29
davidshaatm only L2, but I can duplicate the work from L2 to L3, they are both made symmetrical in their extension APIs15:30
*** jamesmcarthur has quit IRC15:30
ralonsohbecause so far there are no L2/L3 shared extensions15:31
davidshaqos is, isn't it?15:31
davidshait has FIP bw limit15:31
ralonsohyes, but with different interfaces15:31
davidshakk, I think FWaas might have both15:32
ralonsohit's not possible to have a single interface for both15:32
ralonsohdo you have any patch upstream?15:33
davidshaI have patches, just waiting on pep8 before upstreaming them15:33
ralonsohany other update?15:34
davidshaIt's these: https://review.openstack.org/#/c/636330/ https://review.openstack.org/#/c/636333/15:34
*** ttsiouts has joined #openstack-meeting15:34
davidshaNope, thats me, thanks!15:34
ralonsohI'll add both to the etherpad15:34
ralonsohthank you15:35
ralonsohany other update from you folks?15:35
ralonsohThank you very much for attending15:36
ralonsohsee you in two weeks15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:36
openstackMeeting ended Tue Feb 26 15:36:19 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-26-15.00.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-26-15.00.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-26-15.00.log.html15:36
*** yamamoto has quit IRC15:37
*** markvoelker has quit IRC15:37
*** yamamoto has joined #openstack-meeting15:38
*** yamamoto has quit IRC15:38
*** yamamoto has joined #openstack-meeting15:39
*** yamamoto has quit IRC15:39
*** jamesmcarthur has joined #openstack-meeting15:39
*** rubasov has left #openstack-meeting15:40
*** enriquetaso has joined #openstack-meeting15:43
*** shintaro has quit IRC15:45
*** lajoskatona has left #openstack-meeting15:45
*** hongbin has quit IRC15:48
*** e0ne has joined #openstack-meeting15:53
*** vishakha has joined #openstack-meeting15:53
*** sdake has quit IRC15:59
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Feb 26 16:00:07 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** mlavalle has joined #openstack-meeting16:00
slaweqok, lets start then16:01
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqfirst one was:16:02
slaweqslaweq to fix patch with skip_if_timeout decorator16:02
*** sdake has joined #openstack-meeting16:02
slaweqIt is working fine, failed test in http://logs.openstack.org/92/636892/1/gate/neutron-functional/85da30c/logs/testr_results.html.gz was PgSQL test which isn’t marked with this decorator. Now patch is merged and new decorator should be used for some mysql tests16:02
*** ijw has joined #openstack-meeting16:03
slaweqnext one was:16:03
slaweqslaweq to split patch https://review.openstack.org/633979 into two: zuulv3 and py3 parts16:03
slaweqit's done16:03
slaweqpython3 patch: https://review.openstack.org/63862616:04
slaweqand https://review.openstack.org/#/c/633979/ is only for migraton from legacy to zuulv3 job16:04
slaweqone funny thing about this job neutron-tempest-dvr-ha-multinode-full16:04
slaweqit has "ha" in the name so I assumed that it should have l3_ha=True and test HA routers16:05
slaweqbut it don't have it like that16:05
slaweqso it's in fact something like neutron-tempest-dvr-multinode-full job currently16:05
slawequnless I missunderstood it and HA in the name is for something else16:05
slaweqdo You know maybe?16:05
mlavalleI thinl that's fine16:06
mlavallemaybe haleyb know why16:06
haleybyes, it should be testing dvr+ha16:06
njohnstonthat is so weird16:07
*** jrbalderrama has quit IRC16:07
slaweqok, so I have some problems with it and it's failing when I added l3_ha=True to neutron config16:07
slaweqI will continue digging into this one :)16:07
slaweqand I will switch it to zuulv3 with HA set properly :)16:07
*** macza has joined #openstack-meeting16:08
slaweqok, lets move on then16:08
slaweqnext one was16:08
slaweqnjohnston to ask stadium projects about python3 status16:08
*** tssurya has quit IRC16:09
njohnstonyeah, I have not done that; when I started to check I realized that many projects might way that they were fine because they merged the autogenerated changes, without thinking about functional/fullstack/etc.16:09
njohnstonSo I started to do a sweep of those jobs to see how many there were; that is what I am working on right now.  That way I can provide targeted feedback.16:09
slaweqnjohnston: do You have any list of stadium projects which we should take care of?16:10
slaweqnjohnston: maybe You can create etherpad similar to https://etherpad.openstack.org/p/neutron_ci_python3 or add it to the bottom of this one?16:11
njohnstonI'll put the results in an etherpad; mlavalle I may need your help in corralling members of specific projects that I don't know the contact folks for16:11
slaweqnjohnston: thx16:11
mlavallenjohnston: we'll go after them. np16:11
slaweq#action njohnston to create etherpad with python3 status of stadium projects16:11
njohnstonslaweq: The official list of stadium projects is here I believe: https://governance.openstack.org/tc/reference/projects/neutron.html16:11
mlavallenjohnston: THAt is correct16:12
slaweqnjohnston: thx16:12
*** Adri2000 has joined #openstack-meeting16:13
slaweqok, lets move on then16:13
slaweqnext one was: mlavalle to check bug https://bugs.launchpad.net/neutron/+bug/181648916:14
openstackLaunchpad bug 1816489 in neutron "Functional test neutron.tests.functional.agent.l3.test_ha_router.LinuxBridgeL3HATestCase. test_ha_router_lifecycle failing" [High,Confirmed]16:14
mlavalleso I got feedback in https://review.openstack.org/#/c/63671016:14
mlavallewhich I greed with16:14
slaweqmlavalle: but it's different bug ;)16:15
mlavalleI didn't have time to work on this one16:15
slaweqsure, no problem16:16
slaweqI can try to take it from You if You don't mind16:16
mlavalleno, go ahead16:16
slaweqI recently looked into some functional tests issues so I can do this also16:16
slaweq#action slaweq to check bug https://bugs.launchpad.net/neutron/+bug/181648916:16
openstackLaunchpad bug 1816489 in neutron "Functional test neutron.tests.functional.agent.l3.test_ha_router.LinuxBridgeL3HATestCase. test_ha_router_lifecycle failing" [High,Confirmed]16:16
slaweqand the last one was16:17
slaweqslaweq to check bug https://bugs.launchpad.net/neutron/+bug/181558516:17
openstackLaunchpad bug 1815585 in neutron "Floating IP status failed to transition to DOWN in neutron-tempest-plugin-scenario-linuxbridge" [High,Confirmed]16:17
slaweqI was looking into this one16:17
slaweqand it looks strange for me16:17
slaweqI described everythning in bug comments16:17
slaweqplease read it if You will have some time16:17
mlavalleok, will do16:18
slaweqbut basically what looks strange for me is that port don't have device_id but is active16:18
slaweqhow is that possible? do You know?16:18
*** sdake has joined #openstack-meeting16:18
mlavalleare we going to talk about https://bugs.launchpad.net/neutron/+bug/179587016:18
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,In progress] - Assigned to Miguel Lavalle (minsel)16:18
slaweqmlavalle: yes, I wanted to ask about it in tempest/scenario topic16:19
mlavallelet's do it that way16:19
slaweqbut we can talk about it now if You want :)16:19
mlavalleno, I'll follow your guidance16:19
*** yamamoto has joined #openstack-meeting16:19
slaweqok, thx16:19
slaweqso, please read my comments in https://bugs.launchpad.net/neutron/+bug/1815585 - maybe You will have some ideas about it16:20
openstackLaunchpad bug 1815585 in neutron "Floating IP status failed to transition to DOWN in neutron-tempest-plugin-scenario-linuxbridge" [High,Confirmed]16:20
slaweqit's not hitting us very often so it's not urgent issue IMO16:20
*** belmoreira has quit IRC16:20
slaweqbut would be good to fix it somehow :)16:20
slaweqany questions/comments on actions from last week? or can we move on to the next topic?16:21
mlavallenot from me16:21
slaweqok, lets move on then16:21
slaweq#topic Python 316:21
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:21
slaweqwe already spoke about stadium projects16:22
slaweqregarding neutron, we have only switch of neutron-tempest-dvr-ha-multinode-full missing16:22
slaweqpatch is ready https://review.openstack.org/63862616:22
slaweqlater we will have to switch experimental jobs to python316:23
slaweqbut that may be hard as some of them are probably broken already :/16:23
slaweqso we will have to fix them first16:23
njohnstonjust for completeness with the stadium, here is the change I did to get ovsdbapp ready: https://review.openstack.org/#/c/637988/16:24
njohnstonif there are low hanging fruit I'll just take care of it, like I did there16:24
*** yamamoto has quit IRC16:24
slaweqthx njohnston :)16:24
slaweqany other questions/comments related to python 3?16:25
mlavallenot from me16:25
*** sdake has quit IRC16:25
*** zhubx007 has joined #openstack-meeting16:25
slaweqok, so next topic then16:26
slaweq#topic Ubuntu Bionic in CI jobs16:26
*** openstack changes topic to "Ubuntu Bionic in CI jobs (Meeting topic: neutron_ci)"16:26
slaweqI just wanted to mention this email from gmann http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003129.html16:26
slaweqI already pushed test job for neutron https://review.openstack.org/#/c/639361/16:26
slaweqlets see how it will work16:26
mlavallethis is the same one we discussed earlier in the Neutron meeting, right?16:26
slaweqmlavalle: correct16:27
slaweqother thing here is again status of stadium projects16:27
slaweqI will try to push such test patches to each of them tomorrow16:27
njohnstonHow do we want to handle the stadium for this?  That seems like the long pole in the tent, so to speak.16:27
*** sdake has joined #openstack-meeting16:27
slaweqand we will see how it will work16:27
njohnstonsorry, laggy irc client :-)16:27
*** zhubx has quit IRC16:28
mlavallelaggy! new word for me16:28
slaweqnjohnston: I think I will first try with test patches and then we will see what will be to fix there16:28
slaweqnjohnston: mlavalle do You agree?16:28
mlavalleyes, that makes sense16:28
njohnstonsounds good16:28
slaweq#action slaweq to create bionic test patches for stadium projects16:29
slaweqok, so that's all about Bionic16:29
slaweqcan we move on?16:29
njohnstonfor networking-bagpipe make sure your change is a child of https://review.openstack.org/#/c/636154/16:30
slaweqnjohnston: ok, thx for info16:30
slaweq#topic Grafana16:30
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:30
mlavallelaggy browser16:31
mlavallegot to practice my new word16:31
*** wwriverrat has joined #openstack-meeting16:32
*** pcaruana has quit IRC16:32
slaweqthere is one significant spike recently on openstack-tox-lower-constraints16:33
slaweqbut that should be fixed with  https://review.openstack.org/#/c/639074/16:33
mlavallethat's the only big anomaly in grafana16:33
njohnstonI was wondering, why do we think the neutron-functional-python27 job has double the failure rate of the regular neutron-functional job in the check queue?  That seems weird to be since they run the same tests.16:34
slaweqand other anomaly is that neutron-tempest-plugin-dvr-multinode-scenario job wasn't failing 100% of time :D16:34
*** wwriverrat has left #openstack-meeting16:34
slaweqbut only for short while and now it's back to normal :P16:34
*** markvoelker has joined #openstack-meeting16:35
*** sdake has quit IRC16:35
slaweqbut more seriously, we have some problems with functional jobs I think - it's failing around 20-30% of times16:35
slaweqbut there are couple of bugs identified already16:35
slaweqso I hope it will be better when we will merge patches for that16:35
slaweqregarding to grafana, I also pushed today small patch  https://review.openstack.org/639321 to move openstack-tox-lower-constraints to unit jobs graph16:36
slaweqplease review and +1 if You are fine with that :)16:36
*** zhubx007 has quit IRC16:36
*** zhubx007 has joined #openstack-meeting16:37
*** sdake has joined #openstack-meeting16:37
slaweqthx njohnston16:37
slaweqok, lets move on then16:37
slaweq#topic fullstack/functional16:37
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:37
slaweqthx mlavalle16:37
slaweqas I said, we have couple of bugs16:37
slaweqfirst one is https://bugs.launchpad.net/neutron/+bug/181623916:37
openstackLaunchpad bug 1816239 in neutron "Functional test test_router_processing_pool_size failing" [High,In progress] - Assigned to LIU Yulong (dragon889)16:37
slaweqpatch https://review.openstack.org/#/c/637544/ was merged but it still happens, there is new patch also: https://review.openstack.org/#/c/639034/16:38
slaweqso this is still in progress and liuyulong is working on it16:38
slaweqI recently found also one more issue (race) in functional tests16:38
slaweqpatch to fix it is in https://review.openstack.org/#/c/638635/16:38
slaweqplease review this one if You will have some time :)16:39
slaweqexcept those 2, there is also one mentioned earlier today and I will try to check it this week16:39
mlavalleadded to the pile16:39
njohnstonwill do16:39
slaweqso that's all related to functional tests16:39
slaweqthx mlavalle and njohnston16:39
slaweqany questions/comments here?16:39
mlavallenot from me16:40
slaweqok, so next one16:40
slaweq#topic Tempest/Scenario16:40
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:40
slaweqmlavalle: please go on with updates on https://bugs.launchpad.net/neutron/+bug/1795870 :)16:40
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,In progress] - Assigned to Miguel Lavalle (minsel)16:40
*** sdake has quit IRC16:40
mlavalleso in https://review.openstack.org/#/c/636710/16:41
*** sdake_ has joined #openstack-meeting16:41
mlavalleI got feedback that filters to kill python are too broad16:41
mlavallewhich I agree with16:41
mlavalleso I just proposed https://review.openstack.org/#/c/639375/16:41
mlavalleand based on that I will update https://review.openstack.org/#/c/636710/16:42
slaweqok, I will review it today evening or tomorrow morning :)16:43
slaweqmlavalle: I hope You noticed my last comment in https://review.openstack.org/#/c/636710/2/etc/neutron/rootwrap.d/l3.filters16:43
slaweqI also saw few times issues with killing keepalived16:43
mlavalleI saw it16:44
slaweqand e.g. in D/S we solved it by removing /usr/sbin/ from path16:44
slaweqso maybe that will also be necessary16:44
slaweqok, thx16:44
mlavallebut I think that changing the command name in the process solves it16:44
mlavallewe won't filter pythonx anymore16:44
slaweqbut it's for different process16:44
slaweqI'm now speaking about keepalived, not neutron-keepalived-state-change16:45
slaweqthose are 2 different things :)16:45
mlavallein that case, we need to change keepalived16:45
mlavalleI'll take care of it as well16:45
*** sdake_ has quit IRC16:45
slaweqok, thx :)16:45
mlavallethanks for slapping me ;-)16:45
*** sdake has joined #openstack-meeting16:45
slaweqmlavalle: yw :D16:46
slaweqok, can we move on to the last topic for today? or are there any other comments/questions related to tempest jobs?16:46
mlavallelet's do it16:47
slaweqok :)16:47
slaweq#topic Open discussion16:47
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:47
slaweqI wanted to ask You about one more thing and stadium projects (again)16:47
slaweqin Denver we agreed with QA team to move tempest plugins from "main" repositories to tempest-plugin repos16:47
slaweqI think that still many stadium projects didn't finish it16:48
njohnstonwhich ones took any action on it?16:48
slaweqso question here is: how we should do it? should we start moving such plugins to neutron-tempest-plugin repo?16:48
slaweqnjohnston: I think that only midonet did something with this16:49
slaweqlist of tempest plugins is in https://docs.openstack.org/tempest/latest/plugin-registry.html16:49
mlavalleovn didn't?16:49
slaweqeach of them which points to main repo still needs to be moved16:50
*** sdake has quit IRC16:50
slaweqmlavalle: networking-ovn I think don't have own tempest-plugin16:50
slaweqso they don't need to do anything16:50
*** sdake has joined #openstack-meeting16:51
njohnstonI don't even see midonet in the list16:51
slaweqmaybe I mistake something with this midonet16:51
*** _hemna has joined #openstack-meeting16:52
slaweqnjohnston: https://github.com/openstack/neutron-tempest-plugin/commit/5214b27c080208ff4fc6b47c997f8aa6a28a6d4416:52
mlavalleit's not in the list16:52
slaweqI knew there was something16:52
slaweqso basically my question is: how You think we should do this?16:52
slaweqI guess we will have to do it by self mostly16:52
slaweqand in such case I think that the best way would be to move those tests to neutron-tempest-plugin repo16:53
slaweqwhat do You think?16:53
mlavallewhat's the deadline?16:53
njohnstonI think that setting up a separate repo per subproject would be insane, so aggregating them in neutron-tempest-plugin cuts down on the work16:54
slaweqI don't know about any deadline16:54
slaweqgmann: wanted told me in Denver that it would be good to do it ASAP :)16:54
mlavalleso if we can do it slowly and without much disruyption16:54
njohnstonmlavalle: It's the same deadline as the deadline for migrating to neutron-lib :-)16:54
mlavallelet's do it16:55
slaweqok, thx16:55
slaweqso I will prepare some etherpad with list what we need to move16:55
mlavallegive me a piece and I'll help16:55
slaweqand will try to start this work slowly16:55
njohnstongive me a piece and I'll help too16:55
slaweqthen we can split this work between all of us later16:55
mlavalleok, I will take from the etherpad16:55
njohnstonsounds good16:55
slaweqgreat, thx16:55
mlavalleThank you!16:56
slaweq#action slaweq to prepare etherpad and plan of moving tempest plugins from stadium projects to neutron-tempest-plugin repo16:56
slaweqso that was all from me for today16:56
slaweqdo You have anything else You want to talk quickly?16:57
mlavalleI don't16:57
njohnstonme neither16:57
slaweqok, thx for attending16:57
slaweqand have a nice week :)16:57
mlavalleyou too16:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:57
openstackMeeting ended Tue Feb 26 16:57:44 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-26-16.00.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-26-16.00.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-26-16.00.log.html16:57
*** ttsiouts has quit IRC16:59
*** ttsiouts has joined #openstack-meeting17:00
*** sdake has quit IRC17:00
*** sdake_ has joined #openstack-meeting17:02
*** ttsiouts has quit IRC17:05
*** cheng1_ has quit IRC17:07
*** markvoelker has quit IRC17:07
*** gyee has joined #openstack-meeting17:13
*** imacdonn_ is now known as imacdonn17:22
*** e0ne has quit IRC17:24
*** _hemna has quit IRC17:26
*** mlavalle has left #openstack-meeting17:30
*** KurtB has joined #openstack-meeting17:32
*** _alastor_ has quit IRC17:35
*** _alastor_ has joined #openstack-meeting17:36
*** mjturek has joined #openstack-meeting17:36
*** aojeagarcia__ has joined #openstack-meeting17:37
*** aojeagarcia has quit IRC17:40
*** yamamoto has joined #openstack-meeting17:41
*** davidsha has quit IRC17:44
*** yamamoto has quit IRC17:46
*** _hemna has joined #openstack-meeting17:53
*** yamamoto has joined #openstack-meeting18:13
*** kopecmartin is now known as kopecmartin|off18:14
*** yamamoto has quit IRC18:18
*** _hemna has quit IRC18:26
*** sdake_ has quit IRC18:30
*** sridharg has quit IRC18:30
*** sdake has joined #openstack-meeting18:37
*** ekcs has joined #openstack-meeting18:41
*** sdake has quit IRC18:46
*** aojeagarcia__ has quit IRC18:46
*** rfolco|rover has quit IRC18:46
*** sdake_ has joined #openstack-meeting18:47
*** sdake_ has quit IRC18:50
*** Swami has joined #openstack-meeting18:50
*** sdake has joined #openstack-meeting18:51
*** sdake has quit IRC18:55
*** sdake_ has joined #openstack-meeting18:56
*** sdake_ has quit IRC18:56
*** awaugama has quit IRC18:57
*** awaugama_ has joined #openstack-meeting18:57
*** sdake has joined #openstack-meeting18:59
*** sdake has quit IRC19:00
clarkbhelly anyone here for the infra meeting/19:01
*** sdake_ has joined #openstack-meeting19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Feb 26 19:01:45 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
gary_perkinso/ HI!19:02
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-February/006289.html19:03
clarkb#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
clarkbOpenStack TC campaigning period is happenign right now19:03
clarkbwith the voting to start just before Midngith UTC today19:03
*** markvoelker has joined #openstack-meeting19:04
clarkbKeep an eye out for your ballot I guess and you can ping the election officials if you don't get one and expected to19:05
clarkb#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-19-19.01.txt minutes from last meeting19:05
clarkbNo actions called out. Thank you to everyone that managed to review the letsencrypt spec19:05
*** sdake_ has quit IRC19:06
*** sdake has joined #openstack-meeting19:06
clarkb#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
clarkbThat spec just happens to be the next item of discussion19:06
clarkb#link https://review.openstack.org/#/c/587283/ LetsEncrypt Spec19:06
clarkbI think this is ready to go up for approval19:07
clarkbanyone think we should take more time to refine the spec?19:07
fungiwe can refine in the implementation from this point on, i expect19:08
*** igordc has joined #openstack-meeting19:08
ianwi've convinced myself at least with the prototype it should work19:09
ianw(insert famous last words :)19:09
clarkbok I don't hear any objects. Please review and vote on the spec Before EOD Thurdsay (clarkb local time)19:10
clarkbI'll plan to approve the spec if there are no major disagreements between now and then19:10
*** sdake has quit IRC19:10
clarkbmy typing is not great today19:10
clarkb#topic Priority Efforts19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
clarkb#topic Storyboard19:11
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:11
clarkblooks like placement is going to be headed into storyboard19:11
*** rfolco has joined #openstack-meeting19:12
clarkbstoryborad also has a lot of interest from outreachy candidates19:12
fungia LOT19:12
fungioh, and we're close to landing the api side of SotK's attachments work19:12
clarkbI've been trying to keep up and respond to them when things come up in my timezone19:12
*** sdake has joined #openstack-meeting19:12
clarkbthere are current questions about running the unittests locally so if anyone has done thatrecently maybe you can pop over to the storyborad channel and help ivy out19:12
cmurphyoutreachy applications can be really overwhelming @.@19:12
fungii've asked mordred to weigh in on the swiftclient usage there. not sure whether openstacksdk would make it harder to use storyboard with stand-alone swiftclient19:13
fungier, i mean stand-alone swift19:13
clarkbAnd then maybe we can do a followon to the docs because running the script to set things up doesn't seem to have set things up (or maybe its local issue/ I don't know)19:13
mordredit shouldn't19:13
mordredand if it does it's likely something we can/should fix in sdk19:13
fungi#link https://review.openstack.org/633365 Add a Swift storage backend implementation19:14
fungifor anybody who wants to take a look19:14
mordredsdk also transparently handles large object chunking and multi-threaded uploading for the user19:14
fungicmurphy: more overwhelming than we've seen in previous years. like dozens of applicants coming out of the woodwork this time19:14
fungimordred: well, this implementation doesn't upload for you, it hands off an upload url19:14
mordredbut it looks like, from initial looking, that the approach there is to get an upload url from swift that the api consumer should PUT to, I'm guessing19:15
fungibasically just want sb to coordinate and track attachments, not funnel the attachments themselves through sb19:15
mordredthat shoudl probably use the tempurl middleware support - the end user is unlikley to have auth creds for the swift19:15
mordredI'll leave some comments19:15
fungithe corresponding storyboard-webclient changes are up too19:16
clarkbmordred: thank you for helping with that19:17
clarkbAnything else storyboard related?19:17
fungi#link https://review.openstack.org/633611 Add a resource subcontroller for attachments19:17
diablo_rojo_None from me19:18
fungithe webclient side of the implementation starts there19:18
*** _alastor1 has joined #openstack-meeting19:18
fungiyeah, i don't have anything else exciting on the sb front for now19:18
clarkb#topic Update Config Management19:18
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:18
clarkbI've merged the last futureparser change (ask.o.o) which ran into a problem with the postgres puppet module19:19
clarkbianw's old chagne to bump that module to v4.8.0 shoud fix this19:19
*** vishakha has quit IRC19:19
clarkbianw: is that something you want to approve or should I go ahead and do that after our meeting?19:19
clarkb#link https://review.openstack.org/#/c/558995/ Update postgres module to fix usage with puppet futureparser19:19
*** ekcs_ has joined #openstack-meeting19:20
ianwoh, it's been a long time, that's a 5* series URL :)19:20
clarkbianw: indeed19:20
clarkbonce that is sorted I think we are ready to start doing the puppet 4 upgrades too19:20
*** sdake has quit IRC19:20
ianwi think that's ok, iirc it was the minimum viable update?19:20
*** _alastor_ has quit IRC19:20
*** gouthamr has quit IRC19:20
*** liuyulong has quit IRC19:20
*** gouthamr_ has joined #openstack-meeting19:20
clarkbianw: minimum viable for xenial. 4.3.0 would fix the puppet4 issues according to the chagnelog19:20
*** ekcs has quit IRC19:21
*** mriedem has quit IRC19:21
*** ekcs_ is now known as ekcs19:21
clarkbI think we should just make it xenial ready since that is a topic for later in the meeting19:21
*** sdake_ has joined #openstack-meeting19:21
clarkbOn the ansible + docker front corvus has been creating a consistent template for deploying services with host networking using docker compose19:21
ianwyeah, this was in service of ask.o.o updating, so let's do it i say19:21
fungii concur19:21
corvuswe have two services configured for that, zero of which are running19:21
corvusbut should be rsn.  :)19:22
*** mriedem has joined #openstack-meeting19:22
clarkbcorvus: have you had a chance to look at the service restart when image updates thing I pointed out?19:22
corvusoh sorry, 3 services, 2 of which are not running :)19:22
clarkbcorvus: ya overall I think I like it because its quite consistent so far19:22
clarkbyou don't have to change much to deploy foo instead of bar19:22
corvusclarkb: erm, what was the issue with that again?19:22
clarkbcorvus: docker-compose up -d will restart any service that has a new image available19:22
fungii could go for deploying to a bar right about now19:23
clarkbcorvus: and sicne you are using foo-image:latest it will see newer images19:23
clarkbI guess one fix is to fix the image version.19:23
corvusdeploying latest sounds great to me :)19:23
clarkbIn the case of multiple redundant services (like gitea) we mighte be able to get away with serializing the docker compose up commands19:23
clarkbthen haproxy will sort things out for the most part19:23
clarkbits something we'll want to have an answer for when these services go into production. But we don't need to solve it in this meeting19:24
corvuswell, i mean, i think we have the answer19:24
corvusi wrote a docker-compose file that says "run the latest image" and docker-compose is making sure that the latest image is running, so w00t.19:24
clarkbright, but those restarts will be user visible if they coincide with a request right?19:25
corvusyes, but for non-ha services, that's life19:25
*** sdake_ has quit IRC19:25
corvusi do agree that for the ha services, we should tell ansible to run serially19:25
corvusthat's more of an ansible thing than a docker thing though19:26
*** sdake has joined #openstack-meeting19:26
*** e0ne has joined #openstack-meeting19:26
corvusi do think that our gitea servers should always run the latest gitea image we built19:26
corvusi think this gets to the fact that we need to rework our system-config playbooks19:26
mordredyeah. as long as the ansible is serial I think that shoudl work out19:26
mordredcorvus: ++19:26
corvuswe need to stop hanging everything off of base19:26
fungifor ha services, running serially *with a delay* might even be called for, just because there will be some lag in lb checks19:27
corvuswe need the gerrit/zuul/git/gitea playbook.19:27
corvusfungi: we can also execute haproxy commands19:27
corvusthis is the real advantage of using ansible19:27
clarkbya should be able to coordinate the entries in haproxy so that it all happens in a safe manner19:28
corvustake a member offline, upgrade it, put it back online19:28
clarkblooks like https://review.openstack.org/#/c/604925/ is in merge conflict again I'll rebase it again19:28
clarkb(thats the bit needed to have zuul trigger playbooks on bridge)19:28
*** rfolco is now known as rfolco|rover19:28
corvusrelated to this, just to keep folks up to date --19:28
fungicorvus: ooh, i do like the idea of orchestrating pool management in haproxy during updates19:28
corvuswe do not yet have speculative docker images19:28
mordredsad trombone19:29
fungithat's waiting for zuul to support provider affinity for dependent jobs, right?19:29
corvuswe managed to demonstrate that working last week, but we've run into a problem which requires a zuul/nodepool feature before we can use it in prod19:29
corvusso keep in mind we're still in the world where you need to land changes to images first before you can use them19:29
corvus(aka the real world everyone else lives in)19:29
corvusboo ^19:30
fungisoon we can reject their reality and substitute our own19:30
corvusyay ^19:30
clarkbif only the internet was ipv6 ready19:30
fungiand then invite them over for brunch19:30
corvusand yes, the fact that we have non ipv6 providers is the proximate cause.  :(19:30
corvuslet's not get started19:31
clarkbalright anything else related to config management before we talk opendev?19:31
clarkb#topic OpenDev19:31
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:31
fungi(which will also be somewhat about config management, i guess)19:31
corvusas promised (2 weeks ago) i refreshed the tasks needed to make opendev-gerrit happen19:32
corvus#link opendev-gerrit tasks https://storyboard.openstack.org/#!/story/200462719:32
clarkbThe openstack berlin ops meetup planning etherpad (or one of them), https://etherpad.openstack.org/p/BER19-OPS-DUDES, has a section to talk about opendev and opinionate on it19:32
clarkbI don't plan to be in berlin but if anyone else is there that might be a good thing to sit in on19:32
funginow we can all start signing up for the opendev-gerrit tasks19:32
corvusso what would be really great, is if everyone would sign up for those19:32
clarkbcorvus: thank you for getting that posted19:32
corvusi will not be doing all of those myself19:33
*** yamamoto has joined #openstack-meeting19:33
clarkbI'll likely jump on the git:// task19:33
corvusso if no one signs up for those, it won't be done.19:33
fungii will try to at least grab some of the easier ones19:33
clarkbas a devstack core (how did that happen) I'm probably well positioned for that one19:33
fungibut seems like clarkb's already got the easiest one ;)19:33
corvusplease use the storyboard assignment feature to put your name on it19:33
clarkbfungi: I wish that was an easy one. You can have it :P19:34
corvusmost of them are easy19:34
corvusthe gitea servers are just launching nodes at this point19:34
corvusand i already wrote the .htaccess file to do all the redirects19:34
clarkb#action Everyone please sign up for tasks at https://storyboard.openstack.org/#!/story/2004627 to help with the opendev git hosting and gitea work19:35
fungithanks corvus! i'm really excited about this19:35
*** sdake has quit IRC19:35
ianwis that page working?19:35
corvusoh, weird.  that link took a really long time to load for me19:36
*** ralonsoh has quit IRC19:36
ianwoh, yeah, maybe i'm just impatient19:36
*** sdake_ has joined #openstack-meeting19:36
clarkbAnything else to add on the opendev topic?19:37
fungiwe do need someone with rdbms smarts to help us optimize our queries for sb ;)19:37
corvusclarkb: nak19:37
fungi(would be a great opportunity to works one-on-one with an outreacy intern too!)19:37
*** yamamoto has quit IRC19:37
fungiwow, i can't type today19:38
*** markvoelker has quit IRC19:38
clarkb#topic General Topics19:38
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:38
clarkbfungi: neither can I19:38
clarkbFirst up I'd like to bring up the Trusty Upgrades situation again. Last week I realized I didn't really formulate enough thought or discussion around whether or not we thought a sprint would be helpful19:39
clarkbI have been picking off a service at a time and trying to get it finished up. Currently doing health.openstack.org19:39
clarkbWe have about 2 more months of support on Trusty.19:39
fungithere's not a lot left to tackle for a sprint, is there?19:39
clarkbIt would be really helpful if others could grab things off of https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup and help to upgrade them19:39
mordredclarkb: all the fun ones19:40
clarkbfungi: afs, groups, lists, ask, static, the wiki, and graphite and status19:40
clarkbya the list of easy things is shrinking :)19:40
fungilists.o.o is going to need another in-place ubuntu upgrade, i expect, so we don't have to reset its ip address's reputation19:40
clarkbfungi: and corvus suggested we do that same for afs yesterday19:40
fungisounds like ask.o.o may also be an in-place19:40
fungioh, that was afs maybe not ask19:40
mordredfungi: they're both three leter words starting with a19:41
mordredso - you know, close enough19:41
clarkbSo my big ask is please try to find some time for this. And does anyone think a sprint would be helpful?19:41
clarkbopenstack feature freeze is next week. I don't know when RCs happen but we could do a sprint the week after RCs potentially19:41
clarkbI'm happy to organize a sprint if we think that would be useful19:42
fungiit's possible groups.o.o can be decommissioned. i'll make inquiries19:42
mordredthat would be less work than upgrading19:42
fungiwiki is another one which will probably be a snapshot and in-place upgrade unless someone has time to finish the puppeting19:42
clarkbfungi: we should probably start annotating that etherpad with this info19:43
fungistatic, graphite and status are probably not hard. just involve downtime for some stuff and moving cinder devices or rsync'ing data19:43
clarkbfungi: yup19:43
mordredfungi: I think snapshot/in-place sounds better - because at this point I think converting that to docker is likely to be more pleasant than finishing the puppet19:43
fungiand yes, i think that's a great idea19:43
mordred(for wiki)19:43
fungimordred: or converting it to gitea19:44
mordredfungi: or that.19:44
clarkbwith the sprint idea any rough show of hands for people that would be able to dedicate say 3 days to that? or at least a good portion of a 3 day chunk of time?19:44
ianwo/ i could, modulo when i'm awake :)19:45
*** sdake_ has quit IRC19:45
corvusmaybe 2 days? :)19:45
*** yamamoto has joined #openstack-meeting19:45
*** e0ne has quit IRC19:46
clarkbRC1 is targeted for march 22nd ish19:46
*** e0ne has joined #openstack-meeting19:46
clarkbwhich would make march 25-29 the rough time I have in mind. I can ping the openstack release team and ask them if then or ealier is better then suggest a couple options on the infra list19:47
mordredI'm travelling to europe for 2 conferences march 26-april 4 - but could do virtual sprint either around then or as best I could given timezones19:47
clarkbits possible they would want us to do the things before RCs19:47
clarkbok sounds liek the number is greater than just me :)19:47
clarkbI'll talk to the release team and suggest options on the infra list in the near future. Thanks19:47
fungiif folks are in favor of a sprint i can pitch in but am spread a bit thin to dedicate 3 days doing primarily that19:47
*** sdake has joined #openstack-meeting19:47
clarkbThe other item related to this is the puppetmaster.19:48
fungithough i'm happy to continue to work on upgrading servers outside of or without a sprint too19:48
clarkbLast call if you need any scripts or data or anything off of that server19:48
clarkbotherwise I'd like to delete it this week (I'm happy to do the deleting just want to make sure people know this is happening()19:48
fungii need nothing from the old puppetmaster, but snapshot it first?19:48
clarkbI can snapshot it first19:48
clarkb#info clarkb snapshot puppetmaster before deleting the old server19:48
clarkbLast item on the list is thoughts on Infra/OpenDev onboarding and/or update sessions at the denver summit19:49
clarkbI'm leaning towards no on the onboarding session (I think the return on those has been low and spots are limited)19:49
*** yamamoto has quit IRC19:50
clarkbbut askign for an update session to talk about all the big changes around config management and docker and ansible and gitea and even k8s19:50
corvusclarkb: i support that plan19:50
clarkbAlright that is all we had on the agenda.19:51
clarkb#topic Open Discussion19:51
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:52
clarkbAnything else?19:52
fungisounds good to me, though we could also consider abusing the onboarding session to do more of an inservice for folks who want to come learn how to use what we've built... though that might be better saved for once we're further along with the opendev transition19:52
corvuswhich is only going to happen if people sign up for tasks on https://storyboard.openstack.org/#!/story/200462719:52
corvusi'm still the only name on there19:52
clarkbcorvus: its on my list for after the meeting :)19:52
clarkbI'm not hearing anything else so I'll end the meeting now and we can all go sign up on corvus' list. Thanks everyone19:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:55
openstackMeeting ended Tue Feb 26 19:55:09 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-26-19.01.html19:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-26-19.01.txt19:55
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-26-19.01.log.html19:55
*** sdake has quit IRC19:55
fungithanks clarkb!19:56
funginow to sign up for opendev tasks19:56
*** sdake has joined #openstack-meeting19:58
*** sdake has quit IRC20:03
*** vishalmanchanda has quit IRC20:09
*** jamesmcarthur has quit IRC20:15
*** jamesmcarthur has joined #openstack-meeting20:16
*** yamamoto has joined #openstack-meeting20:16
*** jamesmcarthur has quit IRC20:20
*** yamamoto has quit IRC20:21
*** _hemna has joined #openstack-meeting20:23
*** enriquetaso has quit IRC20:24
*** enriquetaso has joined #openstack-meeting20:25
*** imacdonn has quit IRC20:26
*** mathiasb has quit IRC20:28
*** imacdonn has joined #openstack-meeting20:28
*** e0ne has quit IRC20:31
*** diablo_rojo_ has quit IRC20:35
*** diablo_rojo has joined #openstack-meeting20:36
*** awaugama_ has quit IRC20:38
*** gouthamr_ is now known as gouthamr20:42
*** takamatsu_ has quit IRC20:48
*** takamatsu_ has joined #openstack-meeting20:50
*** _hemna has quit IRC20:57
*** erlon has quit IRC21:02
*** bbowen has quit IRC21:05
*** jamesmcarthur has joined #openstack-meeting21:11
*** enriquetaso has quit IRC21:18
*** manjeets_ has joined #openstack-meeting21:22
*** manjeets has quit IRC21:24
*** yamamoto has joined #openstack-meeting21:25
*** zbr|out has quit IRC21:27
*** e0ne has joined #openstack-meeting21:28
*** yamamoto has quit IRC21:30
*** raildo has quit IRC21:33
*** eharney has quit IRC21:33
*** manjeets_ is now known as manjeets21:35
*** markvoelker has joined #openstack-meeting21:35
*** whoami-rajat has quit IRC21:41
*** mjturek has quit IRC21:54
*** ttsiouts has joined #openstack-meeting21:56
*** yamamoto has joined #openstack-meeting21:56
*** yamamoto has quit IRC22:01
*** e0ne has quit IRC22:03
*** bbowen has joined #openstack-meeting22:05
*** rcernin has joined #openstack-meeting22:05
*** markvoelker has quit IRC22:09
*** ttsiouts has quit IRC22:16
*** ttsiouts has joined #openstack-meeting22:16
*** slaweq has quit IRC22:18
*** ttsiouts has quit IRC22:21
*** slaweq has joined #openstack-meeting22:26
*** ttsiouts has joined #openstack-meeting22:28
*** sdake has joined #openstack-meeting22:28
*** slaweq has quit IRC22:30
*** sdake has quit IRC22:30
*** sdake has joined #openstack-meeting22:32
*** sdake has quit IRC22:40
*** sdake_ has joined #openstack-meeting22:41
*** slaweq has joined #openstack-meeting22:44
*** sdake_ has quit IRC22:45
*** ijw has quit IRC22:46
*** sdake has joined #openstack-meeting22:46
*** jamesmcarthur has quit IRC22:49
*** slaweq has quit IRC22:49
*** _hemna has joined #openstack-meeting22:54
*** sdake has quit IRC22:56
*** sdake has joined #openstack-meeting22:58
*** sdake has quit IRC23:00
*** jamesmcarthur has joined #openstack-meeting23:02
*** sdake has joined #openstack-meeting23:02
*** sdake has quit IRC23:06
*** sdake_ has joined #openstack-meeting23:07
*** jamesmcarthur has quit IRC23:09
*** sdake_ has quit IRC23:10
*** cmoura has quit IRC23:11
*** cmoura has joined #openstack-meeting23:11
*** sdake has joined #openstack-meeting23:11
*** zhubx007 has quit IRC23:14
*** zhubx has joined #openstack-meeting23:14
*** _alastor_ has joined #openstack-meeting23:15
*** _alastor1 has quit IRC23:16
*** yamamoto has joined #openstack-meeting23:17
*** sdake has quit IRC23:20
*** yamamoto has quit IRC23:21
*** sdake has joined #openstack-meeting23:22
*** sdake has quit IRC23:25
*** _hemna has quit IRC23:27
*** sdake has joined #openstack-meeting23:27
*** liuyulong has joined #openstack-meeting23:30
*** sdake has quit IRC23:30
*** ttsiouts has quit IRC23:30
*** ttsiouts has joined #openstack-meeting23:31
*** sdake has joined #openstack-meeting23:33
*** sdake has quit IRC23:35
*** ttsiouts has quit IRC23:35
*** sdake has joined #openstack-meeting23:36
*** sdake has quit IRC23:37
*** sdake has joined #openstack-meeting23:38
*** sdake has quit IRC23:40
*** sdake has joined #openstack-meeting23:42
*** sdake has quit IRC23:50
*** jesusaur has quit IRC23:51
*** sdake has joined #openstack-meeting23:51
*** ijw has joined #openstack-meeting23:53
*** yamamoto has joined #openstack-meeting23:55
*** sdake has quit IRC23:55
*** sdake has joined #openstack-meeting23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!