Thursday, 2019-10-03

*** gyee has quit IRC00:06
*** ianychoi has quit IRC00:12
*** ianychoi has joined #openstack-swift00:15
openstackgerritMerged openstack/swift master: Authors/changelog for 2.23.0  https://review.opendev.org/68550300:22
*** ianychoi has quit IRC00:32
*** ianychoi has joined #openstack-swift00:48
*** BjoernT has joined #openstack-swift02:15
*** mkrai_ has joined #openstack-swift02:37
*** BjoernT has quit IRC04:09
*** rcernin has quit IRC04:29
*** rcernin has joined #openstack-swift04:33
*** mkrai_ has quit IRC05:01
*** mkrai_ has joined #openstack-swift05:02
*** spsurya has joined #openstack-swift05:05
*** mkrai_ has quit IRC05:56
*** mkrai__ has joined #openstack-swift05:57
*** ianychoi has quit IRC06:20
*** ianychoi has joined #openstack-swift06:23
*** ianychoi has quit IRC06:29
*** ianychoi has joined #openstack-swift06:31
*** new_student1411 has joined #openstack-swift06:32
*** mkrai_ has joined #openstack-swift06:52
*** mkrai__ has quit IRC06:56
*** mkrai_ has quit IRC06:59
*** mkrai_ has joined #openstack-swift06:59
*** rcernin has quit IRC07:06
*** tesseract has joined #openstack-swift07:12
*** rdejoux has joined #openstack-swift07:20
*** pcaruana has joined #openstack-swift07:28
*** ianychoi has quit IRC07:45
*** e0ne has joined #openstack-swift07:52
*** e0ne has quit IRC07:53
*** mikecmpbll has joined #openstack-swift07:58
*** tkajinam has quit IRC08:00
*** mkrai_ has quit IRC08:24
*** mkrai_ has joined #openstack-swift08:25
*** ccamacho has joined #openstack-swift08:31
*** e0ne has joined #openstack-swift08:49
*** NM has joined #openstack-swift09:01
*** NM has quit IRC09:07
*** diablo_rojo has joined #openstack-swift09:17
*** diablo_rojo has quit IRC09:24
new_student1411timburke , thanks for the reply. It was not the exact issue the way I explained it. Let me do some more research on ec2 credentials authentication.09:33
*** diablo_rojo has joined #openstack-swift10:16
*** diablo_rojo has quit IRC10:40
*** rcernin has joined #openstack-swift10:44
*** rcernin has quit IRC11:34
*** dosaboy has quit IRC11:45
*** baojg has joined #openstack-swift11:47
*** dosaboy has joined #openstack-swift11:54
*** dosaboy has quit IRC12:03
*** dosaboy has joined #openstack-swift12:03
*** baojg has quit IRC12:04
*** mkrai_ has quit IRC12:13
*** mkrai_ has joined #openstack-swift12:18
*** mkrai_ has quit IRC13:01
*** mkrai_ has joined #openstack-swift13:02
*** BjoernT has joined #openstack-swift13:18
openstackgerritAlexandre Lécuyer proposed openstack/swift feature/losf: Add tests for vfile.py  https://review.opendev.org/66637813:28
*** mkrai_ has quit IRC13:29
*** BjoernT has quit IRC13:29
*** BjoernT has joined #openstack-swift13:32
*** mkrai_ has joined #openstack-swift14:22
*** mkrai_ has quit IRC14:28
openstackgerritThiago da Silva proposed openstack/swift master: Start building py3 docker images  https://review.opendev.org/68641915:06
*** BjoernT has quit IRC15:18
*** BjoernT has joined #openstack-swift15:20
*** mkrai has joined #openstack-swift15:21
*** gyee has joined #openstack-swift15:24
tdasilvatburke, clayg, mattoliverau: as I'm making progress on tests, i'm now hitting the use-cases of overwrites and deletes when versioning is suspended. Currently the difference we have over s3 is that on deletes we will keep adding delete markers with a version_id, while on overwrite we don't delete any delete_marker. This is different from from s3 in that aws will add a delete_marker only one and with a 'null'15:27
tdasilvaversion_id. On a overwrite, it will also remove that delete_marker. I don't think our implementation is bad, but i am concerned about the increase version counts as it is counting delete marker (versioning is supposed to be suspended) and the fact that our s3api implementation will probably have to follow swift's behavior and have to deviate a bit from aws s315:27
*** tesseract has quit IRC15:36
*** mkrai has quit IRC15:39
*** mkrai__ has joined #openstack-swift15:39
claygyeah I think when we're suspended we shouldn't create any new delete markers?  Can't we just make sure the static link is a tombstone and call it day?15:43
claygThe only one I worry about is an overwrite while suspended - it's fine to overwrite the static link (since the data is still versioned) but when we re-enable versioning we have to make sure to copy any "not-static-links" out of the public container before we overwrite them with a static link to the new data!?15:45
clayg... but isn't that basically what we have to do when we're enabling versioning for the first time anyway?15:45
claygMaybe I'm misunderstanding the delete_marker situation on suspended...15:46
tdasilvaclayg: regarding the overwrite after re-enable. Yes, we copy non-static-links out of the public container so we are good there...16:01
tdasilvaclayg: re: delete markers. aws will do something a bit weird that when in suspended mode, if you issue a delete, it will write down a delete-marker with version-id='null'16:02
tdasilvaclayg: for reference: http://paste.openstack.org/show/779176/16:04
*** rdejoux has quit IRC16:05
claygyeah #11 is *bogus* - i want to break api compatibility there - i think it's just an accident of how they've implemented16:06
clayg@timburke and I had at one point also talked about in #6 we'd go ahead and assign a version-id (based on the timestamp of the GET) to the object before we add it to the versioned listing as well...16:07
claygthe only time I'd like to see 'null' versions is when we're adding in an for-realzy-object-with-data from the public container - everything in the null-versions container would have a version-id (it's part of the path name!)16:08
claygdo you think our tests would be able to make "useful" assertions about behavior of s3 & swift without having to be much of a stickler on some minor/strange/unimportant differences like the version-id of an object written while suspended and overwritten while enabled?  😬16:10
tdasilvaclayg: sure, i'm not arguing for strictness, but just wanted to make sure we are all on the same page about that.16:12
tdasilva"the only time I'd like to see 'null' versions is when we're adding in an for-realzy-object-with-data from the public container - everything in the null-versions container would have a version-id (it's part of the path name!)" << this is the current implementation16:12
claygno no no - it's good!  we have to do at least two things:16:12
clayg1) know *exactly* how s3api behaves16:12
clayg2) know *exactly* how we want swift-object-versioning to behave!16:13
claygI 100% agree, *if* we decide they should be different we need to be on the same page about that!!!16:13
tdasilvaI'd add a 3rd: know (and document) *exactly* where s3api deviates from aws s3 so that our future selves don't have to wonder about the decisions that were made in case people ask about those differences16:15
tdasilva'cause I know I won't remember :)16:15
claygsame here16:15
claygso but it sounds like 1) the behavior I'm describing makes sense to you for swift-object-versioning and 2) that's what you've implemented!16:16
claygso the only think left is 3) how are we going to document how this is different from s3api16:16
tdasilvayeah16:16
claygI think writing it down is a good first step - but eventually I'd like to codify it somehow... like via a test of some-kinda?16:17
tdasilvame wonders if ceph tests are super strict to pick up on those differences16:17
claygi haven't managed to get ceph's s3 object-versoining tests running again out versoining support yet...16:17
tdasilvaclayg: yeah, in the case of swift tests, i'm making sure to highlight that behavior16:18
claygyeah, the swift-object-versioning tests - for sure - and you could even drop comments "this isn't what s3 does"16:18
claygbut later in the s3api tests - especially the ones we want to run again swift and s3 (and ceph?) - there's an oppertunity to say something about the differences there16:19
clayg... maybe16:19
tdasilva+116:29
*** ccamacho has quit IRC16:31
*** mikecmpbll has quit IRC16:32
openstackgerritOpenStack Release Bot proposed openstack/swift stable/train: Update .gitreview for stable/train  https://review.opendev.org/68643816:35
openstackgerritOpenStack Release Bot proposed openstack/swift stable/train: Update TOX/UPPER_CONSTRAINTS_FILE for stable/train  https://review.opendev.org/68643916:35
openstackgerritOpenStack Release Bot proposed openstack/swift master: Update master for stable/train  https://review.opendev.org/68644016:35
*** e0ne has quit IRC16:36
*** mkrai__ has quit IRC17:06
*** mkrai_ has joined #openstack-swift17:06
*** mkrai_ has quit IRC17:11
*** openstackgerrit has quit IRC17:21
*** e0ne has joined #openstack-swift17:59
*** e0ne has quit IRC18:06
*** spsurya has quit IRC18:07
*** openstackgerrit has joined #openstack-swift18:19
openstackgerritTim Burke proposed openstack/swift master: Update master for stable/train  https://review.opendev.org/68644018:19
timburkeyay! we have a train release!18:19
timburkealso, i have my china visa :-)18:19
claygROFL18:27
clayg  File "/home/vagrant/swift/swift/common/db.py", line 155, in <lambda>18:27
clayg    self, *args, **kwargs))18:27
claygValueError: the query contains a null character18:27
timburkewhomp whomp18:27
timburke*way* down in there https://github.com/python/cpython/blob/v3.7.4/Modules/_sqlite/statement.c#L67-L7018:30
claygs'fine - i forgot to retell myself the fable of ye 'ol "bobby tables" before writing sql18:52
clayg                    query += " name NOT LIKE ? AND"18:52
clayg                    query_args.append('%%\x00%%')18:52
clayg^ is a lot more like what I wanted18:52
claygand sqli's bind/escape whatever is just fine with it18:52
claygI mean prefix=null%00 was working just fine, so I knew something should work 🤷‍♂️18:53
claygrelevant XKCD -> https://xkcd.com/327/18:53
tdasilvatimburke: I also tagged a v2.23.0 release of the docker container: https://hub.docker.com/r/openstackswift/saio/tags18:53
claygtag that docker build!18:54
openstackgerritThiago da Silva proposed openstack/swift master: Start building py3 docker images  https://review.opendev.org/68641918:58
timburkethanks tdasilva!18:59
*** itlinux has quit IRC19:02
*** henriqueof1 has joined #openstack-swift19:04
*** henriqueof has quit IRC19:07
openstackgerritMerged openstack/swift stable/train: Update .gitreview for stable/train  https://review.opendev.org/68643819:44
*** gmann is now known as gmann_afk19:52
*** pcaruana has quit IRC20:18
*** camelCaser has quit IRC21:28
*** camelCaser has joined #openstack-swift21:28
*** rcernin has joined #openstack-swift22:08
*** BjoernT has quit IRC22:31
*** henriqueof1 has quit IRC22:58
*** tkajinam has joined #openstack-swift23:01
timburkewell that's new: https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_654/652184/3/gate/swift-tox-py37/654bebe/job-output.txt23:21
timburke`AssertionError: Invalid switch into Queue.put: ()` coming up out of eventlet23:21
openstackgerritMerged openstack/swift master: Update master for stable/train  https://review.opendev.org/68644023:51
*** NM has joined #openstack-swift23:54
*** NM has quit IRC23:58

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