Tuesday, 2020-03-17

*** jamesmcarthur has quit IRC00:02
*** yamamoto has joined #openstack-meeting00:22
*** jamesmcarthur has joined #openstack-meeting00:28
*** artom has quit IRC00:32
*** jamesmcarthur has quit IRC00:32
*** artom has joined #openstack-meeting00:35
*** ociuhandu has joined #openstack-meeting00:44
*** yamamoto has quit IRC00:47
*** Liang__ has joined #openstack-meeting00:48
*** ociuhandu has quit IRC00:49
*** yamamoto has joined #openstack-meeting00:55
*** nicolasbock has quit IRC01:04
*** jamesmcarthur has joined #openstack-meeting01:07
*** jamesmcarthur has quit IRC01:15
*** jamesmcarthur has joined #openstack-meeting01:16
*** jmasud has joined #openstack-meeting01:22
*** slaweq has joined #openstack-meeting01:23
*** slaweq has quit IRC01:28
*** jamesmcarthur has quit IRC01:53
*** jamesmcarthur has joined #openstack-meeting02:05
*** boldo has joined #openstack-meeting02:16
*** masahito has joined #openstack-meeting02:22
*** masahito has quit IRC02:23
*** jamesmcarthur has quit IRC02:24
*** jamesmcarthur has joined #openstack-meeting02:32
*** rh-jelabarre has quit IRC02:35
*** maohongbo has joined #openstack-meeting02:51
*** maohongbo1 has joined #openstack-meeting03:06
*** maohongbo has quit IRC03:07
*** maohongbo1 is now known as maohongbo03:07
*** apetrich has quit IRC03:09
*** Liang__ has quit IRC03:34
*** maohongbo1 has joined #openstack-meeting03:36
*** maohongbo has quit IRC03:38
*** maohongbo1 is now known as maohongbo03:38
*** ricolin has joined #openstack-meeting03:41
*** Liang__ has joined #openstack-meeting03:47
*** tetsuro has joined #openstack-meeting03:59
*** jamesmcarthur has quit IRC03:59
*** jamesmcarthur has joined #openstack-meeting04:03
*** jamesmcarthur has quit IRC04:08
*** kiyofujin has joined #openstack-meeting04:09
*** jamesmcarthur has joined #openstack-meeting04:10
*** jamesmcarthur has quit IRC04:35
*** maohongbo1 has joined #openstack-meeting04:38
*** maohongbo has quit IRC04:39
*** maohongbo1 is now known as maohongbo04:39
*** jamesmcarthur has joined #openstack-meeting04:48
*** ricolin has quit IRC04:48
*** jamesmcarthur has quit IRC04:53
*** jmasud has quit IRC04:54
*** jmasud has joined #openstack-meeting04:56
*** vishalmanchanda has joined #openstack-meeting04:57
*** kiyofujin has quit IRC04:59
*** links has joined #openstack-meeting05:10
*** Liang__ has quit IRC05:24
*** yamamoto has quit IRC05:31
*** yamamoto has joined #openstack-meeting05:45
*** ricolin has joined #openstack-meeting05:45
*** dklyle has quit IRC06:06
*** ociuhandu has joined #openstack-meeting06:17
*** ociuhandu has quit IRC06:28
*** ociuhandu has joined #openstack-meeting06:28
*** ociuhandu has quit IRC06:33
*** yamamoto has quit IRC06:49
*** yamamoto has joined #openstack-meeting06:53
ricolinmulti-arch SIG meeting on #openstack-meeting-alt in an hour07:04
*** dkushwaha has joined #openstack-meeting07:31
*** keiko-k has joined #openstack-meeting07:47
*** ociuhandu has joined #openstack-meeting07:49
*** lpetrut has joined #openstack-meeting07:51
*** slaweq has joined #openstack-meeting07:56
*** tpatil has joined #openstack-meeting07:59
*** takahashi-tsc has joined #openstack-meeting08:00
*** pbhole has joined #openstack-meeting08:01
*** nitinuikey has joined #openstack-meeting08:02
dkushwaha#startmeeting tacker08:02
openstackMeeting started Tue Mar 17 08:02:32 2020 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
dkushwaha#topic Roll Call08:03
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:03
*** masahito has joined #openstack-meeting08:04
dkushwahahello all08:04
dkushwahaOk, lets start..08:07
dkushwaha#topic Openstack Release schedule08:07
*** openstack changes topic to "Openstack Release schedule (Meeting topic: tacker)"08:07
dkushwahaFor Ussuri release, we have around one month left.08:08
dkushwaha#link https://releases.openstack.org/ussuri/schedule.html08:08
dkushwahawe needs to focus on code patches08:09
dkushwahaUnfortunately i could not sped enough time on review.08:10
dkushwahaI request you all to please review as much as possible, which is needed for code quality08:11
dkushwahaah, my typo08:12
dkushwahatpatil do you have some to discuss ?08:13
tpatilwe have pushed patches for vnf packages and VNFLCM08:13
tpatil#link : https://review.opendev.org/#/q/status:open+topic:bp/tosca-csar-mgmt-driver08:14
tpatilabove for enhancement of vnf packages08:14
*** masahito has quit IRC08:14
tpatil#link : https://review.opendev.org/#/q/topic:bp/support-etsi-nfv-specs+(status:open+OR+status:merged)08:14
tpatilabove for VNFLCM APIs08:14
tpatilStill working on WIP patches. We will push new patches to remove WIP soon08:15
dkushwahai see, multiple patch there .08:16
dkushwahajust a quick question, why we need changes in requirements ?08:16
tpatilYes, lot of code for review08:16
tpatilthat's needed for vnf packages.  We are using sqlalchemy-filter library08:17
hyunsikyang__Hi I am late.08:17
*** tesseract has joined #openstack-meeting08:17
tpatilfor listing vnf packages, user can multiple query parameters in filters which will be mapped to the db models to return matching vnf packages08:18
tpatilfor this purpose we are using sqlalchemy-filter library08:18
*** apetrich has joined #openstack-meeting08:19
dkushwahatpatil +108:19
dkushwahatakahashi-tsc could you please help to review these patches08:21
takahashi-tscOK, I'll check these patches soon.08:22
tpatilFor VNFLCM API, we have dependency on heat-translator08:22
tpatilThere is one patch that's not yet merged: https://review.opendev.org/#/c/696446/08:22
patchbotpatch 696446 - heat-translator - ETSI-NFV SOL 001 translation: ScalingPolicy - 9 patch sets08:22
dkushwahatakahashi-tsc, tpatil,  we needs to close tackerclient patches. so please prioritize accordingly.08:23
tpatilWithout new version of heat-translator library, we cannot release VNFLCM API in U release08:23
dkushwahatakahashi-tsc, tpatil, first we needs to close tackerclient patches. so please prioritize accordingly.08:23
tpatilSure. We will push the last patch for heal command today and all patches will be up for review08:24
dkushwahatpatil, ok so let me focus on https://review.opendev.org/#/c/696446/ first. I will review it and will make sure to ask heat-translator member to merge it08:25
patchbotpatch 696446 - heat-translator - ETSI-NFV SOL 001 translation: ScalingPolicy - 9 patch sets08:25
tpatildkushwaha: That will be great. Thanks08:25
dkushwahatpatil anything else from your side ?08:27
tpatilThats all from my side08:27
dkushwahatakahashi-tsc do you have some update ?08:29
dkushwaha#topic OpenDiscussion08:31
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:31
takahashi-tschttps://review.opendev.org/#/c/700167/ Maybe my question is too comlicated...I change my question simple. Chage to just "which of the two is better?".08:31
patchbotpatch 700167 - tacker-specs - Support event alarm and vdu_autoheal by alarming p... - 4 patch sets08:31
hyunsikyang__Hi dkushwaha , if you have a tine please look at my patches.08:31
patchbotpatch 674761 - tacker - Adding Multi-Interface for Containerized VNF in Ta... - 17 patch sets08:32
hyunsikyang__and we are implementing https://review.opendev.org/#/c/681157/ now.08:32
patchbotpatch 681157 - tacker - [WIP]Implementation Fenix plugin in Tacker - 8 patch sets08:32
dkushwahahyunsikyang__ yup. Sorry  bro, I missed it. Will review it08:32
hyunsikyang__No problem:)08:33
hyunsikyang__I just want to finish it and do another patches. :D08:33
dkushwahatakahashi-tsc, not getting your point. which two ?08:35
takahashi-tscHow to write event_type condition. as event_type or condition.08:36
takahashi-tscE.g. "compute.instance.delete.end". is this event_type or condition08:36
dkushwahaIMO, it is an event.08:37
dkushwahaAlthough i suggest to please explore it in details in heat side08:38
*** ociuhandu has quit IRC08:39
*** ociuhandu has joined #openstack-meeting08:39
takahashi-tscYes, my concern point is heat side thinking. OK, I explore details in heat.08:40
dkushwahatakahashi-tscthanks, once you finish, please update the same on patch.08:42
dkushwahado we have anything else to discuss?08:43
dkushwahaok, Thanks Folks..08:45
dkushwahaPlease help on more and more reviews08:45
dkushwahaClosing this meeting now08:46
takahashi-tscOK thanks08:46
dkushwahathanks all08:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:46
openstackMeeting ended Tue Mar 17 08:46:33 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-03-17-08.02.html08:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-03-17-08.02.txt08:46
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-03-17-08.02.log.html08:46
*** pbhole has quit IRC08:46
*** e0ne has joined #openstack-meeting08:49
*** keiko-k has quit IRC08:51
*** ociuhandu has quit IRC08:54
*** tpatil has quit IRC08:54
*** priteau has joined #openstack-meeting09:01
*** ociuhandu has joined #openstack-meeting09:17
*** ociuhandu has quit IRC09:22
*** yaawang has quit IRC09:24
*** yamamoto has quit IRC09:25
*** yaawang has joined #openstack-meeting09:27
*** dkushwaha has quit IRC09:28
*** priteau has quit IRC09:31
*** rpittau|afk is now known as rpittau09:38
*** nitinuikey has quit IRC09:43
*** tetsuro has quit IRC09:52
*** tetsuro has joined #openstack-meeting09:56
*** tetsuro has quit IRC09:57
*** ociuhandu has joined #openstack-meeting10:05
*** ociuhandu has quit IRC10:12
*** ociuhandu has joined #openstack-meeting10:12
*** yaawang has quit IRC10:23
*** yaawang has joined #openstack-meeting10:23
*** jraju__ has joined #openstack-meeting10:28
*** links has quit IRC10:29
*** maohongbo1 has joined #openstack-meeting10:40
*** maohongbo has quit IRC10:41
*** maohongbo1 is now known as maohongbo10:42
*** Lucas_Gray has joined #openstack-meeting10:46
*** ociuhandu has quit IRC10:46
*** jraju__ has quit IRC10:53
*** ociuhandu has joined #openstack-meeting10:54
*** ociuhandu has quit IRC10:59
*** Lucas_Gray has quit IRC11:02
*** Lucas_Gray has joined #openstack-meeting11:02
*** nicolasbock has joined #openstack-meeting11:05
*** ociuhandu has joined #openstack-meeting11:07
*** Lucas_Gray has quit IRC11:10
*** Lucas_Gray has joined #openstack-meeting11:12
*** ociuhandu has quit IRC11:18
*** yamamoto has joined #openstack-meeting11:27
*** ociuhandu has joined #openstack-meeting11:29
*** rpittau is now known as rpittau|afk11:34
*** rpittau|afk is now known as rpittau|bbl11:34
*** nicolasbock has quit IRC11:34
*** ociuhandu has quit IRC11:34
*** nicolasbock has joined #openstack-meeting11:38
*** nicolasbock has quit IRC11:40
*** ysandeep is now known as ysandeep|afk11:46
*** maohongbo1 has joined #openstack-meeting11:55
*** maohongbo has quit IRC11:57
*** maohongbo1 is now known as maohongbo11:57
*** bbowen has quit IRC12:00
*** bbowen has joined #openstack-meeting12:01
*** rh-jelabarre has joined #openstack-meeting12:05
*** ociuhandu has joined #openstack-meeting12:08
*** yamamoto has quit IRC12:12
*** raildo has joined #openstack-meeting12:14
*** ociuhandu has quit IRC12:18
*** rcernin has quit IRC12:26
*** ociuhandu has joined #openstack-meeting12:33
*** nicolasbock has joined #openstack-meeting12:42
*** njohnston|afk is now known as njohnston12:47
*** enriquetaso has joined #openstack-meeting12:48
*** rpittau|bbl is now known as rpittau12:51
*** Luzi has joined #openstack-meeting12:54
*** ysandeep|afk is now known as ysandeep12:59
*** dklyle has joined #openstack-meeting13:03
*** ociuhandu has quit IRC13:07
*** ociuhandu has joined #openstack-meeting13:43
*** eharney has joined #openstack-meeting13:49
*** ociuhandu has quit IRC13:54
*** ociuhandu has joined #openstack-meeting13:55
*** ociuhandu has quit IRC13:58
*** ociuhandu has joined #openstack-meeting13:58
*** ysandeep is now known as ysandeep|afk14:01
*** Lucas_Gray has quit IRC14:02
*** Lucas_Gray has joined #openstack-meeting14:05
*** Lucas_Gray has quit IRC14:07
*** chuan137 has joined #openstack-meeting14:07
*** Lucas_Gray has joined #openstack-meeting14:09
*** spotz has joined #openstack-meeting14:14
*** chuan137 has quit IRC14:17
*** Lucas_Gray has quit IRC14:18
*** shintaro has joined #openstack-meeting14:20
*** Lucas_Gray has joined #openstack-meeting14:21
*** jeremyfreudberg has joined #openstack-meeting14:21
*** jamesmcarthur has joined #openstack-meeting14:22
*** yamamoto has joined #openstack-meeting14:24
*** yamamoto has quit IRC14:25
*** TrevorV has joined #openstack-meeting14:27
*** maciejjozefczyk has joined #openstack-meeting14:32
*** links has joined #openstack-meeting14:35
*** links has quit IRC14:35
*** ricolin_ has joined #openstack-meeting14:47
*** gmann is now known as gmann_afk14:48
ricolin_Multi-arch SIG meeting in 10 mins14:51
ricolin_feel free to add topic to agenda https://etherpad.openstack.org/p/Multi-Arch-agenda14:52
*** ociuhandu has quit IRC14:56
ricolin_#startmeeting multi-arch15:00
openstackMeeting started Tue Mar 17 15:00:51 2020 UTC and is due to finish in 60 minutes.  The chair is ricolin_. 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: multi-arch)"15:00
openstackThe meeting name has been set to 'multi_arch'15:00
ricolin_#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: multi-arch)"15:01
ricolin_jeremyfreudberg, how's everything15:01
*** shintaro has quit IRC15:01
*** ociuhandu has joined #openstack-meeting15:01
jeremyfreudbergricolin_: things are getting a bit crazy here in boston due to covid-19, but overall life is good15:02
jeremyfreudberghow are you?15:02
ricolin_Taiwan got 6x cases so far15:02
ricolin_things seems containable here15:03
jeremyfreudbergcontainable is good15:03
jeremyfreudbergi think i heard that taiwan is managing the problems well15:03
jeremyfreudbergin comparison to other countries15:03
ricolin_yeah, I guess most of us learned from SARS15:04
ricolin_Got any progress regarding multi-arch?:)15:05
jeremyfreudbergricolin_: no, not really any progress to share here. i still didn't have time for docs :(15:05
ricolin_we have also discuss about ARM wheels support15:06
ricolin_and unit test for arms (or other archs too)15:06
jeremyfreudbergricolin_: unit tests for what?15:07
ricolin_but no volunteer so far15:07
jeremyfreudbergi mean, testing what specifically15:07
ricolin_for arm env15:07
ricolin_allow exist unit tests for projects to run on arm64 env IIUC15:07
jeremyfreudbergoh, you mean running tests on arm env, not writing new tests15:08
ricolin_tonyb, take the action to create tasks on storyboard, I think it will explain more details15:08
ricolin_jeremyfreudberg, exactly15:09
ricolin_#topic open discussion15:09
*** openstack changes topic to "open discussion (Meeting topic: multi-arch)"15:09
ricolin_the devstack support is currently under progress15:10
ricolin_kevinz, is working on15:10
ricolin_Arm support for kubernetes/openstack-cloud-provide is almost there15:10
ricolin_only have to enable in CI job15:11
ricolin_I guess that's all we got for now15:12
jeremyfreudbergyeah, i will try to work on doc before the next meeting in two weeks15:12
ricolin_jeremyfreudberg, sounds great15:12
jeremyfreudbergok, talk to you later, stay safe ricolin_  :)15:14
ricolin_you too15:14
*** lpetrut has quit IRC15:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:14
openstackMeeting ended Tue Mar 17 15:14:37 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-17-15.00.html15:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-17-15.00.txt15:14
openstackLog:            http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-03-17-15.00.log.html15:14
*** jeremyfreudberg has left #openstack-meeting15:15
*** bbowen has quit IRC15:17
*** ricolin_ has quit IRC15:18
*** jmasud has quit IRC15:20
*** bbowen has joined #openstack-meeting15:25
*** priteau has joined #openstack-meeting15:33
*** gyee has joined #openstack-meeting15:38
*** Lucas_Gray has quit IRC15:50
*** ociuhandu has quit IRC15:58
*** Luzi has quit IRC16:20
*** ociuhandu has joined #openstack-meeting16:31
*** ociuhandu has quit IRC16:45
*** ociuhandu has joined #openstack-meeting16:47
*** maohongbo1 has joined #openstack-meeting16:51
*** maohongbo has quit IRC16:53
*** maohongbo1 is now known as maohongbo16:53
*** rpittau is now known as rpittau|afk17:10
*** jamesmcarthur has quit IRC17:11
*** lyarwood has quit IRC17:11
*** jamesmcarthur has joined #openstack-meeting17:12
*** priteau has quit IRC17:12
*** Lucas_Gray has joined #openstack-meeting17:12
*** jamesmcarthur has quit IRC17:13
*** jamesmcarthur has joined #openstack-meeting17:13
*** Lucas_Gray has quit IRC17:15
*** Lucas_Gray has joined #openstack-meeting17:17
*** jamesmcarthur has quit IRC17:28
*** ricolin_ has joined #openstack-meeting17:29
*** jamesmcarthur has joined #openstack-meeting17:29
*** jamesmcarthur has quit IRC17:31
*** jamesmcarthur has joined #openstack-meeting17:31
*** Lucas_Gray has quit IRC17:33
*** jmasud has joined #openstack-meeting17:36
*** tesseract has quit IRC17:37
*** ricolin_ has quit IRC17:43
*** jmasud has quit IRC17:47
*** jmasud has joined #openstack-meeting17:55
*** jmasud has quit IRC17:58
*** Shrews has joined #openstack-meeting18:31
*** ociuhandu has quit IRC18:37
*** AJaeger has joined #openstack-meeting18:41
*** rfolco has joined #openstack-meeting18:44
*** diablo_rojo has joined #openstack-meeting18:45
*** rfolco has quit IRC18:48
*** ijw_ has joined #openstack-meeting18:50
*** Adri2000 has quit IRC18:53
*** ijw has quit IRC18:53
*** Adri2000 has joined #openstack-meeting18:55
clarkbAnyone else here for the infra meeting? we'll get started momentarily19:00
*** rh-jlabarre has joined #openstack-meeting19:00
clarkb#startmeeting infra19:01
*** patchbot has left #openstack-meeting19:01
openstackMeeting started Tue Mar 17 19:01:04 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
clarkbI remember to use the meeting name this time :)19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-March/006609.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** rh-jelabarre has quit IRC19:02
clarkbFirst up is the plan to switch over irc channels today. This ended up not getting communicated outside our bubble very well, but I'm thinking maybe we can still make the change and kindly redirect people as necessary?19:02
clarkbhttps://review.opendev.org/#/c/711106/ is the change to update the bot side of that if we think that is an ok plan19:02
clarkb(re communication fails I got distracted by nodepool and world events things)19:03
* AJaeger will approve that change once this topic is done19:03
AJaegerclarkb: yes, we can tell people - sending an email would be great in addition19:03
clarkbAJaeger: ya maybe doing it concurrently is sufficient19:03
clarkb(does anyone object to that plan: switch, be nice to people in the wrong place, and send email today)19:04
mordredsounds great19:04
* mnaser suggests a jar where you throw 5 cents everytime you use the wrong channel19:05
clarkbsounds like a plan. AJaeger I'm happy to write the email if you don't want to19:05
clarkb(I know its late for you)19:05
AJaegerclarkb: please do19:05
clarkbOk next up19:05
clarkb#link http://lists.openstack.org/pipermail/foundation/2020-March/002852.html OSF email on 2020 events19:05
fungiwe've ramped up use in #opendev a lot in the past week anyway19:05
clarkbI'm sure the foundation would love to hear feedback particularly as this starts to affect more and more of us in a tangible way19:06
fungiand opendev+ptg is only a few months away now19:06
*** vishalmanchanda has quit IRC19:07
clarkbfrom my side, my kids will be home a lot more and I'll likely need to ensure my wife doesn't spend all her time caring for them. This means scheduling may be weird for me especially until we find a routine19:07
clarkbI expect its a similar situation for a growing number of us19:07
AJaegeryeah, kids at home since yesterday...19:08
clarkbsomething something patience19:08
clarkb#topic Actions from last meeting19:08
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:08
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-10-19.01.txt minutes from last meeting19:09
clarkbTheer were no actions19:09
clarkb#topic Specs approval19:09
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:09
clarkb#link https://review.opendev.org/#/c/710057/ xwiki for wikis19:09
clarkbzbr: frickler I believe that ttx has updated that to try and address some of the concerns you raised19:09
clarkbfrom my side I think as a POC this is fine, we'll learn a lot more about vaibility through this experiement and can take it from there19:09
frickleryeah, I'm not completely conviced yet, but I also don't want to block it19:10
clarkbthis is also a problem space where we have interest in usage but less so in implementation so any help we can get there is a good thing imo19:10
clarkbif you've got time to (re)review I know ttx will apprecaite it19:11
fungiwe've also asserted i the past that for some services which opendev doesn't want to provide directly (for a variety of possible reasons) partnering with a hosted solution we can recommend to users is a viable alternative19:11
*** SpamapS has quit IRC19:12
fungifor example, to replace zanata with another supported translation platform19:12
*** tris has quit IRC19:12
clarkbI'll give this another minute before moving to the next topic if there are last bits of input19:13
zbri would personally find the gitea wiki more practical, in the end what stops any project from using their own external SaaS wiki? what makes xwiki more special?19:13
clarkbzbr: gitea wiki is not technically feasible currently19:14
clarkbit requires us to run a single gitea instance instead of 8, that instance must then have writable git repos (somethign that may be problematic with gerrit forcep ushing to it), and we need user management19:14
mnaseris the issue maintaining the wiki itself19:14
mnaseror the spam and whatn ot19:14
fungimnaser: i think that's an issue with any wiki19:14
clarkbmnaser: our mediawiki deployment is in really sad shape and we also don't have many people admining it to deal with spam etc19:15
fungimnaser: are you asking about wiki.openstack.org deployment of mediawiki, or just in general?19:15
clarkbzbr: the spec was updated to capture those issues with the gitea wiki option19:15
mnaseri see there's official docker images for mediawiki and infra is doing a lot of docker-compose these days19:15
*** rh-jlabarre has quit IRC19:15
mnaseri imagine the infrastructure to get a db and an image up is (mostly) there, i think, but i may be trivializing things19:15
clarkbreally I think the biggest issue is no one is saying "I'll make a new wiki deployment and find admins"19:16
clarkbttx is offering an alternative that attempts to address both problems19:16
fungithe openstack infra team (apart from opendev) is basically stuck maintaining a deployment of mediawiki for a while either way, so i don't object to exploring replacing the current puppet with docker images if we can get the right plugins working in it, but that's probably a somewhat separate topic19:16
*** jamesmcarthur has quit IRC19:16
clarkb(but we recognize its an experiement and we'll have to see how well it does)19:16
zbrmy personal impression is that wiki popularity went down since markdown editing on top of git repos become so easy, am I wrong? i see myself having to interact with wikis far less than 10 years ago. Bonus, I do not see much spam as PRs/CRs.19:17
mnaserhonestly -- i'd like to move us (vexxhost) towards doing more self-hosted things, so i can help with a solution towards "ill make a new wiki deployment" -- but i cant solve the "admins" part19:17
clarkbzbr: its a common request from projects using opendev19:17
*** ijw has joined #openstack-meeting19:17
clarkbthere is a group of users for which using git is the wrong tool19:18
corvusmnaser: yeah, i looked at that a little too, i think it's feasible, probably easier than what we're currently doing, but not entirely turn-key19:18
mnaseri'd gladly write a helm chart that we can deploy (maybe in a single node with k3s) so that i can also leverage it19:18
fungiyeah, right now i'm basically the only person checknig wiki.o.o edits and blocking spammers and mass deleting their pages19:18
clarkbbut they need something to share information and collaborate with a bit more reliably (and with history) than etherpad19:18
fricklerso the question is: will xwiki.com do spam moderation as part of the hosting, or will we still have to take care of that ourselves?19:18
*** jamesmcarthur has joined #openstack-meeting19:18
mordredzbr: yeah - I agree with you personally - I much prefer in-repo reviewed rst text19:18
fungias someone who doesn't really even use wiki.o.o these days i'd love for it to be someone else's problem19:18
clarkbfrickler: my understanding is they provide tools to do it, btu then maybe we have to tune them ourselves19:18
clarkbfrickler: and learning how well those tools work is a good outcome of this experiement19:19
zbrclarkb: sure, but this request does not come with specific wiki platfrom in mind? i am asking because i observed people not being open at all to switch one engine with another, they are not created equal.19:19
corvusto represent ttx's pov, he would *also* prefer that, and did an enormous amount of work to reduce the use of wikis by all osf-related projects, but still this need persists; the spec is a recognition of that.19:19
mnaseri can get a helm chart+ansible playbooks that can deploy wikis tested via zuul19:19
clarkbzbr: typically the request is just for a wiki not a specific wiki19:19
corvusand no, i don't think anyone has strong feelings about a particular engine (other than it be open source)19:19
mnaseri have strong feelings about using an external hosted service IMHO, we've historically always walked the path of self-hosting things19:20
mnaserthat's just me though19:20
*** ijw_ has quit IRC19:20
fungii think the "who will police this" is punted, but the multi-tenant nature of xwiki at least allows each fiefdom to do its own policing19:20
mnaserthere's always the possibility of xwiki deciding one day it no longer wants to have a free offering, or they stop maintaining the project19:20
clarkbmnaser: yup and that has happend to us in the past19:21
corvusmnaser: i'd be supportive of revamping our self-hosting19:21
*** rh-jelabarre has joined #openstack-meeting19:21
fungimnaser: and in such a case it's something we can run ourselves19:21
mnaserfungi: actually, my idea is that ever "group" would have their own deployment of mediawiki rather than one big multitenant one19:21
clarkbthe risk is real, but the current state of things is riskier imo19:21
corvusregarding self-policing -- if we have a containerized deployment, ... yeah, what mnaser just said19:21
corvuslike opendev's mailing list service19:21
corvus(and like its git service briefly was, until we folded it back in)19:22
fungimnaser: this same point comes up with the translation platform. we need to move folks off zanata since it's unmaintained. the folks who make the replacement we're looking at also offer to run it free for open source projects (with some caveats) so we talked about taking advantage of that rather than running it ourselves19:22
clarkbmy other concern is that it can often feel like a very small number of us do the life support for these more periphery services19:22
clarkbso even if someone spins up a deployment a bit of involvement beyond that would be nice19:22
mnaseri could use a self-hosted wiki, so i would gladly write helm charts that do it (if we're okay with maybe adopting something like using k3s in a single node)19:22
fungiwe don't want to wind up in the situation we were in with transifex, which was not really open source and then decided to kick all non-paying users off their hosted platform19:22
*** tris has joined #openstack-meeting19:22
*** jamesmcarthur has quit IRC19:22
mnaserif i was to do this, i'd consume it internally here, and hopefully there will be other consumers19:23
corvusmnaser: i'm not familiar with k3s; why not docker-compose?19:23
mnasercorvus: we deploy all of our apps inside k8s right now, so i was hoping that would be a path we can share with infra so that we can use a common base19:24
*** SpamapS has joined #openstack-meeting19:24
mnaserk3s is pretty much a single node k8s stripped down out of all the unnecessary things using local sqlite instead of etcd19:24
mordredcorvus: https://k3s.io/ fwiw19:24
corvusmordred: yeah, i googled that :)19:24
mnaserso that way, infra can consume the helm chart and run wikis, and i can run it in full sized k8s clusters19:24
corvusmnaser: we've talked about moving opendev to k8s, but our aim is to think about that after we actually get containerized services19:24
clarkbI don't think we should add the complexity of yet another system in order to run a system no one is caring for today19:25
corvuswe're like a few years behind schedule on that19:25
clarkb(thats my initial reaction)19:25
clarkbthat is how these system end up unmaintained19:25
corvusso i'm also hesitant to potentially throw a wrench in that process by moving the target19:25
fungialso my employer is a big part of why i've ended up maintaining the wiki. basically osf staff get contacted with complaints, dmca takedown notices, and various other legal threats if nobody keeps on top of spam policing for wiki.openstack.org19:25
*** gmann_afk is now known as gmann19:25
mnaseri understand, i mean fwiw we're adopting a lot more of the opendev "stack" so im building a lot more helm charts to deploy those on k8s19:25
mnaser(recent example is helm charts that are fully tested for lodgeit are a thing now)19:26
mnaserso i was hoping this can start a little roadways towards that but i understand19:26
clarkbI'm not hearing anyone say that an low overhead (for us) experiment is a problem though?19:27
corvusclarkb: which experiment?19:27
clarkbcorvus: the xwiki POC experiment19:27
clarkbthinking we can continue discussion there on the spec19:28
clarkbbut we should probably move forward with the meeting agenda19:28
corvusagreed, i still don't object to that; i also don't object to looking into containerized mediawiki (both to help maintain our current system and to provide an alternative if we don't select xwiki).  i understand some of the mediawiki stack and would be happy to help with that.  i'm less excited about bringing in k3s.19:28
clarkbalright lets move on then19:29
clarkb#topic Priority Topics19:29
*** openstack changes topic to "Priority Topics (Meeting topic: infra)"19:29
clarkb#topic OpenDev19:29
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:29
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2020-March/006603.html OpenDev as OSF pilot project19:29
clarkbif anyone else has thoughts on ^ that thread is still there :)19:29
clarkbI'll try to remind jbryce that update on process would be good, but I think its been a busy couple of weeks19:30
corvusi apparently had the last word on that one19:30
clarkb#link https://review.opendev.org/#/c/710020/ Split OpenDev out of OpenStack governance. This change merged.19:30
clarkbthats in which means we can now land the next change19:30
clarkb#link https://review.opendev.org/#/c/703488/ Update OpenDev docs with new Governance. Now we can merge this change.19:30
clarkbI've removed my WIP and will hit the +A button at the end of the meeting19:31
corvusi'm pretty sure we've all agreed to it in some form, but that could use some more infra-root +2s just for the record :)19:32
* fungi is relieved to see he hasn't forgotten to do that19:32
clarkbcorvus: ya I think most of us have acked it but then a new ps happened for depends on being updated19:32
clarkbfrickler: Shrews ^ I Think you may be the last missing active cores if you want to review it19:33
Shrewsyep, skimming now19:33
clarkbon the service side of things I don't think there have been any major changes in the last week19:34
clarkbanything to add re opendev or should we continue?19:34
*** jamesmcarthur has joined #openstack-meeting19:34
corvusare we talking about gerrit restart this meeting?19:35
clarkbcorvus: yes19:35
clarkbwas goign to lump that into the next topic since it was lsightly related to mordreds review container work19:35
corvusnow or later?19:35
clarkb#topic Update Config Management19:35
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:35
clarkbnow works :)19:35
fungigerrit restart!19:36
* fungi still plans to be on hand19:36
corvuswe're still on for friday the 20?  did we send announcements?19:36
clarkblast week we sort of penciled in friday 20th. I got very distracted and didn't send announcements19:36
corvusi have no conflicts on the 20th :)19:36
corvusor, like any time for the next 3 weeks :)19:36
mordredI still have no conflicts on the 20th19:36
clarkbI can send announcements today if we still think that is the plan19:37
clarkbmordred: ^ are things ready for that on the technical side of the house?19:37
fungiclarkb sounded like he had an appointment to drive a race car or something19:37
corvusyeah, i'd have liked to do an announcement earlier, but hopefully folks will be understanding19:37
mordredclarkb: no - not 100% - but, if they aren't, I don't think we should block on it (I'm still pretty confident they will be by friday)19:37
clarkbfungi: ya I think I've decided that I need the differently applied concentration that the road trip to arizona would have afforded19:37
corvusi think we should do it because the timing is really good19:37
clarkbmordred: gotcha so do the rename and not containers if necessary19:37
mordredyah. rename + containers if we're happy19:38
fungiall sounds fine to me19:38
clarkbin that case I can send announcements after the meeting to the various project lists as well as one for #openstack-infra19:38
corvusi'd really like to do the containers; what needs doing there?19:38
corvusreviews, or is there some mini-task i can help with?19:39
*** maciejjozefczyk has quit IRC19:39
clarkbmordred: ^19:40
mordredcorvus: I just need to do the manage-projects shift and not something else19:41
mordredcorvus: I'll definitely ping you for reviews when I've got the patch19:42
corvusmordred: k, lemme know if/how i can  help, thx19:42
mordredkk. will do19:42
clarkbis it reasonable to potentially say "project additions won't work" for a few days if that doesn't get done before firday?19:42
clarkbthen make that the next week's priority ?19:42
mordredmaybe - but I think it'll get done and be fine19:43
clarkbThe other config management topic was one I added under general topics but realized putting the agenda together on my local machine that we can cover here19:44
clarkbthe nb01/4.opendev.org rebuild19:44
clarkbwe've learned that docker and podman do behave differently at times19:44
clarkbsounds like that is causing us to shift towards docker for consistency19:44
clarkband long story short nb04.opendev.org will be a new server in the near future to avoid hostname conflicts19:45
clarkbianw: mordred ^ anything else to add to that?19:45
ianwnot really, yeah in progress ...19:45
mordredyeah. that covers it19:46
*** jamesmcarthur has quit IRC19:46
clarkb#topic General Topics19:46
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:46
*** jamesmcarthur has joined #openstack-meeting19:46
clarkbfungi: I don't suppose there are updates on the wiki puppetry?19:46
clarkb(based on earlier discussion I don't think so)19:46
mordredminor gitea bump: https://review.opendev.org/#/c/713517/19:47
fungisounds like the best update is that mnaser might try out the docker containers19:47
fungithe biggest challenges there will probably be making sure to cover openid integration and spam control/prevention19:47
*** jmasud has joined #openstack-meeting19:48
fungiwe have a ton of spam prevention mechanisms in place on the current deployment19:48
fungiand the openid extension is kinda finicky (i'm still struggling with it)19:48
fungibut no, i've made no new progress on it19:49
clarkbthats good input for anyone looking at alternative deployment methods19:49
clarkbianw: next up is static.o.o19:50
clarkbhave we cleaned up the bits that need cleaning up? and/or should we remove this topic at this point?19:50
clarkb(as a related side note, the goaccess report generation is working now with the longer timeouts)19:50
ianwno we haven't; maybe give me an action to do that in this week and we can stop discussing it next week19:50
ianw(cleanup static bits i mean)19:51
clarkb#action ianw cleanup static.openstack.org and files02.openstack.org resources that are no longer needed (now served by static.opendev.org)19:51
fungithat entire replacement effort has gone really, really, amazingly well19:51
clarkbwe've covered nb04.opendev.org and talked about gerrit downtime19:51
clarkboh I'll need to know a time window for email announcement19:52
clarkbI expect I'll not be around so will let someone who has volunteered give me a window :)19:52
mordredI'm free all day19:52
fungimy available hours are probably somewhere in the 13:00-00:00 utc range19:52
fungithough i can go later if needed, earlier is a bit of a caffeination risk19:53
corvusi'm generally up by, what... 1400 utc?19:53
clarkbshould we say 1500-1600 UTC then so that corvus can have breakfast?19:54
corvusif clarkb isn't aronud and i'm the latest, i'd say feel free to start at 1400 or even earlier, since i'm backup19:54
clarkbok 1400-1500 it is19:54
corvusbut if clarkb secretly wants us to start at 1500 so he can drop in if he feels like it, that's cool too :)19:55
clarkblets go 1400 then if I decide I want to be around that isn't too terrible for me19:55
clarkband gives me more time after to drive fake cars19:55
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
clarkbAnd now ~4 minutes for anything else19:55
fungiand now for something completely different19:56
fungiit's the toad elevating moment?19:56
fungiowl stretching time?19:56
AJaegerzuul-jobs repo has quite a lot of open reviews where I'm unsure, would appreciate if somebody could do a review round and push stuff forward or advise what should not go in or needs change19:56
clarkb#info zuul-jobs could use reviews19:57
fricklerweird last minute idea: would we want an #opendev-meeting channel, too?19:58
clarkbfrickler: I was thinking we might shift to doing the meeting in channel19:58
fricklerah, I don't like that19:58
clarkb(also the meeting name is channel independent so we can keep doing it here for a bit if necessary or try a few things and still have continuity of log collection)19:59
clarkband at some point call it opendev (and possibly do a file rename on the logs server)19:59
fungii guess there were two main reasons behind openstack's community having dedicated meeting channels... reduction in schedule overlap and it gets the meeting talk uot of the general discussion channel... the first doesn't really apply for us and teh second is a matter of personal taste19:59
clarkbfungi: ya I think the second would be the concern, frickler is that your concern?20:00
fricklerthe idea was that ppl might not like the openstack part of the name here20:00
clarkb(also we are at time but there is no meeting after us so can close this topic quickly)20:00
fricklerand also yes the latter20:00
fungia similar topic is what to do with #openstack-infra-incident20:00
fungibut we're out of time in here20:00
fungi(if this were in #opendev we could just keep going!)20:00
clarkbya I think we can create new channels for both of those in order to keep regular discussions in the main channel20:01
mnaserfwiw something that i noticed when doing in channel meetings is the bot spam gets picked up btw20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:01
openstackMeeting ended Tue Mar 17 20:01:11 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-17-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-17-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2020/infra.2020-03-17-19.01.log.html20:01
clarkbfungi has guilted me into letting you all eat $meal :)20:01
clarkbfeel free to continue the discussion in #opendev and thank you all for yout time20:01
*** Shrews has left #openstack-meeting20:02
*** AJaeger has left #openstack-meeting20:03
*** martial_ has joined #openstack-meeting20:04
*** martial_ is now known as martial20:05
martialWith a ton of people working mostly remotely lately, I do not know that we are having a Scientific SIG meeting today20:05
*** macz_ has joined #openstack-meeting20:06
*** macz_ has left #openstack-meeting20:06
*** jamesmcarthur has quit IRC20:08
*** jamesmcarthur has joined #openstack-meeting20:10
*** jamesmcarthur has quit IRC20:15
*** jamesmcarthur has joined #openstack-meeting20:16
*** ociuhandu has joined #openstack-meeting20:21
*** TrevorV has quit IRC20:25
*** trandles has joined #openstack-meeting20:33
*** jmasud has quit IRC20:55
*** jmasud has joined #openstack-meeting20:56
*** ociuhandu has quit IRC20:57
*** b1airo has joined #openstack-meeting21:00
trandlesHi b1airo meeting today?21:03
b1airohi trandles21:03
b1aironot sure actually, just jumping into Slack to see if we've discussed...21:03
*** jamesmcarthur has quit IRC21:04
b1airoquiet over there - will lurk for a while and see if anyone turns up21:05
b1airoyou being called into many contingency and service continuity meetings at the moment trandles ?21:05
trandlesI haven't seen official word but I have serious doubts about Vancouver PTG and ISC21:06
trandlesWe're all work from home for the time being21:06
trandlesNot even domestic work travel is allowed21:06
trandlesIf this all dies down over the summer we're going to be crushed with late year travel to make up for lost time21:07
b1airogetting it to die down anytime soon would take a much more consistent and coordinated global approach methinks21:07
*** oneswig has joined #openstack-meeting21:08
*** jamesmcarthur has joined #openstack-meeting21:08
oneswigsorry, trouble at mill21:08
b1airo#startmeeting scientific-sig21:10
openstackMeeting started Tue Mar 17 21:10:06 2020 UTC and is due to finish in 60 minutes.  The chair is b1airo. Information about MeetBot at http://wiki.debian.org/MeetBot.21:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:10
*** openstack changes topic to " (Meeting topic: scientific-sig)"21:10
openstackThe meeting name has been set to 'scientific_sig'21:10
b1airo#chair oneswig21:10
openstackCurrent chairs: b1airo oneswig21:10
oneswigwhat's new?21:10
b1airowhole team wfh test today21:10
*** trandles_ has joined #openstack-meeting21:11
oneswigBeen doing it ourselves too.21:11
*** trandles has quit IRC21:11
trandles_Well, my VPN connection to work dropped, sorry about that21:11
trandles_Too many working from home I guess21:11
b1airoother than that, not much. trying to psych myself to dive into our old Bright OpenStack private cloud again this week if i can find some time21:11
b1airoyour VPN takes default gateway i take trandles_ ?21:12
b1airoyour VPN takes default gateway i take it trandles_ ?21:12
trandles_Everything routes through the VPN when connected21:12
trandles_It was surprisingly stable until just now21:13
*** jamesmcarthur has quit IRC21:13
oneswigThe full WFH impact hasn't hit as schools remain open here.21:13
trandles_Schools closed here Monday for 3 weeks21:14
*** ociuhandu has joined #openstack-meeting21:14
trandles_So no definitive word on Vancouver?21:15
oneswigQuick q: does anyone know how atomic ceph rbd snapshots are?  If a volume is active when the snapshot is made, how coherent is the snapshot?21:15
oneswigtrandles_: not seen anything myself but not paid much attention either.21:16
b1airooneswig: they are atomic from the perspective of the block device, i.e., all blocks are snapshot at same time - whether any filesystems atop that device are consistent at that point in time is a different question/issue though21:20
b1airoi imagine there are some potential caveats there if you're cross-mounting a single rbd though21:21
oneswigOK thanks b1airo, good to know21:22
b1airoany cephfs fun to report?21:23
b1airoalso, anyone used dc/os aka mesosphere?21:24
oneswigNothing recently on CephFS.21:24
oneswigb1airo: Nick Jones (formerly of our team) joined D2IQ, formerly Mesosphere.  But I think he's working on Kubernetes.21:25
trandles_b1airo, I hear rumors that someone in LANL HPC is doing some work with DC/OS but it's not me and I don't know too awful much21:25
trandles_I had a summer student do an evaluation of it but it was in 2016 so I'm sure it bears little resemblance to recent DC/OS21:26
*** dtroyer has quit IRC21:26
b1airocheers. in the rebranding process they seem to have moved "mesosphere" from company name to product line ("ksphere" being a newer line of business)21:26
*** dtroyer has joined #openstack-meeting21:27
*** dtroyer has left #openstack-meeting21:27
b1airoone of my teams is using it in dev/test and we're trying to figure out what makes most sense for prod, e.g., keep using dc/os, just do vanilla k8s, konvoy, something else entirely...21:28
b1airoMagnum would be another possibility if we had Bright under control enough to deploy it21:28
*** enriquetaso has quit IRC21:29
*** enriquetaso has joined #openstack-meeting21:30
oneswigThe recent experience we've had with Magnum is that the version of Kubernetes deployed is tied to the version of Magnum (which releases more slowly).  That can be a problem if, shameless neophyte that you are, you want to always run the latest version of k8s and hang the portability.21:31
*** rcernin has joined #openstack-meeting21:31
b1airowould really like to have one container/service orchestration platform that we can use for hosting our own and end-user's services21:31
oneswigI think they might be looking to decouple that more, to everyone's benefit21:31
oneswigWe certainly like using Magnum for that, noting this limitation that you're often a version or two behind on k8s21:32
b1airoyeah, sounds like a prerequisite oneswig21:32
b1airoCray's original Urika tools had this issue and were dead in the water due to it21:33
*** enriquetaso has quit IRC21:34
oneswigI think their issues were far more severe than that.21:35
*** jamesmcarthur has joined #openstack-meeting21:35
b1airoi was being kinder than usual21:35
oneswigtrandles_: how's the first months of OSA going?21:36
trandles_It's been...rewarding?21:36
trandles_When it just works it's great. When something breaks and you can figure out WTF is going on it feels like you've accomplished something.  ;)21:37
*** rcernin has quit IRC21:37
*** rcernin has joined #openstack-meeting21:38
trandles_To be fair almost ALL of the issues I have had are either self-inflicted, a gap in documentation, or due to the gnocchi fiasco.21:38
trandles_I think the benefits of OSA greatly outweigh the challenges I've encountered. I'm also super happy with using LXC for the service containers.21:39
oneswigInteresting - and I don't think your issues are unique to OSA by any means.21:39
trandles_LXC is certainly more lightweight than docker. It's rock-solid stable, survives reboots easily, etc. I had a filesystem fill on one of my two controller testbeds last week and debugging the mess it created was fairly easy with everything in LXC.21:41
*** jamesmcarthur has quit IRC21:41
oneswigDoes it still use bridge networking, or is it host networking?21:43
oneswigFor a while early on I remember we deployed Monasca in LXC containers and it didn't make the host feel rock solid.  That was a few years ago now though.21:45
*** jamesmcarthur has joined #openstack-meeting21:45
trandles_That's the reference for what I deployed on the testbed. We're reviewing it for all of our needs now and seeing what we're going to modify for the larger production cloud.21:45
trandles_When I say "we" I mean with one of our network architects who knows how everything we need to interface without outside of the cloud is put together and a security guy21:46
*** ociuhandu has quit IRC21:46
trandles_We're also using the testbed to convince program that it's worth their money to buy storage appliances and good network gear to offload as much as we can.21:48
oneswigIs it also Linuxbridge networking for tenant overlay networking?21:48
trandles_It's linuxbridge now, yes21:48
oneswigAll the more surprising that there was a plan to deprecate that.21:49
trandles_Networking is the one place where we'll probably end up writing a good bit of our own ansible to get what we actually need.21:49
trandles_But that's not surprising21:49
*** jamesmcarthur has quit IRC21:49
*** jamesmcarthur has joined #openstack-meeting21:50
oneswigtrandles_: will you document/present your networking changes, are they generic for a high-security environment or specific to your place?21:51
trandles_I might be able to. An example is everywhere our production clusters interface with the backend network (license servers, all filesystems, etc.) we are going from the cluster fabric to IB (IPoIB) and running quagga/zebra for OSPF.21:53
trandles_It's pretty specific to our setup and might be changing soon...but that's outside of my control and a large part of why I'm working closely with one of our network gurus to get this right before we actually deploy21:53
oneswigmakes sense, I think.21:55
trandles_I'm not sure it makes sense any more. A lot of this was a product of wanting insane bandwidth and having a crazily parallel backbone to get it. Paths all over the place, incredibly difficult to debug. Now we can buy 100gig commodity hardware.21:57
trandles_It has me kinda dragging my feet a little bit knowing that it's likely to be a lot simpler soon.21:58
oneswigWill it though - surely the clients will just want more of that?21:59
oneswigWe are at the hour - final comments?22:00
trandles_It's the same problem we've always had. Make the network faster and simpler and now we need a better filesystem. ;)22:00
oneswigRight, move the bottleneck!22:00
*** ociuhandu has joined #openstack-meeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:01
openstackMeeting ended Tue Mar 17 22:01:39 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-17-21.10.html22:01
oneswigThanks all22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-17-21.10.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-03-17-21.10.log.html22:01
trandles_Later, stay healthy :D22:01
b1airosorry oneswig trandles_ - i got pulled into a Zoom22:04
b1airosee you later!22:04
*** ociuhandu has quit IRC22:06
*** trandles_ has quit IRC22:17
*** e0ne has quit IRC22:18
*** mattw4 has joined #openstack-meeting22:24
*** mattw4 has quit IRC22:25
*** mattw4 has joined #openstack-meeting22:25
*** mattw4 has quit IRC22:25
*** slaweq has quit IRC22:39
*** bbowen has quit IRC22:45
*** bbowen has joined #openstack-meeting22:45
*** raildo has quit IRC22:46
*** slaweq has joined #openstack-meeting22:50
*** slaweq has quit IRC22:54
*** jamesmcarthur has quit IRC22:56
*** jamesmcarthur has joined #openstack-meeting22:59
*** macz_ has joined #openstack-meeting23:02
*** oneswig has quit IRC23:09
*** macz_ has quit IRC23:16
*** e0ne has joined #openstack-meeting23:30
*** e0ne has quit IRC23:31
*** takahashi-tsc has quit IRC23:35
*** jamesmcarthur has quit IRC23:44
*** jamesmcarthur has joined #openstack-meeting23:46
*** jamesmcarthur has quit IRC23:51
*** ijw has quit IRC23:55

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