Thursday, 2018-05-31

*** klamath has quit IRC00:05
*** klamath has joined #openstack-swift00:08
openstackgerritSamuel Merritt proposed openstack/swift master: Refactor object updater's async-pending finder  https://review.openstack.org/57134300:39
*** gerardgine has quit IRC00:40
*** amandap_ has joined #openstack-swift00:58
*** amandap has quit IRC01:00
*** gyankum has joined #openstack-swift01:19
openstackgerritMerged openstack/swift master: Added PyPI validation check for the readme.  https://review.openstack.org/57121501:22
*** amandap_ has quit IRC01:29
*** lifeless_ has joined #openstack-swift01:40
*** lifeless has quit IRC01:40
*** mvk has quit IRC02:06
*** mvk has joined #openstack-swift02:19
openstackgerritMerged openstack/swift master: removed specific reference to two core reviewers  https://review.openstack.org/57132802:32
*** klamath has quit IRC02:39
*** klamath has joined #openstack-swift03:13
*** klamath has quit IRC03:29
*** amandap has joined #openstack-swift03:29
*** rcernin has quit IRC03:35
*** kei_yama has quit IRC03:43
*** ianychoi has quit IRC03:51
*** rcernin has joined #openstack-swift03:54
*** mvk has quit IRC03:56
*** kei_yama has joined #openstack-swift04:01
*** gyee has quit IRC04:21
*** rcernin has quit IRC04:28
*** rcernin has joined #openstack-swift04:29
*** links has joined #openstack-swift04:38
openstackgerritPete Zaitcev proposed openstack/swift master: Make ShardRanges and its CLI py3-compliant  https://review.openstack.org/57032005:12
*** cshastri has joined #openstack-swift05:16
*** cshastri has quit IRC05:28
*** pcaruana has joined #openstack-swift06:43
*** klamath has joined #openstack-swift06:44
kota_hello, perhaps acoles knows, is there any chance to run swift-container-sharder w/o internal-client.conf located under /etc/swift ?06:47
kota_i noticed storlets gate broken that attempts to setup Swift via devstack but no configuration exists for internal-client then swift-init all start got an error like No such file or directory for container-sharder.06:49
*** klamath has quit IRC06:49
kota_hmmm... anyway, fixing the devstack seems a right way tho.06:52
*** rcernin has quit IRC07:11
kota_https://review.openstack.org/57139107:11
patchbotpatch 571391 - openstack-dev/devstack - Add internal-client config integration for Swift07:11
*** tesseract has joined #openstack-swift07:22
*** ianychoi has joined #openstack-swift07:32
*** geaaru has joined #openstack-swift07:40
*** cbartz has joined #openstack-swift07:41
*** ccamacho has joined #openstack-swift07:44
*** amandap has quit IRC07:45
*** amandap has joined #openstack-swift07:45
*** amandap has quit IRC07:48
*** amandap has joined #openstack-swift07:48
acoleskota_: the path to the internal client conf is configurable07:59
acoleskota_: https://github.com/openstack/swift/blob/26418140108281ae5ac11004ebf33b7b3e08c74d/etc/container-server.conf-sample#L409-L41108:00
kota_acoles: yes, it's configurable but if it doesn't exist, the sharder cannot start the work.08:01
kota_acoles: but, thanks.08:01
acoleskota_: OIC. no, it is required for the sharder08:02
kota_and it seems like that i did duplicate work with https://review.openstack.org/#/c/570869/ :P08:03
patchbotpatch 570869 - openstack-dev/devstack - swift expects an internal client config to start08:03
*** hoonetorg has quit IRC08:11
*** rcernin has joined #openstack-swift08:12
*** rcernin has quit IRC08:12
acoleskota_: internal client is also required for container sync I think?08:12
acolesah no, container sync has an inline default config08:13
acolesso the conf file is not *required*08:13
kota_OIC, we have dsvm gate but it does never fail. the reason seems like, we have an option SWIFT_START_ALL_SERVICES=False for devstack08:13
kota_http://logs.openstack.org/69/570869/2/check/legacy-swift-dsvm-functional/837bd78/logs/local.conf.txt.gz08:13
kota_acoles: that's what I thought about container-sync08:14
kota_I'm not sure if it's *fortunate* or *unfortunate*08:14
*** mikecmpbll has joined #openstack-swift08:15
*** hoonetorg has joined #openstack-swift08:24
kota_timburke, notmyname: perhaps, p 570869 hits the eventlet 0.23.0 issue that breaks swift ???08:27
patchbothttps://review.openstack.org/#/c/570869/ - openstack-dev/devstack - swift expects an internal client config to start08:27
kota_no08:27
kota_no it's not the patch i meant08:27
kota_i meant, p 56470008:28
patchbothttps://review.openstack.org/#/c/564700/ - swift - WIP: Add ceph-s3 test non-voting job08:28
kota_I just saw notmyname's mail in the openstack-dev mailing list -> http://lists.openstack.org/pipermail/openstack-dev/2018-May/130256.html08:30
openstackgerritKota Tsuyuzaki proposed openstack/swift master: WIP: Add ceph-s3 test non-voting job  https://review.openstack.org/56470008:32
*** lifeless_ is now known as lifeless08:42
*** klamath has joined #openstack-swift08:46
*** klamath has quit IRC08:51
*** mikecmpb_ has joined #openstack-swift09:08
*** mikecmpbll has quit IRC09:09
*** amandap has quit IRC09:10
remix_tjnotmyname: just to let you know, EMC implements retention header with a non standard extension: http://doc.isilon.com/ECS/3.2/DataAccessGuide/ecs_c_swift_reterntion.html so my idea is to make this a standard option :-)09:23
*** silor has joined #openstack-swift09:35
*** lifeless has quit IRC09:55
*** lifeless has joined #openstack-swift09:56
*** mikecmpb_ has quit IRC09:58
*** mikecmpbll has joined #openstack-swift09:59
*** silor1 has joined #openstack-swift10:00
*** silor has quit IRC10:03
*** silor1 is now known as silor10:03
*** lifeless has quit IRC10:08
*** lifeless_ has joined #openstack-swift10:08
*** silor has quit IRC10:10
*** armaan has joined #openstack-swift10:33
*** klamath has joined #openstack-swift10:47
*** klamath has quit IRC10:51
*** amandap has joined #openstack-swift10:52
*** gyankum has quit IRC11:00
*** tesseract has quit IRC11:07
*** tesseract has joined #openstack-swift11:08
*** sajjadg has joined #openstack-swift11:25
*** mikecmpbll has quit IRC11:47
*** mikecmpbll has joined #openstack-swift11:49
*** armaan has quit IRC11:50
*** armaan has joined #openstack-swift11:50
*** armaan has quit IRC12:13
*** armaan has joined #openstack-swift12:14
openstackgerritAlistair Coles proposed openstack/swift master: Fix marker and end_marker descriptions in API ref  https://review.openstack.org/57146012:29
*** kei_yama has quit IRC12:29
*** sajjadg has quit IRC12:39
*** prasen has joined #openstack-swift12:41
*** prasen has quit IRC12:48
*** prasen has joined #openstack-swift12:49
*** sajjadg has joined #openstack-swift12:50
*** zaitcev has quit IRC12:57
*** jistr is now known as jistr|mtg12:59
*** amandap has quit IRC12:59
*** armaan has quit IRC13:11
*** armaan has joined #openstack-swift13:12
*** armaan has quit IRC13:17
*** zaitcev has joined #openstack-swift13:17
*** ChanServ sets mode: +v zaitcev13:17
*** armaan has joined #openstack-swift13:23
*** links has quit IRC13:29
*** amandap has joined #openstack-swift13:32
*** klamath has joined #openstack-swift13:36
*** armaan has quit IRC13:38
*** gyankum has joined #openstack-swift13:42
*** mvenesio has joined #openstack-swift13:43
openstackgerritMerged openstack/swift master: Stop overriding _in_sync in container replicator  https://review.openstack.org/57005514:05
*** olc has quit IRC14:08
*** mvenesio has quit IRC14:13
*** amandap has quit IRC14:14
*** prasen has quit IRC14:27
*** armaan has joined #openstack-swift14:46
*** jistr|mtg is now known as jistr14:57
*** sajjadg has quit IRC15:09
*** silor has joined #openstack-swift15:10
*** silor has quit IRC15:13
*** ccamacho has quit IRC15:15
*** ccamacho has joined #openstack-swift15:15
*** itlinux has joined #openstack-swift15:25
*** gyee has joined #openstack-swift15:26
*** pcaruana has quit IRC15:28
*** itlinux has quit IRC15:31
*** itlinux has joined #openstack-swift15:31
*** mvk has joined #openstack-swift15:54
*** amandap has joined #openstack-swift16:03
*** itlinux has quit IRC16:07
*** cbartz has quit IRC16:11
*** hseipp has joined #openstack-swift16:16
*** ccamacho has quit IRC16:21
*** hseipp has quit IRC16:21
notmynamegood morning16:23
*** itlinux has joined #openstack-swift16:24
*** geaaru has quit IRC16:27
*** hseipp has joined #openstack-swift16:27
timburkegood morning16:35
timburkefwiw, the default internal client config for container sync was done for backwards compatibility, so you could upgrade swift before updating config and container sync would still work16:36
timburkethe container sharder, being a new daemon, doesn't have to worry about the upgrade path16:38
*** mikecmpbll has quit IRC16:40
*** armaan has quit IRC16:47
*** hseipp has quit IRC16:47
*** armaan has joined #openstack-swift16:48
timburkeremix_tj: interesting... i've played around with something like setting a retention period for a container -- one of the use-cases that drove me to write https://review.openstack.org/#/c/342857/ was being able to set a default x-delete-after header on PUT to a particular container16:48
patchbotpatch 342857 - swift - Add defaulter middleware16:48
*** amandap has quit IRC16:57
*** prasen has joined #openstack-swift17:02
timburkethat layer of indirection is interesting, though -- being able to change the retention period for *a group* objects by changing the value for the policy is kinda cool17:09
*** klamath_ has joined #openstack-swift17:11
*** klamath__ has joined #openstack-swift17:12
notmynametimburke: can you relink what remix_tj was referring to? my IRC client closed this morning before I could read my znc buffer17:13
timburkenotmyname: http://doc.isilon.com/ECS/3.2/DataAccessGuide/ecs_c_swift_reterntion.html17:14
notmynamethanks17:14
*** klamath has quit IRC17:14
*** klamath_ has quit IRC17:15
notmynamealong those lines, I've been pondering clayg's idea of having a different `unlink_older_than()`. ie an `unlink_newer_than()`, and use that for some sort of "retention"17:16
notmynameit's an interesting compromise for eventually-consistent storage that has a "no overwrites or deletes" policy/rule17:16
notmynameturns into "well maybe you can overwrite data, but we'll get it sorted and give you back the old stuff eventually"17:17
notmynamesounds simpler (and more "swift-y") than adding an etcd layer to the system to get paxos/raft17:18
*** klamath__ has quit IRC17:18
openstackgerritAlistair Coles proposed openstack/swift master: Add detail to container server GET docstring  https://review.openstack.org/57153017:19
openstackgerritAlistair Coles proposed openstack/swift master: WIP Always fetch listings from shards when possible  https://review.openstack.org/57153117:19
*** klamath has joined #openstack-swift17:22
timburkenotmyname: i remember you (or maybe torgomatic?) mentioning once that we could probably come up with a way to have a storage policy for WORM that basically runs the consistency bits in reverse... i still rather like that idea17:22
notmynameI don't think it was me. I thought it was clayg. could have been torgomatic. yeah, it's a pretty cool idea17:23
*** klamath_ has joined #openstack-swift17:24
tdasilvaisn't the issue with that idea that you give a user a 200 response for something that won't be there eventually17:27
tdasilva?17:27
*** klamath has quit IRC17:28
*** klamath has joined #openstack-swift17:29
*** klamath_ has quit IRC17:31
notmynameI don't know how much of an issue that is. I mean, what happens if you send a PUT today, but 15 ms before another PUT starts. you'll get a 200, but your data won't be there17:31
*** klamath_ has joined #openstack-swift17:32
notmynameisn't it a question of how it responds when there are failures? and in that case today, there's valid debate over if what we do is "right" or not17:32
notmynameI think simply writing down what happens and then sticking to it may be sufficient17:33
timburke(obvs, of course, it should respond 409 if there *aren't* failures)17:33
notmynametdasilva: I mean, that's a completely valid point and a really really good thing we should discuss17:33
notmynametimburke: obviously ;-)17:33
*** klamath has quit IRC17:35
clayggood morning17:35
*** gyankum has quit IRC17:35
torgomaticif you're going to do WORM and not lie to the user with 200s for things that vanish, you've got to have an immediately-consistent set somewhere that contains the names of all the objects which are immutably-stored.17:38
timburketorgomatic: but we *already* lie to the user about data that might vanish. we just hand-wave and say "eventual consistency"17:40
timburkewhy can't we do the same here?17:40
*** d0ugal_ has joined #openstack-swift17:40
torgomaticwe could, or we could try to do better than our past selves :)17:40
tdasilvaone way to do it is to rely on strong-consistent backends, that's probably what EMC is doing with isilon...17:42
*** d0ugal has quit IRC17:42
torgomaticif you have strong consistency *somewhere*, it's easy to do stuff like WORM17:43
torgomaticif all you have is eventual consistency everywhere, it's really tough17:43
torgomaticwhat if the user makes a WORM-policy container during a network failure, then PUTs some objects, but then it turns out that the WORM policy loses during container replication, so those "immutable" objects aren't?17:45
*** d0ugal__ has joined #openstack-swift17:51
*** klamath_ has quit IRC17:51
*** klamath has joined #openstack-swift17:51
torgomaticIt probably depends on what you need from WORM. If you want pretty-good guarantees, then a policy-based approach is great. If you've got legal requirements that these documents MUST NOT get overwritten no matter what, then you're going to want the guarantee.17:53
*** d0ugal_ has quit IRC17:53
*** itlinux has quit IRC17:53
notmynameI laugh (on the inside) every time I hear someone give ultimatums about what MUST and MUST NOT happen in distributed systems17:54
*** itlinux has joined #openstack-swift17:57
*** itlinux has quit IRC17:58
*** d0ugal__ has quit IRC17:59
torgomaticthe tools exist to make this particular thing happen with strong guarantees; they're just expensive and on the other side of CAP from where Swift is17:59
notmynameyeah18:00
torgomaticif I had an internal customer asking for WORM, I'd need to find out a bit more about their requirements before choosing the cheap first-write-wins in replication or the expensive index-of-all-objects option18:01
*** itlinux has joined #openstack-swift18:05
*** armaan has quit IRC18:21
*** armaan has joined #openstack-swift18:21
*** d0ugal__ has joined #openstack-swift18:22
*** d0ugal__ has quit IRC18:34
*** tesseract has quit IRC18:34
*** lifeless_ has quit IRC18:39
*** ccamacho has joined #openstack-swift18:45
*** mvk has quit IRC18:52
*** amandap has joined #openstack-swift18:58
*** d0ugal__ has joined #openstack-swift18:59
*** amandap has quit IRC19:02
*** armaan has quit IRC19:04
timburkei'm not *opposed* to taking that kind of an approach -- i think there are a lot of benefits to be had that would resolve a lot of the hard-to-paper-over differences with s3 -- but it seems like it may be beyond the scope of swift19:12
*** prasen has quit IRC19:18
*** armaan has joined #openstack-swift19:37
*** lifeless has joined #openstack-swift19:38
*** armaan has quit IRC19:43
openstackgerritJohn Dickinson proposed openstack/swift master: Added S3 compatibility information to docs  https://review.openstack.org/57156119:51
*** armaan has joined #openstack-swift19:56
*** armaan has quit IRC20:03
openstackgerritJohn Dickinson proposed openstack/swift master: Added S3 compatibility information to docs  https://review.openstack.org/57156120:19
*** lifeless_ has joined #openstack-swift20:36
*** lifeless has quit IRC20:36
*** mikecmpbll has joined #openstack-swift21:06
*** links has joined #openstack-swift21:42
*** hoonetorg has quit IRC21:55
*** itlinux has quit IRC22:04
*** hoonetorg has joined #openstack-swift22:08
*** rcernin has joined #openstack-swift22:13
*** links has quit IRC22:16
*** lifeless_ has quit IRC22:33
*** lifeless has joined #openstack-swift22:34
*** mikecmpbll has quit IRC22:40
*** d0ugal__ has quit IRC22:48
*** d0ugal__ has joined #openstack-swift23:02
*** mikecmpbll has joined #openstack-swift23:03
*** kei_yama has joined #openstack-swift23:09
*** amandap has joined #openstack-swift23:28
notmynametdasilva: FWIW https://github.com/notmyname/alpine_swift  <-- what I've been picking at recently and what I want to include in swift23:34
openstackgerritMerged openstack/swift master: Add detail to container server GET docstring  https://review.openstack.org/57153023:45
openstackgerritMerged openstack/swift master: Remove some Python 2.6 compatibility code in ring  https://review.openstack.org/57042123:55
openstackgerritMerged openstack/swift master: Use X-Timestamp when checking object expiration  https://review.openstack.org/53259523:55
*** mikecmpbll has quit IRC23:58

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