Wednesday, 2019-11-20

*** slaweq has quit IRC00:01
*** ociuhandu has quit IRC00:02
*** ayoung has joined #openstack-meeting00:05
*** slaweq has joined #openstack-meeting00:11
*** apetrich has quit IRC00:15
*** slaweq has quit IRC00:18
*** armax has joined #openstack-meeting00:25
*** brinzhang has joined #openstack-meeting00:32
*** slaweq has joined #openstack-meeting00:42
*** yaawang has quit IRC00:44
*** brinzhang_ has joined #openstack-meeting00:45
*** slaweq has quit IRC00:46
*** brinzhang has quit IRC00:49
*** rfolco has quit IRC00:52
*** yaawang has joined #openstack-meeting00:57
*** slaweq has joined #openstack-meeting01:01
*** nanzha has joined #openstack-meeting01:05
*** slaweq has quit IRC01:05
*** ykatabam has joined #openstack-meeting01:07
*** Liang__ has joined #openstack-meeting01:08
*** ociuhandu has joined #openstack-meeting01:22
*** slaweq has joined #openstack-meeting01:25
*** slaweq has quit IRC01:30
*** ociuhandu has quit IRC01:34
*** lifeless has quit IRC01:34
*** mriedem has quit IRC01:44
*** lifeless has joined #openstack-meeting01:49
*** Liang__ is now known as LiangFang01:54
*** jamesmcarthur has joined #openstack-meeting02:06
*** lifeless has quit IRC02:12
*** macz has joined #openstack-meeting02:12
*** slaweq has joined #openstack-meeting02:13
*** igordc has quit IRC02:18
*** slaweq has quit IRC02:18
*** lifeless has joined #openstack-meeting02:24
*** macz has quit IRC02:24
*** slaweq has joined #openstack-meeting02:24
*** nanzha has quit IRC02:25
*** nanzha has joined #openstack-meeting02:27
*** slaweq has quit IRC02:30
*** ykatabam has quit IRC02:34
*** ayoung has quit IRC02:34
*** ociuhandu has joined #openstack-meeting02:35
*** slaweq has joined #openstack-meeting02:35
*** ociuhandu has quit IRC02:39
*** geguileo has joined #openstack-meeting02:44
*** slaweq has quit IRC02:48
*** gyee has quit IRC02:53
*** slaweq has joined #openstack-meeting03:00
*** ykatabam has joined #openstack-meeting03:00
*** slaweq has quit IRC03:04
*** slaweq has joined #openstack-meeting03:05
*** slaweq has quit IRC03:16
*** macz has joined #openstack-meeting03:18
*** nanzha has quit IRC03:22
*** macz has quit IRC03:22
*** nanzha has joined #openstack-meeting03:22
*** slaweq has joined #openstack-meeting03:26
*** ayoung has joined #openstack-meeting03:27
*** macz has joined #openstack-meeting03:28
*** slaweq has quit IRC03:31
*** macz has quit IRC03:33
*** slaweq has joined #openstack-meeting03:35
*** slaweq has quit IRC03:40
*** ayoung has quit IRC03:42
*** ricolin has joined #openstack-meeting03:43
*** ayoung has joined #openstack-meeting03:45
*** nanzha has quit IRC03:53
*** nanzha has joined #openstack-meeting03:53
*** slaweq has joined #openstack-meeting03:55
*** slaweq has quit IRC04:02
*** liuyulong has quit IRC04:05
*** slaweq has joined #openstack-meeting04:10
*** ayoung has quit IRC04:15
*** slaweq has quit IRC04:15
*** ayoung has joined #openstack-meeting04:15
*** armax has quit IRC04:18
*** slaweq has joined #openstack-meeting04:39
*** slaweq has quit IRC04:44
*** ayoung has quit IRC04:45
*** ayoung has joined #openstack-meeting04:46
*** slaweq has joined #openstack-meeting05:01
*** slaweq has quit IRC05:08
*** brinzhang has joined #openstack-meeting05:09
*** brinzhang has quit IRC05:10
*** brinzhang has joined #openstack-meeting05:11
*** slaweq has joined #openstack-meeting05:11
*** brinzhang_ has quit IRC05:12
*** slaweq has quit IRC05:20
*** pcaruana has joined #openstack-meeting05:25
*** Lucas_Gray has joined #openstack-meeting05:28
*** slaweq has joined #openstack-meeting05:29
*** ociuhandu has joined #openstack-meeting05:31
*** slaweq has quit IRC05:33
*** ociuhandu has quit IRC05:35
*** slaweq has joined #openstack-meeting05:42
*** Lucas_Gray has quit IRC05:45
*** slaweq has quit IRC05:47
*** links has joined #openstack-meeting05:48
*** brinzhang_ has joined #openstack-meeting05:52
*** zaneb has joined #openstack-meeting05:52
*** jraju__ has joined #openstack-meeting05:54
*** links has quit IRC05:54
*** jraju__ has quit IRC05:54
*** brinzhang has quit IRC05:55
*** brinzhang has joined #openstack-meeting06:00
*** brinzhang_ has quit IRC06:03
*** slaweq has joined #openstack-meeting06:10
*** slaweq has quit IRC06:15
*** slaweq has joined #openstack-meeting06:27
*** slaweq has quit IRC06:32
*** larainema has joined #openstack-meeting06:33
*** slaweq has joined #openstack-meeting06:39
*** slaweq has quit IRC06:44
*** slaweq has joined #openstack-meeting07:11
*** brinzhang has quit IRC07:15
*** slaweq has quit IRC07:15
*** brinzhang has joined #openstack-meeting07:16
*** priteau has quit IRC07:38
*** ayoung has quit IRC07:44
*** zaneb has quit IRC07:46
*** ayoung has joined #openstack-meeting07:47
*** slaweq has joined #openstack-meeting07:56
*** tesseract has joined #openstack-meeting07:58
*** e0ne has joined #openstack-meeting07:58
*** macz has joined #openstack-meeting07:59
*** macz has quit IRC08:04
*** lajoskatona has joined #openstack-meeting08:04
*** rsimai_away is now known as rsimai08:04
*** njohnston_ has joined #openstack-meeting08:06
*** njohnston has quit IRC08:07
*** e0ne has quit IRC08:08
*** ociuhandu has joined #openstack-meeting08:09
*** ociuhandu has quit IRC08:19
*** nanzha has quit IRC08:41
*** lajoskatona has left #openstack-meeting08:42
*** nanzha has joined #openstack-meeting08:48
*** e0ne has joined #openstack-meeting08:50
*** ralonsoh has joined #openstack-meeting08:51
*** rpittau|afk is now known as rpittau08:53
*** nanzha has quit IRC08:54
*** ociuhandu has joined #openstack-meeting08:55
*** nanzha has joined #openstack-meeting08:58
*** ociuhandu has quit IRC08:59
*** ociuhandu has joined #openstack-meeting09:00
*** apetrich has joined #openstack-meeting09:03
*** ociuhandu has quit IRC09:03
*** jawad_axd has joined #openstack-meeting09:03
*** ociuhandu has joined #openstack-meeting09:04
*** rfolco has joined #openstack-meeting09:05
*** jamesmcarthur has quit IRC09:07
*** rfolco has quit IRC09:09
*** ociuhandu has quit IRC09:11
*** ociuhandu has joined #openstack-meeting09:11
*** ociuhandu has quit IRC09:13
*** ociuhandu has joined #openstack-meeting09:14
*** ociuhandu has quit IRC09:15
*** jamesmcarthur has joined #openstack-meeting09:15
*** ociuhandu has joined #openstack-meeting09:16
*** ociuhandu has quit IRC09:17
*** ociuhandu has joined #openstack-meeting09:18
*** ykatabam has quit IRC09:18
*** dtrainor_ has joined #openstack-meeting09:19
*** ociuhandu has quit IRC09:19
*** ociuhandu has joined #openstack-meeting09:20
*** dtrainor has quit IRC09:20
*** ykatabam has joined #openstack-meeting09:20
*** Lucas_Gray has joined #openstack-meeting09:22
*** ociuhandu has quit IRC09:26
*** ociuhandu has joined #openstack-meeting09:27
*** ociuhandu has quit IRC09:29
*** ociuhandu has joined #openstack-meeting09:29
*** ociuhandu has quit IRC09:32
*** ociuhandu has joined #openstack-meeting09:32
*** ociuhandu has quit IRC09:34
*** ociuhandu has joined #openstack-meeting09:35
*** ociuhandu has quit IRC09:37
*** ociuhandu has joined #openstack-meeting09:37
*** ykatabam has quit IRC09:38
*** ociuhandu has quit IRC09:39
*** ociuhandu has joined #openstack-meeting09:40
*** ociuhandu has quit IRC09:43
*** ociuhandu has joined #openstack-meeting09:43
*** ociuhandu has quit IRC09:45
*** ociuhandu has joined #openstack-meeting09:46
*** rcernin has quit IRC09:46
*** Wryhder has joined #openstack-meeting09:46
*** ociuhandu has quit IRC09:48
*** Lucas_Gray has quit IRC09:48
*** ociuhandu has joined #openstack-meeting09:49
*** Wryhder is now known as Lucas_Gray09:49
*** ociuhandu has quit IRC09:50
*** ociuhandu has joined #openstack-meeting09:51
*** ociuhandu has quit IRC09:52
*** priteau has joined #openstack-meeting09:52
*** ociuhandu has joined #openstack-meeting09:53
*** ociuhandu has quit IRC09:56
*** ociuhandu has joined #openstack-meeting09:57
*** ociuhandu has quit IRC09:58
*** ociuhandu has joined #openstack-meeting09:58
*** nanzha has quit IRC10:06
*** priteau has quit IRC10:06
*** nanzha has joined #openstack-meeting10:08
*** ykatabam has joined #openstack-meeting10:12
*** ykatabam has quit IRC10:28
*** LiangFang has quit IRC10:32
*** ricolin has quit IRC10:32
*** ayoung has quit IRC10:37
*** ayoung has joined #openstack-meeting10:38
*** brinzhang_ has joined #openstack-meeting10:38
*** brinzhang has quit IRC10:42
*** ykatabam has joined #openstack-meeting10:52
*** ayoung has quit IRC10:52
*** ayoung has joined #openstack-meeting10:53
*** ykatabam has quit IRC10:57
*** brinzhang has joined #openstack-meeting11:01
*** e0ne has quit IRC11:02
*** e0ne has joined #openstack-meeting11:02
*** brinzhang_ has quit IRC11:05
*** e0ne has quit IRC11:07
*** PrinzElvis has quit IRC11:08
*** macz has joined #openstack-meeting11:12
*** macz has quit IRC11:16
*** ociuhandu has quit IRC11:21
*** lpetrut has joined #openstack-meeting11:26
*** brinzhang_ has joined #openstack-meeting11:45
*** Lucas_Gray has quit IRC11:47
*** brinzhang has quit IRC11:49
*** ociuhandu has joined #openstack-meeting11:51
*** raildo has joined #openstack-meeting11:53
*** enriquetaso has joined #openstack-meeting12:01
*** PrinzElvis has joined #openstack-meeting12:15
*** brinzhang_ has quit IRC12:16
*** larainema has quit IRC12:23
*** pcaruana has quit IRC12:24
*** pcaruana has joined #openstack-meeting12:50
*** ociuhandu has quit IRC12:58
*** Lucas_Gray has joined #openstack-meeting13:01
*** priteau has joined #openstack-meeting13:05
*** ricolin has joined #openstack-meeting13:07
*** Lucas_Gray has quit IRC13:11
*** Lucas_Gray has joined #openstack-meeting13:11
*** mriedem has joined #openstack-meeting13:34
*** macz has joined #openstack-meeting13:35
*** macz has quit IRC13:39
*** maciejjozefczyk has quit IRC13:39
*** eharney has quit IRC13:43
*** ociuhandu has joined #openstack-meeting13:44
*** ociuhandu has quit IRC13:48
*** liuyulong has joined #openstack-meeting13:57
*** liuyulong_ has joined #openstack-meeting13:59
liuyulong#startmeeting neutron_l313:59
openstackMeeting started Wed Nov 20 13:59:59 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:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
liuyulong#chair liuyulong_14:00
openstackCurrent chairs: liuyulong liuyulong_14:00
liuyulong#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:01
liuyulongLet's recall the announcements yesterday14:02
liuyulongThen no more from me.14:02
liuyulong#topic Bugs14:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:05
liuyulongNo bug deputy email received this week, so let's directly search the bug list.14:06
liuyulongFirst one14:09
openstackLaunchpad bug 1852777 in neutron "Neutron allows to create two subnets with same CIDR in a network through heat" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:09
ralonsohhi yes14:09
ralonsohI'm still testing this14:09
liuyulongThe distributed lock should be introduced for this, IMO14:09
ralonsohno, is not working14:10
liuyulongA local file or memory lock does not work in multiple physical hosts.14:10
ralonsoheven with the threading lock I have both subnets created14:10
ralonsohdistributed lock?14:10
ralonsohsorry can you point me to this?14:10
liuyulongI mean we should use tooz.14:11
*** priteau has quit IRC14:11
ralonsohah ok14:11
slaweqhi, sorry for being late14:11
ralonsohbut this request will be done to a single server only14:11
ralonsohor am I wrong?14:11
ralonsohso a distributed lock won't be necessary here14:11
*** e0ne has joined #openstack-meeting14:12
liuyulongcreate subnet with same CIDR should be two different API calls.14:12
slaweqralonsoh: I think that each create-subnet request can go to different host with neutron-api process14:12
liuyulongSo it will spread to different hosts.14:12
*** priteau has joined #openstack-meeting14:12
*** whoami-rajat has joined #openstack-meeting14:12
ralonsohbtw, this is going to add an extra delay in subnet creation14:13
ralonsohjust a heads-up to everybody complaining about the time consumption in neutron API14:13
liuyulongBTW, the UNIQUE CONSTRAINT is also worthy to add.14:13
*** priteau has quit IRC14:13
ralonsohbecause two different cidrs can overlap being different14:14
ralonsohjust different masks14:14
ralonsoh10.0.0.0/24 and
liuyulongYes, the distributed lock will make the API workers from different linearly.14:14
slaweqexactly, constraint on db level will not help here14:14
ralonsoh(I tried to do something with IPSets)14:14
ralonsohby adding a new table14:14
ralonsohand adding a register per network14:14
ralonsohcontaining the IPSets of the CIDRs14:15
liuyulongralonsoh, slaweq, but at least it can cover one case.14:15
ralonsohliuyulong, hmmm I don;t think this is enough14:15
liuyulong#chair slaweq14:16
openstackCurrent chairs: liuyulong liuyulong_ slaweq14:16
liuyulong^ just in case14:16
liuyulongralonsoh, yes, I'm not saying it will cover all cases.14:17
slawequnique constraint can at least fix problem when 2 workers will try to create exactly same subnets14:17
slaweqand as it's probably easy to add, it makes sense for me14:17
slaweqbut this will not solve the problem for sure14:17
ralonsohI'll add a partial-bug patch for this14:17
*** whoami-rajat has quit IRC14:18
slaweqliuyulong++ for the idea about unique constraint too14:18
liuyulongI have another bad idea based on such  unique constraint, : )14:18
liuyulongStore each IP of the CIDR and add  unique constraint between IP and network_id, hahaha14:19
ralonsohnot all the IPs14:19
ralonsohbut the IPSet14:19
ralonsohas I proposed before14:19
ralonsohone IPset per network, in one single register14:20
ralonsohthis will force, any time we want to update the network subnets, to update this single register14:20
*** Lucas_Gray has quit IRC14:21
ralonsohthis will use the DB to enforce the logic14:21
liuyulongDatabase has such IPset data type?14:21
ralonsohno, json.dumps(netaddr.IPSet())14:21
ralonsohand then json.loads()14:22
slaweqralonsoh: how one IPSet will work for network is I will have e.g. 2 subnets and ?14:22
ralonsohone sec14:22
liuyulongralonsoh, a json list can be used for unique constraint?14:22
ralonsoh>>> n10=netaddr.IPNetwork('')14:22
ralonsoh>>> n11=netaddr.IPNetwork('')14:22
ralonsoh>>> ips=netaddr.IPSet([n10,n11])14:22
ralonsoh>>> ips14:22
ralonsohIPSet(['', ''])14:22
slaweqand also You will still need to have logic in python to validate this IPset each time e.g. new subnet is added14:23
ralonsohslaweq, yes14:23
slaweqso it still not be atomic14:23
ralonsohbut the point is you can have only one writer context to one DB register14:23
ralonsohas I said, this is not easy and I'm trying to find the way14:23
slaweqahh, ok14:24
slaweqso this would be locked by one api worker14:24
ralonsohit should14:24
slaweqand other would need to wait to read from it, correct?14:24
ralonsoh(of course, this will break the DB normal forms)14:24
ralonsohexactly, it should wait14:24
slaweqthan this may work14:25
liuyulong+1, make sense14:25
slaweqbut one more thing14:26
liuyulongIt looks like a distributed lock implemented by neutron itself for each network during create subnet.14:26
slaweqdo You want to store in db list(ips)? or what exactly?14:26
ralonsohstore str(IPSet)14:27
ralonsohthis is way shorter than the IP list14:27
slaweqTypeError: Object of type IPSet is not JSON serializable14:27
slaweqI have such error when I'm trying to do this14:27
ralonsohI know, we need to create a serializer14:27
slaweqbut ok, we can even store there list of cidrs, and than create IPSet object in fligh during the validation14:28
ralonsohthis could be done just with the ranges list14:28
ralonsohe.g.: ['', '']14:28
liuyulongThis is my understanding: one API try to add 'ip_set' to the 'new table' and it should have uniq constraint for network; while another worker try to write this table will meet uniq constraint error.14:28
ralonsohslaweq, but we should not store the CIDR list14:29
ralonsohslaweq, we already have this information from the DB14:29
ralonsohthis is bad DB design14:29
ralonsohliuyulong, yes, that's the point14:29
liuyulongSo after the first one creation done, and another will start another retry to write this table, and go to the IPAM check again.14:29
ralonsohto use the DB as a lock14:29
slaweqralonsoh: sure, I was thinking about list as You mentioned: ['', '']14:30
ralonsohslaweq, yes another example14:30
ralonsoh>>> n11=netaddr.IPNetwork('')14:31
ralonsoh>>> ips=netaddr.IPSet([n10,n11])14:31
ralonsoh>>> ips14:31
ralonsohone network range for two cidrs14:31
slaweqyes, that makes sense14:32
*** munimeha1 has joined #openstack-meeting14:33
*** mmethot has quit IRC14:34
liuyulongIf neutron is willing to introduce tooz, the subnet creation can also apply lock on the network only, basically logical is same.14:35
*** mmethot has joined #openstack-meeting14:35
liuyulongOK, we have good ideas here, thanks.14:35
liuyulongNext one14:36
openstackLaunchpad bug 1852760 in neutron "When running 'openstack floating ip list' on undercloud, client cannot handle NotFoundException" [Low,Invalid] - Assigned to Nate Johnston (nate-johnston)14:36
njohnston_yes, I moved that to storyboard as it's a client issue!/story/200686314:36
liuyulongIt is a client error. We need user friendly outputs for it. Right?14:37
njohnston_correct.  neutron api is returning the correct thing.14:37
liuyulongAnd the Neutron API response should also add the resource type in the message, IMO.14:38
liuyulongNow it is just "The resource could not be found"14:38
*** maciejjozefczyk has joined #openstack-meeting14:38
njohnston_that would be nice, but not absolutely required14:38
*** PrinzElvis has quit IRC14:38
liuyulongYes, user should remember the resource type they are just trying to find.14:39
*** eharney has joined #openstack-meeting14:39
openstackLaunchpad bug 1852680 in neutron "floatingip can not access after associate to instance" [Undecided,Incomplete]14:39
liuyulongI highly doubt the VM was not set the security group rule correctly.14:40
liuyulongSince there is no more information attached to this now, let's remain it as Incomplete.14:41
slaweqI agree14:42
openstackLaunchpad bug 1852504 in neutron "DHCP reserved ports that were unscheduled are advertised as DNS servers" [Medium,In progress] - Assigned to Mithil Arun (arun-mithil)14:42
liuyulongAlright, another DHCP bug, this was seen in our cloud.14:43
liuyulongMainly are because of the auto_schedule mechanism of DHCP.14:44
slaweqthe issue here is that we are not removing reserved_dhcp_ports but left them unbound, right?14:45
*** jawad_axd has quit IRC14:45
*** jawad_axd has joined #openstack-meeting14:46
liuyulongWe have no fix of this, but as a workaround, I just suggest to disable the auto_schedule of the DHCP, and increase the dhcp_agents_per_network to 3 or more. In such way, it can cover most failure case.14:46
liuyulongslaweq, yes14:46
slaweqmaybe we should remove such ports?14:46
liuyulongslaweq, but you can see that the bug description has more that 2 ACTIVE  DHCP ports...14:47
*** maciejjozefczyk has quit IRC14:47
slaweqliuyulong: yes, but how it's related?14:48
slaweqactive ports are ok, right?14:48
liuyulongI have no idea because we have used the distributed DHCP based on the openflow and ovs local controller.14:49
*** jawad_ax_ has joined #openstack-meeting14:49
liuyulongWhich I proposed during the PTG, : )14:49
*** jamesmcarthur has quit IRC14:49
slaweqyes, I remember that one :)14:49
liuyulongAnyway, it has a fix there:
liuyulongWe can test that.14:50
*** jawad_axd has quit IRC14:50
slaweqyes, let's review this14:51
*** jawad_axd has joined #openstack-meeting14:51
openstackLaunchpad bug 1852468 in neutron "network router:external value is non-boolean (Internal) which causes server create failure" [Undecided,Invalid]14:51
liuyulongIt is invalid now.14:52
liuyulongAnd next:14:52
openstackLaunchpad bug 1852447 in neutron "FWaaS: adding a router port to fwg and removing it leaves the fwg active" [Medium,Triaged]14:52
liuyulongWho is the new daddy of this project now? haha14:52
*** maciejjozefczyk has joined #openstack-meeting14:53
slaweqthere is no new daddy for fwaas (yet)14:53
*** jawad_ax_ has quit IRC14:53
liuyulongAlright, time is running out. Let's move on.14:54
liuyulong#topic On demand agenda14:54
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:54
liuyulongI have one update of IPv6.14:55
*** jawad_axd has quit IRC14:55
liuyulongWe finally move back to dhcpv6-stateful for both address and other option with prefix len of 64.14:55
liuyulongEverything works fine for now, the instance image does not change for the IPv6 and the NetworkManager also works fine.14:56
*** jamesmcarthur has joined #openstack-meeting14:57
* haleyb completely forgot about the time change for this meeting, sorry :( updated...14:59
liuyulongWindows have a very magic behavior, when you add a IPv6 address for a port (once with IPv4 only), the NIC of the windows will automatically set the IPv6 address to it. But for Linux, user should to ifdow/up the network interface to dhcp the IPv6 address.14:59
liuyulongOK, let's end here.14:59
*** openstack changes topic to "OpenStack Meetings ||"14:59
openstackMeeting ended Wed Nov 20 14:59:29 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:59
openstackMinutes (text):
*** liuyulong_ has quit IRC15:02
*** johnthetubaguy has joined #openstack-meeting15:05
*** maciejjozefczyk has quit IRC15:06
*** davee_ has joined #openstack-meeting15:07
*** johnthetubaguy has quit IRC15:07
*** baojg has joined #openstack-meeting15:08
*** johnthetubaguy has joined #openstack-meeting15:09
*** ociuhandu has joined #openstack-meeting15:13
*** ociuhandu has quit IRC15:19
*** tosky has joined #openstack-meeting15:43
*** ociuhandu has joined #openstack-meeting15:56
*** whoami-rajat has joined #openstack-meeting15:56
*** rosmaita has joined #openstack-meeting15:57
rosmaita#startmeeting cinder16:00
openstackMeeting started Wed Nov 20 16:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is rosmaita. 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
_pewp_jungleboyj ( ^_^)/16:00
jungleboyjLets get this party started!16:00
_pewp_jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )16:00
bcmhi o/ thought I might evesdrop on this meeting.16:00
jungleboyjbcm:  Welcome.16:01
jungleboyjAre you using Cinder or looking to contribute or ????16:01
rosmaitawe have no problem with eavesdroppers16:01
*** ociuhandu has quit IRC16:01
toskyno ping?16:01
rosmaitalooks like a decent turnout, i will get started16:02
jungleboyjtosky:  He did it in the Cinder channel.16:02
rosmaitatosky: i did a ping in cinder channel16:02
jungleboyjNew PTL changing something esle too?16:02
rosmaitatosky: btw thank you for your work on the gate yesterday16:02
bcmthanks jungleboyj rosmaita tosky, i actually have a review i'd like to get some opinions on if time permits16:02
jungleboyjtosky:  ++16:02
rosmaitashould be time, i saw you post it in open dicsussion16:02
bcmcool thanks :)16:03
rosmaita#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:03
rosmaita#topic announcements -- virtual ptg16:03
*** openstack changes topic to "announcements -- virtual ptg (Meeting topic: cinder)"16:03
rosmaitaok, about the days/times16:04
rosmaitaCinder Ussuri Virtual PTG Poll had 13 responses16:04
rosmaitaWednesday 1500-1700 UTC is OK for everyone except one person, so one session will happen on Wednesday16:04
rosmaitaThe Thursday and Friday time slots: more than half can't attend, so both those days are out.16:04
rosmaitaTuesday 1400-1600: 30% can't attend or not first choice16:05
rosmaitaTuesday 1500-1700: 23% can't attend or not first choice16:05
rosmaitaMonday 1400-1600: 30% can't attend or not first choice16:05
rosmaitaMonday 1500-1700: only time slot where no one says they cannot attend16:05
rosmaita92% either "love it" or "works for me"16:05
*** armax has joined #openstack-meeting16:05
rosmaitaSo, we will use Monday 1500-1700 to kick off the virtual PTG16:06
rosmaitaand finish on Wednesday16:06
rosmaitai should be completely clear16:06
rosmaitaSo, the Virtual PTG will be:16:06
rosmaitaMonday 25 November 1500-1700 UTC16:06
rosmaitaWednesday 27 November 1500-1700 UTC16:06
rosmaitaand the planning etherpad is:16:06
rosmaitaWe will do the usual thing, start at the beginning, give each topic what it takes, and finish when we are done16:07
rosmaitai put some stuff on the planning pad already, mostly follow ups from the shanghai PTG16:07
jungleboyjWhat is the meeting medium?16:07
rosmaitayes, bluejeans16:08
jungleboyjAh, already in the etherpad.16:08
*** whoami-rajat_ has joined #openstack-meeting16:08
rosmaitalink is on the etherpad unless i pasted it somewhere else by mistake16:08
rosmaitaok, cool16:08
rosmaitaif you haven't used bluejeans before, ping me in irc and i can do a quick meeting with you to make sure you can connect OK16:08
* jungleboyj puts it on the calendar.16:08
rosmaitai will also be online early on monday (at least 20 min early) if you want to try then16:09
rosmaitai will put all this info into an email later today16:09
rosmaitaas far as topics go: feel free to propose anything16:09
rosmaitaalso, if there's something you want to follow up from the Shanghai ptg that's not there, feel free to add it16:10
*** nanzha has quit IRC16:10
rosmaitaand, we will record these 2 sessions in case anyone can't make it16:10
rosmaitathough like i said earlier, there was good consensus on these times16:10
rosmaitaany questions?16:11
*** do3meli has joined #openstack-meeting16:11
jungleboyjThanks for setting it up.16:11
whoami-rajat_rosmaita: I think the extending default volume type for tenants topic isn't there, should I add it?16:11
rosmaitanp, i hope it goes smoothly!16:11
rosmaitawhoami-rajat_: sure16:12
rosmaitawould be good to get a quick discussion of that before gorka writes the spec16:12
rosmaitaok, we can discuss more in open discussion if anything else occurs to anyone16:13
whoami-rajat_rosmaita: oh, I thought I volunteered for that :/16:13
rosmaitawhoami-rajat_: maybe you did, i may be thinking of something else16:13
whoami-rajat_rosmaita: oh ok16:14
rosmaitaand even if gorka volunteered to do it, i am sure he will not mind the help16:14
whoami-rajat_rosmaita: yep, surely, he proposed the topic and have better knowledge of it16:15
whoami-rajat_I could share the workload16:15
rosmaitathat will be great16:16
rosmaita#topic announcements -- spec repo maintenance16:16
*** openstack changes topic to "announcements -- spec repo maintenance (Meeting topic: cinder)"16:16
rosmaitaok, abhishek pointed out that there's no 'ussuri' directory yet16:16
*** gyee has joined #openstack-meeting16:16
rosmaitai will rectify that this afternoone16:16
jungleboyjrosmaita:  __16:16
rosmaitai was wondering what __ was !16:17
rosmaita#topic announcements -- meeting time change16:17
*** openstack changes topic to "announcements -- meeting time change (Meeting topic: cinder)"16:17
rosmaitaok, the poll doesn't close until 23:59 today, but i don't think anything is going to happen to change the current results16:17
rosmaitai have no idea why i didn't make the deadline yesterday16:18
rosmaitabut i guess i'm stuck with that16:18
davee_I demand a recount he he he16:19
rosmaitaso to be scrupulously fair, i will send out an email after the poll closes16:19
rosmaitaso, please look for the email so you are ready for the next meeting16:19
rosmaitawhich will *not* be next week16:19
jungleboyjI vote we throw the poll out due to mismanagement.16:19
rosmaitawe are having the virtual PTG at that time16:19
rosmaitaso the first meeting at possibly a new time will be 4 December16:20
rosmaitadepending on what the time is, it may also entail a change of location16:20
rosmaitaas there are conflicts in this channel16:20
rosmaitabut, #openstack-cinder is set up with the meetbot16:21
toskythere are 4 general meeting rooms, no one is available?16:21
rosmaitaand a lot of projects are having their weekly meetings in their own channel these days16:21
rosmaitatosky: i stopped looking once i found out we have the meetbot in #openstack-cinder16:22
toskybut what is the time exactly? The virtual PTG uses 4 slots16:22
davee_I accidentally made a #openstack-meeting416:22
rosmaitai guess i should ask, is there any reason *not* to have the weekly meeting in #openstack-cinder16:22
rosmaitamy thought was that if we have to move it, might as well just move it to our own channel16:23
davee_easier not to be interrupted by people asking for support in the middle of the meeting and muddying up the meeting notes16:23
rosmaitatosky: the virtual ptg will be in bluejeans16:23
rosmaitadavee_: i suppose that's true16:24
rosmaitai know that #openstack-meeting-alt is not available16:24
*** ricolin has quit IRC16:24
toskyrosmaita: yes, but what is the time? You only said that we are going to have the virtual PTG at that time, but the virtual PTG is spread over 4 hours :)16:24
toskyunless I missed something from the logs16:24
rosmaitatosky: i am being cagy about the meeting time because the poll is still open16:25
toskyoh, I see16:25
davee_There's a new sheriff in town16:25
rosmaitajungleboyj: what do you think about having the meeting in #openstack-cinder ?16:25
rosmaitathe weekly meeting, i mean16:25
tosky(I just need to mention that the are also #openstack-meeting-3 and #openstack-meeting-4 , just in case)16:26
jungleboyjdavee_:  Has a decent point about people interrupting and muddying things up.16:26
jungleboyjI don't have a strong preference though.  We can try it.16:26
rosmaitaok, then i will follow up on tosky's suggestion16:26
jungleboyjOslo has been just using their channel and that seems to work fine.16:27
rosmaitatosky: who reserves the rooms ? infra team?16:27
toskybut of course it can be on the channel as well16:27
rosmaitayeah, oslo, airship, a whole bunch of other teams16:27
toskyI think the procedure is the same regardless of the chosen room: a patch to the repository which regenerates eavesdrop.openstack.org16:27
whoami-rajatAdditionally, there will be patch proposal messages between the meeting notes16:28
rosmaitai was thinking of using #openstack-cinder because no one can reserve it away from us16:28
bnemecThe downside IMHO is that it makes pinging people from other projects harder because they're not necessarily in your channel.16:28
bnemecWe don't tend to have a big problem with interruptions, but then the oslo channel is pretty dead in general so YMMV. :-)16:28
toskyso opendev/irc-meetings, this file:
rosmaitatosky: ty16:29
rosmaitaok, the key point is that everyone needs to watch for an email about the new time and location16:29
* jungleboyj waits with baited breath16:29
*** jawad_axd has joined #openstack-meeting16:29
*** do3meli has left #openstack-meeting16:30
whoami-rajatrosmaita, ++16:30
rosmaitaok, i guess that's it for announcements16:31
rosmaita#topic python 2 testing situation16:32
*** openstack changes topic to "python 2 testing situation (Meeting topic: cinder)"16:32
rosmaitatosky can answer questions, but nova broke the gates yesterday16:32
rosmaitait could not be installed under py216:32
rosmaitabecause of
rosmaitaso this patch is a partial reversion:
*** ociuhandu has joined #openstack-meeting16:33
rosmaitabut the key thing is, we need to remove our py2 jobs, i think16:33
rosmaitathis is what i propose:16:33
rosmaita- for all components, remove the Py 2 support from the classifiers in setup.cfg16:34
toskythe problem in that case that not only they removed the py2 testing, but also prevented others from installing nova with py216:34
rosmaita- remove py2 tests from tox.ini16:34
rosmaita- remove the explicit py2 jobs from .zuul.yaml16:34
*** jawad_axd has quit IRC16:34
rosmaitawhat tosky said16:34
rosmaitaNova had "python-requires = >=3.6" in setup.cfg, but that's what was breaking everything, so we should wait until January to make that change16:34
toskyalso, they removed the py2-specific items from *requirements.txt16:34
toskyso as long as requirements.txt is untouched and there are no strange conditions like that forced python version in the setup, it should be fine16:35
toskyimplementing the steps rosmaita listed above should be fine16:36
rosmaitaok, cool16:36
whoami-rajat this might allow the requirements change?16:37
eharneyso we can probably start killing off python-six during U, too16:37
rosmaitahow about i put up the patch for cinder this afternoon (i am on New York time), tosky can review it tomorrow, and if it looks fine, i'll pathch the other components16:37
toskyjust one thing about explicit py2 jobs: the devstack default is going to switch to py3 (if the patch passes, I think it was merged), so that should help as well (we may want to remove the explicit py3 jobs and switch the py2 jobs to explicitly use py3)16:37
rosmaitaeharney: yeah, smcginnis and e0ne are fighting over who gets to remove six16:38
toskywhoami-rajat: that's the "py3 by default on devstack", correct16:38
*** ociuhandu has quit IRC16:38
jungleboyjHe he.16:38
*** ociuhandu has joined #openstack-meeting16:38
e0nerosmaita: :)16:38
toskywhoami-rajat: but I would play it safe and not break the py2 jobs for others (someone may have set it explicitly)16:38
eharneyi'm sure there will be plenty of patches for everyone to do some of it :)16:38
toskynot now, at least; there is a deadline where everyone is supposed to switch (with one exception, swift)16:39
rosmaitait's on the agenda for the virtual PTG, so maybe we can divide up the work16:39
whoami-rajattosky, ++, making safe changes is better than breaking gate16:39
toskyI would advise to not rip out six until the official deadline for killing py2, but that should be in a month or so16:39
rosmaita#action rosmaita review this discussion and put up a patch to remove py2 testing from cinder in an excellent way16:39
toskythe patches could be prepared anyway16:40
toskybut up to you, and let's see the general status16:40
rosmaitaOk, that's all i had on that topic16:40
rosmaita#topic open discussion16:40
*** openstack changes topic to "open discussion (Meeting topic: cinder)"16:40
rosmaitaok, we need reviews on
rosmaitait's a patch making volume type non nullable in the db16:41
whoami-rajatrosmaita, thanks for putting up the RP+116:41
rosmaitanp, i think we should get it in early16:41
rosmaitabcm: you had something for us?16:41
jungleboyjThat looks like a decent idea.  :-)16:41
whoami-rajatfor volumes, snapshots and encryption table (where volume_type_id) is used16:42
bcmhey - so I was waning to get some feedback on
rosmaitawow, that's been around for a while16:42
bcmI might be asking in the wrong place, I understand its nova code, but my question is basically what is/should be the best practice/ best way to handle stale connection info, and does cinder have an opinion on that?16:43
bcmmy understanding from the feedback on the review is that this code does the thing (CI issues aside) but its doing it "the old way"16:44
bcm so I'm weighing up if its worth going to the CI issues and trying to merge this or look into an alternate path.16:47
*** ayoung has quit IRC16:48
rosmaitalooks like everyone is speechless16:51
rosmaitai think we'll have to look at this offline and get back to you on the review16:51
*** ayoung has joined #openstack-meeting16:51
rosmaitaanything else for open discussion?16:52
bcmok no problem, I might bring this up on the ML/ nova/nova meeting. Thanks16:53
rosmaitabcm: sounds good16:53
rosmaitaok, don't forget virtual PTG monday and wednesday next week, details on
*** macz has joined #openstack-meeting16:54
rosmaitawatch the ML for an announcement about the next cinder meeting time/location, which will be on 4 December16:55
rosmaitathat's all i've got, anything else?16:55
rosmaitaok, thanks everyone, you can have a few minutes back today16:57
*** openstack changes topic to "OpenStack Meetings ||"16:57
openstackMeeting ended Wed Nov 20 16:57:12 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:57
openstackMinutes (text):
*** tosky has left #openstack-meeting16:58
*** anastzhyr has joined #openstack-meeting16:58
*** rpittau is now known as rpittau|afk17:18
*** takamatsu has joined #openstack-meeting17:24
*** jawad_axd has joined #openstack-meeting17:26
*** jawad_axd has quit IRC17:31
*** diablo_rojo has joined #openstack-meeting17:35
*** diablo_rojo has quit IRC17:40
*** jawad_axd has joined #openstack-meeting17:47
*** ayoung has quit IRC17:47
*** ayoung has joined #openstack-meeting17:50
*** jawad_axd has quit IRC17:52
*** whoami-rajat has quit IRC17:53
*** whoami-rajat_ is now known as whoami-rajat17:53
*** igordc has joined #openstack-meeting18:00
*** e0ne has quit IRC18:14
*** tesseract has quit IRC18:18
*** mattw4 has joined #openstack-meeting18:19
*** diablo_rojo has joined #openstack-meeting18:23
*** ralonsoh has quit IRC18:29
*** enriquetaso has quit IRC18:37
*** enriquetaso has joined #openstack-meeting18:37
*** diablo_rojo has quit IRC18:48
*** ociuhandu has quit IRC18:57
*** ociuhandu has joined #openstack-meeting18:59
*** dviroel has joined #openstack-meeting18:59
*** ociuhandu has quit IRC19:03
*** jamesmcarthur has quit IRC19:14
*** jamesmcarthur has joined #openstack-meeting19:27
*** munimeha1 has quit IRC19:29
*** lpetrut has quit IRC19:32
*** lpetrut has joined #openstack-meeting19:32
*** ociuhandu has joined #openstack-meeting19:35
*** e0ne has joined #openstack-meeting19:36
*** dtrainor has joined #openstack-meeting19:43
*** dtrainor_ has quit IRC19:44
*** e0ne has quit IRC19:44
*** ociuhandu has quit IRC19:46
*** ociuhandu has joined #openstack-meeting19:47
*** ociuhandu has quit IRC19:53
*** ociuhandu has joined #openstack-meeting19:57
*** e0ne has joined #openstack-meeting19:58
*** e0ne has quit IRC19:58
*** ociuhandu has quit IRC20:05
*** whoami-rajat has quit IRC20:08
*** eharney has quit IRC20:08
*** e0ne has joined #openstack-meeting20:11
*** e0ne has quit IRC20:14
*** jamesmcarthur has quit IRC20:20
*** jamesmcarthur has joined #openstack-meeting20:23
*** jamesmcarthur has quit IRC20:24
*** jamesmcarthur has joined #openstack-meeting20:26
*** e0ne has joined #openstack-meeting20:30
*** ociuhandu has joined #openstack-meeting20:36
*** ociuhandu has quit IRC20:51
*** ociuhandu has joined #openstack-meeting20:53
timburke#startmeeting swift21:00
openstackMeeting started Wed Nov 20 21:00:17 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: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
*** alecuyer has joined #openstack-meeting21:00
*** patchbot has joined #openstack-meeting21:00
timburkei know kota_'s busy... clayg may still join?21:01
*** zaitcev has joined #openstack-meeting21:02
timburkeapologies, i still haven't updated the agenda since before the summit21:02
timburkethere are a few things going on that i'd like to mention though21:02
timburke#topic continuing py2 support21:02
claygparty time 🥳21:02
*** openstack changes topic to "continuing py2 support (Meeting topic: swift)"21:02
timburkeit sounds like we're basically the only ones wanting to continue supporting py2. i certainly feel like that's the right decision (particularly in light of how recently we added py3 support), but there are likely to be some challenges as everyone else starts dropping support21:04
timburkelooks like devstack is switching to py3 by default21:04
timburkewhich means we need some adjustment of our jobs to continue *actually* testing py221:05
patchbotpatch 695057 - swift - Switch py2 DSVM jobs to only run swift under py2 - 1 patch set21:05
timburke...should fix up our dsmv jobs, but there will probably be some other, similar changes that will come along21:06
*** ociuhandu has quit IRC21:06
timburkebasically, just a heads-up: you might want to periodically check that the gate tests are actually exercising the environments that we *think* they are21:06
timburkesee also:21:07
timburke(which i think is what caused out lower-constraints trouble recently)21:07
timburke#topic stable21:08
*** openstack changes topic to "stable (Meeting topic: swift)"21:08
timburkei recently requested a couple more stable releases, for stein and rocky21:08
patchbotpatch 694854 - releases - Swift stable releases - 2 patch sets21:08
timburkejust as an FYI21:08
mattoliverauoh nice21:08
timburkebut speaking of stable, there have been some interesting conversations on the mailing list about per-project stable cores and who should own that list21:09
timburkebasically, "The proposal that I had was that in mind would be for us to let teams self manage their own stable branches."21:10
mattoliverauthat makes sense to be honest, I never really understood why there was a seperate team21:11
mattoliverauor rather, why it wasn't cores of project + stable team dealing with backports.21:11
timburkeyeah, seems reasonable to me, too. and i think giving project teams that ownership may increase their interest in proposing backports21:12
timburkeor, push them to acknowledge that stable branches aren't really a thing that they do. not sure yet which camp swift would fall into ;-P21:13
claygtimburke: you're a backport master!21:13
*** eharney has joined #openstack-meeting21:14
timburkeclayg, it's one of the nice things about a hand-curated changelog! every couple months or so you've got someone looking through the history and thinking about what's noteworthy, how things impact clients, etc.21:14
timburkeanyway, just a conversation i thought worth pointing out21:15
clayghandcrafted software21:15
timburke#topic PTG photos21:15
*** openstack changes topic to "PTG photos (Meeting topic: swift)"21:15
timburkethey're up!21:15
timburkeand specific to swift...21:15
timburkethanks again to everybody who came, and i look forward to the next time we can all get together :-)21:16
claygvancover!!!  we need mattoliverau21:17
mattoliveraugreat to see cschwede there!21:17
timburkeclayg, mattoliverau's beach house! i bet february's *great* in australia!21:17
mattoliverauyeah, middle of summer on the beach.. it can't really be beat :)21:18
timburkethat's all i've got -- on to updates!21:18
timburke#topic null namespace & versioning21:18
*** openstack changes topic to "null namespace & versioning (Meeting topic: swift)"21:18
timburkeclayg, tdasilva, how's it going?21:18
claygswift's new version api + swiftclient is a lot of fun to use21:19
clayglisting versions and all that fun stuff21:19
claygI'm working on cleaning up the s3api patch21:19
claygshould have all the todos done and tests passing by friday21:19
claygbefore I sign off for t-day next week I expect they'll have my +2 on them anyway21:20
claygbut, it'll be interesting to see what gaps @tdasilva and @timburke find when they get back from their vactions 🤔21:20
claygit's always amazing what a fresh set of eyes can do21:20
*** raildo has quit IRC21:20
claygor even the same eyes - but after they've rested 🤣21:21
tdasilvanew eyes are good too! :)21:21
claygregardless I'm super happy about what we've built - swift's new versoining mode is a really great feature and it makes putting a solid s3 implementation on top just a delight21:21
timburkemattoliverau, alecuyer, rledisez, seongsoocho: this has been a very SwiftStack-driven set of patches -- do you guys have any concerns about that? would any of you want to be sure to review it before it lands on master?21:22
mattoliverauI'll definitely give em a review (and a play) :)21:23
timburkeyay! thanks, mattoliverau21:23
alecuyerIt sounds really good, but yes I need to take the time to actually try it out and read the code!21:23
rledisezi'll try to look at it, not that I have any concerns, but mostly to be sure I understand how it works21:24
claygawesome thanks everyone!21:25
timburkeclayg, are there any last lingering questions or design decisions we ought to bring up with everyone? or is it mostly just a matter of polish at this point?21:25
claygwell we added the swift-specific features for restore with PUT?version-id=x21:26
seongsoocho( I need to take the time to follow up the review.  and I also have a interest about that )21:26
claygthat's a cool trick, and a new API - but it'll all be covered in docs when we're done (and mostly supported in swiftclient)21:26
claygof course you'll be able to ignore all that noise and just use aws s3api cli tool if that's your thing as well21:27
timburkeclayg, right -- because there's also this difference between swift and s3 when doing a version-aware delete of the current version, right?21:28
claygyeah, the other difference with s3 is applying a version-id to unversioned objects when they're overwritten after enabling versioning21:29
claygbasically those design choices make things work better for the swift api given our underlying implementation21:29
claygbut it's probably fine; because s3's behavior there was a bit akward21:30
clayghowever if you REALLY want to destroy the current version AND make the previous version the current versoin we won't do that with one request21:30
clayg... we could potentially add some api sugar to do that at some point - but it's nice if the client can be explicit21:31
timburke...which is probably for the best anyway -- since the proxy would need to make multiple back-end requests even if we could make it one client request21:32
claygYOU BETCHA!21:32
timburkeall right21:32
timburke#topic losf21:32
*** openstack changes topic to "losf (Meeting topic: swift)"21:32
timburkealecuyer, rledisez -- in light of our discussions at the PTG, should i just table this for a while, let us add it back to the agenda if/when it makes sense again?21:33
alecuyeryes, I think that's right21:34
rlediseztimburke: I think it still make sense because there is a use case for it. the question is will it match the next use case?21:34
rledisezbut right now, the dev on losf in OVH is a bit slowing down21:34
rledisezso i'm okay with that too :)21:35
timburkei was about to say -- or, we could turn it into a broader discussion about what you've found in trying things with zfs/xfs-with-realtime-device :-)21:35
rlediseztimburke: we can also do that :)21:35
rledisezin very short I would say the 2 viable options still in course would be zfs or losf :)21:35
rledisezbut we are still investigating21:35
alecuyerI've played with eBPF a bit, it's suprisingly easy to count the VFS calls, but harder to account for it at the block device level. Anyway I'll keep working on this, and trying LOSF/ ZFS etc, and I'll share the results21:36
*** enriquetaso has quit IRC21:36
timburkesounds good21:37
timburke#topic profiling21:38
*** openstack changes topic to "profiling (Meeting topic: swift)"21:38
timburke landed!21:38
patchbotpatch 693116 - swift - proxy: stop sending chunks to objects with a Queue (MERGED) - 5 patch sets21:38
rledisezyeah, thx for all the "recheck" ;)21:39
mattoliveraugreat work on that rledisez21:39
rlediseznot much profiling this week. i have a patch to implement watchdog, all tests passes except 4, I need to dig why.21:39
rledisezafter that I have a couple of other small improvement to come21:39
rledisezand I though a bit more about replacing MD5 for checksuming, I should write that down on etherpad21:40
mattoliveraunice, look forward to them :)21:40
timburkei think i also saw a couple new cases on the etherpad? same-chunk, where proxy and object servers match chunk sizes21:40
rledisezand I'm thinking about etag and the API. the behavior is already a bit "strange" depending on the type of object (raw, SLO, DLO). I'm wondering at some point if we can just "disable" it (from an api point of view)21:41
rlediseztimburke: yes, if the cunk size match, performance are better21:41
*** pcaruana has quit IRC21:42
timburkeall right, i think that's about it21:44
timburke#topic open discussion21:44
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:44
timburkeis there anything else to bring up?21:44
*** e0ne has quit IRC21:44
timburkeall right, let's let mattoliverau and seongsoocho get breakfast :-)21:47
* mattoliverau is hungry21:47
timburkethank you all for coming, and thank you for working on swift!21:47
timburkeoh! one last thing: in light of thanksgiving week next week (and the fact that i'll be on vacation ;-) let's skip the meeting next week21:48
*** dviroel has quit IRC21:48
timburkethanks again!21:48
*** openstack changes topic to "OpenStack Meetings ||"21:48
openstackMeeting ended Wed Nov 20 21:48:32 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:48
openstackMinutes (text):
mattoliverauhave some turkey for those of us who don't have a holiday :)21:48
*** zaitcev has left #openstack-meeting21:55
*** rosmaita has left #openstack-meeting21:55
*** ociuhandu has joined #openstack-meeting21:59
*** ociuhandu has quit IRC22:07
*** anastzhyr has quit IRC22:08
*** slaweq has quit IRC22:26
*** rcernin has joined #openstack-meeting22:31
*** ayoung has quit IRC22:32
*** slaweq has joined #openstack-meeting22:35
*** ayoung has joined #openstack-meeting22:36
*** slaweq has quit IRC22:40
*** kopecmartin is now known as kopecmartin|off22:42
*** slaweq has joined #openstack-meeting22:50
*** enriquetaso has joined #openstack-meeting22:53
*** slaweq has quit IRC22:55
*** jamesmcarthur has quit IRC22:57
*** ayoung has quit IRC23:01
*** ayoung has joined #openstack-meeting23:05
*** slaweq has joined #openstack-meeting23:05
*** slaweq has quit IRC23:10
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:15
*** brault has joined #openstack-meeting23:16
*** slaweq has joined #openstack-meeting23:21
*** ykatabam has joined #openstack-meeting23:25
*** slaweq has quit IRC23:26
*** slaweq has joined #openstack-meeting23:30
*** enriquetaso has quit IRC23:34
*** slaweq has quit IRC23:35
*** slaweq has joined #openstack-meeting23:37
*** slaweq has quit IRC23:45
*** slaweq has joined #openstack-meeting23:48
*** kaisers1 has quit IRC23:48
*** kaisers has joined #openstack-meeting23:48
*** slaweq has quit IRC23:53
*** mattw4 has quit IRC23:59

Generated by 2.15.3 by Marius Gedminas - find it at!