Wednesday, 2019-09-18

*** lbragstad has quit IRC00:19
*** lbragstad has joined #openstack-meeting00:19
*** ykatabam has quit IRC00:29
*** carloss has quit IRC00:30
*** ykatabam has joined #openstack-meeting00:32
*** jamesmcarthur has joined #openstack-meeting00:42
*** b1airo has quit IRC00:50
*** gyee has quit IRC00:50
*** jamesmcarthur has quit IRC01:07
*** markvoelker has quit IRC01:08
*** slaweq has joined #openstack-meeting01:11
*** slaweq has quit IRC01:16
*** markvoelker has joined #openstack-meeting01:20
*** mhen has quit IRC01:33
*** mhen has joined #openstack-meeting01:33
*** yamamoto has joined #openstack-meeting01:56
*** ykatabam has quit IRC01:57
*** apetrich has quit IRC02:10
*** yamamoto has quit IRC02:21
*** yamamoto has joined #openstack-meeting02:21
*** jamesmcarthur has joined #openstack-meeting02:22
*** jamesmcarthur has quit IRC02:38
*** ykatabam has joined #openstack-meeting02:42
*** baojg has quit IRC02:45
*** baojg has joined #openstack-meeting02:45
*** dviroel has quit IRC02:47
*** jamesmcarthur has joined #openstack-meeting02:47
*** larainema has joined #openstack-meeting02:49
*** hemna has joined #openstack-meeting02:52
*** baojg has quit IRC02:53
*** markvoelker has quit IRC03:09
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** jamesmcarthur has quit IRC03:24
*** jamesmcarthur has joined #openstack-meeting03:36
*** hemna has quit IRC03:40
*** jamesmcarthur has quit IRC03:50
*** ricolin has joined #openstack-meeting03:54
*** rbudden has quit IRC03:56
*** ociuhandu has joined #openstack-meeting04:30
*** janki has joined #openstack-meeting04:34
*** ociuhandu has quit IRC04:35
*** whoami-rajat has joined #openstack-meeting04:38
*** pcaruana has joined #openstack-meeting04:46
*** Luzi has joined #openstack-meeting04:59
*** radeks has joined #openstack-meeting05:04
*** markvoelker has joined #openstack-meeting05:10
*** slaweq has joined #openstack-meeting05:11
*** e0ne has joined #openstack-meeting05:14
*** e0ne has quit IRC05:14
*** markvoelker has quit IRC05:14
*** slaweq has quit IRC05:16
*** e0ne has joined #openstack-meeting05:16
*** e0ne has quit IRC05:50
*** kopecmartin|off is now known as kopecmartin05:54
*** ttsiouts has joined #openstack-meeting06:00
*** ttsiouts has quit IRC06:04
*** slaweq has joined #openstack-meeting06:11
*** slaweq has quit IRC06:16
*** igordc has joined #openstack-meeting06:17
*** igordc has quit IRC06:19
*** e0ne has joined #openstack-meeting06:21
*** e0ne has quit IRC06:26
*** armax has joined #openstack-meeting06:39
*** jawad_axd has joined #openstack-meeting06:47
*** ykatabam has quit IRC06:53
*** slaweq has joined #openstack-meeting06:55
*** armax has quit IRC06:56
*** rcernin has quit IRC06:57
*** apetrich has joined #openstack-meeting06:59
*** Liang__ has joined #openstack-meeting07:08
*** trident has quit IRC07:08
*** _pewp_ has quit IRC07:11
*** _pewp_ has joined #openstack-meeting07:12
*** trident has joined #openstack-meeting07:19
*** rpittau|afk is now known as rpittau07:32
*** radeks has quit IRC07:55
*** radeks has joined #openstack-meeting07:55
*** e0ne has joined #openstack-meeting07:57
*** ralonsoh has joined #openstack-meeting08:04
*** ttsiouts has joined #openstack-meeting08:16
*** ociuhandu has joined #openstack-meeting08:37
*** ociuhandu has quit IRC08:41
*** ykatabam has joined #openstack-meeting08:44
*** ociuhandu has joined #openstack-meeting08:52
*** ociuhandu has quit IRC08:53
*** rubasov has joined #openstack-meeting08:53
*** pcaruana has quit IRC08:57
*** ociuhandu has joined #openstack-meeting08:58
*** pcaruana has joined #openstack-meeting09:01
*** priteau has joined #openstack-meeting09:07
*** yamamoto has quit IRC09:27
*** Liang__ has quit IRC09:32
*** panda|ruck|off is now known as panda|ruck09:37
*** tesseract has joined #openstack-meeting09:44
*** yamamoto has joined #openstack-meeting09:58
*** markvoelker has joined #openstack-meeting09:59
*** markvoelker has quit IRC10:04
*** ociuhandu has quit IRC10:07
*** yamamoto has quit IRC10:07
*** zbr has quit IRC10:11
*** ttsiouts has quit IRC10:12
*** zbr has joined #openstack-meeting10:12
*** ttsiouts has joined #openstack-meeting10:13
*** whoami-rajat has quit IRC10:13
*** ykatabam has quit IRC10:14
*** ociuhandu has joined #openstack-meeting10:14
*** markvoelker has joined #openstack-meeting10:16
*** ttsiouts has quit IRC10:17
*** ociuhandu_ has joined #openstack-meeting10:18
*** markvoelker has quit IRC10:20
*** ociuhandu has quit IRC10:22
*** whoami-rajat has joined #openstack-meeting10:34
*** yamamoto has joined #openstack-meeting10:42
*** ttsiouts has joined #openstack-meeting10:55
*** yamamoto has quit IRC11:12
*** njohnston has joined #openstack-meeting11:13
*** pcaruana has quit IRC11:19
*** e0ne_ has joined #openstack-meeting11:20
*** e0ne has quit IRC11:23
*** armax has joined #openstack-meeting11:24
*** psachin has joined #openstack-meeting11:25
*** pcaruana has joined #openstack-meeting11:28
*** raildo has joined #openstack-meeting11:34
*** hyunsikyang has quit IRC11:35
*** Luzi has quit IRC11:35
*** lseki has joined #openstack-meeting11:37
*** ykatabam has joined #openstack-meeting11:42
*** dviroel has joined #openstack-meeting11:48
*** carloss has joined #openstack-meeting11:48
*** brault has joined #openstack-meeting11:49
*** Luzi has joined #openstack-meeting11:49
*** brault has quit IRC11:53
*** ykatabam has quit IRC11:56
*** ykatabam has joined #openstack-meeting11:58
*** yamamoto has joined #openstack-meeting11:59
*** yamamoto has quit IRC12:02
*** yamamoto has joined #openstack-meeting12:02
*** markvoelker has joined #openstack-meeting12:05
*** brault has joined #openstack-meeting12:06
*** janki has quit IRC12:07
*** jamesmcarthur has joined #openstack-meeting12:09
*** jamesmcarthur has quit IRC12:16
*** njohnston_ has joined #openstack-meeting12:19
*** njohnston has quit IRC12:19
*** armax has quit IRC12:20
*** jamesmcarthur has joined #openstack-meeting12:22
*** armax has joined #openstack-meeting12:28
*** jamesmcarthur has quit IRC12:31
*** brault has quit IRC12:34
*** rbudden has joined #openstack-meeting12:48
*** jamesmcarthur has joined #openstack-meeting12:51
*** mriedem has joined #openstack-meeting12:51
*** brault has joined #openstack-meeting12:52
*** janki has joined #openstack-meeting12:52
*** yamamoto has quit IRC12:53
*** janki has quit IRC12:53
*** yaawang has quit IRC12:56
*** yamamoto has joined #openstack-meeting12:57
*** brault has quit IRC12:58
*** ociuhandu_ has quit IRC13:06
*** ricolin_ has joined #openstack-meeting13:08
*** ricolin has quit IRC13:11
*** ricolin_ is now known as ricolin13:12
*** hemna has joined #openstack-meeting13:16
*** eharney has joined #openstack-meeting13:17
*** shilpasd has joined #openstack-meeting13:17
*** ociuhandu has joined #openstack-meeting13:18
*** ttsiouts has quit IRC13:19
*** eharney has quit IRC13:19
*** ttsiouts has joined #openstack-meeting13:20
*** ttsiouts has quit IRC13:20
*** eharney has joined #openstack-meeting13:20
*** ttsiouts has joined #openstack-meeting13:21
*** rbudden has quit IRC13:22
*** rbudden has joined #openstack-meeting13:23
*** munimeha1 has joined #openstack-meeting13:28
*** newbieMe has joined #openstack-meeting13:31
*** enriquetaso has joined #openstack-meeting13:32
*** whoami-rajat has quit IRC13:33
*** psachin has quit IRC13:33
*** newbieMe has quit IRC13:34
*** armax has quit IRC13:35
*** ociuhandu has quit IRC13:35
*** newbieMe has joined #openstack-meeting13:35
*** armax has joined #openstack-meeting13:36
*** newbieMe is now known as newbieAsh13:39
*** brault has joined #openstack-meeting13:48
*** brault has quit IRC13:48
*** Luzi has quit IRC13:49
*** yamamoto has quit IRC13:49
*** artom has quit IRC13:54
*** enriquetaso has quit IRC13:59
*** enriquetaso has joined #openstack-meeting13:59
*** liuyulong has joined #openstack-meeting14:06
liuyulongSorry, I'm late14:06
liuyulong#startmeeting neutron_l314:06
openstackMeeting started Wed Sep 18 14:06:45 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:06
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:06
openstackThe meeting name has been set to 'neutron_l3'14:06
liuyulong#topic Announcements14:07
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:07
liuyulongI have no announcement today.14:08
liuyulongSo if you have, please go ahead.14:08
liuyulongOK, let's move on.14:09
liuyulong#topic Bugs14:09
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:09
liuyulongMiguel sent this on Sunday.14:10
liuyulongFirst one from the deputy's mail:14:12
openstackLaunchpad bug 1843889 in neutron "Windows: IPv6 tunnel endpoints" [Medium,In progress] - Assigned to Lucian Petrut (petrutlucian94)14:12
haleybhi, i'm in two meetings at once though, will try and lurk here14:12
ralonsohIMO, the patch is OK, although we can't test it in the CI14:12
ralonsohLinux CI14:12
ralonsohbtw, #link
liuyulongYes, thank you, patch is simple. But the bug is abit out of my scope honestly. :)14:13
haleybi +W, looked good and they have been good at fixing this code14:15
*** zhubx has quit IRC14:16
liuyulongYou're one step ahead of me while you are attending two meetings. : )14:16
*** zhubx has joined #openstack-meeting14:17
openstackLaunchpad bug 1844168 in neutron "[L3] TooManyExternalNetworks: More than one external network exists." [Low,In progress] - Assigned to LIU Yulong (dragon889)14:17
ralonsohone question in your patch14:17
ralonsohyou removed the router check14:17
ralonsohsorry, the link14:18
liuyulongIMO, this should be related to the external network removal.14:18
liuyulongonce slaweq and Miguel have done some related work.14:18
ralonsohin this patch, you remove the router compatible check14:18
ralonsohbut I think you should retrieve the external network list (pfor this agent)14:19
ralonsohand then check if the router external network is there --> compatible/not compatible then14:19
haleybi also can't remember removing an rpc, do we need to do that?14:20
ralonsohhaleyb, this method should no be used anymore14:20
ralonsohbecause in case of having more than one ext netowkr, an exception will be thrown14:20
ralonsohbut, now we should have something retrieving the ext network list14:21
haleybit is used by bigswitch, and i didn't know how it would affect a mixed-version environment14:21
liuyulonghmm, I may revisit the history of this check.14:21
liuyulongL3 agent supports muiltple external networks, this check is abit strange14:22
liuyulongIf it is not compatible, it should not be scheduled to that agent. But seems we not can't avoid that.14:23
liuyulongMore interesting thing is if a router is scheduled to L3 agent without external_gateway_info, for instance HA router creation, the compatible check does not make any sense.14:26
ralonsohbut you can check that there is no extneral_gw_info14:27
ralonsohbut if you have, you should check the network ID and if this ext net belongs to this L3 agent14:27
liuyulongThen you set the external gateway info, but you may see no errors, but L3 agent just do nothing for this router update notification.14:28
*** yamamoto has joined #openstack-meeting14:28
slaweqmaybe we should now go quickly with smallest possible fir for this reported bug14:29
slaweqand later we can remove (or deprecate) some not used methods14:29
*** enriquetaso has quit IRC14:30
*** ociuhandu has joined #openstack-meeting14:30
slaweqliuyulong: is this bug happening all the time when there is more than one external network in Neutron?14:32
liuyulongActually the get_external_network_id just get all external networks, it does not have any relationship of L3 agent.14:32
liuyulongslaweq, you can see the log search in the bug description.14:33
slaweqok, that should have IMO higher priority and we should maybe target it for rc-114:33
slaweqwhat do You think?14:33
liuyulongI'm OK with it.14:34
slaweqI will ask mlavalle later about it also14:34
liuyulongslaweq, cool, IMO, it is related to this patch:
*** brault has joined #openstack-meeting14:36
slaweqliuyulong: yes, I'm pretty sure it is :)14:36
liuyulongWe have another merged patch, also did such removal.14:37
*** yamamoto has quit IRC14:37
*** yamamoto has joined #openstack-meeting14:37
liuyulongOK, next one14:39
openstackLaunchpad bug 1844171 in neutron "Configuration parameter missing at "Configure the layer-3 agent"" [Low,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)14:39
liuyulongPatch just get a +W from me. : )14:40
ralonsohtrivial patch IMO, +214:40
*** yamamoto has quit IRC14:40
ralonsoh#link (just in case)14:40
*** yamamoto has joined #openstack-meeting14:40
liuyulongNext two are all related to IPv6:14:41
slaweqI also gave +2 :D14:41
openstackLaunchpad bug 1844097 in neutron "Redundant ipv6 address(SLAAC/DHCPv6 stateless) created for port" [Undecided,New]14:41
openstackLaunchpad bug 1844171 in neutron "Configuration parameter missing at "Configure the layer-3 agent"" [Low,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)14:41
openstackRemoving item from minutes: #link
openstackLaunchpad bug 1844123 in neutron "Unable to trigger IPv6 Prefix Delegation" [Undecided,New]14:42
liuyulongOne can not get IPv6 address, but another just get two...14:42
liuyulongDuring our local testing, we tested the port creation in network with IPv4 and IPv6 subnets.14:44
liuyulongIt works fine, the port will have only one IPv4 addr and one IPv6 addr.14:44
ralonsohI don't understand
openstackLaunchpad bug 1844097 in neutron "Redundant ipv6 address(SLAAC/DHCPv6 stateless) created for port" [Undecided,New]14:45
liuyulongFrom the bug description, seems they do not need that IPv6 address...14:45
ralonsohbut they are creating a port in a network with two subnets14:46
ralonsohipv4 and ipv614:46
liuyulongThey think the IPv6 address is "redundant".14:46
*** jawad_axd has quit IRC14:46
ralonsohwhat they are doing is defining the IPv4 one, but the ipv6 will be assigned automatically14:46
*** jawad_axd has joined #openstack-meeting14:46
*** jawad_axd has quit IRC14:46
ralonsohI'll review this and comment in the bug14:46
*** priteau has quit IRC14:47
liuyulongYes, maybe we can mark it as invalid. It is an feature.14:47
liuyulongOK, I remember another bug.14:48
openstackLaunchpad bug 1752903 in neutron "Floating IPs should not allocate IPv6 addresses" [Medium,New]14:51
*** priteau has joined #openstack-meeting14:51
liuyulongAnd I had a proposal for the port creation API once related to this:
openstackLaunchpad bug 1797140 in neutron "[RFE] create port by providing parameters subnet_id only" [Wishlist,Won't fix] - Assigned to LIU Yulong (dragon889)14:52
liuyulongOK, that's all from me.14:53
liuyulongTime is running out...14:54
liuyulong#topic On demand agenda14:54
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:54
liuyulongOK, continue with the IPv6.14:55
*** priteau has quit IRC14:56
liuyulongNetworkManager seems not work for the VM NICs, the configured IPv6 address is not same to the port IPv6 address.14:56
liuyulongMaybe bad settings.14:57
slaweqliuyulong: what do You mean exactly?14:57
*** priteau has joined #openstack-meeting14:58
slaweqdo You mean that instance have got different IPv6 configured with SLAAC/DHCPv6 instead of what is in Neutron's DB?14:58
liuyulongCentOS7 image's default NetworkManger is mis-configured. IMO14:58
liuyulongslaweq, Yes14:58
slaweqit's "privacy extension"14:59
slaweqbasically IPv6 is given to instance by router based on link local IP which is based on MAC address14:59
slaweqif this extension is enabled, request is done with some "fake" mac address thus router responds with wrong IP address15:00
slaweqif You change this setting in NetworkManager, it will work as expected15:00
liuyulongYes, we are tunning the settings15:00
*** shilpasd has left #openstack-meeting15:01
liuyulongOK, let's stop here.15:02
*** openstack changes topic to "OpenStack Meetings ||"15:02
openstackMeeting ended Wed Sep 18 15:02:15 2019 UTC.  Information about MeetBot at . (v 0.1.4)15:02
openstackMinutes (text):
*** artom has joined #openstack-meeting15:03
*** enriquetaso has joined #openstack-meeting15:03
*** gyee has joined #openstack-meeting15:08
*** mattw4 has joined #openstack-meeting15:09
*** zhengMa has joined #openstack-meeting15:12
*** belmoreira has quit IRC15:19
*** rosmaita has joined #openstack-meeting15:27
*** markvoelker has quit IRC15:35
*** david-lyle has quit IRC15:35
*** dklyle has joined #openstack-meeting15:35
*** zbr has quit IRC15:36
*** ttsiouts has quit IRC15:36
*** zbr has joined #openstack-meeting15:37
*** brinzhang has quit IRC15:37
*** brault has quit IRC15:38
*** panda|ruck is now known as panda15:39
*** trident has quit IRC15:41
*** tosky has joined #openstack-meeting15:45
*** jamesmcarthur has quit IRC15:45
*** ociuhandu has quit IRC15:47
*** jamesmcarthur has joined #openstack-meeting15:47
*** ociuhandu has joined #openstack-meeting15:48
*** ociuhandu has quit IRC15:49
*** ociuhandu has joined #openstack-meeting15:49
*** jamesmcarthur has quit IRC15:49
*** jamesmcarthur has joined #openstack-meeting15:52
*** trident has joined #openstack-meeting15:53
*** markvoelker has joined #openstack-meeting15:53
*** deiter has joined #openstack-meeting15:56
*** jamesmcarthur has quit IRC15:57
*** armax has quit IRC15:58
*** raghavendrat has joined #openstack-meeting15:58
*** jamesmcarthur has joined #openstack-meeting15:59
*** newbieAsh has quit IRC16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Sep 18 16:00:49 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
jungleboyjcourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky sfernand16:01
geguileohi! o/16:01
raghavendrathi everyone16:01
_pewp_jungleboyj ( ^_^)/16:02
jungleboyjLooks like we have the usual suspects here.16:02
*** sfernand has joined #openstack-meeting16:03
*** rpittau is now known as rpittau|afk16:03
jungleboyjLets get started16:04
*** thgcorrea has joined #openstack-meeting16:04
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
jungleboyjI didn't have anything in the etherpad but as I look I should announce that next week is RC-1 Target week.16:04
*** woojay has joined #openstack-meeting16:05
jungleboyjI am also noticing that I didn't get Feature Freeze for us into the schedule.16:05
jungleboyjSo, I guess it is the wild west out there!16:05
*** yamamoto has quit IRC16:06
rosmaita(what is that?)16:06
jungleboyjAnyway, any features that need to go in the release need to be reviewed this week.16:06
jungleboyjSquirt Gun?16:06
jungleboyjClosest thing I could find to represent wild west.  :-)16:06
*** jawad_axd has joined #openstack-meeting16:07
jungleboyjAnyway, Otherwise hopefully people have been testing Cinder and looking for bugs.16:07
rosmaitaworks for me, just didn't render very well in my client16:07
*** zbr is now known as zbr|ruck16:07
* jungleboyj looks at the Red Hat team.16:07
eharneywell i think i found one in my own feature, if that counts16:07
sfernanddriver bug fix should also be merged until next week?16:08
jungleboyj:-(  I guess that is good.16:08
e0ne_sfernand: yes16:08
jungleboyjsfernand: Yes, driver bug fixes can be merged .16:08
jungleboyjUntil we cut the RC.16:08
lsekijungleboyj: RC1 or final RC?16:09
e0ne_lseki: RC16:09
rosmaitawith the RC, the stable branch for train will be cut, and from then on, only backports are allowed16:09
jungleboyjUnless it is a critical bug.16:09
smcginnisWe are in overall feature freeze, so any features we want to land yet should have a FFE on the ML.16:09
e0ne_lseki: after RC1 only critical bugfixes are allowed16:09
lsekie0ne_: got it, thanks!16:09
smcginnisWe only need to add a Cinder specific feature freeze to the schedule if we want something earlier than the overall one.16:10
lsekijungleboyj, e0ne_: got it, thanks!16:10
jungleboyjsmcginnis:  Ok.  Glad I didn't mess that up.16:10
jungleboyjSo any new features for drives need an FFE right now.16:10
smcginnisAnd we also have the hardware acceleration patches that should get an FFE now.16:11
jungleboyjsmcginnis:  ++16:11
*** jawad_axd has quit IRC16:11
raghavendratthis is regarding adding Peer Persistence support feature in HPE 3PAR driver:
jungleboyjwalshh_:  So I think you need to submit one for this:
jungleboyjSame for yours raghavendrat16:12
rosmaitafor the hw accel patch, , does it require an email to the ML, or can we declare it OK here?16:12
*** efried is now known as efried_pto16:13
jungleboyjI am fine with getting it in but I think, officially, we need to have an e-mail.16:14
jungleboyjI defer to smcginnis  though.16:14
smcginnisI can't find it documented anywhere.16:14
smcginnisI think the preference is to have it on the ML so there's a record, but if we just want to approve it here, at least this is recorded to reference later if need be.16:15
smcginnisI like to keep things low overhead when we can.16:15
rosmaitai'm just asking because of the time zone, not sure zheng or liang are here16:15
jungleboyjOk.  So, I am ok with approving it here.  I will review it after the meeting.16:15
rosmaitaok, cool16:15
jungleboyjAny objections?16:16
*** radeks has quit IRC16:16
jungleboyjI will take that as a no.16:17
raghavendratcan anyone please share email id of ML. i will send a mail requesting for review16:17
jungleboyjYeah ... that.  :-)16:18
smcginnisPlease don't send posts to the ML asking for reviews. Or do you mean asking for a feature freeze exception? I think that's covered here now.16:18
*** jawad_axd has joined #openstack-meeting16:18
raghavendratthanks rosmaita:16:18
smcginnisjungleboyj: May want to post something listing the features that have been given approval in this meeting though.16:18
rosmaitawhat smcginnis said, though16:18
jungleboyjsmcginnis:  True.16:18
jungleboyjHmmm, looking at raghavendrat his change is related to a bug.16:19
jungleboyjSo, I think we are ok there.16:19
jungleboyjAny objections?16:20
jungleboyjThe last one would be this one from walshh_  That she just pinged me about:
raghavendratactually its new feature in HPE 3PAR; other drivers already have Peer Persistence16:20
smcginnisWhat is peer persistence? Replciation?16:21
jungleboyjSean already gave it a +2, so I think that is ok for an FFE?16:21
raghavendratyes. Active Active replication16:21
*** jawad_axd has quit IRC16:22
jungleboyjIt is limited to their driver.16:23
jungleboyjCI is passing.16:23
*** gmann is now known as gmann_afk16:23
jungleboyjHave I lost everyone here?16:24
*** ayoung has joined #openstack-meeting16:24
jungleboyjπŸ’£ πŸ’₯16:24
e0ne_jungleboyj: sounds good to me to be merged16:24
raghavendratright. its specific to HPE driver16:24
rosmaitano objection from me16:24
* e0ne_ is bombed 16:24
* jungleboyj laughs16:25
jungleboyjOk.  So, I will send a note saying that the following patches are approved for FFEs: and
jungleboyjTeam.  Please review those to get them merged ASAP.16:26
raghavendratpardon me. FFE means ?16:26
jungleboyjNo further FFEs after that.16:26
jungleboyjFeature Freeze Exception16:26
jungleboyjOk, so that kind of covers the one topic in the agenda.16:27
smcginnisraghavendrat: Further context, we are past this and now need explicit approval to merge anything that can be considered a feature -
jungleboyjTrying to not destabilize the release at the last minute.16:28
jungleboyjSo, the other topic for today.16:28
jungleboyj#topic Ranking the Forum Submissions16:28
*** openstack changes topic to "Ranking the Forum Submissions (Meeting topic: Cinder)"16:28
rosmaitaor, thanks16:29
rosmaitawe've got 3 topics proposed16:29
rosmaitajungleboyj: are you willing to moderate your 2 topics?16:29
*** kopecmartin is now known as kopecmartin|off16:29
jungleboyjSure, if you come help.  :-)16:30
geguileojungleboyj: those are good topics  :-)16:31
rosmaitaok, i will propose those 3 -- the upgrade check could easily be cross project, i will say that we would be happy to have it combined with other proposals on that topic16:31
jungleboyjgeguileo:  Thank you.  Hopefully we get some participation.16:31
geguileoyeah, fingers crossed16:31
jungleboyjrosmaita:  ++16:31
rosmaitadoes anyone have an objection to any of the topics?16:32
rosmaita(otherwise, i will assume approval)16:32
jungleboyjLooks like we have decent support for them in the etherpad.16:32
smcginnisShip it16:32
rosmaitai think we have some room, if the volume types gets rejected, we can combine it with the "crazy about cinder" session16:33
jungleboyjrosmaita:  ++16:33
rosmaitaand i can't imagine we're the only people interested in the upgrade checker16:33
jungleboyjI don't know that I have ever had a Forum session rejected.16:33
jungleboyjWith this Summit, though, who knows!16:33
rosmaitahmmm ... you must be better connected than me, i have had a session rejected!16:34
rosmaitaand have also been asked to combine sessions16:34
rosmaitaanyway, i'll get those proposed before the deadline16:34
jungleboyjOk.  Well, we will see how it goes.  :-)16:34
rosmaitaplease add topics if there are things you'd like to see discussed16:35
jungleboyjrosmaita:  ++16:35
jungleboyjNice to see we have 10 people planning to attend.16:36
rosmaitayes, that is cool16:36
lsekiadding a topic there right now16:36
smcginnisSide note related to one of those topics - I think the TC is waiting for finalization of the CentOS 8 release date to see if we can use that as the official distro for Red Hat based platforms. If we need to stick with 7, that may throw a wrench (or spanner if you're one of those people) into the py3-only plan.16:37
smcginnislseki: Would be great to know which options.16:38
smcginnisWe only every identified logging to start, but never went anywhere from there.16:38
smcginnisPartly because of an oslo bug that would just restart the service anyway.16:38
lsekismcginnis: yep, I'm gonna ask the customer about which options besides credentials16:38
jungleboyjsmcginnis:  Do we need to do anything more to fix that or is it all in Oslo?16:39
bnemecNote that that bug is now fixed.16:39
smcginnisI haven't tested it, but with current upper-constraints theoretically it should all work now.16:40
jungleboyjbnemec:  Cool.  Thanks for pitching in.16:40
jungleboyjI should try that at some point.16:40
bnemecYeah, it's only been tested on Nova. Would be interested to know if it works for Cinder too.16:41
jungleboyjbnemec:  ++16:41
rosmaitaok, that's all from me ... we can move to open discussion16:42
jungleboyj#topic Open Discussion16:42
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:42
jungleboyjDoes anyone have anything else they would like to discuss?16:44
jungleboyjLooks like no?16:46
rosmaitanothing from me16:47
jungleboyjWrong link16:47
jungleboyjWake up people!16:47
*** liuyulong has quit IRC16:47
jungleboyjOk.  I guess we will wrap things up for today then.16:48
*** donghao has quit IRC16:48
jungleboyjThanks for attending.  Please try to review the remaining features that need to get in.16:48
e0ne_see you next week!16:49
*** openstack changes topic to "OpenStack Meetings ||"16:49
openstackMeeting ended Wed Sep 18 16:49:07 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:49
openstackMinutes (text):
*** rosmaita has left #openstack-meeting16:49
*** tosky has left #openstack-meeting16:49
zhengMaThanks team!16:49
jungleboyjYep.  Thanks everyone.16:49
*** e0ne_ has quit IRC16:50
*** zhengMa has quit IRC16:50
*** woojay has left #openstack-meeting16:51
*** macz has joined #openstack-meeting16:51
*** ekcs has joined #openstack-meeting16:52
*** tesseract has quit IRC16:53
*** zhengMa has joined #openstack-meeting16:54
*** raghavendrat has left #openstack-meeting16:55
*** brault has joined #openstack-meeting17:00
*** jamesmcarthur_ has joined #openstack-meeting17:09
*** zhengMa has left #openstack-meeting17:11
*** jamesmcarthur has quit IRC17:12
*** whoami-rajat has joined #openstack-meeting17:20
*** armax has joined #openstack-meeting17:26
*** ricolin has quit IRC17:27
*** armax has quit IRC17:31
*** yamamoto has joined #openstack-meeting17:33
*** zbr|ruck is now known as zbr17:36
*** yamamoto has quit IRC17:38
*** armax has joined #openstack-meeting17:42
*** deiter has quit IRC17:46
*** e0ne has joined #openstack-meeting17:48
*** e0ne has quit IRC17:49
*** ociuhandu has quit IRC17:56
*** armax has quit IRC17:57
*** mmethot_ has joined #openstack-meeting17:57
*** mmethot_ has quit IRC17:58
*** mmethot_ has joined #openstack-meeting17:59
*** armax has joined #openstack-meeting18:00
*** mmethot has quit IRC18:00
*** armax has quit IRC18:00
*** e0ne has joined #openstack-meeting18:01
*** priteau has quit IRC18:01
*** brault has quit IRC18:03
*** mmethot_ has quit IRC18:06
*** mmethot has joined #openstack-meeting18:08
*** mmethot has quit IRC18:11
*** ociuhandu has joined #openstack-meeting18:11
*** zhubx has quit IRC18:15
*** rbudden has quit IRC18:15
*** boxiang has joined #openstack-meeting18:15
*** ociuhandu has quit IRC18:16
*** mmethot has joined #openstack-meeting18:16
*** rbudden has joined #openstack-meeting18:25
*** ociuhandu has joined #openstack-meeting18:33
*** ociuhandu has quit IRC18:38
*** mattw4 has quit IRC18:44
*** enriquetaso has quit IRC18:45
*** thgcorrea has quit IRC19:03
*** mriedem has quit IRC19:15
*** mriedem has joined #openstack-meeting19:16
*** ykatabam has joined #openstack-meeting19:21
*** belmoreira has joined #openstack-meeting19:23
*** ociuhandu has joined #openstack-meeting19:24
*** armax has joined #openstack-meeting19:38
*** eharney has quit IRC19:39
*** ociuhandu has quit IRC19:40
*** jbadiapa has quit IRC19:44
*** artom has quit IRC19:47
*** armax has quit IRC19:47
*** mattw4 has joined #openstack-meeting19:50
*** ralonsoh has quit IRC19:56
*** jbadiapa has joined #openstack-meeting19:57
*** larainema has quit IRC20:06
*** enriquetaso has joined #openstack-meeting20:07
*** pcaruana has quit IRC20:10
*** jamesmcarthur_ has quit IRC20:12
*** belmoreira has quit IRC20:13
*** jamesmcarthur has joined #openstack-meeting20:17
*** jamesmcarthur has quit IRC20:17
*** jamesmcarthur has joined #openstack-meeting20:18
*** ayoung has quit IRC20:21
*** ayoung has joined #openstack-meeting20:22
*** enriquetaso has quit IRC20:25
*** eharney has joined #openstack-meeting20:43
*** ociuhandu has joined #openstack-meeting20:56
timburke#startmeeting swift21:01
openstackMeeting started Wed Sep 18 21:01:18 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
timburkewho's here for the swift meeting?21:01
rledisezhi o/21:02
timburkesounds like tdasilva and clayg are going to be a little late, but i think we could get started21:03
timburkeagenda's at
timburkequick reminder that we want to start collecting topics at
timburkei'm as guilty as anyone of needing to put things on there. i feel like i've been running around without a chance to stop, think, and organize. i'll make sure i get to that this week21:05
rlediseztimburke: I can help for Running Swift Cluster as you suggested. I'm just not sure what's expected (how long? slides needed?)21:05
timburkerledisez, i don't know either! i've never done this before ;-)21:06
rledisezlol, let's improvise then21:06
kota_needs help?21:06
timburkei'm also not sure how much interest there will be. yeah, improvisation will probably work best21:06
timburkekota_, maybe? i'd had this thought that i might encourage newcomers to express what they're curious about with regard to swift and then have something of a lecture prepared, but... idk21:07
kota_tdasilva: o/21:08
timburkei think that would still be valuable, but given the lack of newcomers expressing an interest... i'm not sure that it's the best use of time21:08
timburkewe'll see what happens21:09
timburkeanyway, on to updates!21:09
timburke#topic py321:09
*** openstack changes topic to "py3 (Meeting topic: swift)"21:09
timburkei didn't get around to making a probe test job running under py3, sorry21:09
timburke(part of it was being out of town the last couple days21:10
kota_needn't to say, sorry ;-)21:10
timburkebut we've got a new py3 bug!
openstackLaunchpad bug 1844368 in OpenStack Object Storage (swift) "fallocate_reserve cannot be specified as a percentage running under python3" [High,Confirmed]21:11
timburkelooks to be due to some changes in config parser -- sounds like tdasilva did a great job confirming the issue21:11
timburkei'd like to have it fixed for our train release (which is fast approaching!) but if needed, we can backport the fix21:12
kota_hah, ConfigParser21:12
*** sfernand has quit IRC21:12
timburke#topic lots of small files21:13
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:13
rledisezas alecuyer is not here i'll try to summarize what happened recently21:14
*** ykatabam has quit IRC21:14
rledisezrpc as http is merged in the feature branch21:14
*** raildo has quit IRC21:14
rledisezwe tried to deploy yesterday on production 2.22 + losf (with rpc http) + hashes.pkl support21:15
rledisezhashes.pkl to save some CPU21:15
rledisezwe had to rollback, it seems introducing hashes.pkl introduced some random hangs in REPLICATE21:15
rledisezalecuyer is digging it21:15
timburkegood to know21:16
rlediseznext step for performance would probably to cache the list of partitions because it's seems it's very CPU intensive to list the partition21:16
mattoliveraulol, you guys are cowboys.. just deploy to production.. nope doesn't work :P21:16
rledisezmattoliverau: i didn't say it all. just on one server at first. we go to prod by 1/10/100/100021:17
rlediseznot so crazy cowboys :D21:17
mattoliverauahh, yeah makes much more sense :)21:17
kota_that means, it would be compatible with grpc version??>21:17
rledisezkota_: what do you mean?21:18
timburkei think that part's internal to a particular object server, no?21:18
timburkefrom the proxy's perspective, the RPC mechanism shouldn't really matter, right?21:18
kota_change one server from grpc to http, right?21:18
rledisezyes, the protocol between object-server (python) and the RPC server (golang). it was gRPC but due to eventlet, it's now HTTP protocol21:18
*** brault has joined #openstack-meeting21:19
rledisezso, it's totally transparent for anything else than the losf diskfile21:19
timburke(and similarly between two different object servers)21:19
kota_yeah, and the index-sever stands for each node.21:19
rledisezkota_: exactly21:19
kota_make sense.21:19
timburkei know we here at swiftstack did some performance testing, and darrell talked with alecuyer a bit about what we'd found... unfortunately i didn't keep a close eye on that conversation, but i think we weren't seeing *huge* improvements...21:21
timburkerledisez, i think darrell was talking with you; do you remember what the outcome on that was? if there was any idea on what our bottlenecks or bad configuration might be?21:22
*** brault has quit IRC21:23
rledisezhum, I can't exactly remember. maybe darrell could start an etherpad with what you found and we'll check that and confirm or explain or answer21:24
timburkesounds good21:24
claygdid i miss anything exciting?21:24
timburkei also remember alecuyer mentioned he had some patches that needed proposing... do you think any of that might be because of the code delta between what's on the feature branch vs what you're actually running?21:24
timburkeclayg, don't worry, i moved the versioning stuff down ;-)21:24
rlediseztimburke: yes, we are (sadly) some patches ahead because we patch our prod first, but I think we are really close to the feature branch21:25
rledisezand the goal is to run the last stable + feature branch on our cluster21:25
timburkerledisez, that makes perfect sense -- take care of your herd ;-)21:26
timburkebut i really *do* want ot be better about getting patches landed on the feature branch -- if you're *running it in prod*, that kinda sounds like a +2 to me ;-)21:26
timburke#topic sharding21:28
*** openstack changes topic to "sharding (Meeting topic: swift)"21:28
timburkemattoliverau, i'm so sorry, i realy need to look at your patches!21:28
mattoliverauno stress, we have lot's going on :)21:28
mattoliverauI've pushed up
mattoliverauwhich I hope addresses the cleaning up cleave context bug21:29
timburkeremind me, do you have anyone running with sharded containers? or are you doing this just because sharding's kinda your baby?21:29
timburkei love that sense of ownership, but i also don't want you getting burnt out on it ;-)21:30
mattoliverauour swift deployments tools (with my Suse hat on) doesn't support sharding, in fact they a little behind.21:30
mattoliverauIt's something I want to fix. But suse doesn't make swift a priority other then giving me some time on it upstream21:31
timburkeare there other things that Suse would like to see in swift? bugs fixed, features added?21:31
mattoliverauSo one day. In essence. I just know the code really well and feel responsible for bugs ;)21:32
claygmattoliverau: that's super interesting!  I didn't realize the tons of headers bug was about not reaping old contexts?!21:32
timburkewhat can i do to get you something you can show your boss to say, "hey, swift's valuable for us"? :-)21:32
mattoliverauyeah, I wish I knew. Suse just "support" it as apart of OpenStack. They really go out and sell SES to customers with large storage issues.21:33
timburkemight also be outside the scope of this meeting, but i wanted to mention it ;)21:33
mattoliverauI'll been vocal about certain use cases as they come up internally. And always put a how cool Swift would be for that.. so I'm working on the inside :)21:34
timburkeπŸ‘ thanks for that21:35
mattoliverauIf I can push the internal deployment tools forward. Just waiting for the customer who wants something big that Ceph can't handle ;P21:35
timburkeanyway. i'll try to get those patches reviewed. thanks for all your hard work!21:36
timburke#topic versioning21:36
*** openstack changes topic to "versioning (Meeting topic: swift)"21:36
mattoliverauAnyway. Got some sharding patches up for bugs. Haven't worked on autosharding much. I should play with that some more. comments on the current implemenatino welcome.21:36
mattoliverauonto versioning!21:36
timburkeclayg, tdasilva, take it away ;-)21:37
claygso after a false start trying to expand versioned_writes to work with s3api aws object versioning feature...21:37
claygwe decided to expand versioned_writes to work with s3api aws object versioning feature!21:38
claygonly this time with a for-realzy new swift object versioning api that works a lot more like aws s3 object versioning21:38
claygtdasilva: is working on that - and I'm sure lots of docs and func tests will be coming to flush that out and describe how we think it should work so we can start to get some feedback21:39
mattoliverauso this is the WIP patch?21:39
*** patchbot has joined #openstack-meeting21:40
patchbotpatch 682382 - swift - WIP: New Object Versioning mode - 2 patch sets21:40
claygthere's a couple sticking points on the implementation side where there might be some lack of system/storage level features make for less than ideal strategies; so we're experimenting with some different things21:40
timburkebetter :-)21:40
tdasilvamattoliverau: correct21:40
*** panda has quit IRC21:41
claygso there's lot to talk about that... and looking down the road maybe some discussion about different things we might do with s3api while that work is ongoing21:41
*** mriedem is now known as mriedem_afk21:41
*** e0ne has quit IRC21:41
*** panda has joined #openstack-meeting21:42
claygprobably worth noting that symlink based versoinsing is still a good idea - but there's some other things in the legacy versioned writes mode(s) that were problematic and it seems better for clients/consumers to just offer a new shiny21:43
claygwe've been throwing around the anlogy of DLOs vs. SLOs - but with the idea that maybe if the alternative implementation is really significantly better (and easier for s3 consumers to adopt) we might eventually "sunset" legacy mode21:44
claygbut really we're mostly focused on getting an object versioning implementation in swift that is amazing and we can build on for the next decade'21:44
timburkefwiw, i'm starting to collect some of the design discussion currently happening internally at
mattoliverauoh nice21:45
timburkebecause it'll be so much better if mattoliverau and kota_ and rledisez can see what we're thinking and offer feedback on it :-)21:45
claygtimburke: thanks for getting up - we can definately help flesh that out as we go21:45
mattoliverauclayg: +1 re: amazing versioning is a good focus21:45
kota_oh, what, sorry, I'm looking another thing.21:46
mattoliverauI'll take a look at the patch today too to get an idea of where things are at.21:46
timburkekota_, no worries :-) we just always appreciate your insights21:47
kota_good to know for the versioning21:47
mattoliveraujust linking it so it's easy to find in the minutes later21:47
claygmattoliverau: we already got at least one new primative (static links,) out of the deal - I'm hoping we get at least one more before we're thorugh21:47
tdasilvamattoliverau: sorry for the lack of docs for the moment21:47
* kota_ is in U.S. timezone actually to join another meeting21:47
mattoliverauie. when I loose the link :P21:47
claygI'm sure we could sketch out some stuff on the etherpad that eventually ends up looking like some documentation21:48
mattoliverauno stress guys. y'all doing awesome :)21:48
kota_there are good items for improvement consideration in the etherpad21:49
claygtimburke: I think that's all we got this week - but I'll commit to helping work on that etherpad21:49
timburkesounds good21:49
timburkeoh, one more last minute topic!21:50
timburke#topic train release21:50
*** openstack changes topic to "train release (Meeting topic: swift)"21:50
claygCHOO CHOO!21:50
timburkein two weeks or so, i want to be tagging a 2.23.0 for train21:50
mattoliverauwe should call it, train departure :P21:50
claygship     it, ship   it, ship it, shipit, shipitshipitshipit CHOOO CHOOOO21:50
mattoliverautimburke: so maybe a new priority review section21:51
timburkeplease add items to the priority reviews page as you see fit -- i'll make sure i add a release section at the top (and in general clean it up)21:51
timburkemattoliverau, yeah, that :-)21:51
timburke#topic open discussion21:51
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:51
timburkeanything else we ought to talk about?21:52
timburkecan't wait!21:53
claygis there a who's coming list already?21:53
kota_<- whole week21:54
timburkestill need to get my travel sorted, though... and make a state of swift talk21:54
claygkota_: AWESOME!!!21:54
claygi'm just trying to learn how to visa21:54
rledisezfor the record, alex and I have our PTG tickets and plane tickets. we are now trying to get VISA (which is a bit complex for french people). we hope to get them in time21:54
kota_hehe, I don't need VISA for shanghai21:55
timburkeclayg, according to, it's the five of us: you, me, kota_, rledisez, and alecuyer21:55
claygmattoliverau: ??? 😒21:55
mattoliveraume never got the OK, but here others at SUSE are applying for visa's so assume it's not happening. I should go confirm with my manager (whose been away and then away at training)21:56
mattoliverauannoying because it's _very_ close to my timezone.21:56
claygahahha!  true!  maybe one of the easier plane rides for you for a change!21:57
mattoliverauso I would have thought I'd be cheaper to send too.21:57
timburkeif nothing else, it'll be nice to have more overlap with you mattoliverau :-)21:57
mattoliverauyeah,lets see what can get through the great firewall of china.. but I hope to be there virtually :)21:57
claygwe'll have to think about how to dial you in; if you can't make it you'll be missed - until the next one!21:57
claygyeah i'm *nervous* about the tech/equipment/network stuff 😬21:58
timburkei wonder where it'll be...21:58
timburkeclayg, yeah, me too.21:58
rledisezclayg: we got special recommendation from our SOC team…21:58
mattoliverauprobably denver :P21:58
timburkemattoliverau, sounds right :P21:58
timburkeall right, i think i'm gonna call it21:58
kota_denver :/21:59
clayg"soc" is that a french acronym?21:59
timburkethank you all for coming, and thank you for working on swift!21:59
rledisezsecurity operation center i think21:59
mattoliveraukota_: probably not. Just joking21:59
*** openstack changes topic to "OpenStack Meetings ||"21:59
openstackMeeting ended Wed Sep 18 21:59:27 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:59
openstackMinutes (text):
*** patchbot has left #openstack-meeting21:59
*** eharney has quit IRC22:04
*** jamesmcarthur has quit IRC22:06
*** jamesmcarthur has joined #openstack-meeting22:09
*** markvoelker has quit IRC22:24
*** jamesmcarthur has quit IRC22:33
*** ociuhandu has quit IRC22:40
*** munimeha1 has quit IRC22:40
*** rfolco has quit IRC22:43
*** jamesmcarthur has joined #openstack-meeting22:50
*** mriedem_afk has quit IRC22:53
*** jamesmcarthur has quit IRC23:09
*** whoami-rajat has quit IRC23:10
*** ykatabam has joined #openstack-meeting23:11
*** rcernin has joined #openstack-meeting23:16
*** mriedem has joined #openstack-meeting23:17
*** enriquetaso has joined #openstack-meeting23:17
*** jamesmcarthur has joined #openstack-meeting23:34
*** carloss has quit IRC23:34
*** dviroel has quit IRC23:39
*** efried_pto is now known as mriedem123:47
*** mriedem1 is now known as efried_pto23:47

Generated by 2.15.3 by Marius Gedminas - find it at!