Wednesday, 2019-10-16

*** jamesmcarthur has joined #openstack-meeting00:06
*** martial has quit IRC00:13
*** markvoelker has joined #openstack-meeting00:16
*** jamesmcarthur has quit IRC00:18
*** brinzhang has joined #openstack-meeting00:22
*** rbudden has joined #openstack-meeting00:22
*** b1airo has quit IRC00:23
*** brinzhang_ has quit IRC00:24
*** markvoelker has quit IRC00:27
*** markvoelker has joined #openstack-meeting00:36
*** lseki has quit IRC00:45
*** gyee has quit IRC00:45
*** markvoelker has quit IRC00:46
*** nanzha has joined #openstack-meeting01:21
*** zhangchi has joined #openstack-meeting01:27
zhangchi#startmeeting-tricircle01:28
openstackMeeting started Wed Oct 16 01:28:47 2019 UTC and is due to finish in 60 minutes.  The chair is zhangchi. Information about MeetBot at http://wiki.debian.org/MeetBot.01:28
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:28
*** openstack changes topic to " (Meeting topic: -tricircle)"01:28
openstackThe meeting name has been set to '_tricircle'01:28
zhangchiHello all welcome to join tricirlce bio-weekly meeting01:33
*** igordc has quit IRC01:47
*** ricolin has joined #openstack-meeting01:57
*** dmacpher_ has joined #openstack-meeting02:00
*** dmacpher has quit IRC02:02
*** apetrich has quit IRC02:08
*** brault has joined #openstack-meeting02:09
*** baojg has quit IRC02:11
zhangchi sorry. I left for a while. I just had a meeting.02:13
zhangchi#endmeeting tricircle02:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"02:13
openstackMeeting ended Wed Oct 16 02:13:14 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_tricircle/2019/_tricircle.2019-10-16-01.28.html02:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_tricircle/2019/_tricircle.2019-10-16-01.28.txt02:13
openstackLog:            http://eavesdrop.openstack.org/meetings/_tricircle/2019/_tricircle.2019-10-16-01.28.log.html02:13
*** dviroel has quit IRC02:14
*** yaawang_ has quit IRC02:16
*** zhangchi has quit IRC02:18
*** yaawang_ has joined #openstack-meeting02:18
*** markvoelker has joined #openstack-meeting02:47
*** markvoelker has quit IRC02:51
*** brinzhang_ has joined #openstack-meeting02:56
*** brinzhang has quit IRC02:59
*** brinzhang has joined #openstack-meeting03:12
*** brinzhang_ has quit IRC03:15
*** brinzhang_ has joined #openstack-meeting03:16
*** brinzhang has quit IRC03:18
*** brinzhang has joined #openstack-meeting03:36
*** enriquetaso has quit IRC03:38
*** brinzhang_ has quit IRC03:38
*** psachin has joined #openstack-meeting04:02
*** brinzhang_ has joined #openstack-meeting04:04
*** brinzhang has quit IRC04:07
*** brinzhang_ has quit IRC04:14
*** yaawang_ has quit IRC04:14
*** brinzhang_ has joined #openstack-meeting04:15
*** yaawang_ has joined #openstack-meeting04:15
*** rbudden has quit IRC04:17
*** baojg has joined #openstack-meeting04:27
*** pcaruana has joined #openstack-meeting04:37
*** pcaruana has quit IRC05:14
*** brinzhang has joined #openstack-meeting05:14
*** brinzhang_ has quit IRC05:17
*** Luzi has joined #openstack-meeting05:18
*** lpetrut has joined #openstack-meeting05:21
*** brinzhang_ has joined #openstack-meeting05:24
*** lpetrut has quit IRC05:26
*** brinzhang has quit IRC05:27
*** bnemec has joined #openstack-meeting05:38
*** brinzhang has joined #openstack-meeting05:39
*** brinzhang_ has quit IRC05:42
*** links has joined #openstack-meeting05:45
*** jawad_axd has joined #openstack-meeting05:59
*** brault has quit IRC06:06
*** brault has joined #openstack-meeting06:08
*** pcaruana has joined #openstack-meeting06:13
*** brinzhang_ has joined #openstack-meeting06:24
*** brinzhang has quit IRC06:27
*** nanzha has quit IRC06:34
*** nanzha has joined #openstack-meeting06:43
*** ralonsoh has joined #openstack-meeting06:44
*** ktsuyuzaki is now known as kota_06:46
*** slaweq has joined #openstack-meeting06:47
*** brault has quit IRC06:49
*** brault has joined #openstack-meeting06:50
*** apetrich has joined #openstack-meeting06:55
*** brinzhang has joined #openstack-meeting06:59
*** brinzhang_ has quit IRC07:01
*** brinzhang_ has joined #openstack-meeting07:07
*** takamatsu has joined #openstack-meeting07:08
*** brinzhang has quit IRC07:10
*** yaawang_ has quit IRC07:11
*** yaawang_ has joined #openstack-meeting07:12
*** tesseract has joined #openstack-meeting07:12
*** tesseract has quit IRC07:14
*** tesseract has joined #openstack-meeting07:14
*** e0ne has joined #openstack-meeting07:19
*** trident has quit IRC07:27
*** priteau has quit IRC07:29
*** priteau has joined #openstack-meeting07:30
*** Liang__ has joined #openstack-meeting07:31
*** Liang__ is now known as LiangFang07:31
*** trident has joined #openstack-meeting07:31
*** ociuhandu has joined #openstack-meeting07:33
*** ociuhandu has quit IRC07:37
*** tssurya has joined #openstack-meeting07:38
*** brinzhang has joined #openstack-meeting07:47
*** brinzhang_ has quit IRC07:50
*** ttsiouts has joined #openstack-meeting07:57
*** rpittau|afk is now known as rpittau08:12
*** lpetrut has joined #openstack-meeting08:12
*** larainema has joined #openstack-meeting08:15
*** takamatsu has quit IRC08:21
*** brinzhang_ has joined #openstack-meeting08:25
*** brinzhang has quit IRC08:28
*** tssurya has quit IRC08:34
*** brinzhang has joined #openstack-meeting08:34
*** takamatsu has joined #openstack-meeting08:36
*** brinzhang_ has quit IRC08:37
*** nanzha has quit IRC08:40
*** nanzha has joined #openstack-meeting08:43
*** gibi is now known as gibi_off08:58
*** brinzhang_ has joined #openstack-meeting08:59
*** brinzhang has quit IRC09:03
*** ttsiouts has quit IRC09:09
*** ttsiouts has joined #openstack-meeting09:09
*** nanzha has quit IRC09:14
*** nanzha has joined #openstack-meeting09:21
*** panda is now known as panda|drappt09:23
*** LiangFang has quit IRC09:35
*** ociuhandu has joined #openstack-meeting09:42
*** rcernin has quit IRC09:54
*** brinzhang has joined #openstack-meeting10:00
*** brinzhang_ has quit IRC10:04
*** ociuhandu has quit IRC10:13
*** ttsiouts has quit IRC10:20
*** ttsiouts has joined #openstack-meeting10:21
*** ttsiouts has quit IRC10:26
*** kopecmartin|off is now known as kopecmartin10:31
*** brinzhang_ has joined #openstack-meeting10:32
*** brinzhang has quit IRC10:35
*** markvoelker has joined #openstack-meeting10:50
*** ttsiouts has joined #openstack-meeting10:53
*** markvoelker has quit IRC10:56
*** ttsiouts has quit IRC10:58
*** rfolco|ruck is now known as rfolco|brb11:01
*** brinzhang has joined #openstack-meeting11:03
*** brinzhang_ has quit IRC11:06
*** ociuhandu has joined #openstack-meeting11:07
*** ttsiouts has joined #openstack-meeting11:25
*** ttsiouts has quit IRC11:26
*** ttsiouts has joined #openstack-meeting11:26
*** rcernin has joined #openstack-meeting11:30
*** brinzhang_ has joined #openstack-meeting11:33
*** brinzhang has quit IRC11:36
*** raildo has joined #openstack-meeting11:37
*** rubasov has joined #openstack-meeting11:40
*** markvoelker has joined #openstack-meeting11:44
*** markvoelker has quit IRC11:55
*** rfolco|brb is now known as rfolco|ruck11:55
*** nanzha has quit IRC11:55
*** brinzhang has joined #openstack-meeting12:03
*** brinzhang_ has quit IRC12:06
*** markvoelker has joined #openstack-meeting12:10
*** Luzi has quit IRC12:11
*** larainema has quit IRC12:11
*** jamesmcarthur has joined #openstack-meeting12:13
*** jamesmcarthur has quit IRC12:13
*** jamesmcarthur has joined #openstack-meeting12:13
*** enriquetaso has joined #openstack-meeting12:22
*** priteau has quit IRC12:22
*** jamesmcarthur has quit IRC12:26
*** Luzi has joined #openstack-meeting12:27
*** dviroel has joined #openstack-meeting12:31
*** lseki has joined #openstack-meeting12:32
*** brinzhang_ has joined #openstack-meeting12:41
*** brinzhang_ has quit IRC12:42
*** brinzhang_ has joined #openstack-meeting12:42
*** brinzhang_ has quit IRC12:42
*** brinzhang_ has joined #openstack-meeting12:43
*** brinzhang_ has quit IRC12:43
*** brinzhang has quit IRC12:44
*** brinzhang_ has joined #openstack-meeting12:44
*** brinzhang_ has quit IRC12:44
*** liuyulong has joined #openstack-meeting12:49
*** jamesmcarthur has joined #openstack-meeting12:52
*** eharney has joined #openstack-meeting12:56
*** whoami-rajat has joined #openstack-meeting13:00
*** Luzi has quit IRC13:02
*** rbudden has joined #openstack-meeting13:03
*** ociuhandu has quit IRC13:06
*** mriedem has joined #openstack-meeting13:15
*** donghao has quit IRC13:19
*** bauzas has quit IRC13:21
*** enriquetaso has quit IRC13:23
*** bauzas has joined #openstack-meeting13:28
*** davee_ has joined #openstack-meeting13:34
*** davee__ has joined #openstack-meeting13:35
*** ociuhandu has joined #openstack-meeting13:38
*** njohnston has quit IRC13:38
*** njohnston_ has joined #openstack-meeting13:41
*** ociuhandu has quit IRC13:43
*** markvoelker has quit IRC13:46
*** jawad_axd has quit IRC13:51
*** liuyulong_ has joined #openstack-meeting13:55
*** markvoelker has joined #openstack-meeting13:56
liuyulonghi13:57
liuyulong_hi13:57
*** rcernin has quit IRC13:57
liuyulongseems the connection is not so much good...13:57
liuyulong#startmeeting neutron_l313:59
openstackMeeting started Wed Oct 16 13:59:03 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: neutron_l3)"13:59
openstackThe meeting name has been set to 'neutron_l3'13:59
liuyulong#chair liuyulong_13:59
openstackCurrent chairs: liuyulong liuyulong_13:59
*** abishop has quit IRC14:00
*** abishop has joined #openstack-meeting14:00
liuyulongOK, wait a few minute for more people...14:00
slaweqhi14:01
liuyulong_hi14:01
liuyulong_#chair slaweq14:02
openstackCurrent chairs: liuyulong liuyulong_ slaweq14:02
liuyulong#chair slaweq14:02
openstackCurrent chairs: liuyulong liuyulong_ slaweq14:02
ralonsohhi14:02
slaweqhaleyb: njohnston_ ralonsoh bcafarel tidwellr: L3 team meeting, are You joining?14:02
haleybhi14:03
bcafarelo/14:03
haleybi'm half here14:03
slaweqping works ;)14:03
slaweqhi :)14:03
bcafarelhalf a haleyb is already good :)14:03
liuyulong_#chair haleyb14:03
openstackCurrent chairs: haleyb liuyulong liuyulong_ slaweq14:03
liuyulong_Add more chairs just in case if I lose the connection...14:03
slaweqso "hal" or "eyb" is on the meeting?14:03
slaweq;)14:04
bcafarel:)14:04
liuyulong_OK, let's start14:04
liuyulong_#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:04
liuyulong_#link https://etherpad.openstack.org/p/Shanghai-Neutron-Planning14:05
*** jawad_axd has joined #openstack-meeting14:05
liuyulong_One more time for collecting topics...14:05
liuyulong_slaweq you will schedule all these topics to one specific PTG time slot right?14:06
slaweqliuyulong_: yes, I will work on agenda14:06
liuyulong_slaweq, maybe not 'all', just some of them.14:07
slaweqI want to start working on it in the week before summit14:07
*** tssurya has joined #openstack-meeting14:07
*** liuyulong has quit IRC14:08
*** liuyulong has joined #openstack-meeting14:10
liuyulongsorry, I lost the connection, I'm home when we have the L3 meeting, there must be heavy load on internet export of the building or community every night.14:12
*** liuyulong_ has quit IRC14:12
liuyulongAm I missed something?14:13
liuyulongping...14:13
bcafarelliuyulong: if you got slaweq saying "I'll handle it" regarding planning you're all good :)14:14
*** liuyulong_ has joined #openstack-meeting14:15
slaweqbcafarel: I have to handle that ;)14:15
slaweqso I will try to do my best14:15
bcafarelknowing you that will be more than enough!14:15
slaweqliuyulong: please just add as many topics to the etherpad as You want :)14:16
slaweqliuyulong: and don't worry about agenda14:16
slaweqbcafarel: thx :)14:16
liuyulong_I'm back... and reading the log...14:16
liuyulong_slaweq, thanks, it will be great, : )14:17
liuyulong_next thing is the team dinner during every summit, slaweq just mentioned me that on Monday, and I've never joined that ever.14:19
*** ociuhandu has joined #openstack-meeting14:19
slaweqliuyulong_: I see that people are putting info about possible dates in etherpad14:19
slaweqso far it looks for me that Tue or Wed will be the best day14:20
slaweqbut lets wait few more days until we will start looking for something14:20
liuyulong_OK, I see that14:21
liuyulong_so, where should be the best place for the dinner? near the hotel ?14:22
liuyulong_Four Points by Sheraton Shanghai, Pudong -  Address: No 2111 Pudong Nan Road, Shanghai, Shanghai, 200127, China14:24
liuyulong_This is the Travel Support booked hotel for me.14:24
slaweqliuyulong_: lets talk about it later and focus here on L3 stuff maybe :)14:25
*** liuyulong has quit IRC14:25
njohnston_o/14:25
liuyulong_slaweq, sure14:27
liuyulong_Move on14:28
liuyulong_#topic Bugs14:28
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:28
*** liuyulong has joined #openstack-meeting14:28
liuyulong_No deputy bug report mail received this week, so let's go through the LP bug list.14:30
liuyulong_sorry, it is here14:31
liuyulong_#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010107.html14:31
liuyulong_#link https://bugs.launchpad.net/neutron/+bug/184701914:31
openstackLaunchpad bug 1847019 in neutron "test_update_firewall_calls_get_dvr_hosts_for_router failure on rocky" [Critical,In progress]14:31
liuyulong_The patch is merged14:32
bcafarelhttps://review.opendev.org/#/c/687085/ yes14:32
liuyulong_This LP bug status is not right, I guess.14:32
*** liuyulong has quit IRC14:33
*** liuyulong has joined #openstack-meeting14:34
*** ociuhandu has quit IRC14:35
liuyulong_Next14:35
liuyulong_#link https://bugs.launchpad.net/neutron/+bug/184720314:35
openstackLaunchpad bug 1847203 in neutron "l3-agent stops processing router updates" [Undecided,New]14:35
slaweqright, LP bug status is not changed when "only" patch for stable branch is merged14:35
slaweqI will update it manually now14:35
liuyulong_Some possible reasons could be the centralized lock or the wrapper deamon.14:38
liuyulong_We have done some optimizing work in master branch, but some of them are never backported to stable branches.14:39
liuyulong_If there are large sets of routers for the L3 agent, the router sometimes can indeed blocked a really long time before staring processing.14:39
*** davidsha has joined #openstack-meeting14:41
liuyulong_We met such similar issue.14:41
slaweqbut in this case, according to what reported said, it's not like it takes long time to process router14:41
slaweqbut there is nothing in logs simply, like agent would hangs14:42
liuyulong_Here are some optimization measures: 1. set use_helper_for_ns_read = False and root_helper_daemon= for l3-agent in l3_agent.ini14:42
liuyulong_2. upgrade to stable/stein cloud catch most of those patch sets, or backport the related patches...14:43
liuyulong_That's all L3 related bugs from the deputy.14:45
liuyulong_Sorry, I can not see any response from the freenode server...14:46
*** dtrainor has quit IRC14:46
haleybperiodic_sync_routers_task() doesn't have to do anything, it can just return, it's running via the oslo_service library14:47
*** jawad_axd has quit IRC14:48
liuyulong_haleyb, slaweq, please take over the meeting, I may not be able to handle it now...14:49
liuyulonghaleyb, slaweq, please take over the meeting, I may not be able to handle it now...14:49
haleybliuyulong: ack14:49
haleybslaweq: i'll add a comment to the bug about putting a LOG.debug when it returns because there's nothing to do, and ask about oslo-service version14:50
*** priteau has joined #openstack-meeting14:51
*** ociuhandu has joined #openstack-meeting14:51
slaweqhaleyb: I think I already asked for some additional debug log from them, You can explain in more detailed way where to put such additional logging14:51
haleybslaweq: ack14:52
*** ociuhandu has quit IRC14:52
*** ociuhandu has joined #openstack-meeting14:53
*** markvoelker has quit IRC14:54
*** ociuhandu has quit IRC14:54
*** markvoelker has joined #openstack-meeting14:54
*** ociuhandu has joined #openstack-meeting14:54
haleybi have another meeting....14:55
*** links has quit IRC14:55
ralonsohtime is over14:59
*** munimeha1 has joined #openstack-meeting14:59
haleyb#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Wed Oct 16 14:59:15 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-10-16-13.59.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-10-16-13.59.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-10-16-13.59.log.html14:59
slaweqo/15:01
*** panda|drappt is now known as panda15:09
*** liuyulong_ has quit IRC15:10
*** trident has quit IRC15:13
*** trident has joined #openstack-meeting15:17
*** mattw4 has joined #openstack-meeting15:20
*** rsimai is now known as rsimai_away15:23
*** gyee has joined #openstack-meeting15:28
*** ociuhandu has quit IRC15:33
*** ttsiouts has quit IRC15:39
*** ttsiouts has joined #openstack-meeting15:40
*** tssurya has quit IRC15:43
*** ttsiouts has quit IRC15:44
*** jawad_axd has joined #openstack-meeting15:47
*** diablo_rojo has joined #openstack-meeting15:48
*** tosky has joined #openstack-meeting15:48
*** rfolco|ruck has quit IRC15:49
*** jawad_axd has quit IRC15:52
*** ociuhandu has joined #openstack-meeting15:55
*** ociuhandu has quit IRC15:56
*** ociuhandu has joined #openstack-meeting15:56
jungleboyj#startmeeting Cinder16:01
openstackMeeting started Wed Oct 16 16:01:35 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
smcginniso/16:01
*** openstack changes topic to " (Meeting topic: Cinder)"16:01
openstackThe meeting name has been set to 'cinder'16:01
davidshao/16:01
geguileohi! o/16:01
jungleboyj@!16:01
_pewp_jungleboyj (โœงโˆ‡โœง)โ•ฏ16:01
eharneyhi16:01
e0nehi16:02
toskyo/16:02
carlosshi16:02
lsekihi16:02
davee__o/16:02
jungleboyjHowdy everyone.16:02
davee__greetings all16:03
jungleboyjGive everyone another minute to join.16:03
*** lpetrut has quit IRC16:04
walshh_hi all16:04
jungleboyjOk.  Lets get started.16:05
jungleboyjOur last Train meeting.16:05
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-meetings16:05
jungleboyjAnd, therefore I guess the last meeting that I will be running.  :-)16:06
jungleboyj#topic announcements16:06
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:06
jungleboyjSo, next week we will switch to the Usurri meeting etherpad.16:06
jungleboyj#link https://etherpad.openstack.org/p/cinder-ussuri-meetings16:06
jungleboyjIf you have topics for next week please put them in there.16:07
jungleboyjBTW, Brian isn't feeling well today so I am going to run things.16:08
jungleboyjFor this meeting.16:08
*** tesseract has quit IRC16:08
jungleboyjAnyway, want to get feedback on how to handle the ping list.16:08
jungleboyjBrian has copied it over right now.  Do we want to keep the current list or remove it and start fresh?16:09
* jungleboyj hears crickets16:09
e0neAFAIR, we usually start with an empty list each release16:09
smcginnisI think start fresh.16:09
davee__start fresh to trim dead weight16:09
smcginnisKind of the reason to have a new etherpad anyway...16:10
*** anastzhyr has joined #openstack-meeting16:10
jungleboyjOk, so, I will add a new ping list out there and give it a couple of meetings then we will remove the old list.16:10
jungleboyjThanks for the feedback.16:11
jungleboyjReminder to please add to the PTG planning list:16:11
jungleboyj#link https://etherpad.openstack.org/p/cinder-ussuri-ptg-planning16:11
jungleboyjNot a lot of content right now.  Don't want to go all the way to Shanghai for nothing.  ;-)16:11
davee__frequent flier miles for that trip is not exactly nothing ;)16:12
smcginnisMaybe a good task for Brian to post the ML to try to get some topic on there from the Chinese community.16:12
jungleboyjdavee__:  True.  And I am already Comfort + there and back.16:13
whoami-rajatHi16:13
jungleboyjOk.  So, Forum Sessions.  We have these two accepted:16:14
jungleboyj#link https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24404/how-are-you-using-cinders-volume-types16:14
jungleboyj#link https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24403/are-you-using-upgrade-checks16:14
*** macz has joined #openstack-meeting16:14
jungleboyjIf you have notes, discussion points, etc. on these please add them here:16:14
jungleboyjhttps://etherpad.openstack.org/p/cinder-shanghai-forum-proposals16:14
jungleboyj#link https://etherpad.openstack.org/p/cinder-shanghai-forum-proposals16:15
jungleboyjWe will get them into etherpads for discussion at the summit.16:15
jungleboyjOk.  That was what I had for announcements.16:15
*** rfolco has joined #openstack-meeting16:15
jungleboyj#topic follow-up discussion on Removing Legacy Attach Code in Nova16:15
*** openstack changes topic to "follow-up discussion on Removing Legacy Attach Code in Nova (Meeting topic: Cinder)"16:15
jungleboyjSo, we said we would continue this discussion this week.16:15
jungleboyjgeguileo: mriedem Updates here?16:16
geguileojungleboyj: I had a look at the mail thread, replied, and then got dragged into fixing FC in OS-Brick, so I'm not up to date with the conversation16:16
jungleboyjgeguileo:  Ok.  I don't think there was a lot more discussion after your last note.16:17
geguileojungleboyj: I think there was a reply16:17
geguileojungleboyj: but in summary I don't think Nova should try to find a flow with what we have that works for all cases16:18
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010066.html16:18
geguileoI think we should add new functionality to Cinder16:18
*** rfolco has quit IRC16:18
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010069.html16:18
smcginnisThat sounded like the best path forward.16:18
geguileoone that allows them to add the connection_info16:18
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010071.html16:18
geguileoon the Cinder attachment object16:18
*** rfolco has joined #openstack-meeting16:18
jungleboyjgeguileo:  Ok, and I think that was the general agreement for last week's meeting as well.16:19
smcginnisI get a vague feeling that was discussed with John as these APIs were being designed and shot down, but I have no idea why at this point.16:19
smcginnisMaybe it was a slightly different idea though.16:19
geguileoI don't know16:19
jungleboyjsmcginnis:  That does feel slightly familiar.16:19
*** rfolco is now known as rfolco|ruck16:20
*** diablo_rojo has quit IRC16:20
geguileobut I think that that's the option that reduces the chances of finding weird bugs16:20
smcginnisWell, unless someone steps forward with an argument of why it shouldn't be done, I think it makes sense given the current use case.16:20
geguileothat will be blamed on Cinder even if it's not our "fault"16:20
*** diablo_rojo has joined #openstack-meeting16:20
geguileosmcginnis: +116:20
*** samP has quit IRC16:21
smcginnisTangential, but Matt had a good idea for a tempest plugin test to enforce the initialize_connection issue.16:21
smcginnisBut then, that's only really useful if the CIs actually run with the tempest plugin, which I think right now they do not.16:21
smcginnisAt least the majority of them.16:21
davee__user:: I didn't say it was your fault, I said I blamed you16:21
geguileosmcginnis: what was that meant to test?16:22
mriedemthat creating more than 1 attachment with the same host connector doesn't result in multiple backend connections16:22
mriedemi.e. that the driver code was idempotent i think16:22
smcginnisThe after the fact assumption enforced by nova that calling initialize_connection multiple times would be idempotent.16:22
geguileomriedem: but that's not a requirement in Cinder16:22
smcginnisdavee__: ++ :D16:22
geguileomriedem: it's something that we should have been explicit about, but we weren't16:23
geguileobecause we don't have the driver interface properly documented16:23
mriedemgiven the api isn't even documented i'm not sure how anyone outside of digging into the cinder code would know the intentions of the api16:23
toskysmcginnis: let's start from the basics: how do we force he CIs to run the tests from cinder_tempest_plugin?16:23
smcginnistosky: Best we've been able to come up with is a periodic review of what they are actually running.16:24
jungleboyjtosky: Oh, that is a whole other discussion.16:24
jungleboyjsmcginnis: ++16:24
smcginnisSince everyone reports a slightly different format, hard to automate the checking.16:24
toskyit may be useful for other tests too16:24
mriedembefore going off and adding a spec and new API for updating the connection_info on an attachment, geguileo should probably read my response16:24
*** jawad_axd has joined #openstack-meeting16:24
mriedembecause i also feel like jgriffith would be rolling in his grave talking about adding that :)16:24
smcginnis:D16:24
jungleboyjHa!16:25
geguileomriedem: I will read the reply, but I don't think my recommendation will change...16:25
smcginnisIf we say his name three times, maybe he'll show up and review it. ;)16:25
jungleboyjhttps://gph.is/1u23SD716:26
jungleboyjsmcginnis: You mean jgriffith16:26
geguileothe 2 APIs were not meant to be mixed16:26
davee__smcginnis: or stab you in the ear with a Q-tip16:26
mriedemwhat is wrong with this again:16:26
mriedem1. create new attachment,16:26
mriedem2. complete that attachment,16:26
mriedem3. call os-terminate_connection for the old attachment with the old host connector?16:26
mriedemwell, the order there is wrong16:27
geguileo#2 may create a different mapping on the backend or may not16:27
*** jbadiapa has quit IRC16:27
mriedemhow is that different from migrating a server?16:28
jungleboyjI was going to say that this would be good for a cross project discussion (yelling across the room we will be in) but mriedem is lucky enough to avoid the trip across the pond.16:29
mriedemi.e. create a new attachment on dest host, terminate the connection for the source host, complete the dest host attachment to put the volume back into in-use status16:29
*** psachin has quit IRC16:29
geguileomriedem: because migrating uses 2 different hosts16:29
geguileomriedem: and the bug in Nova where it was calling Cinder initialization a second time was fixed16:30
mriedemi'd have to confirm but i wouldn't be surprised if we do ^ for same-host resize as well16:30
mriedemgeguileo: you're talking about live migratoin right16:30
mriedem?16:30
geguileomriedem: yup16:30
mriedemi mean even just simple same-host resize16:30
geguileomriedem: then you may get a similar bug16:31
*** samP has joined #openstack-meeting16:31
geguileoI don't know the Nova code16:31
mriedemwhich would have been around since....forever16:31
mriedemi would need to confirm we do that for same host resize but i don't have anything coming to mind that we treat same-host resize different wrt volumes16:31
mriedemanyway we can move to the ML thread again16:32
mriedemand yeah i won't be in shanghai16:32
*** tidwellr has quit IRC16:33
jungleboyjOk.  Lets move this to the ML if you can keep working this geguileo ?16:34
geguileomriedem: the paths of old terminate and removing an attachment are completely different16:34
mriedemnot from a nova pov16:35
geguileorofl rofl rofl16:35
geguileogood for you16:35
*** jbadiapa has joined #openstack-meeting16:35
mriedemmy point is if this is a problem where the host doesn't change for some drivers, it's been a problem forever16:35
geguileoyou say it as if that would surprise you...16:36
mriedemno it wouldn't16:37
mriedemnothing surprises me in openstack anymore16:37
mriedemi'm surprised when shit *works*16:37
* jungleboyj shakes my head16:37
jungleboyjOk.  Lets move on to the other topics and we can keep working this one in the channel or through the ML.16:38
jungleboyjAny disagreement?16:38
mriedemnope16:39
*** markvoelker has quit IRC16:39
jungleboyjOkie dokie.16:41
jungleboyj#topic Team Dinner at Shanghai PTG.16:41
*** openstack changes topic to "Team Dinner at Shanghai PTG. (Meeting topic: Cinder)"16:41
jungleboyjAnyone interested in doing this?16:41
e0ne+116:41
jungleboyjThere is 1 yes.16:41
jungleboyje0ne:  You will be there?16:42
geguileojungleboyj: +116:42
e0nejungleboyj: yes, just booked a hotel and flights16:42
smcginnisI like food.16:42
jungleboyjOh yeah, there have been some updates in the etherpad.16:42
jungleboyjActually have a good list of people there.16:43
jungleboyjsmcginnis:  So do I.  Too much.16:43
jungleboyjOk, so, it sounds like there is interest.  I will work with Brian to plan something.16:44
lseki +116:44
geguileojungleboyj: thanks!16:44
jungleboyj#action jungleboyj  to work with rosmaita to plan a dinner.  Can talk about nights, etc in next week's meeting.16:44
jungleboyj#topic recording of PTG meetings16:45
*** openstack changes topic to "recording of PTG meetings (Meeting topic: Cinder)"16:45
jungleboyjSo, Given the great firewall, I am trying to decide what we want to do here.16:45
jungleboyjI am going to sign up for a VPN that is supposed to work, but who knows.16:46
jungleboyjI am also only taking my work laptop.  Not personal one.16:47
e0neas a backup plan, we can record it and publish videos after the PTG16:47
jungleboyjI see that we have a few people listed as remote attendees.16:47
jungleboyje0ne: True.  Also concerned by the fact that we are all going to be in one big room.16:48
smcginnisI like that plan e0ne.16:48
geguileojungleboyj: true, everyone in one room should not be great for remotees16:48
smcginnisEven if we can't do real time, we can at least record things for others to watch later.16:48
smcginnisYou know, if they have trouble sleeping or something.16:48
jungleboyjsmcginnis:  So we will have at least content like I the other events.16:48
geguileoyeah, that would be nice16:49
whoami-rajatGlad I'm not remote this time :)16:49
*** markvoelker has joined #openstack-meeting16:49
davee__can anyone point out where to find more info on doing that remote since I cannot attend this one?16:49
jungleboyjOk.  So I will still bring my big Mic and camera.16:49
jungleboyjdavee__:  Well, we will put info in the etherpad and IRC as it happens if we are able to do so.16:50
*** rpittau is now known as rpittau|afk16:50
jungleboyjI will need someone to take over recording on the second day as I will be in TC meetings.16:50
jungleboyjOk.  That answers my question there.16:51
*** ociuhandu_ has joined #openstack-meeting16:51
jungleboyj#topic Update of legacy jobs for moving to py3 only.16:51
*** openstack changes topic to "Update of legacy jobs for moving to py3 only. (Meeting topic: Cinder)"16:51
jungleboyjWho added this topic?16:52
smcginnisAh, that'd be me.16:52
jungleboyj:-)16:52
smcginnisJust a heads up to start thinking or researching.16:52
jungleboyjsmcginnis:  Take it away.16:52
smcginnisI know we have a PTG topic to talk about moving to py3 only.16:53
smcginnisOne thing that I saw somewhere was a mention that some of the legacy jobs may not be set up right to run on a py3-only node.16:53
smcginnisI'm not sure if we are impacted or not.16:53
smcginnisWe have the LIO-barbican job.16:53
smcginnisAnd I think we run a few others that are not in-tree.16:53
toskyif a certain zuul patch lands, we may quickly kill a few of the legacy jobs16:53
smcginnisOK, great. Thanks tosky.16:54
smcginnisI don't really have the bandwidth to investigate, so I wanted to at least make sure others were aware of it.16:54
tosky(see my pending patches; of course you all can start checking if they do what they are supposed to do in the meantime :)16:54
smcginnistosky: Do you have a link to that patch?16:54
smcginnisWould be great if folks could review those and get them through.16:54
*** ociuhandu has quit IRC16:54
smcginnisThat would be one less concern for the migration.16:54
smcginnisNothings finalized with the overall plan, but the hope is to be able to drop py2 support by milestone 1.16:55
smcginnisSo really just a couple months to identify any blockers to doing that.16:55
smcginnisAnd personally, I really wish I had more time to rip out all that compat code. :)16:55
toskyuhm, https://review.opendev.org/#/q/status:open+owner:%22Luigi+Toscano+%253Cltoscano%2540redhat.com%253E%22++topic:zuulv316:55
smcginnisAwesome, thanks tosky16:56
jungleboyjhttps://gph.is/2F9U7tV16:56
toskyand also this zuul patch: https://review.opendev.org/#/c/674334/ (but you can see that from the dependency)16:56
smcginnisCool, I will try to review those later.16:57
jungleboyjCool.16:57
smcginnisI guess that's all from me. Running out of time anyway.16:57
jungleboyjAnything else there smcginnis16:57
smcginnisNope16:57
jungleboyjOk.16:57
jungleboyj#topic open discussion16:57
*** openstack changes topic to "open discussion (Meeting topic: Cinder)"16:57
*** mattw4 has quit IRC16:57
jungleboyjAny topics for the last 3 minutes/16:57
anastzhyrIn the end,  I wanted to say hello to everyone,  I am a newbie in Cinder16:57
jungleboyjanastzhyr: Welcome!16:57
anastzhyrAnd I wanted to contribute to Cinder+Tempest16:58
toskyas a follow-up to my previous question (how do we force 3rd party CIs to run the cinder_tempest_plugin?)16:58
jungleboyjanastzhyr:  Let us know if you have questions.16:58
*** ociuhandu_ has quit IRC16:58
toskywelcome anastzhyr16:58
anastzhyrAnd I would be happy for any help and support in my first steps in open source16:58
jungleboyjtosky:  Need to go through the logs and see who is running them and not.16:58
anastzhyrThanks a lot16:58
smcginnisWelcome anastzhyr!16:59
toskyjungleboyj: I guess we don't have a unified log place; but do all of them at least publish the subunit file?16:59
toskywe can probably discuss it after the meeting, or next week16:59
whoami-rajattosky: I think improving the test coverage in cinder-tempest-plugin is also a related topic16:59
jungleboyjwhoami-rajat:  ++16:59
smcginnistosky: They should be. But then, they also should be running the plugin tests.16:59
smcginnisAnd should be running py3, and should be .....16:59
anastzhyrRight now I start with unit tests for creating and deleting volumes17:00
jungleboyjThere isn't a unified log location.17:00
toskythe two issues can be solved in parallel (making sure that the CIs run the plugin, and that the test coverage is increased)17:00
smcginnisTimes up17:00
jungleboyjI usually start with http://cinderstats.ivehearditbothways.com/cireport.txt and go look at what they push up.17:00
toskyack, thanks!17:00
jungleboyjOk.  We need to stop for today.  We can take this discussion to the cinder channel.17:00
*** mattw4 has joined #openstack-meeting17:00
jungleboyjanastzhyr:  Join us in #openstack-cinder if you have more question.17:00
jungleboyjThanks everyone!17:00
whoami-rajatThanks!17:00
jungleboyj#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:01
openstackMeeting ended Wed Oct 16 17:00:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-16-16.01.html17:01
davidshaThanks!17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-16-16.01.txt17:01
*** davidsha has quit IRC17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-16-16.01.log.html17:01
*** tosky has left #openstack-meeting17:01
*** e0ne has quit IRC17:01
*** markvoelker has quit IRC17:01
*** baojg has quit IRC17:02
*** enriquetaso has joined #openstack-meeting17:07
*** jamesmcarthur has quit IRC17:09
*** markvoelker has joined #openstack-meeting17:13
*** markvoelker has quit IRC17:13
*** markvoelker has joined #openstack-meeting17:14
*** ociuhandu has joined #openstack-meeting17:18
*** munimeha1 has quit IRC17:18
*** ociuhandu has quit IRC17:23
*** priteau has quit IRC17:27
*** ociuhandu has joined #openstack-meeting17:30
*** ociuhandu has quit IRC17:35
*** ricolin has quit IRC17:36
*** dklyle has quit IRC18:00
*** david-lyle has joined #openstack-meeting18:00
*** davee_ has quit IRC18:01
*** mattw4 has quit IRC18:13
*** mattw4 has joined #openstack-meeting18:15
*** e0ne has joined #openstack-meeting18:18
*** jamesmcarthur has joined #openstack-meeting18:23
*** mattw4 has quit IRC18:23
*** kopecmartin is now known as kopecmartin|off18:24
*** mattw4 has joined #openstack-meeting18:25
*** diablo_rojo has quit IRC18:32
*** diablo_rojo has joined #openstack-meeting18:35
*** ralonsoh has quit IRC18:37
*** dtrainor has joined #openstack-meeting18:40
*** e0ne has quit IRC18:57
*** enriquetaso has quit IRC19:25
*** jawad_axd has quit IRC19:30
*** lbragsta_ has joined #openstack-meeting19:48
*** markvoelker has quit IRC19:58
*** markvoelker has joined #openstack-meeting19:58
*** anastzhyr has quit IRC20:12
*** jamesmcarthur has quit IRC20:14
*** igordc has joined #openstack-meeting20:15
*** jamesmcarthur has joined #openstack-meeting20:16
*** jamesmcarthur has quit IRC20:18
*** mattw4 has quit IRC20:19
*** mattw4 has joined #openstack-meeting20:22
*** enriquetaso has joined #openstack-meeting20:23
*** pcaruana has quit IRC20:28
*** abishop has quit IRC20:52
*** jamesmcarthur has joined #openstack-meeting20:53
timburke#startmeeting swift21:00
openstackMeeting started Wed Oct 16 21:00:25 2019 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
kota_hello21:01
rledisezo/21:01
*** patchbot has joined #openstack-meeting21:01
*** alecuyer has joined #openstack-meeting21:01
tdasilvao/21:02
timburkeagenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
alecuyero/21:02
timburkei saw a few interesting things this week, so let's jump right in21:02
timburke#topic shanghai21:02
*** openstack changes topic to "shanghai (Meeting topic: swift)"21:02
timburkeit's coming up so quickly! less than three weeks away!21:03
*** abishop has joined #openstack-meeting21:03
timburkeetherpad's at https://etherpad.openstack.org/p/swift-ptg-shanghai21:03
timburke#link https://etherpad.openstack.org/p/swift-ptg-shanghai21:03
timburkeand i need to start putting slides together :-)21:03
timburkemainly just wanted to do a quick reminder about the etherpad again21:04
timburke#topic train release21:04
*** openstack changes topic to "train release (Meeting topic: swift)"21:04
timburkethe openstack train release is officially out!21:04
timburke#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010156.html21:05
kota_good21:05
timburkea few last-minute py3 bugs were identified in swift, but zaitcev, tdasilva, and clayg were really fast to review them21:06
timburkeand backports are already landed on stable/train21:06
timburkei've got a changelog update at https://review.opendev.org/#/c/688848/21:06
patchbotpatch 688848 - swift (stable/train) - CHANGELOG for 2.23.1 - 1 patch set21:06
timburkeand i'll aim to have a 2.23.1 release later this week21:06
timburkebug fixes were p 688767, p 688766, p 688769, p 688768, and p 68880821:07
patchbothttps://review.opendev.org/#/c/688767/ - swift (stable/train) - Fix kms_keymaster under Python 3 (MERGED) - 1 patch set21:07
patchbothttps://review.opendev.org/#/c/688766/ - swift (stable/train) - py3: Fix swift-drive-audit (MERGED) - 1 patch set21:07
patchbothttps://review.opendev.org/#/c/688769/ - swift (stable/train) - py3: Fix swift-recon (MERGED) - 1 patch set21:08
patchbothttps://review.opendev.org/#/c/688768/ - swift (stable/train) - py3: fix swift-dispersion-populate (MERGED) - 1 patch set21:08
patchbothttps://review.opendev.org/#/c/688808/ - swift (stable/train) - py3: fix swift-account-audit (MERGED) - 1 patch set21:08
tdasilvainteresting that p 688848 builds a docker image, if it gets promoted in docker hub, i might be table to tag with a release 2.23.121:08
patchbothttps://review.opendev.org/#/c/688848/ - swift (stable/train) - CHANGELOG for 2.23.1 - 1 patch set21:08
timburkespeaking of releases and images...21:09
timburke#topic centos8 images are available21:09
*** openstack changes topic to "centos8 images are available (Meeting topic: swift)"21:09
timburke#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010146.html21:09
tdasilvatimburke: can we also backport the build py3 docker images patch?21:09
timburketdasilva, i think that seems reasonable21:10
timburkecentos8 is mostly just an fyi. i know we use centos7 for our probe tests, maybe i'll finally sort out how to make probe tests run in the gate on py321:10
timburkemore release news...21:10
timburke#topic py3821:11
*** openstack changes topic to "py38 (Meeting topic: swift)"21:11
timburkeif you missed it, python 3.8 is out!21:11
timburke#link https://docs.python.org/3/whatsnew/3.8.html21:11
timburkei've already started trying it out (since i've still got py3 freshly loaded into my head)21:11
timburkea few bugs shook out, like the arg to pickle.load() needing to implement readinto() and the cgi module losing some functions21:13
timburkebut on the whole, seems pretty tame! not sure when it'll be available for gate jobs, though21:13
timburkeand on the topic of cpython...21:14
timburke#topic dropping support for py2 within openstack21:14
*** openstack changes topic to "dropping support for py2 within openstack (Meeting topic: swift)"21:14
timburke#link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html21:14
alecuyerOh I saw that.. but some of your py3 patches are still pending right?21:15
timburkediscussions have started regarding when and how and with what sort of communication projects can start dropping py2 support21:15
timburkealecuyer, on 3.8? yeah, https://review.opendev.org/#/c/688591/ landed21:16
patchbotpatch 688591 - swift - py38: Provide readinto() interface for RingReader (MERGED) - 1 patch set21:16
timburkebut https://review.opendev.org/#/c/688594/ is still outstanding21:16
patchbotpatch 688594 - swift - py38: cgi lost some names - 1 patch set21:16
timburkei'm kinda tempted to wait a little and see what six does with https://github.com/benjaminp/six/pull/290 / https://github.com/benjaminp/six/issues/15921:16
timburkeon the py2 front, of course, we already talked about wanting to continue support for a while, in part to continue supporting anyone with xenial's distro python packages21:18
*** igordc has quit IRC21:19
timburkei'll continue to push for keeping py2 testing viable, but it's something to be aware of as the ussuri cycle unfolds21:20
timburkethose are all the general announcements i had21:20
timburkedoes anyone have any questions or comments on them?21:20
tdasilvatimburke: thanks for keeping us updated21:21
timburke๐Ÿ‘21:22
timburkei know i got a lot of value out of having notmyname curate and highlight the bits of the mailing list that were actually relevant when i got burned out on trying to keep up a couple years back :-)21:23
timburkeon to updates!21:23
timburke#topic versioning21:24
*** openstack changes topic to "versioning (Meeting topic: swift)"21:24
timburketdasilva, how are you feeling about https://review.opendev.org/#/c/682382/ ?21:24
patchbotpatch 682382 - swift - WIP: New Object Versioning mode - 13 patch sets21:24
tdasilvamaking progress...21:25
tdasilvaI need to start adding a whole ton of tests around listings21:25
tdasilvaand of course rebase the patch on top of the null-character patch21:25
timburkenice! i'm working on getting https://review.opendev.org/#/c/673682/ rebased on the new swift versioning -- got like 5 of the 8 tests clayg wrote in test/functional/s3api/test_versioning.py passing at the moment21:27
patchbotpatch 673682 - swift - s3api: Implement versioning status API - 3 patch sets21:27
tdasilvatimburke: cool, please feel free to push any new patchsets to p 68238221:28
patchbothttps://review.opendev.org/#/c/682382/ - swift - WIP: New Object Versioning mode - 13 patch sets21:28
timburkewill do. i was thinking about adding an is_latest key when doing ?versions listings...21:28
*** igordc has joined #openstack-meeting21:29
timburketdasilva, anything else people should be aware of, thinking about, or looking at?21:29
*** whoami-rajat has quit IRC21:30
tdasilvano, but i'm sure there will be churn during code review, so the sooner that starts the better :)21:30
timburke#topic lots of small files21:31
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:31
tdasilvaand of course I've been putting off documentation so far, maybe I should start working on that on a separate patch21:31
timburkealecuyer, thanks for fixing up the requirements so https://review.opendev.org/#/c/686846/ could land!21:31
patchbotpatch 686846 - swift (feature/losf) - EC frags are the ones with the # (MERGED) - 2 patch sets21:31
alecuyernp, thanks for your help with it and others21:31
alecuyerI have pushed this small one here https://review.opendev.org/#/c/659254/21:31
patchbotpatch 659254 - swift (feature/losf) - In _get_vfile(), handle the case when a referenced... - 2 patch sets21:31
alecuyerand I need to work on properly detecting and exposing the case where the leveldb database is corrupted21:32
alecuyer(as I mentionned, we currently check this from logs, outside of swift itself)21:32
alecuyerand then we should see if that would have to be monitored by the operator or self-heal21:33
timburkeright... fwiw, needing to fix up swift-drive-audit made me realize we already have some stand-alone tools for parsing kernel logs and such...21:34
timburkeself-heal would be nice, but i think operator-driven would probably be a good initial release21:35
alecuyerIf you think there's a good example there to look at , let me know :)21:35
alecuyerok21:35
timburkeidk -- the fact that we didn't notice that it wasn't py3-ready tells me we don't really use it much, at least in our dev workflows... so might not be the best example ;-)21:36
alecuyerright well I'll do something and we can discuss it21:37
timburke๐Ÿ‘21:37
timburkeall right... with mattoliverau not here, i'm thinking we could probably skip talking about sharding...21:38
timburkeunless someone wants to pick up looking at https://review.opendev.org/#/c/675014/21:38
patchbotpatch 675014 - swift - Latch shard-stat reporting - 4 patch sets21:38
timburkethere's at least one significant issue i need to address, but i think the core of the thing is in pretty good shape21:39
timburke#topic open discussion21:40
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:40
timburkeanything else anyone would like to bring up?21:40
timburkekota_, how was the typhoon? did you and your family have to evacuate?21:43
kota_it was safe on my home including itself.21:44
timburkegood to hear21:44
kota_some part of tokyo affected but here not.21:44
kota_thx21:44
timburkeall right, i suppose we ought to let you go get breakfast :-)21:45
timburkethank you all for coming, and thank you for working on swift!21:45
timburke#endmeeting21:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:45
openstackMeeting ended Wed Oct 16 21:45:35 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-10-16-21.00.html21:45
alecuyerthanks tim, good day/night all21:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-10-16-21.00.txt21:45
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-10-16-21.00.log.html21:45
*** mriedem is now known as mriedem_afk21:46
*** alecuyer has left #openstack-meeting21:46
*** patchbot has left #openstack-meeting21:46
*** mattw4 has quit IRC21:55
*** mattw4 has joined #openstack-meeting21:56
*** raildo has quit IRC21:59
*** slaweq has quit IRC22:00
*** enriquetaso has quit IRC22:09
*** brault has quit IRC22:12
*** brault has joined #openstack-meeting22:12
*** markvoelker has quit IRC22:14
*** lbragsta_ has quit IRC22:26
*** jamesmcarthur has quit IRC22:34
*** david-lyle has quit IRC22:34
*** dklyle has joined #openstack-meeting22:43
*** macz has quit IRC22:56
*** dviroel has quit IRC22:57
*** Lucas_Gray has joined #openstack-meeting23:01
*** bbowen has quit IRC23:02
*** anastzhyr has joined #openstack-meeting23:06
*** diablo_rojo has quit IRC23:10
*** gyee has quit IRC23:16
*** rfolco has joined #openstack-meeting23:25
*** rfolco|ruck has quit IRC23:25
*** mattw4 has quit IRC23:26
*** lbragsta_ has joined #openstack-meeting23:34
*** rfolco has quit IRC23:34
*** rfolco has joined #openstack-meeting23:34
*** Lucas_Gray has quit IRC23:36
*** ykatabam has joined #openstack-meeting23:40
*** verdurin has quit IRC23:40
*** diablo_rojo has joined #openstack-meeting23:45
*** lbragsta_ has quit IRC23:45
*** verdurin has joined #openstack-meeting23:48
*** rfolco has quit IRC23:48
*** enriquetaso has joined #openstack-meeting23:56

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