Wednesday, 2020-05-06

*** ttsiouts has joined #openstack-meeting00:00
*** brinzhang has joined #openstack-meeting00:03
*** jmasud has joined #openstack-meeting00:07
*** ttsiouts has quit IRC00:33
*** rfolco has quit IRC00:35
*** jamesmcarthur has joined #openstack-meeting00:37
*** larainema has joined #openstack-meeting00:42
*** _mlavalle_1 has quit IRC01:10
*** jamesmcarthur has quit IRC01:17
*** jmasud has quit IRC01:17
*** jmasud has joined #openstack-meeting01:39
*** gary_perkins has quit IRC01:40
*** hyunsikyang has joined #openstack-meeting01:52
*** hyunsikyang has quit IRC01:52
*** hyunsikyang__ has quit IRC01:52
*** hyunsikyang has joined #openstack-meeting01:52
*** Liang__ has joined #openstack-meeting01:54
*** ociuhandu has joined #openstack-meeting01:57
*** tetsuro has joined #openstack-meeting02:00
*** yasufum has joined #openstack-meeting02:01
*** hyunsikyang has quit IRC02:01
*** hyunsikyang has joined #openstack-meeting02:01
*** ociuhandu has quit IRC02:02
*** hyunsikyang has quit IRC02:02
*** hyunsikyang has joined #openstack-meeting02:02
*** jmasud has quit IRC02:11
*** yasufum has quit IRC02:18
*** hyunsikyang__ has joined #openstack-meeting02:20
*** hyunsikyang has quit IRC02:24
*** ttsiouts has joined #openstack-meeting02:30
*** yasufum has joined #openstack-meeting02:31
*** yasufum has quit IRC02:32
*** jamesmcarthur has joined #openstack-meeting02:33
*** tetsuro has quit IRC02:37
*** ttsiouts has quit IRC02:39
*** ttsiouts has joined #openstack-meeting02:39
*** luyao has joined #openstack-meeting02:49
*** jmasud has joined #openstack-meeting02:49
*** vishalmanchanda has joined #openstack-meeting03:03
*** baojg has joined #openstack-meeting03:03
*** ykatabam has joined #openstack-meeting03:03
*** ttsiouts has quit IRC03:04
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur has joined #openstack-meeting03:06
*** tetsuro has joined #openstack-meeting03:06
*** jamesmcarthur has quit IRC03:11
*** yasufum has joined #openstack-meeting03:14
*** tetsuro has quit IRC03:16
*** jmasud has quit IRC03:16
*** baojg has quit IRC03:18
*** tetsuro has joined #openstack-meeting03:22
*** yasufum has quit IRC03:26
*** psachin has joined #openstack-meeting03:36
*** jamesmcarthur has joined #openstack-meeting03:41
*** gary_perkins has joined #openstack-meeting03:45
*** tetsuro has quit IRC03:45
*** tetsuro has joined #openstack-meeting03:47
*** tetsuro has quit IRC03:54
*** rh-jelabarre has quit IRC04:02
*** openstack has joined #openstack-meeting04:21
*** ChanServ sets mode: +o openstack04:21
*** hyunsikyang has joined #openstack-meeting04:24
*** hyunsikyang__ has quit IRC04:28
*** hyunsikyang__ has joined #openstack-meeting04:29
*** hyunsikyang has quit IRC04:30
*** tetsuro has joined #openstack-meeting04:34
*** evrardjp has quit IRC04:35
*** evrardjp has joined #openstack-meeting04:36
*** gyee has quit IRC04:40
*** jmasud has joined #openstack-meeting05:00
*** ttsiouts has joined #openstack-meeting05:01
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #openstack-meeting05:05
*** jamesmcarthur has quit IRC05:11
*** jamesmcarthur has joined #openstack-meeting05:11
*** tetsuro has quit IRC05:25
*** tetsuro has joined #openstack-meeting05:27
*** ttsiouts has quit IRC05:33
*** cgoncalves has joined #openstack-meeting05:38
*** tetsuro has quit IRC05:43
*** tetsuro has joined #openstack-meeting05:44
*** ysandeep|away is now known as ysandeep05:51
*** diablo_rojo has quit IRC05:57
*** jamesmcarthur has quit IRC06:00
*** jamesmcarthur has joined #openstack-meeting06:01
*** ociuhandu has joined #openstack-meeting06:01
*** jamesmcarthur has quit IRC06:06
*** ociuhandu has quit IRC06:09
*** tetsuro has quit IRC06:09
*** tetsuro has joined #openstack-meeting06:10
*** ysandeep is now known as ysandeep|away06:12
*** tetsuro has quit IRC06:15
*** jmasud has quit IRC06:17
*** yamamoto has joined #openstack-meeting06:18
*** jmasud has joined #openstack-meeting06:19
*** yamamoto has quit IRC06:24
*** ysandeep|away has quit IRC06:29
*** ociuhandu has joined #openstack-meeting06:39
*** rubasov has quit IRC06:39
*** rubasov has joined #openstack-meeting06:39
*** jamesmcarthur has joined #openstack-meeting06:39
*** ralonsoh has joined #openstack-meeting06:45
*** tetsuro has joined #openstack-meeting06:49
*** tetsuro has quit IRC06:50
*** tetsuro has joined #openstack-meeting06:50
*** jmasud has quit IRC06:51
*** maciejjozefczyk has joined #openstack-meeting06:52
*** belmoreira has joined #openstack-meeting06:53
*** jmasud has joined #openstack-meeting06:55
*** slaweq has joined #openstack-meeting06:56
*** ociuhandu has quit IRC07:00
*** ttsiouts has joined #openstack-meeting07:04
*** jmasud has quit IRC07:14
*** ykatabam has quit IRC07:17
*** jmasud has joined #openstack-meeting07:19
*** lpetrut has joined #openstack-meeting07:19
*** witek has joined #openstack-meeting07:25
*** rpittau|afk is now known as rpittau07:31
*** cgoncalves has quit IRC07:34
*** cgoncalves has joined #openstack-meeting07:40
*** jmasud has quit IRC07:40
*** openstack has joined #openstack-meeting07:47
*** ChanServ sets mode: +o openstack07:47
*** yasufum has joined #openstack-meeting07:52
*** dmellado has quit IRC07:58
*** dmellado has joined #openstack-meeting08:04
*** ttsiouts has quit IRC08:07
*** ttsiouts has joined #openstack-meeting08:07
*** yasufum has quit IRC08:19
*** ociuhandu has quit IRC08:20
*** tetsuro has quit IRC08:26
*** tetsuro has joined #openstack-meeting08:26
*** larainema has quit IRC08:30
*** e0ne has joined #openstack-meeting08:30
*** ociuhandu has joined #openstack-meeting08:34
*** yasufum has joined #openstack-meeting08:37
*** baojg has joined #openstack-meeting08:40
*** jamesmcarthur has quit IRC08:41
*** tetsuro has quit IRC08:46
*** yasufum has quit IRC08:56
*** strigazi has joined #openstack-meeting09:00
*** jmasud has quit IRC09:02
*** tetsuro has joined #openstack-meeting09:15
*** jamesmcarthur has joined #openstack-meeting09:16
*** Liang__ has quit IRC09:24
*** jamesmcarthur has quit IRC09:26
*** rpittau is now known as rpittau|bbl09:44
*** dklyle has quit IRC09:45
*** tetsuro has quit IRC09:54
*** jamesmcarthur has joined #openstack-meeting09:57
*** ttsiouts has quit IRC09:58
*** ttsiouts has joined #openstack-meeting09:59
*** tetsuro has joined #openstack-meeting10:00
*** jamesmcarthur has quit IRC10:07
*** tetsuro has quit IRC10:12
*** tetsuro has joined #openstack-meeting10:15
*** tetsuro has quit IRC10:16
*** baojg has quit IRC10:18
*** tetsuro has joined #openstack-meeting10:18
*** ttsiouts has quit IRC10:27
*** ttsiouts has joined #openstack-meeting10:30
*** tetsuro has quit IRC10:36
*** jamesmcarthur has joined #openstack-meeting10:43
*** jamesmcarthur has quit IRC10:43
*** jamesmcarthur has joined #openstack-meeting10:43
*** maciejjozefczyk_ has joined #openstack-meeting10:43
*** jamesmcarthur has quit IRC10:44
*** maciejjozefczyk has quit IRC10:44
*** jamesmcarthur has joined #openstack-meeting10:44
*** maciejjozefczyk has joined #openstack-meeting10:44
*** tetsuro has joined #openstack-meeting10:48
*** ttsiouts has quit IRC10:48
*** maciejjozefczyk_ has quit IRC10:48
*** maciejjozefczyk_ has joined #openstack-meeting10:49
*** ykatabam has joined #openstack-meeting10:49
*** maciejjozefczyk has quit IRC10:50
*** maciejjozefczyk has joined #openstack-meeting10:50
*** jamesmcarthur has quit IRC10:51
*** janders has joined #openstack-meeting10:51
*** maciejjozefczyk_ has quit IRC10:53
*** maciejjozefczyk_ has joined #openstack-meeting10:55
*** maciejjozefczyk has quit IRC10:55
*** dh3 has joined #openstack-meeting10:57
*** jamesmcarthur has joined #openstack-meeting10:58
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #openstack-meeting10:59
*** tetsuro has quit IRC11:00
*** jamesmcarthur has quit IRC11:01
*** oneswig_ has joined #openstack-meeting11:01
oneswig_#startmeeting scientific-sig11:01
openstackMeeting started Wed May  6 11:01:55 2020 UTC and is due to finish in 60 minutes.  The chair is oneswig_. Information about MeetBot at http://wiki.debian.org/MeetBot.11:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:01
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:01
openstackThe meeting name has been set to 'scientific_sig'11:01
*** jamesmcarthur has joined #openstack-meeting11:02
jandersgday all11:02
oneswig_Hi janders ahem sorry I'm late :-)11:02
janders:)11:03
oneswig_what's new?11:03
jandersnot much11:03
dh3openmpi/mpi4py (new to me at least) - not openstack related though11:03
janderssome interesting attempts to use secgroups the other way round11:03
*** priteau has joined #openstack-meeting11:04
oneswig_mpi4py always seemed like a curious combination11:04
janders(restricting egress with negative matching)11:04
jandersended up putting some extra private subnets and routers in instead11:04
*** maciejjozefczyk_ has quit IRC11:04
jandersbut apparently secgroups cant be used to allow a VM to ping everything except something (e.g. local network)11:05
*** maciejjozefczyk_ has joined #openstack-meeting11:05
oneswig_janders: had an interesting issue with secgroups the other day.  A VM with allowed_address_pairs to relax what IPs and MACs can be transmitted, also disables security groups.11:06
*** jamesmcarthur has quit IRC11:07
jandersinteresting feature11:07
jandersa little scary though11:07
jandersreminds me of a stuff up at one of AUS OpenStack operators back in nova-network days11:08
jandersa puppet bug caused iptables flush cluster wide... while computes were on public IPs11:08
jandersa bit of guessing and attacker can get console access to VMS11:08
oneswig_yikes!11:09
jandersquick rd.break and the floodgates are open11:09
jandersyeah11:09
jandersaccidental disabling of iptables ain't fun11:09
*** vkmc has quit IRC11:09
oneswig_could they remember all the rules to put back :-)11:10
jandersi think the degree of compromise was large enough to sanction mass rebuild of stuff11:10
oneswig_janders: on a different subject, have you contributed a case study to the OSF bare metal white paper?11:11
jandersworking on it11:11
jandersgetting close11:11
oneswig_same here...11:11
jandersissue is its a little too long11:11
janderscutting bits out before I can merge back11:11
oneswig_there's an upper limit on length?11:11
jandersgood problem to have i suppose11:11
jandersi dont think there's a specifc word count etc... mine had a fair bit of detail, code listings, etc11:12
jandersthat needs to go11:12
oneswig_ah right.  I wasn't sure on embedding config myself11:12
*** ociuhandu has quit IRC11:13
*** ociuhandu has joined #openstack-meeting11:14
oneswig_On an administrative point11:14
oneswig_#link Virtual PTG registration open https://www.eventbrite.com/e/virtual-project-teams-gathering-june-2020-tickets-10345699666211:14
priteauOpenDev registration as well11:15
oneswig_Hi priteau, thanks :-)11:15
priteau#link https://www.eventbrite.com/e/opendev-large-scale-usage-of-open-infrastructure-software-registration-10289971983211:15
jandersdone!11:16
jandersit's free - great!11:16
dh3likewise, this morning :)11:17
oneswig_Are they at the same time, how does that work again?11:17
oneswig_ah, no, they are a few weeks apart.  I should read up11:19
*** ociuhandu has quit IRC11:19
oneswig_Now registered for both.11:20
oneswig_Last week's discussion on Open Infra Labs was an interesting one.  Seeing Adjutant in the list of PTG projects reminded me they use that for user onboarding.11:21
oneswig_I'd not heard of it before.11:22
janders(googling)11:22
janderssounds a bit like my bunch of ansible used for onboarding11:22
jandersor maybe im wrong11:24
oneswig_Right - I wasn't sure what it looks like to use.11:24
dh3looks like it exposes some user self-service panels to Horizon too. We are using Cloudforms/ManageIQ for that11:24
*** tetsuro has joined #openstack-meeting11:24
*** ttsiouts has joined #openstack-meeting11:25
janderswhats your feel around the next summit - will it be physical or virtual>11:25
janderss/>/?11:25
oneswig_Berlin in October?  I wonder11:26
witekOctoberfest in Sep has been canceled, but that's not exactly similar size11:26
oneswig_I expect there will be a split: people keen to travel and others anxious to stay at home.  It sounds like Germany is slowly relaxing its lockdown.  I'm doubtful the US will be in a good spot by then though.11:27
oneswig_Hi witek :-)11:27
witekhi11:27
oneswig_If there's a physical summit at all, perhaps it would be hundreds of attendees, not thousands.11:28
jandersright11:28
jandersat this stage it looks like we won't be allowed out of the country even if we wanted11:28
jandersbut at least I got full refunds for OpenDev/PTG and ISC no worries11:29
janders*flight refunds11:29
*** ttsiouts has quit IRC11:30
oneswig_Flight refunds - interesting.  I heard a European budget airline, all the refunds team are "currently not working due to coronavirus" - but the teams for rebooking are available to process your request! :-)11:30
*** rfolco has joined #openstack-meeting11:30
jandersQantas seemed to have a "system issue" which caused all cancellations to be turned into flight credits not refunds11:31
jandersbut that was easy to fix with a little nagging11:31
dh3priorities...! we/Sanger went "no business travel" weeks before lockdown so I expect they will be cautious11:31
*** ttsiouts has joined #openstack-meeting11:32
jandersmuch business travel turned into budget travel after 911 & GFC11:32
jandersI wonder if this will go a step further and turn into videoconferencing instead11:33
oneswig_It's an interesting point as opinion on travelling will have a large amount of subjective disposition to risk11:33
jandersin many cases that wouldn't be a bad thing11:33
oneswig_If I had a fitbit, my daily step count these days would be ~100...11:34
dh3depends on the videoconf platform I think... I bailed from one virtual conference because they used AdobeConnect and it was too unreliable (audio dropping, screen shares failing)11:34
oneswig_AdobeConnect - not heard of that.  Everyone has a pet hate I think.  Skype for Business never feels like fun.11:34
jandersdont get me started on webex11:35
jandersteams is probably the least bad microsoft product on the market though11:35
oneswig_Can you tell which platforms are built on OpenStack?11:35
oneswig_janders: teams, I have a name for my pain.11:36
*** ociuhandu has joined #openstack-meeting11:36
jandersits the least bad tool we use here11:36
jandersi deliberately dont use any reference to "good" or "better" though :P11:37
*** raildo has joined #openstack-meeting11:37
*** witek has quit IRC11:39
*** yamamoto has joined #openstack-meeting11:40
*** witek has joined #openstack-meeting11:40
*** jamesmcarthur has joined #openstack-meeting11:40
*** ociuhandu has quit IRC11:41
oneswig_janders: got the VFLAG stuff working better.11:41
jandersgreat!11:41
jandersso - does it provide performance+redundancy?11:41
oneswig_Upgrade to OVS 2.12 should have been redeploy - I think there were DB schema migration issues.11:41
janderswhat's the aggregate bandwidth?11:41
*** yamamoto has quit IRC11:42
oneswig_Redundancy I haven't checked, performance is good but I only have it as an aggregate of clients on 5 hypervisors so far.11:42
oneswig_I'm planning to get some meaningful data this afternoon, will put a graph on the SIG Slack channel if it's sufficiently pretty11:42
jandersi have no updates on my cx6-ovs issues11:42
oneswig_That's been a long-running issue for you11:43
jandersmlnx are doing some testing in the lab to see if it is a generic bug or sth to do with my setup11:43
jandersyeah11:43
janderswe have some workarounds though11:43
jandersbut overall vpi-eth-cx6 wasnt smooth sailing11:43
janderscx6-ib - no worries11:43
jandersbut overall i dont really see a point... for eth cx5 is more than sufficient11:44
jandersnext stop pcie4/5 and 400GE I suppose11:44
oneswig_I think there are some ipsec offloads in CX6 I was interested in testing.11:45
jandersfor ib it does make sense esp for storage11:45
jandersits very very nice11:45
oneswig_Also the NVMEoF support, I think there was something neat it did with presentation of VFs?11:45
jandersthat is possible11:45
oneswig_not much help if it fails on the "basics" though11:46
janderspcie4 cx6-eth might be more smooth11:46
jandersi sense that hacks around pcie3 limitations dont mix with ethernet all that well11:46
jandersbut - will know for sure when we have full explanation of the ovs issues11:46
jandersand a fix11:46
oneswig_janders: are you a Cumulus customer?11:48
jandersnot really11:48
jandersits a little funny actually11:48
jandersi ended up with some cumulus switches for.... ipmi11:49
jandersbut not using any SDN stuff there11:49
jandersjust dumb switches11:49
jandersas in they are used as dumb switches11:49
oneswig_I wonder what it's prognosis is as an open net os.  I suspect vendors like Dell will take a dim view11:49
oneswig_I don't have anything more to add - janders?11:52
jandersi think im good11:52
jandersthank you all - and stay safe11:52
janderstill next time11:52
oneswig_It must be late in canberra...11:52
janders215211:52
oneswig_Until next time!11:52
oneswig_#endmeeting11:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"11:53
openstackMeeting ended Wed May  6 11:53:03 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)11:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-05-06-11.01.html11:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-05-06-11.01.txt11:53
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-05-06-11.01.log.html11:53
dh3bye!11:53
*** dh3 has quit IRC11:53
*** janders has quit IRC11:53
oneswig_cheerio!11:53
*** oneswig_ has quit IRC11:53
*** andrebeltrami has joined #openstack-meeting12:01
*** rh-jelabarre has joined #openstack-meeting12:02
*** rh-jelabarre has quit IRC12:02
*** rh-jelabarre has joined #openstack-meeting12:03
*** ykatabam has quit IRC12:09
*** rpittau|bbl is now known as rpittau12:18
*** ykatabam has joined #openstack-meeting12:19
*** ociuhandu has joined #openstack-meeting12:25
*** jamesmcarthur has quit IRC12:25
*** ykatabam has quit IRC12:37
*** ykatabam has joined #openstack-meeting12:37
*** tetsuro has quit IRC12:41
*** vkmc__ has joined #openstack-meeting12:50
*** vkmc__ is now known as vkmc12:52
*** hyunsikyang has joined #openstack-meeting12:58
*** jamesmcarthur has joined #openstack-meeting13:01
*** hyunsikyang__ has quit IRC13:02
*** ralonsoh has quit IRC13:08
*** ralonsoh has joined #openstack-meeting13:11
*** rfolco is now known as rfolco|rover13:13
*** eharney has joined #openstack-meeting13:17
*** moguimar has joined #openstack-meeting13:18
*** cgoncalves has quit IRC13:19
*** jamesmcarthur has quit IRC13:21
*** cgoncalves has joined #openstack-meeting13:25
*** ykatabam has quit IRC13:30
*** TrevorV has joined #openstack-meeting13:31
*** dmacpher has joined #openstack-meeting13:33
*** maciejjozefczyk_ is now known as maciejjozefczyk13:37
*** ttsiouts has quit IRC13:39
*** dmacpher_ has joined #openstack-meeting13:39
*** dmacpher has quit IRC13:41
*** ykatabam has joined #openstack-meeting13:53
*** LiangFang has joined #openstack-meeting13:59
*** dmacpher__ has joined #openstack-meeting14:00
*** jamesmcarthur has joined #openstack-meeting14:01
*** dmacpher_ has quit IRC14:03
*** ttsiouts has joined #openstack-meeting14:08
*** ttsiouts has quit IRC14:13
*** ociuhandu has quit IRC14:15
*** ykatabam has quit IRC14:16
*** ociuhandu has joined #openstack-meeting14:16
*** ociuhandu has quit IRC14:20
*** ttsiouts has joined #openstack-meeting14:22
*** jamesmcarthur has quit IRC14:22
*** jhesketh has quit IRC14:22
*** ociuhandu has joined #openstack-meeting14:24
*** belmoreira has quit IRC14:25
*** munimeha1 has joined #openstack-meeting14:28
*** lpetrut has quit IRC14:30
*** ttsiouts has quit IRC14:38
*** belmoreira has joined #openstack-meeting14:44
*** dmacpher__ has quit IRC14:45
*** dklyle has joined #openstack-meeting14:48
*** mlavalle has joined #openstack-meeting14:49
*** dmacpher has joined #openstack-meeting14:49
*** jhesketh has joined #openstack-meeting14:51
*** belmoreira has quit IRC14:54
*** belmoreira has joined #openstack-meeting14:56
*** smcginnis has quit IRC14:58
*** lpetrut has joined #openstack-meeting15:00
*** smcginnis has joined #openstack-meeting15:04
*** belmoreira has quit IRC15:11
*** ttsiouts has joined #openstack-meeting15:13
*** ociuhandu has quit IRC15:13
*** ociuhandu has joined #openstack-meeting15:14
*** ociuhandu has quit IRC15:16
*** ociuhandu has joined #openstack-meeting15:16
*** LiangFang has quit IRC15:18
*** ttsiouts has quit IRC15:18
*** belmoreira has joined #openstack-meeting15:23
*** yasufum has joined #openstack-meeting15:30
*** njohnston is now known as njohnston_15:31
*** njohnsto_ has joined #openstack-meeting15:31
*** njohnsto_ is now known as njohnston15:35
*** belmoreira has quit IRC15:36
*** belmoreira has joined #openstack-meeting15:39
*** jmasud has joined #openstack-meeting15:41
*** dmacpher has quit IRC15:49
*** ociuhandu has quit IRC15:50
*** ociuhandu has joined #openstack-meeting15:51
*** dmacpher has joined #openstack-meeting15:51
*** gyee has joined #openstack-meeting15:53
*** jmasud has quit IRC15:55
*** ociuhandu has quit IRC15:56
*** maciejjozefczyk has quit IRC16:01
*** njohnston has quit IRC16:01
*** ociuhandu has joined #openstack-meeting16:01
*** jmasud has joined #openstack-meeting16:04
*** ttsiouts has joined #openstack-meeting16:05
*** maciejjozefczyk has joined #openstack-meeting16:06
*** maciejjozefczyk_ has joined #openstack-meeting16:07
*** witek has quit IRC16:08
*** maciejjozefczyk has quit IRC16:11
*** ociuhandu has quit IRC16:13
*** ociuhandu has joined #openstack-meeting16:14
*** ociuhandu has quit IRC16:19
*** jamesmcarthur has joined #openstack-meeting16:20
*** jmasud has quit IRC16:21
*** jmasud has joined #openstack-meeting16:23
*** ttsiouts has quit IRC16:23
*** jmasud has quit IRC16:23
*** rpittau is now known as rpittau|afk16:24
*** priteau has quit IRC16:25
*** ociuhandu has joined #openstack-meeting16:33
*** evrardjp has quit IRC16:36
*** evrardjp has joined #openstack-meeting16:36
*** ttsiouts has joined #openstack-meeting16:41
*** psachin has quit IRC16:41
*** ttsiouts has quit IRC16:51
*** jamesmcarthur has quit IRC16:55
*** witek has joined #openstack-meeting16:57
*** maciejjozefczyk has joined #openstack-meeting17:18
*** maciejjozefczyk_ has quit IRC17:20
*** irclogbot_0 has quit IRC17:20
*** maciejjozefczyk has quit IRC17:21
*** maciejjozefczyk has joined #openstack-meeting17:21
*** jamesmcarthur has joined #openstack-meeting17:21
*** maciejjozefczyk_ has joined #openstack-meeting17:22
*** irclogbot_0 has joined #openstack-meeting17:23
*** maciejjozefczyk_ has quit IRC17:23
*** ociuhandu has quit IRC17:26
*** maciejjozefczyk has quit IRC17:26
*** jamesmcarthur has quit IRC17:37
*** jamesmcarthur has joined #openstack-meeting17:38
*** ociuhandu has joined #openstack-meeting17:38
*** ociuhandu has quit IRC17:43
*** ttsiouts has joined #openstack-meeting17:45
*** ttsiouts has quit IRC17:49
*** ociuhandu has joined #openstack-meeting18:02
*** witek has quit IRC18:12
*** yasufum has quit IRC18:19
*** ralonsoh has quit IRC18:19
*** lpetrut has quit IRC18:22
*** e0ne has quit IRC18:34
*** bbowen has quit IRC18:41
*** bbowen has joined #openstack-meeting18:44
*** ociuhandu has quit IRC18:48
*** JangwonLee has quit IRC18:57
*** JangwonLee has joined #openstack-meeting18:58
*** jmasud has joined #openstack-meeting19:04
*** jmasud has quit IRC19:18
*** jamesmcarthur has quit IRC19:25
*** jamesmcarthur has joined #openstack-meeting19:30
*** jamesdenton has quit IRC19:48
*** ociuhandu has joined #openstack-meeting19:53
*** ayoung has joined #openstack-meeting19:54
*** belmoreira has quit IRC19:58
*** jamesdenton has joined #openstack-meeting20:04
*** jamesden_ has joined #openstack-meeting20:08
*** belmoreira has joined #openstack-meeting20:10
*** jamesdenton has quit IRC20:11
*** diablo_rojo has joined #openstack-meeting20:13
*** ociuhandu has quit IRC20:13
*** jamesdenton has joined #openstack-meeting20:21
*** jamesden_ has quit IRC20:22
*** belmoreira has quit IRC20:25
*** ociuhandu has joined #openstack-meeting20:46
*** jamesmcarthur has quit IRC20:50
*** ayoung has quit IRC20:51
*** jamesmcarthur has joined #openstack-meeting20:51
*** ociuhandu has quit IRC20:54
*** patchbot has joined #openstack-meeting20:54
*** ayoung has joined #openstack-meeting20:55
timburke#startmeeting swift21:00
openstackMeeting started Wed May  6 21:00:05 2020 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
seongsoochoo/21:00
rledisezhi o/21:00
kota_hi21:00
mattoliverauo/21:00
alecuyero/21:01
claygo/21:01
timburkeagenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke#topic PTG21:02
*** openstack changes topic to "PTG (Meeting topic: swift)"21:02
timburkemattoliverau very graciously offered to help with PTG planning/organization21:02
clayg❤️ mattoliverau21:03
mattoliverauhey cool.21:03
timburkemattoliverau, what have you learned?21:03
mattoliverauSo we need to get the registraion in and start putting in sessions to times21:03
mattoliverausorry, irc is lagging21:04
mattoliverauSo step 1, to get the registration in, I need to know if there are any other projects your interested in so we can try and avoid overlap21:04
mattoliverauI already have storelets and first contact sig21:04
rledisezI would be interested in Keystone (things like operator feedbacks etc…)21:05
mattoliverauNext we need to know what time suits people because of timezones. For this I'll come up with a doodle poll and post the link in our channel.21:05
mattoliveraurledisez: great!21:06
mattoliverauI'll hold the doodle pool, once I've created it, open until the end of Friday (my time, though can wait a bit longer) just so people have a change to pick times.21:07
mattoliverauI'm guessing meeting time isn't bad, but I'm happy to get up early or stay up late if need be.21:07
timburkei'm feeling the same way -- my current plan is to just show up in irc as much as possible that week :-D21:08
kota_yup. in the day time, it might be hard because kids interrupt me always.21:08
mattoliverauBut step 3, is to make sure all the topics you want to talk about is in the etherpad! So when we have times we can decide the number of blocks and get rooms booked.21:09
kota_oic21:09
mattoliveraumost of this I think happens by the 10th, though this could just be the registration side.21:09
timburke#link https://etherpad.opendev.org/p/swift-ptg-victoria21:09
claygso there IS an in-person presence?21:10
mattoliveraubut I'd like to get some virtual rooms booked before what ever our best times get taken by other projects21:10
claygoh, virtual rooms21:10
*** jamesmcarthur has quit IRC21:10
mattoliverau*needs to happen by21:10
mattoliverauroom booking spreadsheet21:11
mattoliverau#link https://ethercalc.openstack.org/126u8ek25noy21:11
mattoliverauif you want to see what it currently looks like.21:11
timburkekota_, otoh, we'll get to know each other's families so much better than we typically get just from pictures :-)21:11
kota_timburke: :)21:12
mattoliveraulol21:12
kota_good idea21:12
mattoliverauAnyway, sorry for the brain dump21:12
timburkedon't apologize! that was just the sort of overview i was hoping for and never got around to putting together myself21:13
timburkeagain, thank you so much for taking that on, and sorry i didn't ask for help earlier21:13
mattoliveraubasically, 1. If ther eis any project your interested in, let me know; 2. fill out doodle poll once I get a link up later today; 3. update the etherpad;21:13
mattoliverautimburke: nps21:14
timburke#topic object updater21:14
*** openstack changes topic to "object updater (Meeting topic: swift)"21:14
claygupdater 😡21:14
timburkerledisez, thanks for putting this on the agenda! i think you may have noticed that we've been interested in this lately, too ;-)21:14
rledisezYeah, I though I bring the point here cause some of us are having issue with it (at least we do, at ovh :))21:15
rledisezthere is mostly 2 issues in my mind:21:15
rledisezthe first one is that async-pendings can quickly piles up on disks for many reasons (unsharded bug container, network issue, process hanged, …)21:16
*** jamesmcarthur has joined #openstack-meeting21:16
rledisezand while some of them will never be able to be handled by the updater (at least without an operator intervention), some of them can be handled because it was a really transiant situation (like a switch reboot…)21:16
rledisezthe first review is about that: p 57191721:17
patchbothttps://review.opendev.org/#/c/571917/ - swift - Manage async_pendings priority per containers - 5 patch sets21:17
rledisezthe blocking point seems to be that it changes the way async pendings are stored21:17
rledisezthe second issue is that the way we communicate with container-server is by sending one request per async-pendings instead of batching them21:18
rledisezthat what p 724943 is about21:18
patchbothttps://review.opendev.org/#/c/724943/ - swift - WIP: Batched updates for object-updater - 2 patch sets21:18
rledisezI though I would bring this here to have some other oint of view21:18
rledisez(I'm done with the summary. any questions, remarks?)21:19
timburkeso a bit of perspective from clayg tdasilva and i: we've got a cluster that's filling up, leading to quotas being implemented, leading to users wanting to delete a good bit of data, often in fairly large containers21:19
claygit sounds like the issue we're having might be slightly different then - we accepted ~350M deletes into some sharded containers with billions of objects and the updaters keep dos-ing the container dbs 🤷‍♂️21:20
timburkewe're currently sitting at like 450+M async pendings across ~250 nodes, and that's still going up by ~2.5M/hr21:21
alecuyerouch21:21
claygthere's just no flow control across the nodes to try and put db updates in at "the correct rate"21:21
rledisezclayg: yeah, I'm more looking into treating quickly what can be treated while still trying for the problematic containers21:21
claygwe're also learning there's still lots of OTHER updates going into these same containers so we're trying to break up the work and prioritize stuff21:22
claygrledisez: yeah on a "per node" basis we need some way to have "bad containers" somehow get... I guess "error limited" or something like what you've done in the top-of-stack patch where it just "moves on"21:22
claygI'd really like it AT LEAST per-node we could have a per-container rate limit21:23
timburkefwiw, "treating quickly what can be treated" is actually *exactly* what clayg did earlier this week -- run a filtered updater that ignores certain containers, then try running foreground updaters for the remaining ones21:23
claygyeah I don't guess I have that gist up just now, one sec21:25
rlediseztimburke: I saw that tool, there is a link in the review. my issue with it is that it has to open all async-pendings to filter them. I really want to avoid wasting I/O on that (are you running on SSD guys?)21:25
claygoh, no ... i did, just lost it -> https://gist.github.com/clayg/c3d31a62eba590eebd5f5d257c24a29721:26
clayganyways - this is *useful* but not very scalable in terms of operator friendly21:26
*** slaweq has quit IRC21:26
timburkeno, we just took the io hit -- worst case, it slows down object servers which might apply some backpressure to the clients :P21:27
timburkefwiw, another thought i'd had recently was to make the number of successes required to unlink configurable -- if we can get the update to 2/3 replicas, that's *probably* good enough, right?21:28
claygwe're not on SSDs but we do have SOME head room on iops21:28
timburkelet container replication square it21:28
*** jmasud has joined #openstack-meeting21:28
claygI hadn't really considered the overhead of opening an async to parse it only to find out that container is ratelimited 🤔21:28
rledisezhow does replication work on big-unsharded container? I'm not sure it would do a better job21:28
clayg@timburke wants to just put all the async updates in a database - I don't want to have to deal with another .pending file lock timeouts21:29
timburkei mean, they're big... but not *that* big. ~20M rows or so, i think?21:29
claygtimburke: I think rledisez was asking about *un* sharded21:30
claygyeah, sharding was primarily in my mind to fix container replication21:30
timburkeright, but i mean, we could shard that big shard -- we just haven't21:30
claygreplication works great on the shards!21:30
claygtimburke: yeah, we have more sharding to do21:30
timburkewe've been pretty good about sharding the *biggest* guys, we've only got like 2 containers over 50M21:31
timburkeone of them is actually itself a shard 🤔21:31
mattoliverauthen shard the shard :)21:31
alecuyerI'm wondering if this is "fixable" without throttling DELETEs? Unless you have excess IO capacity in your container servers, something is always going to be lagging in your situation, no? (it would be nice of course to prioritize some things but still)21:32
claygwe DO have IO headroom in the container dbs tho21:32
alecuyerok so it's sqlite contention?21:33
claygyeah it's some kind of locking - either we're doing or sqlite21:33
claygyesterday it looked like the replication UPDATE request locked up the db for 25s - then FAILED21:34
claygso we're leaving throughput on the floor and it's unclear we're making progress - we have more investigation to21:34
claygI'll think more on the ordering asyncs by containers - I'm generally pretty happy with the filesystem layout21:34
*** e0ne has joined #openstack-meeting21:35
rledisezwith a new layout, it would be pretty easy to batch updates to send to container as they are grouped all together21:36
claygit's hadn't been obviously terrible to me that a cycle of the updater would read and open the 125K asyncs per-disk21:36
rledisezit was actually a followup I wanted on the first patch (and also to move "legacy" async-pendings)21:36
mattoliveraure container replication, if the 2 container are generally close in side, we use usync (ie sync a bunch of rows) so maybe only needing quruom successes and letting the container possibly usync (batch with other updates) is better, rather then waiting for all replicas. Of course large unsharded will always be an issue.. we just need to shard the buggers.21:36
timburkeand i need to work on getting a good process going for manual shrinking -- part of why i'm hesitant to shard is that i think a lot of those shards are going to end up mostly-empty once everything settles, and we haven't really invested in shrinking yet :-/21:37
claygyeah, the batch updates may indeed be useful ... rledisez you're winning me over on the layout change21:37
rledisezyay! can I offer you a virtual-beer during the virtual-ptg?21:38
mattoliverauI like the idea of splitting the asyncs by container in the sense from a glance you can see how if containers are stuggling, but it that too much directory walking i/o, ie listdir? Maybe one per partition? which will map to container replicas21:38
claygat this point my biggest complaint to change it probably just reservation about changing on-disk layouts and legacy migrations etc21:39
mattoliverauyeah21:39
claygit's a bunch of work - but maybe it's worth it - thanks for bringing this up21:39
claygI don't think I had a good picture of where your thinking was coming from - it's clearer now21:39
rledisezso, the current patch is compatible with current layout, so no break during an update. in case of downgrade, some move of files would be required21:39
claygmattoliverau: yeah some workloads I'd seen had a BUNCH of containers in their cluster21:40
claygI think of all the dirs we create if a node is offline for awhile21:40
clayginstead of "a handful" of problematic containers we get one TLD for each container on a node - which... might still be less 1M - but in the 100Ks21:40
rledisezthe cost of listing a directory of 100K entries is not big, but the cost of inserting a new one is not negligeable21:41
rledisez(i made some measure during my tests)21:41
mattoliverautimburke: yeah, mark as SHRINKING And maybe get to tool to search for the donor etc.21:42
timburkehmm... i wonder if a db could still be a good idea -- have the object-server continue dropping files all over the fs, then have the updater walk that tree and load into db before fanning out workers to read from the db...21:42
alecuyersounds good, I'm afraid of having too many files on disk, wonder why :)21:42
rledisezwhy dropping a file then? with the WAL, insertion should be quite fast, no?21:43
mattoliverauuse the general task queue.. and just hope that container gets updates so we don't have to deal with async.. damn :P21:43
claygmattoliverau: 😆21:43
rledisezI would then even move to appending to a file, just to avoid too many fsync21:43
*** e0ne has quit IRC21:44
timburkeok, this has been a good discussion. are there any decisions or action items we can take away from it?21:45
*** raildo_ has joined #openstack-meeting21:45
*** smcginnis has quit IRC21:46
rledisezshould we investigate the DB idea?21:46
rledisezI'm pretty sure it would be better, but it's also more work so won't be ready soon21:46
alecuyer(I have to say I have no updates on LOSF having had no time to work on it this week. rledisez left it on the agenda as I should get some time next week. So, we can have more time for object updater or other topics)21:47
timburkealecuyer, thanks for hte heads-up21:47
claygi need to investigate the problem in our cluster - that's ahead of me making a decision on the suitability of rledisez 's purposed layout change - but I'd like to review that more seriously given new perspective and anything I learn trying to fix our mess21:47
*** raildo has quit IRC21:48
timburkeok, one more crazy idea, that might be a somewhat cheaper way to investigate the db idea: what about a db per container? we could put it in the disk's containers/ driectory...21:48
claygI was seriously attacted to this idea because of leverage21:50
rledisezyeah, we can just run the container-replicator then21:50
clayg"can't stuff it in the primary container - just put it in a local handoff!"21:50
timburkei mean, we've already got this db schema for tracking exactly the info that's in these updates...21:50
clayghehhe21:50
claygi was concerned that for AC/O clusters there might be some distaste to adding a container-replicator to your object layer21:51
timburke*especially* for the shards -- then you run no risk of proxies getting getting bad acls from the handoff that got popped into existence when the primaries are overloaded21:51
claygwe could just import the container-replicator into the updater and ... well do something21:51
timburketrue enough! we've already got the sharder doing something not so dissimilar21:52
claygtimburke: yeah vivifying containers in the read path is probably not ideal - i was thinking out of band21:52
mattoliverauas handoff conatiners? if so just make sure you get the rowids close to their parent. otherwise it might cuase a rsync_then_merge and that wouldn't go well on really large containers.21:53
claygmattoliverau: good point21:54
*** jamesmcarthur has quit IRC21:55
rledisezwe can avoid that by tuning the limits on the async updater/replicator I guess. but yes, something to take care of for sure21:55
timburkei should read the rsync-then-merge code again...21:56
timburkeall right21:56
timburke#topic open discussion21:56
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:56
timburkeanything else we should talk about in these last few minutes of meeting time?21:56
mattoliveraunope, /me wants breakfst ;)21:58
claygnom nom21:58
claygi might cook eggs and bacon for dinner 🤔21:58
mattoliverauyou totally should! :)21:59
kota_it seems kids woke up.21:59
timburke:-) then this is as good a time as any to21:59
timburke#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:59
openstackMeeting ended Wed May  6 21:59:41 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-05-06-21.00.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-05-06-21.00.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-05-06-21.00.log.html21:59
timburkeoh! and as always, thank you all for coming, and thank you for working on swift :-)22:00
*** raildo_ has quit IRC22:01
*** smcginnis has joined #openstack-meeting22:05
*** andrebeltrami has quit IRC22:11
*** ayoung has quit IRC22:16
*** jmasud has quit IRC22:17
*** ayoung has joined #openstack-meeting22:17
*** jmasud has joined #openstack-meeting22:18
*** ykatabam has joined #openstack-meeting22:25
*** jmasud has quit IRC22:31
*** jmasud has joined #openstack-meeting22:32
*** jmasud has quit IRC22:46
*** TrevorV has quit IRC22:54
*** jmasud has joined #openstack-meeting23:03
*** rh-jelabarre has quit IRC23:07
*** ociuhandu has joined #openstack-meeting23:09
*** ociuhandu has quit IRC23:15

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!