Tuesday, 2020-03-24

*** gibi has joined #openstack-meeting00:19
*** jamesmcarthur has joined #openstack-meeting00:27
*** mattw4 has quit IRC00:28
*** jamesmcarthur has quit IRC00:33
*** hongbin has quit IRC00:37
*** hongbin has joined #openstack-meeting00:41
*** brinzhang_ has joined #openstack-meeting00:54
*** jmasud has quit IRC00:55
*** jmasud has joined #openstack-meeting00:56
*** brinzhang has quit IRC00:58
*** ysandeep|away is now known as ysandeep00:59
*** brinzhang_ has quit IRC01:00
*** brinzhang_ has joined #openstack-meeting01:00
*** macz_ has quit IRC01:01
*** brinzhang_ has quit IRC01:02
*** brinzhang_ has joined #openstack-meeting01:02
*** mattw4 has joined #openstack-meeting01:13
*** Liang__ has joined #openstack-meeting01:17
*** mattw4 has quit IRC01:18
*** masahito has joined #openstack-meeting01:52
*** masahito has quit IRC01:53
*** masahito has joined #openstack-meeting01:58
*** masahito has quit IRC02:00
*** gyee has quit IRC02:02
*** jmasud has quit IRC02:03
*** jamesmcarthur has joined #openstack-meeting02:03
*** jmasud has joined #openstack-meeting02:03
*** maohongbo has quit IRC02:04
*** maohongbo has joined #openstack-meeting02:04
*** masahito has joined #openstack-meeting02:07
*** maohongbo1 has joined #openstack-meeting02:22
*** maohongbo has quit IRC02:24
*** maohongbo1 is now known as maohongbo02:24
*** tetsuro_ has joined #openstack-meeting02:46
*** tetsuro has quit IRC02:49
*** rh-jelabarre has quit IRC02:49
*** jamesmcarthur has quit IRC03:02
*** jamesmcarthur has joined #openstack-meeting03:03
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur_ has joined #openstack-meeting03:06
*** mmethot has joined #openstack-meeting03:09
*** apetrich has quit IRC03:10
*** mmethot_ has quit IRC03:11
*** tetsuro has joined #openstack-meeting03:18
*** maohongbo1 has joined #openstack-meeting03:21
*** tetsuro_ has quit IRC03:22
*** maohongbo has quit IRC03:22
*** maohongbo1 is now known as maohongbo03:22
*** hongbin has quit IRC03:29
*** ricolin_ has joined #openstack-meeting03:32
*** brinzhang has joined #openstack-meeting03:33
*** ricolin_ has quit IRC03:34
*** tetsuro has quit IRC03:35
*** brinzhang_ has quit IRC03:36
*** brinzhang has quit IRC03:37
*** brinzhang has joined #openstack-meeting03:38
*** ricolin has joined #openstack-meeting03:40
*** jamesmcarthur_ has quit IRC03:47
*** jamesmcarthur has joined #openstack-meeting03:49
*** maohongbo1 has joined #openstack-meeting03:50
*** tpatil has joined #openstack-meeting03:51
*** maohongbo has quit IRC03:51
*** maohongbo1 is now known as maohongbo03:51
*** brinzhang_ has joined #openstack-meeting03:54
*** jamesmcarthur has quit IRC03:54
*** masahito has quit IRC03:56
*** brinzhang has quit IRC03:57
*** brinzhang has joined #openstack-meeting03:58
*** brinzhang_ has quit IRC03:59
tpatil#startmeeting Masakari04:00
openstackMeeting started Tue Mar 24 04:00:13 2020 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: Masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
tpatilRoll Call04:00
*** brinzhang_ has joined #openstack-meeting04:01
tpatil#topic: Roll Call04:01
*** openstack changes topic to ": Roll Call (Meeting topic: Masakari)"04:01
*** larainema has joined #openstack-meeting04:03
*** brinzhang has quit IRC04:03
*** brinzhang has joined #openstack-meeting04:04
tpatilNote to everyone: If you want your patches to get merge in U release, please add the list of patches in etherpad below:04:07
*** brinzhang_ has quit IRC04:07
tpatil#link : https://etherpad.openstack.org/p/masakari-u-workitems04:07
*** shilpasd has joined #openstack-meeting04:10
shilpasdGM Tushar san, sorry for delay04:10
tpatilshilpasd: Hi04:10
tpatilshilpasd: Do you have any patches for review?04:11
*** tetsuro has joined #openstack-meeting04:11
tpatilif yes, please add them in https://etherpad.openstack.org/p/masakari-u-workitems04:12
*** shilpasd47 has joined #openstack-meeting04:13
shilpasd47sorry some connection issue at my end04:13
shilpasd47okay will list into etherpad04:14
tpatilshilpasd47: No problem.04:14
*** shilpasd has quit IRC04:15
tpatilI will prioritize the patches that should be merged in U release and spend some time reviewing those accordingly04:15
shilpasd47tpatil: okay, thank you04:15
tpatilshilpasd47: Do you have any points for discussion? If no, let's end this meeting early as no one else has joined this time.04:16
shilpasd47just one query, https://review.opendev.org/#/c/704811/, here we are waiting for the approach to finalize04:16
shilpasd47patch is related to 'Add new filter `host_name` to segment list'04:16
*** suzhengwei__ has joined #openstack-meeting04:16
tpatilI have discussed this point in the last meeting and awaiting Sampath san to reply back.04:17
shilpasd47okay my miss, thank you04:17
tpatilthere are two choices04:17
tpatil1. Go ahead with the changes you have proposed04:17
tpatil2. introduce a new Rest API ``GET /hosts``04:18
suzhengwei__sorry for late.04:18
tpatilsuzhengwei__: Hi04:18
*** jamesmcarthur has joined #openstack-meeting04:18
shilpasd47suzhengwei__: Hi04:19
tpatil#topic: Critical Bugs04:19
*** openstack changes topic to ": Critical Bugs (Meeting topic: Masakari)"04:19
tpatil#link : https://bugs.launchpad.net/masakari/+bug/185876204:19
openstackLaunchpad bug 1858762 in masakari "“UNKNOWN” host_status notification may cause unsafe evacuation" [Critical,Confirmed] - Assigned to Shilpa Devharakar (shilpasd)04:19
tpatilshilpasd47: Do you have any update about this bug?04:20
shilpasd47will push changes today to community for this04:20
tpatilshilpasd47: Ok04:20
tpatilAny other bugs you want to discuss here?04:20
shilpasd47tpatil: no04:21
suzhengwei__tpatil: woud you like to give a review o this simple patch?04:22
tpatilsuzhengwei__: Sure,  I will review it04:22
tpatilIn the beginning of this meeting, I have added a note asking people to add patches that they want to see in U release.04:23
*** maohongbo has quit IRC04:23
tpatilsuzhengwei__: Could you please add the patches to want to see land in U release in below etherpad:04:23
*** maohongbo has joined #openstack-meeting04:23
tpatil#link : https://etherpad.openstack.org/p/masakari-u-workitems04:24
*** jamesmcarthur has quit IRC04:25
tpatilsuzhengwei__: The above patch looks simple but it's missing unit tests. Can you please add unit tests for your changes?04:25
suzhengwei__I will. My own CI workflow is broken, I need to fix it first.04:26
*** diablo_rojo has quit IRC04:27
tpatilsuzhengwei__: Ok, No problem04:27
tpatilMoving to the next topic04:27
tpatil#topic Work Items for Ussuri04:28
*** openstack changes topic to "Work Items for Ussuri (Meeting topic: Masakari)"04:28
tpatilsuzhengwei__: I forgot to mention about patch : https://review.opendev.org/#/c/708325/04:28
tpatilsuzhengwei__: Changes looks good. Need unit tests so that we can merge it patch soon04:29
suzhengwei__ok, i will add unit tests later.04:30
*** jamesdenton has quit IRC04:30
tpatilsuzhengwei__: Ok, Thanks04:31
tpatilEnable/Disable evacuation segment wise04:32
tpatilspecs: https://review.opendev.org/#/c/705893/04:32
shilpasd47tpatil: there are few review comments by Toshikazu Kazu Ichikawa, will address and push the updated path, further please review04:33
tpatilStill I need to review the updated specs, sorry the delay04:33
shilpasd47tpatil: i know your are super busy, so pl no sorry04:34
tpatilshilpasd47: This is different spec I'm talking about04:34
tpatilproposed by suzhengwei__04:34
shilpasd47tpatil: okay, we switched...04:34
shilpasd47sorry, i got confused04:35
tpatilsuzhengwei__: I will this specs soon04:36
suzhengwei__I have update code for this spec, but because my own ci workflow, it still failed.04:36
tpatilsuzhengwei__: Ok, Got it. I will see that this spec and implementation gets merged in U release.04:37
suzhengwei__function test is rely on openstackSDK, so function test will be add in next V branch.04:37
tpatilsuzhengwei__: Only rest API will go in this cycle and you plan to work on OpenStackSDK in next cycle, is it correct?04:38
suzhengwei__not enough time left for U release.04:39
tpatilsuzhengwei__: Ok04:40
tpatilNext work item: Evacuate non-recovery (`HA_enabled = False`) instances04:41
tpatilSpecs: https://review.opendev.org/#/c/702427/04:42
tpatilshilpasd47: Any update?04:42
shilpasd47tpatil: i want your review on this04:42
shilpasd47there are few comments, will address by today04:43
*** suzhengwei_ has joined #openstack-meeting04:43
*** masahito has joined #openstack-meeting04:43
tpatilshilpasd47: Ok, Thanks04:43
tpatilshilpasd47: I will review this specs as well. But are you ready with the implementation?04:44
shilpasd47tpatil: yes04:44
*** jamesmcarthur has joined #openstack-meeting04:44
*** suzhengwei has joined #openstack-meeting04:44
tpatilshilpasd47: Have you already uploaded the patch?04:45
shilpasd47tpatil: on CG, not yet, should i push?04:45
*** suzhengwei__ has quit IRC04:46
shilpasd47since pec is under review i haven't pushed to CG yet04:46
tpatilshilpasd47: Yes, you can push the implementation patch on the CG04:46
shilpasd47tpatil: okay will push today04:47
tpatilshilpasd47: Thanks04:47
tpatilModify masakari-hostmonitor in order to run it inside container04:47
tpatilshilpasd47: Any update?04:47
*** suzhengwei_ has quit IRC04:48
shilpasd47tpatil: here using 'crm' commands to check status for corosync/pacemaker04:48
shilpasd47but 'crm' itself uses systemctl internally to verify the same04:48
shilpasd47so my query, will crm commands will work inside docker?04:48
tpatilWhere did you find out this information?04:49
tpatilthat crm-> uses systemctl?04:49
shilpasd47tpatil: https://github.com/ClusterLabs/crmsh/blob/master/crmsh/utils.py#L179604:49
tpatilThat's important finding. If that's the case, there is no point of making this change. Let me discuss this issue with Sampath san and get back to you04:51
shilpasd47i have gone through this repository and observed that crm uses systemctl, correct me if i am wrong04:51
shilpasd47tpatil: thank you04:51
tpatilCommand parameter support to segment list command to filter out segments based on host input parameter04:52
tpatilshilpasd47: We have already discussed about this work item.04:52
shilpasd47tpatil: yes04:52
shilpasd47tpatil: since approach 2 is not yet finalized, should i focus on implementation for this option?04:53
*** jmasud has quit IRC04:53
tpatilshilpasd: Your call. I will discuss this point with Sampath san and get back to you.04:54
shilpasd47tpatil: okay04:54
shilpasd47tpatil: one more finding regarding 'Modify masakari-hostmonitor in order to run it inside container'04:54
shilpasd47here 'crm status list', this command i was looking for finding status of  corosync and pacemaker04:55
*** brinzhang has quit IRC04:55
shilpasd47but if we want status of 'pacemaker-remote', as of now 'crm' doesn't have support for this04:55
*** brinzhang has joined #openstack-meeting04:55
*** jmasud has joined #openstack-meeting04:56
shilpasd47if check here, 'crm status list' only list status for corosync and pacemaker services.04:56
tpatilshilpasd: I will need time to look into this.04:56
shilpasd47tpatil: yup, just findings i have shared here04:57
tpatilshilpasd47: Understood, thanks. If it's a blocker and cannot be done in U release, you can implement it in the next cycle04:58
tpatilrunning out of time.04:58
tpatilWe have finished discussion on work items planned for U release04:58
tpatilAny other points left for discussion?04:58
shilpasd47tpatil: ok, thanks04:59
tpatilLet's end this meeting here04:59
tpatilThank you, All04:59
shilpasd47thats all from my side, will add list of patches that needs to be review04:59
shilpasd47thank you04:59
tpatilshilpasd47: Thanks05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:00
openstackMeeting ended Tue Mar 24 05:00:09 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-03-24-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-03-24-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2020/masakari.2020-03-24-04.00.log.html05:00
*** jamesdenton has joined #openstack-meeting05:03
*** tpatil has quit IRC05:04
*** brinzhang_ has joined #openstack-meeting05:04
*** brinzhang_ has quit IRC05:05
*** brinzhang_ has joined #openstack-meeting05:06
*** jamesmcarthur has quit IRC05:06
*** brinzhang has quit IRC05:07
*** brinzhang has joined #openstack-meeting05:09
*** brinzhang_ has quit IRC05:12
*** brinzhang_ has joined #openstack-meeting05:12
*** brinzhang has quit IRC05:15
*** links has joined #openstack-meeting05:37
*** brinzhang_ has quit IRC05:54
*** ijw has joined #openstack-meeting06:07
*** ijw_ has quit IRC06:10
*** tetsuro_ has joined #openstack-meeting06:27
*** tetsuro has quit IRC06:31
*** vishalmanchanda has joined #openstack-meeting06:32
*** maohongbo has quit IRC06:34
*** dklyle has quit IRC06:34
*** diablo_rojo has joined #openstack-meeting07:02
*** maohongbo has joined #openstack-meeting07:04
*** jamesmcarthur has joined #openstack-meeting07:08
*** jamesmcarthur has quit IRC07:12
*** maohongbo has quit IRC07:14
*** ijw_ has joined #openstack-meeting07:20
*** ijw__ has joined #openstack-meeting07:20
*** ijw has quit IRC07:23
*** ijw_ has quit IRC07:24
*** shilpasd47 has quit IRC07:27
*** ircuser-1 has joined #openstack-meeting07:30
*** keiko-k has joined #openstack-meeting07:31
*** diablo_rojo has quit IRC07:35
*** jawad_axd has joined #openstack-meeting07:39
*** links has quit IRC07:47
*** links has joined #openstack-meeting07:54
*** belmoreira has joined #openstack-meeting07:56
*** e0ne has joined #openstack-meeting08:00
*** slaweq has joined #openstack-meeting08:05
*** apetrich has joined #openstack-meeting08:09
*** ralonsoh has joined #openstack-meeting08:13
*** yasufum has joined #openstack-meeting08:14
*** e0ne has quit IRC08:26
*** rpittau|afk is now known as rpittau08:26
*** Luzi has joined #openstack-meeting08:29
*** keiko-k has quit IRC08:45
*** jmasud has quit IRC08:55
*** jmasud has joined #openstack-meeting08:56
*** priteau has joined #openstack-meeting08:56
*** e0ne has joined #openstack-meeting09:01
*** brinzhang has joined #openstack-meeting09:04
*** yasufum has quit IRC09:05
*** brinzhang has quit IRC09:05
*** brinzhang_ has joined #openstack-meeting09:06
*** brinzhang_ has quit IRC09:07
*** brinzhang_ has joined #openstack-meeting09:07
*** brinzhang_ has quit IRC09:09
*** brinzhang_ has joined #openstack-meeting09:09
*** brinzhang_ has quit IRC09:10
*** suzhengwei has left #openstack-meeting09:11
*** brinzhang_ has joined #openstack-meeting09:11
*** brinzhang has joined #openstack-meeting09:31
*** Liang__ has quit IRC09:32
*** brinzhang_ has quit IRC09:33
*** ociuhandu has joined #openstack-meeting09:39
*** ociuhandu has quit IRC09:41
*** tetsuro_ has quit IRC09:43
*** priteau has quit IRC09:48
*** number80 has quit IRC09:51
*** number80 has joined #openstack-meeting10:04
*** masahito has quit IRC10:17
*** Lucas_Gray has joined #openstack-meeting10:24
*** andrebeltrami has joined #openstack-meeting11:04
*** Luzi has quit IRC11:35
*** psachin has joined #openstack-meeting11:43
*** rh-jelabarre has joined #openstack-meeting12:00
*** rfolco has joined #openstack-meeting12:02
*** rh-jelabarre has quit IRC12:04
*** rh-jelabarre has joined #openstack-meeting12:10
*** Luzi has joined #openstack-meeting12:13
*** raildo has joined #openstack-meeting12:18
*** ysandeep is now known as ysandeep|brb12:23
*** jmasud has quit IRC12:54
*** Wryhder has joined #openstack-meeting12:54
*** ociuhandu has joined #openstack-meeting12:55
*** Lucas_Gray has quit IRC12:55
*** Wryhder is now known as Lucas_Gray12:55
*** jmasud has joined #openstack-meeting12:56
*** jawad_axd has quit IRC13:02
*** jawad_axd has joined #openstack-meeting13:03
*** psachin has quit IRC13:05
*** ysandeep|brb is now known as ysandeep13:07
*** ociuhandu has quit IRC13:07
*** jawad_axd has quit IRC13:08
*** jawad_axd has joined #openstack-meeting13:24
*** lajoskatona has joined #openstack-meeting13:26
*** jawad_axd has quit IRC13:32
*** jawad_axd has joined #openstack-meeting13:33
*** dklyle has joined #openstack-meeting13:50
*** liuyulong has joined #openstack-meeting13:54
*** e0ne has quit IRC13:59
*** e0ne has joined #openstack-meeting13:59
slaweq#startmeeting networking14:00
openstackMeeting started Tue Mar 24 14:00:25 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
openstackThe meeting name has been set to 'networking'14:00
slaweqok, lets start14:02
slaweq#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
slaweqaccording to https://releases.openstack.org/ussuri/schedule.html next important dates are:14:02
slaweq    Final release for non-client libraries - week of March 30th,14:02
*** ociuhandu has joined #openstack-meeting14:02
slaweqUssuri-3 (feature freeze) - week of April 6th14:02
slaweqso final release of non-client libraries is next week14:02
*** shintaro has joined #openstack-meeting14:03
slaweqI think we should review what is missing and needed there still and get it merged this or early next week14:03
slaweqand then we will prepare releases next week with amotoki14:03
slaweqif You have any patches waiting in review queue which You want to include in this final release of any lib, please ping me and tell me what patch You need14:05
slaweqand then in 2 weeks we have Ussuri-3 and feature freeze14:06
slaweqso we should now focus also on reviewing patches related to RFEs which we want to deliver in Ussuri14:06
slaweqmost of them I think have set review-priority +114:07
slaweqany questions/comments about those dates?14:07
njohnstonlooks good to me14:08
slaweqok, so next one14:08
*** TrevorV has joined #openstack-meeting14:09
slaweqalso about dates, according to https://governance.openstack.org/election/ PTL nomination period starts on Mar 24th which is today14:09
slaweqso if someone wants to candidate - this is week of nominations :)14:09
slaweqnext announcement14:09
slaweqVictoria PTG in Vancouver is cancelled https://www.openstack.org/events/opendev-ptg-2020/14:10
slaweqIf You want to help to organize virtual PTG, please add Your name in https://etherpad.openstack.org/p/Virtual_PTG_Planning14:10
*** brinzhang has quit IRC14:10
slaweqwe will need to find some way to arganize virtual ptg14:10
*** brinzhang has joined #openstack-meeting14:11
slaweqso no team dinner this time :(14:11
njohnstonThis time I won't be the only one participating remotely :-)14:11
slaweqnjohnston: true :)14:11
njohnstonI think it will be different but it will have benefits14:12
bcafarelvirtual team dinner then?14:12
slaweqbcafarel: I'm not sure if that will work fine but we can try :)14:12
*** e0ne has quit IRC14:12
amotokisomeone can have beer from the morning :)14:12
*** e0ne has joined #openstack-meeting14:12
amotokisorry for late14:13
slaweqamotoki: and there will be excuse for that at least :D14:13
*** ociuhandu has quit IRC14:14
slaweqand also speaking about Victoria (Virtual) PTG, we have Victoria PTG planning etherpad: https://etherpad.openstack.org/p/neutron-victoria-ptg14:14
slaweqplease add Your ideas about topics there14:14
slaweqand thx to all who already added some proposals there14:14
njohnstonI rather like the way Ironic is doing their Unconference.  I like the PTG idea but if we go back to the old midcycle concept then we can space things out so people involved in multiple projects dont have to juggle schedules14:14
*** shintaro has quit IRC14:14
*** ociuhandu has joined #openstack-meeting14:14
slaweqnjohnston: but are You talking about virtual midcycle or "real" ones?14:15
njohnstonwell in these days it would be a virtual midcycle14:16
slaweqnjohnston: I guess there is already some discussion about that in TC, right?14:17
njohnstonslaweq: Yeah, let me wait for those ideas to get more fleshed out and I'll being the topic back at that point14:18
amotokiwe are remote so we can split the event into small sessions per topic and coordinate schedules even over multiple weeks. we don't necessarily need to have sessions in consecutive days.14:18
lajoskatonaI think the worst with a virtPTG is that for days we have to be active for the night14:19
njohnstonlajoskatona: It is rough for sure14:19
lajoskatonaso perhaps after identifiing the topics starting smaller meetings for the ones that are not fixed in mails or on irc can be better14:19
slaweqlajoskatona: that indeed sounds like good idea, at least for now14:20
slaweqlets see how it will evolve in next weeks14:20
slaweqI knot gibi already proposed something for nova so we can follow them with some ideas probably :)14:20
slaweqok, lets move on14:21
slaweq#topic Blueprints14:21
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:21
slaweqBlueprints for Ussuri-3: https://launchpad.net/neutron/+milestone/ussuri-314:21
slaweqany updates about them?14:21
*** jamesmcarthur has joined #openstack-meeting14:23
slaweqI wanted to ask about https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN14:23
slaweqlast time we said that last missing patches for this are  https://review.opendev.org/#/c/711317/ and https://review.opendev.org/#/c/702247/14:24
slaweqbut is https://review.opendev.org/#/c/711317/ needed to mark BP as done? this has reported separate bug14:25
slaweqand patch isn't linked with BP at all14:25
slaweqhaleyb: what do You think?14:25
ralonsohslaweq, this patch is still not finished14:26
haleybslaweq: i think getting https://review.opendev.org/#/c/702247/ would close it, and it was just updated, i'll review14:26
haleybthe rest are follow-ons and bug fixes i think14:26
slaweqhaleyb: thx, that's exactly my opinion also14:26
slaweqfor other BPs, I did some progress on https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch14:27
slaweqPatches waiting for review now: https://review.opendev.org/#/q/status:open+topic:bp/enginefacade-switch14:27
*** ysandeep is now known as ysandeep|afk14:28
slaweqand about https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6 - please all, review spec for this https://review.opendev.org/#/c/315604/14:28
ralonsohslaweq, bence found a possible architecture error in the spec14:29
ralonsohwhile doing a POC14:29
rubasovjust commented before this meeting14:29
slaweqrubasov: ralonsoh: yes, I just saw it14:29
slaweqI will read after this meeting14:30
rubasovplease check if you also think it is because the kernel behaves differently14:30
*** jawad_axd has quit IRC14:31
slaweqand that's all update about BPs from me today14:31
slaweqif there is nothing else, lets move on14:32
slaweq#topic Community goals14:32
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:32
slaweqhere currently we have only not finished IPv6-only testing goal14:32
slaweqbut I didn't had time to work on it this last week14:33
haleybwas the unittest.mock change a community goal?14:33
njohnstonhaleyb: no14:33
ralonsohthat was a recommendation14:33
slaweqhaleyb: not yet for sure14:33
slaweqmaybe for V cycle14:33
njohnstonAFAIK noone has proposed it for V cycle14:33
haleybok, i'll mention it in open agenda then14:33
slaweqnjohnston: any updates about migration to Zuul v3 which is Victoria goal?14:34
njohnstonThe only change in the field I know about is https://review.opendev.org/#/c/703949/ for networking-bagpipe14:35
njohnstonlajoskatona: Have you gotten a start on converting networking-odl to zuulv3?14:35
lajoskatonayes, but I have to restart as that was month ago14:35
njohnstonlajoskatona: thinking specifically about https://opendev.org/openstack/networking-odl/src/branch/master/.zuul.d/jobs.yaml#L240 to EOF14:35
*** jlibosva has joined #openstack-meeting14:35
lajoskatonayes I have an old patch for that somewhere14:36
njohnstonlajoskatona: OK, hopefully those jobs wont be too bad, they look pretty straightforward14:36
lajoskatonaI refresh it and ask around in odl community14:36
slaweqlajoskatona: and do You need help with https://review.opendev.org/#/c/703949/ ?14:36
njohnstonand I don't know if we have anyone who can comment on midonet14:36
njohnstonwith odl and midonet and that one bagpipe change I think we're complete14:37
lajoskatonaI think now that horizon is stabilized with pyScss2 those can be pushed forwards14:37
slaweqif You would need help with it lajoskatona, You can ping me14:38
slaweqnext topic14:38
slaweq#topic Bugs14:38
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:38
lajoskatonaslaweq: thanks, I check the fresh resulst and come back14:38
slaweqI was on bug deputy. Summary http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013510.html14:39
slaweqfrom what I wanted to highlight here is14:39
slaweqTwo high bugs related to CI which we should take a look: https://bugs.launchpad.net/neutron/+bug/1867936 https://bugs.launchpad.net/neutron/+bug/186823714:39
openstackLaunchpad bug 1867936 in neutron "test_update_delete_extra_route failing due to timeout when creating subnets" [High,Confirmed]14:39
openstackLaunchpad bug 1868237 in neutron "[tempest] Error in "test_multicast_between_vms_on_same_network" test case" [High,Confirmed]14:39
slaweqboth don't have assignment yet, so if anyone have some cycles to take a look, that would be great14:39
*** Lucas_Gray has quit IRC14:40
slaweqand also https://bugs.launchpad.net/neutron/+bug/1868137 which rubasov is already looking at but maybe someone more familiar with ovn driver could also take a look14:40
openstackLaunchpad bug 1868137 in neutron "default geneve overhead is not set high enough for ovn" [Medium,Confirmed]14:40
slaweqany other bugs You want to discuss with the team today?14:41
*** number80 has quit IRC14:42
haleybslaweq: am i deputy this week?14:42
slaweqhaleyb: no, this week hongbin is deputy14:42
slaweqYour turn is next week14:43
bcafarelnext week plan: create all the bugs!14:43
*** maciejjozefczyk has joined #openstack-meeting14:43
slaweqwe will do competition: who can open more bugs next week :P14:44
haleybi can close them just as fast :)14:44
slaweqhaleyb: :D14:45
slaweqok, lets move on to the last topic for today14:45
slaweq#topic On Demand Agenda14:45
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:45
slaweqanything else You want to discuss today/14:45
haleybi have one14:45
slaweqgo on haleyb14:45
haleybalong the recommendation of moving to unittest.mock, and other projects doing it i created https://review.opendev.org/#/c/711579/14:46
haleybit found some bugs which are in the related change section14:46
slaweqthat is huge patch :)14:46
haleybyes, very big, mostly one-liners luckily14:47
haleybbut it's now failing in the functional tests and needs some debugging, was wondering if i should split it up into unit and functional pieces to get one merged14:47
ralonsoh+1 for this14:48
njohnstonhaleyb: I think that is a good idea14:48
bcafarelI though it was only UT in that review, looks like I missed a few lines in that long list?14:49
slaweqbcafarel: at first glance it seems for me that functional tests may fail due to https://review.opendev.org/#/c/711579/3/neutron/tests/base.py14:49
bcafarelbut +1 on the idea, with fixes in now for UT it is mostly rename/reorder and it looked good to me when I checked14:49
haleybok, i'll get that one passing and propose another follow-on - i think it's the change in test_base.py? at least i thought it was the functional tests failing on a mock14:49
slaweqas those tests inherits from this too14:49
bcafarelah true!14:49
haleybslaweq: ah yes, that's it14:50
haleybso really it's the patches it's depending on that need review14:50
bcafarelok https://review.opendev.org/#/c/713350/ is a bit larger too14:51
*** Luzi has quit IRC14:52
haleybgo big or go home :)14:52
haleybi'm padding my stats14:52
ralonsohand the revert of https://review.opendev.org/#/c/711158?14:53
ralonsoh(this is the last related patch)14:53
haleybralonsoh: i was going to mention that one too14:53
haleyblooking at that again last night, looks like the int_br changes should be reverted for now, but the tun_br one is ok14:54
haleybliuyulong: don't know if you're here but is that ok? ^^14:54
haleybor we just revert and re-do14:54
slaweqI don't understand, why we need revert of https://review.opendev.org/#/c/711158 ?14:55
haleybthat was another change brought by the unittest.mock change, so maybe being too aggressive14:55
ralonsohwe use only native implementation14:55
ralonsohwhy can't we remove deferred?14:55
haleybi think there is still a small piece of code using ofctl in the int br, liu pointed it out i think14:56
ralonsohI'll recheck that14:57
ralonsohbut the add_flow command will depend on the implementation used14:57
ralonsohand now we have only native14:57
slaweqso shouldn't we get rid of this ofctl code instead of reverting Your patch?14:57
haleybhttps://github.com/openstack/neutron/blob/master/neutron/agent/common/ovs_lib.py#L422-L475 was the code14:58
ralonsohyes, you are right14:58
haleybhas a run_ofctl() call :(14:58
ralonsohslaweq, this is not that simple14:58
ralonsohslaweq, https://bugs.launchpad.net/networking-sfc/+bug/185317114:58
openstackLaunchpad bug 1853171 in neutron "Deprecate and remove any "ofctl" code in Neutron and related projects " [Medium,In progress]14:58
liuyulongtons of ovs-ofctl here in the log14:59
slaweqralonsoh: ok, now I remember :)14:59
ralonsohliuyulong, you are right: there are still some OF handled by ofctl14:59
slaweqok, we are running out of time15:00
slaweqso lets continue this in neutron channel if needed15:00
slaweqthx for attending the meeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Mar 24 15:00:28 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-03-24-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-03-24-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-03-24-14.00.log.html15:00
slaweqhave a great week everyone o/15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Mar 24 15:00:38 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 :)15:00
ralonsohyeah, the ofctl removal is not easy15:01
ralonsohthere is no 1:1 conversion15:01
ralonsohlet's wait 30 secs15:01
ralonsoh#topic RFEs15:02
*** sfernand has quit IRC15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/185861015:02
openstackLaunchpad bug 1858610 in neutron "[RFE] Qos policy not supporting sharing bandwidth between several nics of the same vm." [Undecided,New]15:02
ralonsohwe are still waiting for a spec or a POC15:02
slaweqand that seems to be pretty complex15:02
ralonsohI'll ping the author of the RFE today just to know the status15:02
ralonsohyeah, it is15:02
ralonsohso let's wait for it but I don't know if we'll see something landed this cycle15:03
ralonsohand that's all for today in this section!15:03
slaweqI don't think it will be this cycle15:04
ralonsohI dropped the classifier RFE because there are no volunteers to continue with the work15:04
ralonsohso I encourage anyone to continue with it15:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:05
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:05
ralonsohis something missing here?15:05
ralonsoh#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:05
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/186463015:06
openstackLaunchpad bug 1864630 in neutron "Hard Reboot VM with multiple port lost QoS " [Undecided,Fix released] - Assigned to Nguyen Thanh Cong (congnt95)15:06
ralonsohwell addressed by https://review.opendev.org/#/c/709687/15:06
ralonsohalready merged15:06
ralonsohand there is a backport https://review.opendev.org/#/q/If8edd29dd741f1688ffcac341fd58173539ba00015:06
ralonsohbut this patch in Train should be rebased on top of15:06
ralonsoh(one sec)15:06
ralonsoh(now in Train we have a small issue with rally)15:07
ralonsohso we need to wait for it15:07
slaweqnot so small :)15:07
openstackLaunchpad bug 1868691 in neutron "neutron-rally-task fails 100% on stable branches" [Critical,In progress] - Assigned to Bernard Cafarelli (bcafarel)15:07
ralonsohI know, I know...15:07
slaweqbut bcafarel is on it already15:07
ralonsohso the OVS QoS bug is almost solved, even in T15:08
ralonsohnext one15:08
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/186385215:08
openstackLaunchpad bug 1863852 in neutron "[OVN]Could not support more than one qos rule in one policy" [Medium,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:08
*** ociuhandu has quit IRC15:08
slaweqralonsoh: should this be backported also to Stein and older?15:08
slaweqor it applies only to Train?15:08
ralonsohlet me check that15:09
*** ociuhandu has joined #openstack-meeting15:09
ralonsohI'll check that after this meeting15:09
slaweqno, I can check it on my own later, I just though that maybe You will know :)15:09
*** ykatabam has quit IRC15:09
ralonsohno, sorry15:09
ralonsohthat bug was open to master and I know this is also happening in T15:10
ralonsohbut I don't know in previous versions15:10
ralonsohok, the OVN QoS bug15:10
*** mattw4 has joined #openstack-meeting15:10
ralonsohmaciejjozefczyk found today some issues in the patch15:10
ralonsoh#link https://review.opendev.org/#/c/711317/15:11
ralonsohand I still need to reply to haleyb15:11
maciejjozefczykralonsoh, slaweq this should be cherry-picked to train (qos)15:11
ralonsohbut is almost ready, probably in the next PS15:11
*** macz_ has joined #openstack-meeting15:11
ralonsohyes, this QoS refactor should be backported to networking-ovn15:11
ralonsoh(this is going to be funny...)15:11
maciejjozefczykactually everything related to qos should be in train, cause in train we have a limited qos functionality, and mainly its broken15:11
ralonsohyeah, once this patch is merged, I'll push a patch for n-ovn in T15:12
maciejjozefczykralonsoh, thanks!15:13
ralonsohand so far, this is everything I have for today in the meeting backlog!15:13
ralonsohdo you have any other bug?15:13
ralonsohok, so next section15:14
ralonsoh#topic Open Discussion15:14
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:14
ralonsohsomething to add?15:14
slaweqnot from me15:14
ralonsohor do you want 45 mins back?15:14
maciejjozefczykYes, I want to add one thing15:15
*** e0ne has quit IRC15:15
maciejjozefczykWe have bug in Core OVN related to qos, described here15:15
maciejjozefczyk#link https://mail.openvswitch.org/pipermail/ovs-discuss/2020-March/049866.html15:15
maciejjozefczykActually if there are for example 2 ports from the same network on the same chassis (same compute)15:15
maciejjozefczykthose 2 ports share one 'qos bucket'15:16
maciejjozefczykthat means the limit is shared between those ports15:16
maciejjozefczykso if one port is noisy - the other port from the same network could have a problem15:16
*** e0ne has joined #openstack-meeting15:17
ralonsohor just transmitting one flow15:17
maciejjozefczykThe solution would be to create a meter per each OVS inport, and I'm discussing it with OVN folks, to address that15:17
ralonsohthe BW will be shared15:17
ralonsohbut why per inport?15:17
* slaweq needs to leave for few minutes, sorry15:17
ralonsohwhy not one meter per OVN QoS rule?15:17
maciejjozefczyksorry, inport or outport15:17
ralonsohslaweq, bye15:17
maciejjozefczykslaweq, bb!15:18
ralonsohin a future, we'll have "match" fields with other than inport/outport15:18
ralonsohfor example, filtering by ip or mac15:18
maciejjozefczykralonsoh, ah yes15:18
ralonsoh(for FIP, for example)15:18
maciejjozefczykralonsoh, yes you're right15:19
ralonsohthe point is, this is not like classfull HTC in TC15:19
ralonsohwhere you have a qdisc and classes and filters15:19
ralonsoheverything organized in a tree15:19
ralonsohthere is no dependency between ovn qos rules15:19
ralonsohso, IMO, there should be a meter per rule15:20
ralonsohanother topic could be the performance...15:20
ralonsohbut image you have 100 ports in one chassis15:20
ralonsoheach one shaped15:20
ralonsohand 100 FIPs15:20
ralonsohso you'll need those 200 meters, each one different15:20
ralonsohwhat I don';t understand is the current OVN qos implementation15:22
ralonsohmaybe there is a reason for that15:22
ralonsohand we need to implement the qos in another way15:22
ralonsohneutron qos for ovn15:22
ralonsohok, something else to add?15:23
maciejjozefczykfrom me nope15:24
ralonsohthank you all and see you online!15:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:24
openstackMeeting ended Tue Mar 24 15:24:24 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-03-24-15.00.html15:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-03-24-15.00.txt15:24
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-03-24-15.00.log.html15:24
*** links has quit IRC15:24
*** ociuhandu has quit IRC15:24
*** gyee has joined #openstack-meeting15:26
*** ysandeep|afk is now known as ysandeep15:35
*** jamesmcarthur has quit IRC15:49
*** jamesmcarthur has joined #openstack-meeting15:58
*** ociuhandu has joined #openstack-meeting16:02
*** jamesmcarthur has quit IRC16:09
*** mattw4 has quit IRC16:18
*** mattw4 has joined #openstack-meeting16:19
*** jamesmcarthur has joined #openstack-meeting16:21
*** belmoreira has quit IRC16:22
*** jamesmcarthur has quit IRC16:26
*** ysandeep is now known as ysandeep|away16:50
*** jmasud has quit IRC16:54
*** jmasud has joined #openstack-meeting16:55
*** mattw4 has quit IRC16:57
*** mattw4 has joined #openstack-meeting16:58
*** rpittau is now known as rpittau|afk17:18
*** e0ne has quit IRC17:18
*** e0ne_ has joined #openstack-meeting17:18
*** maciejjozefczyk has quit IRC17:21
*** maciejjozefczyk has joined #openstack-meeting17:21
*** jlibosva has quit IRC17:24
*** ociuhandu has quit IRC17:24
*** ociuhandu has joined #openstack-meeting17:25
*** maciejjozefczyk has quit IRC17:26
*** number80 has joined #openstack-meeting17:28
*** lajoskatona has left #openstack-meeting17:32
*** ociuhandu has quit IRC17:32
*** ijw has joined #openstack-meeting17:38
*** ijw__ has quit IRC17:42
*** ianychoi has quit IRC17:45
*** vesper11 has quit IRC17:45
*** mahatic has quit IRC17:45
*** dmsimard|off has quit IRC17:45
*** jokke_ has quit IRC17:45
*** ianychoi has joined #openstack-meeting17:46
*** vesper11 has joined #openstack-meeting17:47
*** irclogbot_0 has quit IRC17:47
*** irclogbot_1 has joined #openstack-meeting17:48
*** jamesmcarthur has joined #openstack-meeting18:04
*** e0ne_ has quit IRC18:04
*** ociuhandu has joined #openstack-meeting18:12
*** number80 has quit IRC18:16
*** jamesmcarthur has quit IRC18:19
*** jamesmcarthur has joined #openstack-meeting18:19
*** ociuhandu has quit IRC18:22
*** larainema has quit IRC18:23
*** ociuhandu has joined #openstack-meeting18:23
*** ociuhandu has quit IRC18:28
*** diablo_rojo has joined #openstack-meeting18:42
*** mattw4 has quit IRC18:46
*** macz_ has quit IRC18:47
*** macz_ has joined #openstack-meeting18:48
*** ociuhandu has joined #openstack-meeting18:51
clarkbinfra meeting time! (in about 2 minutes)18:59
clarkb#startmeeting infra19:01
openstackMeeting started Tue Mar 24 19:01:38 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
clarkbAnyone else here for the meeting?19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-March/006612.html Our Agenda19:01
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkb#link http://lists.openstack.org/pipermail/foundation/2020-March/002854.html PTG going virtual19:02
clarkbI'm sure most or all of us have seen this news already, but wanted to call it out if you hadn't19:02
fungithanks for the heads up!19:02
clarkbThe big impact for us is that we'll likely try to support the virtual event though tools19:03
clarkbcorvus has begun work on a jitsi deployment incorporating our etherpad which looks promising but I'm sure tehre will be other things as well19:03
corvusclarkb: any idea what other things?19:03
clarkbcorvus: right now? no :)19:04
clarkbthough collecting artifacts might be something that becomes more important19:04
clarkbespecially if conversations span timezones and we need to forward more concrete thoughts/items19:05
mordredlike scrolls and treasure chests and magical amulets?19:05
fungidibs on the +1 sword19:05
* mordred weilds the +2 mace of bludgeoning19:05
corvusi thought that was what the etherpad was for...19:06
fungithat probably is what the etherpad is for19:06
corvusjust trying to figure out if i'm barking up the wrong tree19:06
clarkbcorvus: I don't think you are19:06
mordredI think your tree is great!19:06
fungii'm guessing "other things" might be improvements to ptgbot19:07
fungischeduling tools? dunno19:07
clarkbbut there are a lot of moving parts and we've been involved in the technology side a bit in the past19:07
mordredI'm guessing clarkb is just trying to pessimistically anticipate a general need for "other things"19:07
clarkb(so I expect more moving parts)19:07
corvusyeah, lots of other opportunities19:07
* mordred thinks meatpad is amazing19:07
*** ralonsoh has quit IRC19:07
* mordred would like to propose that we cname it so that both spellings are acceptable19:07
fungiveggiepad is leaner and better for you19:08
mordredok - maybe 2 cnames :)19:08
clarkbwe should continue and then we can talk about meetpad in more detail19:08
clarkb#topic Actions from last meeting19:08
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:08
clarkbianw had an action to cleanup files02 and old static resources19:09
clarkbI think I saw a statusbot log action for that?19:09
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-17-19.01.txt minutes from last meeting19:09
ianwyes, the servers are gone.  there was some fun when i tried to look at the volumes :)19:09
ianwi think that is sorted now, need to catch up, but i'll leave the old static volume and have a note to clear it out in a few months, just in case19:09
clarkbsounds good, thanks19:10
ianw... so ... i think the transition is done.  i can move it in specs to the done pile later19:10
clarkb#topic Specs approval19:10
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:10
* mordred hands a +2 chicken of awesome to ianw19:10
*** Shrews has joined #openstack-meeting19:10
clarkbreally quickly before we talk meetpad is the xwiki spec19:10
clarkb#link https://review.opendev.org/#/c/710057/ xwiki for wikis19:11
clarkbfungi: ttx ^ I think we probably can put this up for approval this week given the discussion we had on the topic in last weeks meeting19:11
clarkbI think we are largely on the same page that experimentation around the wiki problem is worthwhile19:11
clarkbis there any disagreement with that?19:11
fungii'm fine with putting it up for a vote but also don't expect it's too urgent19:12
fungigood either way19:12
clarkbya I'm not sure we'll get too much additional feedback if we drag it out, and the topic is fresh in minds now given the discussion last week19:13
*** e0ne has joined #openstack-meeting19:13
clarkbok I'll look to landing that EOD thursday local time.19:14
clarkb#link https://review.opendev.org/714189 meetpad19:14
clarkbFor anyone not familiar the meetpad idea is to combine jitsi meet and etherpad into a remote collaboration tool for events like a virtual PTG (though sure to have uses elsewhere too)19:14
clarkbcorvus: ^ probably ahs a lot more to say about it19:14
corvusi think that about covers it19:15
corvusi'm optimistic that having a tool focused on the design session workflow will be a passable substitute19:16
corvusi've tested it small-scale, but not large scale19:16
corvussince this is a low-commitment standalone service, we might want to think about going aheand and spinning it up to see how it goes19:16
clarkbya I'm hoping we can use it at medium scale a bit before the main event19:16
corvuswe can always shut it down later; it has no persistent storage or anything19:16
fungii can imagine ways in which it could even make some remote participation in otherwise in-person events more viable19:17
mordredespecially since you've got the ansbiels already19:17
corvusand yes, the complete implementation is ready to go19:17
clarkbOn the deployment side my one concern is that the shape of the deployment is very different than our existing docker stuff19:17
corvuswell, not *very* different19:17
corvusi managed to get it using host networking19:17
clarkbya, but instead of process per container its lots of processes per container (including cron)19:17
clarkbit will just look different from the management side which is probably ok if people are aware of it19:18
corvusfwiw, i'm not really aware of it :)19:18
corvusi think the cron stuff is only for certbot?  which we also won't use19:18
corvusbecause i hooked it into our existing acme stuff19:18
clarkbah ok so we can trim out the bits we don't need19:18
mordredyeah - I thnk the images have more stuff in them - but we're not necessarily using those images in that way19:19
corvuswell, i wouldn't trim it out19:19
mordredwhich is fine by me19:19
corvusi'd like to use upstream images if possible19:19
corvus(right now, we need a customized local image because i have a patch outstanding)19:20
mordredyeah. we're really only building these atm because we have to carry a patch right?19:20
clarkbya I'm not opposed, more I wanted to call out how they seemed to be different than how we've tried to construct things19:20
clarkbif we run the upstream images it will be even more clear19:20
corvuswell, i'm not sure they're that different19:20
corvusthey're using our acme letsencrypt stuff, and there are 4 containers for the 4 processes19:20
clarkbI've misread the cron stuff then19:21
corvusit's there, we just won't use it so we can ignore it19:21
corvusi think it fits in pretty well with our model; our docker-compose file is really close to the upstream one19:22
fungiso the images have more in them that we'll be leveraging is the main concern?19:22
corvusso i think it's worked out pretty nice actually19:22
fungier, more in then THAN we'll be leveraging i meant19:22
* fungi can't type19:22
corvusit's close enough to our model that i was able to complete the entire implementation stack in less than a day19:22
clarkbfungi: on my initial read it appeared that we would be using cron to run certbot19:22
clarkbbut I guess thats all there to avoid divergence from the upstream images and not actually to be consumed in our setup19:23
fungiand we're not, got it19:23
corvuswe may yet be19:23
corvusbut it won't do anything19:23
corvusif we really want to pull it out, we can, but i don't think it's a big deal19:24
clarkbif the plan is to use upstream images anyway may as well keep it (since we'll get it back again once we move to their images19:24
corvusi'd like to do that, yes19:24
fungiseems fine to me19:25
corvusso what's the timing here?19:25
clarkbplease review the spec if you haven't already. Then plan to land it next week? Though at the rate implementation is going maybe we should try to get people to review it this week and land the spec sooner than later19:25
corvusto be clear, implementation is done :)19:26
corvusthe next thing is to create the server after the implementation patches land19:26
fungii'd be cool landing it this week19:26
* mordred too19:26
fungisome of us have already reviewed and voted in favor of the spec19:26
clarkbof active roots its missing ianw and myself (and I've actually read it just not finalized my vote (which is positive I'm excited)19:27
frickler+1, looking forward to tsting this19:27
fungidoesn't seem like it needs adjustments19:27
clarkbianw: ^ you ok with landing that this week?19:27
fungialso, it's a timely effort, so the less we unnecessarily delay progress on it, the better19:27
clarkbcool I'll give people until thursday to review it then plan to approve it19:27
corvusshould we ping anyone from other communities about this?19:28
corvusor stand up the server and then do that?19:28
clarkbcorvus: I half expect it would be easier to explain once the service is up19:28
mordredme too19:28
fungii think asking them to help test it out makes more sense19:28
mordred"go look at this"19:28
corvusyeah, i tend to think so too.  there's so little cost in standing it up19:28
fungii expect we'll want to conduct at least one "load test" where we try to get lots of folks using it at the same time19:29
fungiso we can work out sizing before it gets slammed and falls over at ptg time19:29
clarkbas a time check we are about halfway through our allotted time and have more to discuss. Do you think we've gotten the important bits for this spec sorted (until thursday at least)?19:29
corvusclarkb: yep, thanks!19:29
clarkb#topic Priority Efforts19:30
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:30
clarkb#topic Update Config Management19:30
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:30
clarkbmordred: (or fungi or corvus ?) can you fill us in on the gerrit on containers status?19:30
mordredwell ...19:30
mordredwe ALMOST updated on friday during renames19:30
mordredbut then there was some container content issues - mostly the fact that jeepyb was missing19:31
fungithe maintenance went really well, right up until.. yeah. so close!19:31
mordredwe've been unwinding an fixing some issues in the job19:31
fungihook script entrypoints were missing19:31
fungiwas the main setback19:31
mordredas soon as I get another set of images built with the latest jeepyb changes (so close last time) - we'll be in a good position to do another quick restart19:31
mordredthat should be no longer than a stop/start19:32
*** maciejjozefczyk has joined #openstack-meeting19:32
mordredin the process - we learned a gerrit thing that's worth sharing ...19:32
fungithis has also spurred greater testing for jeepyb, so it's not all bad19:32
mordredgerrit init does three things: it downloads the database driver, it expands the plugins from the war, and it runs db migrations19:32
*** e0ne has quit IRC19:32
mordredwe updated the image build script to do the first two - as they make no sense to be runtime activities in a container image19:32
mordredso now seriously we only have to run init for db migrations when we upgrade19:33
mordredso - just a note for everyone to be aware of19:33
clarkband until we get restarted on that new image project creation is not expected to work19:34
clarkb(so we are holding new projects for now)19:34
clarkbmordred: and the testing will incorporate testing of manage-projects?19:34
*** e0ne has joined #openstack-meeting19:34
clarkbit just occured to me that we may want to bind mount in the jeepyb cache for that? somethign to sort out side of the meeting19:34
mordredwe already do!19:35
mordredalthough that's worth a mention19:35
funginew project creation and anything else on the gerrit server is blocked, right (this includes gerritbot config changes)19:35
mordredI added helper scripts for manage-projects and track-upstream that run docker run with the appropriate bind-mounts19:35
mordredfungi: yah19:35
corvusdo we need to hold new projects right now?19:35
mordredso if you go to review-dev and just run manage-projects - it should work19:35
corvusit's still in emergency, right?19:36
mordredyah - I think AJaeger has been holding them19:36
mordredthat's right19:36
corvusso i guess nothing will run automatically19:36
corvusok.  just wanted to double check my understanding on that19:36
fungicorvus: seems like it's safe to keep approving them, they just won't take effect19:36
corvusyeah, though that's potentiall confusing19:36
* fungi was confused that the infra-manual rename hadn't taken effect for gerritbot, for example)19:37
clarkbok sounds like that may be it. Lets move on as we have even more to talk about :)19:38
clarkb#topic OpenDev19:38
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:38
clarkbWe've updated the way Gitea restarts happen. This should allow gerrit's replication plugin to properly detect the remote service is offline which will result in retries19:38
clarkbhttps://review.opendev.org/714691 is small change that will run this in production (we do test it in checka nd gate too) just to be sure it doesn't cause problems unexpectedly later19:39
clarkbAlso the OpenStack TC governance change to excise OpenDev has landed (mentioend this last week) and we've landed our documentation updates19:39
clarkbTwo big todos that come out of that is I think we need to formally elect a project lead as well as start forming the Advisory Board19:40
mordredclarkb: my understanding is that you are now lifetime project lead, right?19:40
clarkbmordred: I was going to nominate you19:40
fungihot potato19:40
corvusnot it19:41
clarkbmore seriously though I was going to start noodling on how the process for both of those. We've got lots of hsitory to work with can liekly come up with something sane19:41
clarkbif you've got ideas or thoughts let me know or feel free to start a mailing list thead19:41
clarkband that takes us to the last set of opendev related topics I had on the agenda (which I'm going to reorder sligthly)19:41
clarkblocation of future meetings as well as need for opendev-discuss mailing list19:41
clarkbinitially I had thought we could do our weekly meetings in #opendev but frickler has indicated that the overlap in communications would cause problems19:42
clarkbI think that concern is valid, so maybe we should create an #opendev-auxillary (I can't spell) where we can have meetings as well as use it for quiet space like the old infra-incident?19:43
frickleryes, I've experienced that e.g. in the qa team and I would not like it19:43
clarkbthen anyone looking to catch up can check that channel for any super important updates and if empty skim #opendev at their leisure19:43
ianw++ to separate19:43
fungia related question is whether we need something similar to or replacing #openstack-infra-incident19:43
clarkbcorvus: any concerns with that from a freenode perspective? I suppose its another channel for bots but we are trimming channels elsewhere for the bots19:43
clarkbfungi: ya I kinda expect we can simply use a single side channel for both19:44
clarkbbecause if there is an important incident we won't be meeting anyway19:44
clarkb(I'm trying to be friendly to bots and not add too many extra channels)19:44
frickleror we make an incident-themed meeting19:44
clarkbfrickler: ya or that19:44
fungiso bikeshed some name which covers meetings and incidents19:45
corvusi think we own the #opendev namespace19:45
fricklerthen the channel could in fact be named #opendev-meeting, I'd think that would make it's purpose more easily visible19:45
fungi#opendev-bikeshed isn't taken ;)19:45
clarkbfrickler: thats a good point. I'm happy to go with that19:45
clarkbanyone want to take an action to push up changes to make that official?19:46
clarkbwe can bikeshed further in review if necessary19:46
fungii can do that unless someone else really wants it19:46
clarkb#action fungi Add new opendev meeting (and incident) channel19:47
clarkbthe other related piece of this is mailing lists19:47
clarkbI thinkwe can just go ahead aand create an opendev-discuss list on lists.opendev.org and start transitioning more of our email communication there19:47
clarkbThen we can possibly fold openstack-infra into openstack-discuss as well19:47
fungiservice-discuss@ would make sense given we already have service-announce@19:48
clarkbfungi: ++19:48
fungii can do the change for that as well19:48
clarkb#action fungi Add service-discuss@lists.opendev.org mailing list19:48
clarkbthank you!19:48
fungiand again, names can be debated in the change19:49
clarkb#topic General Topics19:50
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:50
clarkbThe last agenda item was a catchup on mediwiki updates/cahnges19:50
clarkbI don't think there has been any movement on the puppet retrofit19:50
clarkbbut did want to have this as an opportunity to talk about the possibility of dockerizing the deployment19:50
clarkbmnaser: corvus ^ I think you've both been busy so don't expect there is anything new to discuss, but if there is feel free to share19:51
corvusi don't have anything to report there19:51
fungiif i find time i'll still try to make progress on the puppet module because it's the closest thing we have to documentation for the target configuration19:52
fungibut mostly i suspect it needs troubleshooting done with extensions and possibly extension conflicts19:52
clarkband that takes us to the free for all portion of the meeting19:54
clarkb#topic Open Discussion19:54
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:54
clarkbwe lucked out and our monthly delivery of TP arrived (a few days late) from amazon. But now I'm distributing TP to family19:56
mordredwe have plenty for ourselves19:56
*** rcernin|brb has quit IRC19:57
clarkbAlso oreilly has apparently cancelled all in person events forever. If you were set up to speak at one of their events that info may be useful to you19:58
fungipeople here tend to stockpile it to fling during the st patrick's day parade (which wound up cancelled). this produced an odd dynamic with people unexpectedly sitting on stockpiles of the stuff and stores already running low before the panic hit19:58
clarkb(or attend I suppose)19:59
*** vishalmanchanda has quit IRC19:59
clarkbAnd that is time. Thank you everyone!19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
openstackMeeting ended Tue Mar 24 19:59:46 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-24-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-24-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-24-19.01.log.html19:59
fungithanks clarkb!20:00
*** rubasov has quit IRC20:03
*** ociuhandu has quit IRC20:04
*** ociuhandu has joined #openstack-meeting20:06
*** ociuhandu has quit IRC20:11
*** rubasov has joined #openstack-meeting20:19
*** maciejjozefczyk has quit IRC20:20
*** rubasov has quit IRC20:24
*** e0ne has quit IRC20:24
*** e0ne has joined #openstack-meeting20:25
*** rubasov has joined #openstack-meeting20:26
*** e0ne has quit IRC20:29
*** ijw has quit IRC20:30
*** ijw has joined #openstack-meeting20:30
*** ijw_ has joined #openstack-meeting20:31
*** ijw has quit IRC20:35
*** ijw has joined #openstack-meeting20:42
*** Shrews has left #openstack-meeting20:45
*** ijw_ has quit IRC20:45
*** TrevorV has quit IRC20:47
*** jamesmcarthur has quit IRC20:51
*** jamesmcarthur has joined #openstack-meeting20:52
*** jmasud has quit IRC20:54
*** jmasud has joined #openstack-meeting20:56
*** jamesmcarthur has quit IRC20:56
*** raildo_ has joined #openstack-meeting20:59
*** gadzhet has joined #openstack-meeting20:59
*** raildo has quit IRC21:01
*** gadzhet has quit IRC21:07
*** rfolco has quit IRC21:12
*** jamesmcarthur has joined #openstack-meeting21:14
*** jamesmcarthur has quit IRC21:15
*** jamesmcarthur has joined #openstack-meeting21:16
*** ociuhandu has joined #openstack-meeting21:18
*** ociuhandu has quit IRC21:29
*** ociuhandu has joined #openstack-meeting21:30
*** ociuhandu has quit IRC21:35
*** ociuhandu has joined #openstack-meeting21:36
*** e0ne has joined #openstack-meeting21:43
*** raildo_ has quit IRC21:45
*** ijw has quit IRC21:53
*** ijw has joined #openstack-meeting21:53
*** brinzhang_ has joined #openstack-meeting21:56
*** brinzhang has quit IRC22:00
*** jamesmcarthur has quit IRC22:03
*** jamesmcarthur has joined #openstack-meeting22:04
*** jamesmcarthur has quit IRC22:05
*** ociuhandu has quit IRC22:05
*** jamesmcarthur has joined #openstack-meeting22:05
*** ykatabam has joined #openstack-meeting22:13
*** e0ne has quit IRC22:18
*** slaweq has quit IRC22:23
*** rh-jelabarre has quit IRC22:27
*** andrebeltrami has quit IRC22:34
*** rcernin has joined #openstack-meeting22:45
*** ijw_ has joined #openstack-meeting23:08
*** ijw has quit IRC23:10
*** macz_ has quit IRC23:12
*** jamesmcarthur has quit IRC23:12
*** bbowen has quit IRC23:14
*** ijw has joined #openstack-meeting23:20
*** ijw_ has quit IRC23:23
*** macz_ has joined #openstack-meeting23:27
*** ijw_ has joined #openstack-meeting23:27
*** ijw has quit IRC23:30
*** macz_ has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting23:50
*** ociuhandu has joined #openstack-meeting23:55
*** jamesmcarthur has quit IRC23:57

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