Thursday, 2015-07-23

hocode is here: https://github.com/andrewgaul/object-store-comparison00:00
notmynamehere's runabove /info https://gist.github.com/notmyname/4c1ff71bf7129bf29c5500:00
notmynameho: I know him!00:00
honotmyname: cool!00:01
notmynameactually clayg and I had coffee with him a moth or so ago00:01
claygyeah those guys are cool - SF is such a weird place00:02
claygsaw this guys thing on HN this morning -> https://github.com/begriffs/postgrest#performance00:03
clayglike the joke about slow dynamic lanuages - i should totally look him up - but won't00:03
claygwho writes real thing in Haskell!?00:04
hoyeah, SF is best place for software engineer. i'm jealous.00:05
*** bill_az has joined #openstack-swift00:06
notmynamewow. I have a voucher code for OVH. it has a zero, and both capitol and lower letter "oh". isn't that exactly what you aren't supposed to do?00:06
occupantone time I heard two canadians on a bus talking about their decision to move to SF. One of 'em said "I mean, what would I have done back home? Work for Blackberry?" and then they just laughed for like 30 seconds00:10
notmynamelol00:10
notmynamethe other day on the bus/train in SF I met a guy who work at ta company who's product is built on swift. pretty cool00:12
notmyname(https://www.bigcommerce.com)00:12
occupantwhere you work? you one of the actual rackspacers?00:13
notmyname"actual" rackspacers?00:15
claygnotmyname: you're not an *actual* racker - you're an ex-racker - big diference00:15
claygdfg_: redbo: ahale: and mattoliverau are *actual* rackspacers00:16
occupantmy apartment is like a block away from the office. you guys would covet hard.00:16
notmynameand glange and hurricanerix00:16
claygand prometheanfire when he's around00:16
claygnotmyname: oh and scotticus !00:16
notmynameoccupant: ah, cool. clayg and me work at swiftstack. we used to be in south part00:16
claygoccupant: but none of them work at 2nd & Folsom00:16
claygwe used to have a... yeah right over there00:16
notmynamenow we're next to the montgomery bart station00:16
occupantyup, I'm at 1st and folsom on the same street as that gigantic high rise they're building00:17
occupantI thought they were just going to build another five story condo like everything else on the block. I was really surprised when it kept going up and up.00:17
claygwe're all snobby in the FiDi now00:17
notmynameclayg: at half the rent of SoMA00:18
notmynamewell, not *half*, but significantly less00:18
claygyou know how like twice of nothing is still nothing - rent in SF works the same way but on the other end - half of infinity...00:19
occupantmy roomies and I are in a 3br rent control for $3300, which is pretty amazing for the location.00:23
*** mahatic_ has joined #openstack-swift00:27
notmynametime for me to head home00:27
*** mahatic_ has quit IRC00:28
*** nadeem has quit IRC00:30
*** ndk has quit IRC00:32
*** gyee has quit IRC00:33
*** SkyRocknRoll has quit IRC00:36
*** ndk has joined #openstack-swift00:38
*** jlhinson has quit IRC00:42
*** jasondotstar has quit IRC00:47
*** SkyRocknRoll has joined #openstack-swift00:48
*** SkyRocknRoll has joined #openstack-swift00:48
*** jasondotstar has joined #openstack-swift00:49
*** DericHorn-HP has joined #openstack-swift00:49
*** chlong has quit IRC00:52
*** jasondotstar has quit IRC00:54
claygnotmyname: idk, I don't think I'm happy with the async update patch yet - i'm doing something wrong :'(00:56
claygnotmyname: on my master test with some misbehaving standins for a couple of priamry containers I see put requests all over the place 0.5 - 3.5 - but on the async patch they're all like 1.7?00:57
claygmaybe i'm tired/distracted00:57
claygi'm going to break for dinner and try again later00:58
*** ho_ has joined #openstack-swift01:11
*** kota_ has quit IRC01:12
*** haomaiwang has quit IRC01:12
*** ho has quit IRC01:12
claygphew ok - there finally got it01:44
*** wbhuber has joined #openstack-swift01:49
*** EmilienM|off is now known as EmilienM01:52
*** ho has joined #openstack-swift01:52
*** ho_ has quit IRC01:53
*** ho has quit IRC01:54
*** Nyny has quit IRC01:55
*** ho has joined #openstack-swift01:57
*** thurloat is now known as thurloat_isgone01:58
*** shangxdy has joined #openstack-swift02:00
*** wbhuber has quit IRC02:03
*** chlong has joined #openstack-swift02:11
*** kota_ has joined #openstack-swift02:11
*** ChanServ sets mode: +v kota_02:11
*** DericHorn-HP has quit IRC02:17
*** janonymous has quit IRC02:19
*** annegentle has quit IRC02:28
openstackgerritClay Gerrard proposed openstack/swift: Cleanup nits from container_update_timeout  https://review.openstack.org/20481302:32
claygnice work notmyname!02:33
*** annegentle has joined #openstack-swift02:33
claygkota_: so why in patch 201055 can't we move the fix_response_headers to not try and "fix" the error responses?02:35
patchbotclayg: https://review.openstack.org/#/c/201055/02:35
*** DericHorn-HP has joined #openstack-swift02:38
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419602:55
*** silor has joined #openstack-swift02:55
*** bill_az has quit IRC03:09
*** shangxdy has quit IRC03:16
*** annegentle has quit IRC03:17
*** sanchitmalhotra has joined #openstack-swift03:21
openstackgerritMerged openstack/swift: unit tests: Replace "self.assert_" by "self.assertTrue"  https://review.openstack.org/20409203:25
openstackgerritMerged openstack/swift: Removing commented out code in test/unit/account/test_backend.py  https://review.openstack.org/20457503:26
*** DericHorn-HP has quit IRC03:40
jrichliclayg: all the gory details are there https://etherpad.openstack.org/p/swift_encryption_issues03:41
*** jrichli has quit IRC03:43
*** ppai has joined #openstack-swift03:47
*** annegentle has joined #openstack-swift03:48
peluseclayg, you don't recall and recent bugs and/or fixes for FI of None being passed in to validate_fragment_index() do you (would result in the old 'None: invalid literal for int() with base 10')03:52
*** jrichli has joined #openstack-swift03:57
*** jrichli has quit IRC04:00
*** annegentle has quit IRC04:09
*** HenryG has quit IRC04:09
*** mordred has quit IRC04:11
*** HenryG has joined #openstack-swift04:12
*** mutoulbj has joined #openstack-swift04:18
*** mordred has joined #openstack-swift04:24
jith_Hi all, i have configured the swift (SAIO) for devstack and used the seperate swift(SAIO) for glance backend.. but in horizon->system information , all the services are getting listed but the ip address and Enabled status of swift is not there.. how to make enable in horizon? Also i am getting error while creating the instance "Failed to allocate the network(s), not rescheduling."04:35
*** DericHorn-HP has joined #openstack-swift04:39
mattoliveraujith_: I'll predicate again with I'm not a devstack expert, but horizon uses the keystone catelog, so you need to make sure you have added the swift endpoint to keystone.04:41
*** Kennan has quit IRC04:41
*** Kennan has joined #openstack-swift04:42
jith_mattoliverau: That i have done.. thanks...  Any idea about this error "Failed to allocate the network(s), not rescheduling."04:42
mattoliveraujith_: sounds like a neutron or nova-network problem (depending on what your using for networking)04:44
jith_mattoliverau: Thanks... I am using neutron04:44
*** DericHorn-HP has quit IRC04:53
claygpeluse: nothing comes to mind - is it on the branch where the GET path now includes a frag-index?04:55
*** zaitcev has quit IRC05:03
claygtorgomatic: so If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz" - is a thing, so I sorta think X-If-Not-Frag-Index will work with a plain old etag based If-Match header05:05
claygAnd X-If-Not-Frag-Index just sends down the list of all the fi's we're already got connections for05:06
*** bkopilov has quit IRC05:11
*** bkopilov has joined #openstack-swift05:13
*** DericHorn-HP has joined #openstack-swift05:25
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419605:32
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419605:33
*** DericHorn-HP has quit IRC05:41
*** hrou has quit IRC05:50
*** SkyRocknRoll has quit IRC05:51
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC range GET/COPY handling  https://review.openstack.org/20489205:56
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC range GET/COPY handling  https://review.openstack.org/20489206:00
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Imported Translations from Transifex  https://review.openstack.org/20491406:11
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC range GET/COPY handling  https://review.openstack.org/20489206:11
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix the missing SLO state on fast-post  https://review.openstack.org/18256406:30
*** ppai has quit IRC06:31
*** mahatic has joined #openstack-swift06:36
*** krypto has joined #openstack-swift06:36
kryptocan swift be installed on 2 servers with 2 replicas06:40
kryptowill there be any impact on uploads if one of the server goes down06:41
*** ppai has joined #openstack-swift06:41
kota_krypto: we can make the setting but I guess it is not recommended.06:42
kryptokota_ thanks so will 3 replicas with 3 server provide high data availability06:43
kota_krypto: the upload impact when one of the servers down depends on # of disks in the server.06:44
kota_krypto: yes, high durability and availability.06:44
kryptothanks +kota_06:45
kota_if each server has more than 1 disk, swift can store the 2 replica when the one of the servers down.06:45
kota_into unique 2 disks.06:45
kryptoi have a server with 2 disks in raid 106:46
*** ppai has quit IRC06:46
kryptototal 3 servers like this06:46
kota_well, assuming, if just 1 disk attached to Swift in each server and there are 2 servers and config as 2 replica06:47
kota_when one of them is shutdown, anyone uploads objects anymore.06:48
kota_if 3 servers and 2 replica we can upload objects until two of them halted.06:49
*** chlong has quit IRC06:49
*** ppai has joined #openstack-swift06:50
mattoliveraukrypto: 2 replica on 2 servers (one drive each) wont work well, if one is down all puts will fail as a qourum for replication is (repl /2) +1.. so 2.06:50
mattoliverauSo what kota_said :)06:50
kota_mattoliverau: nice, additional info :D06:51
mattoliverauswift will handle your durability for you, so better to give it more disks (i.e. jbod). As kota_ said 3x servers if a drive each is better. but even better would be multiple drives per server :)06:52
kryptothanks +kota_ and +mattoliverau for helping me with this much information. I will be using 3 servers with 2 replicas and let me try if i can get more disks :)06:54
mattoliverauso instead of using raid 1 to save your files, you could split it, add them all to swift and up the replica count.. but that obviously leaves your system more vulnrable (if its living on the raid1)06:55
mattoliveraukrypto: your welcome06:55
*** jasondotstar has joined #openstack-swift06:55
kota_krypto: :-)06:56
*** SkyRocknRoll has joined #openstack-swift07:05
*** rledisez has joined #openstack-swift07:09
*** proteusguy has quit IRC07:14
*** proteusguy has joined #openstack-swift07:27
*** vinsh_ has joined #openstack-swift07:29
*** vinsh has quit IRC07:31
*** zhill_desktop has quit IRC07:31
*** zhill_desktop has joined #openstack-swift07:33
*** vinsh has joined #openstack-swift07:36
*** vinsh_ has quit IRC07:36
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC range GET/COPY handling  https://review.openstack.org/20489207:58
*** vinsh_ has joined #openstack-swift07:58
*** vinsh has quit IRC07:59
*** vinsh has joined #openstack-swift07:59
*** jistr has joined #openstack-swift08:02
*** mahatic has quit IRC08:02
*** mahatic has joined #openstack-swift08:02
*** vinsh_ has quit IRC08:03
*** jordanP has joined #openstack-swift08:07
*** geaaru has joined #openstack-swift08:10
*** mahatic_ has joined #openstack-swift08:11
*** proteusguy_ has joined #openstack-swift08:12
*** proteusguy_ has quit IRC08:12
*** proteusguy has quit IRC08:13
*** SkyRocknRoll has quit IRC08:13
*** mahatic has quit IRC08:13
*** Kennan has quit IRC08:26
*** SkyRocknRoll has joined #openstack-swift08:26
*** Kennan has joined #openstack-swift08:26
openstackgerritMerged openstack/swift: Add two functional tests for delimiter.  https://review.openstack.org/20230308:28
*** haomaiwang has joined #openstack-swift08:34
*** proteusguy has joined #openstack-swift08:48
*** sanchitmalhotra1 has joined #openstack-swift08:55
*** sanchitmalhotra has quit IRC08:57
*** aix has joined #openstack-swift09:02
*** kota_ has quit IRC09:07
*** sanchitmalhotra has joined #openstack-swift09:08
*** sanchitmalhotra1 has quit IRC09:10
*** peterbusque has quit IRC09:15
*** marzif_ has joined #openstack-swift09:22
*** marzif_ has quit IRC09:23
*** marzif_ has joined #openstack-swift09:24
*** marzif_ has quit IRC09:24
*** marzif_ has joined #openstack-swift09:25
*** jasondotstar has quit IRC09:25
*** mahatic__ has joined #openstack-swift09:26
*** marzif_ has quit IRC09:30
*** mahatic_ has quit IRC09:30
*** silor has quit IRC09:32
openstackgerritOndrej Novy proposed openstack/swift: Time synchronization check in recon.  https://review.openstack.org/19256209:35
*** jasondotstar has joined #openstack-swift09:38
*** sanchitmalhotra1 has joined #openstack-swift09:42
*** jasondotstar has quit IRC09:43
*** sanchitmalhotra has quit IRC09:43
*** sanchitmalhotra has joined #openstack-swift09:49
*** sanchitmalhotra1 has quit IRC09:51
*** sanchitmalhotra1 has joined #openstack-swift09:56
*** sanchitmalhotra has quit IRC09:58
mahatic__mattoliverau, hello! did you happen to set up encryption?10:00
*** jasondotstar has joined #openstack-swift10:31
*** geaaru has quit IRC10:31
*** silor has joined #openstack-swift10:37
*** pksingh has joined #openstack-swift10:37
*** silor1 has joined #openstack-swift10:39
pksinghHi folks, clayg , cschwede , swifterdarrell , torgomatic , could you please review https://review.openstack.org/185061 and https://review.openstack.org/183899, these are there from very long time , thanks in advance :)10:40
*** silor has quit IRC10:42
*** geaaru has joined #openstack-swift10:44
*** silor1 has quit IRC10:44
*** joeljwright has joined #openstack-swift10:45
*** ChanServ sets mode: +v joeljwright10:45
*** krypto has quit IRC10:56
*** chlong has joined #openstack-swift11:08
*** silor has joined #openstack-swift11:10
peluseclayg, wrt the Non fi question - no its something our bencmarking guys ran into in their testing.  Getting more info...11:11
*** sanchitmalhotra has joined #openstack-swift11:17
*** thurloat_isgone is now known as thurloat11:19
*** sanchitmalhotra1 has quit IRC11:19
*** sanchitmalhotra1 has joined #openstack-swift11:22
*** marzif has joined #openstack-swift11:23
*** sanchitmalhotra has quit IRC11:24
*** aix has quit IRC11:27
*** sanchitmalhotra has joined #openstack-swift11:33
*** robefran has quit IRC11:35
*** robefran_ has joined #openstack-swift11:35
*** sanchitmalhotra1 has quit IRC11:35
*** kutija has quit IRC11:35
*** daemontool_ has joined #openstack-swift11:36
*** daemontool_ has quit IRC11:36
*** daemontool_ has joined #openstack-swift11:37
*** kutija has joined #openstack-swift11:38
*** ppai has quit IRC12:00
*** jasondotstar has quit IRC12:11
*** ppai has joined #openstack-swift12:12
*** robefran_ has quit IRC12:13
*** ho has quit IRC12:15
*** thurloat is now known as thurloat_isgone12:16
*** kei_yama has quit IRC12:18
*** tongli has joined #openstack-swift12:18
*** tongli has quit IRC12:22
*** km has quit IRC12:24
*** aix has joined #openstack-swift12:28
*** tongli has joined #openstack-swift12:28
*** ppai has quit IRC12:30
*** dmorita has quit IRC12:33
*** janonymous has joined #openstack-swift12:43
*** ppai has joined #openstack-swift12:43
janonymousHi All, Please find some links for reviews : https://review.openstack.org/#/q/owner:self+status:open+project:openstack/swift,n,z  :)12:52
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873612:54
*** robefran has joined #openstack-swift12:54
haypojanonymous: i don't think that your link is right. "owner: self"12:59
*** robefran has quit IRC13:03
*** mahatic__ has quit IRC13:05
*** mahatic__ has joined #openstack-swift13:06
janonymousohh..ryt..13:13
janonymouswait13:13
*** annegentle has joined #openstack-swift13:14
janonymousPy3 Link : https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z13:14
janonymousMy previous link has an additional bandit topic feature as well..13:14
janonymoushaypo: hey13:15
janonymousWhat's the progress about voting py3 gate ...13:16
janonymousIs there something i could do for that?13:16
*** jasondotstar has joined #openstack-swift13:30
*** annegentle has quit IRC13:36
*** hrou has joined #openstack-swift13:36
*** annegentle has joined #openstack-swift13:36
*** SkyRocknRoll has quit IRC13:41
*** ppai has quit IRC13:43
*** robefran has joined #openstack-swift13:45
*** DericHorn-HP has joined #openstack-swift13:49
haypojanonymous: i updated https://review.openstack.org/#/c/200416/13:52
haypojanonymous: my python pull request was merged into pyeclib, i'm waiting for a a release13:52
haypojanonymous: we need these two stuff to port swift to python 313:53
janonymousYes.13:54
*** bill_az has joined #openstack-swift13:55
*** jrichli has joined #openstack-swift13:56
*** SkyRocknRoll has joined #openstack-swift13:57
*** dgrauet has joined #openstack-swift13:58
*** mahatic__ has quit IRC13:58
*** mahatic__ has joined #openstack-swift13:59
*** wbhuber has joined #openstack-swift14:03
mahatic__jrichli: good morning. got a min?14:04
jrichlimahatic__: hello.  sure14:04
mahatic__jrichli: http://paste.openstack.org/show/401160/ - you gave me that yesterday. When I dig into failures when I ran, on a test like this "test.functional.test_object.TestObject" most of them are failing with AssertionError14:06
*** lpabon_ has joined #openstack-swift14:06
*** lpabon_ has quit IRC14:06
*** lpabon has quit IRC14:07
mahatic__jrichli: but from your paste, only few are failing from that test. I'm not quite sure. I did check that I have the code you pointed to me and the proxy-config right14:07
mahatic__jrichli: any thoughts on that?14:07
jrichlimahatic__: I suggest picking the first one that fails on your list that is not on mine, and debugging to find out why the assertion fails14:08
mahatic__sure14:08
mahatic__jrichli: I wanted to check that I'm not missing any extra code or config options14:08
jrichlimahatic__: I have told you all that I know of.  The proxy config that I sent to you is all you need beyond the code from the last patch.  So I am afraid that debugging is the only way we can find out what is happening.14:10
mahatic__alright14:10
jrichlidid you start with a clean cluster?14:11
jrichliwhen is the last time you did a "resetswift"?14:11
jrichlimahatic__ ^^14:12
mahatic__jrichli: hey, sorry. yesterday :)14:13
*** zul has quit IRC14:14
jrichlimahatic__: great.  So, did you run 'sudo python setup.py develop' and 'sudo python setup.py install'?14:15
mahatic__jrichli: yup all that done14:17
*** jlhinson has joined #openstack-swift14:17
mahatic__jrichli: i'm looking at the errors. Will get back if I find something weird14:18
jrichlimahatic__: ok.  I am looking at some things too.14:20
*** rbrooker has joined #openstack-swift14:20
jrichlimahatic__: I am looking at the failures in the automated tests in the reviews.  But I assume these are different than what you would get.14:21
jrichlimahatic__: for instance, there are problems there because "Unable to read test config /etc/swift/test.conf - file not found"14:22
jrichlimahatic__: be sure to look at the error logs14:22
mahatic__jrichli: oh okay. Let me cross check14:24
*** zul has joined #openstack-swift14:27
jrichlimahatic__:  I also assume you would have different errors than the automated tests because they aren't setup to use encryption middleware yet14:28
mahatic__jrichli: yeah, I thought so14:29
jrichlimahatic__: Actually, that does bring up a good idea.  Maybe you should change back to a normal pipeline first and then run the functests.  they should be successful then.14:30
jrichlithat should isolate the errors that are not due to encryption middleware14:30
mahatic__jrichli: I did run the functests when I first set up SAIO and they were successful14:31
jrichliwhen was that?14:31
mahatic__which is last week I believe14:31
*** briancurtin has quit IRC14:31
*** briancurtin has joined #openstack-swift14:31
jrichlibut you have a new code set now14:31
jrichliso trying the normal pipeline is worth a spin14:31
mahatic__jrichli: yeah, but what did you mean by normal pipeline? without the encryption stuff?14:32
jrichliyes.  just comment out your pipeline, and add back the line without the new middleware.14:33
mahatic__okay14:34
*** lpabon has joined #openstack-swift14:36
*** marzif has quit IRC14:43
*** marzif has joined #openstack-swift14:44
*** annegentle has quit IRC14:56
*** nadeem has joined #openstack-swift14:58
*** nadeem has quit IRC15:00
*** Fin1te has joined #openstack-swift15:01
*** mahatic has joined #openstack-swift15:02
*** mahatic__ has quit IRC15:05
*** minwoob has joined #openstack-swift15:09
*** daemontool_ is now known as marzif_15:10
*** jasondotstar has quit IRC15:12
*** david-lyle has joined #openstack-swift15:17
*** dgrauet has quit IRC15:17
*** nadeem has joined #openstack-swift15:18
*** annegentle has joined #openstack-swift15:18
*** annegentle has quit IRC15:18
*** annegentle has joined #openstack-swift15:19
*** marzif_ has quit IRC15:28
*** rbrooker has quit IRC15:30
*** mutoulbj has quit IRC15:33
*** mahatic_ has joined #openstack-swift15:37
*** mahatic has quit IRC15:37
*** rbrooker has joined #openstack-swift15:38
*** jasondotstar has joined #openstack-swift15:45
*** DericHorn-HP has quit IRC15:52
*** zhiyan has quit IRC15:58
*** zhiyan has joined #openstack-swift15:58
*** rledisez has quit IRC16:00
*** jistr has quit IRC16:01
*** marzif has quit IRC16:02
*** SkyRocknRoll has quit IRC16:04
pelusehttp://newsroom.intel.com/community/intel_newsroom/blog/2015/07/23/intel-announces-cloud-for-all-initiative-to-deliver-benefits-of-the-cloud-to-more-businesses16:06
*** jordanP has quit IRC16:08
*** rbrooker has quit IRC16:12
notmynameinteresting16:12
*** serverascode has quit IRC16:14
*** marzif has joined #openstack-swift16:15
notmynamescotticus: are your teams part of this? ^16:16
*** serverascode has joined #openstack-swift16:16
*** jordanP has joined #openstack-swift16:17
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265716:20
*** breitz has quit IRC16:28
*** breitz has joined #openstack-swift16:28
*** nottrobin has quit IRC16:29
*** nottrobin has joined #openstack-swift16:29
redbomark16:31
redbooops I meant /mark16:32
openstackgerritChristian Schwede proposed openstack/python-swiftclient: Revert "Update mock requirements"  https://review.openstack.org/20515016:35
*** aix has quit IRC16:37
*** silor has quit IRC16:38
*** blmartin has joined #openstack-swift16:42
cschwedetimburke: please have a look at that patch if you have a second or two^^16:42
*** Fin1te has quit IRC16:46
*** jordanP has quit IRC17:01
*** jasondotstar has quit IRC17:03
*** DericHorn-HP has joined #openstack-swift17:18
clayghonestly that rax/intel thing sounds kinda cool - kudos!17:25
*** mahatic has joined #openstack-swift17:31
*** mahatic_ has quit IRC17:35
*** mahatic has quit IRC17:36
*** CaioBrentano has joined #openstack-swift17:37
*** mahatic has joined #openstack-swift17:43
*** marzif has quit IRC17:45
minwoobJust out of curiosity, it seems that most distributed storage system alternatives (such as Ceph, GlusterFS, Lustre, etc) are written in C/C++.17:46
minwoobWere there some reasons originally, for Swift's python origins?17:46
MooingLemurPretty sure it was OpenStack in general17:47
redboWell swift predates openstack by a year or so.  Mostly we just all liked python.17:48
minwoobMooingLemur: Swift was designed/implemented before that, no?17:48
MooingLemuraha, wasn't sure about that17:48
*** janonymous has quit IRC17:51
minwoobredbo: Yeah, it makes me wonder in the other direction, actually -- as to why the others weren't initially implemented using Python like Swift.17:54
redboI don't know.  I'm not so hot on python these days.  Its refusal to acknowledge the existence of multi-core processors makes for a lot of challenges.17:58
minwoobredbo: That's true.18:11
*** eandersson has quit IRC18:11
*** Fin1te has joined #openstack-swift18:13
claygminwoob: I think some of it at least must have had something to do with swift picking *web* storage - ended up with api-systems/web-services guys that knew http and python?  other storage systems started in kernal modules and research projects with contributions from people with old storage/file-system backgrounds?18:16
claygI honestly can't understand why people write things in c++ on purpose.  c sure - but c++ seems more like "I like c, but it takes a frustrating amount of time to do anything useful, and I'm not really going to explore other options - so I'll pretend like learning c++ is a thing that you do a lifetime!"18:17
*** Fin1te has quit IRC18:20
*** geaaru has quit IRC18:28
minwoobclayg: So you're suggesting, perhaps that their rationale for c/c++ wasn't for the performance reasons one would initially suspect, but rather because they had built up a proclivity towards it?18:28
notmynameI'd guess that most projects use a particular language because that's what the original devs were comfortable with18:29
*** hrou has quit IRC18:30
*** hrou has joined #openstack-swift18:30
minwoobnotmyname: Right.18:31
openstackgerritMichael Barton proposed openstack/swift: go: allow profiling  https://review.openstack.org/20523218:49
openstackgerritMichael Barton proposed openstack/swift: go: goroutine leak  https://review.openstack.org/20523418:50
*** sanchitmalhotra1 has joined #openstack-swift18:53
*** bitblt has joined #openstack-swift18:55
*** sanchitmalhotra has quit IRC18:55
*** bitblt has quit IRC18:58
*** DericHorn-HP has quit IRC19:13
*** petertr7_away is now known as petertr719:24
claygredbo: nadeem: ^ FASCINATING!19:26
nadeemGo Profiler is fun :)19:28
claygoohhhhhh - topic for the hackathon?!19:28
nadeemI am still on waitlist for hackathon.19:29
notmynameshouldn't be19:29
claygnotmyname: ^ fix this19:29
nadeemhowever redbo will be there I guess19:29
notmyname"still". you signed up today19:29
nadeemyep sorry I was late :)19:30
claygnadeem: redbo's not that great19:30
*** mahatic has quit IRC19:30
*** annegentle has quit IRC19:37
*** jlhinson_ has joined #openstack-swift19:39
*** jlhinson has quit IRC19:39
*** DericHorn-HP has joined #openstack-swift19:40
*** Fin1te has joined #openstack-swift19:42
*** DericHorn-HP has quit IRC19:44
*** DericHorn-HP has joined #openstack-swift19:45
*** wer has quit IRC19:51
*** wer has joined #openstack-swift19:55
*** minwoob_ has joined #openstack-swift20:00
redbono argument20:02
*** minwoob has quit IRC20:02
*** annegentle has joined #openstack-swift20:09
*** blmartin has quit IRC20:10
*** blmartin has joined #openstack-swift20:10
*** annegentle has quit IRC20:11
*** DericHorn-HP has quit IRC20:12
*** annegentle has joined #openstack-swift20:12
*** annegentle has quit IRC20:13
*** annegentle has joined #openstack-swift20:13
*** petertr7 is now known as petertr7_away20:17
*** petertr7_away is now known as petertr720:20
clayglol20:32
*** zhill has joined #openstack-swift20:35
claygok, what's worth reviewing today?20:38
claygtdasilva: merge conflict!?20:38
tdasilvaclayg: yeah...just noticed that...haven't tried a rebase just yet, but will in a bit...working on the matrix test atm20:40
claygtdasilva: did we ever decide how we think manifests and segments in containers with versions turned on are *supposed* to work - is there any functional tests that prove it?20:40
claygtdasilva: oh yeah :'(20:40
tdasilvaclayg: check it out: https://docs.google.com/spreadsheets/d/1hyo3Q7SS70kG0ZCR3NvXJZ6ikeqqQ04RcRYjOLb44m8/edit?usp=sharing20:40
claygtdasilva: yeah I think that's the ticket!20:41
claygtdasilva: oic "container configuration" refers to the option in the container server *config*20:42
tdasilvaclayg: yeah, let me try to make that clear20:42
claygtdasilva: there's another vector that has to do with a container that has x-version-location stored in it directly (true/false)20:42
tdasilvaclayg: "directly"???20:43
tdasilvaclayg: not sure what you mean by that20:43
claygtdasilva: when you turn on the container server option and then post x-versions-location to a a container - the container db gets a metadata value for "x-versions-location" instead of "x-sysmeta-versions-location"20:44
tdasilvaright, ok, that's what i thought...so yeah..that is sort of implicit on that matrix, I was trying to figure out how to call that out20:45
claygtdasilva: like one of the weird cases was when you have a container with x-versions-location then you upgrade and turn on the middleware and change x-sysmeta-versions-location and then turn off th emiddleware :\20:45
claygi mean on one hand - screw 'em - dont' turn off the middleware after you turn it on (or turn of the container you jerk) - but OTOH i guess it sucks for you?20:46
claygtdasilva: or does the thing that sets x-sysmeta-versions-location always set x-versions-location?20:47
tdasilvayeah, if you turn on middleware, then turn off, it's OFF, no?20:47
clayg^ cause that acctually seems pretty sweet20:47
claygno middleware off depends on the container server setting?20:48
tdasilvacrap this thing is confusing :/20:48
tdasilvalooking...20:48
claygI mean I think I like documenting that once you turn on the middleware you should turn off the container and you can't ever turn versions on the container back on20:48
clayglike you turn on or off versions - but you *have* to use the middleware once you turn it on - and you MUST turn off the container option20:49
tdasilvayeah, once you decide to move over to the middleware, stick with it20:49
claygidk, maybe just something a doc would be good enough20:49
claygtdasilva: yeah I think once you turn on the middleware - as long as you turn off the container - you're fine20:50
claygthe only time you should ahve container on if you have middleware off20:50
clayg^ there that's it20:50
claygou could dfg_: ou20:50
tdasilvaclayg: that certainly simplifies the code20:53
clayghow so?20:54
tdasilvaclayg: like you said, then we don't have to handle the case of the user turning middleware on and off and still expecting things to work20:58
claygtdasilva: ah yeah - so we should document that20:58
tdasilvaclayg: the other thing i need to look into is mattoliverau question about where to place in the pipeline...which also deals with your question about dlo/slo21:01
*** annegent_ has joined #openstack-swift21:02
claygok, so maybe we have columns: "container-server-config-off & middleware-off", "container-server-config-on & middleare-off", "container-server-config-off & middleware-on"21:02
claygtdasilva: that's why I asked21:02
claygtdasilva: about slo21:02
claygtdasilva: i *thought* in some swift meeting you were like "how is this supposed to work" and we all said "you tell us!"21:03
claygmaybe that was acoles_away?21:03
claygtdasilva: anway given those columns you could enumerate a matrix for all the combinations of x-versions-location & x-container-sysmtea-versions-location21:04
*** annegentle has quit IRC21:05
claygtdasilva: like another weird one was "turn on x-versions-locations, turn on middleware, change x-sysmeta-versions-location, remove x-sysmeta-versions-location"21:05
*** robefran has quit IRC21:05
tdasilvaclayg: yeah, basically I was trying to keep the same behavior at is now and then if we think we need change the behavior we should do it in a separate patch21:05
claygI suppose we could enumerate "container-server-config-on & middleware-on" as *not recommended*21:06
claygtdasilva: +1000000 to don't change it in this patch!21:06
claygtdasilva: was mattoliverau suggesting a change or enumerating a difference?  that's why I asked about "what's expected and what's tested"21:06
tdasilvaclayg: hehehe...don't want this thing going to 100 patchsets :D21:06
claygtdasilva: god help us21:06
tdasilvaclayg: what I can say is I don't think even current behavior is not very good21:07
tdasilvaclayg: especially when it comes to versioning and slo and deleting segments and what not...21:08
claygtdasilva: ok, current behavior sucks so bad it's not worth testing?21:08
claygtdasilva: i just... if we change it we have to justify it - i mean... I don't want to make it worse?  idk - i feel like the risk of breaking a client that is getting something out of the current behavior is enough of a reason to justify tests to enumerate what the current behavior is21:09
claygif we don't have those tests then either mattoliverau or I could write them21:09
tdasilvaclayg: no, what I mean is that there isn't even automated testing for it, I think it might be something that's been overlooked??? maybe???21:09
claygtdasilva: +1000 overlooked!21:09
claygtdasilva: maybe the fact that it's lasted this long with no bug reports meaning no one is using it21:10
tdasilvaclayg: yeah yeah, i agree with adding those tests and then we try to keep the behavior the same, I think that would be good. Then in a future work, we move to how we think things should work21:10
claygtdasilva: if we've managed not to break clients through the slo extraction maybe we're fine - it seems unlikely we didn't slip a behavior change in there somewhere?21:11
*** petertr7 is now known as petertr7_away21:11
claygtdasilva: hell we don't even *like* the current versions behavior -> https://review.openstack.org/#/c/155421/21:11
claygsigh21:12
tdasilvalol21:12
claygwe have got to get this crap out of the proxy21:12
tdasilvaagreed21:12
claygi'm just going to +A it and see what happens21:12
clayg:P21:12
claygnotmyname: ^ close your eyes real quick21:12
tdasilvarofl21:12
* clayg forgot momentarily notmyname wrote most (all?) of the original versions code?21:12
notmynameclayg: just means I'll be the first hater on the current state of things21:13
tdasilvaclayg: so here is my plan: 1. test, figure out the current behavior when it comes to cross-functionality between slo and versioning. 2. Add automated tests against current master. 3. make sure those tests passes again middleware patch. 4. make necessary changes to patch21:15
tdasilvamattoliverau: ^^^21:16
claygmattoliverau: I just left on a review that says that plan should be ordered 3, 2, 5 - where 5 is "work on the undelete version of object versions middleware"21:20
*** mgarza_ has joined #openstack-swift21:20
claygoh wait... no what number is merge patch 134347 - that should be number 121:20
patchbotclayg: https://review.openstack.org/#/c/134347/21:20
mattoliverauThat would be 6 :p21:22
mattoliverauAnd morning :)21:22
claygyay matt!21:22
claygmattoliverau: yeah so i'm advocating we just rip this crap out of the proxy ASAP and then figure out where we're at?21:22
mattoliverauIf you moved the middle ware to the right of slo, slo deletes work with versioning.. Slo + versioning (slo being manifested and etagged) does seem edge casey tho21:23
claygI don't even know what it means to version a *slo - am I versioning the whole thing?  just the manifest?  what if the segments are in a container that's different form the manifest?  my head hurts21:23
claygslo deletes don't "work with versioning" - what is the expected behavior?  whose stored where - what's versioned?21:24
clayghow do you define "work with versioning"?21:25
claygtdasilva: new plan - if we move the middleware and mattoliverau +2's I think we might be able to merge!?21:25
mattoliverauYeah I know, but if you can now version manifests and use the same container you could version entire slos.. Kinda..21:25
tdasilvayeah, the problem becomes if users uploaded new versions of a segment but not if others21:25
tdasilvai think that breaks slo deletion21:25
tdasilvas/not if others/not of others21:26
claygmattoliverau: please don't feel threating by my nay-saying - if you think moving the middleware is better I'm all for it - anyone on the planet knows what versions + *lo's should do better than me21:27
*** jrichli has quit IRC21:27
mattoliverauLol, what if you use segments for other things (not just slo), they are versioned. You create and slo, then she time delete it, those old segments might still be important, but I'm the current state they'll be missing from the container (but versions would still exist)21:28
mattoliverauS/she/some21:28
*** zhill has quit IRC21:28
mattoliverauS/I'm/in21:29
mattoliverauI'm failing at writing.. Need coffee and breakfast :p21:29
tdasilvalol21:29
*** Fin1te has quit IRC21:30
tdasilvajust spent a couple of seconds deciphering that21:30
mattoliverauSo I think its not that slos are versionible but so the version delete behavior works as expected21:31
*** DericHorn-HP has joined #openstack-swift21:33
claygnadeem: notmyname says he squared it21:33
nadeemyep true. Thanks notmyname !21:34
tdasilvaclayg: just gave you permissions on the spreadsheet21:34
claygtdasilva: no it's too late - i'm doing my *own* spreadsheet now :P21:35
tdasilvalol...is there an etherpad like tool for spreadsheets?21:35
*** jasondotstar has joined #openstack-swift21:36
*** tongli has quit IRC21:36
claygtdasilva: isn't google docs the eatherpad like tool for google docs?  Or do you just mean "sharable by url by default"21:38
tdasilvayeah, the last part21:38
claygtdasilva: i can't copy and paste from my doc to yours :\21:40
tdasilvaclayg: so you can't write to my sheet at all or just copy and paste?21:41
*** blmartin has quit IRC21:44
*** lpabon has quit IRC21:44
*** CaioBrentano has quit IRC21:44
claygtdasilva: no we're collaborting now!21:46
peluseyou can always print screen and paste :)21:50
*** robefran has joined #openstack-swift21:57
openstackgerritMerged openstack/swift: Imported Translations from Transifex  https://review.openstack.org/20491422:06
notmynameI just got the openstack summit session voting email22:08
*** DericHorn-HP has quit IRC22:08
*** DericHorn-HP has joined #openstack-swift22:10
claygnotmyname: goodness it's that time again *already*22:14
notmynamesomeone named Pete who works at Red Hat has "The Plot to Destroy OpenStack Swift Using C++: Enhancements of Swift API Compatibility in Ceph RADOS Gateway"22:15
notmynamehttps://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/528122:15
*** mgarza_ has quit IRC22:15
claygwhat a great topic for the Openstack Summit!22:15
notmynamewait what?! dfg_ and redbo have a talk submitted? https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/536622:16
clayg"The Plot to Destroy Openstack Swift Usgin go"?22:16
notmynamelol22:16
notmyname"The Plit to Destroy Openstack Swift Using SMR Drives"22:16
hrouSorry notmyname, there's only room for one SMR talk ; - )  Though I'm open to renaming it.22:19
*** nadeem has quit IRC22:20
notmynamehrou: I think that's the subtitle of the existing one22:20
notmynameor maybe, "How to destroy SMR drives with Swift" would be more appropriate ;-)22:20
hrouWe suspected that actually happened at one point, but alas, it was our inexperience and it was simply driving an internal defrag.  But I agree, an appropriate title indeed : )22:22
tdasilva"Swift the Social Butterfly" ???22:22
tdasilvai wonder if there will be voting for best talk tittles22:23
notmynameyeah, that caught my eye too22:23
claygredbo: can you define what you mean by "orphaned data" - I can think of few things I've seen that might be called that - but you hinted at monitoring it - so I'm... curious ;)22:23
redboobjects that dont exizt in containers22:24
redbobut are on object nodes22:25
*** jome has joined #openstack-swift22:25
claygredbo: you can *track* that - like ... how much?22:26
*** mahatic has joined #openstack-swift22:27
claygi mean don't get me wrong - i've got my scripts - but I'm way to scared to let them loose - depending on how much you see in otherwise stable environments - maybe we should go looking for it more aggresively?22:27
redbonot exactly but we pretty regularly go see how much we can find and try to match it back to events or periods of high loaf or whatever22:27
redboload22:27
claygswift always just be loafin' around22:28
jomeHi. I'm new to swift and would like to experiment with it for a project we are working on. There is so much documentation out there that its quite overwhelming. My use case is developing a photo sharing app based on django22:28
notmynamejome: that's great!22:28
jomeI get the part where I can save images via the cli, but I'm quite stuck as to how to retrieve these via a web browser for example.22:29
jomeSo it anyone could point me in the right directions and hold my hand aling the way, that would be helpful22:30
jomeSo if anyone could point me in the right directions and hold my hand along the way, that would be helpful22:30
notmynamejome: do you want anyone to be able to access them (ie public) or only give out limited access to certain people?22:30
jomea mix of both actually... I would like things like static files to be accessible publicly (css, jpgs, js) and users can set permissions on their generated content.22:32
claygtdasilva: yeah so I think https://docs.google.com/spreadsheets/d/1hyo3Q7SS70kG0ZCR3NvXJZ6ikeqqQ04RcRYjOLb44m8/edit#gid=0 is pretty good22:32
claygi'm pretty confident of about half the behaviors - the others I have my expections...22:33
claygmattoliverau: did you decide what we're going to do about the middleware placement versions + *.lo?22:33
notmynamejome: ok, public access is a little simpler22:33
jomeOk... any info how I would go about that? Like some example code22:36
claygzackmdavis: ^ swift-django app!22:36
notmynamesorry. got distracted. seems that the Apple "swift" CLI has taken over on my mac22:37
jomeha ha ha22:37
*** mahatic has quit IRC22:37
claygnotmyname: rewrite python-swiftclient in swift?22:37
notmynameof course!22:38
jome@notmyname any ideas?22:39
notmynamejome: you've already got some objects in a container in swift?22:40
jomeyep22:40
*** jasondotstar has quit IRC22:40
notmynameok, then `swift post <container> -r ".r:*" will make the container public22:41
notmynamelet me know when you have that done22:42
jomeThat would also need to include the auth details. right?22:43
notmynameyes, if you haven't set them up as environment variables22:43
notmynameif you have the latest version of the swift cli tool, you can do `swift auth -v` to get the bash commands to set the environment variables22:44
jomedoing that now...22:46
jomeDone. No response though.22:47
claygugh - so i was going to review 120709 and realized I'll have to bust out sqlite explain and shit and try to wrap my head around a bunch of sqlite index nonsense :\22:47
*** annegent_ has quit IRC22:47
notmynamejome: no response for the container post or the auth command?22:47
claygnotmyname: the swift auth command merged!22:47
* clayg hugs timburke 22:48
notmynameclayg: yeah, and it's in the latest release! thanks :-)22:48
jomethe container post22:48
notmynamejome: ah, that's expected22:48
jomeok22:48
* timburke hugs clayg back22:48
notmynamejome: ok, now you can get the data via a browser. of course the first question is "what's the url?"22:48
timburkenow if we could get https://review.openstack.org/#/c/189387/ in too, we'd have a decent auth story!22:49
notmynamejome: to get your storage URL, do `swift auth` and the first line will have a url in it22:49
jomeok...22:49
notmynamejome: you can also get the url with `swift stat -v`22:49
jomeOk. got the url22:50
notmynamegreat22:50
notmynamejome: ok, my url on my dev environment is http://saio:8080/v1/AUTH_test. since the container named I used is "c" and I upload an object "1MB", then I can access http://saio:8080/v1/AUTH_test/c/1MB in a broswer22:50
notmynamejome: replace with your appropriate values, and you should be good22:51
jomeYeah!!!22:51
jomeWorked like a charm!22:51
notmynameyay!22:51
*** chlong has quit IRC22:52
jomeSo what this would mean is that for any container I need to be public, i run the command there?22:53
*** robefran has quit IRC22:53
jomeAll well and good there...22:53
jomeNow the hard part... :)22:53
notmynamejome: correct. you'd need to set a container as public. you only need to do that once22:54
notmynamejome: the hard part?22:55
jomeTo access files that require authentication/authorization22:56
notmynamevia a browser?22:57
jomeYep. I'd like to build a django app that would serve up such files22:57
notmynamejome: https://swiftstack.com/blog/2015/01/29/swift-feature-highlight-tempurls/22:58
notmynamejome: use tempurls. that link is how/what/etc22:58
jomeOk...22:59
*** haypo has left #openstack-swift22:59
notmynamejome: basically, you get a time-limited URL that is good for only one kind of operation. you can make that server-side and then pass it to the browser22:59
*** david-lyle has quit IRC23:02
jomeI see... So if I upload a photo, say via a form to save in swift, I save it with some accompanying metadata and then when a request is made for that photo, say by my friends, the app generally would create that tempurl for the photo to be served up the browser/client23:03
notmynameyes23:04
*** km has joined #openstack-swift23:05
notmynamejome: the temp-url keys don't have to be created for every object. you can create the tempurl key once (or use 2 keys and rotate them on a schedule if you want)23:05
*** hrou has quit IRC23:05
jomeThanks for this man... Certainly a good nudge in the right direction.23:09
jomeI'll go through this and give you a shout later?23:10
mattoliverauclayg: i think the middleware should move to the otherside of slo, not just because it makes slos+versions work (if that even makes sense) but mainly so anything deleting a versioned object is handled correctly. Then I'm happy to +2 to get versions in. I.e. atm you might have been using the slo segments as individual versioned objects. You place a slo, later delete it.. Now the container holding the latest version of23:11
mattoliverau the segments is now missing them, however the versions container still hold older versions of the files.. Moving the middle ware fixes this. Edge case yes, but I think is expected behaviour (at least in my mind)23:11
notmynamejome: sure. and if I'm not around, there's normally someone who can answer. we've got pretty decent global coverage, even if it is quieter at times :-)23:12
jomeGreat stuff... Say I wanted someone who I needed to formally consult for support, would I find such here?23:13
notmynamejome: most of us work for companies that have some sort of business interest in swift23:14
claygnotmyname: what'd I do to make swiftclient say "error in setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers23:14
clayg"23:14
notmynamejome: eg I work at swiftstack. we have a software product we sell. others work for service providers (rackspace, hp, ibm, etc). others, like red hat, have different kinds of support options23:15
jomeAah...23:15
notmynamejome: so yes, here's better than anywhere else. but we aren't sales people ;-)23:15
notmynameclayg: I don't know. and it took a lot of "FINE. I'll update ALL THE THINGS" and lots of grumpiness to make it work again23:16
jomeI'll take helpful people over sales anyday! :)23:17
*** gyee has joined #openstack-swift23:20
*** wbhuber has quit IRC23:22
*** kei_yama has joined #openstack-swift23:23
*** DericHorn-HP has quit IRC23:24
jomeIs there no other way to achieve the same thing other than tempurls? Unless I am missing something the python client does not seem to provide such a function.23:33
notmynamethe trick is that you can't send custom headers in a browser. ie you can't give someone a url that can only be accessed with an auth token in a header and expect them to be able to load it in a browser (without additional js work). so the auth info has to be in the url itself. that's where you get the signed urls23:35
*** gyee has quit IRC23:36
notmynameso you've got (1) public, no-token access (2) signed url access, and (3) private, with a token access. that's your choice23:36
*** david-lyle has joined #openstack-swift23:36
jomeHmm... ok.23:36
notmynameyou could proxy the data from swift through your django app, this using 3 on the backend but allowing non-tken access behind a login on the front end23:37
notmynamebut then you've added a lot of complexity and you'll be limited by the ability of the django app to scale23:37
*** gyee has joined #openstack-swift23:38
notmynameit's normally better to have the end-users talk directly to swift23:38
jomeSo, you'd advise 1 or 2 from a scalability perspective?23:39
notmynameand a trust perspective. you can hand public and temporary signed urls to untrusted users. you can't hand the creds or a token to untrusted users23:39
notmynamebut yes, from a scale perspective too :-)23:39
jomegreat stuff. Thanks... I'll dabble a bit more23:40
*** darrenc is now known as darrenc_afk23:44
openstackgerritClay Gerrard proposed openstack/swift: Fix string formatting in dispersion cli command  https://review.openstack.org/20532623:48
*** darrenc_afk is now known as darrenc23:54
*** jasondotstar has joined #openstack-swift23:56
*** ho has joined #openstack-swift23:57

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