Tuesday, 2015-11-17

klrmn1notmyname: is hot for the random module today00:00
claygnotmyname: it's more like while True: if client_is_slow(): conn -= 1 elif replication_is_slow(): conn += 1 else: sleep(1)00:00
notmynameyet again, clayg patches my code by replacing it with better code ;-)00:01
*** haomaiwa_ has quit IRC00:01
clayglol00:01
*** haomaiwang has joined #openstack-swift00:01
claygnotmyname: dfg_ was talking about some crazyness where you might try adding capacity and pushing rings *just* to object servers (letting the proxy push stuff to the old primary - now handoff) until your new capacity looks full-ish then pushing the rings out to the proxies too.00:03
notmynamethat's interesting00:03
claygunrelated to rsync max connections - but it's a general idea of how you might let a drive get hammered during capacity adjustment w/o killing on % of client requests quite so bad00:03
notmynamesounds similar to what we were talking about in austin00:03
*** ho has joined #openstack-swift00:04
*** hrou has joined #openstack-swift00:04
notmynamesomehow being able to ingest a node and get data to it without it actually being used by the proxy00:04
claygnotmyname: I agree - sounds crazy - but it might could work - I keep thinking there's a few things we want to do with that have to with cluster having a copy of the "old" ring (part-power adjustment has a similar need)00:04
claygnotmyname: I must have missed that side bar - but yeah that's exactly the idea00:04
claygtotally crazy stuff00:05
notmynameit was phrased as disabling/enabling a drive00:05
claygmeh, not really how I'm thinking about it - there's a few nice things of writing to the old location of the part instead of just some random handoff because one of the current primaries is "disabled"00:06
notmynamesounds like it would be dependent on (1) the placement algorithm doing a good job wrt keeping handoffs relatively stable and not moving too many primaries (2) really really good monitoring about how well replication is running in the cluster and (3) sharp ops team that has things tuned well and the patience to wait for replication cycles before rebalancing rings00:06
notmynameyeah, I agree about wanting something better than a simple "drive is disabled try again" code path. the old location is better than that00:08
notmynamehmm..it essentially makes the ring rollout into a process that takes a lot longer (days instead of minutes)00:08
claygnotmyname: idk, maybe - it's an interesting thought exercise00:09
claygbut anyway00:09
openstackgerritPeter Chng proposed openstack/swift: Append crypto-meta to user-meta  https://review.openstack.org/24588500:09
claygserverascode: the reason this is all relevant is that running with a high max connections won't really bite you until you add some fresh disks - then client request that hit that drive while replication is accidently the whole iops is gunna make some requests sad00:10
claygserverascode: if that's a "quickish" sort of pain because you aren't adding that much capacity it's entirely possilbe no one will care00:11
claygbut as the cluster gets bigger (multiple PB) you'll be back in channel asking what notmyname and I were talking about :P00:11
serverascodeclayg: ok, thanks again00:12
claygthere's less risk going with smaller max connections - except that when you *do* add capacity you'll want to have some inside into your replication logs or recon data to understand just how long it's going to take if only 4-10 parts can be moving onto a drive at a time :\00:12
hogood morning!00:15
notmynamehello ho00:15
honotmyname: hello :-)00:15
mattoliverauho: Morning00:16
homattoliverau: morning! welcome back :-)00:16
*** joeljwright has quit IRC00:17
gmmahapeluse: were you able to get past the issue? Went back and checked my notes and i dont see to have run into that00:17
mattoliverauho: thanks :)00:19
mattoliverauhey gmmaha00:20
pelusegmmaha: no, I'm convinced this whole python pbr setuptools easy-install.pth non-sense was all create to drive me nutso :)00:23
pelusegmmaha: but I'm off to the grocery store so will dork with it later....00:24
openstackgerritMerged openstack/swift: Missing log_name option added  https://review.openstack.org/24544400:26
*** jrichli has joined #openstack-swift00:28
notmynametorgomatic_: seems your 503 etag bug only applies to replicas00:28
torgomatic_notmyname: true00:28
torgomatic_I think the bug says as much00:28
notmynameah, yes. in the comments00:29
notmynameI, like, have to *scroll* to find that00:29
notmynametorgomatic_: anyway, thanks for working on that00:29
torgomatic_notmyname: sure. 5xx errors are pretty important, after all00:30
*** jerrygb has quit IRC00:40
*** jerrygb has joined #openstack-swift00:42
*** jerrygb has quit IRC00:42
*** siva_krishnan has joined #openstack-swift00:46
*** m_kazuhiro has joined #openstack-swift00:51
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
*** wbhuber has quit IRC01:01
*** wbhuber_ has quit IRC01:10
*** wbhuber_ has joined #openstack-swift01:11
*** siva_krishnan has quit IRC01:11
*** wbhuber_ has quit IRC01:15
*** dmorita has joined #openstack-swift01:30
openstackgerritPeter Chng proposed openstack/swift: Append crypto-meta to user-meta  https://review.openstack.org/24588501:38
*** aix has quit IRC01:46
lifelesspeluse: whats up?01:48
*** haomaiwang has quit IRC01:49
*** gyee has quit IRC01:55
peluselifeless: just having issues getting everything updated (setuptools, pbr, pip) and then getting keystone to install.  complains about something related that I don't "get".  Have to run now, if you're around tomorrow and think you can help I'll hit ya up!01:58
lifelesspeluse: this may help - https://rbtcollins.wordpress.com/2015/07/12/bootstrapping-developer-environments-for-openstack/02:01
lifelesspeluse: but sure, ping me tomorrow02:02
peluselifeless: thanks, will take a look!02:06
*** alejandrito has joined #openstack-swift02:08
*** alejandrito has quit IRC02:08
*** alejandrito has joined #openstack-swift02:08
*** klrmn1 has quit IRC02:12
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873602:16
*** alejandrito has quit IRC02:21
*** thucdx has joined #openstack-swift02:25
*** thucdx has left #openstack-swift02:28
*** haomaiwang has joined #openstack-swift02:31
*** alejandrito has joined #openstack-swift02:33
*** haomaiwang has quit IRC02:36
*** haomaiwa_ has joined #openstack-swift02:36
*** zhill has quit IRC02:48
*** sanchitmalhotra has joined #openstack-swift02:53
*** venkat_p has joined #openstack-swift02:59
*** SkyRocknRoll has joined #openstack-swift02:59
*** nadeem has joined #openstack-swift03:01
*** bapalm has quit IRC03:06
openstackgerritvenkatesh proposed openstack/swift: remove unused parameters in the method  https://review.openstack.org/24340103:12
jrichlitimburke: dont suppose you are around?  some slorange stuff is not mixing well with crypto.  i have some questions.03:12
*** m_kazuhiro has quit IRC03:17
*** balajir has quit IRC03:17
*** m_kazuhiro has joined #openstack-swift03:18
*** AbyssOne has quit IRC03:18
*** balajir has joined #openstack-swift03:18
*** mwheckmann has joined #openstack-swift03:24
*** janonymous has joined #openstack-swift03:25
*** AbyssOne has joined #openstack-swift03:26
*** janonymous has quit IRC03:34
*** wbhuber has joined #openstack-swift03:45
*** tsg has joined #openstack-swift03:51
*** klrmn1 has joined #openstack-swift03:57
*** alejandrito has quit IRC04:16
*** trifon has joined #openstack-swift04:20
*** sanchitmalhotra1 has joined #openstack-swift04:29
*** sanchitmalhotra has quit IRC04:31
*** mahatic has joined #openstack-swift04:37
*** sanchitmalhotra has joined #openstack-swift04:39
*** ppai has joined #openstack-swift04:40
*** sanchitmalhotra1 has quit IRC04:41
*** jrichli has quit IRC04:45
*** trifon has quit IRC04:52
*** sanchitmalhotra1 has joined #openstack-swift04:52
*** nottrobin_ has joined #openstack-swift04:53
*** nikhil|afk has joined #openstack-swift04:54
*** sanchitmalhotra has quit IRC04:54
*** matt___ has joined #openstack-swift04:55
*** baffle has joined #openstack-swift04:55
*** redbo_ has joined #openstack-swift04:56
*** MooingLe1ur has joined #openstack-swift04:56
*** timur has joined #openstack-swift04:56
*** haypo_ has joined #openstack-swift04:56
*** zacksh has joined #openstack-swift04:57
*** hrou has quit IRC04:57
*** mwheckmann has quit IRC04:58
*** SkyRocknRoll_ has joined #openstack-swift04:59
*** CrackerJackMack has quit IRC05:00
*** charz has quit IRC05:00
*** serverascode has quit IRC05:00
*** xnox has quit IRC05:00
*** swifterdarrell has quit IRC05:00
*** nottrobin has quit IRC05:00
*** baffle_ has quit IRC05:00
*** redbo has quit IRC05:00
*** zacksh_ has quit IRC05:00
*** nikhil has quit IRC05:00
*** MooingLemur has quit IRC05:00
*** jamielennox has quit IRC05:00
*** jroll has quit IRC05:00
*** wasmum has quit IRC05:00
*** timur_ has quit IRC05:00
*** peluse has quit IRC05:00
*** notmyname has quit IRC05:00
*** mattoliverau has quit IRC05:00
*** haypo has quit IRC05:00
*** jroll has joined #openstack-swift05:00
*** CrackerJackMack has joined #openstack-swift05:00
*** MooingLe1ur is now known as MooingLemur05:00
*** wasmum- has joined #openstack-swift05:00
*** jamielennox has joined #openstack-swift05:01
*** jerrygb has joined #openstack-swift05:01
*** zaitcev has quit IRC05:01
*** peluse has joined #openstack-swift05:01
*** jroll has quit IRC05:02
*** jroll has joined #openstack-swift05:02
*** jroll is now known as Guest8904005:02
*** xnox has joined #openstack-swift05:02
*** nottrobin_ is now known as nottrobin05:02
*** bill_az has quit IRC05:02
*** swifterdarrell has joined #openstack-swift05:02
*** ChanServ sets mode: +v swifterdarrell05:02
*** notmyname has joined #openstack-swift05:03
*** ChanServ sets mode: +v notmyname05:03
*** charz has joined #openstack-swift05:03
*** jamielennox is now known as jamielennox|away05:06
*** serverascode has joined #openstack-swift05:07
*** sanchitmalhotra1 has quit IRC05:10
*** sanchitmalhotra has joined #openstack-swift05:13
*** sanchitmalhotra1 has joined #openstack-swift05:16
openstackgerritMerged openstack/swift: New swauth URL  https://review.openstack.org/24557805:16
*** wbhuber has quit IRC05:17
*** sanchitmalhotra has quit IRC05:18
*** onder has quit IRC05:25
openstackgerritDaisuke Morita proposed openstack/swift-specs: Changing Policies spec  https://review.openstack.org/16876105:26
*** bill_az has joined #openstack-swift05:28
*** onder has joined #openstack-swift05:30
*** sanchitmalhotra has joined #openstack-swift05:34
*** wbhuber has joined #openstack-swift05:35
*** sanchitmalhotra1 has quit IRC05:37
*** jerrygb has quit IRC05:38
*** klrmn1 has quit IRC05:49
*** wbhuber has quit IRC05:54
*** nadeem has quit IRC05:56
*** trifon has joined #openstack-swift05:59
*** matt___ is now known as mattoliverau05:59
*** ChanServ sets mode: +v mattoliverau06:00
*** NM has joined #openstack-swift06:01
mahaticmattoliverau: hello, welcome back!06:06
mattoliveraumahatic: thanks :)06:07
openstackgerritMerged openstack/swift: Remove references to now-missing havana docs  https://review.openstack.org/24532606:11
*** rcernin has joined #openstack-swift06:22
*** sanchitmalhotra1 has joined #openstack-swift06:28
*** sanchitmalhotra has quit IRC06:31
*** jerrygb has joined #openstack-swift06:39
*** sanchitmalhotra has joined #openstack-swift06:45
*** jerrygb has quit IRC06:45
*** sanchitmalhotra1 has quit IRC06:47
*** bill_az has quit IRC06:47
*** nakagawamsa has joined #openstack-swift06:48
*** sileht has joined #openstack-swift06:49
*** nakagawamsa has quit IRC06:49
*** SkyRocknRoll_ has quit IRC06:54
*** kei_yama has joined #openstack-swift06:56
*** dhellmann has quit IRC07:01
*** dhellmann has joined #openstack-swift07:02
*** SkyRocknRoll has quit IRC07:05
*** sanchitmalhotra has quit IRC07:07
openstackgerritMerged openstack/swift: Fix 503 on zero-byte replicated PUT with incorrect Etag  https://review.openstack.org/24601007:08
*** tsg has quit IRC07:08
*** SkyRocknRoll_ has joined #openstack-swift07:11
*** sssagar has joined #openstack-swift07:13
*** sssagar has left #openstack-swift07:14
*** SkyRocknRoll has joined #openstack-swift07:19
*** sanchitmalhotra has joined #openstack-swift07:19
*** takashi has joined #openstack-swift07:21
*** SkyRocknRoll has quit IRC07:33
*** zhill has joined #openstack-swift07:43
*** zhill has quit IRC07:48
*** arnox has joined #openstack-swift08:00
*** SkyRocknRoll has joined #openstack-swift08:02
*** JelleB is now known as a1|away08:14
*** a1|away is now known as JelleB08:14
*** ho has quit IRC08:15
*** rledisez has joined #openstack-swift08:16
*** sanchitmalhotra1 has joined #openstack-swift08:32
*** sanchitmalhotra has quit IRC08:34
*** hseipp has joined #openstack-swift08:36
*** jerrygb has joined #openstack-swift08:40
*** geaaru has joined #openstack-swift08:43
*** jerrygb has quit IRC08:46
*** jordanP has joined #openstack-swift08:51
*** venkat_p has quit IRC08:55
*** sssagar has joined #openstack-swift08:57
*** jmccarthy has quit IRC08:57
*** jmccarthy has joined #openstack-swift08:58
*** sssagar has left #openstack-swift08:59
*** kei_yama has quit IRC09:02
*** kei_yama has joined #openstack-swift09:05
*** SkyRocknRoll has quit IRC09:16
*** ekarlso has quit IRC09:22
*** dmorita has quit IRC09:23
*** zhill has joined #openstack-swift09:25
*** zhill has quit IRC09:26
*** openstackgerrit has quit IRC09:31
*** openstackgerrit has joined #openstack-swift09:31
*** ekarlso has joined #openstack-swift09:37
*** ekarlso has quit IRC09:38
*** ekarlso has joined #openstack-swift09:38
*** esker has joined #openstack-swift09:49
*** joeljwright has joined #openstack-swift09:53
*** ChanServ sets mode: +v joeljwright09:53
*** esker has quit IRC09:54
*** esker has joined #openstack-swift09:55
*** esker has quit IRC09:55
*** ekarlso has quit IRC09:57
*** haypo_ is now known as haypo10:02
*** kei_yama has quit IRC10:10
*** kei_yama has joined #openstack-swift10:11
*** daemontool has joined #openstack-swift10:12
*** daemontool has quit IRC10:14
*** daemontool has joined #openstack-swift10:15
*** haomaiwa_ has quit IRC10:31
*** openstackgerrit has quit IRC10:31
*** openstackgerrit has joined #openstack-swift10:31
*** haomaiwang has joined #openstack-swift10:32
*** sanchitmalhotra1 has quit IRC10:32
*** ekarlso has joined #openstack-swift10:36
*** ekarlso has quit IRC10:39
*** jerrygb has joined #openstack-swift10:43
*** m_kazuhiro has quit IRC10:46
*** Leigh507 has joined #openstack-swift10:47
*** haomaiwang has quit IRC10:47
*** jerrygb has quit IRC10:47
*** haomaiwang has joined #openstack-swift10:49
*** haomaiwang has quit IRC10:49
*** haomaiwa_ has joined #openstack-swift10:49
Leigh507Hi all, Is this the right place to ask for some help with Icehouse swift?10:49
*** daemontool has quit IRC11:11
*** daemontool has joined #openstack-swift11:11
*** daemontool has quit IRC11:23
*** daemontool has joined #openstack-swift11:24
*** mahatic_ has joined #openstack-swift11:25
*** daemontool has quit IRC11:25
*** xnox has left #openstack-swift11:26
*** daemontool has joined #openstack-swift11:26
*** Guest53741 has quit IRC11:27
*** mahatic has quit IRC11:28
*** kei_yama has quit IRC11:44
onovyLeigh507, hi, don't ask to ask, just ask :)11:45
onovythere are (almost) all swift (core) devs here11:45
Leigh507:)11:47
*** NM has quit IRC11:47
Leigh507Ok. So I am trying to set up Swift as an object store authenticating with keystone.11:48
Leigh507When running a swift stat I get a 401.11:48
Leigh507The user has a correct token11:48
Leigh507And the Swift URL returned is valid for the tennant.11:49
Leigh507IE the service catalog URL has the tennant ID appended.11:49
Leigh507I think my issue may reside in ('Www-Authenticate', 'Keystone uri=http://127.0.0.1:35357'),11:49
Leigh507My keystone is on a remote box11:49
Leigh507So I am not sure why localhost is being returned.11:50
Leigh507From what I have seen this is returned when you do not set the auth uri in the proxy conf11:53
Leigh507However this has been set.11:53
Leigh507Onvoy, Also when I curled the swift URL retruned from the service catalog with the auth token provided by keystone I get:11:57
Leigh507< HTTP/1.1 401 Unauthorized HTTP/1.1 401 Unauthorized < Content-Length: 0 Content-Length: 0 < Content-Type: text/plain Content-Type: text/plain < Www-Authenticate: Keystone uri=http://127.0.0.1:35357 Www-Authenticate: Keystone uri=http://127.0.0.1:35357 < X-Trans-Id: tx68e4a70cdf1c40b4acb25-00564b159f X-Trans-Id: tx68e4a70cdf1c40b4acb25-00564b159f < Date: Tue, 17 Nov 2015 11:55:15 GMT Date: Tue, 17 Nov 2015 11:55:15 GMT11:57
*** venkat_p has joined #openstack-swift12:02
venkat_pHow to integrate keystone with SAIO?12:03
*** pushkarajthorat has joined #openstack-swift12:04
*** venkat_p has quit IRC12:11
*** links has joined #openstack-swift12:12
*** links has quit IRC12:12
*** haomaiwa_ has quit IRC12:14
*** NM has joined #openstack-swift12:28
*** jerrygb has joined #openstack-swift12:31
*** Guest89040 is now known as jroll12:36
*** alejandrito has joined #openstack-swift12:42
*** SkyRocknRoll_ has quit IRC12:45
*** pushkarajthorat has quit IRC13:03
*** ppai has quit IRC13:06
*** tsg has joined #openstack-swift13:41
*** haomaiwang has joined #openstack-swift13:47
*** bill_az has joined #openstack-swift13:52
*** haomaiwang has quit IRC13:52
peluselifeless: FYI my issue was with however I upgraded pbr, something didn't work right and keystone dependencies wouldn't install.  I used easy_install to redo pbr and that fixed whatever was wrong... thanks though!13:56
*** ekarlso has joined #openstack-swift14:01
*** joeljwright has quit IRC14:09
*** joeljwright has joined #openstack-swift14:10
*** ChanServ sets mode: +v joeljwright14:10
*** tsg has quit IRC14:19
*** wbhuber_ has joined #openstack-swift14:25
*** wbhuber__ has joined #openstack-swift14:26
*** wbhuber__ is now known as wbhuber14:27
*** proteusguy_ has quit IRC14:29
*** wbhuber_ has quit IRC14:29
*** pushkarajthorat has joined #openstack-swift14:33
*** dustins has joined #openstack-swift14:33
*** hrou has joined #openstack-swift14:33
*** breitz has quit IRC14:36
*** breitz has joined #openstack-swift14:36
*** haomaiwang has joined #openstack-swift14:39
*** ekarlso has quit IRC14:40
*** proteusguy_ has joined #openstack-swift14:46
*** wbhuber_ has joined #openstack-swift14:47
*** rvasilets__ has joined #openstack-swift14:47
*** wbhuber has quit IRC14:50
*** wbhuber_ is now known as wbhuber14:50
*** diazjf has joined #openstack-swift15:00
*** chsc has joined #openstack-swift15:01
*** trifon has quit IRC15:03
*** blmartin has joined #openstack-swift15:06
openstackgerritPeter Chng proposed openstack/swift: Append crypto-meta to user-meta  https://review.openstack.org/24588515:06
*** mac_ified has joined #openstack-swift15:07
*** tongli has joined #openstack-swift15:11
*** siva_krishnan has joined #openstack-swift15:15
*** dustins has quit IRC15:22
*** dustins has joined #openstack-swift15:27
*** tsg has joined #openstack-swift15:30
*** jrichli has joined #openstack-swift15:33
*** daemontool has quit IRC15:34
*** siva_krishnan has quit IRC15:35
*** siva_krishnan has joined #openstack-swift15:35
*** pushkarajthorat has quit IRC15:42
*** bill_az has quit IRC15:44
*** minwoob has joined #openstack-swift15:48
*** proteusguy__ has joined #openstack-swift15:49
gmmaha:wq15:51
*** proteusguy_ has quit IRC15:51
glangevi user ^^15:51
*** dustins has quit IRC15:52
gmmaha:D15:52
gmmahasorry wrong focus window. :( Need to stop windwos from switching focux when i get a msg15:52
glangeeverybody has done that -- no worries :)15:52
*** dustins has joined #openstack-swift15:52
*** daemontool has joined #openstack-swift15:57
*** daemontool has quit IRC15:59
*** daemontool has joined #openstack-swift15:59
*** rcernin has quit IRC16:04
*** mzhou has joined #openstack-swift16:10
timburkegood morning! jrichli, still need help?16:27
*** jlhinson has joined #openstack-swift16:31
*** mwheckmann has joined #openstack-swift16:35
jrichlitimburke: good morning!  Crypto support for sending etag in a footer is now having issues with the change made to line 454 in https://github.com/openstack/swift/blame/feature/crypto/swift/common/request_helpers.py16:37
jrichlitimburke: that conditional check used to also require "and first_byte is None and last_byte is None".  I suppose that was not true in our crypto version of things before, so this didn't raise before.16:39
timburkeit still does that (essentially), just earlier -- line 42616:40
timburkeam i right in thinking the trouble is that we've got the etag for the encrypted segment, not the plaintext segment?16:41
timburkehopefully, the content length will ensure we don't trip the "Too many bytes..." error and leave us ready to receive some footers, but i'm not actually sure...16:43
lifelesspeluse: how weird, that must be the first time in the universe easy_install has fixed something16:43
jrichlitimburke: I assume that is the issue.  I need to verify what etags are what in this method.  I just know that this wasn't satisfying that conditional before (no raise before).16:46
timburkejrichli: so how does one read footers? i don't think i've ever done that...but presumably we should now do it before we close the seg_resp.app_iter on line 45216:48
peluselifeless: just lcuky I guess :)16:48
*** zaitcev has joined #openstack-swift16:52
*** ChanServ sets mode: +v zaitcev16:52
*** tsg has quit IRC16:54
*** tsg has joined #openstack-swift16:55
*** gyee has joined #openstack-swift16:55
openstackgerritMichael Barton proposed openstack/swift: go: fix problem with using single config file  https://review.openstack.org/24650016:58
*** mfalatic has joined #openstack-swift16:59
*** SkyRocknRoll has joined #openstack-swift17:03
*** daemontool has quit IRC17:04
*** daemontool has joined #openstack-swift17:04
*** tsg has quit IRC17:06
*** mzhou has quit IRC17:07
*** mahatic_ has quit IRC17:07
*** mzhou has joined #openstack-swift17:10
jrichlitimburke: I gotta find out which etag is seg_resp.etag.  You see, in crypto world, there are 3 etags: 1) ciphertext MD5; 2) plaintext MD5 encrypted with obj key; 3) plaintext MD5 encrypted with cont key17:10
*** mwheckmann has quit IRC17:10
*** tsg has joined #openstack-swift17:11
timburkejrichli: extra fun! i've not been keeping up :)17:11
*** rledisez has quit IRC17:12
*** janonymous has joined #openstack-swift17:16
*** nadeem has joined #openstack-swift17:17
*** arnox has quit IRC17:18
timburkejrichli: remind me, what's the pipeline look like? and can you currently PUT a SLO manifest with crypto enabled?17:24
*** wbhuber has quit IRC17:24
*** rcernin has joined #openstack-swift17:36
*** petertr7 is now known as petertr7_away17:39
jrichlitimburke: pipeline = catch_errors gatekeeper healthcheck proxy-logging cache bulk tempurl ratelimit crossdomain tempauth staticweb container-quotas account-quotas slo dlo versioned_writes decrypter trivial_keymaster encrypter proxy-logging proxy-server17:39
jrichlitimburke: no, no SLO is working in the version with footers support.  when using fake_footers instead, I believe this is working.17:41
*** geaaru has quit IRC17:44
*** SkyRocknRoll has quit IRC17:45
*** Leigh507 has quit IRC17:48
*** klrmn1 has joined #openstack-swift17:54
*** haomaiwang has quit IRC17:55
*** mwheckmann has joined #openstack-swift17:55
*** mfalatic_ has joined #openstack-swift17:56
*** joeljwright1 has joined #openstack-swift17:57
*** mac_ifie_ has joined #openstack-swift17:57
*** zhill has joined #openstack-swift17:57
*** joeljwright has quit IRC17:58
*** baffle has quit IRC17:59
*** rvasilets__ has quit IRC17:59
*** mfalatic has quit IRC17:59
*** mac_ified has quit IRC17:59
*** jlhinson_ has joined #openstack-swift18:00
*** BAKfr has quit IRC18:00
*** baffle has joined #openstack-swift18:00
*** jordanP has quit IRC18:01
*** BAKfr has joined #openstack-swift18:02
*** jlhinson has quit IRC18:03
minwoobI am trying to create a Swift daemon like the container-sharder that mattoliverau created, but swift-init isn't picking up on the conf nor the process. Are there any set of instructions that document this?18:03
*** diazjf has quit IRC18:07
*** mahatic has joined #openstack-swift18:15
jrichliminwoob: Maybe look at swift/common/manager.py at the ALL_SERVERS18:16
jrichliseems like you would modify that class18:17
*** siva_krishnan has quit IRC18:31
*** mahatic has quit IRC18:35
*** hseipp has quit IRC18:35
*** daemontool_ has quit IRC18:37
minwoobjrichli: That didn't seem to do it, but thanks for the suggestion.18:38
minwoobI'll dig further.18:39
*** petertr7_away is now known as petertr718:41
*** joeljwright1 has quit IRC18:41
notmynameminwoob: did you add it to setup.cfg?18:42
*** daemontool has quit IRC18:44
minwoobnotmyname: I did not. Will go ahead and do that.18:51
minwoobThanks.18:51
*** tsg has quit IRC18:53
*** blmartin has quit IRC18:55
*** lpabon has joined #openstack-swift18:56
*** blmartin has joined #openstack-swift18:56
*** jlhinson_ has quit IRC18:58
*** ssagar has joined #openstack-swift18:59
*** sc68cal_ is now known as sc68cal19:00
*** ssagar has quit IRC19:01
notmynameI'm making some assertions about swift. https://review.openstack.org/246558 based on the tags defined at http://governance.openstack.org/reference/tags/index.html19:04
*** siva_krishnan has joined #openstack-swift19:04
timburkenotmyname: sweet! are all of the testing requirements already satisfied by the grenade gate?19:11
*** siva_krishnan has quit IRC19:13
notmynametimburke: I think19:15
notmynametimburke: colloquially, swift is always used as the examples for these, so i think/hope we're fine :-)19:15
*** siva_krishnan has joined #openstack-swift19:15
timburkenotmyname: oh, i know we definitely adhere to all of these principles. just making sure we *actually* have tests for them :P19:16
*** ekarlso has joined #openstack-swift19:24
*** petertr7 is now known as petertr7_away19:27
tdasilvanotmyname: how do these tags work? or what effect do they have?19:29
notmynamethey "work" by being in a yaml file19:29
notmynameand I think the effect is that lists get built from them19:30
notmyname(I'm not trying to be cynical about it, really)19:30
notmynameso eg the foundation has the new project overview site they talked about at the summit19:30
notmynameand the tags will be shown there19:31
notmynameI think it will be like "these projects can do rolling upgrades"19:31
tdasilvalol...i know..probably not a good question...just trying to understand the context...what's their use, or where do I see them being displayed or something? is this part of the marketplace thing?19:31
tdasilvaoh yeah, the overview site...that's what i was thinking19:31
tdasilvagot it!19:31
notmynamethe goal of the tags generally is to better communicate what each project can do. to ops, to end users, and overall much better than "integrated release" did19:31
notmynamethere's an email. I'll look for the link19:31
notmynamehere19:32
notmynamehttp://lists.openstack.org/pipermail/openstack-dev/2015-November/079542.html19:32
tdasilva"Project Navigator" i think it is called19:32
notmynameyeah, that19:32
notmynameso that's one place I guess they'll be used19:33
torgomatic_oh, so *you* type up a diff with "assert" in it and suddenly you're "helping out project navigator" and "being a good openstack citizen", but when I do it I'm "lazy" and "littering the codebase with garbage"19:33
*** petertr7_away is now known as petertr719:33
notmynameassert:has-cranky-core-devs19:34
tdasilvalol19:34
torgomatic_heh19:34
tdasilvai really don't understand swift's maturity being 3 out 5???19:35
notmyname3?19:35
notmynamewe were 419:35
tdasilvai guess we got downgraded19:36
tdasilvahttp://www.openstack.org/software/releases/liberty/components/swift19:36
notmynameoh weird. we used to have something like 18 different SDKs listed19:37
notmynamealso, I completely disagree that "only 62% of respondents use swift therefore it's not mature enough" is valid in any way19:38
notmynametdasilva: oh, interesting. maybe none of these SDKs have been updated in this release cycle19:39
tdasilvayeah...really don't get that19:39
tdasilvanotmyname: maybe that means maturity19:39
tdasilvaoh, i see: "Status is an integer - the number of SDKs updated within the release cycle that support the service project "19:40
tdasilvathat doesn't seem right19:40
torgomatic_well, according to my arbitrary metrics that I am making up right meow, Swift is 11/10 on the cat-picture scale, beating out every other openstack project by at least 2 units19:40
notmynameyeah19:40
*** torgomatic_ is now known as torgomatic19:40
*** ChanServ sets mode: +v torgomatic19:40
notmynameok, I've got a way to bring it up. I'll have to compose an email19:43
*** diazjf has joined #openstack-swift19:43
blmartinHi guys, do you know of a good way to list containers  in a hidden account? like .test_AUTH_Account?19:44
*** jamielennox|away is now known as jamielennox19:45
*** jlhinson_ has joined #openstack-swift19:48
glangeblmartin: https://github.com/gholt/swiftly <-- you could install that tool on one of your systems "inside" of swift (one with the rings and access to all the swift servers)19:48
*** zhill has quit IRC19:48
glangeand then run swiftly -D /v1/.test_AUTH_Account get19:49
notmynameglange: thanks. I was thinking "use swiftly" ;-)19:50
glangethat's what we do! :)19:50
blmartinawseome glange! Thanks a lot!19:50
*** jamielennox is now known as jamielennox|away19:52
*** jlhinson_ has quit IRC19:54
*** diazjf has quit IRC19:55
*** diazjf has joined #openstack-swift19:56
*** tsg has joined #openstack-swift20:03
*** eariasn has joined #openstack-swift20:04
eariasnwhat would be a downside of switching Swift to Cassandra ?20:04
tdasilvaeariasn: isn't Cassandra a nosql database??? doesn't seem right to compare to swift?20:07
tdasilvatwo different use cases, no?20:07
*** zhill has joined #openstack-swift20:08
eariasnno I meant like put Swift not to use SQLite but Cassandra20:08
tdasilvaoohhh20:08
tdasilvawhere's that plugable  backends patch again???20:09
*** jamielennox|away is now known as jamielennox20:09
glangesqlite helps swift scale because there are many, many independed sqlite dbs in each swift cluster20:09
glangeyou don't want a central db because of that20:09
glangeindependent20:09
glangeeach account is a db, each container is a db20:10
eariasnso the use case is a single container with millions of objects20:10
glangeyou could do that with something simpler than swift20:11
*** dkleute has joined #openstack-swift20:14
claygblmartin: you can also use an internal client -> https://gist.github.com/clayg/9f3078413f5b242034fd20:14
claygeariasn: no reason to avoid a few million objects in a swift container today - maybe if a few million is a working set that's turned over every few weeks - tens of millions is less attractive - but not as unattractive as scaling a single database to the size of a cluster; or managing rebalance/sharding of multiple database servers20:18
*** eranrom has joined #openstack-swift20:18
claygeariasn: sqlite is pretty great at solving container listings for swift - there's some pain points - but there's simpler ways to address them than throwing the baby out with bathwater (e.g. https://review.openstack.org/#/c/218738/)20:19
blmartinclayg: I'll play with that next, never hurts to be more familiar with the inner workings swift. Swiftly worked great for a quick find operation, I must say.20:22
blmartinThanks for writing the gist!20:22
claygblmartin: yeah it's pretty great20:23
*** khoah64 has joined #openstack-swift20:23
claygblmartin: it was no trouble putting the gist together - i have dozens of snippets like that laying around for dev/test - i just grabbed the closest thing and added a usage string ;)20:23
eranromGreetings, I am trying to prioritize, and was wondering what would be more helpful at this point in time: (1) Clay's gigantic ring builder patch or (2) Swift client auth improvements. Independently I will work with acoles on fast post as soon as he reaches a verdict20:25
*** petertr7 is now known as petertr7_away20:26
claygeranrom: no my patch for sure - you should totally hold out on me until I get back to container-sync!20:27
*** blmartin has quit IRC20:28
claygeranrom: maybe patch 202411 patch 214206 patch 160877 or patch 11771020:29
patchbotclayg: https://review.openstack.org/#/c/202411/ - Add functional test for access control (RBAC) with...20:29
patchbotclayg: https://review.openstack.org/#/c/214206/ - Modify functional tests to use testr20:29
patchbotclayg: https://review.openstack.org/#/c/160877/ - Add storage policy support for sorting method20:29
patchbotclayg: https://review.openstack.org/#/c/117710/ - Add concurrent reads option to proxy20:29
eranromclayg: I ownder how seriously I should take this :-)20:29
eranrombut alright.20:29
eranromso just to make sure, since I was a way for some time - the swiftclient auth improvements were not addrressed yet, right?20:30
claygeranrom: hey!  fair is fair!  social capitol is the only leverage we have20:30
*** petertr7_away is now known as petertr720:30
eranrom:-)20:30
claygeranrom: well that and shame... like the one time i ebarassed redbo and he wrote patch 24650020:31
patchbotclayg: https://review.openstack.org/#/c/246500/ - go: fix problem with using single config file20:31
notmynameclayg is all over the priorities ;-)20:31
claygeranrom: I don't20:31
claygack!20:31
redbo_:)20:31
claygeranrom: I don't know what's up with swiftclient auth - I think the priority on swiftclient is probably patch 223319 - but joel has the as wip20:32
patchbotclayg: https://review.openstack.org/#/c/223319/ - New API documentation for python-swiftclient20:32
notmynameeranrom: nothings been done yet on the client auth. but the list clayg gave is a good one (beyong what you mentioned about the rings and fast-post)20:32
claygeranrom: we also have... something about reverse listings - that or acoles' ec patches are on my radar today20:32
eranromok got it, thanks!20:33
claygnotmyname: I think for the moment we just wait for torgomatic's ring-fuzzer review on patch 24157120:33
patchbotclayg: https://review.openstack.org/#/c/241571/ - Put part-replicas where they go20:33
*** elligottmc has joined #openstack-swift20:33
claygnotmyname: and of course I'd love to hear what cschwede thinks we should do for that patch review wise - and see someone from rax add a comment that they ran their rings over it and don't *necessarily* have to kill me immediately (like they can wait until the mid-cycle or whatever)20:34
notmynamehurricanerix janonymous have been looking at the testr change, so I think that's covered for now20:35
notmynameclayg: yes!20:35
notmynameeranrom: probably the simplest "get something useful done soon" review you could do is for patch 20241120:36
patchbotnotmyname: https://review.openstack.org/#/c/202411/ - Add functional test for access control (RBAC) with...20:36
dkleutePlease reference me to outside archived discussions if the answer is out there. Two questions:20:36
dkleute1. Has a database outside of SQLite been considered for much larger scale containers (Talking billions or even trillions of objects in a “single” container.) Riak, Cassandra, Redis… even a full clustered SQL etc.20:36
dkleute2. Has any thought been put into a pluggable container architecture which would allow the underlying database to be swapped out at will to fit specific workloads?20:36
dkleuteBoth these questions come from client requirements in terms of scalability. I hope to generate a discussion as the objections I’ve heard to some of these “databases” may well be out of date. I apologize if I’m re-hashing an old subject.20:36
*** wbhuber has joined #openstack-swift20:36
notmynamedidn't eariasn just ask about that?20:37
eranromnotmyname: ok sure.20:37
claygnotmyname: that review isn't simple - because keystone?20:37
notmynamedkleute: what particular scale questions are you getitng?20:37
notmynameclayg: *shhh*20:37
dkleutenotmyname: He may have. I work with him trying to solve this issue.20:37
hurricanerixnotmyname yeah, i looked at it some and it seems to be working.  i wasn't sure what was up with the ec errors, but i thought i remember a comment from you that you expected those.20:38
clayghurricanerix: not anymore - timburke fixed the EC functest errors20:38
notmynamehurricanerix: any EC errors I was seeing should be resolved by now. timburke fixed it20:38
dkleuteWe need to reach scale of billions of objects without significant (read that as any) performance degredation.20:38
notmynamehurricanerix: is there anything more you're waiting for or expecting to do on that patch then?20:38
claygdkleute: billions of objects isn't a challange per say - but why do they need to be in the same container?20:39
notmynamedkleute: the common answer is to use a lot of containers. but if you're looking for billions of object in one container, then the container sharding work that mattoliverau is working on is what you want to track20:39
hurricanerixnotmyname does timburke have a diff patch that he is going to push?  i was looking at http://logs.openstack.org/06/214206/3/check/gate-swift-dsvm-functional/6952177/console.html.gz20:39
hurricanerixnotmyname which is from the patch you pushed20:40
glangedkleute: don't put a billion objects in one container :)20:40
dkleutenotmyname: Yes, I'm aware of the sharding work. The problem is sharding for this performance and scale will lead to 100,000 containers.20:40
notmynamedkleute: the number of objects is only half of the question. the other is the create/delete rate of those objects too20:40
clayghurricanerix: i don't think that's from after timburke's fixed was merged - recheck no bug20:40
notmynamedkleute: is 100000 containers a problem?20:40
claygnotmyname: 10M container is not a problem20:41
dkleuteAnd, I wrote a hashring to distribute load across thousands of containers. But, these are ultimately short term solutions as they present data expansion and migration challenges.20:41
hurricanerixclayg ahh, so it just needs to be rebased?  let me do that and see what happens.20:41
notmynameclayg: righ20:41
claygnotmyname: I have no idea if 100M container is problem - I think 1B containers might be... well that would be interesting20:41
dkleuteWe haven't gotten to the point where we can test 100,000 containers. Hopefully soon. But my guess is it will be for operations like list.20:41
claygdkleute: not if mattoliverau does his job right!20:42
* clayg cracks the whip20:42
notmynameclayg: right. dkleute was saying that sharding would leak to 100k contianers. I don't see the problem with that (depending on use case)20:42
claygnotmyname: well if they're just a hash of the name you can't do anything smart about prefix listing and subdir path queries and the like20:42
claygnotmyname: jumble jumble20:42
notmynamesure, but with billions of objects, I'm guessing that listing operations aren't something that's done often20:43
mattoliverauEven if they are a listing will only be 10000 at a time, so you never hit all containers20:43
claygnotmyname: idk, -infra had that use-case where they wanted to do like path queries but they wanted lots of things in a single container because of cdn/management overhead of lots and lots of containers20:44
notmynamedkleute: yeah, so the work mattoliverau is doing is in principle similar to you creating 100k containers on the client side20:44
dkleuteWe haven't tried 100k containers yet with that code either.20:44
*** nadeem has quit IRC20:44
notmynameclayg: because of wanting to duplicate filesystem semantics with nested directories (or metadata on those pseudo dirs)20:44
dkleuteBut, still, why do all this sharding work when there are scaleable databases out there that can have billions of records?20:45
claygnotmyname: yeah I mean *thats* the rub - if you're putting 100M objects in a container you're doing some sort of pseudo dir higharchy - at least that's what I've seen when evaluating s3 datasets for migrations20:45
claygdkleute: you ever ran a HA cassandra cluster?  Do you want to run 1000 of them?  Or shard load/accounts and migrate between them?20:46
claygdkleute: the pre-cursor to swift had central db pools - some other older object storage systems have architecture like that - it'd be a step backwards20:47
*** nadeem has joined #openstack-swift20:47
dkleuteno, I haven't. And that may be the answer. Are you saying cassandra can't handle this kind of load at scale? Or Riak... etc.20:47
*** nadeem has quit IRC20:47
claygsqlite is great!  doing all the sharding stuff is just to reduce friction on clients - going with a different metadata architecture would need to be driven by something more than "but I don't *wanna* rewrite my app code to use a dozen containers for 10M objects"20:48
*** nadeem has joined #openstack-swift20:48
mattoliverauThe awesome thing about sqlite is they can be treated like objects and thus get the durability and separation as normal objects.20:48
glangethere are more sqlite databases in the solar system than any other kind of database20:49
dkleuteHas anyone tried it? I'd love to see some metrics.20:50
claygdkleute: I'm pretty keen on Cassandra for like document orientented storage/queries - I don't think it's an ideal solution for swift containers (because they're so simple and screw concensus) - but yeah I think trying to consolidate metadata at swift's scale is a step backwards - it's less of a knock on any other design - just that swift is solving swift's problems20:50
elligottmcI do recall in the latest spec I think there was discussion of sharding the database20:50
claygdkleute: tried what?  storing a billion documents in cassandra?  sure20:51
elligottmcas an option being explored20:51
claygglange: probably a half doezn on mars alone20:51
elligottmcwhich is not the same as going to new database necessarily but seems relevant20:52
glangeit's a true fact!20:52
claygcomparing sqlite to a real database server/process/cluster is like apples to oranges - it's just totally different - just because your django app one time ran on sqlite and then you used mysql does not make them equivilant in any useful sense20:53
notmynameclayg: also unfair since the question implies that sqlite isn't a "real" DB ;-)20:54
claygnotmyname: it's not20:54
dkleuteFor cassandra, I think centralizing is the wrong word. Personally, I would still isolate containers using keyspaces and column families. I'm just surprised someone would want to handle sharding logic before doing something like that.20:55
claygnotmyname: well I don't know -- I guess database can mean different things20:55
elligottmcyou can shard sqllite correct?20:55
claygelligottmc: no - everything in sqlite is a file20:55
elligottmck20:55
claygdkleute: well... surprise!20:55
elligottmcso you would have to switch db's to shard20:55
claygelligottmc: no - you can shard at the application level20:56
glangedkleute: there was an early version of "swift" that had a central postgres db20:56
glangeand it didn't work/scale after a while20:56
dkleutePostgres is a central database. Cassandra/Riak are not.20:56
glangeplus what happens when your db server goes down or whatever20:56
claygdkleute: so here's the thing - for a good deal of deployments it's unclear that even a well tuned cassandra system could serve the swift keyspace for an entire cluster well20:56
claygdkleute: the challange of concensus at scale is problematic to the eventually consistent heavily available design goals of swift20:57
dkleuteclayg: ok, I'd love to know more about that. Doesn't something like cassandra meet those needs out of the box? There's no master, it's distributed, highly available.20:58
elligottmchttps://www.sqlite.org/sharedcache.html20:59
elligottmcseems kinda shardish not the real mccoy20:59
claygdkleute: Riak is not relevant - it's an object storage system like swift except that their listing api is... well... they say don't use it20:59
elligottmcbut maybe helpful20:59
elligottmcif not already in code of so apologies20:59
glangedkleute: if you want to use casandra, go for it :)20:59
dkleuteclayg: yes, cassandra is my "obvious" choice. Is there something other than "it may not scale" holding back trying it out?20:59
notmynameit would be a whole lot of work?21:00
dkleutemore than making sharding stable at similar scale? (this all leads to my second question. pluggable storage architecture)21:00
glangehaha21:00
claygnotmyname: well that and it may not work - column families have the same problem as sqlite indexes - you can't just throw shit in them forever w/o index updates getting slower21:01
*** mzhou_ has joined #openstack-swift21:01
claygwe have such a simple use-case for the datastore - there's no reason we can't do smart shit at the application level and use small simple lean and mean storage systems21:01
dkleuteclayg: yes, there is a scaling limit to everything. but let's say we hit that. wouldn't it still be easier to shard far fewer times against different cassandra clusters?21:02
*** mzhou has quit IRC21:02
*** mzhou_ is now known as mzhou21:02
notmynamewhy would that be easier?21:02
claygdkleute: notmyname: it's *known* to be *harder*21:02
notmynameyou'd have the same work to do in swift, but operationally you'd have a huge amount of new complexity21:02
dkleuteBecause growing and shrinking clusters with thousands or millions of shards is difficult.21:03
*** zacksh has quit IRC21:03
*** zacksh has joined #openstack-swift21:03
glangematt oliver is going to make all that work21:03
glangeout of the box21:03
dkleuteI understand that. I may be assisting with that work. Bit I also need to look at alternatives.21:04
claygdkleute: awesome!21:04
claygdkleute: you should start with cassandra - i'm curious if you think a single instance could handle a cluster reasonably well.21:05
claygdkleute: good luck21:05
dkleuteI doubt it. But maintaining a small cluster of cassandra nodes is easier, to me, than implementing sharding.21:05
glangedkleute: why not just use cassandra without swift?21:05
glangeor use ceph?21:05
dkleuteI wouldn't use cassandra for storing the actual objects.21:06
glangewhat's the maximum value it can store?21:06
dkleuteI'm just trying to solve the bottleneck of SQLite while still maintaining masterless and high availability eventual consistency.21:06
glangebottleneck being that sqlite can't handle a billion objects in a container?21:07
dkleuteWhile also keeping code fast and clean. less code = less room for bugs.21:07
glangeor what is the bottleneck?21:07
dkleuteIn our tests sqlite performance starts degrading between 1M and 10M objects.21:07
glangewhat kind of disks are your container db's on?21:08
glangespinning?21:08
dkleuteI believe that test was SSD's. but I don't know for sure.21:08
glangeok, and just sharding your objects on the client side across many containers isn't an option?21:09
notmynamewhat aspect of sqlite performance was degrading?21:09
*** blmartin has joined #openstack-swift21:09
glangeinsertion time21:09
glangeprobably any operation on the db21:09
eariasnSSD's are being used now.21:09
mattoliverauBut more op overhead (addition of Cassandra clusters). So what is better, getting a solution working built in or leaving it to the operators. But sure a pluggable backend is interesting.. But is a lot of work as well.21:10
dkleuteI wasn't part of the original test. I will try and find all the specifics. Sharding across containers is an option and is being done. But growing a sharded environment is yet another complexity.21:10
glangesharding is pretty easy client side, pick a big number of containers to start with21:11
dkleuteAnd we are talking about growth of Petabytes per month.21:11
claygdkleute: you don't need these jerks to give you approval - you should just do it and publish the code - that'll show 'em21:11
glangepetabytes per month for how long?21:11
glangeyou might end up with the biggest swift cluster ever pretty quickly21:11
claygglange: 10PB next month 1EB by Q121:11
dkleuteForever. And gorwing21:11
dkleute*growing21:11
glangeyou are going to run into all sorts of problems then21:12
*** NM has quit IRC21:12
dkleuteYep.21:12
glangemore than just sqlite :)21:12
glangelike replication might be too slow at that point21:12
dkleuteYep. Hence looking at places to eliminate complexity and increase scalability.21:12
glangedb replication is fast -- it's object replication that is the sticking point21:12
claygdkleute: awesome - gl - keep us posted21:13
glangealso, do you know about the object distribution variablity problem ?21:13
dkleuteYes, right now, the bottleneck we have is SQLite. So, that is what I'm working on.21:13
dkleuteNope. One problem at a time for me. ;)21:13
*** zaitcev has quit IRC21:13
glangewell, you should consider that one too21:13
glangeit's bad21:13
mattoliveraudkleute: clayg is right, give it a go21:13
notmynamewhich is why it's great to have you in here :-) ( dkleute and elligottmc)21:13
claygdkleute: that's how you do it - priortize the list - knock off the first one - reprioritze - rinse/repeat21:13
glangematt, don't try to get out of solving these problems :()21:13
glange:)21:13
dkleuteMatt, I would love to try this. But my knowledge of swift architecture is next to nothing at the moment.21:14
glangedkleute: write object distribution variability problem on your list21:14
notmynamedkleute: https://swiftstack.com/openstack-swift/ is a reasonable single-page overview21:14
openstackgerritTim Burke proposed openstack/python-swiftclient: Use bulk-delete middleware when available  https://review.openstack.org/19088721:15
*** zaitcev has joined #openstack-swift21:15
*** ChanServ sets mode: +v zaitcev21:15
*** eranrom has quit IRC21:15
glangedkleute: I don't think you can push 1EB into a swift cluster in 3 months21:16
dkleuteThat is a good overview of swift. But that's not what I meant. I meant from a coding perspective.21:16
glangethat's another problem21:16
claygglange: and you have some personal investment in preventing him from *trying*?21:17
notmynamedkleute: somewhat dated, but https://swiftstack.com/blog/2013/02/12/swift-for-new-contributors/ might help21:17
claygglange: like you just wanna build up a reserve of i told you so's?21:17
glangehaha, I'm just trying to help -- I see problems, I say something, I'm sorry :)21:17
glangeI'm a helpful person21:17
notmynameglange: http://i.imgur.com/ES6sP.jpg ?21:18
dkleuteAnyone want to spend an hour doing a "What if" code scenario?21:18
dkleute;)21:18
*** siva_krishnan has quit IRC21:18
claygdkleute: no21:18
glangedkleute: you should do everything in middleware21:18
dkleutedidn't think so. ;)21:18
dkleuteAnd my time limit just expired. Thank you so much for the help! I'll dig into it and see what I find.21:19
glangedkleute: you might need to hire a bunch of swift experts for high salaries21:19
dkleuteWe have some help. But, right now, I don't even understand what in the code needs to change.21:19
claygglange is a swift expert21:20
*** wbhuber_ has joined #openstack-swift21:20
glangeand I like money21:20
kota_clayg: you too21:21
claygkota_: I know next to nothing about swift architecture21:21
glangeswift was designed by monkeys21:21
glange(I kid)21:21
tdasilvain the desert?21:21
*** wbhuber has quit IRC21:24
mattoliveraudkleute: sorry it's early for me and I haven't had coffee, but if you want to discuss in more detail I'm happy to listen, I like good ideas. Just email me :)21:24
dkleuteSure! Matt, I would love to talk to you about this.21:24
dkleuteDo you have phone time?21:24
clayg<groan>21:24
*** diazjf has quit IRC21:25
notmynamedkleute: what scale of swift have you tested so far?21:26
openstackgerritRichard Hawkins proposed openstack/swift: Modify functional tests to use testr  https://review.openstack.org/21420621:27
notmynamehurricanerix: thanks. that's a rebase?21:28
hurricanerixnotmyname yeah21:28
hurricanerixi re-ran it and everything seemed good21:28
mattoliveraudkleute: email to start is best, you can write your idea down and I can respond in my own time. And point out areas that would need to change. Etc. But of brain storming.21:28
hurricanerixso hopefully this one passes the gates =)21:28
dkleuteI think 10 million objects. Over a million saw performance degradation on a private cluster.21:28
dkleuteMatt, works for me21:28
dkleuteI have to sign off. Thanks for all the feedback!21:30
notmynamedkleute: there are many swift clusters today with billions of objects. I'd suggest working with swift's design as you grow. and I'd love to help you get involved in upstream dev work! our best contributions come from people solving production problems!21:31
*** dkleute has quit IRC21:34
mattoliverauNow that breakfast is over, morning! :)21:34
notmynamehi mattoliverau!21:35
*** diazjf has joined #openstack-swift21:36
*** jlhinson has joined #openstack-swift21:42
*** mzhou_ has joined #openstack-swift21:42
*** mzhou has quit IRC21:44
*** mzhou_ is now known as mzhou21:44
*** haypo has left #openstack-swift21:45
*** diazjf has quit IRC21:45
*** diazjf has joined #openstack-swift21:48
*** dustins has quit IRC21:48
notmynamehurricanerix: seems to work for me21:48
*** tongli has quit IRC21:50
*** zaitcev has quit IRC21:55
*** hrou has quit IRC21:59
*** khoah64 has quit IRC22:08
*** minwoob has quit IRC22:21
*** rcernin has quit IRC22:21
*** petertr7 is now known as petertr7_away22:22
*** zaitcev has joined #openstack-swift22:28
*** ChanServ sets mode: +v zaitcev22:28
*** diazjf1 has joined #openstack-swift22:30
*** diazjf1 has quit IRC22:30
*** petertr7_away is now known as petertr722:31
*** mwheckmann has quit IRC22:33
*** diazjf has quit IRC22:33
*** zhill has quit IRC22:37
*** zhill has joined #openstack-swift22:40
*** diazjf has joined #openstack-swift22:42
*** thumpba has joined #openstack-swift22:54
onovyhi, https://review.openstack.org/#/c/243040/ // final +A someone pls? :)22:56
claygonovy: I think there's a bug open for that!22:59
*** diazjf has quit IRC23:02
onovyclayg, can't found it23:02
*** tsg has quit IRC23:02
claygonovy: https://bugs.launchpad.net/swift/+bug/150822823:02
openstackLaunchpad bug 1508228 in OpenStack Object Storage (swift) "replicator should warn when there's no local devices" [Undecided,In progress] - Assigned to Syed Ahsan Shamim Zaidi (ahsanmohsin04)23:02
onovyclayg, ah, thanks!23:02
*** km has joined #openstack-swift23:04
openstackgerritOndřej Nový proposed openstack/swift: Log error if a local device not identified  https://review.openstack.org/24304023:05
*** km is now known as Guest604323:05
onovyadded to commit message23:05
*** blmartin has quit IRC23:05
*** thumpba has quit IRC23:07
*** wbhuber_ has quit IRC23:07
*** wbhuber has joined #openstack-swift23:08
*** thumpba has joined #openstack-swift23:08
openstackgerritJonathan Hinson proposed openstack/swift: Transition to 'keymaster'  https://review.openstack.org/24490423:09
onovyclayg, i think peter just implemented Darrell Bishop suggestion from https://review.openstack.org/#/c/180893/223:11
claygswifterdarrell: ^ review onvoy's patch https://review.openstack.org/#/c/180893/223:11
clayger...23:11
claygswifterdarrell: patch 24304023:11
patchbotclayg: https://review.openstack.org/#/c/243040/ - Log error if a local device not identified23:11
onovyPeter's patch :)23:12
*** wbhuber has quit IRC23:12
claygah - sorry23:13
onovynp, i was my suggestion, peter's code :)23:13
onovyit23:13
claygonovy: oic - you have *people* for this sort of work?23:14
clayg;)23:14
onovywe have simple workflow in seznam. i say: implement this and peter will send review. life is good :)23:14
onovyyou gonna do what you gonna do...23:14
onovygotta sry23:15
*** jlhinson has quit IRC23:16
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/17398223:18
*** kei_yama has joined #openstack-swift23:26
*** wuhg has joined #openstack-swift23:26
*** mac_ifie_ has quit IRC23:27
*** alejandrito has quit IRC23:31
*** petertr7 is now known as petertr7_away23:32
*** thumpba has quit IRC23:34
*** diazjf has joined #openstack-swift23:40
*** diazjf1 has joined #openstack-swift23:43
*** diazjf has quit IRC23:46
*** chsc has quit IRC23:50
*** mwheckmann has joined #openstack-swift23:52
*** nadeem has quit IRC23:57

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