Tuesday, 2016-12-06

*** janonymous has joined #openstack-swift00:00
notmynameI've said it for a long time: so many problems would go away if we just prevented people from deleting data. ie "def DELETE(self, req): return HttpMethodNotImplemented(req)"00:04
mattoliveraunotmyname: totally agree, deleting sharding containers is something I haven't quite come to terms with, and that would make it _so_ much easier ;P00:10
notmynameI mean, really?! who needs to delete data? this is a *storage* system. not a *not storage* system. if you want to delete your data, just store it on a ram-disk00:11
notmyname;-)00:11
mattoliveraulol00:13
zaitcevI used to share an office with a senior engineer at Sun who worked on redundant arrays of ramdisks00:16
zaitcevBecause, he said, "our customers don't lose power, and if they do, they have datacenters on all continents"00:16
zaitcevIt was before the SSD revolution, so he may be forgiven, I think, for trying to find the benefits that we take for granted today.00:17
*** tqtran has quit IRC00:25
*** catintheroof has quit IRC00:25
*** clu_ has quit IRC00:30
claygtdasilva: do you have the change that fixes GET to do better with 404 timestamps00:31
claygtdasilva: nm, found it - and added a refernce to lp bug #1503161 - since it seems related00:33
openstackLaunchpad bug 1503161 in OpenStack Object Storage (swift) "[Re-open in 2015 Oct] DELETE operation not write affinity aware" [Undecided,New] https://launchpad.net/bugs/150316100:33
*** tqtran has joined #openstack-swift00:43
*** mingyu has joined #openstack-swift00:50
*** nikivi has quit IRC00:54
*** mingyu has quit IRC00:55
*** diogogmt has quit IRC00:55
*** sams-gleb has joined #openstack-swift00:58
kota_good morning01:00
*** rcernin has quit IRC01:01
timburkeclayg: related to that bug... when do we send the 404 if the *container* doesn't exist? when get_container_info fails on the proxy? what happens when the object server accepts a write, but the container's been deleted by the time the updater runs?01:01
*** sams-gleb has quit IRC01:03
claygtimburke: container db's will accept object updates for deleted objects - if it's a tombstone ... that's fine of course01:14
claygtimburke: I *do* think somewhere the proxy might reject a PUT if a contaier "doesn't exist" based on get_container_info - not sure if that effects delete01:15
claygtimburke: i'd ahve to trace the code... waht are you thinking?01:15
timburkeclayg: *somewhere* we return a 404 if you try to delete an object in a container that doesn't exist, and that needs to be treated differently than getting back a 404 because the object didn't exist, but the container does01:18
*** a1|away has quit IRC01:18
*** a1|away has joined #openstack-swift01:18
kota_clayg: could you have a time to talk about patch 405450?01:19
patchbothttps://review.openstack.org/#/c/405450/ - swift - Fixups for ghost listing fix01:19
timburkeclayg: as far as i'm concerned, 204 + 404 where container actually exists + 503 = 204, timestamps be damned01:19
timburkewhereas 204 + 404 where *container* doesn't exist + 503 depends on the timestamps01:19
claygkota_: sure01:20
claygtimburke: I think a 204 that is tombstoneing a t1.data and 404ing a t2.tombstone can return 404 - unless the responses indicate some other t3.data is also being tombstoned?01:21
timburkebut if the proxy's already decided "container exists" before sending object-server requests, that simplifies things considerably01:21
claygtimburke: yeah, IIRC in PUT that happens near the top of the PUT method in proxy.controller.obj01:21
kota_clayg: exactly, the updater change for error line could make a huge lines and updater will continue to dump it for all requests.01:21
kota_hmm...01:21
kota_not conclude my thought yet.01:22
claygkota_: I think debug is fine for both - we didn't have an issue like "this was broken and we didn't know it"01:22
kota_OTOH, object-server handles it as an error line, https://github.com/openstack/swift/blob/master/swift/obj/server.py#L251-L256, yes, it's only once when the request incomming.01:22
timburkeclayg: i think mainly i'm irked that https://review.openstack.org/#/c/368264/ had to be a thing and i'm looking for ways to sneak that behavior into swift :P01:23
patchbotpatch 368264 - swift3 - Fix the deletion of non-existent keys01:23
kota_clayg: since I reviewed that, I've been realizing why we don't make self.logger.increment('async_pending') if we keep the pending file when the request failed?01:24
claygtimburke: ok, and so currently swift3 just alwasy returns 204?01:24
kota_so it might be helpful rather than log line 'we hvae something failed and we keep the async pending for that'01:24
kota_the failure seems to be incremented thought.01:24
kota_https://github.com/openstack/swift/blob/master/swift/obj/updater.py#L24701:25
claygtimburke: maybe just add a new header to mark the request as "404'd because no container" to all of the places we do that like https://github.com/openstack/swift/blob/5084a63770673c588b3fe832a9c9e52be7d82173/swift/proxy/controllers/obj.py#L71301:26
timburkeclayg: that's not *merged*; currently we 404 like swift. but it's just bit multiple customers in different contexts01:26
timburkelike https://bugs.launchpad.net/swift3/+bug/163851201:27
openstackLaunchpad bug 1638512 in Swift3 "Swift3 is not write affinity aware, that causes multipart upload failed in `404 (NoSuchKey)`" [Undecided,New]01:27
claygtimburke: are you trying to get me to review that s3 change?  I read the commit message and I can see how it would be difficult to translate that behavior to the swift api if it's important01:27
timburkeclayg: not really. just pointing out that users may have a different mental model for what those status codes mean -- and i'm partial toward the "if we write a tombstone, that's successful" model01:29
claygtimburke: the failed upload bug looks terrible - not obvious why changing the response code of DELETE requests for objects would effect the behavior when creating a multi-part object via swift301:29
claygtimburke: the statement "I'm partial toward [an api that behaves different than swift's does]" - it's not an immediately actionable statement to me01:31
claygkota_: one compromise that I liked was to make L247 be a warning and make the new one (the one at error) a debug01:31
*** Guest36 has joined #openstack-swift01:32
claygkota_: I don't think it's *quite* as good as both being debug - but I think the new one being error is actively bad - so i'm mostly concerened with that being changed01:32
timburkeclayg: we persist an upload identifier that gets cleaned up upon completion. i could just as easily have the handling around *just that* tolerate 404s explicitly, but my users expect it *all* the time, so...01:32
timburke(honestly, it was a bit of a drive-by; i didn't even realize i was fixing that case)01:32
timburkeclayg: how's this for actionable: "swift should always 204 when writing a .ts"01:33
claygtimburke: ok so I answered your question by showing you where the object controller currently deals with the container missing case - if you file a bug that says and enduser (or middleware) should be able to differentiate I think adding a header is the most obvious backwards compatible path forward01:33
timburkeonly that'll never merge, because someone somewhere might be depending the old behavior01:34
claygtimburke: i'm not sure if you mean should abstractly - like if we had a time machine - or the API should change - because i don't know how to make that backwards compatible01:34
*** m_kazuhiro has joined #openstack-swift01:34
claygtimburke: ok - so abstractly - coolio - yeah fucking swift api sucks!01:34
timburkeit's not actually that hard to differentiate in middleware -- peak at the env cache, see whether the container exists01:34
claygtimburke: good thinking!  less sure how robust that will be to future maintance as oppsed to a header - but WFM if it works for you!01:35
claygalso obviously no one is trying to keep the information from the user - I think an X-Container-Does-Not-Exist header or somethign would be fine01:35
claygi remember the first time I tried to PUT and got a 404 I was confused - not sure if a header would have helped01:36
timburkeobject-server.conf config value? dont_404_deletes_dumb_dumb = True, only it defaults to False?01:36
claygtimburke: no01:36
timburke:P01:36
claygtimburke: we should not encourage deployments to have non-conforming api's01:36
kota_clayg: k, let me think, still thinking better idea01:38
timburkeclayg: so... golang proxy-server! middleware be damned!01:41
claygtimburke: i... think... you saying something current in-tree official middleware that is "optional" being... hypocritical to my earlier statement?01:43
claygtimburke: i feel like we've got off track from how swift should handle DELETE of tombstone :D01:43
notmynameclayg: timburke: are we talking about DELETEs and 404 vs 204?01:45
timburkenotmyname: i've gotten us a bit... sidetracked :P01:45
claygnotmyname: yes current thinking is to rewrite the proxy in golang and not allow any custom middleware01:45
notmynamelol01:45
timburketotally solves the DELETE problem01:46
notmynameI kinda like the always 204 option. if it writes a .ts, make it return 204 (but being smarter with the returned timestamps is always an option)01:46
notmynametimburke: so would disabline DELETE altogether01:46
notmynamedisabline?01:46
claygit's like the southern bell version of disabling01:47
claygdis-ab-line01:47
notmynameyeah, that's how in went in my head01:47
notmynameanyway, "return 204 if .ts is written" seems reasonable. and not a breaking change to the api01:48
claygmy heaves i don't know why would eAvear want to go dis-ab-line DELETE altogether01:48
notmynamefamily just got home. I'm afk for a bit01:50
timburkenotmyname: no, that'd totally break the api -- DELETE to an object that doesn't exist used to 404, then it would 20401:54
*** Guest36 has quit IRC01:54
kota_oh... wait?02:07
kota_why object_update returns HTTP_INTERNAL_SEVER_ERROR for the first item in the return tupple in failure case?02:07
kota_that should be true/false02:08
kota_:/02:08
claygkota_: you can't fix *all* the bugs in one patch!  ;)02:10
kota_clayg: sure02:11
claygkota_: i'm worried you're thinking too hard on this issue!  save your braincells - we have many issues unfortuantely :'(02:16
*** klrmn has quit IRC02:17
claygkota_: e.g. is there anything I can do to help with isa-l-rs-cauchy?02:17
kota_clayg: yeah, i can add +2 for that soon but I'm in pazzling we could may remove the debug line, anyway?02:17
kota_clayg: could you wait a bit?02:17
claygkota_: of course!02:18
*** isotope has joined #openstack-swift02:24
*** isotope has quit IRC02:29
kota_clayg: not yet tested just dump my thought into code, https://gist.github.com/bloodeagle40234/2d747f44909d3d3f153a27a70afb7a3902:35
kota_ok, i got an error, TypeError: 'set' object does not support indexing02:37
kota_need to fix a bit02:37
kota_fixed and url link is same, https://gist.github.com/bloodeagle40234/2d747f44909d3d3f153a27a70afb7a3902:39
kota_er, maybe we can keep debug log line in the failure case02:41
kota_but, I need to think more for the case the udater process in the second time (with attempts to less than whole replicas)02:42
*** winggundamth has quit IRC02:48
*** winggundamth has joined #openstack-swift02:49
*** bkopilov has quit IRC03:13
*** dmorita has quit IRC03:16
*** briancline has joined #openstack-swift03:29
*** klrmn has joined #openstack-swift03:31
openstackgerritTim Burke proposed openstack/pyeclib: Fix checksum memory leak  https://review.openstack.org/40730203:48
*** links has joined #openstack-swift03:52
*** arch-nemesis has quit IRC03:53
notmynametimburke: no, currently you DELETE and get a 404 sometimes (depending on things not in your control)--but yes for unknown objects you get a 404--yet we always actually do something for you. I'm proposing that telling the client that we wrote the tombstone isn't a horrible idea03:56
notmynameno, I'm not arguing that the result on a delete to a 404 isn't different. just that returning a 204 is more consistent and more accurate. and that since currently we require that clients handle both 204 and 404 for reasons beyond their understanding--which we've seen both with customers and the community--simply returning a 204 is reasonable and very low risk04:02
*** tqtran has quit IRC04:03
*** psachin has joined #openstack-swift04:03
*** m_kazuhiro_ has joined #openstack-swift04:07
*** m_kazuhiro has quit IRC04:10
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873604:37
*** bkopilov has joined #openstack-swift04:41
*** mmuffinman has joined #openstack-swift04:50
*** klrmn has quit IRC04:55
*** dmorita has joined #openstack-swift05:16
*** dmorita has quit IRC05:21
*** mingyu has joined #openstack-swift05:21
*** mingyu has quit IRC05:26
*** sanchitmalhotra has joined #openstack-swift05:31
*** sanchitmalhotra1 has joined #openstack-swift05:43
*** sanchitmalhotra has quit IRC05:44
*** sanchitmalhotra1 is now known as sanchitmalhotra05:44
*** ppai has joined #openstack-swift05:51
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: ISA-L Cauchy support  https://review.openstack.org/39326305:59
*** tqtran has joined #openstack-swift06:03
*** tqtran has quit IRC06:07
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: DON'T MERGE: just checking if the test failed  https://review.openstack.org/40733306:09
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: Fix checksum memory leak  https://review.openstack.org/40730206:12
*** tovin07 has joined #openstack-swift06:25
*** ppai has quit IRC06:31
*** sams-gleb has joined #openstack-swift06:33
*** sams-gleb has quit IRC06:33
*** sams-gleb has joined #openstack-swift06:34
*** rcernin has joined #openstack-swift06:34
*** sams-gleb has quit IRC06:38
*** sanchitmalhotra has quit IRC06:39
*** ppai has joined #openstack-swift06:48
*** SkyRocknRoll has joined #openstack-swift06:53
*** SkyRocknRoll has quit IRC06:58
*** ChubYann has quit IRC07:06
*** m_kazuhiro_ has quit IRC07:09
*** SkyRocknRoll has joined #openstack-swift07:10
*** ppai has quit IRC07:11
*** rcernin has quit IRC07:12
*** ppai has joined #openstack-swift07:24
*** bikmak has quit IRC07:25
*** Guest66666 has quit IRC07:27
*** Guest66666 has joined #openstack-swift07:29
*** rcernin has joined #openstack-swift07:34
*** Jeffrey4l has quit IRC07:36
*** ppai has quit IRC07:39
*** hseipp has joined #openstack-swift07:41
*** pcaruana has joined #openstack-swift07:42
*** Jeffrey4l has joined #openstack-swift07:52
*** d0ugal has joined #openstack-swift07:57
*** d0ugal has quit IRC07:57
*** d0ugal has joined #openstack-swift07:57
*** mvk has quit IRC08:01
*** sanchitmalhotra has joined #openstack-swift08:16
*** silor has joined #openstack-swift08:26
*** silor1 has joined #openstack-swift08:31
*** silor has quit IRC08:32
*** silor1 is now known as silor08:32
*** mvk has joined #openstack-swift08:33
*** geaaru has joined #openstack-swift08:48
*** Guest36 has joined #openstack-swift08:50
*** si1ver has quit IRC08:57
*** si1ver has joined #openstack-swift08:58
*** Guest36 has quit IRC08:59
*** Guest36 has joined #openstack-swift09:01
*** dmorita has joined #openstack-swift09:01
*** oshritf has joined #openstack-swift09:01
*** psachin has quit IRC09:04
*** dmorita has quit IRC09:06
*** asettle has joined #openstack-swift09:09
*** psachin has joined #openstack-swift09:17
*** hseipp has quit IRC09:21
*** hseipp has joined #openstack-swift09:28
*** daemontool has joined #openstack-swift09:35
*** tqtran has joined #openstack-swift10:06
*** ppai has joined #openstack-swift10:07
*** abalfour has quit IRC10:08
*** abalfour has joined #openstack-swift10:08
*** Trpger has joined #openstack-swift10:09
*** tovin07 has quit IRC10:09
*** tqtran has quit IRC10:10
*** Trpger has left #openstack-swift10:12
*** daemontool has quit IRC10:23
*** SkyRocknRoll has quit IRC10:48
*** Guest36 has quit IRC10:51
*** dfflanders has quit IRC10:53
openstackgerritSachin Patil proposed openstack/swift: get_part_nodes should raise error on invalid part  https://review.openstack.org/40252211:04
*** daemontool has joined #openstack-swift11:11
openstackgerritGábor Antal proposed openstack/swift: Use more specific asserts in test/unit/obj tests  https://review.openstack.org/34283011:32
*** vint_bra has joined #openstack-swift11:41
*** jamielennox is now known as jamielennox|away11:44
*** cdelatte has joined #openstack-swift11:46
*** ppai has quit IRC12:00
*** ppai has joined #openstack-swift12:09
*** tingo has joined #openstack-swift12:13
*** tingo has quit IRC12:17
*** acoles_ is now known as acoles12:18
*** kei_yama has quit IRC12:19
*** bkopilov has quit IRC12:39
*** cdelatte has quit IRC12:51
*** cdelatte has joined #openstack-swift12:58
*** xionchen_ has joined #openstack-swift13:19
*** peterlisak has quit IRC13:42
*** onovy has quit IRC13:42
*** _JZ_ has joined #openstack-swift13:43
*** catintheroof has joined #openstack-swift13:43
*** ppai has quit IRC13:52
*** daemontool has quit IRC14:04
*** joeljwright has joined #openstack-swift14:11
*** ChanServ sets mode: +v joeljwright14:11
*** StraubTW has joined #openstack-swift14:18
*** StraubTW has quit IRC14:21
*** StraubTW has joined #openstack-swift14:22
*** links has quit IRC14:40
openstackgerritMerged openstack/swift-specs: Show team and repo badges on README  https://review.openstack.org/40285914:50
*** peterlisak has joined #openstack-swift14:52
*** onovy has joined #openstack-swift14:52
*** StraubTW has quit IRC14:54
*** psachin has quit IRC15:00
*** cdelatte has quit IRC15:00
*** siva_krish has joined #openstack-swift15:00
*** sams-gleb has joined #openstack-swift15:02
*** cdelatte has joined #openstack-swift15:03
*** StraubTW has joined #openstack-swift15:07
*** tqtran has joined #openstack-swift15:10
*** tqtran has quit IRC15:15
*** tuan_luong has joined #openstack-swift15:19
*** StraubTW has quit IRC15:20
*** xionchen_ has quit IRC15:24
*** StraubTW has joined #openstack-swift15:36
*** isotope has joined #openstack-swift15:41
*** StraubTW has quit IRC15:46
*** jmccarthy has joined #openstack-swift15:46
jmccarthyHiya, quick I hope question about storage network and swift, the docs seem to suggest bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS that I've found so far, how do I enable/configure portions to function in the Storage Network ?15:49
jmccarthyOh - guess I should have kept reading :)15:51
jmccarthySet the bind_ip configuration option to STORAGE_LOCAL_NET_IP.15:51
jmccarthyEdit the account-server.conf, container-server.conf and object-server.conf files in the /etc/swift directory. In each file, update the [DEFAULT] section as follows:15:51
jmccarthy[DEFAULT]15:51
jmccarthybind_ip = STORAGE_LOCAL_NET_IP15:51
*** isotope has quit IRC15:53
notmynamegood morning16:02
jmccarthyMorning !16:05
jmccarthyI was just asking this a minute ago :) Is it really only a case of the bind_ip setting for account-server.conf, container-server.conf and object-server.conf to have swift use storage network 'in the back' ?16:06
notmynamejmccarthy: I'm not 100% clear on your question, but I think the answer is yes16:07
jmccarthyI'm sure I'm not asking it clearly :) Hehe I mean for things that don't *have to be on the public network (like calls to api/mgmt interface) maybe stuff like replicator auditor and internal things to swift, so they can do that stuff on storage network (not public)16:09
notmynameyep16:10
jmccarthyOk cool I'm going to try that out :) Thanks !16:10
notmynamethe bind_ip in the proxy conf is what you put in your load balancer and your clients talk to. the bind_ip in the account, container, object (ACO) conf should match what's in the respective ring files16:11
jmccarthyOh whoa ok great point re:ring files - didn't think of that !16:11
notmynamethe proxy uses the ring to find the right IP/port and then talks to that server16:11
notmynamebut here's the extra complexity...16:11
notmynameyou can add a separate replication ip/port in the ring too16:11
notmynameto start with, you might not need that16:12
notmynameit's there so you can have a separate network for the internal background processes that won't interfere with client-originated requests16:12
notmynameit's normally used by having a separate object server config that's listening on the replication ip/port16:13
notmynameie you'd have 2 object servers running on a box: one for client traffic and one for replication/background/internal traffic16:13
notmynamemake sense?16:13
*** catinthe_ has joined #openstack-swift16:14
jmccarthyDefo that's the sort of thing I'm thinking about - ok so if I make the bind_ip config changes, and update rings to point to ips on that storage network, I'm up to that point :) With only those changes, where would replication happen ?16:14
jmccarthyIn the storage network ?16:15
*** bkopilov has joined #openstack-swift16:16
notmynameyes. if you don't designate a separate replication network, both client-originated traffic (ie via the proxy server) and internal-only traffic (eg from replication) will be on the same interface16:16
*** daemontool has joined #openstack-swift16:16
*** catintheroof has quit IRC16:16
jmccarthyHmm ok I lost it :)16:16
notmynameFWIW, https://www.swiftstack.com/docs/admin/hardware.html#example-configuration has some words and pictures that may help. note that those are docs related to the swiftstack product, not just the open-source swift storage engine (and my employer)16:17
jmccarthyI have proxy server on mgmt net, and with reconfigure, no other bind_ip on that net lets say - the others are on storage net now16:17
*** rcernin has quit IRC16:17
jmccarthyThe client traffic is only on mgmt net, and proxy server talks to rest on storage right ?16:17
*** catinthe_ has quit IRC16:18
notmynameyeah, so the proxy server has 2 interfaces, right? one for the external-facing and one for the cluster-facing16:19
*** pcaruana has quit IRC16:19
jmccarthyproxy has 2 yep, so I mean in this case, no api traffic happens on storage net if I'm thinking right, then where does replication happen ? (i.e. I have not setup a third network for this)16:20
notmynameyou've got a public and an internet network? then the replication traffic would be on the internal network16:20
jmccarthyI was thinking it would happen on the storage net16:21
notmynameah! http://learn.swiftstack.com/rs/034-CBF-009/images/Cisco-and-SwiftStack-Reference-Design-Document.pdf has a better picture on page 1216:21
jmccarthyOk yes the internal one I'm calling the storage net :)16:21
notmynameright16:21
notmyname:-)16:21
*** zul has quit IRC16:22
notmynamejmccarthy: I need to step away for a few minutes16:22
jmccarthy:) It's cool - that helped a lot16:23
jmccarthyThanks !16:23
*** oshritf has quit IRC16:23
*** zul has joined #openstack-swift16:25
*** mvk has quit IRC16:26
*** tuan_luong has quit IRC16:34
*** chsc has joined #openstack-swift16:36
*** chsc has quit IRC16:36
*** chsc has joined #openstack-swift16:36
*** chsc has quit IRC16:50
*** vinsh has joined #openstack-swift16:54
* notmyname back16:58
* notmyname back17:00
*** catintheroof has joined #openstack-swift17:03
*** catintheroof has quit IRC17:03
*** catintheroof has joined #openstack-swift17:04
*** tqtran has joined #openstack-swift17:12
*** geaaru has quit IRC17:18
*** hseipp has quit IRC17:22
*** rcernin has joined #openstack-swift17:26
*** diogogmt has joined #openstack-swift17:32
*** chsc has joined #openstack-swift17:34
*** chsc has joined #openstack-swift17:34
*** asettle has quit IRC17:42
*** dmorita has joined #openstack-swift17:43
*** bkopilov has quit IRC17:51
*** chsc has quit IRC17:53
*** cbartz has left #openstack-swift17:56
*** bkopilov has joined #openstack-swift17:58
*** mvk has joined #openstack-swift18:00
*** isotope has joined #openstack-swift18:00
*** arch-nemesis has joined #openstack-swift18:00
openstackgerritThiago da Silva proposed openstack/swift: add object_post_as_copy to saio.  https://review.openstack.org/40762718:02
*** siva_krish has quit IRC18:04
*** siva_krish has joined #openstack-swift18:06
*** joeljwright has quit IRC18:08
tdasilvajrichli: hello, are you around?18:13
*** acoles is now known as acoles_18:16
*** dmorita has quit IRC18:30
*** dmorita has joined #openstack-swift18:31
*** asettle has joined #openstack-swift18:35
jmccarthyOh is this current ?18:37
jmccarthyNote18:37
jmccarthySyntax of adding device has been changed: R<ip_replication>:<port_replication> was added between z<zone>-<ip>:<port> and /<device_name>_<meta> <weight>. Added devices will use <ip_replication> and <port_replication> for replication activities.18:37
jmccarthyLike:18:37
jmccarthy-ring-builder object.builder add z1-127.0.0.1:6010R127.0.0.1:6050/sdb1 118:37
jmccarthy(from http://docs.openstack.org/developer/swift/replication_network.html)18:37
jrichlitdasilva: hello18:49
jrichlitdasilva: I am consuming mass quantities.  We are having something we call our "progressive lunch" day at work.  There is food at each floor of the building.18:51
tdasilvajrichli: hehe, no worries, after pinging you I imagined you would be at lunch18:51
tdasilvajrichli: was just pinging about symlinks, left a note for you at the patch18:51
jrichligreat, thanks18:51
jrichlitdasilva: are we wanting to allow a symlink's target header to be updated?  i guess not, right?18:53
tdasilvacorrect, at some point (i think in san antonio) we decide to allow users to only create symlinks with a PUT request18:54
jrichliah, ok18:54
*** asettle has quit IRC18:54
tdasilvajrichli: that's at least how I remember, but I couldn't find a place where we wrote that down :(18:54
*** asettle has joined #openstack-swift18:55
jrichlitdasilva: the suggestion you mentioned sounds good.  I am not thinking really deeply about symlinks at the moment, though, so I will mull it over later tonight :-)18:55
tdasilvajrichli: cool, no worries, thanks! :)18:56
*** asettle has quit IRC18:59
*** dmorita has quit IRC19:00
*** klrmn has joined #openstack-swift19:01
*** dmorita has joined #openstack-swift19:02
*** arch-nemesis has quit IRC19:07
*** jamielennox|away is now known as jamielennox19:07
*** silor has quit IRC19:13
*** catinthe_ has joined #openstack-swift19:14
*** bapalm_ has quit IRC19:14
*** cnf has quit IRC19:15
*** catintheroof has quit IRC19:16
*** bapalm has joined #openstack-swift19:18
*** cnf has joined #openstack-swift19:27
*** cnf has quit IRC19:29
*** cnfer has joined #openstack-swift19:29
*** jmccarthy has quit IRC19:33
*** mmotiani has quit IRC19:33
*** ChubYann has joined #openstack-swift19:33
*** jmccarthy has joined #openstack-swift19:34
*** cnfer has quit IRC19:34
*** a1|away has quit IRC19:35
*** a1|away has joined #openstack-swift19:35
*** cnf has joined #openstack-swift19:35
*** mmotiani has joined #openstack-swift19:36
*** jmccarthy has left #openstack-swift19:38
*** Jeffrey4l has quit IRC19:42
*** Jeffrey4l has joined #openstack-swift19:42
*** cnf has quit IRC19:43
*** siva_krish has quit IRC19:48
*** cnf has joined #openstack-swift19:49
*** dmorita has quit IRC19:58
*** dmorita has joined #openstack-swift19:59
*** catintheroof has joined #openstack-swift20:02
*** catinthe_ has quit IRC20:04
*** siva_krish has joined #openstack-swift20:06
*** chsc has joined #openstack-swift20:07
*** chsc has joined #openstack-swift20:07
*** isotope has quit IRC20:11
*** isotope has joined #openstack-swift20:11
*** asettle has joined #openstack-swift20:11
claygntata: do changes like patch 407627 get picked up by your https://github.com/ntata/swift-setup-scripts project?20:13
patchbothttps://review.openstack.org/#/c/407627/ - swift - add object_post_as_copy to saio.20:13
*** asettle has quit IRC20:14
claygkota_: I agree with everything you said about patch #40545020:35
patchbothttps://review.openstack.org/#/c/405450/ - swift - Fixups for ghost listing fix20:35
claygthanks!20:35
*** nikivi has joined #openstack-swift20:36
*** isotope has quit IRC20:38
claygkota_: timburke: tdasilva: what's the status on patch #393263?  That'd be pretty good to be able to do isa-l with parity > 4 again right!?  Reviews of pyeclib & liberasurecode are *easy and fun* using vagrant-swift-all-in-one's new "reec" sciprt!?20:39
patchbothttps://review.openstack.org/#/c/393263/ - liberasurecode - ISA-L Cauchy support20:39
*** nikivi has quit IRC20:40
*** nikivi has joined #openstack-swift20:40
*** asettle has joined #openstack-swift20:41
claygoh... acctually you *still* have to get isa-l installed some home - I cloned git@github.com:01org/isa-l.git and followed the readme to get it `make install`ed20:43
*** daemontool_ has joined #openstack-swift20:44
*** isotope has joined #openstack-swift20:45
*** daemontool has quit IRC20:47
*** diogogmt has quit IRC20:48
*** siva_krish has quit IRC20:51
*** david-lyle has quit IRC20:55
*** karenc_ is now known as karenc21:02
openstackgerritClay Gerrard proposed openstack/swift: Split up tests for Concurrent Gets  https://review.openstack.org/28658921:04
*** catintheroof has quit IRC21:06
*** cdelatte has quit IRC21:18
claygeasy review of the day that could help a new contrib get some code landed - patch #40601221:29
patchbothttps://review.openstack.org/#/c/406012/ - swift - Fix swift-get-nodes arg parsing for missing ring21:29
clayg... assuming you agree with me that swift-get-nodes on master sucks compared to this change21:29
*** Jeffrey4l has quit IRC21:32
*** Jeffrey4l has joined #openstack-swift21:34
*** nikivi has quit IRC21:39
*** nikivi has joined #openstack-swift21:40
mattoliveraumorning21:40
*** arch-nemesis has joined #openstack-swift21:42
*** chlong has joined #openstack-swift21:43
openstackgerritThiago da Silva proposed openstack/swift: Symlink implementation.  https://review.openstack.org/23216221:45
*** nikivi has quit IRC21:45
*** daemontool_ has quit IRC21:55
*** daemontool_ has joined #openstack-swift21:55
*** sams-gleb has quit IRC22:04
*** sams-gleb has joined #openstack-swift22:04
*** chlong has quit IRC22:06
*** chlong has joined #openstack-swift22:07
*** sams-gleb has quit IRC22:09
ntataclayg, yes it does! My saio makes use of the master's copy of doc/saio/swift/proxy-server.conf :)22:10
jrichlintata: great!  clayg: good thought.  I will try to keep the scripts in mind going forward22:11
*** chlong has quit IRC22:12
tdasilvantata: so is that patch bad for your script? sorry, i think i'm missing something...22:15
jrichlitdasilva: I was saying that I want to be sure to think of those scripts.  but in this case, I think we are fine since she copies the file you are changing, so the changes will be integrated.22:17
jrichliof course, ntata is the one who knows!  I just wanted to be clear on what my statement meant22:18
tdasilvajrichli: cool, hopefully it is not breaking anything22:18
*** vint_bra has quit IRC22:22
ntatajrichli, thank you for helping me out :). tdasilva, you're not disturbing my scripts at all. Even if it does, I'll make sure to tweak them to work around your solution22:22
*** david-lyle has joined #openstack-swift22:24
*** daemontool_ has quit IRC22:33
*** daemontool_ has joined #openstack-swift22:34
tdasilvantata: :)22:35
*** asettle has quit IRC22:40
*** david-lyle has quit IRC22:41
*** isotope has quit IRC22:49
*** asettle has joined #openstack-swift23:00
*** asettle has quit IRC23:01
*** rcernin has quit IRC23:02
*** jamielennox is now known as jamielennox|away23:05
*** jamielennox|away is now known as jamielennox23:06
*** isotope has joined #openstack-swift23:07
*** isotope has quit IRC23:16
openstackgerritMerged openstack/swift: add object_post_as_copy to saio.  https://review.openstack.org/40762723:22
notmynamehello, world23:25
*** chsc has quit IRC23:27
mattoliveraunotmyname: o/23:28
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:35
*** kei_yama has joined #openstack-swift23:36
*** vinsh has quit IRC23:46
*** catintheroof has joined #openstack-swift23:58

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