Wednesday, 2020-01-29

*** hyunsikyang has quit IRC00:00
*** armax has quit IRC00:00
*** hyunsikyang has joined #openstack-meeting00:08
*** munimeha1 has quit IRC00:21
*** jamesmcarthur has joined #openstack-meeting00:28
*** jamesmcarthur has quit IRC00:38
*** enriquetaso has quit IRC00:45
*** armax has joined #openstack-meeting01:04
*** jmasud has joined #openstack-meeting01:11
*** slaweq has joined #openstack-meeting01:11
*** jamesmcarthur has joined #openstack-meeting01:14
*** slaweq has quit IRC01:16
*** jamesmcarthur has quit IRC01:16
*** jamesmcarthur has joined #openstack-meeting01:19
*** jamesmcarthur has quit IRC01:21
*** igordc has quit IRC01:23
*** yamamoto has joined #openstack-meeting01:25
*** Lucas_Gray has quit IRC01:26
*** jamesmcarthur has joined #openstack-meeting01:47
*** Liang__ has joined #openstack-meeting01:52
*** gyee has quit IRC01:55
*** kopecmartin has quit IRC01:57
*** kopecmartin has joined #openstack-meeting02:00
*** jamesmcarthur has quit IRC02:03
*** jamesmcarthur has joined #openstack-meeting02:14
*** yamamoto has quit IRC02:19
*** rfolco has joined #openstack-meeting02:31
*** rfolco has quit IRC02:36
*** jamesmcarthur has quit IRC02:53
*** yamamoto has joined #openstack-meeting03:08
*** slaweq has joined #openstack-meeting03:11
*** yamamoto has quit IRC03:15
*** slaweq has quit IRC03:16
*** links has joined #openstack-meeting03:18
*** jamesmcarthur has joined #openstack-meeting03:29
*** jamesmcarthur has quit IRC03:38
*** dmacpher_ has joined #openstack-meeting04:03
*** dmacpher has quit IRC04:05
*** Liang__ has quit IRC04:09
*** jmasud has quit IRC04:12
*** jmasud has joined #openstack-meeting04:13
*** Liang__ has joined #openstack-meeting04:33
*** redrobot has quit IRC04:37
*** Liang__ has quit IRC04:38
*** redrobot has joined #openstack-meeting04:38
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:15
*** mmethot_ has joined #openstack-meeting06:17
*** mmethot has quit IRC06:20
*** masahito has joined #openstack-meeting06:36
*** jiaopengju1 has joined #openstack-meeting06:45
*** jiaopengju has quit IRC06:47
*** jiaopengju1 has quit IRC06:47
*** jiaopengju1 has joined #openstack-meeting06:48
*** lajoskatona has joined #openstack-meeting07:00
*** lajoskatona has left #openstack-meeting07:00
*** slaweq has joined #openstack-meeting07:11
*** slaweq has quit IRC07:15
*** redrobot has quit IRC07:21
*** etp has left #openstack-meeting07:21
*** masahito has quit IRC07:30
*** maciejjozefczyk has joined #openstack-meeting07:54
*** slaweq has joined #openstack-meeting07:56
*** tesseract has joined #openstack-meeting08:03
*** rpittau|afk is now known as rpittau08:08
*** jmasud has quit IRC08:11
*** jmasud has joined #openstack-meeting08:14
*** rcernin has quit IRC08:20
*** mdelavergne has joined #openstack-meeting08:53
*** oneswig has joined #openstack-meeting08:55
*** belmoreira has joined #openstack-meeting08:57
*** ralonsoh has joined #openstack-meeting08:59
ttx#startmeeting large_scale_sig09:00
openstackMeeting started Wed Jan 29 09:00:01 2020 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
oneswighello09:00
belmoreirao/09:00
ttxHi everyone!09:00
jiaopengju1hi09:00
ttxAgenda at:09:00
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting09:00
ttxI reordered it a bit to give masahito time to join before we discuss oslo.metrics09:00
ttxamorin: around?09:01
oneswigI must leave after 30 minutes, apologies09:01
amorinHello09:01
amorinI am here09:01
ttxok let's start then09:02
Dinesh_BhorHello, Sorry for being absent for a long time.09:02
mdelavergneHi09:02
*** masahito has joined #openstack-meeting09:02
ttx#topic Progress on "Documenting large scale operations" goal09:02
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"09:02
masahitoo/09:02
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation09:02
ttxWe had the following action items from last meeting(s):09:02
ttx- Collect and add links to relevant articles around large scale openstack (if you find any) to the etherpad09:02
ttxWe had some links filed from the Discovery initiative (experimentations on edge)09:02
ttxBut otherwise not that much09:02
ttxBut then maybe it's more of a long-term action, and we should just carry it over?09:03
Dinesh_Bhoryes i think so09:03
oneswigI think so.  New things will turn up09:03
ttxIt's more as we find them, to remember to add those to the etherpad :)09:03
ttx- oneswig to follow up with Scientific community to find such articles09:03
ttxoneswig: did you mention it on the Scientific SIG meeting ?09:03
belmoreiraI added few links today. But this will be a working in progress09:03
oneswigttx: I did.  We have meetings in two timezones and I raised it in both.  I think people looked at the etherpad but I don't think anything more was added by them, unfortunately.09:04
ttxOK, I propose we have a standing item in meetings, to regularly review the list we collected so far... rather than an action item09:05
oneswigHowever as above I'll keep looking for useful links from scientific sig discussions going forward.09:05
ttxsince this will basically never be "done"09:05
ttxWe can curate the list and categorize it on the etherpad itself09:05
ttxdoes that work for everyone?09:06
oneswigyes09:06
Dinesh_Bhor+109:06
ttxThe other action was around amorin's documenting configuration defaults for large scale09:06
jiaopengju1+109:06
ttxamorin: How is that going ?09:06
amorinhey all09:06
masahito+109:06
amorinI did not had enough time to work on this topic09:07
ttxThat's fine. If you need help in specific areas just tell us09:07
ttxAs I mentioned when we started this, it's ok to go slowly. Members of this group all have demanding day jobs :) The essential is to make regular progress09:08
amorinyup09:09
ttxAnything else on that topic?09:09
ttxI'll take that as a 'no'09:09
ttx#topic "Scaling within one cluster" goal09:10
*** openstack changes topic to ""Scaling within one cluster" goal (Meeting topic: large_scale_sig)"09:10
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling09:10
ttxWe had the following action items from last meeting(s):09:10
ttx- all post short descriptions of what happens (what breaks first) when scaling up a single cluster09:10
ttx#link https://etherpad.openstack.org/p/scaling-stories09:10
ttxNobody posted anything yet ^09:10
ttxSo... Is it that you did not find the time, or that you don't have anything to say, or somethign else?09:10
ttx(trying to see if it's still a good idea)09:11
oneswigThe investigation I have been doing has been on instrumentation, and there may be a scaling story in that.09:11
ttxpersonally, I don't have much to say because I do not operate a large scale cluster myself09:11
masahitoJust I didn't have much free time to do it :-(09:11
ttxmasahito: maybe just add a link to that presentation you did in Shanghai. I think that would be a great start :)09:12
Dinesh_Bhordidn't find the time to document. For our case it was RabbitMQ, Nova-scheduler. Will add after the meeting.09:12
masahitottx: ah, okay. I didn't think of it. I'll do that.09:12
oneswigmasahito: I enjoyed your presentation in Shanghai - please do :-)09:13
ttxMy hope is that once we have a few things in there, we can ask again to the openstack-discuss list and get them to add to it09:13
ttxIt's just difficult to seed the list initially09:13
ttxWe can also make sure it's a topic discussed at future Ops Meetups09:14
ttxok next...09:14
ttx- masahito to produce first draft for the oslo.metric blueprint09:15
ttx#link https://review.opendev.org/#/c/704733/09:15
masahitoyes. This is actually a draft.09:15
ttxI propose taht between now and next meeting, we all read the review the draft and comment as necessary09:15
oneswigNice work, will do.09:16
ttxso that we iterate toward a final proposal09:16
ttxDoes that sound like a good idea ?09:16
*** lucasagomes has joined #openstack-meeting09:16
amorinok for me09:16
jiaopengju1I will review it09:17
ttx#action all to review oslo.metrics draft at https://review.opendev.org/#/c/704733/09:17
masahitoFeel free to add you comment09:17
masahitosorry, away from keyboard09:17
*** masahito has quit IRC09:17
ttx- all learn more about golden signals concept09:17
ttx#link https://landing.google.com/sre/book.html09:17
ttxI'll admit I did not find the time to read that09:18
Dinesh_Bhorme too09:18
oneswigIt's quite fluffy... the details could be condensed09:18
amorinI'll try to read it also09:19
oneswigIf possible I'd like to propose a kind of show and tell about some investigation we have been doing in this area09:19
oneswigfor the next meeting09:19
ttxIs there a specific chapter we should focus on ?09:19
ttxsure that would be perfect09:19
oneswigprobably this bit; https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-systems/#xref_monitoring_golden-signals09:19
ttxok, that sounds more reasonable to digest09:20
ttxLet's read that before next meeting as preparationfor your show-and-tell09:20
oneswigOne of my colleagues has been doing some good work on using telemetry from HAproxy in Monasca.09:20
ttx#action all learn about golden signals by reading https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-systems/#xref_monitoring_golden-signals09:21
oneswigThere have been recent developments (in the last year or so) which really improve the data available about API service times09:21
ttx#action oneswig to prepare show-and-tell about some investigation they have been doing in this area09:21
oneswigWill do.09:22
ttxoneswig: how much time will you need ?09:22
oneswigProbably 15 minutes, depends on how much detail is wanted.09:22
ttxok so it will fit the regular meeting ok09:23
oneswigyes, no problem.09:23
ttxAnything else on that topic ?09:23
oneswignot from em09:24
ttx#topic Other topics09:24
*** openstack changes topic to "Other topics (Meeting topic: large_scale_sig)"09:24
oneswigme09:24
ttxLast meeting belmiro proposed a every-two-week cadence.09:24
ttxIf that still works for everyone, I will officially add the Large Scale SIG meeting so that it appears on the official meetings agenda at http://eavesdrop.openstack.org/09:24
amorinok for me09:25
ttx#action ttx to add meeting to eavesdrop on a every-two-week cadence09:25
ttx#info next meeting Feb 12, 9utc09:25
ttxIs that ok for everyone ?09:25
Dinesh_Bhoryes09:25
jiaopengju1it's ok for me09:25
ttxOK, is there anything else you wanted to discuss in this meeting?09:26
ttxanything else we should be doing between now and next meeting?09:26
ttxIf not, I'll post a summary with all the action items we just discussed. Please try to complete them by next meeting :)09:27
ttxand close this one09:27
*** e0ne has joined #openstack-meeting09:27
ttxoneswig: in time for your next meeting :)09:28
Dinesh_Bhornothing from my side09:28
oneswigperfect, thanks :-)09:28
ttxThanks everyone! Talk to you all again in two weeks!09:28
jiaopengju1thanks09:28
ttxAnyone from teh group present at FOSDEM this weekend?09:28
Dinesh_BhorThanks everyone...09:29
ttxbelmoreira, amorin oneswig maybe09:29
belmoreiraI'm not going09:29
oneswigsorry ttx, not this time for me at fosdem09:29
ttxOK, I'll represent :)09:30
ttxThanks all09:30
ttx#endmeeting09:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:30
openstackMeeting ended Wed Jan 29 09:30:14 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-29-09.00.html09:30
mdelavergnethanks everyone, bye!09:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-29-09.00.txt09:30
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-01-29-09.00.log.html09:30
*** oneswig has quit IRC09:31
amorinno fosdem for me this year, but some of my collegues will be there09:31
ttxnoted09:45
*** mdelavergne has left #openstack-meeting09:45
*** lifeless has quit IRC10:19
*** dviroel has joined #openstack-meeting10:30
*** psachin has joined #openstack-meeting10:35
*** pcaruana has quit IRC10:57
*** oneswig has joined #openstack-meeting10:58
*** priteau has joined #openstack-meeting11:00
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Jan 29 11:00:19 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
oneswigHello11:00
oneswig... echo ...11:00
ttx... o ...11:05
oneswighi ttx11:05
oneswigquiet, real quiet today (should have posted an agenda... :-(11:06
ttxI replied so that you did not feel too lonely :)11:06
oneswigWe usually pull in 4-5 but there were no agenda items from the sig slack channel11:06
*** janders has joined #openstack-meeting11:08
jandersg'day all11:08
janderssorry mac issues11:08
janderstime to get a real laptop not a toy11:08
oneswigHi janders, just us and ttx right now...11:08
jandersI did see that mention of the Mellanox HDR OpenStack press release from last week's log11:09
oneswigMacbook?  Mine runs IRC just fine... got about 6GB in swap doing something though.11:09
jandersmy 5 cents - it was indeed running fine for quite a while, I think they just streamlined it a little more11:09
oneswigjanders: is that your doing I wonder?11:09
oneswigwhat's different with hdr that required change?11:10
jandersI might have contributed a little :)  but mostly good work by MLNX11:10
jandersI think most work was around tripleo integration bits11:11
oneswigAh, Ok.11:11
jandersHDR... good question - I haven't played with HDR200 vfs11:11
jandersI've got HDR200 storage and HDR100 computes11:11
oneswigI've been having lots of fun this last week with VF-LAG11:11
janders*maybe* there was a bit of fiddling there11:11
jandersspecifically - HDR200 on PCIe311:12
jandersother than that - I think it was most integration work11:12
jandersVF-LAG - interesting!11:12
janderswhat is it like?11:12
jandersI've never touched it - and it could be interesting for my cyber system going forward in certain circumstances11:13
oneswigJury's out at present.  The major issue I had was the systemd/udev plumbing to put VFs into switchdev mode instead of "legacy" mode.11:13
oneswigCuriously, it worked in legacy mode but I haven't got around to trying it in switchdev mode yet.  That's todays fun.11:14
janderswhat does it look like from VM owner perspective? ethX and ethY, each coming off a different port?11:14
oneswigWhen I was misconfiguring it, I got Tx bandwidth of 1 port and it appeared I could receive on either port.11:14
oneswigjanders: no, 1 VF, somehow coupled to 2 PFs.11:14
jandersor is it magicnic0 which stays up despite ports backing it going up and down?11:14
jandersok so option 2) nice!11:15
oneswigI think that's the idea.  Haven't tested the failover bit yet.11:15
jandersis the promise that you can aggregate bandwidth and failover at the same time?11:15
*** Lucas_Gray has joined #openstack-meeting11:16
oneswigThe aggregated bandwidth needs verifying but the failover capability is intended for sure.11:16
oneswigI'll let you know!11:16
oneswigAny news on Supercloud?11:17
oneswigbtw I'm hoping to write up the VF-LAG experience for next week, it's almost completely undocumented fwiw11:18
jandersactually I do have some news, what might be disappointing is these are not very performance related11:18
*** psachin has quit IRC11:18
jandersSuperCloud got bogged down in the cyber security realm for some time it seems11:18
janders but I have hit some interesting challanges and issues lately11:19
jandersin terms of cyber specifics I proposed the volume-transfer based mechanism of copying unsafe data in (and at a later stage - possibly copying data out)11:19
janderswill see what my security team have to say about this one11:20
jandersbut so far a so good, people seem to be liking the idea11:20
oneswigthis is malware payloads for analysis?11:20
jandersyes, in encrypted form11:20
oneswigLoving your work, janders :-)11:20
jandersI might try submit something for Vancouver on this, it is getting quite interesting really11:21
jandersvery different than what I typically do11:21
oneswigIs this into bare metal instances?11:21
jandersVMs at this stage11:21
jandersbut you raised an interesting point11:21
oneswigprobably wise unless you really trust your layers of defence :-)11:21
jandersthis system will be used by guys who uncovered spectre/meltdown so looking at hardware layer security might be in scope11:22
jandersit wasn't brought up yet, so mostly looking at VMs11:22
jandersI should probably say - guys who participated in uncovering spectre/meltdown - it was a big, orchestrated effort11:22
jandersso that's one interesting bit11:23
jandersthe other bit is more operational11:23
jandershit some interesting failure modes in OSP13 which likely impact later releases, too11:23
jandersBZ coming soon11:23
jandershttps://bugzilla.redhat.com/show_bug.cgi?id=179540211:23
oneswigYou might need to give those researchers access to bios settings, microcode etc.11:23
openstackbugzilla.redhat.com bug 1795402 in openstack-nova "Nova list --all-tenants | ERROR (ClientException): Unexpected API Error. | <type 'exceptions.TypeError'> (HTTP 500)" [Medium,New] - Assigned to nova-maint11:23
jandersessentially we had AMQP dropout brick an entire project11:24
oneswigtypeerror - suggests a code path nobody else is tickling11:24
janders(and "openstack server list --all-projects")11:24
jandersI think it is rare, but when you hit it it does get very ugly very quickly11:24
oneswigouch11:24
oneswigis that Queens?11:25
jandersessentially if AMQP dropout happens in a very bad time during instance creation, instance ends up with missing fields in DB and nova can't handle that11:25
jandersyes, queens11:25
jandersOSP16 should be out soon, but it will probably be a while before we upgrade11:25
jandersI fixed this within an hour from when it happened by setting deleted=1 for instance and re-creating11:26
oneswigAre you getting rabbit issues often enough to hit this?11:26
jandersit only happened once so far11:26
oneswigNice work for getting to the bottom of it!11:26
jandersbut as per Murphy's law it happened at the least appropriate time11:26
janderswhen I had a contractor set up something time-sensitive11:26
jandersso I did a quick and dirty fix and then had RHAT guys had a look11:27
jandersthey have some really smart fellas up in Brisbane11:27
jandersthe "proper" fix in the BZ was their work11:27
jandersit's interesting how nova ended up in that state - I thought I will share11:28
oneswigthanks, really interesting to know!11:28
jandersthere are known issues with OSP13 AMQP connection handling in nova-compute which are fixed in latest minor updates11:28
jandersthose might be affecting later versions, not sure11:28
jandersso the root cause of this is likely fixed11:28
jandersbut in case of future errors... nova should be smarter11:29
jandersI hope to see some resiliency enhancementw11:29
jandersit should purge network cache itself instead of needing this11:29
janderssupposedly there is a periodic task that does that but what im hearing is it is yet to be seen to fix anything11:29
jandersso - if you ever hit this (hope not) here's the SQL :)11:30
jandersother than that I will be putting in some policy customisations into heat - and splitting GPFS backend for "connected" and "disconnected" instances soon11:31
janders(connected=with_floating_ips disconnected=only_accessible_via_vnc in our terminology)11:31
jandersso - long story short - not a lot of action, but some interesting stuff happening11:32
oneswigsounds like you've had your hands busy!11:32
jandersa little, yes! :)11:33
oneswigThanks for the update, always good to hear your news11:33
jandershttps://photos.app.goo.gl/dcLYzuRMNeHJKHv4A this nasty thing has been keeping us busy lately11:34
jandersCanberra has been affected by bushfire smoke lately but was lucky enough to avoid big fires nearby... till this week11:35
jandersso far it's not too bad but we gotta keep an eye on it11:35
oneswigouch.  Take care janders!11:35
jandersthanks oneswig :)11:35
oneswigI don't think there's anything else to cover here.11:36
jandersdo you know when does CFP for Vancouver open?11:36
jandersI keep checking the website but haven't seen much so far11:36
priteaujanders: Given the new format of this event, I am not sure if there will be a CFP as usual?11:36
jandersinteresting!11:37
priteauMaybe ttx knows more about this11:37
janderswould you be happy to explain the new format in a nutshell/11:37
priteauI only know what's publicly available on the eventbrite page11:37
priteauEach day will be broken into three parts:11:38
priteauShort kickoff with all attendees to set the goals for the day or discuss the outcomes of the previous day11:38
priteauOpenDev: Morning discussions covering projects like Ansible, Ceph, Kubernetes, OpenStack, and more11:38
priteauPTG: Afternoon working sessions for project teams and SIGs to continue the morning’s discussions.11:38
priteauSee https://www.eventbrite.com/e/opendev-ptg-vancouver-2020-tickets-8892327089711:38
janderssounds like less presentations, more discussions?11:38
priteauYes, it explicitely says: OpenDev [...] will include discussion oriented sessions around a particular topic to explore a problem within a topic area, share common architectures, and collaborate around potential solutions.11:39
janderslooks like the balance between the "main" summit and PTG is about to turn upside-down...11:40
*** pcaruana has joined #openstack-meeting11:40
janderswhich might not be a bad thing, but it is indeed very different than what it used to be11:40
jandersgood? bad? what do you guys think?11:40
priteauAFAIK there will still be a usual summit in Q4 202011:41
priteauDunno if this new event is an improvement, we shall see11:41
oneswigI like the focus of the new session, I hope it turns out how it is being described11:41
jandersone tricky bit is11:41
janderswith many organisations getting travel approvals is heaps easier when you have a presentation slot in11:42
janders(that does include CSIRO)11:42
oneswiglightning talk slot in a sig session perhaps :-)11:42
jandershaha :D  I like your thinking oneswig11:42
jandersif SARS-ng epidemic isn't too bad I'd very much like to re-visit Vancouver (and probably LA/California on the way back)11:43
janderslooks like Qantas is now flying direct SYD-YVR - AND getting out of US is so much easier than getting in, immigration-queues wise11:44
jandersthe above would be my way to go11:44
jandersJune is the right time to do this, too11:45
jandersallright! it's getting close to the hour - so if you guys would like to wrap up, please go ahead11:46
jandersgood chatting - and we'll chat next week11:46
ttxre opendev11:47
oneswigsame to you janders11:47
ttxthere will not really be a CFP per se11:47
jandersttx so more like tracks moderated by project leads, etc?11:48
ttxeach theme should have a programming committee responsible for picking content. Those may use a CFP, but probably will just reach out to find suitable speakers.... Presentations are just one side of the event11:48
ttxmost of it is open discussion11:48
ttxMore details will be out soon as we push out the call for programming committee members11:48
oneswiggreat, thanks for clarifying ttx11:49
janders+111:49
oneswigOK, any final items?11:50
jandersttx we're happy to help as the SIG :)11:51
jandersoneswig I think we're good. See you next week! :)11:52
oneswiglikewise janders11:52
oneswig#endmeeting11:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"11:52
oneswigthanks all11:52
openstackMeeting ended Wed Jan 29 11:52:33 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)11:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-29-11.00.html11:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-29-11.00.txt11:52
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-01-29-11.00.log.html11:52
*** rpittau is now known as rpittau|bbl11:53
*** janders has quit IRC11:54
*** ociuhandu has joined #openstack-meeting11:58
*** hyunsikyang has quit IRC12:05
*** hyunsikyang has joined #openstack-meeting12:06
*** rfolco has joined #openstack-meeting12:10
*** raildo has joined #openstack-meeting12:12
*** jmasud has quit IRC12:12
*** jmasud has joined #openstack-meeting12:13
*** anastzhyr has joined #openstack-meeting12:22
*** links has quit IRC12:24
*** oneswig has quit IRC12:26
*** ociuhandu has quit IRC12:31
*** masahito has joined #openstack-meeting12:33
*** masahito has quit IRC12:34
*** masahito has joined #openstack-meeting12:37
*** masahito has quit IRC12:40
*** ociuhandu has joined #openstack-meeting12:40
*** masahito has joined #openstack-meeting12:43
*** masahito has quit IRC12:46
*** enriquetaso has joined #openstack-meeting12:50
*** jawad_axd has joined #openstack-meeting12:54
*** Lucas_Gray has quit IRC12:59
*** artom has quit IRC13:06
*** rh-jelabarre has joined #openstack-meeting13:12
*** maciejjozefczyk has quit IRC13:14
*** ociuhandu has quit IRC13:17
*** ociuhandu has joined #openstack-meeting13:21
*** ociuhandu has quit IRC13:26
*** rpittau|bbl is now known as rpittau13:30
*** Shrews has left #openstack-meeting13:31
*** maciejjozefczyk has joined #openstack-meeting13:39
*** redrobot has joined #openstack-meeting13:46
*** Lucas_Gray has joined #openstack-meeting13:49
*** jamesmcarthur has joined #openstack-meeting13:49
*** Liang__ has joined #openstack-meeting13:53
*** Liang__ is now known as LiangFang13:53
*** strigazi has quit IRC13:56
*** sfernand has joined #openstack-meeting14:00
*** ociuhandu has joined #openstack-meeting14:00
*** strigazi has joined #openstack-meeting14:02
*** Lucas_Gray has quit IRC14:14
*** anastzhyr has quit IRC14:31
*** jamesmcarthur has quit IRC14:38
*** jawad_axd has quit IRC14:39
*** jmasud has quit IRC14:39
*** jawad_axd has joined #openstack-meeting14:39
*** jamesmcarthur has joined #openstack-meeting14:40
*** jawad_ax_ has joined #openstack-meeting14:43
*** jawad_axd has quit IRC14:45
*** jamesmcarthur has quit IRC14:45
*** jawad_ax_ has quit IRC14:48
*** priteau has quit IRC14:50
*** priteau has joined #openstack-meeting14:51
*** anastzhyr has joined #openstack-meeting14:55
*** priteau has quit IRC14:56
*** ayoung has quit IRC15:00
*** ayoung has joined #openstack-meeting15:01
*** dklyle has quit IRC15:02
*** dklyle has joined #openstack-meeting15:03
*** priteau has joined #openstack-meeting15:07
*** jamesmcarthur has joined #openstack-meeting15:09
*** jamesmcarthur has quit IRC15:14
*** ociuhandu has quit IRC15:24
*** artom has joined #openstack-meeting15:31
*** jamesmcarthur has joined #openstack-meeting15:47
*** ociuhandu has joined #openstack-meeting15:52
*** jamesmcarthur has quit IRC15:53
*** lbragstad has joined #openstack-meeting15:57
*** eharney has quit IRC16:09
*** maciejjozefczyk has quit IRC16:11
*** gyee has joined #openstack-meeting16:14
*** e0ne has quit IRC16:34
*** lbragstad has quit IRC16:38
*** jamesmcarthur has joined #openstack-meeting16:39
*** eharney has joined #openstack-meeting16:51
*** dviroel has left #openstack-meeting16:55
*** ociuhandu has quit IRC16:59
*** bnemec-ooo has quit IRC17:00
*** anastzhyr has quit IRC17:11
*** lucasagomes has quit IRC17:12
*** enriquetaso has quit IRC17:20
*** enriquetaso has joined #openstack-meeting17:21
*** jmasud has joined #openstack-meeting17:25
*** jmasud has quit IRC17:30
*** rpittau is now known as rpittau|afk17:33
*** jmasud has joined #openstack-meeting17:34
*** rubasov has quit IRC17:38
*** jmasud has quit IRC17:41
*** jmasud has joined #openstack-meeting17:46
*** jmasud has quit IRC17:52
*** jmasud has joined #openstack-meeting17:57
*** mattw4 has joined #openstack-meeting18:01
*** lbragsta_ has joined #openstack-meeting18:04
*** jmasud has quit IRC18:06
*** jamesmcarthur has quit IRC18:09
*** jamesmcarthur has joined #openstack-meeting18:18
*** jmasud has joined #openstack-meeting18:18
*** lbragsta_ has quit IRC18:20
*** rubasov has joined #openstack-meeting18:20
*** jamesmcarthur has quit IRC18:26
*** jmasud has quit IRC18:27
*** jmasud has joined #openstack-meeting18:30
*** priteau has quit IRC18:33
*** eharney has quit IRC18:38
*** jmasud has quit IRC18:41
*** jmasud has joined #openstack-meeting18:44
*** benj_ has quit IRC18:47
*** benj_ has joined #openstack-meeting18:47
*** ralonsoh has quit IRC18:47
*** jmasud has quit IRC18:49
*** eharney has joined #openstack-meeting18:51
*** jamesmcarthur has joined #openstack-meeting18:55
*** tesseract has quit IRC18:59
*** igordc has joined #openstack-meeting19:02
*** jmasud has joined #openstack-meeting19:15
*** jmasud has quit IRC19:20
*** jmasud has joined #openstack-meeting19:24
*** eharney has quit IRC19:26
*** jamesmcarthur has quit IRC19:27
*** mattw4 has quit IRC19:29
*** mattw4 has joined #openstack-meeting19:30
*** e0ne has joined #openstack-meeting19:34
*** jamesmcarthur has joined #openstack-meeting19:38
*** eharney has joined #openstack-meeting19:39
*** e0ne has quit IRC19:39
*** eharney has quit IRC19:48
*** jmasud has quit IRC19:48
*** dklyle has quit IRC19:56
*** gmann is now known as gmann_afk19:57
*** anastzhyr has joined #openstack-meeting20:00
*** rubasov has quit IRC20:01
*** lifeless has joined #openstack-meeting20:01
*** rubasov has joined #openstack-meeting20:02
*** dklyle has joined #openstack-meeting20:03
*** dklyle has quit IRC20:08
*** e0ne has joined #openstack-meeting20:11
*** dklyle has joined #openstack-meeting20:14
*** sfernand has quit IRC20:18
*** e0ne has quit IRC20:19
*** LiangFang has quit IRC20:19
*** slaweq has quit IRC20:22
*** kprice789 has joined #openstack-meeting20:23
*** slaweq has joined #openstack-meeting20:23
*** mattw4 has quit IRC20:25
*** jawad_axd has joined #openstack-meeting20:52
*** slaweq has quit IRC20:54
*** jawad_axd has quit IRC20:56
*** alecuyer has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Jan 29 21:00:01 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
alecuyero/21:00
timburkeso i've only got one topic to bring up21:01
timburke#topic 2.24.0 release21:01
*** openstack changes topic to "2.24.0 release (Meeting topic: swift)"21:01
timburkeversioning's landed!21:02
kota_o/21:02
alecuyercongrats!21:02
timburkeall the big bugs we were worried about before the release have been fixed21:02
tdasilvao/21:02
kota_awesome21:02
mattoliverauo/21:02
timburkelet's ship the new best swift yet! :-)21:02
timburkei've got an authors/changelog patch up at https://review.opendev.org/#/c/704481/21:03
patchbotpatch 704481 - swift - Authors/changelog for swift 2.24.0 - 2 patch sets21:03
seongsoocho🎉21:03
*** eharney has joined #openstack-meeting21:03
timburkebut people keep approving more patches, so i might need to add to it :D21:03
*** slaweq has joined #openstack-meeting21:03
timburkeif you want a pretty view of the notes, there's a reno preview at https://2105da1522365286042c-1f0fc773a02f07142ed8f243d3787b76.ssl.cf2.rackcdn.com/704481/2/check/build-openstack-releasenotes/2d0ef89/docs/current.html21:04
timburkeany extra eyes on what should or shouldn't be included, or any fo my splling misteaks would be much appreciated21:05
timburkethanks mattoliverau for the feedback on the ring-builder note21:05
*** jamesmcarthur has quit IRC21:05
mattoliverauNps21:06
timburkei hope to have the changelog landed and a release requested this week21:06
timburkeand i'm so pleased to add seongsoocho and csmart to our authors file :D21:07
timburkethat's all i've got...21:07
timburke#topic open discussion21:07
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:07
timburkewhat do you guys have to bring up?21:08
*** artom has quit IRC21:08
timburkei know rledisez proposed a bunch of patches recently...21:08
*** slaweq has quit IRC21:09
rledisezI made some progress on the MD5 middleware that calculate md5 of objects that input the proxy and then EC or crypto does not have to care about. not ready to push it yet, but it's in progress21:09
rledisezit' the first step to remove MD5 as internal checksum algorithm21:09
timburkenice! you've been very busy then21:09
mattoliverauWow21:09
rledisezI have an other patch that improve network bandwidth with EC, but i'm struggling with an eventlet issue in the unit tests21:09
rledisezif anyone can have a look would be nice (i didn't push it yet)21:10
*** Lucas_Gray has joined #openstack-meeting21:10
rledisezi don't have a clue what to change to make tests pass (I tried adding some sleep() but he…)21:10
timburkerledisez, i'd be happy to -- curious about what the failure looks like, and what you did to improve things21:10
*** slaweq has joined #openstack-meeting21:11
rledisezthx timburke, i'll push it soon21:11
rledisezjust as a side note, i've been playing a bit with ISA-L for vectorizing MD5 calculation, it's interresting, but kinda hard to do. but there is probably some nice thing to do with it if I can figure it out21:12
timburkeoh, interesting...21:12
timburkerledisez, i also found it kinda funny that shortly after you pushed up p 704435, zaitcev wrote up https://bugs.launchpad.net/swift/+bug/186123321:13
openstackLaunchpad bug 1861233 in OpenStack Object Storage (swift) "Container updater crashes the account server repeatedly" [Undecided,New]21:13
patchbothttps://review.opendev.org/#/c/704435/ - swift - Mark a container reported if account was reclaimed - 1 patch set21:13
rledisezyeah, I need to pass again on this patch, thx for the review21:13
*** slaweq has quit IRC21:16
timburkeseparately, i'd be curious if you've ever run into container-sync trouble that might be solved by p 702783 -- i just noticed something fishy while i was getting container-sync loaded into my head again21:16
patchbothttps://review.opendev.org/#/c/702783/ - swift - container-sync: Stop continuing to update sync poi... - 2 patch sets21:16
*** gmann_afk is now known as gmann21:17
claygohai21:18
timburkeclayg, i think you may have missed most of the meeting already ;-)21:19
claygeverything is proceeding exactly as i have foreseen21:20
timburkewell, if no one has anything else to bring up...21:21
timburkethank you all for coming, and thank you for working on swift!21:22
timburkei'm so excited to get a fresh release out, thank you all so much for all your hard work21:23
timburke#endmeeting21:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:23
openstackMeeting ended Wed Jan 29 21:23:26 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-29-21.00.html21:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-29-21.00.txt21:23
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-29-21.00.log.html21:23
*** rcernin has joined #openstack-meeting21:32
*** jamesmcarthur has joined #openstack-meeting21:32
*** mattw4 has joined #openstack-meeting21:40
*** apetrich has quit IRC21:43
*** jmasud has joined #openstack-meeting21:55
*** patchbot has left #openstack-meeting21:55
*** raildo has quit IRC21:57
*** ociuhandu has joined #openstack-meeting22:01
*** jmasud has quit IRC22:06
*** ociuhandu has quit IRC22:06
*** jmasud has joined #openstack-meeting22:09
*** jmasud has quit IRC22:16
*** rh-jelabarre has quit IRC22:17
*** jamesmcarthur has quit IRC22:18
*** jamesmcarthur has joined #openstack-meeting22:19
*** artom has joined #openstack-meeting22:19
*** enriquetaso has quit IRC22:22
*** e0ne has joined #openstack-meeting22:23
*** rfolco has quit IRC22:33
*** kaisers has quit IRC23:06
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:16
*** kaisers has joined #openstack-meeting23:23
*** e0ne has quit IRC23:24
*** jmasud has joined #openstack-meeting23:52

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