Wednesday, 2019-12-18

*** epei_ has quit IRC00:00
*** mattw4 has quit IRC00:02
*** epei has joined #openstack-meeting00:03
*** ijw has joined #openstack-meeting00:07
*** ijw has quit IRC00:07
*** epei has quit IRC00:08
*** ijw has joined #openstack-meeting00:08
*** ijw has quit IRC00:08
*** ijw has joined #openstack-meeting00:10
*** bnemec has quit IRC00:14
*** jawad_axd has joined #openstack-meeting00:14
*** jawad_axd has quit IRC00:18
*** armax has joined #openstack-meeting00:27
*** yamamoto has joined #openstack-meeting00:32
*** jawad_axd has joined #openstack-meeting00:34
*** ykatabam has quit IRC00:35
*** ykatabam has joined #openstack-meeting00:38
*** jawad_axd has quit IRC00:39
*** rodrigods has quit IRC00:39
*** brinzhang has joined #openstack-meeting00:44
*** gyee has quit IRC00:47
*** jawad_axd has joined #openstack-meeting00:55
*** jawad_axd has quit IRC01:00
*** artom has quit IRC01:08
*** Liang__ has joined #openstack-meeting01:09
*** jawad_axd has joined #openstack-meeting01:16
*** jawad_axd has quit IRC01:21
*** yamamoto has quit IRC01:34
*** jawad_axd has joined #openstack-meeting01:37
*** ijw has quit IRC01:40
*** ijw has joined #openstack-meeting01:40
*** jawad_axd has quit IRC01:41
*** ijw has quit IRC01:45
*** diablo_rojo has quit IRC01:55
*** jawad_axd has joined #openstack-meeting01:57
*** jawad_axd has quit IRC02:01
*** dklyle has quit IRC02:03
*** david-lyle has joined #openstack-meeting02:03
*** yamamoto has joined #openstack-meeting02:04
*** ykatabam has quit IRC02:06
*** mriedem has quit IRC02:09
*** armax has quit IRC02:12
*** jawad_axd has joined #openstack-meeting02:18
*** ykatabam has joined #openstack-meeting02:18
*** jawad_axd has quit IRC02:22
*** jawad_axd has joined #openstack-meeting02:39
*** jawad_axd has quit IRC02:43
*** yamamoto has quit IRC02:44
*** apetrich has quit IRC03:09
*** yamamoto has joined #openstack-meeting03:11
*** gouthamr has quit IRC03:14
*** brinzhang_ has joined #openstack-meeting03:18
*** brinzhang_ has quit IRC03:20
*** brinzhang has quit IRC03:21
*** brinzhang_ has joined #openstack-meeting03:22
*** yaawang has joined #openstack-meeting03:23
*** gouthamr has joined #openstack-meeting03:24
*** jamesmcarthur has joined #openstack-meeting03:29
*** ykatabam has quit IRC03:29
*** psachin has joined #openstack-meeting03:39
*** jamesmcarthur has quit IRC03:44
*** brinzhang has joined #openstack-meeting03:49
*** brinzhang_ has quit IRC03:51
*** yamamoto has quit IRC03:58
*** brinzhang_ has joined #openstack-meeting04:24
*** brinzhang has quit IRC04:27
*** masahito has joined #openstack-meeting04:33
*** osmanlicilegi has joined #openstack-meeting04:34
*** masahito has quit IRC04:38
*** yamamoto has joined #openstack-meeting04:39
*** epoojad1 has joined #openstack-meeting04:49
*** yamamoto has quit IRC04:49
*** Lucas_Gray has joined #openstack-meeting04:50
*** brinzhang_ has quit IRC04:54
*** Lucas_Gray has quit IRC04:58
*** Lucas_Gray has joined #openstack-meeting05:00
*** ykatabam has joined #openstack-meeting05:11
*** pcaruana has joined #openstack-meeting05:24
*** Lucas_Gray has quit IRC05:27
*** yonglihe has joined #openstack-meeting05:29
*** ricolin has joined #openstack-meeting05:29
*** links has joined #openstack-meeting05:34
*** ayva has joined #openstack-meeting05:38
*** zaneb has quit IRC05:53
*** hyunsikyang has quit IRC05:58
*** ociuhandu has joined #openstack-meeting06:07
*** ociuhandu has quit IRC06:11
*** masahito_ has joined #openstack-meeting06:13
*** masahito_ has quit IRC06:17
*** masahito has joined #openstack-meeting06:18
*** masahito has quit IRC06:22
*** masahito has joined #openstack-meeting06:25
*** epei has joined #openstack-meeting06:28
*** masahito has quit IRC06:30
*** epei has quit IRC06:33
*** masahito has joined #openstack-meeting06:44
*** jamesmcarthur has joined #openstack-meeting06:46
*** janki has joined #openstack-meeting06:48
*** jamesmcarthur has quit IRC06:51
*** ykatabam has quit IRC06:55
*** rcernin has quit IRC06:56
*** epei has joined #openstack-meeting07:05
*** epei has quit IRC07:09
*** lpetrut has joined #openstack-meeting07:26
*** hyunsikyang has joined #openstack-meeting07:41
*** masahito has quit IRC07:45
*** kozhukalov has joined #openstack-meeting07:52
*** kopecmartin|off is now known as kopecmartin07:53
*** slaweq has joined #openstack-meeting08:03
*** vesper11 has quit IRC08:09
*** jawad_axd has joined #openstack-meeting08:09
*** ricolin has quit IRC08:11
*** vesper11 has joined #openstack-meeting08:14
*** masahito has joined #openstack-meeting08:16
*** ykatabam has joined #openstack-meeting08:17
*** ricolin has joined #openstack-meeting08:18
*** epei has joined #openstack-meeting08:22
*** yaawang has quit IRC08:25
*** epei has quit IRC08:27
*** slaweq has quit IRC08:36
*** ralonsoh has joined #openstack-meeting08:40
*** yamamoto has joined #openstack-meeting08:48
*** slaweq has joined #openstack-meeting08:50
*** oneswig has joined #openstack-meeting08:51
*** yamamoto has quit IRC08:52
*** mdelavergne has joined #openstack-meeting08:57
*** kozhukalov has quit IRC08:58
*** rpittau|afk is now known as rpittau08:59
ttx#startmeeting large_scale_sig09:00
openstackMeeting started Wed Dec 18 09:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: large_scale_sig)"09:00
openstackThe meeting name has been set to 'large_scale_sig'09:00
ttx#topic Rollcall09:00
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"09:00
oneswighi09:00
ttxwho is around?09:00
amorinhey all09:00
ttxoneswig, amorin o/09:00
oneswiggreetings \o09:00
masahitoo/09:01
ttxWhile we wait for more, here is our agenda:09:01
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting09:01
ttxFeel free to add other topics !09:01
ttxjiaopengju, Dinesh_Bhor: around?09:02
mdelavergnehi09:02
ttxetp: too09:02
etpo/09:02
ttxok let's get started09:03
ttx#topic Last meeting actions09:03
*** openstack changes topic to "Last meeting actions (Meeting topic: large_scale_sig)"09:03
ttxWe have minutes for our last meeting at:09:03
ttx#link http://eavesdrop.openstack.org/meetings/large_scale_sig/2019/large_scale_sig.2019-11-27-09.00.html09:03
ttxWe had the following actions:09:03
ttx- ttx to propose large scale SIG creation changes to openstack-sigs repository09:03
ttxThat's done, our SIG is now official at https://governance.openstack.org/sigs/ !09:03
ttxWe also have a basic information page on the wiki at https://wiki.openstack.org/wiki/Large_Scale_SIG09:04
ttx- ttx to send meeting summary and create two etherpads to further refine the two initial goals09:04
amorinyay!09:04
masahitoThanks for the patch and organization :-)09:04
ttxI did that too, and we'll dive in the etherpads for the rest of the meeting09:04
ttx#topic Objective: Scaling within one cluster, and instrumentation of the bottlenecks09:05
*** openstack changes topic to "Objective: Scaling within one cluster, and instrumentation of the bottlenecks (Meeting topic: large_scale_sig)"09:05
ttxwith the following volunteers: masahito, oneswig, YusukeTatsumi, jiaopengju09:05
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling09:05
ttxTo kick off the discussion I suggested two subgoals on that one09:05
ttx- Document "average" single-cluster scaling limits today, and what usually breaks first09:05
ttx- Measurement of MQ behavior through oslo.metrics09:06
ttxLast I looked, nobody jumped on the first one. Does it sound like a valuable goal ? Or should we focus on the second for now?09:06
ttxMy thought was that describing what currently happens when we scale a cluster up, and what tends to fail first and at which limit, gives us a good base.09:06
ttx(I personally have no idea because I don;t have that experience, only second-hand accounts)09:07
oneswigI think it is a valuable goal.  The difficulty is finding someone who does this regularly enough.09:07
amorinwhat we can without so much effort is collecting the experiences from everybody in the group09:07
ttxAnd with your collective experience, you're well positioned to describe that.09:07
ttxyes... Does not have to be a formal documentation, we could set it up as a mailing-list thread where each would contribute their experience...09:07
ttxOr an etherpad with a call for participation...09:07
amorinyes, and maybe add a link to this etherpad or the mail on a wiki page09:08
amorinso we can find it easily09:08
masahitoIs the first goal like an userstory?09:08
ttxmasahito: yes... the goal is to describe what currently breaks first when we scale up. I bet each case is a bit different... but09:09
ttxI also bet there are general issues09:09
masahitoIf so, I could quickly write the problem we hit before. I thought it targeted some technical document, like actual configuration for scaling.09:09
ttxLike we all know rabbit is (one of the) first to break09:09
ttxNo, I was thinking more like "tell us your story when you scaled up, what broke"09:10
ttx(and at which numbers, if possible)09:10
ttxdo you prefer etherpad or an email thread as a way to cllect that information?09:11
amorin+1 for etherpad09:11
*** altk has joined #openstack-meeting09:11
ttxIn both cases we should be ready to seed the discussion, to encourage others to talk09:11
amorinwe can do both actually09:11
ttxand by we I mean you, since I don;t have experience to contribute in that area09:11
ttxamorin: not a bad idea09:11
amorinan etherpad and a mail to let everybody aware09:11
ttxpost email, and collect the results in an etherpad09:12
*** jiaopengju1 has joined #openstack-meeting09:12
masahito+109:12
amorin+109:12
etp+109:12
ttxOK, so how about... you all prepare a short description of what usually happens to you when you scale up a single cluster up to a point. We wait until after new year. I create an etherpad and send a call for stories early January09:13
ttxand then you reply to that thread with your prepared stories, hopefully encouraging others to chime in09:13
ttxwe collect all the stories in a single etherpad09:13
ttxthen reduce that etherpad to common trends09:14
amoringood plan09:14
etpworks for me09:14
jiaopengju1+1, sorry for my late09:14
masahitoI'm okay09:14
ttx#action all prepare a short description of what happens (what breaks first) when scaling up a single cluster09:15
ttx#action ttx to prepare etherpad and send ML thread asking for user scaling stories, to be posted after the end-of-year holidays09:15
ttxok, we have a plan09:15
ttx<--- happy09:15
ttx- Measurement of MQ behavior through oslo.metrics...09:16
ttxwe have some early steps documented09:16
ttxWho is interested in writing that oslo.metric blueprint?09:16
ttx(or collaborate on one)09:16
ttxI think LINE is well advanced on that09:16
masahitoyes, I wrote it on the etherpad09:17
ttxmaybe you can post the first draft and we can help you review it?09:17
masahitoYes.09:17
ttx#action masahito to produce first draft for the oslo.metric blueprint09:18
ttxok.. anything more to do immediately on that subgoal?09:18
masahitoI don't have much time to work for writing the draft right now. I will be able to push the bp in beggining of next year.09:19
ttxsure, no hurry :)09:19
ttxJust documenting next steps09:19
ttxoneswig added another subgoal: Instrumentation for "golden signals"09:20
ttxI think that would be very valuable. But it feels more like a second-stage goal09:21
oneswigI did... I think the terminology in this book might be useful to adopt.09:21
oneswigttx: it's more abstract than specific cases such as rabbit09:21
ttxOnce we identify what the current state is09:21
ttxI think golden signals will emerge09:21
ttxunless you think we can start documenting that already?09:22
amorinwhat do you mean by golden signals?09:22
oneswigNot sure.  I can start in early 2020.09:22
ttxor maybe as a first step, learn about that concept09:22
oneswiggolden signals are tell-tales, strong indicators for symptoms of trouble.09:23
etpdo you mean like nova api response time increasing suddenly/steadily?09:23
ttxI know! it's when my phone vibrates09:23
oneswigetp: yes, exactly that kind of thing - that would be a latency measurement09:24
amorinok thanks09:24
etpthose do tend to reveal interesting things :)09:24
oneswigapologies I must leave in a few minutes - diary conflict09:25
ttxok moving on quickly09:25
ttxI propose as action that we read a bit more about golden signals between now and next meeting09:26
ttx#action all learn more about golden signals concept as described in https://landing.google.com/sre/book.html09:26
ttxOK, let's move to the other goal09:26
ttx#topic Objective: Document large scale configuration and tips &tricks09:27
*** openstack changes topic to "Objective: Document large scale configuration and tips &tricks (Meeting topic: large_scale_sig)"09:27
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation09:27
ttxAgain I did suggest two subgoals based on our discussion last week09:27
ttxerr... last meeting09:27
ttxThe first one is probably a group exercise... If you find doc or blogposts that can help, add them here. There may not be that many.09:27
ttxSearching planet.openstack.org may help.09:27
*** apetrich has joined #openstack-meeting09:27
ttx#action all add links to relevant articles around large scale openstack (if you find any) to the etherpad09:28
oneswigWith a Scientific SIG hat on, it might be a useful group for gathering data from.  I can follow up on that.09:28
oneswighave to go, sorry but do set an action iif you agree.09:28
*** oneswig has quit IRC09:28
ttxyes, scientific communities are generally more used to sharing09:28
ttx#action oneswig to follow up with Scientific community to find such articles09:29
ttxThe second subgoal is around documenting configuration values09:30
ttxamorin suggested several tactics there09:30
ttxPatching existing docs, producing a new doc, or a mixture of both...09:30
amorinyes09:30
ttxWhat do others think?09:30
ttxMy gut feeling is that this should appear in regular doc, if it's good and current enough to support that. If not good/current, a new doc might be preferable09:30
amorinI think the best is my last proposition09:30
amorina mix between patching current doc and eventually have an external pages with details09:31
ttxyeah that would probably work best09:31
ttxallows to discover settings, without making the original doc too complex09:31
amorinyup09:32
amorinI have the feeling that it would help09:32
amorinat least, help me :p09:32
etp+1, external page would be useful linked to golden metrics09:32
ttxOK, so what would be the next step for this?09:33
amorinI dont know how we should proceed09:34
amorinbut maybe we should ask the PTL of each project09:34
ttx#agree we should patch existing doc to point to a separate new doc09:34
amorinwhat they thing about our plan?09:34
amorinmaybe they will have ideas09:34
ttx'OK, so the simplest would be to post a ML thread with [largescale-sig] and [ptl]09:35
ttxIf that does not work, I can help with engaging more directly09:35
amorinok09:36
ttxbut having the thread as a base we can link to will be useful in all cases09:36
amorinI can start this thread if you want09:36
ttxthat would be perfect. Again I think we should avoid the end-of-year, because that's when threads go ignored09:36
*** Liang__ has quit IRC09:36
amorinok, I can start it in january09:37
ttxA lot of people just declare ML bankrupcy after the holidays :)09:37
ttx#action amorin to start a thread on documenting configuration defaults for large scale, introduce the "mixture of both" tactic09:37
ttxAlright, we have next steps here too... anything else on that topic?09:38
ttxAny other topic you'd like to discuss?09:39
ttx#topic Any other business09:40
*** openstack changes topic to "Any other business (Meeting topic: large_scale_sig)"09:40
ttxI noticed we have a new group member, mdelavergne09:40
ttxmaybe you can introduce yourself?09:40
mdelavergneYep :)09:40
ttxWhat would you like to achieve in this group, and do you find our early goals in line with that09:41
mdelavergneHi everyone, I'm am a PhD student at Inria, I work with the discovery initiative which tried to evaluate Openstack at the edge (so large scale and wanwide), and I'm trying to help with pointers to what we did, and trying to learn from your experiences mostly !09:42
ttxperfect! welcome09:42
mdelavergnethanks :)09:42
amorinwelcome!09:42
etpwelcome!09:43
masahitowelcome :)09:43
ttxTime to discuss next meeting date...09:43
ttxI think it's safe to skip the next two weeks. Do you prefer January 8 or January 15 for next meeting?09:43
masahitoI'm not available January 8.09:43
ttxI feel like we won't have made much progress by January 8... Maybe the 15th would be better? Just before Chinese new year09:44
ttxAs long as we start those threads before we should be good09:44
jiaopengju115th is ok for me09:44
masahito15th works for me.09:44
etp+1 for 15th09:44
mdelavergne15th is fine by me09:44
amorin15th is ok for me09:44
ttxAlright looks like a winner. Hopefully belmiro will be able to join us on that date09:45
ttx#agreed next meeting: January 15, 9utc #openstack-meeting09:45
ttxI'll send the meeting summary and the list of actions.09:45
ttxWe have a bunch of threads to start, and the week of January 6 is probably the best for that09:46
*** rsimai_away is now known as rsimai09:46
ttxAlright... anything else before we close?09:46
ttxThanks again to everyone for your participation in the group, and have a great end of year09:47
ttx#endmeeting09:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:47
openstackMeeting ended Wed Dec 18 09:47:38 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2019/large_scale_sig.2019-12-18-09.00.html09:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2019/large_scale_sig.2019-12-18-09.00.txt09:47
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2019/large_scale_sig.2019-12-18-09.00.log.html09:47
masahitoThanks. Have a good end of year!09:47
mdelavergneThanks and have a nice holidays!09:48
amorinthanks all09:48
etpThanks all09:49
*** apetrich has quit IRC09:58
*** ociuhandu has joined #openstack-meeting09:59
*** masahito has quit IRC10:06
*** e0ne has joined #openstack-meeting10:11
*** ociuhandu has quit IRC10:34
*** janki has quit IRC10:35
*** ociuhandu has joined #openstack-meeting10:36
*** ociuhandu has quit IRC10:40
*** ociuhandu has joined #openstack-meeting10:42
*** ociuhandu has quit IRC10:48
*** tbarron_ has joined #openstack-meeting10:59
*** ociuhandu has joined #openstack-meeting11:16
*** ociuhandu has quit IRC11:22
*** ociuhandu has joined #openstack-meeting11:23
*** ociuhandu has quit IRC11:24
*** ociuhandu has joined #openstack-meeting11:25
*** ociuhandu has quit IRC11:29
*** yaawang has joined #openstack-meeting11:31
*** Lucas_Gray has joined #openstack-meeting11:34
*** Lucas_Gray has quit IRC11:38
*** ociuhandu has joined #openstack-meeting11:40
*** apetrich has joined #openstack-meeting11:42
*** Lucas_Gray has joined #openstack-meeting11:42
*** ralonsoh has quit IRC11:48
*** ociuhandu has quit IRC11:50
*** ralonsoh has joined #openstack-meeting11:51
*** ociuhandu has joined #openstack-meeting11:51
*** masahito has joined #openstack-meeting11:52
*** brinzhang has joined #openstack-meeting11:54
*** brinzhang_ has joined #openstack-meeting11:56
*** jiaopengju2 has joined #openstack-meeting11:57
*** epoojad1 is now known as epoojad1|afk11:59
*** brinzhang has quit IRC11:59
*** jiaopengju1 has quit IRC12:00
*** altk has quit IRC12:00
*** jiaopengju1 has joined #openstack-meeting12:01
*** ociuhandu has quit IRC12:03
*** epoojad1|afk has quit IRC12:04
*** raildo has joined #openstack-meeting12:05
*** masahito has quit IRC12:20
*** ociuhandu has joined #openstack-meeting12:25
*** brinzhang has joined #openstack-meeting12:25
*** brinzhang_ has quit IRC12:28
*** brinzhang_ has joined #openstack-meeting12:28
*** ociuhandu has quit IRC12:28
*** ociuhandu has joined #openstack-meeting12:29
*** ociuhandu has quit IRC12:30
*** brinzhang_ has quit IRC12:30
*** ociuhandu has joined #openstack-meeting12:30
*** brinzhang_ has joined #openstack-meeting12:30
*** brinzhang has quit IRC12:31
*** brinzhang_ has quit IRC12:32
*** brinzhang_ has joined #openstack-meeting12:33
*** brinzhang_ has quit IRC12:34
*** ociuhandu has quit IRC12:34
*** ociuhandu has joined #openstack-meeting12:34
*** brinzhang_ has joined #openstack-meeting12:35
*** brinzhang_ has quit IRC12:36
*** Lucas_Gray has quit IRC12:36
*** brinzhang_ has joined #openstack-meeting12:36
*** brinzhang has joined #openstack-meeting12:38
*** brinzhang_ has quit IRC12:41
*** bbowen has quit IRC12:44
*** brinzhang_ has joined #openstack-meeting12:45
*** brinzhang has quit IRC12:48
*** senrique_ has joined #openstack-meeting12:52
*** bbowen has joined #openstack-meeting13:00
*** jiaopengju2 has quit IRC13:04
*** jiaopengju2 has joined #openstack-meeting13:04
*** Shrews has left #openstack-meeting13:05
*** electrofelix has joined #openstack-meeting13:05
*** jamesmcarthur has joined #openstack-meeting13:05
*** ociuhandu has quit IRC13:06
*** ociuhandu has joined #openstack-meeting13:07
*** ociuhandu has quit IRC13:11
*** jamesmcarthur has quit IRC13:12
*** ociuhandu has joined #openstack-meeting13:12
*** jamesmcarthur has joined #openstack-meeting13:13
*** ociuhandu has quit IRC13:18
*** brinzhang has joined #openstack-meeting13:19
*** ykatabam has quit IRC13:19
*** brinzhang_ has quit IRC13:22
*** jamesmcarthur has quit IRC13:29
*** brinzhang_ has joined #openstack-meeting13:30
*** ociuhandu has joined #openstack-meeting13:32
*** brinzhang has quit IRC13:33
*** brinzhang_ has quit IRC13:33
*** brinzhang_ has joined #openstack-meeting13:34
*** brinzhang_ has quit IRC13:35
*** ociuhandu has quit IRC13:39
*** njohnston is now known as njohnston|xmas13:40
*** mriedem has joined #openstack-meeting13:43
*** ociuhandu has joined #openstack-meeting13:47
*** Liang__ has joined #openstack-meeting13:47
*** Liang__ is now known as LiangFang13:48
*** LiangFang has quit IRC13:49
*** Liang__ has joined #openstack-meeting13:50
*** jiaopengju2 has quit IRC13:50
*** senrique_ is now known as enriquetaso13:50
*** jiaopengju1 has quit IRC13:50
*** Liang__ is now known as LiangFang13:50
*** jamesmcarthur has joined #openstack-meeting13:55
*** jamesmcarthur has quit IRC13:59
*** ociuhandu has quit IRC14:00
*** jamesmcarthur has joined #openstack-meeting14:03
*** dviroel has joined #openstack-meeting14:04
*** ociuhandu has joined #openstack-meeting14:04
*** sfernand has joined #openstack-meeting14:06
*** bnemec has joined #openstack-meeting14:10
*** priteau has joined #openstack-meeting14:17
*** ociuhandu has quit IRC14:26
*** ociuhandu has joined #openstack-meeting14:27
*** ociuhandu has quit IRC14:31
*** LiangFang has quit IRC14:33
*** Liang__ has joined #openstack-meeting14:34
*** Liang__ is now known as LiangFang14:34
*** ociuhandu has joined #openstack-meeting14:47
*** mriedem has quit IRC14:51
*** david-lyle is now known as dklyle14:51
*** mriedem has joined #openstack-meeting14:51
*** ociuhandu has quit IRC14:56
*** jawad_axd has quit IRC14:58
*** jawad_axd has joined #openstack-meeting15:02
*** ociuhandu has joined #openstack-meeting15:02
*** LiangFang has quit IRC15:03
*** jawad_ax_ has joined #openstack-meeting15:06
*** jawad_axd has quit IRC15:06
*** jawad_ax_ has quit IRC15:10
*** links has quit IRC15:10
*** anastzhyr has joined #openstack-meeting15:15
*** ociuhandu has quit IRC15:19
*** ociuhandu has joined #openstack-meeting15:20
*** ociuhandu has quit IRC15:21
*** ociuhandu has joined #openstack-meeting15:21
*** lpetrut has quit IRC15:23
*** yamamoto has joined #openstack-meeting15:24
*** eharney has quit IRC15:29
*** yamamoto has quit IRC15:29
*** panda has quit IRC15:31
*** panda has joined #openstack-meeting15:33
*** yamamoto has joined #openstack-meeting15:54
*** jawad_axd has joined #openstack-meeting15:56
*** rsimai is now known as rsimai_away15:56
*** jawad_axd has quit IRC16:01
*** woojay has joined #openstack-meeting16:03
*** gyee has joined #openstack-meeting16:03
*** rbudden has joined #openstack-meeting16:04
*** woojay has left #openstack-meeting16:08
*** armax has joined #openstack-meeting16:09
*** epei has joined #openstack-meeting16:11
*** jawad_axd has joined #openstack-meeting16:17
*** jawad_axd has quit IRC16:21
*** yamamoto has quit IRC16:22
*** eharney has joined #openstack-meeting16:24
*** mdelavergne has quit IRC16:25
*** ociuhandu has quit IRC16:30
*** eharney_ has joined #openstack-meeting16:33
*** eharney has quit IRC16:37
*** epei has quit IRC16:56
*** epei has joined #openstack-meeting16:57
*** yamamoto has joined #openstack-meeting16:58
*** kopecmartin is now known as kopecmartin|off16:58
*** epei_ has joined #openstack-meeting17:00
*** epei has quit IRC17:01
*** sfernand has quit IRC17:06
*** dtrainor has quit IRC17:08
*** dtrainor has joined #openstack-meeting17:08
*** yamamoto has quit IRC17:11
*** artom has joined #openstack-meeting17:17
*** jawad_axd has joined #openstack-meeting17:18
*** diablo_rojo has joined #openstack-meeting17:18
*** rpittau is now known as rpittau|afk17:21
*** jawad_axd has quit IRC17:23
*** dklyle has quit IRC17:26
*** david-lyle has joined #openstack-meeting17:26
*** david-lyle has quit IRC17:26
*** david-lyle has joined #openstack-meeting17:26
*** mattw4 has joined #openstack-meeting17:35
*** panda has quit IRC17:36
*** epei_ has quit IRC17:37
*** panda has joined #openstack-meeting17:39
*** psachin has quit IRC17:39
*** ociuhandu has joined #openstack-meeting17:51
*** dviroel has quit IRC17:53
*** ociuhandu has quit IRC17:55
*** rubasov has quit IRC17:57
*** enriquetaso has quit IRC17:59
*** rfolco has quit IRC18:07
*** electrofelix has quit IRC18:09
*** priteau has quit IRC18:19
*** ralonsoh has quit IRC18:25
*** e0ne has quit IRC18:39
*** eharney_ has quit IRC18:40
*** rubasov has joined #openstack-meeting18:42
*** enriquetaso has joined #openstack-meeting18:43
*** rfolco has joined #openstack-meeting18:52
*** jamesmcarthur has quit IRC19:03
*** jamesmcarthur has joined #openstack-meeting19:26
*** dviroel has joined #openstack-meeting19:32
*** jamesmcarthur has quit IRC19:38
*** e0ne has joined #openstack-meeting19:58
*** david-lyle is now known as dklyle20:00
*** enriquetaso has quit IRC20:08
*** jamesmcarthur has joined #openstack-meeting20:09
*** anastzhyr has quit IRC20:15
*** rf0lc0 has joined #openstack-meeting20:15
*** rfolco has quit IRC20:17
*** e0ne has quit IRC20:25
*** slaweq has quit IRC20:36
*** rf0lc0 has quit IRC20:41
*** slaweq has joined #openstack-meeting20:44
timburke#startmeeting swift21:01
openstackMeeting started Wed Dec 18 21:01:32 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
timburkewho's here for the swift meeting?21:01
rledisezo/21:02
timburkequiet. maybe this'll be a fast one21:03
timburkeas always, agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:04
timburke#topic next meeting21:04
*** openstack changes topic to "next meeting (Meeting topic: swift)"21:04
tdasilvao/21:04
timburkejust a reminder: no meeting next week (Dec 25) or the week after (Jan 1)21:04
timburkeso next meeting will be Jan 821:04
tdasilvaack21:05
timburkethat's all i've got, really -- on to updates!21:05
timburke#topic versioning21:06
*** openstack changes topic to "versioning (Meeting topic: swift)"21:06
mattoliverauo/ (sorry I'm late)21:06
timburketdasilva, how's it going?21:06
timburkemattoliverau, no worries :-)21:06
timburkei can also talk about what *i've* found as a reviewer ;-)21:07
timburkei've been poking at getting a probe test for sharding a new-style versioned container21:07
tdasilvawe are continuing to make good progress I think. timburke left comments on the swift versioning so we are working through some of those21:07
tdasilvasorry, i type slow21:07
timburkeit's still early for you ;-)21:08
timburke(in particular, i'm looking to shard the backing, reserved-name container)21:08
tdasilvajust wanted to add we added some todo items to the bottom of the ehterpad: https://etherpad.openstack.org/p/swift-object-versioning21:08
tdasilvakind of summarizes last few items we are currently aware of and working on21:09
timburkesounds good21:09
timburkeany other input we need from people, or is it mostly a matter of cranking through the remaining issues?21:10
tdasilvaso yeah, we are pushing it hard to get it over the finish line soon21:10
claygI’m working on a version of the brain splitter that can use internal client so I can have reconciler probe tests for the null namespace.21:10
timburkeclayg, *i* was thinking i need that, too!21:10
claygOh. Well today’s been crazy. Maybe tomorrow.21:11
*** yamamoto has joined #openstack-meeting21:11
*** zaitcev has joined #openstack-meeting21:12
timburkei'll see how far i can get; throw up whatever i've got at EOD, anyway21:12
*** ayoung has joined #openstack-meeting21:12
timburkeam i right in thinking that we know what needs to happen, and there aren't really any decisions we need to make regarding it?21:13
tdasilvaoh21:13
tdasilvai think we said last week we would discuss again about `enabled by default` ?21:13
tdasilvaor am i confused?21:13
timburkesorry, i'd forgotten. i think i'm of the opinion that i *wouldn't* recommend it by default yet (for upstream, anyway)21:15
tdasilvaactually, yeah, nevermind: "anyway, something to think about. i don't think we're likely to enable-by-default before the next time we all see each other face-to-face, anyway ;-)"21:15
*** raildo has quit IRC21:16
timburkemaybe i'll feel differently once i've got probe tests for sharding/reconciler/expirer ;-)21:16
tdasilvaespecially given the probe tests ...right!21:16
timburkesounds like we've got what we need to keep moving21:16
timburke#topic profiling/md5 optimization21:17
*** openstack changes topic to "profiling/md5 optimization (Meeting topic: swift)"21:17
timburkerledisez, how's it going?21:17
*** yamamoto has quit IRC21:17
rledisezwell, I didn't di much on that. I mostly think about how I would implement it. I don't want to redo the whole world, so i'll try to be smart in integrating that. but no real code for now21:18
timburke👍21:18
rledisezthe different combination (crypto/replica, crypto/EC, EC, replica) make it a bit hard to do something really optimized (in the way it's designed). i'm thinking about that too21:19
*** alecuyer has joined #openstack-meeting21:20
rledisezthat's all for me about that21:20
timburkei wonder how crazy it'd be to always use footers and have someone pretty far left (like, gatekeeper or something) be responsible for validating the client data and storing the etag... then have everything else punt to a crc or something lighter-weight...21:21
rledisezit's exactly what i'm building. I wrote it that way in the etherpad.21:22
timburkewe need more hours in the day! at least, that's usually *my* problem ;-)21:22
timburke#topic RFC-compliant etags21:23
*** openstack changes topic to "RFC-compliant etags (Meeting topic: swift)"21:23
timburkeso i've got a patch to enable it cluster-wide, but it sounds like rledisez might have a separate middleware that would allow finer-grained control...21:23
timburkei haven't seen that patch yet, though ;-)21:24
rlediseztimburke: I totally forgot to push it. i'll put a reminder for tomorrow21:24
timburkethanks! it doesn't have to be perfect -- i'd be happy to help polish docs or tests or what-have-you :D21:25
rledisezit's "run-in-prod" polished, no more ;)21:25
timburkei just had one other thing i wanted to draw attention to, this time with a little more time for discussion :-)21:25
timburke#topic ranged SLO reads21:26
*** openstack changes topic to "ranged SLO reads (Meeting topic: swift)"21:26
*** rf0lc0 has joined #openstack-meeting21:26
*** rf0lc0 has quit IRC21:26
timburkeso we had a customer complaining about latency variations21:26
timburkeas i was helping look into it, i noticed that ranged SLO reads have this funny request pattern:21:27
timburkeproxy sends the range request down to the object server21:27
timburkeobject server just has a manifest, so it responds 416 (that range is way off the end of the thing!)21:27
zaitcevI presume this is replicated, but go on.21:27
timburke(good point; yes, though the range manipulations we do for EC mean you get much the same behavior)21:28
timburkeproxy says, well, no, actually i want that *whole manifest*!21:28
timburkeobject server sends it back21:28
timburkeproxy finds the appropriate segment, requests *that*21:29
timburkeobject server sends it back, and we can actually start serving users21:29
timburkei set out to get rid of that 416-refetch behavior and just have the object-server send the whole manifest from the get-go21:30
zaitcevWait, how does proxy know that it's an SLO object to begin with.21:30
zaitcevOf course it asks for a range first.21:30
timburkei think i designed my solution fairly smartly; it adds a new, not-slo-specific header to tell the object server "hey, if you see any of these pieces of metadata, ignore the range header i sent"21:31
zaitcevoh, nice21:31
timburkethen has slo add X-Static-Large-Object to that list21:31
zaitcevor.... you could _always_ ignore range for manifests21:32
timburkei was thinking that i don't really want object-server to need to know *more* about large objects -- we've already seen how much trouble it is that they have to know about swift_bytes, for example21:32
timburkei was mostly inspired by the x-backend-etag-is-at behavior we already have21:33
timburkethere is a wart, though, that i'm not sure i like: the EC obj controller (currently) pops off the Range header so that swob behaves itself when it makes the response21:34
timburkeso i guess i'm wondering: has anyone else seen this behavior or had users complain about it?21:36
timburkedoes this design seem reasonable?21:36
timburkeand are we ok with that wart? (even in this patch, it means that SLO has to grab the range itself before it calls down to the app, just so it can replace it later...)21:37
zaitcevI did not notice, but that's because I barely have any SLOs at all. It sounds completely plausible for the reasons of a-priori information that I just mentioned.21:37
mattoliverauI like the approach, re: generic header and middleware can add to it, smart. I guess I need to look to understand the wart some more21:38
timburkei tried to capture it in the commit message; you can also see the consequence of it in https://review.opendev.org/#/c/697739/3/swift/common/middleware/slo.py21:39
mattoliverauCool, I'll check it out21:40
timburkethanks! i'll see about getting that save/restore logic out to the EC controller, too... i feel like that should be doable, and it'd remove my only real concern21:41
timburkethat's all i've got21:41
timburke#topic open discussion21:41
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:41
*** dviroel has quit IRC21:41
timburkewhat else would people like to bring up?21:41
timburkeall right, looks like we can let mattoliverau, tdasilva, and seongsoocho grab some breakfast ;-)21:43
timburkethank you all for coming, and thank you for working on swift!21:44
timburketalk to you all next year :-)21:44
timburke#endmeeting21:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:44
openstackMeeting ended Wed Dec 18 21:44:19 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-12-18-21.01.html21:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-12-18-21.01.txt21:44
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-12-18-21.01.log.html21:44
mattoliverauThanks timburke21:44
*** zaitcev has left #openstack-meeting21:49
*** dtroyer has joined #openstack-meeting21:52
*** pcaruana has quit IRC21:54
*** alecuyer has left #openstack-meeting22:03
*** jamesmcarthur has quit IRC22:04
*** bbowen has quit IRC22:05
*** mattw4 has quit IRC22:07
*** mattw4 has joined #openstack-meeting22:10
*** haleyb has quit IRC22:22
*** haleyb has joined #openstack-meeting22:26
*** rbudden has quit IRC22:31
*** bbowen has joined #openstack-meeting22:34
*** mriedem has quit IRC22:51
*** mattw4 has quit IRC22:51
*** mattw4 has joined #openstack-meeting22:59
*** rcernin has joined #openstack-meeting23:10
*** rbudden has joined #openstack-meeting23:25
*** mattw4 has quit IRC23:40
*** mattw4 has joined #openstack-meeting23:40
*** mattw4 has quit IRC23:45
*** yamamoto has joined #openstack-meeting23:46
*** mattw4 has joined #openstack-meeting23:46

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