Friday, 2020-01-24

ormandjcoreycb: thanks so much and sorry for the slow response! much appreciated00:12
*** diablo_rojo has joined #openstack-swift00:32
*** manuvakery has joined #openstack-swift01:08
timburketdasilva, i'm starting to wonder if bulk needs to learn more about versions :-/01:11
timburkemainly because SLO needs to learn more about versions01:12
tdasilvamm..was hoping that it would be transparent to bulk01:15
tdasilvabut i'm assuming you looking somewhere around here: https://github.com/openstack/swift/blob/master/swift/common/middleware/slo.py#L1518 ?01:16
timburkeyeah01:16
timburkenew set of patches coming in a bit01:19
tdasilvak01:21
*** diablo_rojo has quit IRC02:03
*** openstackgerrit has joined #openstack-swift03:02
openstackgerritTim Burke proposed openstack/swift master: New Object Versioning mode  https://review.opendev.org/68238203:02
openstackgerritTim Burke proposed openstack/swift master: s3api: Implement object versioning API  https://review.opendev.org/67368203:02
timburkeunit tests are pretty busted, but i htink func tests should demonstrate where i want to go03:02
*** manuvakery has quit IRC03:18
*** psachin has joined #openstack-swift03:38
*** mkrai has joined #openstack-swift04:19
*** evrardjp has quit IRC05:34
*** evrardjp has joined #openstack-swift05:34
*** gyee has quit IRC05:47
openstackgerritTim Burke proposed openstack/swift stable/train: Allow bulk to fwd some headers at tar extraction  https://review.opendev.org/70410806:45
openstackgerritTim Burke proposed openstack/swift master: container-sync: Sync static links similar to how we sync SLOs  https://review.opendev.org/69813907:29
openstackgerritTim Burke proposed openstack/swift master: New Object Versioning mode  https://review.opendev.org/68238207:29
openstackgerritTim Burke proposed openstack/swift master: s3api: Implement object versioning API  https://review.opendev.org/67368207:29
*** mkrai has quit IRC07:44
*** rdejoux has joined #openstack-swift08:08
*** mkrai has joined #openstack-swift08:09
*** tkajinam has quit IRC08:20
*** ccamacho has joined #openstack-swift08:20
*** pawan-gupta has quit IRC08:32
*** tesseract has joined #openstack-swift08:34
*** rpittau|afk is now known as ironic08:51
*** ironic is now known as rpittau08:51
*** evrardjp has quit IRC08:54
*** pcaruana has joined #openstack-swift09:14
*** mkrai has quit IRC11:14
*** rpittau is now known as rpittau|bbl11:28
*** mkrai has joined #openstack-swift11:33
*** mkrai has quit IRC11:53
*** pawan-gupta has joined #openstack-swift11:54
*** pawan-gupta_ has joined #openstack-swift11:54
*** pawan-gupta_ has quit IRC12:25
*** pawan-gupta has quit IRC12:26
*** pawan-gupta has joined #openstack-swift12:26
*** mkrai has joined #openstack-swift12:27
mkraiHI, I am trying to find an openstack command to create an account in Swift, what is it?12:27
seongsoochomkrai:  Hi, Are you using keystone for swift auth?12:58
mkraiseongsoocho, Yes12:59
DHEthen you usually don't need to. there's a proxy-server.conf setting to auto-create an account.13:00
seongsoochomkrai:  OK, Then, If account_autocreate=true in your proxy-server.conf, the account will be create automatically.13:00
mkraiseongsoocho, Ok and what if I want to create a new account manually?13:00
mkraiseongsoocho, Is there any command for it?13:00
seongsoochomkrai:  Maybe You can use REST API for account.  The PUT http method.13:01
DHEis there a keystone "god admin" user rule?13:02
DHEbecause with keystone, you wouldn't have a means of accessing the account once created anyway unless you had such a user13:02
DHEI guess you could add some ACLs to some containers...13:02
*** rpittau|bbl is now known as rpittau13:40
*** mkrai has quit IRC13:56
*** jvisser has joined #openstack-swift13:57
*** seongsoocho has quit IRC14:49
*** seongsoocho has joined #openstack-swift14:49
*** psachin has quit IRC14:52
*** coreycb has quit IRC14:57
*** coreycb has joined #openstack-swift14:57
*** mkrai has joined #openstack-swift15:04
*** gregwork has quit IRC15:55
*** gyee has joined #openstack-swift16:14
*** diablo_rojo has joined #openstack-swift17:03
*** rdejoux has quit IRC17:10
claygtimburke: so did you already get into that unavailable versions container change?17:24
*** tesseract has quit IRC17:27
*** rpittau is now known as rpittau|afk17:35
openstackgerritClay Gerrard proposed openstack/swift master: New Object Versioning mode  https://review.opendev.org/68238217:35
timburkeclayg, yup. thanks for fixing up the pep8 fail!17:50
claygi have the container-sync change checked out - i was just reading your notes17:50
timburkeon https://review.opendev.org/#/c/698139/ -- that used to be the "Skip container-sync when versioning enabled" patch, but i pulled the versioning-specific stuff out to the versioning patch17:51
patchbotpatch 698139 - swift - container-sync: Sync static links similar to how w... - 16 patch sets17:51
claygI guess fixing syncing of the static links is helpful somewhat orthogonally to versioning17:51
claygand the "don't container-sync versions" requires the symlink header shuffling to work the way we want?17:52
timburkein large part i wanted to get https://review.opendev.org/#/c/682382/78/swift/common/middleware/container_sync.py to be really crisp -- there was a bunch of other middleware re-org going on :-/17:53
patchbotpatch 682382 - swift - New Object Versioning mode - 78 patch sets17:53
claygit was interesting that rledisez is saying he needs container-sync to work before he can make a move on versioning, since we kinda added the "don't be undefined with container-sync" knowing that it was an issue17:53
claygok, yeah that part looks great!17:53
timburkei think we also have been pretty clear that we *want* the features to play well together, we just don't want to block forward progress on it17:54
claygwell... I mean... to the extent we "want" container-sync to be a thing - my thinking on that rolls into bucket policies and pulling 1space out of crawling containers17:56
claygas we get more and more aws compatible having versioning work with "the stuff formally known as container-sync" starts to be interesting again17:57
claygmaybe there's a middle step that's just "teach container-sync how to versions"17:57
timburkeclayg, how do you feel about the 412 around https://review.opendev.org/#/c/682382/78/test/probe/test_object_versioning.py@204 ? i don't know what status i *want*, but i don't think that's it...18:05
patchbotpatch 682382 - swift - New Object Versioning mode - 78 patch sets18:05
claygany idea where the 412 is coming from?18:06
timburkei mean, the *hope* is that it's a transient server error and the versions container was just temporarily unavailable...18:06
timburkehttps://review.opendev.org/#/c/682382/78/swift/common/middleware/versioned_writes/object_versioning.py@38918:07
patchbotpatch 682382 - swift - New Object Versioning mode - 78 patch sets18:07
claygoh, so it's very specific we can return whatever we want18:07
timburkeyup. 412 was just carry-over from old-style versioning18:08
claygyeah any 400 series is fine, 404 is probably about as good as 412 - if we can throw a body/message in there that's unique eventually clients would grow robust to re-enabling versioning as needed18:08
claygwell, i guess _check_response_error is somewhat generic, maybe a 404 there isn't always a missing versions container18:10
timburkeyup -- see also https://review.opendev.org/#/c/682382/74/test/unit/common/middleware/test_object_versioning.py@181218:10
patchbotpatch 682382 - swift - New Object Versioning mode - 78 patch sets18:10
claygoic, yeah I think it'd be reasoable to change that - did it *used* to be a 404 before we special cased the 404 => 412 translation then?18:11
timburkei think it would've 500ed or 503ed, looking at the rest of _check_response_error18:13
claygyeah so that code must have come in before or along with the repair-version-link api - cause it wouldn't make sense to server error18:27
claygmayb we could pull the generic handling out and try to catch the 404's and return more context specific 400's18:28
claygi'm still on p 698139 right now tho - I think it needs more unitests and I'm not sure I understand all the header forwarding that's going on (like static links to slos)18:30
patchbothttps://review.opendev.org/#/c/698139/ - swift - container-sync: Sync static links similar to how w... - 16 patch sets18:30
*** mkrai has quit IRC18:30
*** psachin has joined #openstack-swift18:47
claygtimburke: i 100% agree with your take on http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012158.html are you gunna respond then?18:49
timburkeclayg, yeah, i can do that18:56
claygtimburke: awesome thanks for catching that one - i totally missed it!18:58
*** mvkr has quit IRC19:00
*** psachin has quit IRC19:23
*** theintern_ has joined #openstack-swift19:27
*** theintern_ has quit IRC19:38
claygso I would have swore `echo '' | swift upload test -H 'x-symlink-target: test/test' --object-name link -` was working 🤔19:41
claygbut I guess that's why @charz did p 69421119:42
patchbothttps://review.opendev.org/#/c/694211/ - python-swiftclient - Support uploading Swift symlinks without content. - 8 patch sets19:42
openstackgerritClay Gerrard proposed openstack/swift master: container-sync: Sync static links similar to how we sync SLOs  https://review.opendev.org/69813919:47
timburkeclayg, the echo adds a newline -- `< /dev/null swift upload test -H 'x-symlink-target: test/test' --object-name link -` should work, but it's definitely cumbersome20:09
timburkeclayg, you gonna restack the versioning patches, or should i?20:17
claygoh the newline!!! I've probably done echo -n or something20:17
timburkeyeah, that'd work, too20:18
claygI wasn't immediately working on a restack - it doesn't seem like these things are  going to land imminantly20:18
timburkebut really, we should probably just land the client patch -- i should look at that next20:18
claygi'm not sure about that interface on the client patch 😬20:18
timburkeyeah, maybe. gotta remember what it's like20:19
claygit's not very condusive to doing "batch" sorts of things like some of the other commands with their --prefix and the like20:19
claygI think @tdasilva may have suggested it, or maybe @charz came up with it on his own20:19
claygi can imagine migrating a replicated container <foo> to <foo>_ec and then wanting to symlink the lot of 'em20:20
claygI guess as long as the service api is reasonable it's less important that we support that use-case from the command line20:20
timburkeidk that there's a good way to make it more batch-y though -- reminds me that i once played around with writing a swiftclient with a mode that basically adds a DSL for scripting...20:22
clayganyway - on the versioning patches, it seems like things are setup to want us to land container-sync pre-req first20:22
claygso maybe wait for p 698139 to land and then rebase?20:22
patchbothttps://review.opendev.org/#/c/698139/ - swift - container-sync: Sync static links similar to how w... - 17 patch sets20:22
claygtimburke: ultimately I think `swift copy` and `swift link` should have "about" the same api 🤷20:22
timburkefair enough20:23
timburkeanyway, if we can agree on what we want the missing-archive status(es) to be, i think the swift side at least is ready to go20:23
claygok, well then before we respin maybe I can pull that down and play with some different responses that might work see what looks good20:25
timburkei think there's a good chance we'll want to distinguish between 404-archive-is-missing and 404-version-id-not-found fwiw20:26
claygtimburke: yes i agree20:32
claygI think some of the reason we ended up with 412 was wanting to distinguish between PUT-repair-versioning-symlink "container not found" vs "target version-id not found"20:33
claygI think "status" might be too course grained and we just need to say 400 "read the body for more info"20:33
claygbut, idk20:33
timburkeidk that what we have *makes* that distinction, tho :-/20:36
claygI think the 412 on "target version-id not found" is unambiguously NOT a 404 "container not found" 🤷20:51
claygbut I think ultimately there's to many things going through the _check_resp_error20:51
*** rdejoux has joined #openstack-swift21:28
timburkeclayg, so do we want sync_to in p 698139 or no? 'cause we've got some unit test failures to do with that...21:33
patchbothttps://review.opendev.org/#/c/698139/ - swift - container-sync: Sync static links similar to how w... - 17 patch sets21:33
*** diablo_rojo has quit IRC21:48
*** rdejoux has quit IRC21:51
*** rcernin has quit IRC22:34
openstackgerritMerged openstack/swift master: Allow Timestamp comparisons against out-of-range values  https://review.opendev.org/70295023:37
*** mvkr has joined #openstack-swift23:38

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