Wednesday, 2016-05-11

*** lyrrad has quit IRC00:02
*** delatte has quit IRC00:08
*** pgbridge has quit IRC00:11
openstackgerritSamuel Merritt proposed openstack/swift: Skip SLO-reconciling probe test when SLO is off
*** chlong_ has joined #openstack-swift00:22
*** chlong_ has quit IRC00:22
kota_good morning00:23
*** chlong_ has joined #openstack-swift00:27
*** chlong_ has quit IRC00:28
mattoliveraukota_: morning00:29
kota_mattoliverau: morning, I'm reading the irc log looks like a bunch of conversation yesterday.00:32
kota_tdasilva: great work for pyeclib/liberasurecode migration, I will look at, thanks!00:40
*** thumpba has joined #openstack-swift00:48
hosanaigood morning00:51
kota_hosanai: morning00:53
hosanaikota_: morning!00:53
hosanaiclayg: I fixed vsaio (with keystone) in my repo. The content of the fix is removed last two commits and used stable/liberty branch of keystone.00:53
mattoliverau hosanai: morning00:56
hosanaimattoliverau: morning!00:56
*** ozialien10 has quit IRC00:59
tdasilvakota_: thanks, I have to push a some fixes01:01
*** sgundur- has left #openstack-swift01:01
tdasilvacan anybody figure out why patch 311219 is not merging?01:03
patchbottdasilva: - swift - Remove ThreadPool class01:03
kota_tdasilva: looks like patch 311219 is waiting the previous depended patch landed.01:10
patchbotkota_: - swift - Remove ThreadPool class01:10
kota_but patch 310864 (the previous patch) looks stalling at zuul verification.01:11
patchbotkota_: - swift - Remove threads_per_disk setting01:11
kota_not sure01:11
*** tqtran has quit IRC01:12
tdasilvakota_: duh, I'm still not used to the new gerrit gui when it comes to dependencies, older gui was much easier to see01:13
tdasilvakota_: thanks01:13
kota_tdasilva: agree, current gui is too complicated so I just downloaded the patch set via git review -d <n> and look at the git log history ;)01:14
openstackgerritMerged openstack/swift: Remove threads_per_disk setting
*** klamath has quit IRC01:37
openstackgerritMerged openstack/swift: Remove ThreadPool class
kota_tdasilva: congrats :)01:37
*** klamath has joined #openstack-swift01:38
*** suyash has quit IRC01:43
*** dmorita has joined #openstack-swift01:54
*** natarej has quit IRC01:58
*** dmorita has quit IRC01:58
*** natarej has joined #openstack-swift01:59
*** NM has quit IRC02:13
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC ring validation at ring reload
*** sgundur- has joined #openstack-swift02:16
*** sgundur- has left #openstack-swift02:16
openstackgerritSamuel Merritt proposed openstack/swift: Make eventlet.tpool's thread count configurable in object server
*** gyee has quit IRC02:20
notmyname#success threads per disk has been removed02:23
openstackstatusnotmyname: Added success to Success page02:23
*** klamath has quit IRC02:41
*** sheel has joined #openstack-swift02:53
*** dmorita has joined #openstack-swift02:54
*** sgundur- has joined #openstack-swift02:58
*** sgundur- has left #openstack-swift02:58
*** thumpba has quit IRC03:04
*** links has joined #openstack-swift03:21
*** ankur has joined #openstack-swift03:27
*** Jeffrey4l has joined #openstack-swift03:35
openstackgerritMerged openstack/swift: resurrect gholt blog posts on building consistent hashing ring
*** dmorita has quit IRC03:44
*** dmorita has joined #openstack-swift03:56
*** dmorita has quit IRC04:01
*** pcaruana has joined #openstack-swift04:02
openstackgerritTim Burke proposed openstack/swift: Allow concurrent bulk deletes
jrichliclayg sgundur- acoles eranrom : I was wrong that my config was the issue.  I never have gotten a successful run on those 3 container-sync probetests using anything later than patch 27096104:13
patchbotjrichli: - swift - Container-Sync to perform HEAD before PUT object o... (MERGED)04:13
jrichliacoles is not seeing the error, and I have run with the same contents as he has in my container-sync-realms.conf04:14
jrichlieranrom: the error I am seeing happens every time - not just intermittently04:15
*** arch-nemesis has joined #openstack-swift04:16
openstackgerritMahati Chamarthy proposed openstack/swift: crypto: Remove BYOK support
*** esker has joined #openstack-swift04:24
*** dmorita has joined #openstack-swift04:27
*** esker has quit IRC04:28
*** dmorita has quit IRC04:30
*** arch-nemesis has quit IRC04:35
*** psachin has joined #openstack-swift04:42
*** takashi has joined #openstack-swift04:47
takashigood afternoon :-)04:47
kota_takashi: good afternoon04:49
*** takashi has quit IRC04:52
*** takashi has joined #openstack-swift04:55
*** rcernin has joined #openstack-swift04:58
*** thumpba has joined #openstack-swift05:05
*** thumpba has quit IRC05:10
openstackgerritMahati Chamarthy proposed openstack/swift: crypto: Override flag to fix probe tests
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix EC ring validation at ring reload
*** ChubYann has quit IRC05:26
janonymouspdardeau: Nice work on ring overview doc.05:30
*** silor has joined #openstack-swift05:33
*** silor1 has joined #openstack-swift05:38
*** silor has quit IRC05:39
*** silor1 is now known as silor05:39
*** ankur has quit IRC06:07
mahaticjrichli: could you post the 3 probe test errors you see with container-sync? Want to verify06:08
*** itlinux has joined #openstack-swift06:18
*** david-lyle has quit IRC06:23
*** david-lyle has joined #openstack-swift06:27
eranrommahatic, jrichli, acoles_: The tests that fail are in Amongst them are: test_sync_with_post_as_copy, test_sync_with_stale_container_rows06:27
eranromBasically what the test does is (1) create a source and target containers with the appropriate metadata for unidirectional replication06:28
eranrom(2) add some stuff to the source06:28
eranrom(3) have the sync daemon to work06:28
eranrom(4) validate that objects are replicated06:28
mahaticeranrom: thanks! are they 2 errors or 3? I also see this one: ERROR: test_sync_with_fast_post (test.probe.test_container_sync.TestContainerSync)06:29
eranrommahatic: there are 3 but I need to run once more to find it.06:29
*** jmccarthy has quit IRC06:29
*** jmccarthy has joined #openstack-swift06:30
eranromWhat happens is that replication fails, because on the target side, the container_sync middleware fails to retrieve the sync key (when using get_container_info), since getting the info always seem to fail on the first time.06:30
*** dmorita has joined #openstack-swift06:31
*** mmcardle has joined #openstack-swift06:31
eranromThe get_info code seem to populate the cache but fail to actually return the info. The second time get_info is called the cache is populated and everything works fine.06:32
eranromThus, a workaround would be e.g. to do head on the target container as soon as it is created with the sync key metadata.06:32
eranromBut changing the test accordingly would be cheating :0)06:32
eranromThis is why I posted yesterday a question on the get_info code.06:33
eranromI will try to dig deeper into this.06:33
*** ppai has joined #openstack-swift06:34
mahaticeranrom: thanks for the details, that helps06:34
eranrommahatic: thank you for looking.06:34
*** dmorita has quit IRC06:35
hosanaieranrom: interesting. it06:47
hosanaieranrom: sorry. wait a minute06:48
*** zaitcev has quit IRC06:50
*** thumpba has joined #openstack-swift07:06
-openstackstatus- NOTICE: pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved07:08
*** ChanServ changes topic to "pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved"07:08
*** rcernin has quit IRC07:09
*** rcernin has joined #openstack-swift07:10
hosanaieranrom: i try to understand the root of code. Is it passed L575 at here make a req with env.copy() at L551 in then uses it at L57507:11
*** thumpba has quit IRC07:11
hosanaieranrom: if above root is correct, i would like to try env instead of env.copy() at L551 to narrow down the problem.07:11
hosanaieranrom: btw i have an idea for workaround; when getting container info fails, tries to get it again in base.py07:12
*** SkyRocknRoll has joined #openstack-swift07:12
eranromhosanai: regarding the workaround, I tried it (in get_info I called the get from cache once more) but then got some strange unit tests failures07:14
eranromhosanai: The lines above (e.g. L551) are  in or
hosanaieranrom: L551 in versioned_writes.py07:15
*** rledisez has joined #openstack-swift07:16
eranromhosanai: gotcha, you are saying that this env.copy breaks the assumption made by the get_info code (regarding GETorHEAD_base updating the env)?07:17
hosanaieranrom: yep, i don't have container-sync env now (i couldn't reproduce it) so i guess the code is related to this issue.07:21
eranromhosanai,: wow good catch!!! Can I just try to remove it from the pipeline?07:22
eranromwould it break anything?07:22
hosanaieranrom: my idea is use "req = Request(env)" instead of "req = Request(env.copy())" for investigation...07:25
*** daemontool_ has joined #openstack-swift07:26
eranromhosanai: right, but I thought that there might be a ggod reason why it has a copy so I asked about removing it from the pipeline. Anyway, the probtests work when the versioned_writes are removed from the pipeline!!!07:27
eranromLet me try with your suggestion now.07:28
*** klrmn has quit IRC07:31
eranromhosanai,: your suggestion also works! That was a superfast root cause analysis!!!07:31
*** jmccarthy1 has joined #openstack-swift07:46
eranromacoles_,:Any chance that the container sync probe tests work for you due to not having versioned_writes in the pipeline?07:47
*** chlong has quit IRC07:49
kota_eranrom: just small note, env is a dictionary for HTTP environment variable and if it's updated, the update will be remaining anywhere.07:50
kota_eronrom: that's reason why env.copy() is needed to save the original environment dictionary.07:51
openstackgerritMerged openstack/python-swiftclient: Check responses when retrying bodies
kota_eranrom: for safety, trying to use make_subrequest might be a solution to keep the env safe07:52
hosanaieranrom: thanks for the trial :-) it's not reach to the root cause.07:59
*** ntt has quit IRC08:01
*** jordanP has joined #openstack-swift08:01
*** SkyRocknRoll has quit IRC08:03
hosanaieranrom:  the approach works, the env.copy is not necessary for L575 so move "req = Request(env.copy())" to  L580  .08:03
hosanaieranrom: only for COPY req08:04
eranromgotcha. So why are you saying this is not the root cause :-) ?08:05
hosanaieranrom: we just know the root of problem but don't know the reason08:06
*** mingdang1 has joined #openstack-swift08:06
eranromyou mean the reason why the copy middleware does an env.copy?08:06
kota_hmm...probably I am missing some key points, quit out from the conversation.08:06
eranromkota_,no worries, here is the point: from some reason the versioned_writes middleware creates a new request with an enc.copy for each request that passes through it. Thus, any modifications done on the env after versioned_writes is not seen by any middleware before it.08:07
*** ntt has joined #openstack-swift08:08
*** mingdang1 has quit IRC08:08
hosanaieranrom: i'm in meeting now so i will check the conversation later, sorry...08:08
*** mingdang1 has joined #openstack-swift08:08
*** dmk0202 has joined #openstack-swift08:08
eranromhosanai,: sure, thatks for the help!08:08
eranromkota_,does this make sense? Do you think that make_subrequest bypasses this?08:09
kota_not sure but make_subrequest is for keeping some important variables.08:10
kota_km: wooa?08:10
kota_well, wait, I don't have clear memory for it.08:11
kmsorry miss08:12
*** ntt has quit IRC08:12
kota_eranrom: maybe, i'm still in fog. do you mean the env updated in the subrequest will be missing at the middleware located in left of versioned_writes, right?08:13
*** km has left #openstack-swift08:14
eranromkota_,right. more precisely any updates made to the right of versioned writes will not bee seen08:14
*** asettle has joined #openstack-swift08:14
eranromkota_,: that is any updates to the env.08:15
kota_interesting, and sounds reasnable. that is because it will prevent any information leak to left side.08:15
kota_and versioned_writes should be at the most right side in the pipeline.08:16
*** SkyRocknRoll has joined #openstack-swift08:16
kota_so the proxy-app is only a man can update the env.08:16
kota_ah, except proxy-logging and proxy-app08:17
kota_eranrom: so what's env value do you expect to pass to left side?08:17
*** daemontool_ has quit IRC08:18
eranromkota_,: so in general many 'middlewares' do a get_info_(account/container). the get_info code looks at the cache, and if the info is not in cache, it generates a head request that reaches the proxy app. Now, the proxy/controller/ GETorHEAD_base populates the cache but also puts the required info on the env08:19
eranromkota_,: and so the env is where the get_info code (called by the middleware) is looking for the info.08:20
*** daemontool_ has joined #openstack-swift08:20
eranromkota_,: the result is that any first call to get_info would fail. On the seconde call it will find it in cache.08:20
kota_(the first call try env info, and then try memcache and then GETorHEAD and cache it into memcache and env)08:22
eranromkota_,: I think so yes08:25
kota_and the env will be passed through from left to right.08:26
*** Shashikant86 has joined #openstack-swift08:26
*** cbartz has joined #openstack-swift08:26
kota_so I'm wondering why there is a problem at the left middleware if a middleware in right update the account/container info that will be added only when the left didn't do get_info.08:28
kota_the left middlware does something (refer the info) when the response comming back from right middleware?08:29
eranromkota_, exactly.08:29
kota_ah, the anlysis is still WIP?08:30
eranromget_info generates a head request with some env. this is done to the left of versioned_writes. then versioned writes copies the env, then GETorHEAD  updates the copied env, and so the code in get info that is after the head does not see that change08:31
eranromwell, this is something that hosanai has found. He also made the point that versioned_writes does not need to do the copy for every request that passes it, but rather only for request whose method is COPY (and perhaps also delete and put)08:32
*** Shashikant86 has quit IRC08:33
eranromtwo initial test where I (1) removed the versioned_writes from the pipeline  and (2) changes the env.copy to env seem to soleve the problem08:33
eranromkota_,: so this is where we stand08:33
kota_but no answer right now, but sounds like it may appear when merging "decouple versioned writes from COPY"08:36
kota_that patch changes the handling COPY to GET/PUT and it touches env dictionary.08:37
eranromneed to look at the patch08:38
*** takashi has quit IRC08:38
*** jistr has joined #openstack-swift08:38
*** Shashikant86 has joined #openstack-swift08:44
*** Shashikant86 has quit IRC08:45
hosanaieranrom, kota_: i'm back. i have been searching patches which are related to this. could you double check/try patch 280977?08:50
patchbothosanai: - swift - Make info caching work across subrequests08:50
*** kei_yama has quit IRC08:53
*** ndk has quit IRC08:54
*** ndk_ has joined #openstack-swift08:55
hosanaieranrom, kota_: could you also double-check patch 280978?08:55
patchbothosanai: - swift - Fix up get_account_info and get_container_info08:55
eranromhosanai: will review thanks!08:56
kota_hosanai: looks like what we might need (not sure), thanks.08:59
kota_hosanai: I need more time to look at the problem and solution.09:00
*** thumpba has joined #openstack-swift09:10
*** acoles_ is now known as acoles09:14
*** thumpba has quit IRC09:15
*** tesseract has joined #openstack-swift09:20
*** daemontool_ has quit IRC09:21
acoleseranrom: i have versioned_writes in pipeline, but even if it is not explicitly there it *should* be auto-inserted - take a look at your proxy log at startup and it will have a log of the pipeline (grep "Pipeline is" )09:22
*** daemontool_ has joined #openstack-swift09:22
kota_eranrom: I'm not sure but I'm realizing if we can doubt the memcache setting?09:27
kota_scrolling back to the log, you described as the first call failed, and second succeeded.09:27
acoleseranrom: but...I had allow_versioned_writes=False, when True I see the tests fail :/ which makes sense because when you remove versioned_writes from the pipeline, it will be auto-inserted but with its default settings which is allow_versioned_writes=false09:28
*** takashi has joined #openstack-swift09:28
acoleseranrom: and the copied request environ is not used when allow_versioned_writes is false09:28
kota_if memcached server halted with some reasons, memocache.get in get_info  failed but the second will succeed because the HEAD result will be in env.09:29
kota_not sure though.09:29
kota_need to look at/and test.09:30
*** takashi has quit IRC09:30
kota_eranrom: sorry I'm running out of time, keep it in my heads, hope to talk later.09:32
kota_see you.09:32
*** daemontool_ has quit IRC09:40
*** daemontool_ has joined #openstack-swift09:40
*** daemontool_ has quit IRC09:40
*** daemontool_ has joined #openstack-swift09:40
eranromacoles, kota_: alright, so it seems like hosanai nailed the problem. I need to go offline now. talk to you later. Thanks!09:42
*** sanchitmalhotra has joined #openstack-swift09:43
*** sanchitmalhotra1 has quit IRC09:43
acoleseranrom: kota_ i just made a small patch that fixes it, will push to gerrit fyi09:43
mahaticeranrom: glad to know the root cause. hosanai: nice catch!09:49
*** sanchitmalhotra1 has joined #openstack-swift09:54
*** sanchitmalhotra has quit IRC09:56
hosanaieranrom: how to re-produce the problem? just execute probe test? i still couldn't re-produce it...10:04
hosanaiacoles: oh, you already made a patch for it. great!10:04
acoleshosanai: kota_ eranrom jrichli i didn't see a bug report so made one
openstackLaunchpad bug 1580528 in OpenStack Object Storage (swift) "container sync probe tests fail when allow_versioned_writes is true" [Undecided,New]10:05
acolesyou may like to add your diagnosis of the cause ^^10:07
openstackgerritAlistair Coles proposed openstack/swift: Use original environ in versioned_writes container handling (WIP)
*** daemontool_ has quit IRC10:08
*** daemontool_ has joined #openstack-swift10:08
*** mingdang1 has quit IRC10:10
acoleshosanai: kota_ eranrom jrichli that is a quick fix ^^, I don't have time yet to know if it is a complete fix, or the best fix, and the patch could do with a unit test, so it's WIP and I am more than happy for someone else to take it on as co-author or squash or copy10:10
*** mingdang1 has joined #openstack-swift10:10
*** stevemar has quit IRC10:13
*** stevemar has joined #openstack-swift10:15
hosanaiwith this bug staticweb with versioned_write might not working... i have to leave now see you later.10:15
*** hosanai has quit IRC10:15
*** natarej has quit IRC10:16
*** natarej has joined #openstack-swift10:17
*** daemontool_ has quit IRC10:17
*** daemontool has joined #openstack-swift10:18
*** naseer036 has joined #openstack-swift10:32
*** daemontool has quit IRC10:48
*** naseer036 has quit IRC10:49
openstackgerritAlistair Coles proposed openstack/swift: crypto - don't break conditional GETs on unencrypted objects
*** jistr is now known as jistr|mtg11:00
openstackgerritMerged openstack/swift: crypto - add functional test to verify container listing detail
*** jamie_h has quit IRC11:46
*** ppai has quit IRC11:50
*** ChanServ changes topic to "Let's talk! We're nice | Review Dashboard: | Logs: | Meetings: | Community Dashboard:"11:59
-openstackstatus- NOTICE: We have a workaround for our mirrors to attempt to translate package names if a match isn't immediately obvious. A more complete fix is yet to come. It is now safe to 'recheck' any jobs that failed due to "No matching distribution found". Please join #openstack-infra if you discover more problems.11:59
*** ppai has joined #openstack-swift12:01
*** jistr|mtg is now known as jistr12:11
*** mmcardle has quit IRC12:16
*** asettle has quit IRC12:20
*** ppai has quit IRC12:23
*** marcusvrn_ has joined #openstack-swift12:24
*** mmcardle has joined #openstack-swift12:27
*** openstackgerrit has quit IRC12:33
*** openstackgerrit has joined #openstack-swift12:33
*** ppai has joined #openstack-swift12:36
*** jamielennox is now known as jamielennox|away12:45
*** ppai has quit IRC12:46
*** asettle has joined #openstack-swift12:47
*** daemontool has joined #openstack-swift12:51
*** links has quit IRC12:52
*** daemontool has quit IRC12:53
*** jamielennox|away is now known as jamielennox12:53
*** daemontool has joined #openstack-swift12:53
*** jamie_h has joined #openstack-swift12:56
*** takashi has joined #openstack-swift12:57
*** pauloewerton has joined #openstack-swift12:58
*** rickyrem has joined #openstack-swift13:01
kota_hmm.... looks like the reason why versioned_writes does env.copy() is that versioned_writes can mangle the env['PATH_INFO'] when the method is COPY?13:16
kota_if it's true, req instance in __call__ method should use the original (not copy) and then do make_subrequest if another path (e.g. for get_source or for put to versions container)13:18
kota_just dumping what I thought.13:18
openstackgerritMonty Taylor proposed openstack/swift: Update paths to point to
openstackgerritMonty Taylor proposed openstack/swift: Add godep manifest file
*** BAKfr has quit IRC13:26
*** BAKfr has joined #openstack-swift13:28
*** dmorita has joined #openstack-swift13:32
kota_ah, the reason why object_request is not affected the env.copy() problem is it will call, start_response) directly w/o env copy.13:33
*** cdelatte has joined #openstack-swift13:33
kota_but it is still complicated with the code. hm....13:33
*** daemontool has quit IRC13:34
*** dmorita has quit IRC13:36
*** klamath has joined #openstack-swift13:38
*** cdelatte has quit IRC13:38
*** klamath has quit IRC13:38
*** chlong has joined #openstack-swift13:38
*** klamath has joined #openstack-swift13:38
openstackgerritNandini Tata proposed openstack/swift: add Tempest Plugin for functional tests
*** SkyRocknRoll has quit IRC13:53
*** ametts has joined #openstack-swift13:56
*** thumpba has joined #openstack-swift13:57
*** daemontool has joined #openstack-swift13:58
*** links has joined #openstack-swift14:01
*** _JZ_ has joined #openstack-swift14:01
pdardeaujanonymous: thx14:12
*** sgundur- has joined #openstack-swift14:13
*** daemontool has quit IRC14:13
*** mingdang1 has quit IRC14:20
pdardeaugood morning14:22
kota_pdardeau: good morning14:23
pdardeaukota_: o/14:23
pdardeaukota_: surprised to see you online at this hour!14:23
kota_pdardeau: :) usually I'm here at wednesday night.14:24
*** daemontool has joined #openstack-swift14:31
*** hezhiqiang has joined #openstack-swift14:36
*** lowecase has joined #openstack-swift14:37
acoleskota_: yeah i don't think that env.copy is required for *all* requests, patch 31494714:38
patchbotacoles: - swift - Use original environ in versioned_writes container...14:38
acoleskota_: maybe that patch ^^ should use the original env for some obj requests too??14:39
acolesjrichli: ^^14:39
*** takashi has quit IRC14:39
kota_acoles: probably the reason why object request is not affected is the object_request can take the original env like self.object_request(*snip*)(env, start_response)14:41
kota_i.e. object_request will return and it will take the original env (not copied)14:42
kota_and then the call is probably for the original request (e.g. PUT object, in my looking).14:43
acoleskota_: you mean line 583?14:44
kota_it seems all requests in object_request method are subrequests14:45
*** daemontool has quit IRC14:45
kota_i mean just only for PUT object case though.14:45
kota_(COPY too but I didn't check deeply for DELETE object case)14:46
acoleskota_: yes, the object put path always returns, then, start_response) is called like you say14:49
acolesthe delete path is less obvious.14:49
*** pgbridge has joined #openstack-swift14:49
acolesI think the delete path may end up with the copied environ being used in the response14:50
kota_acoles: maybe true, in my memory, the delete case's response should be from DELETE versioned_container/previous_version_object14:51
*** lowecase has quit IRC14:52
*** lowecase has joined #openstack-swift14:52
kota_that HTTP request path info should be different from the original env, so I think it would be handled as subrequest with copied env.14:53
kota_not yet look around there.14:53
acoleskota_: anyway I agree that the env should not be copied so early in the __call__14:53
*** links has quit IRC14:54
kota_acoles: exactly, imo, we should copy (i like to use make_env or make_subrequest) only when it's obviously subrequset different from the original request path.14:55
*** daemontool has joined #openstack-swift14:55 is becomming tommorow, pend this as tommorow's task14:57
*** lowecase has quit IRC14:57
kota_acoles: sorry, will look at your patch tommorow. thanks.14:57
*** lowecase has joined #openstack-swift14:58
* tdasilva is trying to come up to speed on this discussion14:58
*** pgbridge has quit IRC15:01
acolestdasilva: summary - versioned_writes makes a copy of the request environ, which means that get_info updates the info in the copied environ, which seems to cause container_sync probe tests to fail because a get_info doesn't return container info, although I'm not sure why the info isn't found in memcache.15:02
tdasilvaacoles: mmm..interesting...while looking at the bug, it seems that the problem only shows up if user explicitly sets allow_versioned_writes to True ???15:03
*** lowecase has quit IRC15:03
acolestdasilva: yes because otherwise versioned_writes does not actually use the copied env for container requests15:04
tdasilvabtw...if I remember correctly, with copy middleware, we get rid of the env.copy all together15:04
tdasilvabecause copy requests never reach versioned_writes middleware15:04
acolesof course!15:05
patchbottdasilva: patch 156923 - swift - Refactor server side copy as middleware15:05
tdasilvaacoles: would that help?15:06
*** arch-nemesis has joined #openstack-swift15:12
*** jistr has quit IRC15:13
*** diogogmt has joined #openstack-swift15:14
*** esker has joined #openstack-swift15:17
*** pgbridge has joined #openstack-swift15:20
acolestdasilva: i think it would! kota_ eranrom jrichli ^^15:20
acolescopy middleware will save us :)15:20
tdasilvaacoles: re copy middleware, there's already a +2 from timburke but mattoliverau left a -1 that I think is worth making the changes he suggested, especially the one around renaming the middleware to just copy15:21
tdasilvait would be a small enough change, maybe we can still land this patch this week :| ???15:22
admin6Hi there. Sorry to disturb you with some stupid questions but since I’ve upgraded my swift servers to v2.7, I have a lot of messages "STDERR: UnicodeDecodeError" in the object-replicator logs that I didnt’ saw before with v2.5. These logs appears when rebalancing a replica3 object ring (more logs in, have you suggestions regarding that encondind/decoding problem/warning ?15:23
jrichlitdasilva: let's hope timburke is ok with the name change :-)15:25
tdasilvajrichli: yeah, I'd like to hear from timburke first to make sure he is ok with it15:26
*** esker has quit IRC15:26
*** esker has joined #openstack-swift15:27
*** klrmn has joined #openstack-swift15:27
acolestdasilva: yes, I agree about the name, I just never had the courage to say so - +1 for mattoliverau15:28
acolesalso agree, check with timburke15:28
acolestdasilva: just leaving a couple of replies to mattoliverau's other comments15:28
tdasilvaacoles: cool! thanks15:29
acolestdasilva: how about just 'cp'15:29
*** jistr has joined #openstack-swift15:31
*** diogogmt has quit IRC15:33
*** jistr has quit IRC15:33
*** jistr has joined #openstack-swift15:33
acolestdasilva: the doc dup could be cleaned up in a follow up but imho if the name is changing it should change before merging15:34
tdasilvaacoles: agreed15:35
*** dmorita has joined #openstack-swift15:42
*** dmorita has quit IRC15:43
sgundur-jrichli: hi, sorry had missed the conv yesterday, now went through the discussion in the logs!15:44
jrichlisgundur- : np.  looks like there is something to fix after all :-)15:45
sgundur-jrichli: so now my probetests should pass on master + 314947 ?15:47
*** rcernin has quit IRC15:47
jrichlisgundur- : yes.  I haven't tested that out yet, but will be looking at that patch later today.15:48
sgundur-jrichli: great, I ll try it out now15:48
openstackgerritDavid Goetz proposed openstack/swift: go: shuffle suffix dirs when replicating a partition
acolesjrichli: sgundur- note conversation above from tdasilva that this should also fix the probe test errors
patchbotacoles: patch 156923 - swift - Refactor server side copy as middleware15:51
acolesbe interested if someone has time to verify that15:51
*** dmorita has joined #openstack-swift15:51
*** dmorita has quit IRC15:51
*** dmorita_ has joined #openstack-swift15:51
tdasilvadisclaimer: all I said is that in copy middleware env.copy is removed :D15:52
jrichliacoles: i will try that first15:53
* jrichli can't right now, but will soon15:54
*** lakshmiS has joined #openstack-swift15:55
acolesadmin6: can you file that as a bug report? and if you are able to also include any device names you might have in your ring with non-ascii characters?15:56
acolesadmin6: or I can file it if you don't have/don't want a launchpad account15:57
*** joeljwright has joined #openstack-swift15:57
*** ChanServ sets mode: +v joeljwright15:57
*** diogogmt has joined #openstack-swift15:59
acolesadmin6: btw that's not a stupid question16:00
admin6I don’t have a launchpasd account and I’m not familiar with that. Whet do you mean by device names with non-ascii chars?16:00
admin6acoles: thanks :-)16:00
*** nadeem has joined #openstack-swift16:01
*** nadeem has quit IRC16:01
*** nadeem has joined #openstack-swift16:02
admin6acoles: here is my swift-ring-builder result for that ring
janonymousacloes: is it double encoding case?16:03
*** dmk0202 has quit IRC16:07
*** pgbridge has quit IRC16:07
*** esker has quit IRC16:08
*** lyrrad has joined #openstack-swift16:11
*** gyee has joined #openstack-swift16:13
admin6acoles: I juste remember already having an ubuntu one account so I’ve create a bug report :
openstackLaunchpad bug 1580678 in OpenStack Object Storage (swift) "UnicodeDecodeError when rebalancing a ring" [Undecided,New]16:20
admin6acoles: I must leave now, I’ll be available tomorrow. thanks.16:21
acolesadmin6: thanks16:21
*** cbartz has quit IRC16:23
*** klrmn has quit IRC16:25
*** rledisez has quit IRC16:34
timburkegood morning16:37
claygjrichli: heh, after "fixing" my config (servers per port) the container sync probe tests passed for me16:42
claygjrichli: but I am still getting 3 error tests - something about KeyError - is there *really* a patch for that which hasn't landed yet (!?)16:42
*** Jeffrey4l has quit IRC16:43
*** nadeem has quit IRC16:44
notmynameI just +A'd to get some of the probe tests fixed16:46
patchbotnotmyname: patch 311899 - swift - Fix probe tests from commit cf48e7516:46
AJaegernotmyname: IMHO is ready for merge now - the other-requirements.txt introduction.16:47
AJaegerYou can always add additional files later on...16:48
claygwhat is *this* "Suppression partition" !?16:48
notmynameAJaeger: ack16:48
claygnotmyname: so patch 311899 reverts the default port changes - that's cool - but did the saio instructions update remakerings?16:51
patchbotclayg: - swift - Fix probe tests from commit cf48e7516:51
*** nadeem has joined #openstack-swift16:51
claygnotmyname: I'm more worried that if someone did manage to get through the saio instructions they'd end up with a ring config that won't pass probetests?16:51
notmynameclayg: no, I don't think so. that was the bug16:51
claygi suppose I could have just looked :P16:52
notmynameok, stupid question16:53
notmynameI can pip install -r reqs just fine16:53
clayg^ not a question16:53
notmynamebut `tox -e bindep` gives me the classic "error in setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected ',' or end-of-list in dnspython>=1.12.0;python_version<'3.0' at ;python_version<'3.0'" error16:54
notmynamewhy is the tox env not getting the right pip pbr setuptools whatever?16:54
clarkbbecause virtualenv bundles all of that stuff16:54
clarkbso you need to upgrade virtualenv16:54
clarkb(this is one reason that the distros consider bundling to be terribleness)16:55
*** asettle has quit IRC16:55
notmynameclayg: told you it was a stupid question16:56
*** nadeem has quit IRC16:56
notmynameclayg: sorry. I didn't build my whole box from latest-nightly sources16:56
notmynameAJaeger: "ERROR: InvocationError: '/home/swift/swift/.tox/bindep/bin/bindep test'"16:57
*** psachin has quit IRC16:58
AJaegernotmyname: strange ;(16:58
notmynameAJaeger: is that just telling me that the commands didnt' work? or that there's an error somewhere?16:58
AJaegernotmyname: thanks for the gist. It tells you - see line 8 - that you do not have libsqlite3-dev pkg-config installed16:59
notmynameAJaeger: also, does this mean bindep should be added to test-requirements.txt?16:59
AJaegerBut should have...16:59
notmynameAJaeger: "should". I mean, I kinda know that this box does in fact work with swift ;-)16:59
AJaegernotmyname: no, the idea here is to not add it since none of the other jobs needs it.16:59
acolesclayg: you're a genius!17:00
notmynameor maybe my dev box is working because I'm not linking anythign against sqlite?17:00
AJaegernotmyname: that might be the case here...17:00
acolesand so Successful rsync becomes
klamathcan someone help explain the splice function in the object-server conf?17:01
acolesclayg: note the è in Succès de Rsync17:01
AJaegernotmyname: bindep environment includes a dependency on bindep itself - a developer should be able to run "tox -e bindep" and it works, so it should have minimal dependencies.17:01
klamathdoes that help with the o_temp issues with xfs?17:01
*** jistr has quit IRC17:02
AJaegerYou might have in test-requirements packages that need devel libraries, and therefore don't want to install them to avoid a chicken/egg problem.17:02
sgundur-jrichli: acoles - i tried current master + patch156923 ; probetests pass17:02
acolessgundur-: thanks17:02
sgundur-jrichli: acoles: but at the end of unittests - I get this log -
sgundur-probably from here -
AJaegernotmyname: does that answer your questions?17:03
claygacoles: i sorta want *my* logs to say "Succès de Rsync" now :'(17:03
AJaegerspeaking about Infra: There's a change to run keystone V3 jobs on swift for project-config: - I'd like some swift folks to review that, please17:04
patchbotAJaeger: patch 313659 - openstack-infra/project-config - Run Swift functional tests in Identity v3-only17:04
sgundur-acoles: the unittests pass, but just that log at the end17:04
notmynameAJaeger: well, it's an answer :-)17:05
*** mragupat has joined #openstack-swift17:06
notmynameAJaeger: I don't see anything that I'd expect to require sqlite dev headers17:06
*** jmccarthy1 has quit IRC17:07
AJaegernotmyname: should I remove those two entries from my change?17:07
*** BAKfr has quit IRC17:08
AJaegerI can respin easily... Just like to finish this soon if possible before I disappear for two weeks of vacation...17:08
notmynameunless someone else has reason to believe that we actually require libsqlite3-dev or pkg-config17:08
acolesclayg: how about rotating locales so you get a new language every day ;)17:08
AJaegerlet's remove them - and you can always add back ;)17:08
openstackgerritAndreas Jaeger proposed openstack/swift: List system dependencies for running common tests
AJaegerSo, let's see whether Jenkins agrees with testing ;)17:09
*** BAKfr has joined #openstack-swift17:10
claygacoles: I only like the ones where rsync comes of sounding smug - "Do you *like* the way I push le bytes?"17:10
acolessgundur-: ah, the ChunkWriteTimeout returns :(17:10
acolesclayg: you mean urrrrsync ;)17:11
claygit's like every time we write a new unittest based on those in-process guys17:11
*** hezhiqiang has quit IRC17:12
*** nadeem has joined #openstack-swift17:12
*** ChubYann has joined #openstack-swift17:16
*** klrmn has joined #openstack-swift17:17
*** tqtran has joined #openstack-swift17:18
acolesAJaeger: ack re patch 313659, I'll try to take a look17:28
patchbotacoles: - openstack-infra/project-config - Run Swift functional tests in Identity v3-only17:28
AJaegerthanks, acoles17:30
*** dmorita has joined #openstack-swift17:31
*** openstackgerrit has quit IRC17:33
*** openstackgerrit has joined #openstack-swift17:33
*** dmorita_ has quit IRC17:34
*** sileht has quit IRC17:37
*** silor has quit IRC17:43
*** sileht has joined #openstack-swift17:44
*** acoles is now known as acoles_17:45
jrichliclayg: not sure what the KeyError is for.  There were 2 issues I knew of: the ports - which is fixed by a patch about to be merged - and the 3 container-sync issues related to versioning that you wont see if you have versioned writes off.17:53
*** CaioBrentano has joined #openstack-swift17:53
*** dmorita has quit IRC17:54
*** thumpba has quit IRC17:54
*** dmorita has joined #openstack-swift17:54
*** thumpba has joined #openstack-swift18:05
*** ChubYann has quit IRC18:11
*** dmorita has quit IRC18:12
*** dmorita has joined #openstack-swift18:13
*** dmorita has quit IRC18:13
*** raildo has joined #openstack-swift18:17
raildohey guys, I'm working to create a new job that runs swift functional tests in a identity v3-only devstack, and adds this job to the swift pipeline but I need someone on swift core team to take a look on this patch:
patchbotraildo: patch 313659 - openstack-infra/project-config - Run Swift functional tests in Identity v3-only18:18
openstackgerritMonty Taylor proposed openstack/swift: Use govendor to help manage requirements
notmynameraildo: earlier acoles_ said he'd look at it. (but it's already evening for him so probably not until tomorrow at the earliest)18:20
raildonotmyname: ok, np. thanks :)18:20
notmynamedfg_: so you know where the monty patches are coming from....18:21
notmynamedfg_: for looking at the best way to do dependency management, there's godep, glide, and govendor. he's proposing patches for each of those so we can compare and see what they're like18:21
notmynamedfg_: probably we'll use either govendor or glide over godep18:22
notmynamedfg_: and nobody's expecting these specifically to land. it's more of "ok, that's what it looks like, can we live with it and does it work" sort of thing18:22
openstackgerritMonty Taylor proposed openstack/swift: Use glide for dependency management
*** ChubYann has joined #openstack-swift18:23
sgundur-jrichli: I tried master+311899+314947 ; probetests fail with - ; is it my local settings ?18:25
jrichlisgundur- : interesting.  I haven't seen that one before.  BUT, I haven't tried running with the fix today yet.  Will do soon and let you know.  thx!18:26
openstackgerritAlistair Coles proposed openstack/swift: crypto - cleanup decrypter exception handling
jrichlihas anyone run with a compressed container DB?18:28
sgundur-jrichli: ok, thanks :)18:28
*** natarej has quit IRC18:33
*** natarej has joined #openstack-swift18:34
claygjrichli: pretty sure the KeyError things were the port changes in the tests?18:38
jrichliclayg: ah, ok.  i am surprised you only got 3 of those.  i never did test that version :-)18:39
openstackgerritAlistair Coles proposed openstack/swift: crypto - cleanup decrypter exception handling
tdasilvatimburke: around?18:40
timburketdasilva: yep18:40
tdasilvatimburke: hey! not sure if you had a chance to read up on the convo around copy middleware, but mattoliverau made some suggestions for changes18:41
*** rvasilets__ has joined #openstack-swift18:41
timburkeyeah, i'd been following along a bit. took a long weekend, but was catching up last night18:41
tdasilvatimburke: was wondering if you could take a look and think that they are ok to be made and get a quick +2 from you again :)18:41
timburkewill do18:41
tdasilvaok, I won't push the changes until you give your opinion as I'd prefer to not lose your +2 at this point. mattoliverau said he would be willing to +2 also and leave changes for a follow-up, but I think the name change is worth doing now18:42
openstackgerritAlistair Coles proposed openstack/swift: crypto - cleanup encrypter error handling
*** acoles_ is now known as acoles18:43
*** mragupat has quit IRC18:44
timburketdasilva: yeah, if we're doing the name change, better to do it now. may as well push; i'll be sure to find time today18:47
tdasilvatimburke: thanks!18:47
acolesraildo: will those new v3 only func tests be non-voting18:49
raildoacoles: yes18:49
raildoacoles: this job-suffix 'nv' represent that the job will be non-voting18:50
patchbotraildo: patch 313659 - openstack-infra/project-config - Run Swift functional tests in Identity v3-only18:50
acolesraildo: got it, i suspected that might be the case. like notmyname said I won't be able to look properly til later this week, just finishing today18:51
*** tesseract has quit IRC18:51
raildoacoles: np :)18:52
acolesclayg: might you be able to approve this patch 290391 ? I fear another merge conflict...18:52
patchbotacoles: - swift - Rename hash_cleanup_listdir tests18:52
*** joeljwright has quit IRC18:52
acolesclayg: or perhaps I should say "approuvez s'il-vous-plaît" ;)18:54
pdardeauacoles: clayg: pretty soon we'll see the nick 'grandfromage' show up here :)18:56
openstackgerritThiago da Silva proposed openstack/swift: Refactor server side copy as middleware
acolespdardeau: lol18:58
*** mmcardle has quit IRC19:03
* notmyname afk for a bit19:09
*** NM has joined #openstack-swift19:13
*** acoles is now known as acoles_19:20
*** vint_bra has joined #openstack-swift19:21
dfg_notmyname: ok cool. we will check them out on our end19:30
openstackgerritMerged openstack/swift: Fix probe tests from commit cf48e75
*** lakshmiS_ has joined #openstack-swift19:38
*** thumpba has quit IRC19:38
notmynamedfg_: great, thanks19:38
*** dmk0202 has joined #openstack-swift19:38
*** lakshmiS has quit IRC19:39
notmynametorgomatic: thanks for another great ML post :-)19:40
*** thumpba has joined #openstack-swift19:42
*** thumpba has quit IRC19:43
*** thumpba has joined #openstack-swift19:43
*** thumpba has quit IRC19:45
*** thumpba has joined #openstack-swift19:45
*** nadeem has quit IRC19:50
*** nadeem has joined #openstack-swift19:51
notmynameAJaeger: patch 298313 looks good in the gate :-)19:52
patchbotnotmyname: - swift - List system dependencies for running common tests19:52
notmynamethe golang ML thread has 124 messages from the last 8 days. that's only 15.5 per day! come on! we can do better. with a little extra effort, I think we can get it up to 20 messages per day!19:57
*** mmcardle has joined #openstack-swift19:59
*** daemontool has quit IRC20:09
*** daemontool has joined #openstack-swift20:14
NMHey guys. Just to be sure: the maximum number of objects per container, depends on a lot of things, right?  Like memory, disk i/o, network…20:14
glangeNM_ yes, also if you have big containers you might have troubles with disks holding those big containers filling up before other container holding disks20:16
glangeand you'll also just see a long decline in performance as the number of objects increases20:17
notmynameNM: where the performance is in object PUTs per second in that container20:17
glangeand maybe deletes20:17
glangebut not gets20:18
notmynameglange: people shouldn't be deleting data in swift anyway ;-)20:18
glangethe filling up disks to early thing can be a big problem depending on your cluser/usage patterns20:18
glangeit like doesn't really have a good fix, I think?20:19
NMWell, right now we have 5M objects in a single container. Not sure if it's a big number for swift.20:19
notmynameNM: depends mostly on what kind of media your containers are on. if on flash (SSD) and you're ok with <200 PUTs/s, then you're probably fine until you start running out of space on the SSDs20:20
glangeyeah, SSDs fixes a lot of pain there20:20
notmynameNM: and the other thing to check is the container replication time. large containers will get to a point where it's extremely difficult to keep them in sync.20:21
glangeNM_ the work around is sharding your objects across many containers20:21
NMWhat would define a container as large? Number of objects?20:22
notmynameNM: at 5M objects in a single container (and I assume, growing), it's probably a good idea to think about how you could shard the data across containers20:22
glangejust mod_ on the name20:22
ahaleor you make a ring change and two huge dbs end up on the same device and suddenly fill up completely20:22
NMI'm almost sure we will reach 10M if we do nothing.20:22
glangewrite your application to shard20:22
glange10 containers, 1 million objects per container20:22
NMglange: I'll talk to our devs.20:24
glangedude, devs are the worst :)20:24
glangegood luck20:24
NMhahaha!  We go in group of 3, to talk to devs. Usually it's kind persuasive20:26
notmynamedfg_: is up to datE?20:26
dfg_notmyname: no20:27
notmynamedfg_: there's been a few questions about how to do builds for the golang stuff, so I was poking around at what you had done20:27
dfg_notmyname: oh. well the debian stuff in there is prob not changed but we haven't updated the code there for a while because we changed where we release from to something internal20:30
NMThanks guy.20:30
NMnotmyname: I think it's time to have ssd :D20:31
notmynameNM: you don't?! yeah, always put accounts and containers on flash drives :-)20:31
notmynamedfg_: ok. I'm not particularly concerned with the .deb building (although yes that will be a good starting point for other stuff). maybe a better thing to ask about is how you do tests on your dev VM20:32
notmynamedfg_: so maybe I can imagine what that would look like on a CI/gate image20:32
NMnotmyname: I'll quote you to our backoffice team.20:32
notmynameNM: "some guy on the internet totally said that we need to buy a whole bunch of SSDs"20:33
NMnotmyname: Seenm legit.20:33
*** pcaruana has quit IRC20:42
dfg_notmyname: redbo made a little CI server: it posts to the gerrit but the link needs to be updated to just run off of :8020:43
*** rcernin has joined #openstack-swift20:44
notmynamedfg_: that looks like it's running the upstream functests against a hummingbird deployment. which is good, but doesn't do the hummingburd unittests. right?20:44
dfg_ya i think it does20:46
dfg_ya- at the top of the console input20:46
*** suyash has joined #openstack-swift20:47
notmynamedfg_: ah, ok. I see20:47
*** nadeem has quit IRC20:49
*** joeljwright has joined #openstack-swift20:50
*** ChanServ sets mode: +v joeljwright20:50
notmynamedfg_: having a "set -x" on your test script and/or seeing the job definition on that jenkins server would be really really helpful.20:53
*** Harin has joined #openstack-swift20:55
*** Harin has quit IRC20:56
*** thumpba has quit IRC20:56
jrichlisgundur- : my probetests run cleanly now with those patches - I am not seeing the same error that you have20:57
*** takashi has joined #openstack-swift20:57
bkeller`mine seem fine too20:57
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements
*** acoles_ is now known as acoles20:59
sgundur-jrichli: thanks, ll recheck if I have messed up my settings!20:59
*** raildo is now known as raildo-afk21:00
notmynameswift team meeting time in #openstack-meeting21:00
*** m_kazuhiro has joined #openstack-swift21:03
*** m_kazuhi_ has joined #openstack-swift21:07
*** m_kazuhiro has quit IRC21:10
*** ekarlso has quit IRC21:11
*** ekarlso has joined #openstack-swift21:14
*** pauloewerton has quit IRC21:15
openstackgerritMerged openstack/swift: Rename hash_cleanup_listdir tests
acolesclayg: thanks ^^21:21
claygacoles: i just click whatever buttons you tell me to21:21
*** jordanP has quit IRC21:23
*** lakshmiS_ has quit IRC21:26
*** nadeem has joined #openstack-swift21:28
*** nadeem has quit IRC21:29
*** nadeem has joined #openstack-swift21:30
*** mmcardle has quit IRC21:34
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements
timburkeoh, tdasilva: i think the copy patch may close as a drive-by... thoughts?21:48
openstackLaunchpad bug 1260446 in OpenStack Object Storage (swift) "when you copy a slo the destination doesn't get its content-length and etag set correctly in the container listings" [Undecided,In progress] - Assigned to Alistair Coles (alistair-coles)21:48
*** NM has quit IRC22:00
*** CaioBrentano has quit IRC22:01
mattoliverautimburke, tdasilva: I'll checkout and hopefully +2/+A copy patch post meeting I'm going into.22:02
mattoliverauunless someone does it first of course22:03
*** takashi has quit IRC22:06
*** m_kazuhi_ has quit IRC22:06
*** nadeem has quit IRC22:07
*** kmARC has joined #openstack-swift22:07
acolestdasilva: there is a functional test here which you could use to verify part of fixing bug1260446 (not suggesting you necessarily add it to the patch at this point)22:08
patchbotacoles: patch 248219 - swift - Fix listing of SLO manifest bytes after POST or COPY22:08
acolesclayg: so IIRC you're client driven policy migration use case has the client make any POSTs to the target, and the symlink 'rejects' POSTs with a redirect, but the client shouldn't really be POSTing to a symlink? I think I convinced myself that was workable.22:10
acoless/you're/your/ :?22:10
*** jordanP has joined #openstack-swift22:13
*** jordanP has quit IRC22:14
*** acoles is now known as acoles_22:19
*** ozialien10 has joined #openstack-swift22:21
*** acoles_ is now known as acoles22:21
acolestdasilva: also sgundur- verified that the copy patch fixes the container sync probe test bug
openstackLaunchpad bug 1580528 in OpenStack Object Storage (swift) "container sync probe tests fail when allow_versioned_writes is true" [Undecided,New]22:22
*** acoles is now known as acoles_22:27
*** dmk0202 has quit IRC22:47
*** vint_bra has quit IRC22:53
*** joeljwright has quit IRC22:56
*** bill_az has joined #openstack-swift22:58
*** Jeffrey4l has joined #openstack-swift22:59
*** jamielennox is now known as jamielennox|away23:02
*** mingdang1 has joined #openstack-swift23:03
*** mingdang1 has quit IRC23:13
*** zigo has quit IRC23:14
*** mariusv has quit IRC23:14
*** mingdang1 has joined #openstack-swift23:14
*** zigo has joined #openstack-swift23:15
*** arch-nemesis has quit IRC23:16
*** NM has joined #openstack-swift23:16
*** mariusv has joined #openstack-swift23:16
*** mariusv has quit IRC23:16
*** mariusv has joined #openstack-swift23:16
*** ozialien10 has quit IRC23:27
*** ozialien10 has joined #openstack-swift23:28
*** kei_yama has joined #openstack-swift23:30
*** diogogmt_ has joined #openstack-swift23:34
*** diogogmt_ has quit IRC23:34
*** tamizh_geek has quit IRC23:34
*** tamizh_geek has joined #openstack-swift23:36
*** diogogmt has quit IRC23:37
*** ozialien10 has quit IRC23:37
*** ozialien10 has joined #openstack-swift23:38
*** hosanai has joined #openstack-swift23:40
*** ChanServ sets mode: +v hosanai23:40
hosanaigood morning!23:43
timburkegood morning hosanai!23:44
notmynamehello hosanai23:44
hosanaitimburke, notmyname: hello23:46
notmynameso that's interesting. xenial doesn't let me create an XFS partition with a 256 byte inode. must be 51223:50
notmyname"Minimum inode size for CRCs is 512 bytes"23:50
*** jamielennox|away is now known as jamielennox23:51
notmynameand 512 is now the default23:51
notmynamemy older saio had 256 byte inodes23:54
notmynamethat was precise. anyone want to check on trusty?23:54
*** rvasilets__ has quit IRC23:56
clarkbnotmyname: that man page would appear to be buggy in that case (still says minimum and default is 256 bytes)23:56
notmynameclarkb: yeah, it definitely was the old default :-)23:57
timburkenotmyname: assuming i'm reading the output of xfs_info correctly, trusty seems to work with (and default to) 25623:57
notmynametimburke: thanks23:57
notmynameclarkb: weird. I have xfsprogs 4.3.0 installed (came with xenial server)23:58
notmynamedefinitely an error though23:58

Generated by 2.14.0 by Marius Gedminas - find it at!