Tuesday, 2020-01-28

*** njohnston_ has quit IRC00:28
*** njohnston has joined #openstack-meeting00:28
*** dviroel has quit IRC00:31
*** jhesketh has joined #openstack-meeting00:41
*** mattw4 has quit IRC00:43
*** gyee has quit IRC01:17
*** jamesmcarthur has joined #openstack-meeting01:18
*** enriquetaso has quit IRC01:23
*** yamamoto has joined #openstack-meeting01:26
*** jamesmcarthur has quit IRC01:43
*** diablo_rojo has joined #openstack-meeting01:59
*** jamesmcarthur has joined #openstack-meeting02:07
*** mhen has quit IRC02:07
*** jamesmcarthur has quit IRC02:19
*** yamamoto has quit IRC02:19
*** yamamoto has joined #openstack-meeting02:20
*** Liang__ has joined #openstack-meeting02:28
*** yamamoto has quit IRC02:39
*** yamamoto has joined #openstack-meeting02:42
*** yamamoto has quit IRC02:42
*** yamamoto has joined #openstack-meeting02:43
*** jamesmcarthur has joined #openstack-meeting02:44
*** masahito has joined #openstack-meeting02:45
*** jamesmcarthur has quit IRC02:45
*** jamesmcarthur has joined #openstack-meeting02:50
*** yamamoto has quit IRC02:52
*** diablo_rojo has quit IRC02:53
*** jamesmcarthur_ has joined #openstack-meeting02:54
*** jamesmcarthur has quit IRC02:54
*** jamesmcarthur_ has quit IRC03:03
*** jamesmcarthur has joined #openstack-meeting03:03
*** jamesmcarthur has quit IRC03:08
*** yamamoto has joined #openstack-meeting03:29
*** jamesmcarthur has joined #openstack-meeting03:34
*** jmasud has joined #openstack-meeting03:35
*** jamesmcarthur has quit IRC03:41
*** jmasud has quit IRC03:50
*** tpatil has joined #openstack-meeting03:50
*** jmasud has joined #openstack-meeting03:54
*** diablo_rojo has joined #openstack-meeting04:01
tpatilPing Masakari members?04:03
*** shilpasd has joined #openstack-meeting04:06
tpatil#startmeeting Masakari04:07
openstackMeeting started Tue Jan 28 04:07:10 2020 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:07
*** openstack changes topic to " (Meeting topic: Masakari)"04:07
openstackThe meeting name has been set to 'masakari'04:07
tpatilHi All04:07
shilpasdtpatil: Hi04:07
*** kiyofujin has joined #openstack-meeting04:08
tpatilshilpasd: Hi04:08
tpatil#topic Critical Bugs04:08
*** openstack changes topic to "Critical Bugs (Meeting topic: Masakari)"04:08
tpatilLP Bug #185876204:09
openstackLaunchpad bug 1858762 in masakari "“UNKNOWN” host_status notification may cause unsafe evacuation" [Critical,Confirmed] https://launchpad.net/bugs/185876204:09
tpatilIt seems like a simple fix04:10
*** masahito has quit IRC04:10
shilpasdtpatil: ok, will assigned to me and will fix04:10
tpatilThat will be great04:11
tpatilshilpasd: Do you want to discuss about any other reported bugs?04:14
shilpasdtpatil: LP Bug #185875704:14
openstackLaunchpad bug 1858757 in masakari "nova process not disable" [Undecided,New] https://launchpad.net/bugs/185875704:14
tpatilI have added one review comment on the patch : https://review.opendev.org/#/c/701506/04:14
patchbotpatch 701506 - masakari - nova process not disable - 1 patch set04:14
shilpasdtpatil: ok, thank you04:15
tpatilI think this issue can be fixed in masakari-processmonitor instead of masakari04:15
tpatilMoving next04:16
tpatil#topic Ussuri work items04:16
*** openstack changes topic to "Ussuri work items (Meeting topic: Masakari)"04:16
tpatil#link : https://etherpad.openstack.org/p/masakari-u-workitems04:17
tpatilEvacuate non-recovery (’HA_enabled = False’) instances in shutoff status at host failure except specified tenants04:17
tpatilThere is a specs uploaded for this item. will review it soon04:18
tpatilFor past 2-3 weeks, I have been very busy working on another OpenStack project so I couldn't spend lot of time on Masakari04:18
*** rcernin has quit IRC04:18
*** rcernin has joined #openstack-meeting04:18
shilpasdtpatil: ya i know, hope you will b free very soon04:19
tpatilSorry for that. Will start checking all backlogs starting from end of next week.04:19
shilpasdbe*04:19
shilpasdtpatil: thank you!04:19
tpatilspecs : https://review.opendev.org/#/c/702427/04:19
patchbotpatch 702427 - masakari-specs - Evacuate non-recovery (`HA_enabled = False`) insta... - 2 patch sets04:19
tpatilI will review this specs as soon as I get time04:20
shilpasdtpatil: thanks04:20
tpatil#2: Modify masakari-hostmonitor in order to run it inside container04:20
tpatilAny update?04:20
tpatilI think the bigger issue is testing in the CI gate job04:21
shilpasdtpatil: not started yet because of other engagements, will start after pushing fixes for LP Bug #185876204:21
openstackLaunchpad bug 1858762 in masakari "“UNKNOWN” host_status notification may cause unsafe evacuation" [Critical,Confirmed] https://launchpad.net/bugs/1858762 - Assigned to Shilpa Devharakar (shilpasd)04:21
tpatilpresently, we don't have CI job to run masakari-hostmonitor as it requires pacemaker and multinode setup04:22
tpatilshilpasd: OK04:22
tpatil#3: Command parameter support to segment list command to filter out segments based on host input parameter04:22
shilpasdtpatil: changes are done, its under internal review, once done will upload to CG for review04:23
*** armax has quit IRC04:24
tpatilshilpasd: I know that you are working on this item. Can you please report it as a bug so that we can include it in the release notes.04:24
shilpasdtpatil: yes will do that today and will let you know once done04:24
tpatilshilpasd: Thanks04:25
tpatilThat's all work items listed in the etherpad for Ussuri04:26
tpatilmoving next04:27
tpatil#topic AOB04:27
*** openstack changes topic to "AOB (Meeting topic: Masakari)"04:27
shilpasdtpatil: nothing from my side04:28
tpatilok, Let's end this meeting then04:28
tpatilThank you, All04:28
tpatil#endmeeting04:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:29
openstackMeeting ended Tue Jan 28 04:29:12 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-01-28-04.07.html04:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-01-28-04.07.txt04:29
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-01-28-04.07.log.html04:29
*** masahito has joined #openstack-meeting04:35
*** jamesmcarthur has joined #openstack-meeting04:37
*** jamesmcarthur has quit IRC04:41
*** kiyofujin has quit IRC04:45
*** tpatil has quit IRC04:47
*** jamesmcarthur has joined #openstack-meeting05:12
*** jamesmcarthur has quit IRC05:18
*** links has joined #openstack-meeting05:25
*** links has quit IRC05:25
*** masahito_ has joined #openstack-meeting05:32
*** masahito has quit IRC05:32
*** toabctl has quit IRC06:05
*** toabctl has joined #openstack-meeting06:12
*** jamesmcarthur has joined #openstack-meeting06:13
*** masahito_ has quit IRC06:15
*** lpetrut has joined #openstack-meeting06:16
*** jamesmcarthur has quit IRC06:18
*** e0ne has joined #openstack-meeting06:26
*** masahito has joined #openstack-meeting06:31
*** psachin has joined #openstack-meeting06:39
*** jamesmcarthur has joined #openstack-meeting06:51
*** jamesmcarthur has quit IRC06:56
*** e0ne has quit IRC07:15
*** ociuhandu has joined #openstack-meeting07:30
*** njohnston has quit IRC07:33
*** ociuhandu has quit IRC07:35
*** yamamoto has quit IRC07:37
*** slaweq has joined #openstack-meeting07:38
*** yunyoung has joined #openstack-meeting07:40
*** jamesmcarthur has joined #openstack-meeting07:52
*** jamesmcarthur has quit IRC07:57
*** joxyuki98 has joined #openstack-meeting08:01
joxyuki98#startmeeting tacker08:01
openstackMeeting started Tue Jan 28 08:01:25 2020 UTC and is due to finish in 60 minutes.  The chair is joxyuki98. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: tacker)"08:01
openstackThe meeting name has been set to 'tacker'08:01
yunyounghello08:01
yunyoungI want to be a contributor of tacker project08:02
joxyuki98#topic Roll Call08:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:02
joxyuki98hi yunyoung08:02
yunyounghi ~08:02
joxyuki98welcome to the Tacker project!08:02
joxyuki98Is this your first time to attend our IRC meeting?08:03
yunyoungyeah it is first time08:03
yunyoungI uploaded the blueprint08:03
joxyuki98good08:03
yunyoungbut there is no review..08:03
yunyoungso I want to get your review08:04
joxyuki98okey. please wait a while for other attendees.08:04
*** takahashi-tsc has joined #openstack-meeting08:05
yunyoungok!08:06
*** rpittau|afk is now known as rpittau08:07
*** masahito has quit IRC08:09
joxyuki98let's start. I have another schedule after 20 miniutes.08:10
joxyuki98#topic BP08:10
*** openstack changes topic to "BP (Meeting topic: tacker)"08:10
joxyuki98yunyoung, do you have any discussion related to your spec?08:11
joxyuki98https://review.opendev.org/#/c/685867/08:11
patchbotpatch 685867 - tacker-specs - blueprint - 4 patch sets08:11
yunyoungI uploaded blueprint. Here is my url for my blueprint.08:11
yunyounghttps://review.opendev.org/#/c/685867/08:11
patchbotpatch 685867 - tacker-specs - blueprint - 4 patch sets08:11
*** yamamoto has joined #openstack-meeting08:12
*** yamamoto has quit IRC08:12
*** yamamoto has joined #openstack-meeting08:12
yunyoungCan you approve my bluerint ?08:12
joxyuki98Yeah, I will review it in a few days. But your spec seems to need more changes.08:13
joxyuki98Could you check https://docs.openstack.org/infra/manual/developers.html# when you have a time?08:14
joxyuki98This page instructs you how to write a spec and patches.08:14
yunyoungI already see that page08:15
yunyoungwhat should I modify my blueprint?08:15
joxyuki98thanks.08:15
*** tesseract has joined #openstack-meeting08:16
joxyuki98At first, https://review.opendev.org/#/c/685867/ is a "spec", not a blueprint. You should register a blueprint to launchpad.08:16
patchbotpatch 685867 - tacker-specs - blueprint - 4 patch sets08:16
joxyuki98https://blueprints.launchpad.net/tacker08:17
yunyoungwe registered that to launchpad08:17
yunyounghttps://blueprints.launchpad.net/tacker/+spec/redundancy-module-vnffg08:17
yunyounghere is url of my launchpad08:17
joxyuki98good, then you should link your spec to the blueprint by writing proper commit message.08:18
hyunsikyangHi jo and all,08:19
hyunsikyangI am late.08:19
joxyuki98https://wiki.openstack.org/wiki/GitCommitMessages, here is a guide of commit message.08:19
joxyuki98hi hyunsikyang08:19
yunyoungwhat shoud I do more for review? link my spec to bluepint? I don't know what that means exactly...08:21
joxyuki98yunyoung, I will put comments including such of commit message once I review your spec. But it is helpful if you read the guide and make change by yourself.08:21
joxyuki98Sorry but I have only 8 minutes left. hyunsikyang, do you have anything to talk?08:23
hyunsikyangNO. I checked your comment.08:23
hyunsikyangI will reply it on my review08:24
joxyuki98Thanks. I don't intend to block your proposal and look forward to your reply.08:25
yunyoungjoxyuki. then if I want your approvement, should I modify blueprint?08:25
joxyuki98No, you should modify your "spec".08:25
yunyounghttp://specs.openstack.org/openstack/tacker-specs/specs/stein/vdu-auto-healing.html08:27
yunyounglike this?08:27
*** jamesmcarthur has joined #openstack-meeting08:27
joxyuki98It is one of the sample and for example see https://review.opendev.org/#/c/582930/08:28
patchbotpatch 582930 - tacker-specs - VNF packages support for VNF onboarding (MERGED) - 20 patch sets08:28
hyunsikyangyunyoung, I think, at first you should describe in your spec abstract. Not blueprint.08:29
hyunsikyangyou should describe your abstract in your spec...08:30
joxyuki98Yes, please write proper commit message.08:30
*** nitinuikey has joined #openstack-meeting08:30
yunyoungah.. okay08:30
yunyoungthanks!08:30
joxyuki98I am very sorry but I have to leave. Thanks guys and welcome yunyoung.08:31
joxyuki98#endmeeting08:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:31
openstackMeeting ended Tue Jan 28 08:31:08 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-01-28-08.01.html08:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-01-28-08.01.txt08:31
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-01-28-08.01.log.html08:31
*** joxyuki98 has quit IRC08:31
*** jamesmcarthur has quit IRC08:32
*** rubasov has joined #openstack-meeting08:35
*** ralonsoh has joined #openstack-meeting08:38
*** yunyoung has quit IRC08:38
*** tetsuro has joined #openstack-meeting08:58
*** priteau has joined #openstack-meeting08:59
*** nitinuikey has quit IRC09:40
*** yamamoto has quit IRC09:44
*** takahashi-tsc has quit IRC09:44
*** yamamoto has joined #openstack-meeting09:46
*** yamamoto has quit IRC09:50
*** masahito has joined #openstack-meeting10:01
*** _erlon_ has quit IRC10:03
*** _erlon_ has joined #openstack-meeting10:03
*** ociuhandu has joined #openstack-meeting10:08
*** Lucas_Gray has joined #openstack-meeting10:10
*** electrofelix has joined #openstack-meeting10:10
*** ociuhandu has quit IRC10:21
*** Lucas_Gray has quit IRC10:32
*** masahito has quit IRC10:36
*** Lucas_Gray has joined #openstack-meeting10:40
*** anastzhyr has quit IRC10:45
*** yunyoung has joined #openstack-meeting10:51
*** ociuhandu has joined #openstack-meeting10:55
*** dviroel has joined #openstack-meeting10:56
*** ykatabam has quit IRC11:00
*** Lucas_Gray has quit IRC11:00
*** Lucas_Gray has joined #openstack-meeting11:06
*** rpittau is now known as rpittau|bbl11:18
*** tetsuro has quit IRC11:19
*** masahito has joined #openstack-meeting11:20
*** yunyoung has quit IRC11:39
*** yamamoto has joined #openstack-meeting11:42
*** yamamoto has quit IRC11:43
*** bbowen has quit IRC11:45
*** lpetrut has quit IRC11:50
*** Lucas_Gray has quit IRC11:50
*** masahito has quit IRC11:50
*** Lucas_Gray has joined #openstack-meeting12:01
*** Lucas_Gray has quit IRC12:06
*** raildo has joined #openstack-meeting12:06
*** Lucas_Gray has joined #openstack-meeting12:09
*** yamamoto has joined #openstack-meeting12:18
*** yamamoto has quit IRC12:19
*** rcernin has quit IRC12:29
*** enriquetaso has joined #openstack-meeting12:29
*** ociuhandu has quit IRC12:29
*** ociuhandu has joined #openstack-meeting12:30
*** ociuhandu has quit IRC12:35
*** hjensas has joined #openstack-meeting12:38
*** Lucas_Gray has quit IRC12:39
*** Lucas_Gray has joined #openstack-meeting12:40
*** bbowen has joined #openstack-meeting12:50
*** yamamoto has joined #openstack-meeting12:51
*** bbowen_ has joined #openstack-meeting12:53
*** munimeha1 has joined #openstack-meeting12:54
*** bbowen has quit IRC12:56
*** yamamoto has quit IRC12:57
*** rh-jelabarre has joined #openstack-meeting13:01
*** rpittau|bbl is now known as rpittau13:04
*** psachin has quit IRC13:06
*** munimeha1 has quit IRC13:07
*** munimeha1 has joined #openstack-meeting13:07
*** ociuhandu has joined #openstack-meeting13:10
*** jamesmcarthur has joined #openstack-meeting13:11
*** jamesmcarthur has quit IRC13:13
*** jamesmcarthur has joined #openstack-meeting13:13
*** eharney has joined #openstack-meeting13:17
*** Luzi has joined #openstack-meeting13:20
*** ociuhandu has quit IRC13:20
*** njohnston_ has joined #openstack-meeting13:32
*** jamesmcarthur has quit IRC13:35
*** psachin has joined #openstack-meeting13:38
*** jamesmcarthur has joined #openstack-meeting13:39
*** njohnston_ is now known as njohnston13:44
*** jamesmcarthur has quit IRC13:45
*** jamesmcarthur has joined #openstack-meeting13:47
*** ociuhandu has joined #openstack-meeting13:53
*** lajoskatona has joined #openstack-meeting13:59
*** ociuhandu has quit IRC14:00
slaweq#startmeeting networking14:00
openstackMeeting started Tue Jan 28 14:00:27 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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
slaweqhi14:00
openstackThe meeting name has been set to 'networking'14:00
rubasovo/14:00
njohnstono/14:00
ralonsohhi14:00
amotokio/14:00
bcafarelhi14:01
lajoskatonao/14:01
haleybhi14:01
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqfirst releases related things14:02
slaweqWe are getting close to Ussuri-2, it will be in the week of February 10: https://releases.openstack.org/ussuri/schedule.html14:02
*** rsimai_away is now known as rsimai14:02
slaweqso we should focus on reviewing patches related to BPs scheduled for Ussuri-2 (but we will get to BPs later)14:02
slaweqWe are also getting close to Rocky EM: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012207.html14:02
slaweqso if You have any backports to rocky which You would like to be released, please reach out to our stable core team14:04
slaweqand the last one (as a reminder)14:05
slaweqwe are still looking for maintainers for neutron-fwaas14:05
slaweqlast call mail was sent by me some time ago: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012099.html14:05
slaweqbut TBH I don't think we will have any volunteers to maintain it :/14:06
slaweqany other announcements from the team?14:07
slaweqok, I guess there is no other announcements from the team14:09
slaweq#topic Blueprints14:09
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:09
slaweqhere are all BPs for U-2: https://launchpad.net/neutron/+milestone/ussuri-214:09
slaweqwe may probably have problems with https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant as owner of it can't work on it anymore so we need new volunteer14:10
*** redrobot_ has joined #openstack-meeting14:10
slaweqI reached out to amorin from OVH to ask about it but he don't know if they will have anyone new to work on this soon, so probably we will need to postpone it for now14:11
slaweqdo You have any updates about other BPs?14:11
*** redrobot_ is now known as redrobot14:11
bcafarelmlavalle had an update he sent yesterday because he would not be able to attend, not sure if you saw it14:11
slaweqbcafarel: I think I missed it14:12
slaweqwas it on ML?14:12
bcafarel"made good progress with tagging during create port bulk. The patch is good to go: https://review.opendev.org/#/c/700755, which now depends on https://review.opendev.org/#/c/704240"14:12
patchbotpatch 700755 - neutron - Implement tagging during bulk port creation - 12 patch sets14:12
patchbotpatch 704240 - neutron - Pass result dict to extensions by create port bulk - 3 patch sets14:12
bcafareljust good ol' IRC :)14:13
slaweqok, thx bcafarel :)14:13
slaweqI saw he also set review priority for those patches14:13
slaweqI will today or tomorrow go through list with other patches related to BPs for U-2 and will set priority for them too14:14
slaweqso please check this review-prio list next days and review those patches :)14:14
slaweqok, so I guess there is no updates about other BPs for today14:16
slaweqlets move on then14:16
slaweq#topic Community goals14:17
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:17
slaweqI still didn't had time to work on this PTL docs yet14:17
slaweqnjohnston: any updates about dropping py2 support?14:17
njohnstonThe drop py27 goal appears to have been achieved, as far as I can tell14:17
njohnstonall changes have merged14:17
njohnstonwe may find a few little leftovers here and there over time14:18
njohnstonso projects are now fine to make their code incompatible with py27: removing six, etc.14:18
slaweq\o/ that's great news14:18
slaweqthx njohnston for all work on that14:18
ralonsohcool!14:18
ralonsohthanks njohnston14:18
bcafarelI saw gmann sent a patch for neutron-tempest-plugin, we may have a few bits left there14:19
njohnstonwe have great progress on the zuulv3 migration, which is going to be a goal for the V cycle14:19
* bcafarel looking for review14:19
slaweqI will mark this goal as done and will remove it from meeting's agenda14:19
*** yamamoto has joined #openstack-meeting14:20
bcafarelhttps://review.opendev.org/#/c/704257/14:20
patchbotpatch 704257 - neutron-tempest-plugin - [ussuri][goal] Drop python 2.7 support and testing - 1 patch set14:20
njohnstonbcafarel: Yes I think I remember that, the branchless tempest plugins are in a little bit of an odd situation, and gmann has been great helping shepherd the whole QA infrastructure so it handles that14:20
slaweqbut our problem is only for rocky, right?14:20
slaweqstein and newer already runs on py3 IIRC14:21
njohnstonright14:21
gmann#link https://review.opendev.org/#/c/704257/14:21
patchbotpatch 704257 - neutron-tempest-plugin - [ussuri][goal] Drop python 2.7 support and testing - 1 patch set14:21
gmanni need to check rocky issue if that is same.14:21
slaweqso it's problem only for few weeks14:21
slaweqas we agreed some time ago to run tagged version of plugin on EM branches14:21
slaweqand rocky will be EM in few weeks14:21
slaweqhi gmann :)14:22
gmannto fix py2 things on rocky. we merged the running tempest on py3 venv - https://review.opendev.org/#/q/topic:bug/1860033+status:merged14:22
gmannso it should be fine.14:22
njohnstonthe error for that change seems to be a requirements problem14:22
njohnstonCould not find a version that satisfies the requirement zipp===2.0.1 (from -c https://releases.openstack.org/constraints/upper/master (line 702)) (from versions: 0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.5.0, 0.5.1, 0.5.2, 0.6.0, 1.0.0, 1.1.0)14:22
amotokiAs of now it failed due to zipp in py2. zipp issue has been fixed I think14:23
*** Lucas_Gray has quit IRC14:23
*** Wryhder has joined #openstack-meeting14:23
amotokihttps://review.opendev.org/#/c/704263/ should fix it.14:23
patchbotpatch 704263 - requirements - Use zipp 1.1.0 for python 3.5 and lower (MERGED) - 1 patch set14:23
gmannyeah, it is fixed14:23
gmannrecheck should work now as tempest patch is merged recently - https://review.opendev.org/#/c/703011/14:24
patchbotpatch 703011 - tempest - Define python3 as basepython for Tempest tox env (MERGED) - 9 patch sets14:24
*** Wryhder is now known as Lucas_Gray14:24
*** pcaruana has quit IRC14:24
slaweqok, lets check this patch than14:25
slaweqthx gmann for help with that14:25
njohnstonthanks gmann!14:25
*** Luzi has quit IRC14:26
slaweqso lets move on to the next topic than14:26
slaweq#topic Bugs14:26
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:26
slaweqlajoskatona was on bug deputy14:27
lajoskatonaYes14:27
slaweqlajoskatona: any bugs You want to bring up for team's attention?14:27
lajoskatonaas I wrote in the summary I think it was a quiet week, mostly with CI related bugs14:27
lajoskatonaand some moving of old networking-ovn bugs to neutron launchpad folder14:28
*** jamesden_ has joined #openstack-meeting14:28
lajoskatonaAnd as I remember perhaps one is not covered with somebody14:28
*** jamesdenton has quit IRC14:29
lajoskatonahttps://bugs.launchpad.net/neutron/+bug/1860662 perhaps this one is without owner14:29
openstackLaunchpad bug 1860662 in neutron "[OVN] FIP on OVN Load balancer doesn't work if member has FIP assigned on DVR setup" [Medium,New]14:29
lajoskatonaso I think that's it for bugs14:29
lajoskatonaOhhh, perhaps 2 that can be good for drivers team,14:30
lajoskatonahttps://bugs.launchpad.net/neutron/+bug/186033814:30
openstackLaunchpad bug 1860338 in neutron "[OVS] OVS agent should not plug/unplug smartNIC ports" [Wishlist,New]14:30
ralonsohyes, about this one14:31
lajoskatonaThis one is related to recent smartnic support pathces14:31
slaweqI also wanted to ask about it14:31
ralonsohthis is a concern related to smart nics and OVS14:31
*** dmacpher has quit IRC14:31
ralonsohOVS agent should take care of >=L2 events14:31
ralonsohnot L114:31
ralonsohthat means: should not plug or unplug any interface14:32
ralonsohbut I have a meeting this week with other RH and Mellanox guys14:32
ralonsohabout this14:32
ralonsohso I'll add my comments in the bug14:32
slaweqralonsoh: but my first question here is: should we treat it as RFE or bug?14:32
ralonsohslaweq, I prefer to hear from Mellanox about smart nics and future developments14:33
ralonsohand the we (Neutron community) can decide about this14:33
ralonsohthen*14:33
slaweqralonsoh: ok, please update LP with any additional info which You will have14:33
ralonsohsure14:33
slaweqthx ralonsoh14:34
lajoskatonaThe other one is this one: https://bugs.launchpad.net/neutron/+bug/186052114:34
openstackLaunchpad bug 1860521 in neutron "L2 pop notifications are not reliable" [Undecided,New]14:34
lajoskatonathat is already marked as RFE14:34
lajoskatonaThat's really all of last week14:35
lajoskatonaregarding bugs14:35
slaweqyes, I will take care of it to triage it14:35
slaweqthx a lot lajoskatona14:35
lajoskatona:-)14:36
slaweqour bug deputy this week is tidwellr and he confirmed me by email that he will take care of it14:37
slaweqand next week bug deputy will be Swami, I will ping him via email too14:38
slaweqok, I think we can move on14:38
slaweqor do You have any bugs which You want to talk about now?14:39
slaweqok, so I think we can move on14:40
slaweq#topic Networking OVN and ML2+OVS+DVR Convergence14:40
*** openstack changes topic to "Networking OVN and ML2+OVS+DVR Convergence (Meeting topic: networking)"14:40
slaweqI think lucasgomes isn't here now14:41
ralonsohone sec14:41
slaweqralonsoh: maybe You have any updates about it?14:41
ralonsohnot all the info14:42
*** lucasagomes has joined #openstack-meeting14:42
*** maciejjozefczyk has joined #openstack-meeting14:42
ralonsohwe have some problems with the FT tests14:42
ralonsohthere we go ^^14:42
* haleyb looks for the review topic14:42
ralonsohlucasagomes, hi, can you update the OVN migration status?14:42
lucasagomesralonsoh: hi there, yes14:42
haleybhttps://review.opendev.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/neutron-ovn-merge14:43
lucasagomesso I think we are similar to last week, we have the ovn driver almost enterily merged but it's missing functional tests14:43
lucasagomesthat said, we needed a new version of ovsdbapp in order to have the FT to start to run14:43
lucasagomesthat's done14:43
lucasagomesso now they r being executed and we need to take a look in a few tests that are failing14:43
lucasagomeshopefully all will be sorted by this week14:44
lucasagomesI also started migrating the bugs from the networking-ovn bug tracker to the neutron bug tracker14:44
lucasagomesso don't freak out if u see a bunch of new bugs popping up for OVN there14:44
lucasagomesI guess that's mostly it14:44
lucasagomesnot sure if mentioned last week... but, we now have an tempest OVN test running (voting) in the gate14:45
slaweqthx lucasagomes14:45
slaweqdo You need to propose new ovsdbapp release? or are You still waiting for some patch to be merged there?14:45
haleybone related item, i've been working on getting an ipv6-only job working for OVN, think it's happy now14:45
* haleyb waits14:45
lucasagomesslaweq: it's been released already14:45
lucasagomesand requirements have been bumped14:45
slaweqlucasagomes: ok, great then14:45
slaweqhaleyb: sorry, go on :)14:46
haleybhttps://review.opendev.org/#/c/703685/ and https://review.opendev.org/#/c/700939/ just need a few reviews14:46
patchbotpatch 703685 - neutron - Fix OVN agent devstack script to support IPv6 - 3 patch sets14:46
patchbotpatch 700939 - neutron - Define new ipv6-only job for OVN - 10 patch sets14:46
lucasagomeshaleyb: awesome! Will take a look today at it14:46
haleybi like the patchbot14:46
*** Lucas_Gray has quit IRC14:47
haleyblucasagomes: thanks!14:47
lucasagomesah btw, to help with reviews I created a small OVN driver dashboard that filters out the reviewsing in neutron14:47
lucasagomesif u interested: https://bit.ly/2voTVXf14:47
* lucasagomes is off-topic 14:47
maciejjozefczykthanks lucasagomes14:47
slaweqthx lucasagomes for the link14:47
slaweqlooks nice14:47
slaweqand thx for update lucasagomes and haleyb14:48
lucasagomesyw14:48
slaweqok, lets move on14:49
slaweq#topic On Demand Agenda14:49
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:49
slaweqwe have one topic there:14:49
slaweq"Do we need to change job definitions on stable branches as well?"14:49
*** Lucas_Gray has joined #openstack-meeting14:49
slaweqI'm not sure who added it, njohnston is it Yours?14:49
lajoskatonaIt was me14:49
slaweqahh, ok14:50
slaweqso go on lajoskatona :)14:50
lajoskatonaThe question came from bagpipe or bgpvpn job changes to zuukv314:50
lajoskatonaand the problem is that now some job definitions are in some common repo (job-configs or similar) and infra tend to ave the new jobs in porject repos14:51
lajoskatonawhich I understand, but if we have one zuulv3 job definition in project repo, and old one somewhere else that can cause problems for maintenance14:51
lajoskatonaand cause confusion, etc...14:52
slaweqIn neutron repo we keept jobs for stable branches to be legacy ones14:52
lajoskatonaSo my question is do we need to change old branches job definitions to zuulv3 (where possible) or let it as  it is and care for multiple job definitions for the same job14:52
slaweqso we didn't backport those patches which proposes zuulv3 jobs to stable branches14:52
*** Lucas_Gray has quit IRC14:53
slaweqbut we changed names of jobs14:53
slaweqas old jobs has got "legacy" in name14:53
lajoskatonaok, then that is clear, let the legacy jobs as they are14:53
slaweqso we proposed new (zuulv3) jobs without this word "legacy"14:53
lajoskatonathanks14:53
slaweqbut I'm open to any other ideas how to do this14:54
lajoskatonaOk, I check my patches,14:54
amotokiIMHO we can backport zuulv3 changes. It would reduce the maintenance cost especially in small projects.14:54
lajoskatonaslaweq: no, I am ok with it, In my mind I can argue fro both solutions, so I wanted to hear other opinions as well14:54
lajoskatonaI think the most important is to have a common agreement otherwise it will be more difficult :-)14:55
*** Lucas_Gray has joined #openstack-meeting14:56
bcafarelhmm true we made sure that all new jobs get new names (even if close sometimes)14:56
slaweqfrom my personal experience I can say that migrating to zuulv3 may not be as straight forward in some cases and doing it also for stable branches may be even harder, especially now with this all "dropping py2 support nightmare" :)14:56
slaweqand maintenance of those jobs in stable branches is pretty minimal usually14:57
lajoskatonasalweq: yeah that is also one thing to consider, that it is time consuming to do the conversion14:57
bcafarelmy main fear is that things go south when trying to backport new job definition - needed code changes somehow, not working on older branches, etc - but that should not blocking from attempting it :)14:57
*** shintaro has joined #openstack-meeting14:58
*** Wryhder has joined #openstack-meeting14:58
slaweqI would say: keep legacy jobs for stable branches, at least if it works fine, when such job will require some fixes, we can think about moving it to zuulv3 for stable branches then14:59
lajoskatonaI think it is better to have similar approach at least on networking projects, so all to change to v3 or let legacy to be legacy14:59
slaweqok, we are almost out of time now14:59
lajoskatonaOk, for me it is ok, and I suppose acceptable for infra as well14:59
slaweqthx for attending the meeting14:59
slaweq#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Jan 28 15:00:04 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-01-28-14.00.html15:00
njohnstono/15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-01-28-14.00.txt15:00
lajoskatonabye15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-01-28-14.00.log.html15:00
slaweqhave a great week guys :)15:00
slaweqo/15:00
amotokio/15:00
ralonsohbye and hello15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Jan 28 15:00:20 2020 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
slaweqhi ralonsoh :)15:00
ralonsohhello!15:00
ralonsohdon't worry, the agenda is almost empty today15:00
ralonsohDavid is not going to attend, I'll update the RFE status15:01
*** Lucas_Gray has quit IRC15:01
*** Wryhder has quit IRC15:01
*** Liang__ has quit IRC15:01
ralonsohlet's start then15:01
ralonsoh#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:01
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:01
ralonsohthe spec is merged15:01
slaweqand there is also one small follow up for this spec, right?15:02
ralonsohbut there is a patch to amend it15:02
ralonsohhttps://review.opendev.org/#/c/703431/15:02
patchbotpatch 703431 - neutron-specs - Missing caveat in NC DSCP spec - 2 patch sets15:02
slaweqright :)15:02
ralonsohexactly15:02
ralonsohIMO, it's ok now15:02
ralonsohI'll +2 it15:02
slaweqthx15:02
ralonsohDavid is going to push the last patch for the n-lib patch15:02
lajoskatonao/15:03
ralonsoh#link https://review.opendev.org/#/c/670049/15:03
patchbotpatch 670049 - neutron-lib - Neutron-Classifier service plugin - 9 patch sets15:03
ralonsohlajoskatona, hi!15:03
ralonsohthere are some errors in the CI but nothing serious15:03
lajoskatonaJust for info: I started to write some tempest API tests for it15:03
ralonsohIMO, the n-lib is almost ready15:03
ralonsohlajoskatona, the classifier?15:03
lajoskatonaralonsoh: yes15:03
ralonsohlajoskatona, that's fantastic! please, add this info to the LP15:04
ralonsohor use the bug number15:04
lajoskatonaas I see there's no tempest for it in the original repo, and I thought that can be useful15:04
lajoskatonaralonsoh: will do15:04
ralonsohfor sure that will be very helpful15:04
slaweqlajoskatona++ thx a lot :)15:04
ralonsohand I have no more updates for this RFE15:05
lajoskatonayour welcome15:05
ralonsohlet's see if, in 2 weeks, we have the neutron patch ready15:05
slaweqralonsoh: I hope so :)15:06
ralonsohok, next one15:06
*** Lucas_Gray has joined #openstack-meeting15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/185136215:06
openstackLaunchpad bug 1851362 in neutron "[RFE] ports do not inherit their associated network's policy" [Low,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:06
ralonsohlast patch is in the gate15:06
ralonsoh#link https://review.opendev.org/#/c/693244/15:06
patchbotpatch 693244 - neutron - Add "qos_network_policy_id" to port definition - 4 patch sets15:06
ralonsoh7 rechecks15:06
*** jamesmcarthur has quit IRC15:07
ralonsohbut this is the last one15:07
ralonsohI'll remove this RFE from the list next meeting15:07
ralonsohthanks for the reviews!15:07
ralonsohbtw, I have some requests to backport this feature15:07
*** jamesden_ is now known as jamesdenton15:07
*** psachin has quit IRC15:07
ralonsohthis is not possible: there is an API change15:07
ralonsohand because this is not a bug, only a RFE, this is not going to be possible15:07
slaweqyes15:08
ralonsohok, next one15:08
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184316515:08
openstackLaunchpad bug 1843165 in neutron "RFE: Adding support for direct ports with qos in ovs" [Wishlist,Fix released] - Assigned to waleed mousa (waleedm)15:08
ralonsoh#link https://review.opendev.org/#/c/611605/15:09
patchbotpatch 611605 - neutron - Add support for direct ports with QoS in OVS (MERGED) - 22 patch sets15:09
ralonsohmerged last week15:09
ralonsohthanks to the smart nics QoS support15:09
ralonsohthe patch "only" enables to use those ports with the QoS extension15:09
ralonsohof course, we have sanity checks for this15:09
ralonsohI'll remove this RFE from the list next week15:09
ralonsohand that's all I have in the RFE section15:10
ralonsohsomething else?15:10
slaweqnope15:10
ralonsohlet's move on15:10
ralonsoh#topic Bugs15:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:10
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184517615:10
openstackLaunchpad bug 1845176 in neutron "Removing of QoS queue in neutron-ovs-agent fails due to existing references" [Medium,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:10
ralonsoh#link https://review.opendev.org/#/c/687922/15:11
patchbotpatch 687922 - neutron - Add OVS QoS driver cache for minimum bandwidth rules (MERGED) - 15 patch sets15:11
ralonsohthe patch was merged last week15:11
ralonsohthis patch, I think so, will reduce the number of errors in the CI15:11
*** pcaruana has joined #openstack-meeting15:11
ralonsohrelated to fullstack QoS tests15:11
slaweqfingers crossed :)15:11
ralonsoh(I don't remember now the LP bug for this)15:11
ralonsohlet's find it during the next meeting15:12
ralonsohI'll remove this bug from the list for the next meeting15:12
ralonsohnext one15:12
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/185317115:12
openstackLaunchpad bug 1853171 in neutron "Deprecate and remove any "ofctl" code in Neutron and related projects " [Medium,In progress] - Assigned to David Shaughnessy (david-shaughnessy)15:12
ralonsohas commented, this is going to be a long life bug15:13
ralonsohand maybe we won't be able to remove ofctl from Neutron15:13
ralonsohthere are some parts, like the firewall, using it15:13
lajoskatonaralonsoh: I started to work on bagpipe, but I have slow progress regarding this ofctl one15:13
ralonsohlajoskatona, yes, and bagpipe15:14
slaweqso it's "cross project" effort, right?15:14
ralonsohit is15:14
lajoskatonayeah, as I remember 3-4 project use neutron ofctl methods15:14
ralonsohbut also there are some sections in the firewall I don't know how to implement using native implementation15:14
ralonsohso it's a bit more complicated as I expected15:14
ralonsohthe main think is: no new development should use it15:15
*** jamesden_ has joined #openstack-meeting15:15
ralonsohthing*15:15
slaweqmaybe we can ask otherwiseguy for help with those hard parts?15:15
ralonsohyes, he can help us a lot15:15
ralonsohbut when I talked to David, he told me that this is a low priority bug15:16
ralonsohand he will start implementing the migration once the classifier is merged15:16
ralonsohor the main part15:16
ralonsohmakes sense15:16
ralonsohI would reduce the "importace" to low15:17
slaweqyes, it's definitely not urgent thing15:17
ralonsohand last bug is15:18
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/182409515:18
openstackLaunchpad bug 1824095 in neutron "Fullstack job broken in stable/stein branch" [High,Fix committed] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:18
ralonsohThe patch was merged15:18
ralonsohone sec...15:18
ralonsoh#link https://review.opendev.org/#/c/651458/15:18
patchbotpatch 651458 - neutron (stable/stein) - Specify physical network in QoS fullstack tests (MERGED) - 2 patch sets15:18
*** jamesdenton has quit IRC15:18
*** ociuhandu has joined #openstack-meeting15:18
ralonsoha simple cherry-pick from a previous one15:18
ralonsohI'll remove it from the list15:19
ralonsohand that's all I have15:19
ralonsoh#topic Open Discussion15:19
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:19
ralonsohdo you have something to discuss?15:19
slaweqI'm good15:21
ralonsohperfect then, thank you very much for attending today. Next meeting in 40 mins in this channel (Neutron CI)15:21
ralonsoh#endmeeting15:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:21
openstackMeeting ended Tue Jan 28 15:21:51 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-01-28-15.00.html15:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-01-28-15.00.txt15:21
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-01-28-15.00.log.html15:21
slaweqo/15:21
slaweqralonsoh: no, CI meeting is moved to Wednesday15:22
lajoskatonao/15:22
slaweqwe talked about it last time, do You remember?15:22
*** jamesden_ is now known as jamesdenton15:23
*** Lucas_Gray has quit IRC15:24
*** Wryhder has joined #openstack-meeting15:24
*** ociuhandu has quit IRC15:24
ralonsohslaweq, ahhhhh yes! thanks!15:24
*** Wryhder is now known as Lucas_Gray15:25
*** ociuhandu has joined #openstack-meeting15:25
slaweq:)15:25
*** Lucas_Gray has quit IRC15:27
*** Lucas_Gray has joined #openstack-meeting15:29
*** ociuhandu has quit IRC15:37
*** jamesmcarthur has joined #openstack-meeting15:37
*** diablo_rojo has quit IRC15:47
*** Lucas_Gray has quit IRC15:48
*** e0ne has joined #openstack-meeting15:50
*** jamesmcarthur has quit IRC15:52
*** shintaro has quit IRC15:54
*** ayoung has quit IRC15:55
*** jamesmcarthur has joined #openstack-meeting15:57
*** armax has joined #openstack-meeting16:05
*** ociuhandu has joined #openstack-meeting16:08
*** ociuhandu has quit IRC16:12
*** psachin has joined #openstack-meeting16:12
*** maciejjozefczyk has quit IRC16:20
*** gyee has joined #openstack-meeting16:20
*** raildo has quit IRC16:25
*** raildo has joined #openstack-meeting16:25
*** raildo has quit IRC16:28
*** raildo has joined #openstack-meeting16:28
*** lajoskatona has quit IRC16:37
*** rfolco is now known as rfolco|bbl16:46
*** rsimai is now known as rsimai_away17:00
*** tesseract has quit IRC17:01
*** dmacpher has joined #openstack-meeting17:12
*** lucasagomes has quit IRC17:15
*** psachin has quit IRC17:15
*** artom has quit IRC17:22
*** artom has joined #openstack-meeting17:22
*** artom has quit IRC17:27
*** artom has joined #openstack-meeting17:29
*** lajoskatona has joined #openstack-meeting17:37
*** vishakha has quit IRC17:37
*** ociuhandu has joined #openstack-meeting17:42
*** igordc has joined #openstack-meeting17:46
*** ociuhandu_ has joined #openstack-meeting17:46
*** ociuhandu has quit IRC17:47
*** ociuhandu_ has quit IRC17:51
*** maciejjozefczyk has joined #openstack-meeting17:55
*** dustinc has quit IRC17:58
*** dustinc has joined #openstack-meeting17:58
*** electrofelix has quit IRC17:59
*** priteau has quit IRC18:01
*** diablo_rojo has joined #openstack-meeting18:02
*** armax has quit IRC18:10
*** e0ne has quit IRC18:10
*** Shrews has joined #openstack-meeting18:13
*** walshh_ has quit IRC18:29
*** anastzhyr has joined #openstack-meeting18:29
*** walshh_ has joined #openstack-meeting18:30
*** rpittau is now known as rpittau|afk18:40
*** armax has joined #openstack-meeting18:42
*** yamamoto has quit IRC18:48
*** yamamoto has joined #openstack-meeting18:51
clarkbanyone else here for the infra meeting?18:59
Shrewso/18:59
clarkbWe will get started shortl19:00
clarkb*shortly19:00
ianwo/19:00
corvuso/19:01
clarkb#startmeeting infra19:01
*** patchbot has left #openstack-meeting19:01
openstackMeeting started Tue Jan 28 19:01:12 2020 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/2020-January/006583.html Our Agenda19:01
zbro/19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI did not have any announcements to announce19:01
corvusclarkb: nice announcement19:02
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkbcorvus: it was agood one19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-01-21-19.01.txt minutes from last meeting19:02
clarkbThere were no actions recorded in the last meeting19:02
clarkb#topic Priority Efforts19:03
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:03
clarkbLet's dive right in then19:03
clarkb#topic OpenDev19:03
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:03
*** lajoskatona has quit IRC19:03
clarkblink https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack Governance19:03
clarkb#link https://review.opendev.org/#/c/703134/ Split OpenDev out of OpenStack Governance19:03
clarkb#link https://review.opendev.org/#/c/703488/ Update OpenDev docs with new Governance19:03
clarkbI think these two changes are just about ready to go in. At least I haven't seen much new feedback recently on the first one19:04
clarkbI'll bring it up with the TC to see what the next steps are from their side to keep it moving19:04
clarkbbut if you've got any input now would be a great time to record it19:04
*** yamamoto has quit IRC19:05
clarkbAre there any questions about this move to bring up here?19:05
*** yamamoto has joined #openstack-meeting19:06
*** yamamoto has quit IRC19:06
*** yamamoto has joined #openstack-meeting19:07
clarkbThe other opendev item I wanted to bring up was that we had been experiencing a ddos from huawei cloud against our gitea servers19:07
corvus(likely unintentional)19:07
clarkbcorrect19:07
clarkbI ended up emailing our OSF board member from huawei and they said they were customer IPs so couldn't put us directly in touch but did bring it up with the customer19:08
clarkbsince then I've not noticed similar behavior19:08
clarkbIf we continue to see similar OOMing behavior though we should likely strongly consider gitea hosts with more memory.19:08
clarkbfungi mentioned rate limiting requests, but I think that may make it worse because the git processes would stay around longer as the requests would take more time. And it is the git processes loading a bunch of info into memory that causes the problems19:09
clarkb(another option may be more gitea hosts as that will distribute load from lb better)19:09
clarkbsomething to monitor but for now it is no longer an emergency19:09
corvusin the long run, if we can get to a single distributed instance, we should be able to handle that better with load balancing19:09
clarkb++19:10
corvusbut yeah, until that happens, it seems like either more ram or more hosts are the best short term options19:10
fungiyes, if the gitea servers all shared a coherent backend filesystem view that would be much easier to absorb and scale19:10
corvus(more hosts should work in this case since we're talking about multiple source ips)19:11
fungiright now we can't even guarantee that two gitea servers have the exact same commits at any given point in time, due to gerrit scheduling replication to them independently19:11
ianware they "legitimate" requests, or more looking like scripts gone wild?19:11
clarkbianw: it looked like periodic CI jobs that cloned everythign from scratch each day19:12
fungiianw: best guess is a ci system which doesn't cache repositories locally and clones them all for every build19:12
clarkbfrom hundreds of hosts19:12
fungitiming also could be related to the recent cinder announcement about drivers without third-party ci getting marked as unsupported19:13
clarkbthat is possible19:13
ianweven if we could infinitely scale, perhaps rate limiting that sort of thing is best for everyone anyway19:13
fungihuawei representatives did say it wasn't a huawei system though, just some customer in their public cloud19:13
fungithe challenge is how to rate-limit it so that it doesn't make the matter worse, as clarkb points out19:14
clarkbif we wanted to go the rate limit route we'd have to limit requests before git gets forked19:14
clarkbit is doable but a naive approach would likely not work well19:14
*** yamamoto has quit IRC19:14
fungii suspect the only sane limits would have to be implemented within gitea itself19:15
*** e0ne has joined #openstack-meeting19:15
fungifor example, to allow the host to stop serving new requests once system resource utilization reaches some defined thresholds19:15
fungiso that the load balancer starts sending subsequent requests to other hosts in the pool19:16
fungicould also implement that with a health check agent reporting host info in haproxy, but that's complex to set up19:16
*** e0ne has quit IRC19:17
*** rfolco|bbl has quit IRC19:19
ianwcan haproxy "count" how many connections have been made, and cut you off?  or are the ips spread out enough that it would get under that but still cause problems?19:19
clarkbI think the ips were spread out enough in this case19:20
fungiyou could do that with iptables/conntrack actually19:20
*** maciejjozefczyk has quit IRC19:20
clarkbwhich is why a consumption monitoring system might be necessary19:20
clarkbcloning nova requirse just over a gig of memory19:20
clarkbhave enough of those (and not very many) and you run out of memory19:20
*** jamesmcarthur has quit IRC19:21
fungiyeah, it's less about the request volume and more about the impact of specific requests19:21
fungiand somewhat, though not directly correlated to, the data transferred19:22
clarkbhaving a proper gitea cluster should largely mitigate this as long as our k8s cluster has enough headroom19:23
clarkbas new giteas can be spun up to meet increases in demand19:23
clarkbits possible we may just want to focus on making ^ a reality19:23
corvusi haven't checked in on the status of elasticsearch support recently19:24
corvusprogress is being made https://github.com/go-gitea/gitea/pull/942819:25
corvusbut we still need code search for that19:26
clarkbexciting, maybe we keep that as the focus as it solves other problems too. And keep the other option in mind if the ddos problems comes back or gets worse19:26
clarkbAnything else on this topic or should we move on?19:27
ianwis this they type of thing we could have a story to track19:27
ianwi sort of worry that there's a lot of investigation not consolidated on it anywhere19:28
clarkbianw: ++ (too easy to forget when things are broken)19:28
clarkb#action clarkb write up story on gitea OOMs and DDoS19:28
clarkbI'll fix that19:28
ianwthanks, that will be great as we track it over time19:29
clarkb#topic Update Config Management19:30
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:30
clarkbI don't think mordred has made much progress on the dockerification of gerrit19:30
clarkbhe has been busy with travel and such19:30
clarkbDoes anyone else have config management updates to bring up?19:30
ianwi really want to get back to nodepool builder from containers very soon19:31
clarkbianw: is that running on the nodepool side's testing yet?19:32
ianwummm ... not sure19:34
clarkbno worries, was just curious19:34
clarkb#topic General Topics19:34
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:34
clarkbI/we have been semi formally pushign on getting rid of Trusty once and for all the last few days19:35
ianw(re: nodepool yes we have container tests merged)19:35
clarkbI've been working on a static.openstack.org replacement which needs a new gerritlib release which I'll push after the meeting19:36
fungistatus not static, right?19:36
clarkbonce that is in I half expect it to be functional, I'll confirm that then update dns19:36
clarkber yes status.19:36
clarkbAs part of this I realized we have a lack of testing around jeepyb and gerritlib so I've been working on a new job this morning to do an integration test with a running gerrit19:36
clarkbthis should give us a lot more confidence in jeepyb and gerritlib changes which are likely to become important as we tool up some of the opendev self serve stuff. If nothing else we can reuse the test platform and build different tools19:37
clarkbI'm close to having that stack ready for review and will bring it up after the meeting once I have the ready for review commits pushed19:37
clarkbianw: any progress on static? I think the change to add the host landed yesterday19:37
ianwif i could get some eyes on19:38
ianw#link https://review.opendev.org/70452319:38
ianwhit a small snag deploying openafs19:38
ianwbut, after that, we should be able to test out governance and security sites with local host updates19:39
ianwif we're happy, we can switch dns at some point after that19:39
ianwwith that POC the other bits should proceed quickly as we get them published to afs19:39
clarkbsounds good, I'll review that after the meeting19:40
clarkbwiki was the other big host in this list, fungi have you had a chance to psuh on it yet?19:40
fungiunfortunately no. trying to get freed up to do that today19:41
clarkbok let us know if we can help19:41
zbrcan i add something about our static websites?19:41
fungihave to run some errands after the meeting and will then figure out where i last left off19:41
clarkbzbr: sure19:41
zbrwe should enable google site tools in order to know who is linking to us and be able to reindex quickly when we update stuff19:41
zbror find links that are broken19:42
ianwthat's usually dropping a randomly named html file in the root, right?19:42
zbrenabling it requires only some kind of site verification, no JS mess is needed.19:42
zbrexactly19:42
corvusi don't think that's something that the infra/opendev team needs to do19:43
zbrwhen zuul docs got broken I raised https://review.opendev.org/#/c/702888/ fro enabling it.19:43
corvusthat should be up to the individual projects19:43
clarkbindividual projects should be able to verify themselves if its based on content in the site19:43
fungii'd be very uncomfortable forcing an tacit endorsement of some proprietary third-party service on all sites opendev hosts19:44
corvusmy read is that the zuul project is not thrilled about the idea19:44
fungian alternative is to do what we did for docs.openstack.org and provide 404 reporting scraped from teh apache error logs19:44
zbrso we provide a worsened experience to the users just for the spite of proprietary 3rd parties?19:45
clarkbzbr: I think the goal would be to address the problem without relying on a proprietary service. The preexisting 404 scanner tool is one such method (as fungi points out)19:45
zbrclearly the docs where broken for days before we fixed them19:45
clarkband if projects wish to opt into those proprietary tools they can do so without our input aiui19:45
fungifor the record, zuul's docs were not broken for days. external serch engines were serving stale cached links19:46
fungizuul's documentation provides its own index which is required to be consistent by the tool which builds it19:47
fungii'll grant that the integrated keyword searching for sphinx is not great compared to what external services provide, but that's independent of the documentation index itself19:47
clarkbzbr: but yes, one of the explicit goals here is to push viable project hosting via open source tooling19:47
fungiand to improve those open tools where necessary19:48
ianwis that hash in the file name based on the URL, or based on the user account requesting to add the site?19:48
zbrok, i just wanted to state that we should not ignore the UX19:48
corvusianw: that's for a user account19:48
corvushttps://review.opendev.org/702888 would give zbr administrative control of the zuul-ci.org domain in google webmaster tools19:49
ianwok, so it's not like you add one file and everyone/anyone could verify it19:49
zbrtrue, but someone has to do it, i does not have to be me.19:49
corvusin fact, no one has to do it19:50
*** ociuhandu has joined #openstack-meeting19:50
fungias evidenced by the fact that no one has so far19:50
*** e0ne has joined #openstack-meeting19:50
zbrso is better to do nothing just because we don't want to give someone the permission to do SEO19:50
corvusi feel like the conversation has looped back to 19:4519:51
Shrewsthe fact that folks find it better to use an external search engine to find the docs they need points to the fact that we should improve the layout of our current docs to make things easier to find. the reorg was (hopefully) the beginning of that effort19:51
clarkbI think this is a question for the zuul project not opendev, but I also don't think anyone is saying we have to give up. Simply thatZuul would like to use open source tools to address this problem19:51
clarkbwe only have about 8 minutes left and there are a couple more topics, I think we should move on19:51
corvusShrews, clarkb: ++19:52
clarkbI wanted to point out we have deployed a new (arm64) cloud to production in nodepool19:52
clarkbUnfortunately there is some weird network behavior between nb03 and the cloud apis so we have been unable to upload images19:52
ianwalso the mirror has disappeared unexpectedly, and the api hasn't helped determine why19:52
clarkbwe've reached out to kevinz on this but it is the chinese new year so expect it might be a little while before that gets fixed19:52
ianwtracking things in19:53
ianw#link https://storyboard.openstack.org/#!/story/200719519:53
clarkbthis new cloud will give us like 5 times the capacity for arm64 jobs19:53
clarkbit is very exciting19:53
ianwyep, and we'll for sure help sort out any stability issues, we always do :)19:54
clarkbAnd finally I set up a followup call with the airship team to talk about any new questions about adding the ericsson cloud to opendev nodepool. That happens tomorrow at 1600UTC on jitsi meet.19:54
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-January/006578.html Airship CI Meeting details here19:54
*** ociuhandu has quit IRC19:54
clarkbI ended up using jitsi meet for something else recently and it worked really well so wanted to give it a go. It is shaping up to be an open source alternative to google hangouts and zoom etc19:55
clarkbya'll are welcome to join. The timing is probably bad for ianw, you should sleep in instead :)19:55
clarkbAnd with that we have ~3 minutes for anything else19:56
clarkb#topic Open Discussion19:56
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:56
fungizbr: i've been evaluating our various options for open tools to perform analysis of our web activity in socially-conscious ways, producing reports which avoid any use of pii so they can be provided publicly. so far each of the classic tools i've evaluated has had one problem or another, but this one came to my attention last week i'm curious to try:19:57
fungi#link https://www.goatcounter.com/19:57
zbrthanks, still think we are missing the point.19:58
fungii apparently am19:58
zbryou cannot force google to reindex your site with 3rd party tools, neither to convince them to tell you about incoming links, broken stuff and so on.19:59
zbrthis is not about analytics stuff19:59
clarkbzbr: right, but if we properly add redirects then we don't need to force reindexing20:00
fungiyou can however find out what links are "broken" by seeing what urls folks request which return errors and add corresponding redirects20:00
clarkbwe can instead rely on their periodic reindexing20:00
clarkband we are at time20:00
clarkbthank you everyone20:00
clarkb#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Jan 28 20:00:30 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-01-28-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-01-28-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-01-28-19.01.log.html20:00
fungithanks clarkb!20:00
zbrnot really because if you look at the logs you will know about broken link only when someone will visit you again, not before it happens.20:00
clarkbfeel free to shift discussion over to #openstack-infra though the web hosting discussion might be better in #zuul20:00
*** shilpasd has quit IRC20:02
*** rfolco has joined #openstack-meeting20:24
*** armax has quit IRC20:30
*** armax has joined #openstack-meeting20:32
*** diablo_rojo has quit IRC20:34
*** bbowen_ has quit IRC20:44
*** jamesmcarthur has joined #openstack-meeting20:51
*** ralonsoh has quit IRC20:57
*** Lucas_Gray has joined #openstack-meeting21:07
*** jamesmcarthur has quit IRC21:17
*** jamesmcarthur has joined #openstack-meeting21:18
*** slaweq has quit IRC21:23
*** ayoung has joined #openstack-meeting21:27
*** slaweq has joined #openstack-meeting21:28
*** slaweq has quit IRC21:33
*** bbowen_ has joined #openstack-meeting21:37
*** e0ne has quit IRC21:39
*** slaweq has joined #openstack-meeting21:43
*** slaweq has quit IRC21:47
*** yamamoto has joined #openstack-meeting21:50
*** yamamoto has quit IRC21:55
*** raildo has quit IRC21:58
*** rcernin has joined #openstack-meeting22:00
*** jamesmcarthur has quit IRC22:01
*** jamesmcarthur has joined #openstack-meeting22:03
*** hyunsikyang has quit IRC22:10
*** hyunsikyang has joined #openstack-meeting22:11
*** diablo_rojo has joined #openstack-meeting22:27
*** jamesmcarthur has quit IRC22:34
*** jmasud has quit IRC22:34
*** jamesmcarthur has joined #openstack-meeting22:36
*** jamesmcarthur has quit IRC22:45
*** rfolco has quit IRC22:46
*** rh-jelabarre has quit IRC22:50
*** jamesmcarthur has joined #openstack-meeting22:50
*** jamesmcarthur has quit IRC23:03
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:16
*** dviroel has quit IRC23:23
*** panda has left #openstack-meeting23:36
*** anastzhyr has quit IRC23:49

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