Wednesday, 2016-01-27

*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** daemontool_ has quit IRC00:04
ho_good morning!00:06
*** daemontool_ has joined #openstack-swift00:06
*** blmartin has joined #openstack-swift00:13
mattoliverauho_: morning00:13
*** daemontool_ has quit IRC00:13
ho_mattoliverau: morning!00:13
*** tongli has quit IRC00:20
*** fbo has quit IRC00:20
*** fbo_ has joined #openstack-swift00:20
openstackgerritMerged openstack/swift-bench: Bump eventlet min version to 0.17.4  https://review.openstack.org/27148700:25
claygoh yeah, that reminds me - i wanted to check if i was already packaging psutil00:25
clayghrmm... yeah but it's only 0.4.100:26
claygwhoa - latest from pypi is 3.4.2 (!?)00:27
claygpreciase has 1.2.100:28
*** nadeem has quit IRC00:37
*** fthiagogv_ has joined #openstack-swift00:41
*** dmorita_ has quit IRC00:43
*** fthiagogv has quit IRC00:43
torgomaticwow, swift-bench changes merge *fast*00:46
torgomaticI've gotten so used to things taking at least a few hours, but swift-bench changes take less than 2 minutes00:46
kota_hello00:47
torgomatichi00:47
kota_torgomatic: o/00:48
kota_torgomatic: speaking of which, did you notice my ping for patch 271920?00:49
patchbotkota_: https://review.openstack.org/#/c/271920/ - swift - CompositeRing Support00:49
torgomatickota_: yes, I saw that. I'm going to look at it once I'm done with the thing I'm currently working on00:50
claygonovy: peterlisak: hey before we going making the auditors even slower by nicing them - do either you have any intrest in taking a stab a lp bug #118365600:50
openstackLaunchpad bug 1183656 in OpenStack Object Storage (swift) "object auditors don't finish" [Undecided,Confirmed] https://launchpad.net/bugs/118365600:50
kota_torgomatic: sounds cool, thanks :-)00:50
kota_that one is still stuck on gerrit failure though :/00:51
*** m_kazuhiro has joined #openstack-swift00:52
claygonovy: peterlisak: I also think maybe psutil is a fairly meaty dependency - I wonder what it might look like to just make a quick little ctypes wrapper like we do for other things in utils?  Did you try it to compare the two options?00:53
mattoliveraukota_: o/00:54
kota_mattoliverau: o/00:54
*** dmorita has joined #openstack-swift00:54
claygonovy: peterlisak: lastly I'm curious how much further you want to take the setpriority options?  Do you have any reason to believe they make sense in the the proxy where there's hardly any file-system access?  Does it make sense to document them everywhere if all we really want (right now) is to nice the auditors?00:54
*** arch-nemesis has quit IRC00:57
*** haomaiwang has quit IRC01:01
*** haomaiwa_ has joined #openstack-swift01:01
*** fthiagogv__ has joined #openstack-swift01:02
*** fthiagogv_ has quit IRC01:04
*** mgarza has quit IRC01:10
*** zhill has quit IRC01:11
*** haomaiwa_ has quit IRC01:12
*** fthiagogv_ has joined #openstack-swift01:12
*** fthiagogv__ has quit IRC01:14
*** dmorita has quit IRC01:15
*** dmorita has joined #openstack-swift01:18
openstackgerritMerged openstack/swift: Add __next__() methods to utils iterators for py3  https://review.openstack.org/23704001:19
*** garthb_ has quit IRC01:20
claygmattoliverau: haypo's still at it!?01:22
*** xiangxinyong has joined #openstack-swift01:24
*** rminmin has joined #openstack-swift01:25
*** Jeffrey4l has joined #openstack-swift01:28
*** david-lyle has quit IRC01:36
*** fthiagogv__ has joined #openstack-swift01:36
*** fthiagogv_ has quit IRC01:39
*** fthiagogv_ has joined #openstack-swift01:43
*** fthiagogv__ has quit IRC01:45
*** diogogmt has quit IRC01:48
*** dmorita has quit IRC01:48
*** dmorita has joined #openstack-swift01:53
*** jmccarthy has quit IRC01:54
*** jmccarthy has joined #openstack-swift01:55
*** haomaiwang has joined #openstack-swift01:57
mattoliverauclayg: seems it never ends :)01:58
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:01
*** xiangxinyong has quit IRC02:01
*** dmorita has quit IRC02:06
*** nexusz99 has joined #openstack-swift02:06
*** fthiagogv__ has joined #openstack-swift02:08
nexusz99Why swift using XFS filesystem? Is there any document about that reason?02:09
*** fthiagogv_ has quit IRC02:10
claygcause like one time 5 years ago someone did some benchmark on file systems and liked XFS the best - and it hasn't really let us down yet?02:27
claygGluster likes XFS - so does redhat in general02:27
claygI like XFS having worked with it awhile02:27
claygwhy *not* use XFS!?02:27
claygand Dave is cool guy02:28
clayghe's helped us out on the ML a couple times - shit liek that02:28
claygalso someone is probably redbo, he takes crap notes02:28
*** daemontool has joined #openstack-swift02:31
*** diazjf has joined #openstack-swift02:33
*** fthiagogv_ has joined #openstack-swift02:34
*** dmorita has joined #openstack-swift02:34
nexusz99@clayg oh.. thanks. I need to find the benchmark result.02:35
*** fthiagogv__ has quit IRC02:36
redbohttps://docs.google.com/spreadsheets/d/1cjMYx-wAqqgvj_pI8HMCpbEDmVGgeFbqVTVyHBgzncs/pubchart?oid=5&format=interactive02:36
redbohttps://docs.google.com/spreadsheets/d/1cjMYx-wAqqgvj_pI8HMCpbEDmVGgeFbqVTVyHBgzncs/pubchart?oid=4&format=interactive02:37
redboI have a lot of data, but it's all a few years old now.  Supposedly ext4 has gotten better since then.02:38
*** Jeffrey4l has quit IRC02:38
nexusz99what does 'FS Traversal Times' mean?02:39
redboamount of time it takes to enumerate all the files on the filesystem02:39
redbowhich is something I care about more than write speed, as long as write speed is reasonable02:40
nexusz99A ha! Thanks!02:42
*** Jeffrey4l has joined #openstack-swift02:48
*** forcebanana has quit IRC02:55
*** Jeffrey4l_ has joined #openstack-swift02:57
*** esker has quit IRC02:57
*** diogogmt has joined #openstack-swift02:58
*** venkat has joined #openstack-swift03:00
*** Jeffrey4l has quit IRC03:00
*** haomaiwang has quit IRC03:01
*** haomaiwa_ has joined #openstack-swift03:01
*** janonymous has joined #openstack-swift03:03
* clayg takes back about redbo's note-taking03:07
*** diazjf has quit IRC03:08
*** sanchitmalhotra has joined #openstack-swift03:10
redboWell, there's some crappiness.  Like I didn't write down what "EXT4-tuned" means.03:12
*** xiangxinyong has joined #openstack-swift03:16
*** nexusz99 has quit IRC03:20
*** nexusz99 has joined #openstack-swift03:32
*** dmorita has quit IRC03:48
*** xiangxinyong has quit IRC03:49
*** rminmin has quit IRC03:51
*** mingdang1 has joined #openstack-swift04:00
*** haomaiwa_ has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
mahatic_good morning04:19
kota_mahatic: good morning :-)04:20
mahatic_kota_: hello04:20
*** trifon has joined #openstack-swift04:21
*** dmorita has joined #openstack-swift04:21
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add assertions to mem_server unit tests  https://review.openstack.org/27289304:23
*** david-lyle has joined #openstack-swift04:25
*** david-lyle has quit IRC04:25
*** dmorita has quit IRC04:25
*** dmorita has joined #openstack-swift04:30
*** mragupat has joined #openstack-swift04:33
*** david-lyle has joined #openstack-swift04:38
*** trifon has quit IRC04:45
*** dmorita has quit IRC04:54
openstackgerritKota Tsuyuzaki proposed openstack/swift: Follow up mem_server diskfile fixes  https://review.openstack.org/27289304:54
*** dmorita has joined #openstack-swift04:55
*** klrmn has quit IRC04:56
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:01
*** forcebanana has joined #openstack-swift05:06
*** ChubYann has quit IRC05:14
*** blmartin has quit IRC05:15
*** dmorita has quit IRC05:21
*** aparnav has joined #openstack-swift05:21
*** dmorita has joined #openstack-swift05:28
*** ChubYann has joined #openstack-swift05:29
*** dmorita has quit IRC05:33
*** dmorita has joined #openstack-swift05:33
*** km has quit IRC05:35
*** km has joined #openstack-swift05:39
notmynamemattoliverau: still here?05:43
notmynamemattoliverau: note the last 2 tweets https://twitter.com/linuxconfau05:44
mattoliveraunotmyname: still here05:45
mattoliverauYay possible disruptions05:46
notmynameI'm still coming ;-)05:49
notmynameI just checked in for my flight05:49
*** ChubYann has quit IRC05:49
mattoliverauI'm sure it'll be fine, the LCA in Brisbane got washed out to venue changed, but was still awesome :)05:51
notmynameit seems like I do need to pack some rain gear05:52
notmynamehttp://forecast.io/#/f/-37.8175,144.967105:52
*** haomaiwang has quit IRC06:01
*** silor has joined #openstack-swift06:01
*** haomaiwa_ has joined #openstack-swift06:01
*** trifon has joined #openstack-swift06:03
*** SkyRocknRoll has joined #openstack-swift06:09
*** silor1 has joined #openstack-swift06:10
mattoliveraunotmyname: and a life raft ;)06:11
*** silor has quit IRC06:12
*** silor1 is now known as silor06:12
notmynameheh06:12
mattoliverauOK, culled my slides down a little. looking a little better now.06:12
notmynamegreat06:12
notmynameI'm reviewing swift for genomics workloads right now...06:12
mattoliverauso you'll be at the bioinformatics mini conf then I guess :P06:13
notmynameit looked interesting :-)06:13
mattoliveraunotmyname: plus, if we get rained out and need to evacualte to a boat, then our LCA tradition continues, notmyname and mattoliverau on a boat at LCAs ;)06:13
notmynamethat's true!06:14
notmynamewe've been on a boat together in 2 countries. we need to make it 306:14
mattoliverau+1 :)06:14
*** mragupat has quit IRC06:28
*** nexusz99 has quit IRC06:31
*** ppai has joined #openstack-swift06:31
*** dmorita has quit IRC06:45
*** asettle is now known as asettle-afk06:51
*** haomaiwa_ has quit IRC07:01
*** haomaiwa_ has joined #openstack-swift07:01
*** dmorita has joined #openstack-swift07:06
*** nexusz99 has joined #openstack-swift07:07
*** dmorita has quit IRC07:11
openstackgerritHisashi Osanai proposed openstack/swift: Add unit tests for checking responses in AccountController  https://review.openstack.org/27114207:13
*** silor1 has joined #openstack-swift07:18
*** cbartz has joined #openstack-swift07:18
*** silor has quit IRC07:21
*** Jeffrey4l_ has quit IRC07:21
*** kei_yama has quit IRC07:21
*** kei_yama has joined #openstack-swift07:21
*** Jeffrey4l_ has joined #openstack-swift07:21
*** silor1 has quit IRC07:22
*** silor has joined #openstack-swift07:23
*** rcernin has joined #openstack-swift07:27
*** chlong_zzz is now known as chlong07:31
*** SkyRocknRoll has quit IRC07:37
*** zaitcev has quit IRC07:38
openstackgerritHisashi Osanai proposed openstack/swift: Add unit tests for checking responses in ContainerController  https://review.openstack.org/27116007:41
*** zhill has joined #openstack-swift07:44
*** fbo_ is now known as fbo07:45
*** SkyRocknRoll has joined #openstack-swift07:50
*** arnox has joined #openstack-swift07:58
*** haomaiwa_ has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** dmorita has joined #openstack-swift08:05
*** dmorita has quit IRC08:09
*** rledisez has joined #openstack-swift08:22
*** geaaru has joined #openstack-swift08:29
*** asettle-afk has quit IRC08:33
*** km has quit IRC08:33
*** zhill has quit IRC08:55
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
*** vinsh has quit IRC09:04
*** asettle has joined #openstack-swift09:04
*** dmorita has joined #openstack-swift09:07
*** venkat has quit IRC09:07
*** nexusz99 has quit IRC09:09
*** acoles_ is now known as acoles09:10
*** dmorita has quit IRC09:12
acolesgood morning09:15
*** joeljwright has joined #openstack-swift09:19
*** ChanServ sets mode: +v joeljwright09:19
*** jordanP has joined #openstack-swift09:20
*** nexusz99 has joined #openstack-swift09:20
mattoliverauacoles: Evening!09:21
*** venkat has joined #openstack-swift09:22
acoleswow that was a short day, good night :)09:22
*** takashi_ has joined #openstack-swift09:30
*** Jeffrey4l_ is now known as Jeffrey4l09:30
*** jordan_ has joined #openstack-swift09:34
*** jordanP has quit IRC09:34
*** permalac has joined #openstack-swift09:34
*** jordan_ has quit IRC09:34
*** jordanP has joined #openstack-swift09:35
*** asettle has quit IRC09:38
*** jistr has joined #openstack-swift09:43
*** takashi_ has quit IRC09:44
acolesho_: are you still here?09:50
*** asettle-afk has joined #openstack-swift09:53
*** forcebanana has quit IRC09:56
*** forcebanana has joined #openstack-swift09:56
*** SkyRocknRoll has quit IRC09:57
*** forcebanana has quit IRC09:57
mingdang1@kota_  hello, how to see the swift log09:57
*** aix has joined #openstack-swift09:57
mingdang1someone can help me ?09:58
*** admin6 has joined #openstack-swift09:58
*** haomaiwang has quit IRC10:01
*** haomaiwa_ has joined #openstack-swift10:01
*** venkat has quit IRC10:09
*** m_kazuhiro has quit IRC10:09
*** SkyRocknRoll has joined #openstack-swift10:13
openstackgerritAlistair Coles proposed openstack/swift: Remove unnecessary code from test_account.py  https://review.openstack.org/27297910:20
acoles^^ totally trivial review10:20
*** haomaiwa_ has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
nttHI, is there a way for create the thumbnail of an image in swift (eg some middleware)?11:05
*** haomaiwang has quit IRC11:10
*** Razva has joined #openstack-swift11:10
Razvahey! I'm trying to setup a Swift storage and I have a question: is there any way to make the swift machine use its own IP, instead of using the controller as a router? what I'm trying to achieve here is swift content -> net, not swift content -> controller -> net11:10
tdasilvantt: not in swift core. there might be third-party middleware that does that...sounds pretty cool11:13
tdasilvaRazva: I'm assuming by controller you mean Swift proxy, is that correct? if so, no, you have to go through the proxy11:14
ntttdasilva: yes I found something and I will try to write a middleware. Another question: is there a way to do a kind of "bulk download": Download a list of files as a zip11:14
*** mingdang1 has quit IRC11:14
tdasilvantt: there's bulk upload, but no download11:15
ntttdasilva: and write a middleware is a bad idea in your opinion?11:15
openstackgerritAlistair Coles proposed openstack/swift: Copy more headers when copying object  https://review.openstack.org/27272411:15
Razvatdasilva: no, I'm talking about the OpenStack controller (we have all the services installed on a single machine, except Compute)11:16
tdasilvantt: for bulk download?11:16
nttyes11:16
tdasilvaacoles: interesting11:16
tdasilvaRazva: mmm...not sure what the openstack controller is, sorry11:17
tdasilvaRazva: but generally speaking, the user can send a request directly to swift proxy11:17
*** kei_yama has quit IRC11:18
tdasilvantt: I think you could pull that off with slo, but there's no compression11:18
Razvatdasilva oook so what do I need to do/install in order to achieve this?11:26
tdasilvaRazva: you mentioned trying to run everything in one machine, so it sounds like you are in try-out mode. I'd start with setting up a SAIO VM: http://docs.openstack.org/developer/swift/development_saio.html11:27
admin6Hi, I’m trying to test/validate/understand object replication by putting an object in a rep3 container, then deleting 2 of the 3 replicas directly on their disk location. Now I’m expecting to see something happening in the object replicator or updater logs of my storage nodes, at least during the next hour, but nothing special happens. Any idea?11:27
tdasilvaadmin6: are you running all swift services?11:28
Razvatdasilva everything except Swift. :|11:29
*** ppai has quit IRC11:29
admin6it seems so : swift-object-server swift-object-replicator, swift-object-auditor and swift-object-updater are running on all my aco nodes11:30
tdasilvagotta run to a meeting, be back later11:30
*** bkumar has joined #openstack-swift11:33
*** bkumar has quit IRC11:35
*** bkumar has joined #openstack-swift11:35
*** ho_ has quit IRC11:36
acolesadmin6: the replicator does not discover objects that have been manually deleted. it uses a cache of the state of the objects in a partition that is updated as objects are put and deleted via the object server API, and if that cache state does not change then the replicator does not find any work to do.11:38
admin6acoles: ok, but what about a corrupted data file? is’nt supposed the replicator process to check md5sum of files and detect that type of corruption, then takes action to copy it back froma good replica ? I can modify some replica instead of deleting them.11:42
*** Farzad has joined #openstack-swift11:43
*** aix has quit IRC11:43
FarzadHi there,11:43
*** ppai has joined #openstack-swift11:43
*** pcaruana has joined #openstack-swift11:44
FarzadHow can I config swift for multi-connection and resume support downloading?11:44
*** takashi_ has joined #openstack-swift11:44
*** asettle-afk has quit IRC11:45
acolesadmin6: the object-auditor process checks length and md5sum, and it it detects corruption it quarantines the file and updates the partition state, which the replicator would then discover has changed. so you'd need to corrupt/truncate a .data file, run auditor, then run replicators11:48
*** Farzad has quit IRC11:49
admin6acoles: Ok so I should expect something in my object-auditor.log11:49
admin6acoles: cool : ERROR Object /srv/node/staco1z4d02/objects/246773/923/f0fd7353eaccab3450da4cac094fb923 failed audit and was quarantined: Exception reading metadata11:50
admin6acoles: and now, I should expect log from the replicator logs11:51
acolesadmin6: should be11:55
admin6acoles: the replicator is running every 30 seconds, but didn’t do anything for my quarantined object…11:56
acolestdasilva: versioned_writes should be *after* slo and dlo, correct? thats what the sample config file says, and where I think it should be, but its not where it gets auto-inserted :/11:58
*** Razva has quit IRC12:05
*** bkumar has quit IRC12:06
mahatic_acoles: I removed it. I started my services, ran some tests, it's still not auto-inserted, should I do something else too?12:08
acolesadmin6: when you didn't do anything, do you mean the object file is still corrupt, or there is nothing obvious in the logs?12:10
acolesadmin6: also, the replicator needs to have run once after the object was written and before the auditor run (I just realised that while experimenting myself)12:11
acolesmahatic_: so when your proxy starts up it logs its pipeline 'Pipeline was modified.' - you don't see that?12:12
*** mingdang1 has joined #openstack-swift12:14
mahatic_acoles: nope!12:16
mahatic_acoles: I was on feature/crypto, but it shoudn't matter right. I tested on master again. I don't see it in the piple as well, nor the message12:17
mahatic_pipeline*12:17
acolesmahatic_: in proxy.log? you'll only see it if you had a mandatory middleware missing from your config file pipeline12:18
mahatic_acoles: sorry12:18
mahatic_acoles: I do see the message12:18
acolesmahatic_: phew :)12:18
mahatic_acoles: and yes it is before slo!12:18
mahatic_acoles: :)12:18
acolesmahatic_: thanks for confirming that I am not insane12:18
acolesmahatic_: well, not more insane than usual12:19
*** daemontool has quit IRC12:19
mahatic_acoles: lol. rather I confirmed, I am indeed running swift :P12:19
admin6acoles: I got no logs from the replicator, however the 2 replicas file that I have corrupt disapeared, even their directory as disapear (f0fd7353eaccab3450da4cac094fb923)12:19
admin6acoles: I’ve only one replica that is valid, ans nothing has been created / recreated either in the base devices nor in the handoff devices.12:20
acolesmahatic_: yeah, i was beginning to wonder if you were on havana release or somethinf :)12:22
acolesadmin6: the auditor will remove the dirs for corrupt objects12:22
acolesadmin6: if you look in the parent dir that remains do you see a hashes.pkl file?12:22
acolesadmin6: i.e. <device>/objects/<partition>12:23
admin6no, directory /srv/node/staco1z4d02/objects/246773/923 is empty12:23
mahatic_acoles: lol. git told me I'm only 31 commits behind the master ;)12:23
acolesadmin6: you need to have PUT object, run replicators, then corrupt object, then run auditor, then run replicator12:24
admin6acoles: Ok, I’ll retry the process from the begining12:24
*** aix has joined #openstack-swift12:25
acolesadmin6: the hashes.pkl would be in /srv/node/staco1z4d02/objects/246773, but now I think about it, that's not necessarily a great indicator12:26
acolesadmin6: btw, fwiw the hashes.pkl file is where the replicator maintains its perspective of the partition's state.12:27
admin6acoles: I’ve not a single hashses.pkl files anywhere on my devices…12:31
acolesadmin6: and you have put object(s) and run the object-replicators?12:32
admin6acoles: yes.12:32
*** SkyRocknRoll has quit IRC12:33
acolesadmin6: weird. and you never see your corrupted object files restored? if sp, seems like there is some issue with replicator.12:36
acolesadmin6: sorry, have to go for a while12:36
admin6acoles: I’m wondering if tat could’nt come from a misconfiguration on my side regarding dedicated network replicas. I’ve declared two different networks in each devices such as :12:37
admin6id  region  zone      ip address  port  replication ip  replication port      name weight partitions balance meta12:37
admin6             0       1     1      10.10.1.51  6000      10.10.2.51              6003 staco1z1d01 4000.00      54237    0.0012:37
*** pcaruana has quit IRC12:37
admin6but I did not configure specific things elsewhere in the conf files12:38
*** daemontool has joined #openstack-swift12:39
*** ppai has quit IRC12:41
admin6acoles: nothing listen on port 6003. That should probably be part of my problem :-)12:45
*** SkyRocknRoll has joined #openstack-swift12:49
*** takashi_ has quit IRC12:51
*** aparnav has quit IRC12:54
*** ppai has joined #openstack-swift12:55
*** SkyRocknRoll has quit IRC12:59
*** david-lyle has quit IRC13:08
*** haomaiwang has joined #openstack-swift13:14
*** chlong has quit IRC13:15
*** chlong has joined #openstack-swift13:28
*** ho_away has joined #openstack-swift13:32
openstackgerritHisashi Osanai proposed openstack/swift: Add unit tests for checking responses in AccountController  https://review.openstack.org/27114213:36
acolesadmin6: any luck changing your port?13:37
admin6acoles: no, I’m still testing without succes. however I’m not sure that my swift-ring-builder object.builder —replication-port 6003 —change-replication-port 6000 worked becaus md5sul of object.ring.gz is still the same.13:41
acolesadmin6: I think you need to do a write-ring after using set-info to change your replication ports13:47
acolesadmin6: but I'm not hugely familiar with those commands13:48
*** ho_away has quit IRC13:48
admin6acoles: that’s not things we change everyday ;-)13:49
admin6acoles: now after applying write_rings, I see a lot of rsync logs in my object-replicator.log. Seems that it is applying all the backlogs :-)  I’m confifent it will work better now13:53
*** zul has joined #openstack-swift13:59
*** daemontool has quit IRC14:00
admin6acoles: Thanks for your help :-)14:00
*** proteusguy has quit IRC14:00
*** haomaiwang has quit IRC14:01
acolesadmin6: np. glad to hear you got it sorted. remember not to manually delete diskfiles for fun though :)14:01
*** haomaiwang has joined #openstack-swift14:01
*** diogogmt has quit IRC14:01
admin6acoles :-D I’ll try to remember14:01
*** haomaiwang has quit IRC14:02
*** haomaiwa_ has joined #openstack-swift14:02
peterlisakacoles, admin6: hi, i have one patch 253038 ... it compares ring-file and ring-builder (checks if ring file is up-to-date), IMO it could help in your issue, gives you info to do a write-ring.14:02
patchbotpeterlisak: https://review.openstack.org/#/c/253038/ - swift - Add info about state of ring file to default command.14:02
*** haomaiwa_ has quit IRC14:03
*** sanchitmalhotra has quit IRC14:03
*** haomaiwa_ has joined #openstack-swift14:03
*** diogogmt has joined #openstack-swift14:03
*** fthiagogv_ has quit IRC14:03
*** haomaiwa_ has quit IRC14:04
*** haomaiwang has joined #openstack-swift14:04
admin6peterlisak: Thanks14:04
*** haomaiwang has quit IRC14:05
*** haomaiwa_ has joined #openstack-swift14:05
*** haomaiwa_ has quit IRC14:06
*** haomaiwa_ has joined #openstack-swift14:06
*** haomaiwa_ has quit IRC14:07
*** haomaiwa_ has joined #openstack-swift14:07
*** haomaiwa_ has quit IRC14:08
*** haomaiwang has joined #openstack-swift14:08
*** haomaiwang has quit IRC14:09
*** haomaiwang has joined #openstack-swift14:09
*** haomaiwang has quit IRC14:10
*** haomaiwang has joined #openstack-swift14:10
*** haomaiwang has quit IRC14:11
*** haomaiwang has joined #openstack-swift14:11
*** haomaiwang has quit IRC14:12
*** haomaiwa_ has joined #openstack-swift14:12
*** haomaiwa_ has quit IRC14:13
*** haomaiwang has joined #openstack-swift14:13
*** haomaiwang has quit IRC14:14
*** haomaiwang has joined #openstack-swift14:14
*** haomaiwang has quit IRC14:15
*** haomaiwa_ has joined #openstack-swift14:15
*** haomaiwa_ has quit IRC14:16
*** haomaiwa_ has joined #openstack-swift14:16
*** haomaiwa_ has quit IRC14:17
*** david-lyle has joined #openstack-swift14:17
*** haomaiwa_ has joined #openstack-swift14:17
*** proteusguy has joined #openstack-swift14:17
*** mingdang1 has quit IRC14:17
*** haomaiwa_ has quit IRC14:18
*** haomaiwang has joined #openstack-swift14:18
*** haomaiwang has quit IRC14:19
*** haomaiwa_ has joined #openstack-swift14:19
*** haomaiwa_ has quit IRC14:20
*** haomaiwa_ has joined #openstack-swift14:20
*** haomaiwa_ has quit IRC14:21
*** diogogmt has quit IRC14:21
*** haomaiwa_ has joined #openstack-swift14:21
*** haomaiwa_ has quit IRC14:22
*** haomaiwang has joined #openstack-swift14:22
*** haomaiwang has quit IRC14:23
*** haomaiwa_ has joined #openstack-swift14:23
*** haomaiwa_ has quit IRC14:24
*** haomaiwang has joined #openstack-swift14:24
*** haomaiwang has quit IRC14:25
*** 64MAAWZHI has joined #openstack-swift14:25
*** 64MAAWZHI has quit IRC14:26
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:26
*** haomaiwa_ has joined #openstack-swift14:26
openstackgerritAlistair Coles proposed openstack/swift: Insert versioned_writes in correct pipeline position  https://review.openstack.org/27307314:31
*** daemontool has joined #openstack-swift14:31
acolestdasilva: jrichli ^^ phew this copy/versions stuff is sooo complicated. turns out the bug 1537042 I saw was actually due to versioned_writes being auto-inserted ahead of SLO in pipeline :/14:32
openstackbug 1537042 in OpenStack Object Storage (swift) "versioned_writes middleware is mis-placed in proxy pipeline" [Undecided,In progress] https://launchpad.net/bugs/1537042 - Assigned to Alistair Coles (alistair-coles)14:33
acoleswhen it is after SLO there are different bugs then jrichli was right and the slo copy_hook is not called, because the copy request uses a new environ and the copy_hook is not copied into it that environ.14:34
acolesbut when versioned_writes is after SLO there are other bugs like bug 1365862 which maybe jrichli's patch fixes?14:35
openstackbug 1365862 in OpenStack Object Storage (swift) "Object Versioning for Large Object does not work" [Undecided,Confirmed] https://launchpad.net/bugs/1365862 - Assigned to Zhou Yuan (yuan-zhou)14:35
acolesnotmyname: ^^ 'cost of complexity' !!14:36
*** SkyRocknRoll has joined #openstack-swift14:37
*** ho_away has joined #openstack-swift14:41
*** david-lyle has quit IRC14:44
openstackgerritHisashi Osanai proposed openstack/swift: Add unit tests for checking responses in ContainerController  https://review.openstack.org/27116014:53
*** nadeem has joined #openstack-swift14:53
openstackgerritAlistair Coles proposed openstack/swift: Copy headers correctly when copying object  https://review.openstack.org/27272414:54
acolesjrichli: I think I may now be competing with your patch ^^14:55
*** nadeem has quit IRC14:57
*** nadeem has joined #openstack-swift14:58
*** haomaiwa_ has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
*** zul has quit IRC15:03
jrichliacoles: I had noticed you uploaded that patch yesterday, and was gonna chat with you about it this morning.15:08
jrichliI just got in and need to visit the caf to get sustenance - brb15:10
acolesjrichli: i am not *intentionally* competing with you. your patch helped me track down the real bug, cos your patch failed func tests on my saio15:10
*** diazjf has joined #openstack-swift15:11
jrichliacoles: oh geez, of course not.  that is not why i wanted to chat! it did seem like you had figured some things out :-)15:11
acolesjrichli: lol. so not *that* kind of chat then :)15:12
acolesjrichli: so you were right about the copy_hook not being called15:13
*** lcurtis has joined #openstack-swift15:13
*** blmartin has joined #openstack-swift15:14
*** artide has joined #openstack-swift15:15
*** bkumar has joined #openstack-swift15:17
*** mingdang1 has joined #openstack-swift15:18
*** bkumar has quit IRC15:20
pdardeaugood morning15:20
*** mingdang1 has quit IRC15:23
*** ppai has quit IRC15:24
*** cschwede has quit IRC15:34
*** eranrom has joined #openstack-swift15:35
*** mragupat has joined #openstack-swift15:35
openstackgerritAlistair Coles proposed openstack/swift: Remove a print statement from tests  https://review.openstack.org/27311315:36
acoles^^ another trivial review15:36
*** artide has quit IRC15:38
tdasilvaacoles, jrichli: you guys are right on top of things15:38
tdasilvajrichli: do you still have that patch that fixes slo on patch 260179?15:39
patchbottdasilva: https://review.openstack.org/#/c/260179/ - swift - decouple versioned writes from COPY15:39
eranromacoles: Any place where I can comment on the fastpost spec?15:39
eranromacoles: I understand you have deviated, but want to make sure I understand some details15:39
acoleseranrom: the spec has merged. you can propose changes, just like a code change, in the swift-specs repo15:40
eranromacoles: alright15:40
acoleseranrom: or if you see where it needs clarification then propose an update15:40
jrichlitdasilva: yes.  i am just catching up on scrollback.  do you want me to upload that, or show you what I did?15:40
eranromacoles,: ok, will do15:41
tdasilvajrichli: feel free to go ahead an upload, I was hoping to finish today, but I'm running out of time...flying back home today and need to finish packing15:41
acolestdasilva: back to the snow?15:41
*** cschwede has joined #openstack-swift15:42
tdasilvaacoles: yep! :(15:42
*** cbartz has left #openstack-swift15:42
acolestdasilva: ouch15:43
tdasilvaacoles: hehe...but that's ok..missing home by now15:43
*** awelleck has joined #openstack-swift15:43
tdasilvaso I will be missing meeting later tonight15:44
acolestdasilva: before you leave, where should versioned_writes should be w.r.t. slo? https://review.openstack.org/27307315:44
acolesis the doc wrong or the code?15:44
tdasilvaacoles: you are correct, it should be after slo15:44
acolestdasilva: thanks15:44
tdasilvait was my mistake to not add it there, I was probably thinking that by just adding that entry after slo would be enough15:44
jrichlitdasilva: ok, thanks.  Have a safe trip!15:46
*** dmorita has joined #openstack-swift15:47
acolestdasilva: its not obvious! and I think it might work on master if the other middlewares are also auto-inserted, because of the auto-insert ordering.15:47
tdasilvaacoles: yeah, spelling it out is the right way to go to avoid any mess up15:48
*** nadeem has quit IRC15:49
*** ho_away has quit IRC15:51
*** dmorita has quit IRC15:51
*** dmorita has joined #openstack-swift15:55
*** dmorita has quit IRC16:00
*** haomaiwang has quit IRC16:01
*** 21WAAW3MN has joined #openstack-swift16:01
*** mgarza_ has joined #openstack-swift16:03
*** rcernin has quit IRC16:09
pchngacoles: So if I understand your comments in patch 266545, the change is basically to ensure that in diskfile.BaseDiskFile._construct_from_data_file(), any sysmeta found in the .meta files should take precedence? This is what I gathered from the updates to the test_server.py you suggested. (I made these changes, and the updated UT passed)16:12
patchbotpchng: https://review.openstack.org/#/c/266545/ - swift (feature/crypto) - Ensure sysmeta is written/updated on (fast) POST16:12
*** natarej_ has quit IRC16:13
*** natarej_ has joined #openstack-swift16:13
*** natarej_ has quit IRC16:13
*** natarej has joined #openstack-swift16:14
*** david-lyle has joined #openstack-swift16:14
*** klrmn has joined #openstack-swift16:16
*** diazjf has quit IRC16:17
*** tdasilva has quit IRC16:21
*** tdasilva has joined #openstack-swift16:26
timburkegood morning16:27
*** diazjf has joined #openstack-swift16:28
*** forcebanana has joined #openstack-swift16:28
*** arch-nemesis has joined #openstack-swift16:33
acolestimburke: good morning16:34
acolespchng: see this line https://github.com/openstack/swift/blob/master/swift/obj/diskfile.py#L1831-183116:34
acolespchng: that ^^ always replaces any sysmeta keys found in .meta with sysmeta from .data file16:35
acolespchng: you'll need to change that so that the .data file sysmeta is added to metadata first and then .meta file sysmeta keys are added, taking precedence16:36
*** Toni_ has quit IRC16:37
acolespchng: but note that we are talking about x-object-sysmeta-* keys only. its a little confusing because this is NOT the keys in DATAFILE_SYSTEM_METADATA.16:37
*** david-lyle has quit IRC16:38
acolespchng:  in fact DATAFILE_SYSTEM_METADATA might be better named IMMUTABLE_METADATA - those immutable metadata items should always take precedence over keys in .meta file, that should not be changed.16:38
*** david-lyle has joined #openstack-swift16:40
openstackgerritJanie Richling proposed openstack/swift: WIP: Change POST-as-COPY to preserve the DLO manifest contents  https://review.openstack.org/25279116:41
jrichliacoles ^^16:41
jrichliacoles: as if you didn't have enough on your mind ;-)16:41
*** zaitcev has joined #openstack-swift16:52
*** ChanServ sets mode: +v zaitcev16:52
*** ho_away has joined #openstack-swift16:52
acolesjrichli: could it be the test assertion is wrong on line 2456. you updated the x-object-manifest to point to the manifest itself i think.16:52
acolesso the contents of the large object would be the contents of the manifest object when the multipart-manifest=get is omitted from the POST16:53
jrichliacoles: oh geez!16:54
pchngacoles: Thanks, appreciate the explanation!16:54
acolesand in fact when the param is included the test proves a bug? which is that the POST fails to overwrite the original x-object-manifest16:55
acolesso its a neat test!16:55
jrichlianother bug in large objects.  ugh!16:56
*** diogogmt has joined #openstack-swift16:56
jrichlior is that overlapping with what will be fixed with your recent patch?16:56
*** ho_away has quit IRC16:57
*** trifon has quit IRC16:58
*** jistr has quit IRC16:59
*** admin0 has joined #openstack-swift17:00
admin0hello all17:00
acolesidk, what should we expect when POSTing a new x-object-manifest header but also using multipart-manifest=get? for sure, we do not expect the manifest to have the large object copied into its body, which is the case, phew, but which x-object-manifest header should win? I would argue the new one in the POST, so that's a bug17:00
acolesjrichli: ^^17:00
admin0when new storage node is added, is it the objects that are moved, or partitions ?17:00
*** 21WAAW3MN has quit IRC17:01
*** awelleck1 has joined #openstack-swift17:01
*** haomaiwang has joined #openstack-swift17:01
admin0nv17:02
admin0nvm17:02
acolespchng: i meant to say, i'd expect some unit tests to break when you change things there17:02
acolespchng: so there'll be some more work to fix those17:03
pchngacoles: Yes, already seeing some of that with changes to diskfile.py17:03
*** fthiagogv has joined #openstack-swift17:03
*** awelleck has quit IRC17:03
pchngacoles: Haven't looked at the func, probe tests yet but will check/compare to see if any changes to make as well17:04
admin0i have some ring related questions .. suppose i have 4 zones are 1000 containers .. do each zone get 250 containers ?17:07
*** dmorita has joined #openstack-swift17:07
admin0and if data replication is = 3, does each conttainer in the same zone have 1/3 of the data ?17:07
admin0if replicaiton = 3, is it 1 per zone, or is it 3 containers in the same zone ?17:07
*** dmorita has quit IRC17:11
*** sanchitmalhotra has joined #openstack-swift17:15
*** klrmn has quit IRC17:17
*** rledisez has quit IRC17:17
*** arnox has quit IRC17:17
*** jmccarthy has quit IRC17:20
*** admin6 has quit IRC17:20
*** McMurlock has quit IRC17:22
*** McMurlock has joined #openstack-swift17:22
*** permalac has quit IRC17:22
*** McMurlock has quit IRC17:26
*** gmmaha has quit IRC17:28
openstackgerritDarrell Bishop proposed openstack/swift: Allow IPv6 addresses/hostnames in StatsD target  https://review.openstack.org/27099117:29
*** McMurlock has joined #openstack-swift17:29
*** pgbridge_ has quit IRC17:33
*** dmorita has joined #openstack-swift17:34
*** dmorita has quit IRC17:35
*** Razva has joined #openstack-swift17:35
Razvahey folks! how in the world can I find the Swift S3 "Access Key" and "Access Secret"?17:36
*** aix has quit IRC17:36
*** pgbridge_ has joined #openstack-swift17:36
timburkeRazva: what auth system are you using?17:37
timburkekeystone, tempauth, swauth, something else...17:37
*** dmorita has joined #openstack-swift17:37
Razvatimburke keystone17:38
*** dmorita has quit IRC17:38
*** dmorita has joined #openstack-swift17:39
timburkeRazva: `openstack ec2 credentials list` is probably a good place to start; if there aren't any credentials defined, `openstack ec2 credentials create`17:42
timburkeit's been a while since i've had to do either of those, though; i don't remember the details real well17:43
*** awelleck1 has left #openstack-swift17:46
Razvatimburke swift = s3 not ec2. should I search for ec2 or s3?17:49
*** gmmaha has joined #openstack-swift17:51
admin0The minimum number of hours before a partition can be reassigned is 8  —17:51
*** dmsimard has quit IRC17:51
admin0how to change that value to less ?17:51
admin0reassigned = reshuffeled for re-balancing ?17:51
timburkeRazva: still use the ec2 cred commands; i think they just lump all of the AWS-like credentials under one name. at any rate, it's what swift3's functional tests use: https://github.com/openstack/swift3/blob/v1.9/swift3/test/functional/setup_keystone#L56-L5717:52
*** ho_away has joined #openstack-swift17:54
*** garthb has joined #openstack-swift17:55
*** eranrom has quit IRC17:55
*** zhill has joined #openstack-swift17:59
timburke181 subcommands is *too many* subcommands...17:59
*** ho_away has quit IRC17:59
*** rcernin has joined #openstack-swift17:59
*** haomaiwang has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:01
*** Jeffrey4l has quit IRC18:02
admin0is there a tool to show/calculate total swift object size ?18:04
admin0total swift usage ?18:04
admin0in GB or TB18:04
*** Microwise has joined #openstack-swift18:12
*** klrmn has joined #openstack-swift18:17
*** jordanP has quit IRC18:18
Razvatimburke when connecting with s3curl I get "<html><h1>Not Found</h1><p>The resource could not be found.</p></html>"18:22
Razvaso it connects (I've tried with a dummy IP and it cont connection refused)18:22
*** nadeem has joined #openstack-swift18:24
timburkeRazva: are you trying to list buckets/containers, list keys/objects, or get a particular object? what's your swift3 config look like? (maybe this would be better over in #swift3...)18:25
Razvatimburke any command that - via s3curl - will show me that I can connect to the Swift instance18:29
Razvaso this way I can see if it's a networking/firewall problem18:29
*** vinsh has joined #openstack-swift18:41
*** cdelatte has joined #openstack-swift18:43
*** daemontool_ has joined #openstack-swift18:45
*** daemontool has quit IRC18:47
*** Microwise has quit IRC18:51
*** haomaiwang has quit IRC19:01
*** haomaiwa_ has joined #openstack-swift19:01
*** geaaru has quit IRC19:05
*** tongli has joined #openstack-swift19:10
*** mrmoje has joined #openstack-swift19:22
*** silor has quit IRC19:27
*** acoles is now known as acoles_19:28
openstackgerritJames Nzomo proposed openstack/python-swiftclient: Fix segmented upload to pseudo-dir via <container>  https://review.openstack.org/27172819:29
admin0my dispersion-report does not work because  my URL is like https://<project-name>.url/  — are there any developers around who can help me with this ?19:32
*** klamath has joined #openstack-swift19:40
* clayg hides in the corner19:45
jrichlihee hee, clayg: btw, love the blade runner reference in the docs.  i didn't read that until notmyname tweeted about it19:46
claygjrichli: oh did he - lol19:47
ahaleoh its clayg :)19:47
ahalei was looking at that handoff thing i said about yesterday again, but with current ring builder built ring19:48
ahaleim not convinced its better in that weird case - https://gist.github.com/ahale/b91fc9bc745e710e070a19:49
openstackgerritMerged openstack/swift: _get_info_cache should encode unicode metadata  https://review.openstack.org/26701619:49
*** ho_away has joined #openstack-swift19:57
*** admin0 has quit IRC19:58
*** haomaiwa_ has quit IRC20:01
*** haomaiwang has joined #openstack-swift20:01
*** ho_away has quit IRC20:01
*** ChubYann has joined #openstack-swift20:04
claygahale: ok, good notes - will take me some time to digest20:06
*** barra204 has quit IRC20:06
*** daemontool has joined #openstack-swift20:06
ahaleyeah no worries, it took me a little while to work out , its all a bit confusing20:07
*** mrmoje has quit IRC20:07
ahaleand sorry for the sketchy code :)20:08
ZyricGood morning20:08
claygahale: looks fine20:08
RazvaI might be to tired, but I swear that I cannot find any documentation on Liberty regarding S3 API20:09
zaitcevWhy would you20:09
*** daemontool_ has quit IRC20:09
claygahale: FWIW, IME, everyone thinks their code looks like crap until they read a *bunch* of code - then they realize all code looks like crap, and start to idolize code that looks only marginally inscrutible vs. the piles of shit most of live our lives in20:09
ahalelol20:10
zaitcevSwift is one of the best codebases I hacked on for 30 years.20:10
zaitcevAnd surprisingly our acceptance of "cleanups" helps.20:10
claygzaitcev: parts are better than others - but that's still high prise - she's one of my favorites too - but I've been in it to long - and the bad parts annoy the fuck out of me20:11
ahaleyeah no clarity of swift code helped me a ton when i started doing this20:11
ahalebut that was before diskfile ;)20:12
zaitcevI too think Peter took it a step too far with the Manager and Writer.20:13
claygrofl20:13
claygManager might have been my fault - I know the router was my bad20:13
zaitcevThere was a certain logic to it, because we needed Writer to avoid some kind of tricky fd leak and was difficult to solve with just the monolithic DiskFile class.20:14
claygzaitcev: don't buy it - monolithic BaseDiskFile FTW20:14
zaitcevwhy didn't you -2 it then20:15
zaitcevyou have all the moral authority20:15
*** sanchitmalhotra has quit IRC20:15
pdardeauclayg: is there anything that marks (or tracks) the bad parts and identifies what makes them bad? for education and later cleanup20:15
claygzaitcev: i wasn't at the hack-a-thon when it got merged *acctually*20:16
claygbut it was fine, it had gone on long enough and there was more better than worse by far20:16
claygI have a love hate with DiskFile - acoles_ has been in there like a boss - it's probably not the part that annoys me the most (although now I'm trying to think what *is*)20:16
*** SkyRocknRoll has quit IRC20:16
claygpipelines?  anything with auto in the name probably...20:17
claygpdardeau: not for a long time - i've started to open wishlist's tho - people are even working on them - it's spooky20:17
claygzaitcev: oh - TESTS - for the love of god every test that chuck ever wrote where he called a controller's VERB method directly instead of req.get_response(app)20:18
claygtest.unit.proxy.test_server20:19
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873620:21
claygwhat time is the thing with the deal?20:21
zaitcevWhat thing with what deal?20:22
*** blmartin has quit IRC20:26
openstackgerritJanie Richling proposed openstack/swift: Change POST-as-COPY to preserve the DLO manifest contents  https://review.openstack.org/25279120:26
jrichliacoles_: thanks for the help on the functest,  that worked!20:26
jrichliacoles_: now i just need everyone to agree on the behavior of POST to a DLO manifest!20:27
*** forcebanana has quit IRC20:28
claygjrichli: I think it should be traslated to a DELETE (after copying to a hidden version container)20:30
jrichliclayg: either that is a joke, or I am seriously never gonna get this stuff.20:31
clayglol - it was joke! i was talking in another chan - sheez20:37
clayg;)20:38
jrichliwhew!20:38
jrichliif you wanna give your input: https://bugs.launchpad.net/swift/+bug/148779120:38
openstackLaunchpad bug 1487791 in OpenStack Object Storage (swift) "POST to DLO squashes data without fast-POST" [Undecided,Confirmed]20:38
jrichlithe patch i have out there is implementing what was deemed as "option #2"20:38
*** diazjf has quit IRC20:41
*** dmorita has quit IRC20:42
*** awelleck has joined #openstack-swift20:42
*** dmorita has joined #openstack-swift20:46
notmynameteam meeting in 14 minutes. I may be a few minutes late20:46
*** blmartin has joined #openstack-swift20:47
mattoliveraumorning20:48
*** cbartz has joined #openstack-swift20:48
jrichlimattoliverau: morning!  so when does your conference start?20:48
mattoliveraujrichli: on Monday, so Sunday arvo/evening for you :)20:49
jrichliand i remember reading about arvo in channel :-)20:49
*** dmorita has quit IRC20:50
notmyname...that feeling when you wake up at 4:30am with an upset stomach the day of an international flight...20:51
jrichlinotmyname: hope you are feeling better now20:52
notmynamethanks. I'm not feeling worse :-/20:52
*** ho_away has joined #openstack-swift20:53
jrichlioh, that doesnt sound too good, although I guess that is a the bright side20:53
mattoliveraujrichli: nice one, otherwise I'd need to give everyone an Aussie Slang lesson again20:54
mattoliveraunotmyname: :(20:54
*** acoles_ is now known as acoles20:57
kota_mornig20:57
ho_awaygood morning!20:58
jrichlimattoliverau:  I think you could compile a whole series of lessons and we still wouldn't know all the slang.  i remember that video you posted a while back.20:58
*** dmorita has joined #openstack-swift20:58
notmynamemeeting time in #openstack-meeting20:59
jlhinsonmattoliverau: jrichli: arvo?20:59
*** haomaiwang has quit IRC21:01
mattoliveraujlhinson: afternoon21:01
*** haomaiwang has joined #openstack-swift21:01
mattoliveraujrichli: this one: https://www.youtube.com/watch?v=yDb_WsAt_Z0 :)21:02
*** forcebanana has joined #openstack-swift21:02
*** diazjf has joined #openstack-swift21:15
*** rcernin has quit IRC21:16
*** Razva has quit IRC21:20
*** bill_az has joined #openstack-swift21:21
*** mrmoje has joined #openstack-swift21:23
*** awelleck has quit IRC21:31
openstackgerritJonathan Hinson proposed openstack/swift: Automatic refresh of memcache config settings  https://review.openstack.org/21849021:43
*** mingdang1 has joined #openstack-swift21:46
*** mingdang1 has quit IRC21:50
*** diazjf has quit IRC21:51
*** lifeless has quit IRC21:53
hroukota_, hey did you have any idea what folks are currently doing for symlink, other than us of course ? :)21:53
kota_well21:54
*** lifeless has joined #openstack-swift21:55
kota_at first, i didn't catch up in detail for current status of symlinks but...21:55
hroukota_,  FYI you can see the conversation re: the problems with symlink here "https://etherpad.openstack.org/p/swift_symlink_post_strategy"21:55
hrouproblems with post and symlinks I should say21:55
kota_ah yeah, roughly21:55
*** cbartz has left #openstack-swift21:56
onovypatch 258158 // anyone have problem with this deprecation remove?21:56
patchbotonovy: https://review.openstack.org/#/c/258158/ - swift - Keystone middleware deprecated option is_admin rem...21:56
joeljwrighttimburke: looks like notmyname says no21:56
kota_i should know also current problem on fast-post21:56
claygkota_: I'm down with not waiting on fast-post for symlinks - but honestly I'm more interested in getting fast-post fixed than getting symlinks released?21:56
timburkeclayg: yeah, the _RetryBody patch is just a follow-up21:56
timburkethe unicode one is also quite small21:56
kota_if we have a solvable issue, yes do it with post-as-copy.21:56
kota_but...21:57
claygtimburke: I'm honestly not sure I caught all those links bro - do you acctually need some eyes or are you just waving your arms?21:57
acolestimburke: is the _RetryBody one your one? I'm already +2 on that :)21:57
timburkeacoles: it is :)21:57
acolestimburke: so I'm done with all the good ones? :D :D21:57
joeljwrighttimburke: I can probably find time on Friday to spend some time on swiftclient review21:58
hrouclayg, kota_ well I believe we all established / agreed it works today as is with post-as-copy :)  Not that I'm disagreeing that getting fast-post working (so it can be used throughout) is not more interesting / important21:58
kota_clayg: wow, i think you can save us :P21:58
joeljwrighttimburke: unless the sky falls in on me again21:58
timburkeclayg: i just know that if *i* don't point them out, they'll probably continue to be overlooked21:58
timburkejoeljwright: thanks21:59
claygi'm re-reading that pad - but I don't think i've missed anything - no progress?21:59
*** haomaiwang has quit IRC22:01
kota_i'm also reading that pad to catch up22:01
hrouclayg, if that was in reference to symlink, nope no progress on where we left - we still believe fast-post has a problem with the existing symlink implementation.  Haven't had too many resources to think that one through more as of late.22:01
*** haomaiwang has joined #openstack-swift22:01
ho_awayacoles: onvoy: takashi: regarding keystone (deprecated issue) i have path 201461. just advertisement :-)22:02
ho_awayacoles: onvoy: takashi: patch 20146122:03
patchbotho_away: https://review.openstack.org/#/c/201461/ - swift - Improve Keystone v3 token support22:03
clayghrou: oh, ok, np22:03
*** achhabra has joined #openstack-swift22:04
clayghrou: so who is m_kazuhiro - is *he* working on symlinks?22:04
*** ho_away has quit IRC22:04
*** mrmoje has quit IRC22:04
hrouclayg, I think so ;)  Chatting with him now to figure that out actually22:04
kota_clayg: my collegue22:04
kota_clayg: he is working on swift tiering.22:05
hroukota_, neat !  Yea I can see why this matters a lot for them in that case.22:05
kota_and also wants to know he can use symlink earlier for tiering or not.22:05
claygoic22:06
acoleshrou: that pad says "swift is missing documentation on dos and don't due to the eventual inconsistency nature" - you want me to try to write something, somewhere?22:06
claygacoles: no!  hrou said he would do it in Japan22:06
hrouacoles, I'd love that, we actually wrote a little in house too actually ;)  But need to clean that up22:06
*** mrmoje has joined #openstack-swift22:06
hrou^^ and see I'm not saying anything differently ;)22:06
clayghrou: bah :shipit:22:06
acolesclayg: hrou i guess it'll be done...eventually :)22:07
*** achhabra has left #openstack-swift22:07
claygacoles: !!!! oh oh oh - i get it!22:07
hrouacoles, pun intended there ? ;)22:07
hrouacoles, you know what let me take the first crack at it, I'm sure you'll have a lot to add either way !22:07
*** marcusvrn_ has quit IRC22:07
hrouand we have notes.22:07
acolesactaull it wasn't intended pun, but in retrospect it's better that way22:08
*** joeljwright has quit IRC22:09
kota_hrou: to collect actual problem on symlink with fast-post, could you help me to point out the paragrah in the pad?22:10
*** ho_away has joined #openstack-swift22:10
acoleshrou: basically, "don't ever take a piece of state that a client wrote at t1 and internally store it under time t2, or t0"22:10
hroukota_, we don't actually go into detail on the problem there, let me write that up, most of the etherpad is concentrated on post-as-copy handling and how there is NOT a problem with it ;)22:10
claygacoles: but moving it to t3 is just http://hqwallbase.pw/images/medium/a-tyrannosaurus_rex_drums_nuclear_explosions_orange_wallpaper-42087.jpg22:11
kota_hrou: oic22:11
hrouacoles, way to go .. sum up 1 month of work in a single sentence .. ;) ... jk yea something like that but we go into a few use cases that are problematic (a lot of it centers around post-as-copy, which you can argue we can throw out eventually).22:11
*** ho_away has quit IRC22:12
acolesclayg: sure! t3 is a special case. anything can be made to be the real deal at t3. not t4 tho.22:12
acoleswe're joking of course, in case anyone is listening22:12
hrouof course ;)22:13
clayghrou: but... whe you say "NOT a problem [with post-as-copy]" - you mean "it's EVERY BIT AS MUCH OF A PROBLEM as post-as-copy" (right?)22:13
claygI think post-as-copy was written under the facllacy that "that will rarely happen" is different from saying "that will happen"22:13
hrouclayg, hehe yes, so to date I've been very careful to say it the way you did above ... but got lazy above22:14
hrouclayg, 100% agreed22:14
clayghrou: no problem - wanted to make sure I was following - yeah sux22:14
clayghrou: the question was about if the API could make it so post updates wrote directly to the target (instead of returning a redirect) or something22:14
hrouclayg, right which leads to an interesting conversation of, does ever post now need a head to determine if it is a symlink22:16
hrouclayg,  or is that something we do at the object server layer22:16
hroukota_, acoles - just as a reminder the current implemtnation is simply:  Post puts metadata on symlink directly, you do get/head - we get the metadata from the target and the symlnk, and return whatever is newer only.22:18
acoleshrou: but didn't we discuss that in tokyo, and that the result of a HEAD could be stale, so you may end up posting to the link anyway? (I confess I'm a little out of touch)22:18
*** trifon has joined #openstack-swift22:19
hrouacoles, yep!  It may be, but that's Ok, we're operating in the context of the information that's known at the time (its really no different than if you make an application decision as a result of a head which does something to another object), we touch on that in the etherpad22:19
kota_if we could have etag in symlink, could we use if-match for the GET/HEAD which might be stale?22:19
*** daemontool has quit IRC22:19
hroukota_, that's interesting thought !  But I think the trick there would be getting the etag in the symlink there in the first place.22:21
kota_ah, for now, seems talking about "making Symlink" process....22:21
ZyricIs there a way to simulate a large and well populated cluster that doesn't involve slowly building a large and well populated cluster (or alternatively, a fast way to produce one)?22:21
hroukota_, you could have a similar argument that the etag was stale at the time of the head we'd have to drive (to get the etag of the target object)22:21
kota_hrou: yup, e.g. if-modified-since22:23
acoleshrou: i gotta go, i'll try to get up to speed with the ether pad22:23
hroukota_, what about the case where the target doesn't exist first though ;)22:24
kota_not completely if we have a lot of handoffs with different timesatmps.22:24
hrouacoles, sure !  But I'll deffinetly add more about fast-post overall going forward.22:24
hroukota_, once you bring in the handoff situation, anything is possible, which is essentially what we get at in that ehterpad22:24
*** acoles is now known as acoles_22:24
kota_hrou:k22:25
*** diazjf has joined #openstack-swift22:25
claygZyric: I've made many an overnight run filling up develpoment/lab enivonrments of swift - let me know if you cook something up22:26
hroukota_, now mind you, by adding the etag you are in my mind changing where the problem exists (lets ignore the 404 on symlink create ... :), so the problem in this situation is if the initial etag is accurate (it may not be due to handoffs) but assuming it is, you've solved the problem on the other end of the spectrum (i.e. at post time)22:26
claygtimburke: so patch 270991 looked super simple, and it's had your +2 on it for a week - thought I'd try to help out...22:26
patchbotclayg: https://review.openstack.org/#/c/270991/ - swift - Allow IPv6 addresses/hostnames in StatsD target22:26
claygtimburke: but when I checkout master the test fails - but with a KeyError instead of the decode error I was expecting?22:27
claygtimburke: well - i guess the lp bug #1532096 is a KeyError - but it looks like a *diferent* KeyError22:28
openstackLaunchpad bug 1532096 in python-swiftclient "Error with uploading large object includes unicode path" [Undecided,In progress] https://launchpad.net/bugs/1532096 - Assigned to Jude Augustine Job (judeaugustine-j)22:28
kota_hrou: i thought we could simlar semantics with slo, if an user set an etag to "make a symlink" request, middleware can accurate it (?) not sure i am addressing right problem :22:30
kota_:/22:30
*** daemontool has joined #openstack-swift22:30
hroukota_, yes !  If you tell me the etag of the target object when you create the symlink you've just closed all sorts of holes ;)22:30
timburkeclayg: :/ i know i saw it reproduce...maybe that was when i was mucking with my own tests...22:30
claygtimburke: i have no idea what this test is doing honestly22:31
claygit mocks _upload_segment_job, then calls _upload_object_job - do our unittests maybe hide errors that the threads behind the service object are spitting out?22:31
claygdo you use ./run_tests.sh or ./.unittests or nosetests directly?22:32
hroukota_, but I'm not sure if this would work for all applications of symlink, that's a really interesting thought though !  I wonder if in your tiering case that's sufficent.  Mind you the problem you'll have with tiering is "who gives you the etag of the target" :)  If its the user great, but that doesn't make sense in tiering, it'll be "swift it self" through a head/... getting you into a similar situation.22:32
Zyricclayg, that'd be great! I need something a bit more representative to test halt/restarting object and account audits.22:32
ZyricMy development resources are a single i5 4200U 1.6-2.3GHz laptop with 8gb RAM, I'm running a Ubuntu 14.04 SAIO.22:32
claygtimburke: yeah the error i was looking for was being logged - i just needed to use nose22:32
clayghurricanerix: aren't you somehow knowing something about the testr/subunit stuff?  I *liked* nose.  I know part of that was just having spent a lot of time with it - but Ned is cool guy!22:33
kota_in my feeling, it could be because tiering agent should know which objects should be moved (i expect the agent also know the etag to prevent rollback come  from eventual consistency...)22:34
kota_not sure, need to talk with m_kazuhiro.22:34
*** admin0 has joined #openstack-swift22:35
hroukota_, yep!  It could be, so I think that'd be a neat discussion to have, it does close some holes but ... it does imply the object needs to exist first, I'm not sure if that'd be problematic for some use cases.  As far as I know other than tiering, swift3 is the other context where this is useful, you probably know the details there though ? :)22:35
timburkeclayg: would you feel better about it with something like http://paste.openstack.org/show/485203/ ?22:35
timburkethen i see testtools.matchers._impl.MismatchError: None is not KeyError(u'\u30c6',)22:36
kota_and if an user don't mind the etag (just want to link the eventual newest one), yup, symlink can set the etag from extra HEAD response (even if it's stale) for itself.22:37
timburke(plus the logging output, if run through nosetests)22:37
ZyricCould nyone give me an estimate of a good starting point for a large but manageable cluster with specs like mine? I haven't had need to make a large cluster before.22:37
*** daemontool_ has joined #openstack-swift22:37
kota_that's same sematics wiht SLO22:37
hroukota_, at symlink creation time we just drive a head always IFF we don't have an etag .. gotcha !22:37
kota_need more eyes, anyway :)22:38
timburkethanks clayg!22:39
*** daemontool has quit IRC22:39
hroukota_, there are more complications like say I intentionally re-put the target, I'd have to update that somehow22:39
*** trifon has quit IRC22:39
kota_hrou: how about to use X-Timestamp?22:39
hroukota_, and if its stale re-drive the head to get a new etag ?22:40
kota_maybe no, just put as old object though it might be removed soon.22:41
kota_as eventual consitency22:41
hroukota_, Right but I don't think that's accurate unless you operate under an assumption that customers never intentionally re-put the target (and expect the symlink to keep working after)22:42
kota_you said about "un-intentionally re-put"?22:43
claygtimburke: ohhhhh - yeah problaby22:44
*** asettle-afk has joined #openstack-swift22:44
hroukota_, ah no sorry I meant *intentionally* :)22:44
timburkeclayg: some day when i have too much free time i should go add that to pretty much all of the tests...22:44
claygtimburke: so you really can't get the logging on faiure automatically from testr?22:44
claygtimburke: or more likely just no one knows *how*22:45
timburkemore likely22:45
claygtimburke: hell i don't even know how to run a just a single test?22:45
hroukota_, this is probably why at some point we just thought "failing post" would just be easier ;)22:45
*** asettle-afk is now known as asettle22:45
claygwhere rcollins when you want to give him grief!22:45
clayghrou: not "fail" so much as return a 3XX22:45
hrouclayg, or that !  Let the application handle it22:46
kota_clayg: or 202(?) with stale X-Timestamp22:46
clayghrou: besides doesn't tiering need PUT's to be poxied to the target too?  why does it matter if the POST is proxied automatically if it's going to have to intercept PUT's anyway?22:46
claygkota_: 2XX would only make sense to me if the transformation was persisted in the system in some way - I haven't been keeping up with the whole conversation22:47
timburkeclayg: something like this mostly works: tox -e py27 -r '.*test_upload_object_job_file_with_unicode_path'22:47
timburke-r for regex22:47
timburkeor something22:47
claygmaybe22:47
hrouclayg, that'd be an interesting question for m_kazuhiro i.e. how do they envision tiering working utilizing this symlink implemntation.  I've had chats with folks where no, the idea was not to have PUTs hit the object on the colder tier, but rather operate almost akin to symlinks today22:47
claygi best I still like nose better22:48
clayghrou: oh right - no that makes sense22:48
hrouthat is PUT overwrites symlink, and someone else cleansup the tier'd object at some point.22:48
hrouclayg, both can !  Really, that's why desinging symlink for all possible use cases gets complicated :)22:48
timburkeclayg: ditto. i generally just use nose, then tox when i'm reasonably content that it'll actually behave as expected in all envs22:49
hroukota_, yea I'm not sure I like 2xx really22:49
hroukota_, because that's not what took place, the post is lost from the context of the target object, and remember that's all this application knew about in the first place.22:50
kota_i like to bet the cleanup process in the out of symlink scope for simplyfying.22:50
hroukota_, I'm liking 3xx more though now that I think about it, any thoughts on that ?22:50
hroukota_, i.e. fail posts period, but give the application a chance to handle it.22:51
hrou307 maybe22:52
kota_interesting22:54
kota_or 301?22:55
hroukota_, maybe I was afraid that would cause the application to route all further requests (get/put/head) to that URI which isn't quite what we want.22:57
timburkekota_: 307. maybe 302, but i like that the method is (supposed to be) the same. 301 tends to be cached, potentially for a while22:57
hroutimburke, right exactly !  which takes care of my concern above.22:58
kota_or just returning 404 with informational headers (e.g. was liked to xxxx)?22:58
hroukota_, :)  Sure that was the original plan actually, well some error / 404 code.22:58
kota_(or informational bodies)22:58
*** daemontool has joined #openstack-swift22:58
hrouwe were going to return the X-symlink-target-* headers yep22:59
kota_hrou: sorry, i'm running out of time to be here, for now.22:59
hroukota_, me too :) Its Ok, you're going to the hackathon right ? Unfortunetly I don't think I can make it, it'd be nice to touch base before so a conversation can be had about this up there (I think the "up" is applicable for most folks ;).23:00
timburkeif we're going 4xx, i vote 409 or 40023:00
kota_hrou: i'll be online again in 2 hours, it would be nice to update the etherpad with tthis conversation (and your thought) :)23:00
*** haomaiwang has quit IRC23:01
kota_hrou: yup, i'll be there.23:01
*** haomaiwa_ has joined #openstack-swift23:01
*** daemontool_ has quit IRC23:01
*** diazjf has quit IRC23:01
hroukota_, awesome, Ok sounds good I'll update this again and we'll talk more about this;  Thanks for all the input !23:02
*** km has joined #openstack-swift23:08
*** ho_away has joined #openstack-swift23:13
*** ho_away has quit IRC23:17
*** chlong has quit IRC23:18
*** admin0 has quit IRC23:21
*** mragupat has quit IRC23:22
*** kei_yama has joined #openstack-swift23:28
*** chlong has joined #openstack-swift23:30
*** dmorita has quit IRC23:31
*** asettle is now known as asettle-afk23:31
*** dmorita has joined #openstack-swift23:32
*** nadeem has quit IRC23:36
*** blmartin has quit IRC23:41
*** mingdang1 has joined #openstack-swift23:47
*** klamath has quit IRC23:53

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