Tuesday, 2019-05-07

*** dkehn2 has quit IRC00:00
*** mattw4 has quit IRC00:03
*** mriedem has quit IRC00:09
*** ijw has quit IRC00:30
*** ijw has joined #openstack-meeting00:30
*** yamamoto has joined #openstack-meeting00:34
*** ijw has quit IRC00:36
*** larainema has quit IRC00:42
*** Adri2000 has quit IRC00:46
*** Lucas_Gray has quit IRC00:46
*** larainema has joined #openstack-meeting00:49
*** Adri2000 has joined #openstack-meeting00:51
*** whoami-rajat has joined #openstack-meeting01:16
*** diablo_rojo has joined #openstack-meeting01:17
*** jamesmcarthur has joined #openstack-meeting01:25
*** yamamoto has quit IRC01:33
*** rubasov has quit IRC01:34
*** rubasov has joined #openstack-meeting01:37
*** baojg has joined #openstack-meeting01:37
*** jamesmcarthur has quit IRC01:43
*** Swami has quit IRC01:44
*** bbowen_ has quit IRC02:04
*** jamesmcarthur has joined #openstack-meeting02:14
*** hongbin has joined #openstack-meeting02:19
*** jamesmcarthur has quit IRC02:30
*** jamesmcarthur has joined #openstack-meeting02:43
*** rcernin has quit IRC02:43
*** samueldmq has quit IRC02:46
*** boxiang has quit IRC02:46
*** iyamahat__ has joined #openstack-meeting02:47
*** iyamahat_ has quit IRC02:49
*** yamahata has quit IRC02:50
*** boxiang has joined #openstack-meeting02:50
*** iyamahat__ has quit IRC02:53
*** lbragstad has quit IRC02:54
*** jamesmcarthur has quit IRC03:04
*** jamesmcarthur has joined #openstack-meeting03:06
*** yamamoto has joined #openstack-meeting03:20
*** jamesmcarthur has quit IRC03:26
*** rcernin has joined #openstack-meeting03:29
*** tpatil has joined #openstack-meeting03:43
*** jamesmcarthur has joined #openstack-meeting03:56
*** imsurit_ofc has joined #openstack-meeting04:00
*** shilpasd has joined #openstack-meeting04:00
*** tashiromt has joined #openstack-meeting04:01
tpatil#startmeeting Masakari04:02
openstackMeeting started Tue May  7 04:02:05 2019 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:02
*** openstack changes topic to " (Meeting topic: Masakari)"04:02
openstackThe meeting name has been set to 'masakari'04:02
tpatilHi All04:02
tpatilI don't see Sampath online, so I have started today's meeting04:02
tpatiltashiromt: Hi04:02
tpatilLet's wait for Sampath to join this meeting04:03
tpatilFYI, Last week PTG was held in Denver but this time there were no sessions planned during PTG04:05
*** e0ne has joined #openstack-meeting04:06
tpatilOk, Let's start the meeting. This meeting I don't have any agenda from my side but let's go through the usual stuff one by one04:07
tpatil#topic Bugs04:07
*** openstack changes topic to "Bugs (Meeting topic: Masakari)"04:07
tpatilAny bugs you want to discuss here?04:07
tpatilI don't see any new bugs reported in the last two weeks04:08
tpatil#link https://bugs.launchpad.net/masakari/+bug/181565704:08
openstackLaunchpad bug 1815657 in masakari "python 3 failures - /usr/bin/masakari-wsgi and unit tests" [High,Fix committed] - Assigned to Shilpa Devharakar (shilpasd)04:08
tashiromtI don't have any bugs today04:08
tpatilThis bug was fixed in Stein release so it should be marked as Fix Released04:09
tpatil#action Mark #bug 1815657 as fix release04:09
tpatiltashiromt: Ok, Thank you04:10
tpatil#topic Train Work items04:10
*** openstack changes topic to "Train Work items (Meeting topic: Masakari)"04:10
*** e0ne has quit IRC04:12
tpatilSome of the blueprints in LP are still open even though they are implemented, I will discuss about it with Sampath and take action to mark it as implemented04:12
tpatil#action Mark completed blueprints as implemented (samP/tpatil)04:12
tpatilReal time rendering of notifications in masakari-dashboard (slow progress)04:13
tpatilHere, we would like to show the graph of  host failure workflow in masakari-dashobard in same way as done for Network topology04:14
tpatilSecond work item we are working on is : Add support to install host monitor in devstack04:15
*** diablo_rojo has quit IRC04:16
tpatilWork in going on, planning to complete it in milestone-104:16
tpatilAnyone who wants to talk about any work item you have planned to contribute in Train cycle?04:17
tpatilSeems like no one at this moment04:19
tashiromtToday I dont have a work item for Train04:20
tpatiltashiromt: Ok04:20
tpatilIf you have no other topics for discussion, let's end this meeting early04:20
*** jamesmcarthur has quit IRC04:22
tpatilThank you all for attending this meeting, I will end this meeting now.04:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:25
openstackMeeting ended Tue May  7 04:25:35 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-05-07-04.02.html04:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-05-07-04.02.txt04:25
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-05-07-04.02.log.html04:25
*** ricolin has joined #openstack-meeting04:26
*** hongbin has quit IRC04:33
*** tpatil has quit IRC04:36
*** janki has joined #openstack-meeting04:37
*** yamahata has joined #openstack-meeting04:42
*** tashiromt has quit IRC05:01
*** e0ne has joined #openstack-meeting05:22
*** ricolin has quit IRC05:24
*** ijw has joined #openstack-meeting05:29
*** ijw_ has joined #openstack-meeting05:31
*** ijw_ has quit IRC05:33
*** ijw has quit IRC05:34
*** ijw has joined #openstack-meeting05:35
*** dkushwaha has joined #openstack-meeting05:37
*** radeks_ has joined #openstack-meeting05:43
*** ijw_ has joined #openstack-meeting05:53
*** e0ne has quit IRC05:56
*** ijw has quit IRC05:56
*** kopecmartin|off is now known as kopecmartin06:01
*** lpetrut has joined #openstack-meeting06:07
*** vishalmanchanda has joined #openstack-meeting06:14
*** radeks_ has quit IRC06:20
*** pcaruana has joined #openstack-meeting06:21
*** radeks_ has joined #openstack-meeting06:22
*** jbadiapa has joined #openstack-meeting06:33
*** slaweq has joined #openstack-meeting06:36
*** e0ne has joined #openstack-meeting06:46
*** dkushwaha has left #openstack-meeting06:48
*** e0ne has quit IRC06:53
*** armax has quit IRC07:03
*** tesseract has joined #openstack-meeting07:26
*** rcernin has quit IRC07:27
*** dkushwaha has joined #openstack-meeting07:43
*** joxyuki has joined #openstack-meeting07:50
*** trident has quit IRC08:01
*** trident has joined #openstack-meeting08:02
*** bhagyashris has joined #openstack-meeting08:03
dkushwaha#startmeeting tacker08:04
openstackMeeting started Tue May  7 08:04:45 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:04
*** openstack changes topic to " (Meeting topic: tacker)"08:04
openstackThe meeting name has been set to 'tacker'08:04
dkushwaha#topic Roll Call08:04
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:04
dkushwahawho is here for Tacker weekly meeting?08:05
*** rossella_s has joined #openstack-meeting08:06
*** takahashi-tsc has joined #openstack-meeting08:06
hyunsikyangHi jo and dkushwaha08:06
dkushwahahello joxyuki hyunsikyang08:07
joxyukihi, hyunsikyang08:07
dkushwahaHow was the summit?08:07
*** jaewook_oh has joined #openstack-meeting08:07
hyunsikyangnot many people, compare to last summit.08:07
joxyukisnow at Tuesday :(08:08
dkushwahahi bhagyashris08:08
hyunsikyangand in the tacker session, around 20~ people attended.08:08
dkushwahahyunsikyang, ~20 is also good :)08:09
dkushwahahyunsikyang, how was your talk?08:09
takahashi-tscHello all, this is my first participation in Tacker meeting.08:09
hyunsikyangHi takahashi08:09
dkushwahahello takahashi-tsc, welcome in Tacker Team08:09
hyunsikyangUm.. I only have 10 min so I brifely explain it08:09
*** hokeeeeun has joined #openstack-meeting08:10
dkushwahahyunsikyang, yea, 10 minute is really too short08:10
dkushwahahello jaewook_oh JangwonLee_08:10
hyunsikyangbut, some people doesn't know about tacker. so That session was good for introducing Tacker.08:10
hyunsikyangI get namecard from some teleco company.08:11
dkushwahajoxyuki, hyunsikyang , do you want to share some input(if any) from summit08:12
hyunsikyangI talked with fenix PTL and Fenix also consider ETSI spec to adapt it to fenix. So we also good chance to consider ETSI spec as a MANO08:13
hyunsikyangMore and More , Many people focus on the container, so whatif, tacker also focus on the container related features, it also good.08:15
hyunsikyangand we also consider how we provides some feautures for Edge cloud collaboration kinds of things08:15
dkushwahahyunsikyang, yea, we needs to prioritize C-VNF related activities08:15
joxyukiyeah, generally edge computing session increased.08:16
joxyukiit seems affected by 5G growing.08:17
dkushwahajoxyuki, hyunsikyang yea, 5g growing rapidly now a days08:18
hyunsikyangThat is, We should think about features as a perspective of telco view.08:18
joxyukifor example, I think, Multi-VIM support might be required.08:19
hyunsikyangMaintenance,Edge, lightweight things..08:19
dkushwahahave you got chance to talk some telco operators and there views/inputes for tacker?08:19
joxyukisorry nothing from me08:20
dkushwahajoxyuki, what it mean by Multi-VIM(as we already supporting it)??08:20
joxyukiyeah, we already support it but is it feasible for edge?08:20
hyunsikyangI talked with one guy who come from middle east and he asked me why tacker is not well known..08:21
joxyukiI mean, for edge, such as StarlingX will be supported as VIM08:21
hyunsikyangAnd he said, these feautres is good for telco provider. but, he want to know how they adapt tacker to real environment.08:21
dkushwahajoxyuki, I see, need to check us more for Edge cloud things08:22
hyunsikyangyes. Our team also consider it how we adapt it to tacker.08:22
hyunsikyangI met Jo and we also talked about etsi spec.08:22
dkushwahanice :)08:23
hyunsikyangIt also good features:)08:23
dkushwahaThanks joxyuki hyunsikyang for good inputs.08:24
dkushwahamoving next..08:24
hyunsikyangyou're welcome.08:24
dkushwaha#topic BP08:24
*** openstack changes topic to "BP (Meeting topic: tacker)"08:24
dkushwaha#topic VNF Package support BP08:25
*** openstack changes topic to "VNF Package support BP (Meeting topic: tacker)"08:25
dkushwaha#link https://review.opendev.org/#/c/58293008:25
joxyukiI wrote my memo on https://etherpad.openstack.org/p/tacker-train-grooming08:25
dkushwahajoxyuki, I gone though the spec, and overall looks good to me as of now08:26
dkushwahaI have few questions08:26
joxyukithanks, but biggest problem is that we need to support ETSI NFV-SOL001.08:27
dkushwahajoxyuki, Any approach on that ?08:27
joxyukiyes, my team are also plannning to address it but it will be U cycle.08:28
joxyukithen, at Train, just creating VNF package will be availble but not able to create VNF from it.08:29
dkushwahajoxyuki, I see it will be a big task08:29
dkushwahajoxyuki, I hope that should be ok, to move step by step.08:30
*** hadai has joined #openstack-meeting08:30
dkushwahajoxyuki, regarding VNF package do you have some plan to how deal with extracted CSAR resources ?08:31
joxyukiok, I will keep to make effort08:31
joxyukidkushwaha, current plan is storing VNF packages to local file system08:32
joxyukisuch as /var/lib/tacker but it is configurable08:32
joxyukiand VM images shall be registerd to Glance if any.08:33
dkushwahajoxyuki, agree to that approach. one more approach can be...08:33
dkushwahacreate a temp VM(may be we can call it as resource/package manager), and use it to extract CSAR bundle, upload all images/binaries/meat etc files there. And once deployment done, clean that VM08:35
dkushwahaIt will help to keep all  csar resources separate and secure.08:36
dkushwahaIt is one of my point, but yes I wanted all your opinions on that08:36
joxyukidkushwaha, thanks for your idea :)08:37
joxyukiI will examine it08:39
dkushwahajoxyuki, cool, we can discuss more in vPTG08:39
dkushwahamoving next..08:40
dkushwaha#topic visually design TOSCA templates08:40
*** openstack changes topic to "visually design TOSCA templates (Meeting topic: tacker)"08:40
dkushwaha#link https://review.opendev.org/#/c/55368408:40
dkushwahaLooking for some volunteer who can pick it up08:41
hyunsikyangwhat you mean? Trinh Nguyen want to get off this work?08:43
dkushwaha visually design TOSCA templates support can help to make Tacker user friendly08:43
dkushwahahyunsikyang, As Trinh is busy in some other activities, so it will be good if some other  can lead it08:44
*** priteau has joined #openstack-meeting08:44
hyunsikyangAh, OK:)08:45
dkushwahamoving next..08:45
dkushwaha#topic #Tacker vPTG08:46
*** openstack changes topic to "#Tacker vPTG (Meeting topic: tacker)"08:46
dkushwaha#link https://etherpad.openstack.org/p/Tacker-PTG-Train08:46
dkushwahaI am thinking to have one day vPTG on 14th May08:47
dkushwahaLet me know if it ok, otherwise please suggest as per your availability08:48
*** ralonsoh has joined #openstack-meeting08:48
hyunsikyangIt's good to me.08:48
dkushwahaand timing: it will be 4 hours virtual meetup 08:00 UTC to 12:00 UTC08:50
dkushwahajoxyuki, bhagyashris jaewook_oh JangwonLee_ takahashi-tsc ^^08:51
takahashi-tscIt's good to me, and I'd like to join vPTG. I'm interested in support ETSI.08:51
joxyukialmost OK, but until 11a.m. UTC08:51
joxyukilet me talk my topic first08:52
dkushwahajoxyuki,  ok, sure08:52
joxyukivery thanks team :)08:53
bhagyashrisAgree with joxyuki08:53
jaewook_ohi'll attend at that time08:53
bhagyashrisThank you :)08:53
dkushwahathanks all08:54
dkushwahaI will share meeting channel later08:54
dkushwaha#topic OpenDiscussion08:55
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:55
dkushwahaI have noting to discuss as of now.08:55
dkushwahacouple of more minutes left.08:56
hyunsikyangI will present my blueprint in the vPTG. but, before that could you check my blueprint?08:56
hyunsikyanghttps://review.opendev.org/#/c/643242/ and https://review.opendev.org/#/c/636272/08:57
hyunsikyangone is related fenix. another one is for multi interface for C-VNF.08:57
dkushwahahyunsikyang, sure, it is in my list, will review it08:57
hyunsikyangare you gonna make a etherpad for vPTG?08:58
dkushwahahyunsikyang, it is https://etherpad.openstack.org/p/Tacker-PTG-Train08:59
dkushwahawe use this one08:59
dkushwahaThanks Folks for joining this meeting.08:59
dkushwahaclosing it now.08:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:00
openstackMeeting ended Tue May  7 09:00:02 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-05-07-08.04.html09:00
hyunsikyangthanks all09:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-05-07-08.04.txt09:00
*** hokeeeeun has quit IRC09:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-05-07-08.04.log.html09:00
*** joxyuki has quit IRC09:08
*** takahashi-tsc has quit IRC09:09
*** electrofelix has joined #openstack-meeting09:21
*** hadai has quit IRC09:24
*** bhagyashris has quit IRC09:25
*** jaewook_oh has quit IRC09:30
*** jaewook_oh has joined #openstack-meeting09:30
*** cheng1 has quit IRC09:38
*** cheng1 has joined #openstack-meeting09:40
*** raildo has joined #openstack-meeting09:54
*** zbr has joined #openstack-meeting10:04
*** ijw_ has quit IRC10:17
*** ijw has joined #openstack-meeting10:17
*** pcaruana has quit IRC10:19
*** ijw has quit IRC10:22
*** dkushwaha has quit IRC10:36
*** bbowen_ has joined #openstack-meeting10:41
*** bbowen_ has quit IRC10:50
*** pcaruana has joined #openstack-meeting10:55
*** ijw has joined #openstack-meeting10:57
*** ijw has quit IRC11:05
*** priteau has quit IRC11:11
*** carloss has joined #openstack-meeting11:15
*** yamamoto has quit IRC11:18
*** Lucas_Gray has joined #openstack-meeting11:22
*** imsurit_ofc has quit IRC11:44
*** baojg has quit IRC11:44
*** yamamoto has joined #openstack-meeting11:49
*** bbowen has joined #openstack-meeting11:52
*** bbowen_ has joined #openstack-meeting11:53
*** yamamoto has quit IRC11:53
*** yamamoto has joined #openstack-meeting11:53
*** yamamoto has quit IRC11:54
*** yamamoto has joined #openstack-meeting11:54
*** yamamoto has quit IRC11:54
*** bbowen has quit IRC11:56
*** yamamoto has joined #openstack-meeting11:56
*** jamesmcarthur has joined #openstack-meeting12:02
*** mriedem has joined #openstack-meeting12:05
*** larainema has quit IRC12:12
*** jamesmcarthur has quit IRC12:28
*** rfolco|ruck is now known as rfolco|dentist12:29
*** _hemna has quit IRC12:47
*** hemna has joined #openstack-meeting12:48
*** yamamoto has quit IRC12:57
*** jaewook_oh has quit IRC12:57
*** yamamoto has joined #openstack-meeting12:58
*** yamamoto has quit IRC13:03
*** mmethot has joined #openstack-meeting13:04
*** tssurya has joined #openstack-meeting13:05
*** shilpasd has quit IRC13:09
*** lseki has joined #openstack-meeting13:09
*** ijw has joined #openstack-meeting13:18
*** lbragstad has joined #openstack-meeting13:20
*** ijw has quit IRC13:23
*** bobh has joined #openstack-meeting13:25
*** bobh has quit IRC13:25
*** hemna has quit IRC13:25
*** hemna has joined #openstack-meeting13:26
*** yamamoto has joined #openstack-meeting13:32
*** enriquetaso has joined #openstack-meeting13:33
*** e0ne has joined #openstack-meeting13:36
*** yamamoto has quit IRC13:37
*** e0ne has quit IRC13:39
*** lpetrut has quit IRC13:40
*** artom has quit IRC13:45
*** ayoung has quit IRC13:49
*** ijw has joined #openstack-meeting13:53
*** zaneb has quit IRC13:53
*** shintaro has joined #openstack-meeting14:01
*** boxiang has quit IRC14:02
*** boxiang has joined #openstack-meeting14:03
*** Yipei has joined #openstack-meeting14:06
*** artom has joined #openstack-meeting14:12
*** janki has quit IRC14:14
*** artom has quit IRC14:18
*** pcaruana has quit IRC14:19
*** rfolco|dentist is now known as rfolco|ruck14:20
*** Yipei has quit IRC14:21
*** apetrich has quit IRC14:29
*** armax has joined #openstack-meeting14:37
*** pcaruana has joined #openstack-meeting14:38
*** apetrich has joined #openstack-meeting14:38
*** efried is now known as efried_pto14:39
*** Yipei has joined #openstack-meeting14:47
*** Yipei has left #openstack-meeting14:48
*** Yipei has joined #openstack-meeting14:49
*** Yipei has quit IRC14:49
*** cheng1__ has joined #openstack-meeting14:59
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue May  7 15:00:11 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
*** shintaro has quit IRC15:01
ralonsohhmmm people is still suffering the hangover of the PTG15:01
ralonsohanyway, for the records15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:02
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Fix released] - Assigned to Bence Romsics (bence-romsics)15:02
ralonsohBoth tempest and fullstack tests are still under development15:02
ralonsoh#link https://review.openstack.org/#/c/629253/15:02
ralonsoh#link https://review.openstack.org/#/c/642527/15:02
ralonsohDocs are merged15:02
ralonsohNova API must be polished this release15:03
ralonsohBut great job, again15:03
ralonsohnext one15:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:03
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:03
ralonsohI didn't have time to finish it during the PTG15:03
ralonsohI have some patches upstream15:03
ralonsohBut the final patch to use VXLAN filtering in QoS is still under development15:04
ralonsohnext one15:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181847915:04
openstackLaunchpad bug 1818479 in neutron "RFE Decouple placement reporting service plugin from ML2" [Wishlist,Incomplete] - Assigned to Bence Romsics (bence-romsics)15:04
ralonsohThis one is going to be discussed and followed in the drivers meeting15:04
ralonsohbut because is QoS related, we'll track it here15:05
ralonsoh#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:05
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/182669515:05
openstackLaunchpad bug 1826695 in neutron "[L3][QoS] cache does not removed when router is down or deleted" [Medium,In progress] - Assigned to LIU Yulong (dragon889)15:05
ralonsohThere is an ongoing patch15:05
ralonsoh#link https://review.opendev.org/#/c/656105/15:05
ralonsoh#topic Open Discussion15:06
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:06
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:06
ralonsohI'm still reviewing https://review.opendev.org/#/c/63633315:06
ralonsohI don't know how to decouple this feature from Neutron, making it totally independent from the Neutron code15:06
ralonsohdoing something like a service pluging15:07
ralonsohthe problem15:07
ralonsoh1)  is this feature depends on QoS15:07
ralonsoh2) requires a DB modification15:07
*** rfolco|ruck is now known as rfolco|lunch15:08
ralonsoh3) the agent QoS extension drivers should be aware of this new pluging15:08
ralonsoh--> I don't see a method of making this feature independent from Neutron15:09
ralonsohand that's all for today15:10
ralonsohsee you in two weeks, bye!15:10
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:10
openstackMeeting ended Tue May  7 15:10:50 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-05-07-15.00.html15:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-05-07-15.00.txt15:10
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-05-07-15.00.log.html15:10
*** pcaruana has quit IRC15:16
*** ygbo has joined #openstack-meeting15:19
*** rfolco|lunch is now known as rfolco|ruck|free15:22
*** rfolco|ruck|free is now known as rfolco|ruck15:22
*** jamesmcarthur has joined #openstack-meeting15:24
*** armstrong has joined #openstack-meeting15:24
*** artom has joined #openstack-meeting15:27
*** ijw has quit IRC15:28
*** cheng1__ has quit IRC15:40
*** bobh has joined #openstack-meeting15:45
*** Lucas_Gray has quit IRC15:49
*** gyee has joined #openstack-meeting15:55
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue May  7 16:00:19 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
slaweqlets wait couple more minutes for njohnston_ ralonsoh and others, maybe they will join16:01
*** ygbo has quit IRC16:01
*** e0ne has joined #openstack-meeting16:02
slaweqok, lets start16:03
slaweqfirst thing:16:03
slaweq#link http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?orgId=116:03
slaweqplease open now so it will be ready later :)16:03
slaweq#topic Actions from previous meetings16:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:03
slaweqfirst action from 2 weeks ago was16:03
slaweqmlavalle to continue debuging reasons of neutron-tempest-plugin-dvr-multinode-scenario failures16:04
mlavalleI didn't make progress on this one16:04
mlavalledue to Summit / PTG16:04
slaweqsure, I know :) Can I assign it to You for next week?16:04
mlavalleyes please16:04
slaweq#action mlavalle to continue debuging reasons of neutron-tempest-plugin-dvr-multinode-scenario failures16:04
slaweqmlavalle to recheck tcpdump patch and analyze output from ci jobs16:05
slaweqthat is next one ^^16:05
slaweqany update?16:05
mlavalleI spent time this morning looking at that16:05
mlavalleI think my tcpdump command is too broad: http://logs.openstack.org/21/653021/2/check/neutron-tempest-plugin-dvr-multinode-scenario/0a24d77/controller/logs/screen-q-l3.txt.gz#_Apr_23_00_47_57_85335716:06
mlavallegetting weird output as you can see16:06
mlavallebad checksums and that kind of stuff16:06
mlavalleso I am going to focus a little bit more16:06
mlavalleI am going to trace qr and qg interfaces16:07
mlavallewith tcp and port 2216:07
mlavallemakes sense?16:07
slaweqand please add "-n" option to not resolv IPs to hostnames16:07
slaweqIMHO it will be easier to look16:07
mlavalleyes, you are right16:08
mlavalleI will probably also focus on singe node jobs first16:08
haleyband maybe -l to not buffer16:08
slaweqyes, and also "-e" to print mac addresses16:08
mlavallethanks for the recommendations. I will follow them16:09
mlavalleI have a stupid question16:09
mlavallecan I ask it?16:09
slaweqsure :)16:09
slaweqthere are no stupid questions ;)16:09
mlavallein looking at what job to focus in kibana, I noticed this: http://logs.openstack.org/66/641866/10/check/neutron-tempest-dvr-ha-multinode-full/ec1105b/job-output.txt#_2019-05-07_14_03_22_45451716:10
mlavallewe are not using password ssh in any case, right?16:10
slaweqno, ssh key is used always I think16:11
mlavalleyes, that's what I think also16:11
mlavallebut it was worth asking the dumb question16:11
*** beagles has quit IRC16:11
slaweqthis is exactly example of this second "type" of errors with SSH connectivity16:12
slaweqlook at http://logs.openstack.org/66/641866/10/check/neutron-tempest-dvr-ha-multinode-full/ec1105b/job-output.txt#_2019-05-07_14_03_22_55072716:12
slaweqinstance-id was received properly from metadata server16:12
slaweqbut then 2 lines below, failed to get public-key16:12
slaweqit is exactly what I was testing last week16:13
mlavalledo you have a feel of what is the ratio between type 1 and type 2 failures?16:13
*** beagles has joined #openstack-meeting16:13
slaweqI don't know exactly but I would say 50:5016:13
mlavalleI think the tcpdump testing I'm doing should help with type 116:14
mlavalleso I will focus on those16:14
mlavallein type 2, we know we have connectivity16:14
mlavallebecause we fail athenticating16:14
*** jamesmcarthur has quit IRC16:15
slaweqin this case problem is with slow answer for metadata requests16:15
slaweqhere is this failed request in neutron metadata agent's logs16:18
slaweqand http://logs.openstack.org/66/641866/10/check/neutron-tempest-dvr-ha-multinode-full/ec1105b/controller/logs/screen-n-api-meta.txt.gz#_May_07_13_15_04_543966 -- that how it looks in nova16:18
slaweq10 seconds gap in logs there16:18
slaweqmlavalle: maybe You can try to talk with someone from nova team to look into those issues16:19
slaweqcan I add it as an action for You also?16:20
slaweq#action mlavalle to talk with nova folks about slow responses for metadata requests16:20
slaweqok, next one was16:20
slaweqnjohnston move wsgi jobs to check queue nonvoting16:20
slaweqI know it's done, we have wsgi jobs running in check queue currently16:21
slaweqand tempest job is kinda broken now16:21
*** manjeets__ is now known as manjeets16:21
slaweqso we will have to investigate it also16:21
slaweqbut that isn't very urgent for now16:21
slaweqnext one then16:22
slaweqralonsoh to debug issue with neutron_tempest_plugin.api.admin.test_network_segment_range test16:22
slaweqI don't know if ralonsoh did anything with it16:22
ralonsohI didn't have time for it16:22
slaweqsure, no problem :)16:22
slaweqcan I assign it to You for this week?16:23
slaweq#action ralonsoh to debug issue with neutron_tempest_plugin.api.admin.test_network_segment_range test16:23
slaweqthx ralonsoh :)16:23
slaweqand the last one was:16:23
slaweqslaweq to cancel next week meeting16:23
slaweqdone - that was easy :P16:23
slaweqok, any questions/comments?16:23
slaweqok, I will take this silence as no :)16:24
slaweqso lets move on then16:24
slaweq#topic Stadium projects16:24
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:24
*** zaneb has joined #openstack-meeting16:24
slaweqfirst "Python 3 migration"16:25
slaweqetherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:25
*** whoami-rajat has quit IRC16:25
slaweqI know that tidwellr started doing something with neutron-dynamic-routing repo16:25
slaweqhis patch https://review.opendev.org/#/c/657409/16:26
slaweqI just checked that for neutron-lib we are actually good16:27
*** vishalmanchanda has quit IRC16:28
slaweqI will try to go through those projects in next weeks16:28
slaweqanyone wants to add something in this topic?16:29
slaweqok, lets move on16:29
slaweqtempest-plugins migration16:30
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:30
slaweqand I have a question here16:30
slaweqI was recently struggling with error on jobs run on rocky and queens repos for networking-bgpvpn16:30
slaweqbut at the airport yesterday I realized that we probably don't need to run those jobs for stable branches yet16:31
slaweqas we will not remove tests from stable branches from stadium projects' repos, right?16:31
slaweqso we should only have this jobs in neutron-tempest-plugin repo for master branch for now and add stable branches jobs starting from Train release16:32
slaweqis that correct?16:32
mlavalleI think so16:32
slaweqok, so that will make at least my patch easier :)16:33
slaweqI will remove jobs for stable branches from it and it will be ready for review than16:33
slaweqany other questions/updates?16:34
mlavallenot from me16:35
slaweqok, so lets move on then16:35
slaweq#topic Grafana16:35
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:35
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate - just a reminder :)16:35
slaweqthere isn't anything very bad there - all looks pretty same as usual16:36
*** njohnsto_ has joined #openstack-meeting16:37
mlavalleI think so16:37
slaweqdo You so anything what You want  to talk about?16:37
haleybis there a bug for the slow job failure? looks like a volume issue?16:38
slaweqhaleyb: issues with volume (or volume backup) happens in various tempest jobs quite often16:38
slaweqhaleyb: do You have link to example?16:38
haleybsecond failure16:39
slaweqyes, such errors happens from time to time16:39
slaweqI'm not sure if exactly this one was reported to cinder but I was reporting some similar errors already16:40
*** njohnsto_ has quit IRC16:40
slaweqand we also discussed about it in QA session on PTG16:40
haleybjust seemed like it picked up recently in the gate, at 20% now16:40
slaweqI hope You all saw recent email from gmann about it16:40
*** whoami-rajat has joined #openstack-meeting16:43
slaweqhaleyb: I'm not sure if those 20% are only because of this issue16:43
slaweqoften there are also problems with ssh to instances16:43
slaweqok, lets move on to the next topic16:44
haleybslaweq: yes, that was in the other test failure, it's just at 2x the other jobs for failures16:44
slaweqhaleyb: where tempest-slow is 2x the other jobs failures? I don't see it to be so high16:44
*** e0ne has quit IRC16:45
haleybslaweq: argh, it's number of jobs run, i was looking at the right side...16:45
slaweqahh :)16:45
slaweqbut that is kinda strange that this job was so many times :)16:46
haleybright, they should all be the same16:46
slaweqyes, I will check if this graph is properly defined in grafana16:46
slaweqit is not16:47
slaweqit counts jobs from check queue instead of gate queue16:47
slaweqI will fix that16:47
slaweq#action slaweq to fix number of tempest-slow-py3 jobs in grafana16:48
slaweqthx haleyb for pointing this :)16:48
slaweqok, lets move on then16:48
slaweq#topic fullstack/functional16:48
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:49
slaweqwe still have quite high failure rates for those jobs :/16:49
slaweqfor functional tests quite often we still hits bug https://bugs.launchpad.net/neutron/+bug/182303816:49
openstackLaunchpad bug 1823038 in neutron "Neutron-keepalived-state-change fails to check initial router state" [High,Confirmed]16:49
slaweqlike e.g. in     * http://logs.openstack.org/64/656164/1/gate/neutron-functional/c59dd7c/testr_results.html.gz16:49
*** yamahata has quit IRC16:50
slaweqand I have a question to You about that16:50
slaweqsome time ago I did https://github.com/openstack/neutron/commit/8fec1ffc833eba9b3fc5f812bf881f44b4beba0c16:51
slaweqto address this race condition between keepalived and neutron-keepalived-state-change16:51
slaweqand it works fine for me locally16:51
slaweqbut in the gate for some (unknown for me) reason, this initial check of status is failing with error like http://logs.openstack.org/64/656164/1/gate/neutron-functional/c59dd7c/controller/logs/journal_log.txt.gz#_May_07_11_21_0516:52
slaweqI have no idea why it is like that16:52
slaweqmaybe You can take a look into that and help me with it16:53
haleybslaweq: sorry, tuned out for a second, will look16:53
slaweqI send today some DNM patch https://review.opendev.org/#/c/657565/ to check if this binary is really in .tox/dsvm-functional/bin directory16:53
slaweqand it is there16:54
mlavallethanks haleyb.16:54
slaweqthanks haleyb16:55
haleybslaweq: hmm, privsep-helper not found?  that's odd16:55
mlavallefwiw, I've been noting in the devstack I run in my mac (1 controller / network, 1 compute, DVR) that my HA routers sometimes has 2 masters16:55
haleybslaweq: project-config fix @ https://review.opendev.org/657646 :)16:56
mlavallethat happens after I restart the deployment16:56
slaweqmlavalle: that is probably different issue16:56
slaweqwhen this "my race" happend there were 2 standby routers instead of masters16:57
slaweqhaleyb: thx16:57
slaweqhaleyb: but in my DNM patch I tried to install oslo.privep simply16:58
mlavalleI'll try to debug it then16:58
slaweqand it looks that for python2.7 job it can find it now16:58
slaweqbut there is another error there still :/16:58
slaweqI will have to look into it16:58
*** radeks_ has quit IRC16:59
slaweqand this is odd because it works fine for me locally, and I also don't think there are such errors in e.g. tempest jobs16:59
slaweqso this issue is now strictly related to functional jobs IMO16:59
slaweqok, I think we are running out of time now16:59
slaweqthx for attending and see You next week17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue May  7 17:00:08 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-05-07-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-05-07-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-05-07-16.00.log.html17:00
*** njohnston_ is now known as njohnston17:01
*** armax has quit IRC17:02
*** iyamahat has joined #openstack-meeting17:03
*** iyamahat_ has joined #openstack-meeting17:05
*** iyamahat has quit IRC17:08
*** mlavalle has left #openstack-meeting17:08
*** bobh has quit IRC17:14
*** armax has joined #openstack-meeting17:18
*** ttsiouts has joined #openstack-meeting17:22
*** yamahata has joined #openstack-meeting17:24
*** bobh has joined #openstack-meeting17:42
*** kopecmartin is now known as kopecmartin|off17:46
*** ttsiouts has quit IRC17:47
*** electrofelix has quit IRC17:47
*** ttsiouts has joined #openstack-meeting17:48
*** armax has quit IRC17:51
*** lbragstad has quit IRC17:59
*** lbragstad has joined #openstack-meeting17:59
*** ralonsoh has quit IRC18:00
*** mattw4 has joined #openstack-meeting18:06
*** ijw has joined #openstack-meeting18:08
*** armax has joined #openstack-meeting18:12
*** ttsiouts has quit IRC18:14
*** ijw has quit IRC18:14
*** ijw has joined #openstack-meeting18:14
*** ijw has quit IRC18:15
*** ijw has joined #openstack-meeting18:16
*** ijw has quit IRC18:17
*** ijw has joined #openstack-meeting18:17
*** armax has quit IRC18:17
*** armstrong has quit IRC18:18
*** ijw has quit IRC18:19
*** ijw has joined #openstack-meeting18:20
*** ttsiouts has joined #openstack-meeting18:29
*** ttsiouts has quit IRC18:35
*** ayoung has joined #openstack-meeting18:36
*** Shrews has joined #openstack-meeting18:40
*** zbr is now known as zbr|pto18:45
*** _hemna has joined #openstack-meeting18:51
*** ayoung has quit IRC18:54
*** bobh has quit IRC18:55
*** ayoung has joined #openstack-meeting18:56
clarkbInfra meeting time19:00
clarkbanyone else here for that?19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue May  7 19:01:09 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
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-May/006360.html19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** ttsiouts has joined #openstack-meeting19:02
clarkbI've got a really weird week coming up between recovering from being away from home for 9 days, my wife is having minor surgery on Wednesday, and somewhere in there I'm visiting the dentist too. Mostly just a heads up that I may not be around during normal hours19:02
clarkbI get a feeling that for many of us that were in denver this is also true19:03
corvusthis is true for me, though the particulars are different19:03
fungibest to assume it's a fairly weird week for everyone19:04
fungiand i'll be entirely afk thursday through monday19:04
fungifor vacation19:04
clarkboh also I've got a shower that leaks19:05
clarkbthough I think I'm just gonna have ap lumber deal with that so I can do the other stuff19: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-04-23-19.01.txt minutes from last meeting19:05
clarkbIt has been a while since we had a meeting and we were all recovering from post opendev migration in that meeting19:05
clarkbMay as well jump ahead straight into the fun stuff I think19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic OpenDev19:06
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:06
*** ttsiouts has quit IRC19:06
clarkbAt the PTG fungi, corvus, mordred, ttx and myself were able to have some discussions around the high level needs for OpenDev19:07
clarkb#link https://etherpad.openstack.org/p/2019-denver-ptg-infra-planning PTG Discussion notes19:07
mordredit was good19:07
clarkbThat has some notes on the thoughts for this. Basically we would like to have namespace owners and delegate responsibility for what goes into a namespace to them19:07
corvusclarkb: lines 59-69?19:08
clarkbWe were thinking that we would create a meta config repo per namespace to track and manage that19:08
corvuscan folks not at the discuss follow lines 59-69?  or do we need to write that up in more words (as a ML post or spec?)19:08
corvusnot at the *discussion*19:08
clarkbI half expect we'll need to write that up as a spec19:09
clarkbbut I agree, would be good to get input from folks that weren't able to be at the PTG.19:10
mordredyeah. I imagine it will be basically what's in those lines with more conjunctions and stuff19:10
clarkbI'm happy to write up a recap email using more words too (which may help me remember things better as well)19:10
mordredmaybe more pronouns and adverbs thrown in19:10
*** tesseract has quit IRC19:10
*** pabelanger has joined #openstack-meeting19:11
clarkbOther opendev related items: We need to fix our gitea deployment so that we can upgrade gitea to 1.8.0 + corvus' patch19:11
clarkbDeleting the old cgit servers is on my todo list as well19:11
mordredthe update to the test jobs is getting *closer819:12
clarkbya thats the next topic of discussion maybe we should jump ahead and I'll take on the todo of writing a recap email in the near future (to add more words to our notes on the therpad)19:12
corvusthe hangup on gitea is https://review.opendev.org/65552219:12
corvustests for that change caught a legit behavior change which needs to be investigated19:13
clarkb#link https://review.opendev.org/655522 Upgrades gitea to 1.8.0 but our tests discovered a legit behavior change that needs investigating19:13
*** yamamoto has joined #openstack-meeting19:13
mordredyeah. we're also making updates to that test job in https://review.opendev.org/#/c/656871/ - which is orthogonal to the behavior change19:13
clarkb#action clarkb Write PTG (and summit) recap email to capture our discussions there19:13
clarkb#topic Update Configuration Management19:14
*** openstack changes topic to "Update Configuration Management (Meeting topic: infra)"19:14
clarkbAnother major topic of discussion was how to get from where we are today with cron + ansible to zuul + ansible for deploying our systems19:14
corvuslines 46-57 on the etherpad19:14
clarkb#link https://review.opendev.org/#/c/656871/ Split base playbook into many playbooks19:15
corvus656871 implements lines 47-5019:15
mordredit is currently unhappy making the root account in the gitea install for reasons I don't grok yet19:15
clarkbThis change is the result of those discussions. The general idea being that if we have finer grained playbooks we can have zuul run those when appropriate without needing to run the whole thing every time19:15
clarkbThe step after that chnage will be to add zuul jobs to run those playbooks19:15
corvusthat'll be important for infra-core folks to know about, since once we land that, we'll want to keep going in that direction and no longer overload the base playbook.19:16
mordredit's very exciting progress19:16
clarkbI think we expect to have a cron of some sort (perhaps zuul periodic pipeline driven) to ensure base level things like firewalls are up to date across the board19:17
clarkbbut have most service level stuff driven by specific zuul updates19:17
clarkbAlso on the config management side of the house we are ready to do our last set of puppet 4 updates. So I may bug people for reviews on those once I am properly back to being able to watch that19:18
clarkbOnce that is done we can cleanup a bunch of our old puppet 3 jobs19:18
clarkbwhich should hopefully make testing quicker and more reliable for our system changes19:18
fungialso implications that we'll be able to (eventually) drop the puppet apply and beaker jobs19:18
fungionce we're exercising them all via the ansible run jobs19:19
mordredyeah. because then puppet becomes an impl detail of the playbook for the service19:19
clarkbAnd finally, I think our docker image jobs are pretty robust at this point but we still do sometimes have jobs fail because they try to authenticate to dockerhub as if they are our local registry. I've got an agenda item for this towards the end of the meeting19:19
clarkb#topic Storyboard19:20
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:20
clarkbwe discovered that we had improperly created some storyboard groups at the summit19:20
clarkbfungi got those sorted out19:20
clarkbmy email inbox went crazy with storyboard story updates during last week as well19:21
clarkbI think SotK persia and diablo_rojo_phon were busy19:21
clarkbwas anyone better than me at following along on what changes were being made?19:21
fungiyes, they had a storysquash at the ptg19:21
fungibasically triaging and combining/splitting/closing stories for storyboard and storyboard-webclient19:22
clarkbThere was also a constructive feedback session at the forum19:23
* clarkb finds a link to the etherpad for that19:23
clarkb#link https://etherpad.openstack.org/p/storyboard-pain-points19:23
clarkb#topic General Topics19:24
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:24
clarkb#link https://etherpad.openstack.org/2019-denver-ptg-infra-planning Denver PTG 2019 notes19:24
clarkbin case anyone missed it ^ is where the notes were taken during the PTG19:25
clarkbI've also just taken an action to write up a recap email so keep an eye out on the -infra list for that19:25
clarkbIs there anything we haven't already touched on that people want more details on? questions? concerns?19:25
ianwdoes splitting up the base playbook like this mean the bridge mysql/ara work is basically not necessary?19:26
ianwwe'll just essentially have the logs from post job runs instead?19:27
corvusianw: we're still expecting the playbooks to run via bridge's ansible, so that could still be useful19:27
corvus(i think that ways always the plan)19:27
clarkbianw: we will have those logs, but the way the current CD jobs are set up is to execute ansible-playbook on bridge19:27
clarkb(so we won't get the data in the zuul ara)19:27
*** jamesmcarthur has joined #openstack-meeting19:27
ianwahh, right, that was your root login stuff19:27
clarkbgiven that I think having ara for the bridge run ansible-playbook is still useful19:28
fungiwhich is probably good for avoiding information leaks anyway19:28
ianwcool, ok thanks for clarifying19:28
*** tssurya has quit IRC19:29
mordredianw: oh - speaking of - I pinged you in scrollback about the letsencrypt roles - but it turns out we weren't running one of them, so nothing to worry about :)19:29
clarkbThat is a good transition to the next topic :)19:29
clarkbwe have a buildset registry and a buildset proxy registry in our docker image build jobs19:29
clarkbsometimes that buildset proxy registry fails (seems to happen more on ipv6 clouds that NAT to dockerhub) so my idea to fix that is to use the in region docker proxy19:30
clarkbthose in region mirror nodes have a floating IP so don't go through the many to one nat shared by the test nodes19:30
clarkbHowever corvus pointed out that since we'll be publishing the resulting docker images we should get tls set up on those first19:30
clarkbmy plan is to roughly add all our in region mirrors to opendev.org DNS, add ssl vhosts to them then run the LE stuff to get certs for the opdnev.org names19:31
clarkbThen with SNI I don't even need to change ports19:31
fungithat'll be nice19:32
clarkbAs part of this we probably want to transition most/many things to https (and not just the dockerhub proxy)19:32
clarkbI expect apt to present the biggest pain there but otherwise should be a win all around19:33
clarkbianw: ^ any concerns with doing that given your LE work?19:33
clarkblike should https://review.opendev.org/#/c/652801/ get in first?19:33
clarkb#link https://review.opendev.org/#/c/652801/ Add handlers for LE certs updates for integration with existing services19:34
clarkbinfra-root ^ if you have time to review that it would be much appreciated19:34
*** jamesmcarthur has quit IRC19:34
*** _hemna has quit IRC19:34
*** jamesmcarthur has joined #openstack-meeting19:34
ianwclarkb: yeah, i think it could be a bit asynchronous.  we can deploy the keys first and make sure they're all there ok, then update the puppet to insert them into apache config19:35
ianwthen, within at least 90 days i guess, we need something to figure out restarting apache when then renew :)19:35
ianwbut probably having that before we start is a better idea19:35
clarkbya, would be good to have that sorted out before we have too many to retrofit19:35
*** jamesmcarthur has quit IRC19:35
*** jamesmcarthur has joined #openstack-meeting19:36
ianwmy idea, with 652801 would be that ansible would drop a flag file, which puppet would notice, remove and restart apache19:36
ianwas we, someday, move the hosts to more ansible control, we should be integrate more with listeners etc19:37
clarkbianw: have you had a chance to see my comments on that change yet?19:37
clarkbcurious to see what you think about them (but overall I was happy with the chagne)19:37
corvuswhy have puppet do it and not ansible directly?19:37
clarkbcorvus: that was one of my questions :)19:37
corvusah i see that now :)19:38
ianwi haven't cycled, back, but will today.  i'm happy to help setup the initial mirror certs19:38
clarkbgreat thanks19:38
corvus(it doesn't bother me that ansible would be restarting a service it didn't set up)19:38
clarkbThe last item I had on the agenda this week was to bring up the trusty upgrades/cleanups19:38
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:38
ianwwill respond, but the idea was that ansible *can* do it, if we want -- but there might be things where it's more complex than service foo restart so i wanted to make sure it could be flexible19:39
clarkbI'd like to delete the groups servers this week if I can find time to sit down and make sure I back them up and delete the right instances19:39
clarkbIf we can finish cleaning up this list we'll be able to remove old nodepool images and test jobs which is nice to have on top of the EOL problem19:39
clarkbfungi: ^ re groups ashlee had thoguht you had already done a db backup and/or instance snapshot19:39
clarkbfungi: do you know if any of that has been done yet?19:40
fungiyes, i did19:40
clarkbcool so mostly just a matter of deleting the instances now?19:40
fungithere is a db snapshot and a server snapshot19:40
clarkbI can add them to the list with the old cgit cluster19:40
fungiyes, should be safe to proceed19:40
clarkbFor those of you that have names on updating some of those remaining services let me know if I can do anything to help19:41
clarkbAnd with that I think we've hit the end of our agenda19:42
clarkb#topic Open Discussion19:42
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:42
*** jamesmcarthur has quit IRC19:42
clarkbWe should set a date for straggler opendev renames to happen19:42
clarkbthen encourage everyone to update the rename request list for that to happen if they want a rename19:42
*** ttsiouts has joined #openstack-meeting19:43
clarkbmaybe the end of the month (gives people time to get back from summit and realize they want a rename)19:43
*** ayoung has quit IRC19:43
fungisounds good to me, i should be around after this weekend19:43
ianwone thing to update on is testinfra which i've spent a bit of time with.  it's ansible 2.8 compatible now ... but not using ansible-runner unfortunately19:44
corvusmy schedule returns to normal after may 2219:44
clarkbianw: I suppose as long as it works with newer ansible our use case is met19:44
clarkbcorvus: fungi rgr seems like the 31st might be a good day to pencil in then (thinking others are also in recovery mdoe and may not even notice yet that a name needs changing)19:44
ianwclarkb: sort of, i've sent in a fix for ipv6 addresses that broke us19:45
pabelangerI actually had one, but didn't add it to meeting agenda. Where do we stand on getting nodepool / k8s integration? ~5months ago we landed: https://review.opendev.org/620755 for kube config for nodepool, but I kinda lost track where things are. Given what we know about namespaces in k8s / nodepool / zuul, is that something someone could pick up again and try to say get tox job on k8s? Or do we need19:45
pabelangernew features in zuul / nodepool?19:45
clarkbianw: fun19:45
ianwmordred: could you look at https://review.opendev.org/656908 which lets us install testinfra in tox sibilings correctly19:45
clarkbpabelanger: I believe everything is in place for that to work now. Just need to add jobs for it (but I'm sure that if you add jobs for it we'll discover other fixes are necessary_19:45
mordredpabelanger: it's a thing I think we're definitely still poking at - but I don't think we're in a rush to run tox jobs in k8s because it'll ultimately be more expensive to do so19:45
clarkbmordred: pabelanger right I think the idea was to start with jobs that exercise nodepool'19:46
clarkbs support of k8s19:46
clarkbnot to shift large workload to it19:46
corvusyeah, if someone wants to poke at that i say go for it19:46
pabelangerokay, that is fine, I mostly wanted to say I am interestd in it, and think I can offer some time to enable it.  I just used tox as example.19:46
mordredtotes - and I think it would be great to have you poke at it19:47
corvusthere is a chance that i screwed up the credentials for that and we might need to re-export them19:47
pabelangerso, expect some questions in coming days on what we'd like to do :)19:47
*** yamamoto has quit IRC19:47
pabelangercool, thanks!19:47
* mordred hands pabelanger a turkey19:48
clarkbAlright, anything else before we call it a meeting?19:50
clarkbSounds like no. Everyone enjoy their weird weeks and thank you! See you here next week.19:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:52
openstackMeeting ended Tue May  7 19:52:28 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-05-07-19.01.html19:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-05-07-19.01.txt19:52
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-05-07-19.01.log.html19:52
fungithanks clarkb!19:52
*** bbowen_ has quit IRC20:12
*** ttsiouts has quit IRC20:16
*** artom has quit IRC20:31
*** diablo_rojo has joined #openstack-meeting20:32
*** slaweq has quit IRC20:36
*** slaweq has joined #openstack-meeting20:42
*** tssurya has joined #openstack-meeting20:52
*** slaweq has quit IRC20:55
*** raildo has quit IRC21:10
*** slaweq has joined #openstack-meeting21:12
*** diablo_rojo has quit IRC21:15
*** ttsiouts has joined #openstack-meeting21:18
*** ttsiouts has quit IRC21:23
*** slaweq has quit IRC21:25
*** bbowen_ has joined #openstack-meeting21:30
*** hongbin has joined #openstack-meeting21:35
*** mriedem has quit IRC21:36
*** mattw4 has quit IRC21:46
*** mattw4 has joined #openstack-meeting21:50
*** ijw has quit IRC21:57
*** ijw has joined #openstack-meeting21:57
*** slaweq has joined #openstack-meeting22:11
*** njohnston has quit IRC22:15
*** slaweq has quit IRC22:24
*** jamesmcarthur has joined #openstack-meeting22:57
*** bobh has joined #openstack-meeting23:03
*** ayoung has joined #openstack-meeting23:04
*** rcernin has joined #openstack-meeting23:06
*** slaweq has joined #openstack-meeting23:11
*** yamamoto has joined #openstack-meeting23:17
*** artom has joined #openstack-meeting23:21
*** bobh has quit IRC23:21
*** slaweq has quit IRC23:24
*** jamesmcarthur has quit IRC23:27
*** ttsiouts has joined #openstack-meeting23:35
*** lseki has quit IRC23:40
*** hongbin has quit IRC23:41
*** bbowen_ has quit IRC23:47
*** bbowen_ has joined #openstack-meeting23:47
*** whoami-rajat has quit IRC23:55
*** mattw4 has quit IRC23:56

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