Wednesday, 2019-08-07

*** yamamoto has quit IRC00:04
*** lseki has quit IRC00:06
*** mmethot_ has joined #openstack-meeting00:09
*** mmethot has quit IRC00:13
*** rbudden has joined #openstack-meeting00:13
*** mattw4 has quit IRC00:16
*** b1airo has quit IRC00:19
*** markvoelker has joined #openstack-meeting00:23
*** tetsuro has joined #openstack-meeting00:32
*** senrique_ has joined #openstack-meeting00:33
*** hongbin has joined #openstack-meeting00:34
*** jamesmcarthur_ has quit IRC00:47
*** armax has quit IRC00:50
*** yamamoto has joined #openstack-meeting00:52
*** ykatabam has joined #openstack-meeting00:52
*** tetsuro has quit IRC00:57
*** jamesmcarthur has joined #openstack-meeting01:01
*** ricolin has joined #openstack-meeting01:02
*** tetsuro has joined #openstack-meeting01:02
*** jamesmcarthur has quit IRC01:04
*** carloss has quit IRC01:11
*** igordc has quit IRC01:13
*** igordc has joined #openstack-meeting01:15
*** ricolin_ has joined #openstack-meeting01:17
*** ricolin has quit IRC01:20
*** igordc has quit IRC01:23
*** pcaruana has quit IRC01:26
*** tetsuro has quit IRC01:28
*** gyee has quit IRC01:33
*** yamahata has quit IRC01:38
*** iyamahat_ has quit IRC01:38
*** markvoelker has quit IRC01:39
*** bobh has joined #openstack-meeting01:40
*** markvoelker has joined #openstack-meeting01:40
*** jamesmcarthur has joined #openstack-meeting01:56
*** jamesmcarthur has quit IRC01:58
*** jamesmcarthur has joined #openstack-meeting01:59
*** haleyb has quit IRC02:01
*** apetrich has quit IRC02:09
*** ykatabam has quit IRC02:18
*** jamesmcarthur has quit IRC02:22
*** jamesmcarthur has joined #openstack-meeting02:22
*** jamesmcarthur has quit IRC02:25
*** jamesmcarthur has joined #openstack-meeting02:26
*** ricolin_ is now known as ricolin02:27
*** senrique_ has quit IRC02:41
*** yamamoto has quit IRC02:44
*** yamamoto has joined #openstack-meeting02:45
*** igordc has joined #openstack-meeting02:49
*** ircuser-1 has quit IRC02:52
*** bobh has quit IRC02:53
*** jamesmcarthur has quit IRC02:56
*** tetsuro has joined #openstack-meeting02:58
*** ykatabam has joined #openstack-meeting03:07
*** jamesmcarthur has joined #openstack-meeting03:12
*** markvoelker has quit IRC03:14
*** whoami-rajat has joined #openstack-meeting03:19
*** yamahata has joined #openstack-meeting03:20
*** tetsuro has quit IRC03:29
*** psachin has joined #openstack-meeting03:36
*** markvoelker has joined #openstack-meeting03:38
*** ianychoi_ has joined #openstack-meeting03:38
*** ianychoi has quit IRC03:42
*** markvoelker has quit IRC03:43
*** pcaruana has joined #openstack-meeting03:44
*** hongbin has quit IRC03:49
*** dviroel has quit IRC03:59
*** jamesmcarthur has quit IRC04:00
*** tetsuro has joined #openstack-meeting04:03
*** diablo_rojo has joined #openstack-meeting04:04
*** markvoelker has joined #openstack-meeting04:24
*** jamesmcarthur has joined #openstack-meeting04:30
*** markvoelker has quit IRC04:38
*** rbudden has quit IRC04:39
*** jamesmcarthur has quit IRC04:55
*** rbudden has joined #openstack-meeting04:58
*** jamesmcarthur has joined #openstack-meeting05:01
*** links has joined #openstack-meeting05:06
*** diablo_rojo has quit IRC05:11
*** Luzi has joined #openstack-meeting05:19
*** kopecmartin|off is now known as kopecmartin05:23
*** tetsuro has quit IRC05:30
*** igordc has quit IRC05:31
*** jamesmcarthur has quit IRC05:35
*** iyamahat has joined #openstack-meeting05:35
*** ociuhandu has joined #openstack-meeting05:49
*** ociuhandu has quit IRC05:53
*** jamesmcarthur has joined #openstack-meeting06:03
*** markvoelker has joined #openstack-meeting06:18
*** markvoelker has quit IRC06:22
*** tetsuro has joined #openstack-meeting06:24
*** apetrich has joined #openstack-meeting06:37
*** jamesmcarthur has quit IRC06:37
*** slaweq has joined #openstack-meeting06:48
*** yamamoto has quit IRC07:00
*** rcernin has quit IRC07:03
*** tssurya has joined #openstack-meeting07:08
*** yamamoto has joined #openstack-meeting07:09
*** ykatabam has quit IRC07:10
*** tesseract has joined #openstack-meeting07:26
*** ralonsoh has joined #openstack-meeting07:29
*** jamesmcarthur has joined #openstack-meeting07:35
*** lpetrut has joined #openstack-meeting07:38
*** ralonsoh has quit IRC07:54
*** jamesmcarthur has quit IRC08:08
*** Lucas_Gray has joined #openstack-meeting08:12
*** links has quit IRC08:12
*** mauro|call has quit IRC08:13
*** mauro|call has joined #openstack-meeting08:14
*** e0ne has joined #openstack-meeting08:18
*** panda has quit IRC08:22
*** links has joined #openstack-meeting08:23
*** panda has joined #openstack-meeting08:23
*** ralonsoh has joined #openstack-meeting08:26
*** tetsuro has quit IRC08:35
*** ralonsoh has quit IRC08:35
*** tetsuro has joined #openstack-meeting08:36
*** jamesmcarthur has joined #openstack-meeting08:42
*** ralonsoh has joined #openstack-meeting08:47
*** Lucas_Gray has quit IRC08:48
*** markvoelker has joined #openstack-meeting08:50
*** Lucas_Gray has joined #openstack-meeting08:53
*** markvoelker has quit IRC08:55
*** mauro|call has quit IRC08:58
*** mauro|call has joined #openstack-meeting09:00
*** Lucas_Gray has quit IRC09:01
*** Lucas_Gray has joined #openstack-meeting09:02
*** ociuhandu has joined #openstack-meeting09:03
*** ociuhandu has quit IRC09:13
*** mauro|call is now known as takamatsu09:14
*** ociuhandu has joined #openstack-meeting09:16
*** tetsuro has quit IRC09:19
*** ociuhandu has quit IRC09:25
*** ociuhandu has joined #openstack-meeting09:29
*** jamesmcarthur has quit IRC09:57
*** ricolin_ has joined #openstack-meeting10:01
*** zaneb has quit IRC10:03
*** zbitter has joined #openstack-meeting10:03
*** ricolin has quit IRC10:03
*** carloss has joined #openstack-meeting10:12
*** yamamoto has quit IRC10:18
*** ykatabam has joined #openstack-meeting10:39
*** yamamoto has joined #openstack-meeting10:41
*** yamamoto has quit IRC10:45
*** rfolco has joined #openstack-meeting10:54
*** rfolco|ruck has quit IRC10:54
*** yamamoto has joined #openstack-meeting10:59
*** ociuhandu has quit IRC11:07
*** Wryhder has joined #openstack-meeting11:16
*** Lucas_Gray has quit IRC11:17
*** Wryhder is now known as Lucas_Gray11:17
*** Lucas_Gray has quit IRC11:21
*** Lucas_Gray has joined #openstack-meeting11:31
*** raildo has joined #openstack-meeting11:38
*** jamesmcarthur has joined #openstack-meeting11:38
*** boxiang has quit IRC11:42
*** boxiang has joined #openstack-meeting11:42
*** markvoelker has joined #openstack-meeting11:49
*** ociuhandu has joined #openstack-meeting12:09
donnydSo I have the compiled data on where the nodepool instances are headed on the public interwebs12:11
*** markvoelker has quit IRC12:11
donnydJust trying to figure out how to present it in a way that doesn't cough up topologies12:11
*** ociuhandu has quit IRC12:14
*** jamesmcarthur has quit IRC12:16
*** markvoelker has joined #openstack-meeting12:16
*** ociuhandu has joined #openstack-meeting12:19
*** ociuhandu has quit IRC12:22
*** ociuhandu has joined #openstack-meeting12:23
*** ykatabam has quit IRC12:27
*** kaisers has joined #openstack-meeting12:28
*** rfolco has quit IRC12:28
*** Lucas_Gray has quit IRC12:34
*** ociuhandu has quit IRC12:38
*** haleyb has joined #openstack-meeting12:38
*** ociuhandu has joined #openstack-meeting12:39
*** zbr has quit IRC12:46
*** ociuhandu has quit IRC12:46
*** ociuhandu has joined #openstack-meeting12:48
*** ricolin_ is now known as ricolin12:48
*** jamesmcarthur has joined #openstack-meeting12:49
*** zbr has joined #openstack-meeting13:02
*** Lucas_Gray has joined #openstack-meeting13:09
*** mriedem has joined #openstack-meeting13:10
*** lseki has joined #openstack-meeting13:12
*** iyamahat has quit IRC13:13
*** iyamahat_ has joined #openstack-meeting13:13
*** jamesmcarthur has quit IRC13:13
*** jamesmcarthur has joined #openstack-meeting13:14
*** raub has quit IRC13:22
*** zbitter is now known as zaneb13:22
donnydOk, I think I have it sanitized enough. Now should I send it somewhere?13:39
*** jamesmcarthur has quit IRC13:44
*** raub has joined #openstack-meeting13:46
*** jamesmcarthur has joined #openstack-meeting13:46
*** ociuhandu has quit IRC13:48
*** ociuhandu has joined #openstack-meeting13:49
*** Lucas_Gray has quit IRC13:49
*** electrofelix has quit IRC13:50
*** jamesmcarthur has quit IRC13:51
*** jamesmcarthur has joined #openstack-meeting13:53
*** links has quit IRC13:55
*** Lucas_Gray has joined #openstack-meeting13:56
*** tesseract has quit IRC13:56
*** tesseract has joined #openstack-meeting13:57
*** whoami-rajat has quit IRC13:57
*** tesseract has quit IRC14:00
liuyulong#startmeeting neutron_l314:00
openstackMeeting started Wed Aug  7 14:00:53 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:01
liuyulong#chair haleyb14:01
openstackCurrent chairs: haleyb liuyulong14:01
liuyulong#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:01
*** tesseract has joined #openstack-meeting14:01
liuyulongUnfortunately, the port forwarding topic was not accepted by the Summit Team.14:03
*** ociuhandu has quit IRC14:03
liuyulongSo mlavalle and I will not share this in the Summit. : )14:04
liuyulongAny other announcements?14:04
liuyulongOK, let's move on.14:05
liuyulong#topic Bugs14:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:05
*** ociuhandu has joined #openstack-meeting14:06
*** liuyulong_ has joined #openstack-meeting14:07
haleybthere were some new bugs filed last week in the l3 space14:07
*** slaweq has quit IRC14:07
liuyulong_Bad network connection...14:07
openstackLaunchpad bug 1838699 in neutron "Removing a subnet from DVR router also removes DVR MAC flows for other router on network" [High,Confirmed]14:08
*** slaweq has joined #openstack-meeting14:08
haleybslaweq confirmed it, but it will need an owner14:08
ralonsohMy comment yesterday was not registered...14:08
ralonsohin this bug14:09
openstackLaunchpad bug 1838697 in neutron "DVR Mac conversion rules are only added for the first router a network is attached to" [Undecided,Incomplete]14:09
liuyulong_this is also related.14:09
ralonsohif you have more than one DVR, the match flows will be the same14:09
ralonsohthat means, when you deleted the flows, you'll delete all of them14:09
haleybliuyulong_: ack, makes sense think they were both filed by same person14:09
ralonsoh(I'l write this comment again in the bug)14:10
haleybralonsoh: thanks14:10
liuyulong_ralonsoh, so it is designed like that, it is a feature?14:10
ralonsohI don't think so14:10
ralonsohthat means we can't have more than one DVR per host14:11
ralonsohbut I need confirmation14:11
*** ociuhandu has quit IRC14:11
ralonsohI'll write the comment again in the bug14:11
*** dviroel has joined #openstack-meeting14:11
liuyulong_OK, thank you, I read some code ealier, the ovs-agent will query the related flow by ports subnet.14:12
liuyulong_If more than one dvr ports in same subnet, it will indeed delete once for all.14:12
liuyulong_haleyb, I have bad network connection now, please take over the meeting chair.14:15
haleybnext bug,
openstackLaunchpad bug 1838793 in neutron ""KeepalivedManagerTestCase" tests failing during namespace deletion" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:15
haleyb was created - thanks ralonsoh14:15
ralonsohI need to check the CI again14:16
haleybralonsoh: i've added myself to review so will look at next update14:16
haleybnext bug,
openstackLaunchpad bug 1838403 in neutron "Asymmetric floating IP notifications" [Medium,New]14:18
haleybi had triaged this last week and couldn't reproduce part of it.  see now it was on queens, so perhaps part was fixed14:19
haleybstill needs owner to track down the other possible issued with notifications, if noone wants it i can take a look14:20
liuyulong_How to "delete a router that still has fip"?14:20
*** ociuhandu has joined #openstack-meeting14:20
haleybliuyulong_: right, it didn't work for me on master, but can't imagine it works on queens either14:20
haleybliuyulong_: the part we need to investigate is what happens with a VM is destroyed - is the floating IP in one of the messages?  his trace showed it wasn't14:21
liuyulong_If the VM port is delete, l3_db will catch port_delete notification and release the FIP.14:22
haleybliuyulong_: yes, but is that sending a notification?14:24
*** ociuhandu has quit IRC14:25
* haleyb wonders how fast liuyulong_'s modem is :) (if anyone remembers what a modem is)14:25
ralonsoh28.8 bauds per sec14:26
haleybzoom zoom14:26
liuyulong_Subscrition is more accurate.14:26
haleybliuyulong_: oh, maybe they didn't subscribe to all the events?14:27
*** Lucas_Gray has quit IRC14:27
liuyulong_This line it is.14:28
*** ykatabam has joined #openstack-meeting14:28
*** Lucas_Gray has joined #openstack-meeting14:29
haleybliuyulong_: there is nothing there regarding floating IP though, maybe i'm mis-understanding14:30
*** Luzi has quit IRC14:30
haleybliuyulong_: if i'm listening for FLOATINGIP events shouldn't i get one when a port with an associated floating IP is deleted?14:31
haleybeither way, please add a comment to the bug so maybe the submitter can track things down14:32
liuyulong_I have no details about the FIP events now, but according to my experiences, the floating IP will finally get disassociated.14:33
haleybthere was one more new bug14:33
openstackLaunchpad bug 1839004 in neutron "Rocky DVR-SNAT seems missing entries for conntrack marking" [Undecided,Incomplete]14:33
haleybdon't know if tidwellr is here, but this looked like maybe a mis-configuration14:34
* tidwellr is lurking14:34
haleybtidwellr: hi, and this involved dynamic-routing too, any thoughts based on last update?14:35
tidwellrthere's still something to look into in that bug, supposedly there was an address scope mismatch and yet the API was reporting that it was finding a next-hop for the tenant subnet14:36
tidwellrthat doesn't seem right14:36
haleybtidwellr: it could be correct if snat was enabled though i think, but he had it disabled14:37
*** senrique_ has joined #openstack-meeting14:38
tidwellryou can see that the uplink subnet is in the null address scope14:40
*** Wryhder has joined #openstack-meeting14:40
tidwellrthen, he shows neutron-dynamic-routing returning a next-hop for his tenant subnet14:40
tidwellrthat should only happen if the inside and outside subnets are both in the same address scope14:41
tidwellreither the info in the bug report is inaccurate, or there is still a bug14:41
*** Lucas_Gray has quit IRC14:41
*** Wryhder is now known as Lucas_Gray14:41
haleybso is that a bug in neutron or dynamic-routing?14:42
tidwellrassuming the steps in the bug report are accurate, yes14:42
tidwellrnot sure how that would slip through the tests though, I would have to really look closely at that14:43
haleybyes a bug in dynamic-routing?14:43
tidwellrhe ran "openstack bgp speaker list advertised routes" and it returned routes it shouldn't have had14:44
haleybtidwellr: should we re-assign?  as the scoping issue looks like user error14:44
*** ociuhandu has joined #openstack-meeting14:45
*** ykatabam has quit IRC14:45
*** mattw4 has joined #openstack-meeting14:46
tidwellrI'll leave a comment, then try to reproduce this myself. It seems pretty straight forward given his instructions in the bug report14:46
*** altlogbot_2 has quit IRC14:46
haleybtidwellr: thanks14:46
haleybliuyulong_: i didn't have any other new bugs, did you have old ones you wanted to talk about?  or anyone else?14:46
*** altlogbot_0 has joined #openstack-meeting14:47
liuyulong_Yes, I have14:47
liuyulong_For the fix: and the
openstackLaunchpad bug 1834308 in neutron "[DVR][DB] too many slow query during agent restart" [Medium,In progress] - Assigned to LIU Yulong (dragon889)14:48
*** yamamoto has quit IRC14:48
liuyulong_It is well tested locally. It does not break DVR functions. But I still hope to see if more test result can come from our community.14:49
liuyulong_The next is:
openstackLaunchpad bug 1828494 in neutron "[RFE][L3] l3-agent should have its capacity" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)14:50
liuyulong_I have one question, how many router do you guys think a network node can host? 100? 200? 1000?14:51
ralonsohno idea14:51
tidwellrwhen I ran network nodes in production, we capped it at 25014:51
haleybliuyulong_: there is no easy answer for that14:51
*** jamesmcarthur has quit IRC14:51
haleybi think the limiting factor always seems to be how long it takes to restart the agents14:52
tidwellrthere are a lot of unique factors that go into that number we came up with though14:52
tidwellrand when I say we capped it, I mean we would add network nodes and rebalance routers to spread the load14:52
liuyulong_I have one result, when the router reach 300+, the ovs-agent will never restart successfully.14:53
tidwellrthat's consistent with what I've observed (anecdotally)14:54
*** ianychoi_ is now known as ianychoi14:54
liuyulong_My env is 17 physical hosts for dvr_snat nodes, with 2700+ router, disable DHCP.14:54
*** yamamoto has joined #openstack-meeting14:54
liuyulong_Every ovs-agent will host about 1700+ ports!14:54
liuyulong_Yes, I've tested 400+ ports for a ovs-agent once, it is about 40+ mins to restart.14:55
*** mattw4 has quit IRC14:55
liuyulong_Ovs-agent seems can be easily stuck in many code path....14:57
haleybthat is too long of course, should it be on the performance sub-team's list ?14:58
liuyulong_Should be, make sense15:00
haleybliuyulong_: we're at time15:01
liuyulong_Let's end here.15:01
liuyulong_This nick does not have that right.15:01
liuyulong_haleyb, please end our meeting, thank you.15:01
*** openstack changes topic to "OpenStack Meetings ||"15:02
openstackMeeting ended Wed Aug  7 15:02:00 2019 UTC.  Information about MeetBot at . (v 0.1.4)15:02
openstackMinutes (text):
*** mattw4 has joined #openstack-meeting15:02
*** liuyulong_ has quit IRC15:02
*** iyamahat_ has quit IRC15:04
*** mattw4 has quit IRC15:08
*** mattw4 has joined #openstack-meeting15:09
*** jamesmcarthur has joined #openstack-meeting15:18
*** ircuser-1 has joined #openstack-meeting15:19
*** yamamoto has quit IRC15:21
*** yamamoto has joined #openstack-meeting15:21
*** slaweq_ has joined #openstack-meeting15:26
*** slaweq has quit IRC15:29
*** davidsha has joined #openstack-meeting15:31
*** rosmaita has joined #openstack-meeting15:35
*** zhengMa has joined #openstack-meeting15:37
*** tosky has joined #openstack-meeting15:45
*** diablo_rojo has joined #openstack-meeting15:48
*** apetrich has quit IRC15:51
*** jamesmcarthur has quit IRC15:52
*** apetrich has joined #openstack-meeting15:53
*** armax has joined #openstack-meeting15:55
*** whoami-rajat has joined #openstack-meeting15:55
*** woojay has joined #openstack-meeting15:56
*** ralonsoh has quit IRC15:57
*** ralonsoh has joined #openstack-meeting15:58
*** tesseract has quit IRC15:58
*** jbadiapa has joined #openstack-meeting16:00
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Aug  7 16:00:39 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 tosky16:00
geguileohi! o/16:01
_pewp_jungleboyj (。・∀・)ノ16:01
jungleboyjThis week's agenda:16:01
*** tesseract has joined #openstack-meeting16:02
jungleboyjLooks like we have all the usual suspects here.16:03
jungleboyjSo, we can get started.16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:03
jungleboyjWe are just two weeks from our mid-cycle:
jungleboyjTopics are still a little light.16:04
jungleboyjGlad to see we are back up to 5 people in physical attendance.16:04
jungleboyjWelcome woojay !16:04
woojaythank you.16:04
*** yamamoto has quit IRC16:05
whoami-rajatjungleboyj: should we also add the feature progress discussion there.16:05
jungleboyjSo, please get your topics into the etherpad.16:05
jungleboyjwhoami-rajat:  Yes.  I was going to work on going through our previous PTGs and pull todos and stuff out of there.16:05
*** gyee has joined #openstack-meeting16:05
jungleboyjIf you want to start a section on feature progress that would be great.16:06
jungleboyjpots: #/root16:06
*** yamamoto has joined #openstack-meeting16:06
*** yamamoto has quit IRC16:06
whoami-rajatjungleboyj:  okay, great.16:06
*** sfernand has joined #openstack-meeting16:06
jungleboyjwhoami-rajat:  Thank you.16:06
*** yamamoto has joined #openstack-meeting16:07
jungleboyjI will be getting in to Raleigh early Monday so I should be in town before everyone if you need anything.16:07
jungleboyjI will add my cell phone to the etherpad.16:07
*** igordc has joined #openstack-meeting16:07
*** iyamahat has joined #openstack-meeting16:08
jungleboyjOk.  I think that is all on that for today.  More next week.16:09
jungleboyjI have gone through all our CI systems and marked those that just aren't reporting as unsupported.16:09
*** tssurya has quit IRC16:10
jungleboyjIn a sign that the process works, Synology saw the patch and got things fixed.  :-)16:10
jungleboyjrosmaita: Indeed.16:11
jungleboyjOr they are working on fixing things at least.16:11
*** yamamoto has quit IRC16:11
jungleboyjMore on CIs later.16:11
jungleboyjrosmaita: Had an announcement.16:11
rosmaitajust a reminder of some upcoming deadlines16:12
*** Lucas_Gray has quit IRC16:12
rosmaitaTrain release of non-client libraries (os-brick, cinderlib) roughly 4 weeks away (week of 2 September)16:12
rosmaitaM-3 is the week after that (week of 9 Sept)16:12
rosmaitaM-3 marks the Train release of client libraries (python-cinderclient, python-brick-cinderclient-ext)16:12
rosmaitait is also the feature freeze16:12
rosmaitathat's all16:13
jungleboyjrosmaita:  How is patch throughput on those libraries?16:14
jungleboyjDo we need more attention to get patches in?16:14
rosmaitahaven't really checked16:14
jungleboyjrosmaita:  Ok, something we should look into before the mid-cycle so we can get reviews done if necessary.16:14
jungleboyjI added it to the etherpad.16:15
rosmaitaspot check of os-brick looks good16:15
jungleboyjOk.  Good.16:16
jungleboyjI thought I had looked a little while back and things looked ok.16:16
jungleboyjI think that is good for announcements.16:16
jungleboyj#topic Python 3rd Party CI requirement16:17
*** openstack changes topic to "Python 3rd Party CI requirement (Meeting topic: cinder)"16:17
jungleboyjSo, despite our best efforts to communicate this new requirement.  It appears that half our CIs haven't made a chance.16:17
e0neunfortunately, it will be a hard requirement in the next release anyway16:18
kaisersjust as a note: I'm one of the stragglers and now working on it16:18
jungleboyjI sent out a note to all CI Maintainers and have not seen e-mail back.16:18
jungleboyjI do see that two maintainers have updated the etherpad as requested.16:19
jungleboyjkaisers: Thank you for the update.16:19
jungleboyjAlso Hedvig is working on support.16:19
jungleboyjWe have a couple CIs that need to be updated from py3.5 to 3.716:19
jungleboyjNot rushing to mark them unsupported as they are on 3.516:19
jungleboyjThank you to rosmaita and pots for putting together some helpful information.16:20
jungleboyjSo, the question is what do we do now?16:20
jungleboyjDo I mark half out drivers as unsupported?16:20
* jungleboyj doesn't really want to be the PTL that cut the project in half. :-)16:21
e0neIMO we need to do it16:21
smcginnisBetter to do it now and give some warning than just having them removed in U because they can no longer work.16:21
e0nebecause they won't work in U16:21
smcginnise0ne: ++16:21
jungleboyje0ne: smcginnis ++16:21
eharneyjust for context... why won't they work in U?16:21
*** ociuhandu has quit IRC16:22
e0neeharney: U release will drop python2 support16:22
*** jamesmcarthur has joined #openstack-meeting16:22
*** ociuhandu has joined #openstack-meeting16:22
jungleboyjThe thing that scares me is that the vendors continue to be ignorant of this.16:22
rosmaitai wonder whether we leave them in for T but have an additional flag or something for the driver page16:22
*** jbadiapa has quit IRC16:23
rosmaitagive just a bit more time to get them fully supported for U16:23
*** ricolin_ has joined #openstack-meeting16:23
jungleboyjWe pull the drivers in V and then when customers update to that level in a couple years we have a crap storm on our hands.16:23
e0nerosmaita: that's why we introduced 'unsupported' flag16:23
smcginnisThey will be left in for T, they just will require an operator to explicitly declare in their config that they are aware they are running a driver that is not validated.16:24
jungleboyjrosmaita:  I don't have a problem with adding a py3 support flag in the matrix so it is clear that is why it is being deprecated.16:24
rosmaitawell, the thing is, if they are running T on py2, they should actually be supported, right?16:24
smcginnisBut then if they don't in U, we haven't gone through a deprecation period to remove them.16:25
potsI didn't make any changes to my driver when I switched from 2.7 to 3.7, so it's conceivable that these other drivers won't all stop working when python2 is gone.16:25
*** ricolin has quit IRC16:26
smcginnispots: Yes, but no way to know that for sure and that is why we have the third party CI requirement we have had since ~icehouse.16:26
eharneyhave we heard anything about issues blocking CIs from moving to py3?  or is it mostly just about making sure someone goes and does it?16:26
* jungleboyj loves pots' optimism. 16:26
smcginnisHedvig did find they have a code issue with py3.7, but likely something easy(ish) to fix.16:26
jungleboyjeharney:  Based on pots  it is about people actually paying attention and doing it.16:26
jungleboyjeharney or rosmaita:  Do you have any strings as Red Hat to pull to try to get more attention to this?16:28
jungleboyjThis is going to impact you guys as much as anyone.16:28
eharneyjungleboyj: our string is that drivers will have to certify on python 3.6 for the Stein release of our product16:28
*** ociuhandu has quit IRC16:28
*** markvoelker has quit IRC16:28
jungleboyjeharney: So, they need to show support even before train.16:29
*** ricolin_ is now known as ricolin16:29
*** psachin has quit IRC16:30
jungleboyjSo, some vendors will get hit by this for RHOSP16 ?16:30
jungleboyjOh.  That is right.16:31
jungleboyjThat is in beta right now.  So, what testing has been done there?16:31
eharneyi'm not sure it's gotten too far down the path of driver certification yet16:32
jungleboyjeharney:  So, that isn't too helpful at this point.16:33
potsjust curious, does anyone offer Cinder CI as a service, as an alternative to every vendor rolling their own?16:33
jungleboyjDo you think you can find out a bit more before the mid-cycle eharney.16:33
smcginnisA few of us have joked about starting a business to do that for years.16:33
jungleboyjpots: Someone could be rich.16:33
jungleboyjpots:  Looking to start a business?16:33
eharneyjungleboyj: sure16:33
e0nepots: only for opensource storages :)16:34
jungleboyjeharney:  Thanks.16:34
potswell, this is so different from how we certify storage for Windows, VMware, etc.  It might be easier for some companies to just write a check than to stand up a CI like this in house.16:35
smcginnisYeah, I do think it's a legitimate business idea.16:35
jungleboyjpots:  But then someone needs to have one of every storage backend.16:35
e0nepots: such CIs require to have a hardware16:35
jungleboyje0ne: ++16:35
potshardware is the easy part for the vendors16:36
smcginnisJust need a colo facility and customers to ship their hardware to you.16:36
potsI'm in NYC.  I DO have free electricity in my apartment but...16:36
jungleboyjpots:  Come join us at the mid-cycle and we can start a business plan.16:37
smcginnisAnyway, probably should get back to business.16:37
jungleboyjI am going Solar and to 1 GB fibre this fall.  Not sure I have enough outlets.16:37
jungleboyjYeah, back to business.16:37
jungleboyjSo, it sounds like I should start pushing up the unsupported patches.16:37
jungleboyjDo we want to add a field to the support matrix?16:38
e0nejungleboyj: +116:38
rosmaitaso getting back to the 'unsupported' issue, is it possible to keep them supported in T but 'deprecated' due to lack of py3 CI?16:38
*** markvoelker has joined #openstack-meeting16:38
jungleboyjrosmaita: The previous answer was that that is what the unsupported flag is for.16:38
*** baojg has quit IRC16:38
rosmaitayeah, but it seems different semantically16:39
rosmaitathough i haven't been around here very long, admittedly16:39
jungleboyjThe point there is to get people's attention when they upgrade.  The driver is about to not work and the operator should know that.16:39
smcginnisWell, if it was a requirement to run CI under py37, and they didn't update their CI, then that does meet the requirement that it is unsupported.16:39
*** tesseract has quit IRC16:39
smcginnisBut I get the nuance.16:39
*** ricolin has quit IRC16:40
rosmaitai'm just worried about the sheer number of noncompliant drivers16:40
jungleboyjSo, I guess that is an optics issue.16:40
jungleboyjDo we add a new flag/warning for T and hope that people do something about it.16:40
whoami-rajatjungleboyj: the drivers running py35 or py36 won't be marked unsupported right?16:41
*** lpetrut has quit IRC16:41
jungleboyjwhoami-rajat: No, but I will be following up with them to get them to udpate it.16:41
eharneyis there a doc/landing page somewhere for people to get all the info if they are suddenly finding a "your driver is unsupported." message from cinder?16:41
jungleboyjWell, we have the release note that goes with it explaining what it means.16:42
*** markvoelker has quit IRC16:42
jungleboyjWe don't have a page explaining all that that I know of.  Happy to add some documentation.16:42
smcginnisI think the release notes we include with that are pretty good -
jungleboyjThat is probably a good thing to do.16:43
*** markvoelker has joined #openstack-meeting16:44
*** baojg has joined #openstack-meeting16:44
*** baojg has quit IRC16:44
jungleboyjYeah, it tells them what to do.16:44
jungleboyjI think it would be good to have an operator facing page that explains why this happens thouhg.16:44
*** ociuhandu has joined #openstack-meeting16:44
*** baojg has joined #openstack-meeting16:44
jungleboyjJust now that we are likely to have more people running into this.16:44
*** baojg has quit IRC16:45
jungleboyjWant to make it clear that this is something they should follow up with the vendor on, not be mad at OpenStack.16:45
*** baojg has joined #openstack-meeting16:45
*** baojg has quit IRC16:45
jungleboyjSo, I will look into doing that.16:46
*** baojg has joined #openstack-meeting16:46
rosmaitai guess my caveat to marking these unsupported would be the releasenote should be clear it's a py3 CI issue16:46
*** baojg has quit IRC16:46
rosmaitai think we want to distinguish people doing py2 CI vs. no CI at all16:46
jungleboyjrosmaita:  Ok.  Agreed.16:46
jungleboyjrosmaita: ++16:46
*** baojg has joined #openstack-meeting16:47
*** baojg has quit IRC16:47
jungleboyjOk, so, make the reason clear in the release note.  Improve the documentation on what it means to be unsupported.16:47
*** baojg has joined #openstack-meeting16:48
*** baojg has quit IRC16:48
rosmaitai can take a crack at the doc improvement, because i clearly don't have a good grasp of this at the moment16:48
jungleboyjStart submitting patches for this.  Try to hold out until late in the release to merge the patches to give other people time to start fixing this.16:48
jungleboyjrosmaita: Ok.  Sounds good.16:48
jungleboyjI can help you with that.16:48
*** baojg has joined #openstack-meeting16:48
jungleboyjThink we should do that in official documentation.  Not a wiki.16:48
*** baojg has quit IRC16:48
rosmaitaright, i think on the support matrix page (though we can discuss offline)16:49
jungleboyjOk.  Sounds good.16:49
potsDoes OpenStack have a marketing person who should be aware of this?  It seems like we should be reaching out to the vendors' marketing folks in case the right people didn't see Jay's e-mail.16:49
rosmaitapots: ++16:49
jungleboyjpots: Ah, good question.16:49
jungleboyjLet me follow up on that with the foundation.16:50
*** baojg has joined #openstack-meeting16:50
*** baojg has quit IRC16:50
*** ociuhandu has quit IRC16:50
*** baojg has joined #openstack-meeting16:51
*** igordc has quit IRC16:51
*** baojg has quit IRC16:51
jungleboyjWes.  I will send an e-mail to him today.16:51
jungleboyjAnd Erin too maybe.16:51
*** baojg has joined #openstack-meeting16:51
*** baojg has quit IRC16:51
smcginnisI'm a little concerned that we are flipping this where the community needs to be the ones watching and taking care of vendor drivers when it should be the other way around. If a vendor has customers that want to use their storage in OpenStack, it's on them to stay involved and make sure that is available.16:52
*** baojg has joined #openstack-meeting16:52
*** baojg has quit IRC16:52
e0nesmcginnis: +116:53
jungleboyjsmcginnis: I agree, but this is also at a point where I feel like this should be escalated.16:53
rosmaitasmcginnis: ordinarily, i would agree with you, but when half the drivers are noncompliant, i think we need to look on our side too16:53
*** baojg has joined #openstack-meeting16:53
jungleboyjI don't want Cinder to be cut in half and have the foundation come back and say WTF?16:53
*** baojg has quit IRC16:53
jungleboyjrosmaita: ++16:53
jungleboyjI mean, this makes me stick to my stomach.16:53
rosmaitasick, even16:54
*** baojg has joined #openstack-meeting16:54
jungleboyjYeah, that too.  Can't type while wretching16:54
*** baojg has quit IRC16:54
jungleboyjThis speaks to the health of the community.16:54
jungleboyjAnyway, I am going to reach out to the foundation and see what happens.16:54
smcginnisThese vendors are not participating and making sure OpenStack is healthy. I'm just fine seeing them go away (and lose markey opportunities) if they don't care about the project.16:54
*** baojg has joined #openstack-meeting16:54
*** baojg has quit IRC16:55
jungleboyjsmcginnis:  I know.16:55
*** baojg has joined #openstack-meeting16:55
*** baojg has quit IRC16:55
jungleboyjAnyway, I think we have a general direction here.  Can talk more at the mid-cycle.16:55
jungleboyjThere is one more topic on the schedule.16:56
jungleboyj#topic encryption effort update16:56
*** openstack changes topic to "encryption effort update (Meeting topic: cinder)"16:56
*** baojg has joined #openstack-meeting16:56
*** diablo_rojo__ has joined #openstack-meeting16:56
rosmaitaproposed changes to os-brick will be along the lines of what was proposed as an oslo library16:56
*** baojg has quit IRC16:56
rosmaitawith the Train os-brick release a month away, i'm pessimistic that they'll make train16:56
*** diablo_rojo has quit IRC16:56
rosmaitai was thinking it might be a good idea to request a feature branch for this work?16:56
rosmaitaor is that too much trouble?16:56
*** baojg has joined #openstack-meeting16:57
*** baojg has quit IRC16:57
rosmaitathat's all i have16:57
jungleboyjNot sure how hard that is to do.16:57
eharneyi think we usually get pretty far with a well-organized patch series16:57
smcginniseharney: ++16:57
jungleboyjeharney: ++16:57
eharneynot sure a feature branch would provide much benefit16:57
*** baojg has joined #openstack-meeting16:57
smcginnisFrom what I've heard, feature branches end up being mroe trouble than they're worth.16:58
*** baojg has quit IRC16:58
rosmaitaok, i will not suggest it, then16:58
smcginnisTheir easy to make, just need to add it to the deliverable file in the releases repo.16:58
*** baojg has joined #openstack-meeting16:58
*** baojg has quit IRC16:58
jungleboyjOk.  But if they are too much trouble lets not go that direction.16:59
jungleboyjOk.  So, I think that is it for this meeting.16:59
jungleboyjThanks for the discussion everyone.16:59
*** openstack changes topic to "OpenStack Meetings ||"16:59
openstackMeeting ended Wed Aug  7 16:59:55 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:59
openstackMinutes (text):
*** tosky has left #openstack-meeting17:00
*** rosmaita has left #openstack-meeting17:01
*** ociuhandu has joined #openstack-meeting17:01
*** woojay has left #openstack-meeting17:01
*** zhengMa has quit IRC17:01
*** e0ne has quit IRC17:06
*** igordc has joined #openstack-meeting17:10
*** jamesmcarthur has quit IRC17:12
*** artom has quit IRC17:13
*** brinzhang_ has joined #openstack-meeting17:16
*** altlogbot_0 has quit IRC17:17
*** davidsha has quit IRC17:18
*** brinzhang has quit IRC17:19
*** altlogbot_3 has joined #openstack-meeting17:23
*** jamesmcarthur has joined #openstack-meeting17:28
*** ociuhandu has quit IRC17:29
*** altlogbot_3 has quit IRC17:30
*** jamesmcarthur has quit IRC17:32
*** jamesmcarthur has joined #openstack-meeting17:34
*** ekcs has joined #openstack-meeting17:35
*** altlogbot_0 has joined #openstack-meeting17:35
*** mattw4 has quit IRC17:38
*** ociuhandu has joined #openstack-meeting17:39
*** jamesmcarthur has quit IRC17:39
*** ociuhandu has quit IRC17:43
*** jamesmcarthur has joined #openstack-meeting17:49
*** jamesmcarthur has quit IRC18:00
*** kopecmartin is now known as kopecmartin|off18:00
*** jamesmcarthur has joined #openstack-meeting18:01
*** Vadmacs has joined #openstack-meeting18:05
*** diablo_rojo__ is now known as diablo_rojo18:13
*** artom has joined #openstack-meeting18:17
*** yamahata has quit IRC18:27
*** iyamahat has quit IRC18:27
*** Vadmacs has quit IRC18:32
*** mattw4 has joined #openstack-meeting18:33
*** iyamahat has joined #openstack-meeting18:42
*** mattw4 has quit IRC18:44
*** mattw4 has joined #openstack-meeting18:44
*** isq_ has left #openstack-meeting18:46
*** e0ne has joined #openstack-meeting18:49
diablo_rojoHello StoryBoard meeting attendees! We will be skipping our weekly meeting this week. If you have any questions/comments, please join us in #storyboard!18:52
*** jamesmcarthur has quit IRC19:03
*** jamesmcarthur has joined #openstack-meeting19:16
*** jamesmcarthur has quit IRC19:35
*** lpetrut has joined #openstack-meeting19:35
*** jamesmcarthur has joined #openstack-meeting19:36
*** sfernand has quit IRC19:36
*** vesper11 has quit IRC19:37
*** e0ne has quit IRC19:46
*** markvoelker has quit IRC20:01
*** lpetrut has quit IRC20:01
*** markvoelker has joined #openstack-meeting20:03
*** whoami-rajat has quit IRC20:17
*** tdasilva has joined #openstack-meeting20:55
*** ralonsoh has quit IRC20:58
clayglet's go!!!21:00
timburke#startmeeting swift21:00
openstackMeeting started Wed Aug  7 21:00:12 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
timburkeclayg, so excited! you beat the meeting start!21:00
timburkeagenda's mostly a continuation of a lot of outstanding work21:01
timburke#topic shanghai21:01
*** openstack changes topic to "shanghai (Meeting topic: swift)"21:01
timburkejust a quick reminder that prices for the shanghai summit increase next week -- if you're going, you might want to buy now21:02
timburke(i'm not sure off-hand what the price will increase *to*, i just know it will increase)21:02
timburkethanks everybody for decalring whether you'll be there or not on the etherpad -- it should definitely help the foundation plan for attendance21:02
kota_and also timburke should respond to the TC how *Swift* PTG will be going?21:03
*** yamamoto has joined #openstack-meeting21:03
timburkeyup -- on my list for this week :-)21:03
timburke(attendance will probably be a little light, but then, we were expecting that)21:03
timburkeon to updates!21:04
timburke#topic py321:04
*** openstack changes topic to "py3 (Meeting topic: swift)"21:04
timburkei've been working on finishing up the py3 func tests recently21:04
timburkethere were a couple patches small enough that i didn't feel bad +A'ing myself21:04
timburkeaside from that, the main advance was in starting on the s3 tests21:04
timburkeand i saw that mattoliverau's been doing some review, so thanks for that!21:04
timburkei'm torn between wanting probe tests (because they'll exercise more of the system) or func tests (so we can start reducing the total number of gate jobs running)21:06
timburkebut we're getting there on both fronts!21:06
*** slaweq_ has quit IRC21:06
timburkeany questions on py3?21:06
timburke#topic lots of small files21:07
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:07
*** diablo_rojo has quit IRC21:07
timburkei'm guessing there hasn't been too much going on upstream here, with alecuyer still on vacation21:07
*** diablo_rojo has joined #openstack-meeting21:08
kota_timburke: true21:08
rlediseztimburke: yes21:08
kota_nothing except I bought the PTG ticket.21:08
*** yamamoto has quit IRC21:08
timburkebut we've been playing around with it at SwiftStack! we can get it to run, at least :-)21:08
timburkeis there anything else we should talk about for it? what are the next steps that we want to take?21:09
rledisezwow, that's something! somebody else make it running \o/21:09
timburkerledisez, always good when we can get past "works on my machine" :-)21:09
claygor "works in my public cloud" or w/e21:10
claygbut definately progress - it's gunna be a hoot21:10
*** slaweq_ has joined #openstack-meeting21:11
timburkehopefully i'll be able to give it more attention Real Soon Now21:11
timburkerledisez, as we find issues, where's a good place for us to collect them?21:12
clayggerrit?  with fixes?21:12
rledisezclayg: +121:12
claygobviously if we don't know *how* to fix it a failing test and a ping in IRC would be a good start... probably NOT lp bugs21:12
timburkeclayg, that's my usual way of dealing with issues, but sometimes people want something more trackable ;-P21:13
claygbut we could certainly do a etherpad or trello tracker if activity ramps up to the point that it's needed?21:13
timburkei was trying to remember if we had a trello board set up or anything21:13
kota_trello might be good place21:13
rledisezand definitively a ping, because we are some commits ahead for some bugfix (I think it's on alecuyer todolist to upstream them asap)21:13
timburkethanks kota_21:13
clayg^ oh, BOOM21:13
timburkelove it. i think there's one thing i oughta write up (or as clayg suggested, just go ahead and fix)21:14
timburke#topic sharding21:15
*** openstack changes topic to "sharding (Meeting topic: swift)"21:15
timburkei know we've got mattoliverau's patches21:15
mattoliverauI haven't done much extra here21:15
timburkei put up one or two others -- not exactly to do with autosharding, but certainly to do with having a completed feature21:15
mattoliverauI've been meaning to do some more testing of the existing patches, but got caught up with work :(21:15
mattoliverauI saw! thanks21:16
mattoliverauOne tracking updated and some py3 fixes right?21:16
timburkein particular, to stop hammering the root container quite so much21:16
mattoliverauyeah thank'll be a good thing :)21:17
timburkeoh, right -- the other thing wasn't a patch but a bug21:17
openstackLaunchpad bug 1839355 in OpenStack Object Storage (swift) "container-sharder should keep cleaving when there are no rows" [Undecided,New]21:17
*** slaweq_ has quit IRC21:17
mattoliverauoh, interesting21:17
timburkethough i'm not entirely sure on the right resolution there. working through mostly-empty DBs quickly would be good, but i wonder if we could save the hassle of creating (and replicating) all those shard dbs21:18
timburkesomethign to think about, anyway21:18
timburke#topic symlinks and versioning21:19
*** openstack changes topic to "symlinks and versioning (Meeting topic: swift)"21:19
claygthe realization for me was that it can take a long time to shard an empty container just because of the cardinality of shard ranges (the handoff knows about ranges because of replication, but it still takes many cycles to say "yup, noting in that range, nothing in that one either; good enough for this cycle - see you next time!" ZZZzzzzz21:19
timburkeyeah, that was about the point at which i wrote up the bug, shortly after doing the math to figure out how long it'll take to clear it21:20
clayghardlinks to SLOs won't always have the slo_etag and symlink_bytes bits correct in the container listings ->
timburkenot sure there's much we can do about that, though :-/21:21
claygwould love to have some feedback on how we put that in the docs without sounding stupid... "fixing it" seems not worth it considering the cruft and time it would take to essentially just reupload the manifest for them21:22
claygsometimes trying to make things better just makes things more complicated 🤷‍♂️21:22
timburkeon the plus side, neither will the SLO it's pointing at...21:22
claygtimburke: that's not a plus by any measure21:22
claygit's just bad and now the badness will accretes21:23
timburketrue enough. but we're *mostly* not making things actively worse?21:23
*** markvoelker has quit IRC21:23
*** raildo has quit IRC21:23
claygI mean I think that paragraph that explains how hardlinks worse *does* make it actively worse  - like the sphere of context where the problem forced users to have to think about it is bigger now21:24
clayg... but on the whole I think the change is still a net gain - obviously I want hardlinks!21:24
timburkei'm still hopeful that the total number of SLOs written *with* the metadata will be orders of magnitude larger than the total number written *without*, given enough time21:24
claygjust rubber hit the road and this is best we've come up with yet21:24
clayg... suggestions welcome 😁21:24
*** vesper11 has joined #openstack-meeting21:25
claygi'm rebasing symlink_versions now and mostly hoping i'm done with hardlinks (sans the amazing doco suggestions I'm going to get following this meeting)21:26
claygI am also finding it annoying that you have to dig out the manifest etag to make a hardlink21:26
timburkeclayg, is there anything the rest of us should be weighing in on? are you looking for consensus on what the listing should look like, say?21:26
claygI'd like to either add support python-swiftclient's `stat` command to do query-params (?multipart-manifest=get) OR make *LO's always return the an X-Manifest-Etag21:27
clayg... or both?  preferences?  opinions?21:27
claygI would like as many people as possible to read the docs on the hardlink patch so they understand the feature21:27
timburkex-manifest-etag's not a bad idea... we've already got it loaded in our head anyway...21:27
tdasilvaseems like the api change is better than the client change??21:28
claygif they want to play with `swift upload links -H 'content-length: 0' --object-name link.version -H 'x-symlink-target: test/big.version' -H 'x-symlink-target-etag: b89c395acda3886b823803b7dccb4765' - </dev/null` that's cool too, practically a review!21:28
claygbut just reading the docs and asking questions about the parts that seem weird would be SUPER helpful - maybe we missed something obvious21:29
*** jamesmcarthur has quit IRC21:29
claygbut even better - it adds documentation to the review - so later after we merge it and we're like "why didn't we do XYZ" we wrote that down somewhere21:29
timburkeclient change might be nice, too -- i could see some utility to being able to download the SLO manifest from the cli more easily21:29
*** jamesmcarthur has joined #openstack-meeting21:29
*** macz has joined #openstack-meeting21:29
claygtimburke: well there's also symlink=get - so yeah broad support in the cli for query params would be pretty sick21:30
tdasilvatimburke: agree, was just thinking in terms of one versus the other, but both sound even better :)21:31
claygbut it sounds like everyone likes x-manifest-etag too - so that's probably even cheaper21:31
timburkeclayg, do you want to add that as part of the hardlinks patch, or should i propose that separately?21:31
*** senrique_ has quit IRC21:32
timburkeor you could do it. maybe you'd prefer i spend my time reviewing ;-)21:32
claygno strong preference on my end - probably sufficiently orthogonal to warrent a seperate patch if for no other reason to keep patch count down21:32
claygwell, I'm not going to do anything until I finish the rebase on symlink_versions and I'm out of time today...21:32
timburkei'll see about knocking that out real quick21:33
claygso if while looking at hardlinks you were to "accidently" purpose a dependent patch that added x-manifest-etag I could +2 it in the morning ;)21:33
timburkeanything else for symlinks and versioning?21:33
*** jamesmcarthur has quit IRC21:34
claygnot at this time - other non swiftstack cores - please take 10m to read the docs and throw some comments on there21:34
clayghappy to take questions21:34
claygappreciate the feedback21:34
kota_will do21:35
kota_might take a time Friday on my time.21:35
timburkethanks kota_21:35
timburke#topic open discussion21:35
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:35
timburkeanything else we ought to discuss?21:35
timburkefwiw i've been playing with different ways to get a feel for what's going on in swift, and i feel like i've come up with a decent dashboard, at least to prep for this meeting21:37
kota_looks good21:38
*** markvoelker has joined #openstack-meeting21:38
timburkei might need to propose fewer patches though -- i'm not sure i like seeing my name that much :-/21:38
mattoliverautimburke: don't stop being you, your awesome!21:39
*** jamesmcarthur has joined #openstack-meeting21:40
timburkeall right, seems like there isn't much more to talk about right now -- let's call it a little early and let kota_ and mattoliverau get breakfast ;-)21:40
mattoliverauAnd just to jump back a bit. I'll start reading the hardlink docs today. I have some long meetings this morning... I'll need something to read :P21:41
mattoliverau\o/ breakfast time!21:41
timburkethanks mattoliverau!21:41
timburkethank you all for coming, and thank you for working on swift!21:41
*** openstack changes topic to "OpenStack Meetings ||"21:41
openstackMeeting ended Wed Aug  7 21:41:32 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:41
openstackMinutes (text):
*** zaitcev_ has joined #openstack-meeting21:43
*** zaitcev_ has left #openstack-meeting21:43
*** diablo_rojo has quit IRC21:46
*** markvoelker has quit IRC21:50
*** tidwellr has quit IRC22:02
*** diablo_rojo has joined #openstack-meeting22:05
*** ykatabam has joined #openstack-meeting22:08
*** diablo_rojo has quit IRC22:10
*** slaweq_ has joined #openstack-meeting22:11
*** rcernin has joined #openstack-meeting22:15
*** slaweq_ has quit IRC22:16
*** markvoelker has joined #openstack-meeting22:19
*** mriedem has quit IRC22:24
*** brinzhang has joined #openstack-meeting22:31
*** ykatabam has quit IRC22:33
*** brinzhang_ has quit IRC22:34
*** markvoelker has quit IRC22:38
*** jamesmcarthur has quit IRC22:41
*** jamesmcarthur has joined #openstack-meeting22:42
*** notmyname has quit IRC22:45
*** jamesmcarthur has quit IRC22:47
*** jamesmcarthur has joined #openstack-meeting22:50
*** markvoelker has joined #openstack-meeting22:53
*** macz has quit IRC22:53
*** jamesmcarthur has quit IRC22:57
*** tdasilva has quit IRC23:02
*** tdasilva has joined #openstack-meeting23:02
*** markvoelker has quit IRC23:08
*** yamamoto has joined #openstack-meeting23:08
*** slaweq_ has joined #openstack-meeting23:11
*** notmyname has joined #openstack-meeting23:15
*** slaweq_ has quit IRC23:16
*** jamesmcarthur has joined #openstack-meeting23:28
*** jamesmcarthur has quit IRC23:33
*** igordc has quit IRC23:35
*** markvoelker has joined #openstack-meeting23:38
*** markvoelker has quit IRC23:43
*** jamesmcarthur has joined #openstack-meeting23:43
*** jamesmcarthur has quit IRC23:46
*** tdasilva has quit IRC23:51
*** mattw4 has quit IRC23:51
*** tdasilva has joined #openstack-meeting23:52
*** tdasilva has quit IRC23:55
*** tdasilva has joined #openstack-meeting23:56

Generated by 2.15.3 by Marius Gedminas - find it at!