Wednesday, 2020-01-15

*** rfolco has quit IRC00:06
*** macz has quit IRC00:32
*** ricolin has joined #openstack-meeting00:37
*** anastzhyr has quit IRC00:52
*** Liang__ has joined #openstack-meeting01:13
*** Liang__ is now known as LiangFang01:14
*** jamesmcarthur has joined #openstack-meeting01:37
*** jamesmcarthur has quit IRC01:44
*** hongbin has joined #openstack-meeting02:02
*** hongbin has quit IRC02:02
*** hongbin has joined #openstack-meeting02:03
*** hongbin has quit IRC02:03
*** hongbin has joined #openstack-meeting02:04
*** hongbin has quit IRC02:04
*** hongbin has joined #openstack-meeting02:06
*** mhen has quit IRC02:18
*** jamesmcarthur has joined #openstack-meeting02:25
*** jamesmcarthur_ has joined #openstack-meeting02:28
*** jamesmcarthur has quit IRC02:28
*** macz has joined #openstack-meeting02:30
*** macz has quit IRC02:35
*** rmk has quit IRC03:32
*** rmk has joined #openstack-meeting03:35
*** gyee has quit IRC03:56
*** jamesmcarthur_ has quit IRC04:08
*** jamesmcarthur has joined #openstack-meeting04:10
*** hongbin_ has joined #openstack-meeting04:12
*** hongbin has quit IRC04:15
*** macz has joined #openstack-meeting04:30
*** macz has quit IRC04:34
*** hongbin_ has quit IRC04:37
*** jamesmcarthur has quit IRC04:43
*** jamesmcarthur has joined #openstack-meeting04:44
*** jamesmcarthur has quit IRC04:50
*** jamesmcarthur has joined #openstack-meeting05:15
*** jamesmcarthur has quit IRC05:23
*** etp has left #openstack-meeting05:38
*** jamesmcarthur has joined #openstack-meeting05:57
*** jamesmcarthur has quit IRC06:02
*** davee___ has joined #openstack-meeting06:04
*** davee_ has quit IRC06:06
*** mugsie has quit IRC06:11
*** mugsie has joined #openstack-meeting06:14
*** jamesmcarthur has joined #openstack-meeting06:36
*** jamesmcarthur has quit IRC06:42
*** dmsimard has quit IRC06:50
*** dmsimard has joined #openstack-meeting06:54
*** apetrich has quit IRC07:11
*** masahito has joined #openstack-meeting07:12
*** davee__ has quit IRC07:16
*** davee_ has joined #openstack-meeting07:16
*** masahito has quit IRC07:17
*** ralonsoh has joined #openstack-meeting07:27
*** jamesmcarthur has joined #openstack-meeting07:38
*** jamesmcarthur has quit IRC07:43
*** e0ne has joined #openstack-meeting07:54
*** e0ne has quit IRC07:54
*** e0ne has joined #openstack-meeting07:54
*** anastzhyr has joined #openstack-meeting07:56
*** belmoreira has joined #openstack-meeting07:57
*** tesseract has joined #openstack-meeting07:58
*** tesseract has quit IRC07:58
*** tesseract has joined #openstack-meeting07:59
*** maciejjozefczyk has joined #openstack-meeting08:06
*** slaweq has joined #openstack-meeting08:09
*** e0ne has quit IRC08:11
*** e0ne has joined #openstack-meeting08:11
*** Luzi has joined #openstack-meeting08:14
*** e0ne has quit IRC08:15
*** rpittau|afk is now known as rpittau08:22
*** jamesmcarthur has joined #openstack-meeting08:39
*** jamesmcarthur has quit IRC08:45
*** dmellado has quit IRC08:51
*** mdelavergne has joined #openstack-meeting08:54
*** dmellado has joined #openstack-meeting08:55
*** oneswig has joined #openstack-meeting08:57
*** etp has joined #openstack-meeting08:59
belmoreira#startmeeting large_scale_sig09:00
openstackMeeting started Wed Jan 15 09:00:20 2020 UTC and is due to finish in 60 minutes.  The chair is belmoreira. 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
amorinhello!09:00
belmoreiraHello everyone. Welcome to the Large Scale SIG meeting.09:00
oneswighello!09:00
belmoreira#topic Rollcall09:00
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"09:00
oneswigo/09:00
belmoreirao/09:01
etpo/09:01
amorino/09:01
belmoreiragreat. let's start with our first topic09:02
belmoreira#topic "Scaling within one cluster" goal09:02
*** openstack changes topic to ""Scaling within one cluster" goal (Meeting topic: large_scale_sig)"09:02
belmoreira#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling09:02
belmoreiraThere's no much progress in the etherpad09:03
oneswigAfraid not.  Over here we are making slow progress towards improving instrumentation.09:03
belmoreiraoslo.metrics blueprint is a great idea09:04
belmoreiralet's wait for masahito feedback in the draft blueprint09:05
oneswigI think it ties in well with a fishbowl session from Shanghai, advocating exposing metrics from each service.09:05
belmoreiraBut this only focus in collecting metrics09:06
belmoreiraI'm sure we can expand this more09:06
belmoreiraI'm thinking about interaction with other services. Like Placement and how it's deployed09:07
belmoreiradoes it make sense?09:07
oneswigbelmoreira: can you elaborate?09:08
belmoreirain my opinion scaling one nova cell is more than just rabbit and DB. For example, Nova interacts with placement and neutron and in my view we should focus in those scaling limits as well.09:10
*** masahito has joined #openstack-meeting09:11
belmoreiraalso, being only one cell, how the different components are deployed (shared rabbit or not - for example) will affect the scalability of the deployment09:11
masahitoSorry to be late. My IRC client doesn't work well :-(09:11
oneswighi masahito09:11
belmoreirawelcome masahito09:11
masahitohello o/09:12
belmoreiraoneswig does it make sense?09:12
oneswigbelmoreira: is there any study on the growth rate of placement as a function of number of hypervisors?  It could be polynomial (ie really bad)...09:12
oneswigbelmoreira: makes sense to me.09:13
mdelavergne(hi, sorry for being late) I think it is definitely relevant to consider the placement and network09:13
belmoreirafor example: placement is linear, but the number of requests that it can handle will change considering how it's deployed and options09:14
oneswig#link discussion from Shanghai on common monitoring via oslo https://etherpad.openstack.org/p/PVG-bring-your-crazy-idea09:14
oneswigunfortunately there are no actions or follow-up in that etherpad09:15
belmoreirait's not that crazy to me. It would be very cool.09:16
*** lucasagomes has joined #openstack-meeting09:16
belmoreiramasahito do you have any update regarding the oslo.metric blueprint09:17
masahitoNot much update.09:17
masahitobecause of some outage in our cluster :-(09:17
*** lucasagomes has left #openstack-meeting09:17
masahitoBut I want to finish to write the first draft by end of January.09:18
oneswigwas thinking of your talk about LINE yesterday - had a rabbitmq issue on a system here09:18
belmoreiraThanks masahito. Let us know.09:19
belmoreiraoneswig related with scalability?09:19
oneswignot this time, only moderate scale09:20
oneswigwould have been timely otherwise :-)09:20
belmoreiraanyone as something else related to this topic?09:20
belmoreiraLet's continue to update the etherpad with our experiences in scaling one nova cell.09:21
*** apetrich has joined #openstack-meeting09:21
belmoreiramoving to the next topic in the agenda09:22
belmoreira#topic Progress on "Documenting large scale operations" goal09:22
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"09:22
belmoreiraamorin started a thread in the mailing list to document the particular configuration that makes important for large scale deployments09:22
belmoreirathanks09:22
amorinyes09:22
belmoreira#link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011820.html09:22
belmoreira#link https://etherpad.openstack.org/p/large-scale-sig-documentation09:22
amorinI got an answer from slawek (neutron PTL)09:23
amorinhere created a neutron bug: https://bugs.launchpad.net/neutron/+bug/185841909:23
openstackLaunchpad bug 1858419 in neutron "Docs needed for tunables at large scale" [Medium,Confirmed] - Assigned to Slawek Kaplonski (slaweq)09:23
amorinjust like mriedman did for nova09:23
amorinso we can collect the tunings over there09:23
amorinthey also notify us about rabbit and DB params09:23
amorinwhich I believe are important also09:24
slaweqamorin: hi, yes and we have some input from liuyulong who is neutron core and has a lot of large scale deployment experience also09:24
slaweqso we need to start working on some patches based on those comments09:24
amorinyup09:24
slaweqand also if You have anything to add there, feel free to write comments or send patches related to this bug :)09:24
oneswigsounds great!09:25
amorinI am pretty sure I can find some tunings based on OVH experience, I will try to do that09:26
belmoreiraThis is great. Thank you amorin slaweq09:26
etpsounds good09:26
amorinAlso, I proposed to do some documentation change to identify parameters which could affect large scale09:26
slaweqamorin: I know You will :)09:26
amorinwhat do you think about this?09:27
etpbtw has anyone compared different generally available neutron plugins ovs/ovn/...?09:27
amorinI havnt, on our side we use custom plugins based on OVS09:28
amorinmaybe slaweq know if OVN is able to scale?09:28
oneswigOnly for performance.09:28
slaweqamorin: I know there were some tests of ovn on scale done by networking-ovn team09:28
belmoreiraetp definitely that is interesting. It would be great to know more09:28
slaweqI can try to search for them if You want to check them09:29
etpi noted that there's spec in Ussuri to move reference from ovs to ovn09:29
slaweqetp: no, for Ussuri are only moving networking-ovn code to be in-tree neutron driver09:29
etpah, maybe I misread it :)09:30
slaweqbut in the future we will probably want to switch our "default" backend to be ovn instead of ovs-agent09:30
slaweqbut not in Ussuri for sure09:30
belmoreiraI just added in the etherpad a presentation about CERN network deployment and the configuration options that we use. Will cross check to what is proposed. In our case we use linux bridge09:31
amorinack09:31
etpslaweq: we are also looking in to same direction, when it happens remains to be seen09:31
slaweqetp: yes09:32
etpbelmoreira: tnx09:32
slaweqIf I will have link to any comparison between ovn and other backends I will place it in etherpad https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling09:32
slaweqok?09:32
belmoreiraplease do09:33
amorinyes, thanks09:33
belmoreirashould we have the same approach with other projects? like keystone, placement, glance?09:34
belmoreirahave a bug open for relevant options for large deployments?09:34
amorinI think it could be nice, but it should come from them, we can force them09:35
amorinwe cant*09:35
amorinsorry09:35
oneswigI had an action item to poll the Scientific SIG for data points.  I'll add it to today's meeting (at 1100 UTC)09:36
belmoreiraamorin: ok, let's try to signal issues first in the etherpad09:37
belmoreiraoneswig thanks09:37
amorinyes09:37
belmoreiraanything else related to this topic?09:37
*** tonyb has joined #openstack-meeting09:38
belmoreiramoving on09:38
belmoreira#topic AOB09:38
*** openstack changes topic to "AOB (Meeting topic: large_scale_sig)"09:38
belmoreiraIs there something else that you would like to discuss?09:39
amorinnot on my side09:40
oneswignot for me09:40
belmoreira#topic Next Meeting09:40
*** openstack changes topic to "Next Meeting (Meeting topic: large_scale_sig)"09:40
masahitonot from my side09:41
*** jamesmcarthur has joined #openstack-meeting09:41
belmoreiraIf we follow the 2 weeks rule the next meeting will be on January 29. Is this OK?09:41
oneswig+109:41
masahito+109:41
amorin+109:41
masahitols09:41
mdelavergne+109:42
belmoreira#agreed next meeting: January 29, 9utc #openstack-meeting09:42
belmoreiraAnything else before we close the meeting?09:42
oneswighave to go, thanks everyone09:42
*** pcaruana has joined #openstack-meeting09:42
belmoreiraThanks everyone09:42
oneswigps it's on the agenda now https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_15th_202009:43
mdelavergnethanks09:43
masahitothanks, all09:43
etpthanks all09:43
belmoreira#endmeeting09:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:43
openstackMeeting ended Wed Jan 15 09:43:21 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-15-09.00.html09:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-15-09.00.txt09:43
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-15-09.00.log.html09:43
amorinthanks!09:43
*** jamesmcarthur has quit IRC09:46
*** mdelavergne has left #openstack-meeting09:55
*** LiangFang has quit IRC09:58
*** e0ne has joined #openstack-meeting10:07
*** jamesmcarthur has joined #openstack-meeting10:42
*** masahito has quit IRC10:43
*** simon-AS5591 has joined #openstack-meeting10:45
*** mattia has joined #openstack-meeting10:45
*** jamesmcarthur has quit IRC10:46
*** dh3 has joined #openstack-meeting10:59
*** janders has joined #openstack-meeting10:59
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Jan 15 11:00:15 2020 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.11:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:00
openstackThe meeting name has been set to 'scientific_sig'11:00
oneswigSIG time!11:00
*** witek has joined #openstack-meeting11:00
oneswig#link Today's agenda https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_15th_202011:00
oneswiggreetings all11:00
jandersg'day all11:00
dh3morning!11:01
jandersHappy New Year 202011:01
oneswigjanders: saw your presentation from kubecon last week, nice work!11:01
jandersoneswig: thank you! :)11:01
jandersit was a great conference11:01
oneswigclarification - kubecon last november, saw it last week11:01
oneswigdid you get many questions in follow-up?11:01
jandersjust a few.. now I'm thinking if I replied :)  was pretty hectic end of the year11:02
oneswig#link Janders at Kubecon https://www.youtube.com/watch?v=sPfZGHWnKNM11:02
oneswigSo many moving parts though!  Does it hold together?11:03
mattiahello everyone11:03
oneswigHi mattia, welcome11:03
jandersit does - and it's getting better :)  waiting for some kit to arrive and hope to test 100GE version and HDR200 version of RDMA-K8s11:04
jandersit's still early days though11:04
oneswigHave you looked at options for PMIX so MPI jobs can sit on top?11:04
jandersno, not yet11:05
jandersI was mostly thinking connecting to non-k8s storage and GPU workloads. I'm sure MPI workloads will bubble up too though11:06
oneswigIt seems a lot less straightforward than putting containers into a Slurm environment.  But with the energy going into it I'm sure a workable solution will appear11:07
oneswig#link PMIX and kubernetes hinted to here https://pmix.org/wp-content/uploads/2019/04/PMIxSUG2019.pdf11:07
oneswigjanders: big numbers for your storage bandwidth at the end of the presentation11:08
jandersit's still work in progress but in a scenario where a fair chunk of workloads is cloud-native and MPI is a small fraction I think this approach makes good sense11:08
*** melwitt has quit IRC11:09
oneswigyes - that looks like the use case11:09
oneswig... I'm sure we had an agenda somewhere ... oops11:09
jandersthat was actually from our OpenStack system, but when I get more kit I hope to see these in k8s containers as well11:09
oneswigbe interesting to know where you take it next11:10
janderswe're getting close to going live with the cyber system so my bosses aren't to keen with me testing on the same kit11:10
jandersi have some interesting (I hope) questions on that - but let's leave that for AOB11:10
oneswigcurse those production obligations!11:10
jandershaha! :)11:10
oneswigOK, time to start11:10
jandersI keep saying ops focused guys they are no fun11:10
oneswig#topic OpenStack board elections11:11
*** openstack changes topic to "OpenStack board elections (Meeting topic: scientific-sig)"11:11
oneswigJust a quick reminder to vote for individual directors this week11:11
oneswigI'd share a link but I think they are all somehow individual11:12
*** pcaruana has quit IRC11:12
oneswigThat's all on that :-)11:12
oneswig#topic Large-Scale SIG survey11:12
*** openstack changes topic to "Large-Scale SIG survey (Meeting topic: scientific-sig)"11:12
oneswigEarlier this morning there was a Large Scale SIG meeting11:13
oneswigThere don't appear to be minutes for it on Eavesdrop...11:13
oneswigaha http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-15-09.00.html11:14
oneswig#link request for data on large-scale configuration http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011820.html11:14
dh3Thanks, I missed that (feeling I'm spread a bit thin at the moment) - not that we are *so* large as some11:15
*** anastzhyr has quit IRC11:15
oneswigHi dh3, everything is relative I guess!11:16
oneswigThe Large Scale SIG are hoping for input on scaling issues faced in real-world experiences.11:17
oneswig(and what tools to tackle them)11:17
oneswig#link Large Scale SIG etherpad https://etherpad.openstack.org/p/large-scale-sig-documentation11:17
jandersDB, AMQP, Neutron... guessed 3/3 and the order, too :)11:19
oneswigjanders: low-hanging fruit that :-)11:20
janderswith other APIs it's probably easier to just deploy more API nodes than to optimise... to a degree that is - and that assumes DB scaling is sorted out separately :)11:20
oneswigOne interesting starting point was the idea to create an Oslo module for standardising telemetry from OpenStack services, and making it available as prometheus or statsd11:21
jandersvery prom(eth)ising11:21
oneswigoh, good :-)11:21
oneswigI don't think there's a spec for review yet but I think its underway11:22
jandersI think scalable telemetry was one of the PITA/WTF areas of OpenStack for quite a while so this sounds awesome11:23
jandersI got quite far with just switching it off but that's not good either11:23
dh3is the intention that this data is for developers or operators? (or both) and if devs, has anyone thought about "phone home" reporting like Ceph added recently?11:24
oneswigjanders: indeed.11:24
oneswigdh3: I think it's for operators principally, but I expect there's a symbiosis where operators have the pain points and use this as evidence for developers, perhaps.11:25
oneswigIf people are interested they can encourage this effort by adding their support to the etherpad!11:26
jandersRHATs are pumping a fair bit of effort into SAF11:26
dh3OK. For operators there is a downstream process where - having received some data or telemetry trend or errors - they need to decide what to do about it (not necessarily being an expert in tuning MySQL or RabbitMQ or ...)11:26
janders("Service Assurance Framework")11:27
dh3I will try to get some coherent thoughts onto the etherpad.11:27
jandersI wonder if the two directions could be combined11:27
oneswigjanders: what's that?11:27
oneswigThe lauchpad tickets on gathering config parameters that are important for scale may be worth a look11:27
jandersOpenShift/K8S powered, Prometheus based OpenStack monitoring11:27
dh3embarrassed to say I had not met SAF and we have RHOSP11:27
oneswigNova https://bugs.launchpad.net/nova/+bug/1838819 Neutron https://bugs.launchpad.net/neutron/+bug/185841911:28
openstackLaunchpad bug 1838819 in OpenStack Compute (nova) "Docs needed for tunables at large scale" [Undecided,Confirmed]11:28
openstackLaunchpad bug 1858419 in neutron "Docs needed for tunables at large scale" [Medium,Confirmed] - Assigned to Slawek Kaplonski (slaweq)11:28
jandersit's on my TODO list but due to resourcing constraints our first monitoring solution for the cyber system is gonna be Nagios11:28
jandersSAF looks quite good though11:28
oneswiggot a link?11:28
jandersand its getting a lot of good press from the Brisbane support guys who are real OpenStack gurus, hats off to them11:29
jandersif they say its good im totally gonna try it11:29
janders(looking it up)11:29
dh3I found https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/service_assurance_framework/introduction-to-service-assurance-framework_assembly (not sure if there's a free/OSS side?)11:29
oneswiglooks like it's purely a RHOSP thing11:29
jandersyes it is but I'd be surprised if it doesn't have a good upstream11:30
oneswigThe data at source does sound like it would be the same though11:30
jandersI cant find public link - would you like doco from KB over email?11:30
dh3janders: anything you can share will be interesting (though we are likely to move off RH at some point so wary of lockin)11:31
oneswigThanks janders, one to watch11:31
witekhttps://github.com/redhat-service-assurance/telemetry-framework11:31
oneswigHi witek, welcome!11:31
oneswigand thanks for the link11:31
witekthey have presented it first time at the summit in Berlin11:31
jandersdh3: what's the best email to send it to?11:32
dh3janders: dh3@sanger.ac.uk please11:32
dh3witek: thanks, I will look up the talk11:32
jandersoneswig: dh3: done11:33
dh3thanks, on first skim it looks the same as the access.redhat.com docs, I will find a quiet corner to read it this afternoon11:35
jandersyeah that's the source11:36
jandersI reviewed this with my monitoring expert and we figured it's worth a go, might be a good solution going forward11:36
oneswigIf more telemetry data is made available via standard protocols, everyone wins11:36
jandersbut it's too complex to be deployed as the initial monitoring solution for our cyber system11:36
witekit follows similar architecture as Monasca11:38
oneswigI should perhaps rtfm but I wonder what SAF are doing for the limitations around eg retention policies in prometheus11:38
oneswigjanders: do they have a story for logs and notifications?11:39
jandersspeaking of OSP, 16 is out in beta11:39
jandersnotifications - yes, I believe so11:39
janderslogs - in what sense?11:39
oneswigyou know, like syslog11:40
janderslogstash/elasticsearch kind of stuff?11:40
oneswigyep11:40
jandersI think they do this via collectd somehow but this part I'm less familiar with11:40
oneswigsounds like when they get there they will have reinvented much of what monasca does today ;-)11:41
janders:)11:41
jandersas long as the wheel is still round, a little reinvention is tolerable even if not optimal11:41
oneswiganyway, should move on I guess.  Final comments on large scale?11:42
jandersnothing specific just big +1 for the initiative11:42
dh3likewise11:42
jandersI think there was a need for this for a very long time11:42
oneswigsure, I think so too11:43
*** jamesmcarthur has joined #openstack-meeting11:43
oneswig#topic events for 202011:43
*** openstack changes topic to "events for 2020 (Meeting topic: scientific-sig)"11:43
janderson that... do you guys know what's the CFP timeframe for Vancouver?11:43
oneswigOK y'all, lets get some links out for events coming up...11:43
oneswigjanders: not heard, nor checked11:43
jandersi looked around but haven't managed to find any info11:44
dh3we were talking about conferences in the office this morning. wondering when the European summit dates/location might be announced. and a bit sad there are no upcoming OpenStack Days listed11:44
jandersit feels like that's typically Jan-Feb for the May conferences11:44
jandersthis year NA event is bit later so perhaps so is CFP11:44
oneswig#link UKRI Coud Workshop (London) https://cloud.ac.uk/11:44
oneswigCFP closing date for that is end of Jan I think11:45
jandersis there anything interesting coming up for ISC2020? I was asked by my boss if I wanna go11:46
oneswigI know the group who did SuperCompCloud at SC2019 have a similar workshop planned (CSCS in Switzerland, Indiana University, maybe others)11:46
dh3we had the Arista conference ("Innovate") and Lustre LUG/LAD on our radar11:47
jandersat least OIS Vancouver and ISC20 don't overlap (but are close enough to make it tricky for us Aussies to attend both)11:47
*** jamesmcarthur has quit IRC11:48
oneswigjanders: I'm expecting to go to ISC 2020, hopefully see you there.11:50
jandersthat would be great! :)11:50
jandersare you likely headed to Vancouver as well?11:50
oneswigI expect so, provided they aren't the same week :-)11:51
janderslooks like they are not :)11:51
oneswigNot planning on Cephalocon though - Seoul in March https://ceph.io/cephalocon/11:51
oneswig#link HPCAC Swiss Workshop in April is also good https://www.hpcadvisorycouncil.com/events/2020/swiss-workshop/11:52
oneswigdh3: where do cloud-oriented bioinformaticions go for conferences?11:53
dh3oneswig: I'm not sure that the cloud emphasis affects the choice of conference but I will ask around11:55
jandersas we're nearing the end of the hour I have some AOB11:56
oneswig#topic AOB11:56
dh3other than some of platform-oriented things like Kubecon maybe have a bit more of an application focus than say the OpenStack summit11:56
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:56
oneswigwell spotted :-)11:56
jandersdo you have much experience with cinder volume transfers?11:56
jandersI'm thinking using this as a tool for devsecops guys to make malware samples available to cyber researchers11:56
dh3we tried it several releases back and it "just worked" but we didn't have a use case/user story for it11:57
dh3for small scale (malware samples are small right) I might look at image sharing instead?11:57
janders1) people upload encrypted malware to secure dropbox 2) devsecops guys have a VM that sits on the same provider network as the dropbox and they create a volume, attach it and copy encrypted malware in 3) they give the volume to the researcher11:58
jandersI need a more fancy backend setup than glance can offer11:58
*** dviroel has joined #openstack-meeting11:58
janderswith cinder I can have separate pools for normal and disco volumes11:58
jandersi tried transfers today and it *just worked*11:59
oneswigI've used rbd export to effectively dd out a running volume before11:59
jandersif you guys have no horror stories how it breaks terribly in some corner cases I think I will endorse this solution11:59
oneswignot used a cinder method before though11:59
jandersok! thanks oneswig12:00
dh3rbd export works for us (in "trying circumstances" too)12:00
oneswiggood luck with it janders!12:00
jandersthanks and I will report back12:00
oneswigok, time to close, thanks everyone12:00
jandersthank you all12:00
oneswig#endmeeting12:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"12:00
openstackMeeting ended Wed Jan 15 12:00:40 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-15-11.00.html12:00
dh3thanks, bye12:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-15-11.00.txt12:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-15-11.00.log.html12:00
*** oneswig has quit IRC12:02
*** simon-AS559 has joined #openstack-meeting12:03
*** rfolco has joined #openstack-meeting12:06
*** simon-AS5591 has quit IRC12:06
*** janders has quit IRC12:18
*** ociuhandu has joined #openstack-meeting12:26
*** jamesmcarthur has joined #openstack-meeting12:44
*** pcaruana has joined #openstack-meeting12:49
*** jamesmcarthur has quit IRC12:49
*** enriquetaso has joined #openstack-meeting12:55
*** ociuhandu has quit IRC12:59
*** jamesmcarthur has joined #openstack-meeting13:15
*** witek has quit IRC13:20
*** eharney has quit IRC13:20
*** jamesmcarthur has quit IRC13:24
*** jamesmcarthur has joined #openstack-meeting13:24
*** ociuhandu has joined #openstack-meeting13:27
*** ykatabam has quit IRC13:32
*** jamesmcarthur has quit IRC13:36
*** liuyulong has joined #openstack-meeting13:41
*** Liang__ has joined #openstack-meeting13:45
*** jamesmcarthur has joined #openstack-meeting13:47
*** mnaser has quit IRC13:54
*** mnaser has joined #openstack-meeting13:55
liuyulong#startmeeting neutron_l314:00
*** rfolco has quit IRC14:00
openstackMeeting started Wed Jan 15 14:00:37 2020 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
liuyulonghi there14:01
slaweqhi14:01
*** Liang__ is now known as LiangFang14:01
*** rfolco has joined #openstack-meeting14:01
liuyulong#topic Announcements14:01
*** eharney has joined #openstack-meeting14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:01
*** sfernand has joined #openstack-meeting14:02
liuyulongAll things were mentioned during neutron team meeting yesterday.14:03
liuyulongSo I guess we can move on then?14:03
*** rcernin has quit IRC14:04
liuyulongOK, let's move on.14:04
liuyulong#topic Bugs14:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:04
*** andrebeltrami has joined #openstack-meeting14:04
liuyulong[neutron] Bug deputy report - Jan 06 to 1214:05
liuyulong#link http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011955.html14:05
liuyulongLet's revisit this bug first.14:05
liuyulong#link https://bugs.launchpad.net/neutron/+bug/177445914:06
openstackLaunchpad bug 1774459 in neutron "Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,In progress] - Assigned to Brian Haley (brian-haley)14:06
ralonsohhi14:06
*** rsimai_away is now known as rsimai14:06
liuyulong#link https://review.opendev.org/#/c/601336/14:06
liuyulong^ this is the fix of the bug.14:06
liuyulong#link https://review.opendev.org/#/c/653883/14:07
liuyulongThis should be related to the bug and fix.14:07
liuyulongI've tested this with some new based on the problem we met locally. So I created a new bug https://bugs.launchpad.net/neutron/+bug/185963814:08
openstackLaunchpad bug 1774459 in neutron "duplicate for #1859638 Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,In progress] - Assigned to Brian Haley (brian-haley)14:08
*** vkmc has quit IRC14:09
*** vkmc has joined #openstack-meeting14:09
haleybhi14:10
liuyulongAnd back to fix, I've left some comments. Some of them are technical issues, IMO, it should be addressed.14:11
haleybimho #link https://review.opendev.org/#/c/653883/ is ready to merge14:12
liuyulonghaleyb, yes, looks good to me.14:13
haleybi see your comments on the other one, i've had no time to get back to it recently14:14
*** dh3 has quit IRC14:14
liuyulonghaleyb, sure, we can continue the details in the gerrit.14:15
haleybor if anyone has more cycles... i was hoping it was a quick update but doesn't look it14:16
liuyulongBesides I also have an idea to fix the bug when we have no GARP from users VM.14:16
liuyulongL2pop and ARP responder will not be considered, ARP request and reply will be flooded to tunnels... (Bad news...)14:19
*** jungleboyj has quit IRC14:20
liuyulongARP reply will be sent to local qr-device and flood to tunnels at same time. Then all routers will be aware of the allowed address mac.14:21
*** jungleboyj has joined #openstack-meeting14:21
liuyulongOK, I will summary these comments to the LP bug or gerrit.14:27
liuyulongNext one:14:28
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185866114:28
openstackLaunchpad bug 1858661 in neutron "Error when creating a Linux interface" [High,Confirmed]14:28
liuyulongslaweq, ralonsoh any updates about this ?14:28
ralonsohliuyulong, no sorry, I didn't have time14:29
ralonsohmaybe tomorrow14:29
slaweqme neighter14:29
liuyulongIt blocks the CI in high failure rate, or not?14:30
ralonsohsometimes yes, but this is not a repetitive error14:31
liuyulongAlright, not 100% is good news. And we also have this from the deputy bug list:14:32
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185864214:32
openstackLaunchpad bug 1858642 in neutron "paramiko.ssh_exception.NoValidConnectionsError error cause dvr scenario jobs failing" [High,Confirmed]14:32
ralonsohyes, I'm on it now14:32
liuyulongOK, all these issues can be discussed during CI meeting in details later.14:36
liuyulongNext one14:36
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185916314:36
openstackLaunchpad bug 1859163 in neutron "Create port with fixed ipv6 address for non-router ports is not allowed anymore" [Medium,Fix committed] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:36
liuyulongJust updated the status of the bug, it is fixed.14:37
liuyulong#link https://review.opendev.org/#/c/701965/14:37
ralonsohcool!14:37
ralonsohwaiting for the gate14:37
liuyulongNext one14:37
liuyulong#link sometimes yes, but this is not a repetitive error14:37
liuyulong#undo14:38
openstackRemoving item from minutes: #link sometimes14:38
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185841914:38
openstackLaunchpad bug 1858419 in neutron "Docs needed for tunables at large scale" [Medium,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:38
*** jamesmcarthur has quit IRC14:40
liuyulongAgain, I'm now revisit those patches of scale issues have the config options.14:40
liuyulong#link https://review.opendev.org/#/c/364793/14:40
liuyulongThis can be an example.14:40
slaweqthx liuyulong for working on this14:41
liuyulongslaweq, np14:42
*** artom has joined #openstack-meeting14:42
liuyulongThat's all from the deputy list. Let's shot a quick scan of LP bug list.14:42
*** lseki has quit IRC14:44
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185808614:44
openstackLaunchpad bug 1858086 in neutron "qrouter's local link route cannot be restored " [Medium,Confirmed]14:44
*** diablo_rojo_phon has quit IRC14:44
*** lseki has joined #openstack-meeting14:44
liuyulongAssigned to me now, I will try to fix it in neutron-server API to disable such route update.14:45
slaweqif You are changing API You should add new api extension to make this change discoverable14:45
ralonsoheven if this is an error?14:45
slaweqralonsoh: I think so14:45
ralonsoh(just asking)14:45
ralonsohperfect14:46
slaweqas we are changing API behaviour14:46
slaweqso e.g. we will not be able to test it in tempest properly14:46
slaweq(potentially)14:46
slaweqso it should be probably some shim extension but still we will need that14:46
liuyulongSure14:47
liuyulongNo more bugs from me now. Any updates?14:47
ralonsohno14:47
slaweqI have one new14:48
slaweqhttps://bugs.launchpad.net/neutron/+bug/185983214:48
openstackLaunchpad bug 1859832 in neutron "L3 HA connectivity to GW port can be broken after reboot of backup node" [Medium,New] - Assigned to Slawek Kaplonski (slaweq)14:48
slaweqreported just before this meeting14:48
slaweqI'm working on some fix for this14:48
slaweqbut for now only fix which I have in mind requires changes in both L3 and ovs agent14:48
*** diablo_rojo_phon has joined #openstack-meeting14:49
*** electrofelix has joined #openstack-meeting14:49
slaweqand also second thing14:50
slaweqI yesterday sent patch https://review.opendev.org/#/c/702547/ which is (I hope) fix for old issue with dvr routers14:50
slaweqplease review it when You will have some time14:50
ralonsohsure14:50
slaweqand that's all from my side14:50
liuyulongLooks like the GARP issue for bug 1859832.14:50
openstackbug 1859832 in neutron "L3 HA connectivity to GW port can be broken after reboot of backup node" [Medium,New] https://launchpad.net/bugs/1859832 - Assigned to Slawek Kaplonski (slaweq)14:50
slaweqliuyulong: not GARP but MLDv2 packets14:51
slaweqas it's related to IPv6 strictly14:51
liuyulongyes, no matter which type of packets, the gateway mac will be refreshed to "backup" node in physical switch.14:52
slaweqliuyulong: exactly14:53
slaweqI was trying to describe as clear as I possible the issue in bug report14:53
slaweqI hope it will be clear for You what's going on there14:53
slaweqbut if not, I can try to explain it e.g. on IRC if You will have any questions14:54
liuyulongI have a simple way to verify this issue.14:54
liuyulongWhen you have centralized floating IPs in the snat gateway, you can use "neutron l3-agent-router-add" to add a new HA member to the router, to see if the floating IP traffic is broken.14:56
slaweqliuyulong: but it's race and it can happen only sometimes14:57
slaweqso it's possible that on not overloaded system when You are adding only one router, it will be fine14:57
liuyulongThe way I mentioned can 100% reproduce the problem.14:57
*** macz has joined #openstack-meeting14:57
slaweqbut in general it's true what You said, it can break in such case14:57
liuyulongSo you have any idea to fix the issue?14:58
slaweqliuyulong: yes14:58
slaweqI want to create port in br-int and add some additional flag to say to ovs agent to not remove dead_vlan_tag14:59
slaweqand then, when l3 agent will do all with this port, update ovs port to remove this flag14:59
slaweqand than ovs agent will change tag to proper one14:59
slaweqthat's long story short15:00
slaweqbut I'm still working on it15:00
slaweqI hope to send something to gerrit this week15:00
liuyulongAll right, time is up. Let's move to our channel.15:00
liuyulongslaweq, thanks.15:00
slaweqk15:00
slaweqo/15:00
liuyulong#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Jan 15 15:00:43 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-01-15-14.00.html15:00
ralonsohbye15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-01-15-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-01-15-14.00.log.html15:00
*** ociuhandu has quit IRC15:01
*** rfolco is now known as rfolco|bbl15:03
*** Luzi has quit IRC15:04
*** apetrich has quit IRC15:07
*** jamesmcarthur has joined #openstack-meeting15:22
*** ociuhandu has joined #openstack-meeting15:28
*** ociuhandu has quit IRC15:39
*** ociuhandu has joined #openstack-meeting15:40
*** LiangFang has quit IRC15:46
*** eharney has quit IRC15:48
*** eharney has joined #openstack-meeting15:52
*** efried is now known as efried_afk15:56
*** melwitt has joined #openstack-meeting16:00
*** witek has joined #openstack-meeting16:01
*** gyee has joined #openstack-meeting16:03
*** armax has joined #openstack-meeting16:07
*** carloss has joined #openstack-meeting16:12
*** simon-AS559 has quit IRC16:15
*** sfernand has quit IRC16:31
*** andrebeltrami has quit IRC16:34
*** ociuhandu has quit IRC16:39
*** ociuhandu has joined #openstack-meeting16:39
*** pcaruana has quit IRC16:45
*** clayg has quit IRC16:49
*** clayg has joined #openstack-meeting16:49
*** beisner has quit IRC16:50
*** beisner has joined #openstack-meeting16:50
*** simon-AS559 has joined #openstack-meeting16:51
*** simon-AS5591 has joined #openstack-meeting16:52
*** simon-AS559 has quit IRC16:56
*** rsimai is now known as rsimai_away16:57
*** ociuhandu has quit IRC16:59
*** maciejjozefczyk has quit IRC17:04
*** maciejjozefczyk has joined #openstack-meeting17:04
*** simon-AS5591 has left #openstack-meeting17:06
*** ociuhandu has joined #openstack-meeting17:08
*** gmann has quit IRC17:09
*** gmann has joined #openstack-meeting17:10
*** rpittau is now known as rpittau|afk17:15
*** tesseract has quit IRC17:26
*** njohnston has quit IRC17:28
*** njohnston has joined #openstack-meeting17:29
*** ociuhandu has quit IRC17:33
*** jgriffith has quit IRC17:40
*** jgriffith has joined #openstack-meeting17:42
*** e0ne has quit IRC18:03
*** electrofelix has quit IRC18:07
*** ociuhandu has joined #openstack-meeting18:14
*** carloss has quit IRC18:18
*** ociuhandu has quit IRC18:19
*** eharney has quit IRC18:26
*** rfolco|bbl is now known as rfolco18:28
*** TheJulia has quit IRC18:29
*** rpittau|afk has quit IRC18:30
*** seongsoocho has quit IRC18:30
*** masayukig has quit IRC18:30
*** _erlon_ has quit IRC18:30
*** evgenyl has quit IRC18:30
*** coreycb has quit IRC18:30
*** donnyd has quit IRC18:30
*** csatari has quit IRC18:30
*** jamespage has quit IRC18:30
*** tdasilva has quit IRC18:30
*** walshh_ has quit IRC18:30
*** lamt has quit IRC18:30
*** ildikov has quit IRC18:31
*** arne_wiebalck_ has joined #openstack-meeting18:31
*** mnaser has quit IRC18:31
*** xyang has quit IRC18:31
*** donnyd has joined #openstack-meeting18:31
*** arne_wiebalck has quit IRC18:31
*** arne_wiebalck_ is now known as arne_wiebalck18:31
*** jamespage has joined #openstack-meeting18:32
*** datasundae has quit IRC18:32
*** diablo_rojo_phon has quit IRC18:32
*** TheJulia has joined #openstack-meeting18:32
*** datasundae has joined #openstack-meeting18:32
*** seongsoocho has joined #openstack-meeting18:32
*** coreycb has joined #openstack-meeting18:33
*** tdasilva has joined #openstack-meeting18:33
*** ildikov has joined #openstack-meeting18:33
*** csatari has joined #openstack-meeting18:33
*** johnsom has quit IRC18:33
*** mnaser has joined #openstack-meeting18:34
*** johnsom has joined #openstack-meeting18:35
*** masayukig has joined #openstack-meeting18:35
*** walshh_ has joined #openstack-meeting18:36
*** csatari has quit IRC18:38
*** eharney has joined #openstack-meeting18:38
*** TheJulia has quit IRC18:40
*** rcernin has joined #openstack-meeting18:40
*** jamespage has quit IRC18:40
*** donnyd has quit IRC18:40
*** donnyd has joined #openstack-meeting18:42
*** tdasilva has quit IRC18:43
*** jamesmcarthur has quit IRC18:44
*** slaweq has quit IRC18:47
*** xyang has joined #openstack-meeting18:55
*** efried_afk is now known as efried18:55
*** witek has quit IRC19:08
*** dklyle has quit IRC19:36
*** ociuhandu has joined #openstack-meeting19:36
*** dklyle has joined #openstack-meeting19:37
*** dklyle has quit IRC19:37
*** dklyle has joined #openstack-meeting19:38
*** jamespage has joined #openstack-meeting19:52
*** jamespage has quit IRC19:52
*** e0ne has joined #openstack-meeting19:57
*** e0ne has quit IRC20:04
*** TheJulia has joined #openstack-meeting20:08
*** _erlon_ has joined #openstack-meeting20:11
*** enriquetaso has quit IRC20:13
*** enriquetaso has joined #openstack-meeting20:13
*** jamesmcarthur has joined #openstack-meeting20:19
*** eharney has quit IRC20:36
*** slaweq has joined #openstack-meeting20:36
*** vishalmanchanda has quit IRC20:44
*** enriquetaso has quit IRC20:45
*** patchbot has joined #openstack-meeting20:46
*** ralonsoh has quit IRC20:57
*** alecuyer has joined #openstack-meeting20:57
*** seongsoocho_ has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Jan 15 21:00:43 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
*** tdasilva has joined #openstack-meeting21:00
timburkewho's here for the swift meeting?21:00
alecuyero/21:00
tdasilvaeu21:01
kota_hi21:01
seongsoocho_o/21:01
timburkeas usual, the agenda's at21:01
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkei've been out of town for much of the last week, so i don't really have much more than updates to bring up21:02
timburke#topic versioning21:02
*** openstack changes topic to "versioning (Meeting topic: swift)"21:02
timburkei've been taking a look, and tdasilva has been busy addressing the last few issues we've found21:03
timburkeif you have any concerns about the new API, now's the time to check it out!21:03
timburke#link https://review.opendev.org/#/c/682382/21:03
patchbotpatch 682382 - swift - New Object Versioning mode - 72 patch sets21:03
timburke#link https://review.opendev.org/#/c/673682/21:03
patchbotpatch 673682 - swift - s3api: Implement object versioning API - 44 patch sets21:03
timburkei hope to have both of those landed within the next week or so, with any lingering issues being addressed as follow-up patches21:04
timburketdasilva, anything i forgot to mention about that?21:04
timburkeand everyone else, anything else you'd like to know about it?21:04
tdasilvanope, hoping to review a bit more of the swift client too, it would be nice to get that merged as closed together with the swift patches as possible21:05
timburkeagreed21:05
*** jamesmcarthur has quit IRC21:06
kota_sounds reasonable21:06
timburkei'll also go back and abandon some of the alternate approaches we looked at on our way to this solution21:06
timburkeoh yeah, and the client patch is21:07
timburke#link https://review.opendev.org/#/c/691877/21:07
patchbotpatch 691877 - python-swiftclient - object versioning features - 9 patch sets21:07
timburke#topic bulk regression21:07
*** openstack changes topic to "bulk regression (Meeting topic: swift)"21:07
timburke#link https://launchpad.net/bugs/185754621:07
openstackLaunchpad bug 1857546 in OpenStack Object Storage (swift) "Auto-extract looses X-Delete-At and X-Delete-After headers" [High,Confirmed]21:07
timburkei saw rledisez put up an alternate fix21:08
timburke#link https://review.opendev.org/#/c/701736/21:08
patchbotpatch 701736 - swift - Allow bulk to fwd some headers at tar extraction - 2 patch sets21:08
timburkehas anyone had a chance to look at either of the proposed fixes?21:08
*** zaitcev has joined #openstack-meeting21:09
kota_that option 2 looks good to me.21:10
kota_just looking now21:10
timburkei was just about to ask if anyone had a preference for which way we fix it ;-)21:10
*** jamesmcarthur has joined #openstack-meeting21:10
*** dviroel has quit IRC21:10
zaitcevIf we're talking about the versioning prompted by S3, I haven't reviewed it, sorry.21:11
timburkei guess my only concern is all the other allowed_headers at https://github.com/openstack/swift/blob/2.23.0/etc/object-server.conf-sample#L13521:11
tdasilvaI haven't looked at either yet, but I'll try to take a look today21:12
kota_ah, it's in object-server config...21:13
timburkezaitcev, this is the bulk-upload fix -- we've now got two solutions proposed: p 700652 (which mostly backs out the subrequest change that caused the regression but still fixes logging) and p 701736 (which starts copying over a subset of headers to the cleaned-up subrequest env)21:13
patchbothttps://review.opendev.org/#/c/700652/ - swift - Revert "bulk: Use make_subrequest to make subreque... - 1 patch set21:13
patchbothttps://review.opendev.org/#/c/701736/ - swift - Allow bulk to fwd some headers at tar extraction - 2 patch sets21:13
*** lseki has quit IRC21:14
*** jamesmcarthur has quit IRC21:15
*** jamesmcarthur has joined #openstack-meeting21:15
kota_hmm...21:16
tdasilvais allowed headers available in /info?21:16
timburkenope; wrong layer :-(21:16
timburkeproxy vs object21:17
tdasilvai guess it would not be if it's a object server config21:17
tdasilvaright21:17
*** slaweq has quit IRC21:19
timburkei'm not sure i like the hard-coded list -- seems like it'd be better as a configurable list... but then also allowing whole prefixes? hmm... trying to remember if we have some prior art for that...21:20
kota_good point21:20
timburkeor have object meta hardcoded, then configurable list for extra headers *shrug*21:21
timburkeanyway, i suppose we can argue approaches more on the reviews21:22
timburkeone extra topic to inject:21:22
timburke#topic next swift release21:22
*** openstack changes topic to "next swift release (Meeting topic: swift)"21:22
timburkeit's been a while since we did a release, i think it's about time for a new one!21:22
zaitcevI lean towards Romain's approach, BTW21:23
*** luyao has quit IRC21:23
timburkei'll look to see what else we could merge for it, but i'm looking at three things, mainly:21:23
timburkeversioning (ideally, with s3 support)21:23
timburkebulk fix21:23
timburkeand py3 formpost fix21:23
timburke#link https://launchpad.net/bugs/185825921:24
openstackLaunchpad bug 1858259 in OpenStack Object Storage (swift) "Upload failed if filename is unicode string in formpost (python3)" [High,Confirmed]21:24
timburkeseongsoocho_ already looked at https://review.opendev.org/#/c/701497/ (thanks!)21:24
patchbotpatch 701497 - swift - py3: Fix formpost unicode filename issues - 2 patch sets21:24
seongsoocho_timburke: yey !!! o/21:24
timburkeif anyone's got a moment to give it a spin, that'd be great21:24
tdasilvaI think p 697739  might also be able to make it to that list21:25
patchbothttps://review.opendev.org/#/c/697739/ - swift - Have slo tell the object-server that it wants whol... - 6 patch sets21:25
timburkesounds good21:25
timburke*maybe* even https://review.opendev.org/70005621:25
patchbotpatch 700056 - swift - Middleware that allows a user to have quoted Etags - 5 patch sets21:25
timburkei'll get a fresh version up soon that actually has the right names everywhere ;-)21:26
timburkethat's all i've got for today21:26
timburke#topic open discussion21:26
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:26
zaitcevWhat about client 3.8.2 or something?21:26
timburkeanything else people want to bring up?21:27
timburkezaitcev, yeah, that sounds good too21:27
timburkeif we can get the versioning patch for the client, all the better :-)21:27
zaitcevOn the dark data patch, or, rather auditor plugin patch https://review.opendev.org/212824, I had a change of heart and decided to agitate against the process separation.21:28
patchbotpatch 212824 - swift - Let developers/operators add watchers to object audit - 20 patch sets21:28
tdasilvathere's a also a client link patch that would be great to have, not sure its state tho21:28
*** igordc has joined #openstack-meeting21:29
tdasilvap 69421121:29
patchbothttps://review.opendev.org/#/c/694211/ - python-swiftclient - Support uploading Swift symlinks without content. - 7 patch sets21:29
zaitcevThis is going to be a week of catching up on reviews.21:32
tdasilvazaitcev: was just thinking the same :)21:32
timburkezaitcev, i'd love that :D21:32
timburkeall right, that's all i've got21:32
zaitcevAnyway, Sam and Alistair are not with us anymore.21:33
zaitcevSo, I guess I own the auditor API if nobody objects.21:33
zaitcevRomain had some input...21:33
alecuyerIll have to read up.. missed that patch, but that's a really nice idea21:33
timburkeright after this i'll update the priority reviews wiki to reflect the release plan21:33
alecuyer(I see there's some history there :) )21:33
timburkealecuyer, just a little ;-)21:33
timburkewell, let's let seongsoocho_, kota_, and tdasilva grab breakfast if they haven't yet21:35
timburkethank you all for coming, and thank you for working on swift!21:35
kota_thx21:35
timburke#endmeeting21:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:35
openstackMeeting ended Wed Jan 15 21:35:42 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-15-21.00.html21:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-15-21.00.txt21:35
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-15-21.00.log.html21:35
*** alecuyer has left #openstack-meeting21:36
*** zaitcev has left #openstack-meeting21:36
*** tdasilva has quit IRC21:36
*** vishakha has quit IRC21:38
*** rcernin has quit IRC21:42
*** eharney has joined #openstack-meeting21:48
*** ociuhandu has quit IRC21:54
*** jamesmcarthur has quit IRC22:06
*** jamesmcarthur has joined #openstack-meeting22:16
*** jamesmcarthur has quit IRC22:19
*** maciejjozefczyk has quit IRC22:35
*** dosaboy has quit IRC22:36
*** dmacpher has quit IRC22:37
*** dklyle has quit IRC22:40
*** diablo_rojo has quit IRC22:45
*** enriquetaso has joined #openstack-meeting22:47
*** dklyle has joined #openstack-meeting22:49
*** seongsoocho_ has quit IRC22:52
*** dosaboy has joined #openstack-meeting22:53
*** patchbot has left #openstack-meeting22:54
*** rcernin has joined #openstack-meeting22:55
*** igordc has quit IRC23:09
*** igordc has joined #openstack-meeting23:10
*** jamespage has joined #openstack-meeting23:27
*** tdasilva has joined #openstack-meeting23:37
*** tobiash has quit IRC23:38
*** tobiash has joined #openstack-meeting23:39

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