Thursday, 2016-01-07

kota_mattoliverau: new baby will come around there but there is a conference.00:00
*** kei_yama has quit IRC00:01
mattoliveraukota_: nope :( .. That's too close to baby o'clock, and I don't want to be on the opposite side of the world if Bec goes into labour.00:01
mattoliverau^bristol00:01
mattoliverauI'd have loved to be there, then I'd go visit my brother. Austin maybe.. But the baby will be only be around 6 weeks old, which might be too hard for my wife if I leave, so we'll see00:03
kota_mattoliverau: gotcha, thanks00:04
notmynamemattoliverau: just got my AUS visa00:05
*** kei_yama has joined #openstack-swift00:06
notmynamemattoliverau: now I just need to actually write my talk ;-)00:06
mattoliveraunotmyname: me too.. I keep procrastinating... I have played with presentty, but 80 charater limit means ascii art diagrams I think will be too small to explain sharding :P00:07
mattoliveraunotmyname: but I did manage to create an ascii swift logo in the right size :P00:07
notmynameI've always had good intentions of using something like that. but frankly using keynote is a *lot* more productive (for the time put in) and works really well00:08
notmynamecool!00:08
notmynamenow I just have to put up with the looks of disdain for taking an apple laptop to LCA ;-)00:08
mattoliveraunotmyname: yeah, well I've fallen back to using stanard slides for now, now I just need content :)00:09
mattoliveraunotmyname: lol, yeah, but most people in the audience seems to have macs now.. which is funny to see :)00:09
*** itlinux has quit IRC00:10
*** itlinux has joined #openstack-swift00:11
*** lcurtis has quit IRC00:29
*** haomaiwa_ has joined #openstack-swift00:33
openstackgerritReedip proposed openstack/swift-bench: Remove support for py33/py26  https://review.openstack.org/26448600:35
*** haomaiwa_ has quit IRC00:38
notmynamelifeless: around?00:40
notmynameI have a question about testrepository00:40
notmynamelifeless: in case you see this later, I'm curious about the comments and reasoning behind patch 26052200:42
patchbotnotmyname: https://review.openstack.org/#/c/260522/ - Put py34 first in the env order of tox00:42
*** tsg has joined #openstack-swift00:42
*** minwoob has quit IRC00:47
*** gyee has quit IRC00:54
*** blmartin has quit IRC00:56
notmynamethis is very cool https://twitter.com/gsvitak/status/68226015185696768101:02
*** Jeffrey4l has joined #openstack-swift01:07
*** zhill has quit IRC01:12
openstackgerritHisashi Osanai proposed openstack/swift: Fix signal handling for daemons with InternalClient  https://review.openstack.org/25934701:16
*** badari has quit IRC01:19
mattoliverauawesome01:21
lifelessnotmyname: hi01:34
*** itlinux has quit IRC01:35
lifelessnotmyname: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068979.html01:35
*** robefran has quit IRC01:42
*** garthb_ has quit IRC01:45
*** tsg has quit IRC01:45
notmynamelifeless: ah, ok01:50
notmynameinteresting01:50
notmynamelifeless: so what would you recommend? tough it out until testr moves out of venv? go ahead and land patch 260522? something else?01:50
patchbotnotmyname: https://review.openstack.org/#/c/260522/ - Put py34 first in the env order of tox01:50
lifelessnotmyname: putting it first seems harmless, no ?01:53
notmynamemaybe? but then again, putting it last seems harmless too ;-)01:54
timburkelifeless: breaks (in a different way) on my mac :(01:54
notmynamelifeless: when your email says "have a discussion about issues" I don't think I know enough about the issues to know what it means01:54
lifelesstimburke: oh :(01:54
lifelesstimburke: thats frustrating01:54
timburkeyup01:54
lifelessnotmyname: so that effort is basically stalled, so I don't recommend any option which involves just waiting on it.01:55
timburkebut i can reproduce the issue in a trusty VM, so...idk01:55
notmynameah ok01:55
notmynamein some ways, I don't really care. it's bootstrapping to get tests to run. that part isn't really important to me (compared to you know, actually having running tests).01:56
notmynametimburke: to be fair, I'm not sure running tests on osx is really a "supported" thing ;-)01:56
timburkeshit, it i could, i'd require they pass on windows :P01:57
notmynamethey do. as long as it's inside a VM running linux ;-)01:57
openstackgerritMichael Barton proposed openstack/swift: Merge branch 'master' into feature/hummingbird  https://review.openstack.org/26451702:17
*** klrmn has quit IRC02:17
*** haomaiwang has joined #openstack-swift02:26
*** haomaiw__ has joined #openstack-swift02:29
*** haomaiwang has quit IRC02:31
*** esker has joined #openstack-swift02:40
*** xiangxinyong has joined #openstack-swift02:45
*** chenhuayi has joined #openstack-swift02:45
*** chenhuayi has quit IRC02:48
*** xiangxinyong has quit IRC02:50
*** sanchitmalhotra has joined #openstack-swift02:53
*** mragupat has joined #openstack-swift02:58
*** haomaiw__ has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** janonymous has joined #openstack-swift03:02
*** links has joined #openstack-swift03:10
*** links has quit IRC03:10
*** links has joined #openstack-swift03:12
*** klrmn has joined #openstack-swift03:15
*** esker has quit IRC03:35
*** esker has joined #openstack-swift03:37
*** Jeffrey4l has quit IRC03:37
*** esker has quit IRC03:41
*** ChubYann has quit IRC03:42
openstackgerritCharles Hsu proposed openstack/swift: Add a note for functional tests with Keystone.  https://review.openstack.org/26266403:47
*** venkat has joined #openstack-swift03:50
*** ppai has joined #openstack-swift03:59
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
jrichliDue to our discussion in the meeting today, I wrote bug 1531698 as a "wishlist" item.  I'd be interested in working on this, if other people thought it'd be a good thing.04:06
openstackbug 1531698 in OpenStack Object Storage (swift) "Create an Advanced Features Matrix - docs and tests" [Undecided,New] https://launchpad.net/bugs/153169804:06
*** esker has joined #openstack-swift04:06
jrichliin the end, it might turn out looking like most of the answers are obvious, and the docs and tests are already being covered, I don't know.  but it might be worth seeing if it covers some things that are missing.04:08
*** mragupat has quit IRC04:08
*** esker has quit IRC04:11
*** esker has joined #openstack-swift04:17
*** Jeffrey4l has joined #openstack-swift04:19
*** esker has quit IRC04:22
*** km__ has quit IRC04:57
*** sanchitmalhotra has quit IRC05:00
*** haomaiwang has quit IRC05:01
*** haomaiwa_ has joined #openstack-swift05:01
*** esker has joined #openstack-swift05:03
kota_mahati: my change on meeting wiki (link to 2016 meeting log) conflicted with your change! you already updated that, thanks!05:04
*** esker has quit IRC05:08
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620105:09
*** mragupat has joined #openstack-swift05:21
mattoliveraujrichli: I don't know, you want to put up your hand to add better testing and documentation to advanced features.. That sounds like a horrible idea, when does adding more and better testing improve a project as complex as swift :p (BTW that's sarcasm and who would say no especially when you are already throwing yourself under the bus for it) ;)05:23
mattoliverau</sarcasm>05:23
openstackgerritKota Tsuyuzaki proposed openstack/swift: Support last modified on listing containers  https://review.openstack.org/19863405:24
kota_was trying to push "reabase" bottun on gerrit, expecting to follow parent patch...05:24
mattoliveraujrichli: sounds good even if it turns out we have adequate testing.. Then at least we know :)05:25
mattoliveraukota_: gerrit api strikes again05:25
* mattoliverau thinks he's had too much coffee at his last meeting and is now in super sarcasm mode05:26
kota_lol05:27
kota_but i don't know how to make sure the branch keep right consistency unless pulling it local :/05:29
kota_looks like it worked as i expected05:30
kota_follow to newest patch of parent and...05:31
kota_wow, keep +1 for previous patch set.05:31
kota_i guess, sometimes it would be good but sometimes it would be worse...05:31
kota_btw, does someone know why stackanalytics halted to keep track to record Swift activities?05:34
kota_or i might be missing something?05:35
kota_http://stackalytics.com/?module=swift&metric=commits commits ended at Dec 12...05:36
*** sanchitmalhotra has joined #openstack-swift05:37
kota_http://stackalytics.com/?module=swift&metric=marks reviews looks to be recorded till Dec 31...05:37
openstackgerritMerged openstack/swift: Fixing the deprecated library function.  https://review.openstack.org/26272205:38
mahatickota_: ah okay :) np05:55
*** esker has joined #openstack-swift05:58
*** haomaiwa_ has quit IRC06:01
*** 7JTABHHZB has joined #openstack-swift06:01
*** esker has quit IRC06:18
*** mragupat has quit IRC06:30
*** PsionTheory has quit IRC06:38
*** SkyRocknRoll has joined #openstack-swift06:40
*** SkyRocknRoll has quit IRC06:46
*** tongli has quit IRC06:51
*** eranrom has joined #openstack-swift06:53
*** aerwin3_ has quit IRC06:53
*** kota_ has quit IRC06:53
*** hurricanerix has quit IRC06:54
*** peluse has quit IRC06:54
*** aerwin3 has joined #openstack-swift06:55
*** kota_ has joined #openstack-swift06:56
*** hurricanerix has joined #openstack-swift06:56
*** peluse has joined #openstack-swift06:56
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873606:58
*** tongli has joined #openstack-swift06:58
*** SkyRocknRoll has joined #openstack-swift06:59
*** esker has joined #openstack-swift07:00
*** 7JTABHHZB has quit IRC07:01
*** esker has quit IRC07:05
*** dmorita has quit IRC07:05
*** haomaiwang has joined #openstack-swift07:07
*** jsuchome has joined #openstack-swift07:29
*** ppai has quit IRC07:34
eranromho_,: Hi07:34
*** klrmn has quit IRC07:37
ho_eranrom: hello07:38
eranromI think your patch is much better, as it is more generic.07:40
eranromAlso, I do not think that there is anything to merge from mine.07:40
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620107:41
ho_eranrom: thanks! i will add your name and upload it later. is it ok for you?07:41
eranromsure, no need to add my name :-)07:42
eranromho: but pehaps add: Closes-Bug: #1419901 to the commit message07:42
openstackbug 1419901 in OpenStack Object Storage (swift) "container-sync checks invalid ClientException" [Critical,In progress] https://launchpad.net/bugs/1419901 - Assigned to Eran Rom (eranr)07:42
eranromho: I am struggling with the following problem - you might have an idea.07:43
ho_eranrom: i will add both. if possible, please test the patch in your env :)07:44
eranromho_,:sure will do.07:44
eranromho: I wanted to do a regression probe test that will make sure the problem does not come up again.07:44
eranromho: I can easily write a probe test that will cause the ClientException to get raised, but I do not know how can I:07:46
eranromeither check the log or loopk at the internal container info07:47
eranromDo you think I can run swift-container-info from a probe test?07:47
eranromho: Anyway I will abondon my patch and test yours in my env.07:48
openstackgerritHisashi Osanai proposed openstack/swift: Fix ClientException handling in Container Sync  https://review.openstack.org/25630607:55
ho_eranrom: sorry for late response. I wanted to use edit func of gerrit and this was a good chance but i did mis-operation 10min before... (i got cold sweat)07:58
*** Jeffrey4l has quit IRC07:58
ho_eranrom: i only changed the commit message and looks succeeded.07:59
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** trifon has joined #openstack-swift08:05
*** dmorita has joined #openstack-swift08:06
ho_eranrom: sorry, i have no idea for the probe test. i think unittest is fine for this case (but i usually made a test with saio for my peace) :-)08:09
*** arnox has joined #openstack-swift08:09
*** dmorita has quit IRC08:10
*** Jeffrey4l has joined #openstack-swift08:11
*** rledisez has joined #openstack-swift08:15
*** silor has joined #openstack-swift08:16
eranromho_: no problem. I will test in my env and update gerrit once done.08:22
*** silor1 has joined #openstack-swift08:26
*** silor has quit IRC08:27
*** silor1 is now known as silor08:27
*** ppai has joined #openstack-swift08:30
*** yatin has joined #openstack-swift08:40
*** esker has joined #openstack-swift08:53
*** esker has quit IRC08:57
openstackgerritMahati Chamarthy proposed openstack/swift: Remove content-type encryption/decryption  https://review.openstack.org/26129208:58
*** jordanP has joined #openstack-swift08:59
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
*** haomaiwang has quit IRC09:08
*** haomaiwang has joined #openstack-swift09:09
*** venkat has quit IRC09:10
*** venkat has joined #openstack-swift09:13
*** ejat_ is now known as ejat09:23
*** ejat has quit IRC09:23
*** ejat has joined #openstack-swift09:23
*** daemontool has joined #openstack-swift09:32
*** haomaiwang has quit IRC09:35
*** jistr has joined #openstack-swift09:41
*** haomaiwa_ has joined #openstack-swift09:45
*** tongli has quit IRC09:48
*** Jeffrey4l has quit IRC09:53
*** haomaiwa_ has quit IRC09:58
*** bkmz has quit IRC10:01
*** bkmz has joined #openstack-swift10:01
*** haomaiwang has joined #openstack-swift10:07
*** Jeffrey4l has joined #openstack-swift10:09
openstackgerritHisashi Osanai proposed openstack/swift: Fix ClientException handling in Container Sync  https://review.openstack.org/25630610:20
*** haomaiwang has quit IRC10:32
*** esker has joined #openstack-swift10:41
*** ho_ has quit IRC10:42
*** haomaiwang has joined #openstack-swift10:45
*** esker has quit IRC10:45
*** haomaiwang has quit IRC10:57
*** yatin has quit IRC11:03
*** acoles_ is now known as acoles11:06
*** haomaiwang has joined #openstack-swift11:08
*** jordanP has quit IRC11:09
*** yatin has joined #openstack-swift11:10
acolesmahatic: are you here? I have a question about your comment on https://review.openstack.org/#/c/21145111:20
*** haomaiwang has quit IRC11:21
mahaticacoles: hello, i'm here11:21
nttHi, is there some procedure to move all data from a swift cluster to another? I have one swift cluster (for dev purposes) where swift_hash_path_suffix and prefix are too "easy" and another cluster in production not yet started. Could I move all data between the two?11:22
acolesmahatic: in https://review.openstack.org/#/c/211451/19/test/unit/common/middleware/test_decrypter.py11:22
acolesyour first comment is correct, my mistake11:22
acolesbut the second I cannot see a problem?11:22
acolesthe bad iv is only used for value of x-object-sysmeta-crypto-meta-test i.e. only the user meta header11:23
acolesthe body iv and crypto_meta is good, i think?11:23
mahaticlooking11:23
*** haomaiwang has joined #openstack-swift11:24
mahatica min please11:24
*** sanchitmalhotra has quit IRC11:28
mahaticacoles: test_get_with_bad_iv_for_object_body - i thinnk a bad iv is not passed on for the body encryption: enc_body = encrypt(body, key, fake_iv())11:28
mahaticacoles:  _test_bad_iv_for_user_metadata and  test_get_with_bad_iv_for_object_body are doing the same, aren't they?11:29
*** sh__ has joined #openstack-swift11:30
acolesmahatic: if we passed a bad is to encrypt then it would raise an error.11:31
acolesmahatic: one test simulates a bad iv being returned in the meta for a header, the other has bad iv in crypto meta for the body11:31
acolesin each case we want to verify that a 500 response is returned11:32
mahaticacoles: I thought that was because of this header: 'X-Object-Sysmeta-Crypto-Meta': get_crypto_meta_header(crypto_meta=bad_crypto_meta11:32
mahaticin test_get_with_bad_iv_for_object_body11:32
sh__Hi All, While doing rebalance I am getting this note:"Dispersion of 33.214188 indicates some parts are not optimally dispersed.You may want to adjust some device weights, increase the overload or review the dispersion report." How to remove it.11:32
acolesbut the response messages are different in each case11:32
acolesmahatic: yes, X-Object-Sysmeta-Crypto-Meta': get_crypto_meta_header(crypto_meta=bad_crypto_meta causes the body decrypt to raise error11:33
*** dmorita has joined #openstack-swift11:33
acoles(but not the header decrypt)11:33
mahaticoh right, that makes sense11:34
mahaticno problem then11:34
acolesok i will fix the other and then merge this11:35
*** haomaiwang has quit IRC11:36
mahaticgreat, thanks11:36
openstackgerritAlistair Coles proposed openstack/swift: Modify unit tests to include real crypto  https://review.openstack.org/21145111:37
*** dmorita has quit IRC11:39
acolesmahatic: done11:39
*** yatin has quit IRC11:39
mahaticyay11:41
*** 16WAAH8AU has joined #openstack-swift11:41
*** 16WAAH8AU has quit IRC11:53
*** haomaiwa_ has joined #openstack-swift11:54
*** esker has joined #openstack-swift11:56
*** esker has quit IRC12:00
*** haomaiwa_ has quit IRC12:01
*** m_kazuhiro has quit IRC12:03
*** haomaiwang has joined #openstack-swift12:06
*** haomaiwang has quit IRC12:13
*** haomaiw__ has joined #openstack-swift12:13
*** esker has joined #openstack-swift12:17
*** esker has quit IRC12:22
*** jmccarthy has joined #openstack-swift12:26
*** tsg has joined #openstack-swift12:32
*** haomaiw__ has quit IRC12:35
*** haomaiwa_ has joined #openstack-swift12:38
*** silor1 has joined #openstack-swift12:41
*** silor has quit IRC12:41
*** silor1 is now known as silor12:41
*** resker has joined #openstack-swift12:50
*** delattec has joined #openstack-swift12:50
*** janonymous_ has joined #openstack-swift12:51
*** haomaiwa_ has quit IRC12:51
*** cdelatte has quit IRC12:52
*** resker has quit IRC12:52
*** Jeffrey4l has quit IRC12:53
*** haomaiwang has joined #openstack-swift12:58
*** haomaiwang has quit IRC13:01
*** haomaiwa_ has joined #openstack-swift13:01
*** Jeffrey4l has joined #openstack-swift13:02
*** links has quit IRC13:07
*** eranrom has quit IRC13:08
*** haomaiwa_ has quit IRC13:09
*** SkyRocknRoll has quit IRC13:11
*** bkmz has quit IRC13:16
*** bkmz has joined #openstack-swift13:16
*** haomaiwa_ has joined #openstack-swift13:16
*** haomaiwa_ has quit IRC13:18
*** urth has quit IRC13:18
*** urth has joined #openstack-swift13:20
*** kei_yama has quit IRC13:21
*** ppai has quit IRC13:21
*** SkyRocknRoll has joined #openstack-swift13:23
*** haomaiwang has joined #openstack-swift13:46
*** jordanP has joined #openstack-swift13:47
*** sh__ has left #openstack-swift13:53
*** wanghua has quit IRC13:53
*** silor has quit IRC13:56
*** dmorita has joined #openstack-swift14:00
*** haomaiwang has quit IRC14:01
*** 5EXAAOC18 has joined #openstack-swift14:01
*** robefran has joined #openstack-swift14:02
*** janonymous_ has quit IRC14:02
*** eranrom has joined #openstack-swift14:03
openstackgerritPeter Lisák proposed openstack/swift: Change schedule priority of daemon/server in config  https://review.openstack.org/23879914:04
*** delatte has joined #openstack-swift14:05
*** dmorita has quit IRC14:05
*** delattec has quit IRC14:08
*** esker has joined #openstack-swift14:11
*** silor has joined #openstack-swift14:14
*** janonymous_ has joined #openstack-swift14:16
*** esker has quit IRC14:20
*** esker has joined #openstack-swift14:21
*** tsg has quit IRC14:22
openstackgerritMahati Chamarthy proposed openstack/swift: Decrypt multipart mime doc  https://review.openstack.org/24837714:25
openstackgerritMahati Chamarthy proposed openstack/swift: Have versioned_writes use reverse listings  https://review.openstack.org/26479014:25
openstackgerritMahati Chamarthy proposed openstack/swift: Log error if a local device not identified in replicator  https://review.openstack.org/26479114:25
openstackgerritMahati Chamarthy proposed openstack/swift: Add functional test for multi-range GET requests.  https://review.openstack.org/26479214:25
mahaticuh oh14:27
*** daemontool_ has joined #openstack-swift14:33
acolesmahatic: problem?14:34
*** daemontool has quit IRC14:34
mahaticacoles: yeah :( 211451 needed this 251606. So i rebased14:37
mahaticbasically this is the chain:14:37
mahatic251606 -> 211451 -> 26129214:38
mahaticnow I want to add 248377 to the end of the chain. Problem is 248377 has latest master changes (with MultiRangeGet tests) and 251606 (first one in chain) is older than that14:39
*** blmartin has joined #openstack-swift14:40
mahaticdid it make any sense? :)14:40
acolesno ;)14:40
acolesso was 248377 based on master?14:41
*** venkat has quit IRC14:41
acolesno that doesnt make sense, sorry14:41
mahaticacoles: heh. okay, patch 248377 needs to be rebased onto patch 261292. But first has latest code than the latter14:41
patchbotmahatic: https://review.openstack.org/#/c/248377/ - Decrypt multipart mime doc14:41
patchbotmahatic: https://review.openstack.org/#/c/261292/ - Remove content-type encryption/decryption14:41
mahaticacoles: 248377 is based on latest master merge you had done14:42
*** badari has joined #openstack-swift14:42
*** petertr7_away is now known as petertr714:43
*** lpabon has joined #openstack-swift14:45
mahaticif I am starting afresh (let's say for some new work, new patch), would I pull the code from feature/crypto and go on from there? (this would generate a commit in git log as Merge "feature/crypto" into <current-branch>"14:45
*** dmorita has joined #openstack-swift14:45
*** minwoob has joined #openstack-swift14:46
acolesmahatic: ok i am confused how you ended up where you are14:46
acolesyes you woul dpull feature/crypto14:46
acoleswhile you are on feature/crypto branch14:47
*** esker has quit IRC14:48
acolesthen git checkout -b new-branch14:48
acolesmake your changes, and git commit -a14:48
*** esker has joined #openstack-swift14:48
acolesyou don't get an auto-generated merge commit message14:49
*** dmorita has quit IRC14:50
*** dslevin_ has quit IRC14:50
*** SkyRocknRoll has quit IRC14:51
mahaticacoles: sorry, I ended up there because of multiple different rebasing14:51
*** lpabon has quit IRC14:51
acolesmahatic: looks like you are not based on the latest version of 21145114:51
mahaticacoles: i only have a remotes/origin/feature/crypto14:51
mahaticacoles: 211451 doesn't have multirangeGET tests from master. (because of old code)14:52
acolesmahatic: ah, 211451 didn't get rebased on latest feature/crypto14:54
mahaticacoles: yup14:54
*** petertr7 is now known as petertr7_away14:55
acolesmahatic: so maybe your patch was based on feature/crypto, you rebased onto the 211451 and as a result re-played head of feature/crypto onto 21145114:56
acolesmahatic: bbiab, need to fetch my cake before it disappears :D14:57
*** Vinsh has quit IRC14:57
*** lpabon has joined #openstack-swift14:57
mahaticacoles: yes, indeed14:57
mahaticacoles: :D enjoy!14:57
*** doxavore has joined #openstack-swift14:59
*** 5EXAAOC18 has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
acolesmahatic: it was all gone :(15:01
mahaticacoles: aw! too bad15:02
acolesmahatic: when you rebase do you use the -i option, cos then you will see exactly what is going to happen15:03
*** vinsh has joined #openstack-swift15:04
mahaticacoles: I do. and I knew this was the chain. But since the others were merged, I didn't think they would be chained like that15:04
acolesyeah it can get confuding15:04
acolesconfusing*15:04
acolesyou'll need to abandon those gerrit reviews you created ^^ for the patches already on feature/crypto15:05
*** Jeffrey4l has quit IRC15:06
acolesand then you have two options:15:06
mahaticyeah, but I'd probably have to wait until patch 261292 goes into feature/crypto as well15:06
patchbotmahatic: https://review.openstack.org/#/c/261292/ - Remove content-type encryption/decryption15:06
mahaticsince that is dependent on 21145115:07
acoles1. wait for 211451 to merge (~1 hour perhaps) when it will be at HEAD of feature/crypto, then we'll rebase 261292 on HEAD and you can rebase your patch on that15:08
mahaticor I'l just wait until 211451 merges15:08
mahaticyup15:08
acolesyeah, that!15:08
mahatic:)15:08
acolesdo you want to hear option 2? cos its going to take me longer to type :)15:08
mahatic:D let me type my option 215:09
*** Jeffrey4l has joined #openstack-swift15:09
acolesoption 1 sounds good...15:09
acoles;)15:09
*** diogogmt has joined #openstack-swift15:10
mahatici can wait until 211451 merges and, take a back of up 26192, create a new branch off feature/crypto. Copy my back up code, commit with same change id15:10
mahaticheh, but that would be more work15:10
acolesmahatic: more work that git can do for you15:11
mahaticacoles: right15:11
mahaticacoles: option 1! :D15:11
mahaticwhat's your option 2? ;) (curious)15:12
*** mragupat has joined #openstack-swift15:12
*** SkyRocknRoll has joined #openstack-swift15:12
*** eranrom has quit IRC15:12
*** eranrom has joined #openstack-swift15:13
acolesmahatic: my option 2 is you take your local checkout of 211451 and rebase it onto feature/crypto (so get it to the same state that zuul will when it merges) then rebase the the other patches onto that. it just allows you to move forwards immediately.15:13
acolesmahatic: but you may end up pushing a new version of 211451 while its in the zuul queue and idk if that will cause it to get dropped from queue15:14
mahaticright!15:14
acolesmahatic: so ... option 1 == easy life15:15
mahaticacoles: I can wait up, gtg anyway15:15
mahaticyup15:15
acolesmahatic: zuul says you have 1hr8m to wait15:16
mahaticacoles: ah, maybe i'll check back after my dinner.15:16
mahaticacoles: thank you!15:17
*** diogogmt has quit IRC15:22
doxavoreis there a threshold that replication times should be kept under? we tweaked the # of replicators and rsync max connections down in order to reduce request latency, which is fairly important to us (not that it's low/fast, but that we don't regularly have timeouts). our replication cycle time seems to be hanging around 12h now.15:22
*** robefran has quit IRC15:24
*** SkyRocknRoll has quit IRC15:29
jrichlimattoliverau: Thanks for the response.  And no worries, I enjoy your sarcasm :-)  I had just logged-off before seeing your message.15:30
*** breitz has quit IRC15:30
*** breitz has joined #openstack-swift15:30
jrichliacoles: sorry you missed your cake :-(  I will bring some sweets to the hackathon to make up for it15:34
janonymous_Haha, cake war :P15:35
*** lcurtis has joined #openstack-swift15:38
openstackgerritPeter Lisák proposed openstack/swift: Change schedule priority of daemon/server in config  https://review.openstack.org/23879915:39
*** garthb has joined #openstack-swift15:40
jrichlijanonymous_: acoles gets cake at work something like everyday (well, not today)!  I am wondering if we will be able to sample this cake when we are there ...15:41
janonymous_cool :)15:42
acolesjrichli: thursday is the official cake day in HPE Cloud. but then there are the unofficial days...15:44
janonymous_you guys are in ibm ryt..15:45
jrichlijanonymous_: i'm at ibm.  acoles at HPE.15:47
janonymous_Ohh i see ,sry didn't knew :)15:47
jrichlino worries!15:48
*** itlinux has joined #openstack-swift15:50
*** tongli has joined #openstack-swift15:51
janonymous_jrichli: is the keymaster work is in progress or done ?15:51
jrichlijanonymous_: keymaster v1 is done (with a caveat).  But if you recall, that is using derived keys from one secret that is stored in a config file.15:53
jrichlijanonymous_: the caveat is that we are currently working off a fixed key due to issues in other functionality.  Once we have COPY as middleware, it will be easy to switch back to multiple keys.15:54
janonymous_jrichli: can i get some links for reference, i was reading about these.15:54
jrichliall I have are etherpads ... but I can get that15:55
janonymous_jrichli: no problem, i would go through that, also i attended the summit sessions, i remember the basic flow though15:56
*** haomaiwang has quit IRC16:01
*** haomaiwa_ has joined #openstack-swift16:01
*** silor has quit IRC16:02
jrichlijanonymous_: there are 3 etherpads, all designed for a slightly different reason16:03
jrichlihttps://etherpad.openstack.org/p/Swift_SmartKeyMaster16:03
jrichlihttps://etherpad.openstack.org/p/swift_production_keymaster_issues16:03
jrichlihttps://etherpad.openstack.org/p/swifjt-keymaster-with-castellan16:03
jrichliand they haven't been updated since the summit, or recently afterwards16:04
*** fthiagogv has joined #openstack-swift16:04
*** fthiagogv has left #openstack-swift16:05
janonymous_Thanks!16:05
*** fthiagogv has joined #openstack-swift16:05
*** itlinux has quit IRC16:05
*** klrmn has joined #openstack-swift16:05
*** itlinux has joined #openstack-swift16:07
portantenotmyname: hello16:09
portantecurious if swift is using oslo logging at all?  I am guessing not16:09
portanteand is there any pressure to move off of using rsyslog16:10
*** eranrom has quit IRC16:11
openstackgerritBill Huber proposed openstack/swift: Re-format the SLO manifest file on new multipart-manifest GET call  https://review.openstack.org/26390216:13
wbhuberdfg: ^^ the patch now includes func tests.  feel free to review at your earliest convenience.16:13
*** diogogmt has joined #openstack-swift16:19
*** diogogmt_ has joined #openstack-swift16:22
*** itlinux has quit IRC16:22
dfgwbhuber: cool thx16:23
*** diogogmt has quit IRC16:24
*** diogogmt_ is now known as diogogmt16:24
*** robefran has joined #openstack-swift16:24
*** itlinux has joined #openstack-swift16:25
*** lpabon has quit IRC16:39
*** blmartin has quit IRC16:39
*** garthb has quit IRC16:39
*** blmartin has joined #openstack-swift16:41
peluseportante: yo!16:42
peluseportante: I know the answer to your first question is no, notmyname will have to answer the one on pressure...16:42
portantepeluse: hi16:42
portantethanks16:43
dfgwbhuber: what dod you mean about the "This also covers the need for a copy mechanism when it does a GET16:43
dfgand a PUT." in the commit message?16:43
dfgwhat did16:43
dfgare you talking about the user sending a GET and a PUT, not using COPY ?16:44
wbhuberdfg: what i meant was that instead of doing put, get and modify the manifest manually before we copy it to another location.  this new format should skip the last two steps (with a copy).16:46
wbhuberdfg: i'll go clarify that up in the commit message. perhaps take that out for clarity.16:46
dfgwbhuber: no i was just checking. its because of the kinda weird COPY and ?multipart-manifest=get doing a COPY of the manifest file. if you do a COPY with ?multipart-manifest=get-raw then it just concatenates the segments like if you sent no query string16:48
dfgwhich is fine i guess16:48
dfgi mean- i can't think of an alternative16:50
*** itlinux has quit IRC16:52
*** gyee has joined #openstack-swift16:55
wbhuberhm..  let me try fiddle with the message a bit.16:55
*** itlinux has joined #openstack-swift16:57
*** dslevin_ has joined #openstack-swift16:59
*** jordanP has quit IRC16:59
*** mragupat has quit IRC17:00
*** mragupat has joined #openstack-swift17:00
*** haomaiwa_ has quit IRC17:01
*** 77CAAHQRX has joined #openstack-swift17:01
*** mragupat has quit IRC17:02
*** mragupat has joined #openstack-swift17:02
*** esker has quit IRC17:05
*** daemontool_ has quit IRC17:06
*** itlinux has quit IRC17:10
*** itlinux has joined #openstack-swift17:11
*** mragupat_ has joined #openstack-swift17:19
*** mragupat has quit IRC17:22
*** garthb has joined #openstack-swift17:24
openstackgerritJonathan Hinson proposed openstack/swift: WIP Conditional GETs Fix  https://review.openstack.org/25760317:33
*** chsc has joined #openstack-swift17:33
notmynamegood morning17:37
notmynameportante: what peluse said. swift doesn't use oslo.logging. there's only occasional mild pressure to use it. but mostly people are fine with "well it would be ok with me if swift were to have configurable logging so I can make it look like oslo.logging fields"17:39
notmynameportante: however, very few, if any, of those conversations are with people who actually use swift. it's mostly from people who are pushing a "you should do what everyone else is doing" idea (as opposed to "it's broken and the new way fixes it")17:41
*** rledisez has quit IRC17:43
*** itlinux has quit IRC17:45
*** itlinux_ has joined #openstack-swift17:45
*** jistr has quit IRC17:45
*** CaioBrentano has quit IRC17:47
*** CaioBrentano has joined #openstack-swift17:47
*** hseipp has joined #openstack-swift17:48
*** hseipp has quit IRC17:48
*** hseipp has joined #openstack-swift17:48
*** cschwede has quit IRC17:50
*** dmorita has joined #openstack-swift17:52
*** yarkot has joined #openstack-swift17:53
*** arnox has quit IRC17:53
*** can8dnSix has joined #openstack-swift17:56
*** can8dnSix has quit IRC17:58
*** 77CAAHQRX has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:01
*** dmorita has quit IRC18:05
*** esker has joined #openstack-swift18:06
*** vinsh has quit IRC18:06
*** itlinux_ has quit IRC18:06
*** vinsh has joined #openstack-swift18:07
*** dmorita has joined #openstack-swift18:08
*** CaioBrentano has quit IRC18:09
openstackgerritTim Burke proposed openstack/python-swiftclient: Prompt for missing password  https://review.openstack.org/18938718:09
*** jordanP has joined #openstack-swift18:10
*** proteusguy_ has quit IRC18:11
*** hseipp has quit IRC18:11
*** tongli_ has joined #openstack-swift18:11
*** esker has quit IRC18:11
*** itlinux has joined #openstack-swift18:12
*** esker has joined #openstack-swift18:13
*** fthiagogv has quit IRC18:14
*** tongli has quit IRC18:14
*** garthb_ has joined #openstack-swift18:14
*** ndk has quit IRC18:14
*** garthb has quit IRC18:15
*** fthiagogv has joined #openstack-swift18:17
*** tsg has joined #openstack-swift18:20
*** proteusguy_ has joined #openstack-swift18:23
*** itlinux has quit IRC18:28
*** esker has quit IRC18:28
*** itlinux has joined #openstack-swift18:30
*** gyee has quit IRC18:31
*** esker has joined #openstack-swift18:33
*** ndk has joined #openstack-swift18:35
*** haomaiwang has quit IRC18:35
*** jsuchome has quit IRC18:38
*** zaitcev has joined #openstack-swift18:40
*** ChanServ sets mode: +v zaitcev18:40
acolesmahatic: patch 211451 hasn't merged yet, assuming it does I can help with rebasing the dependent patches tomorrow if you don't mind waiting for a.m. in my timezone18:40
patchbotacoles: https://review.openstack.org/#/c/211451/ - Modify unit tests to include real crypto18:40
*** acoles is now known as acoles_18:41
*** itlinux has quit IRC18:43
*** tongli has joined #openstack-swift18:51
*** lpabon has joined #openstack-swift18:52
*** tongli has quit IRC18:53
*** tongli_ has quit IRC18:53
*** itlinux has joined #openstack-swift18:54
openstackgerritPaul Dardeau proposed openstack/swift: Remove limit of 64K devices by providing 4 bytes per device id when needed.  https://review.openstack.org/26492218:55
*** jordanP has quit IRC18:55
notmynamepdardeau: cool18:56
openstackgerritPeter Lisák proposed openstack/swift: Change schedule priority of daemon/server in config  https://review.openstack.org/23879918:56
*** haomaiwang has joined #openstack-swift18:56
*** dmorita has quit IRC18:57
*** eranrom has joined #openstack-swift18:58
*** dmorita has joined #openstack-swift18:58
*** dmorita has quit IRC18:58
*** dmorita_ has joined #openstack-swift18:59
*** haomaiwang has quit IRC19:01
pdardeaunotmyname: thx19:02
notmynameI'll take a look a little later. glad to see it up19:02
openstackgerritMerged openstack/swift: Modify unit tests to include real crypto  https://review.openstack.org/21145119:05
*** wmn-tech has joined #openstack-swift19:07
*** esker has quit IRC19:07
*** klamath has joined #openstack-swift19:08
klamathhowdy yall, wondering if swift-drive-audit controls the drive.recon file located in /var/cache/swift or whatever you configured the recon dir to be.19:08
*** dslevin_ has quit IRC19:10
*** esker has joined #openstack-swift19:11
wmn-techHi guys I am running a small cluster with 3 nodes having 4 hdd each. I have uploaded some files to the cluster now I am getting high cpu load on one node which is created by some swift process I can see hard disks working on iotop The problem is I am unable to kill any swift processes How can I kill them19:12
*** itlinux_ has joined #openstack-swift19:13
*** itlinux has quit IRC19:14
*** robefran has quit IRC19:18
*** robefran has joined #openstack-swift19:19
*** petertr7_away is now known as petertr719:20
openstackgerritAlan Erwin proposed openstack/swift: Refactoring the expiring objects feature  https://review.openstack.org/25208519:22
*** rsFF has joined #openstack-swift19:23
*** itlinux has joined #openstack-swift19:25
*** itlinux_ has quit IRC19:28
*** dslevin_ has joined #openstack-swift19:28
*** esker has quit IRC19:28
*** badari_ has joined #openstack-swift19:29
*** Guest38743 has quit IRC19:29
*** klrmn1 has joined #openstack-swift19:30
*** Jeffrey4l has quit IRC19:30
*** garthb__ has joined #openstack-swift19:31
*** yarkot has quit IRC19:31
*** yarkot has joined #openstack-swift19:31
*** tsg_ has joined #openstack-swift19:31
*** redbo_ has joined #openstack-swift19:33
*** Jeffrey4l has joined #openstack-swift19:33
*** wasmum- has joined #openstack-swift19:35
*** powerbsd has joined #openstack-swift19:35
*** itlinux has quit IRC19:35
*** torgomatic_ has joined #openstack-swift19:36
*** stevemar_znc has joined #openstack-swift19:37
*** janonymous_ has quit IRC19:37
*** philipw_ has joined #openstack-swift19:37
*** itlinux has joined #openstack-swift19:38
*** alpha_ori_ has joined #openstack-swift19:38
*** tsg has quit IRC19:38
*** garthb_ has quit IRC19:38
*** klrmn has quit IRC19:38
*** badari has quit IRC19:38
*** albertom has quit IRC19:38
*** briancurtin has quit IRC19:38
*** sileht has quit IRC19:38
*** alpha_ori has quit IRC19:38
*** swifterdarrell has quit IRC19:38
*** redbo has quit IRC19:38
*** torgomatic has quit IRC19:38
*** wasmum has quit IRC19:38
*** philipw has quit IRC19:38
*** stevemar has quit IRC19:38
*** alpha_ori_ is now known as alpha_ori19:38
*** powerbsd is now known as albertom19:38
*** stevemar_znc is now known as stevemar19:40
*** ChubYann has joined #openstack-swift19:40
*** swifterdarrell has joined #openstack-swift19:40
*** ChanServ sets mode: +v swifterdarrell19:40
*** sileht has joined #openstack-swift19:41
*** briancurtin has joined #openstack-swift19:45
*** itlinux has quit IRC19:53
vinshWhere can I read/learn about the "daemonize = on" setting for swift services?19:56
*** esker has joined #openstack-swift19:57
vinshThe source code I guess :)19:57
vinsh"Whether or not to run replication as a daemon"  What are the ups/downs to that?19:57
wmn-techvinsh: Hay dude do you have any proper fine tuning manual for this thing so far I am unable to find a proper explained doc if you can provide some links its very helpful :)20:00
*** esker has quit IRC20:01
*** zhill has joined #openstack-swift20:01
vinshWell..20:02
vinshhttp://docs.openstack.org/developer/swift/deployment_guide.html  ?20:02
*** esker has joined #openstack-swift20:02
*** esker has quit IRC20:03
*** itlinux has joined #openstack-swift20:03
*** esker has joined #openstack-swift20:04
wmn-techvinsh: Using the same :(20:05
vinshwmn-tech: Start reading then :) -> http://www.amazon.com/OpenStack-Swift-Administering-Developing-Storage/dp/149190082220:07
wmn-techvinsh: ahah cool bro we are on same track https://books.google.co.in/books?id=ALHXBAAAQBAJ&pg=PA165&lpg=PA165&dq=openstack+swift+8+core+server&source=bl&ots=74MGu6WUbK&sig=izgxEsr7du3ZNeZ3eEISs04dWvA&hl=en&sa=X&ved=0ahUKEwiOn_6ZuJjKAhVIBo4KHX_KA0QQ6AEITDAI#v=onepage&q=openstack%20swift%208%20core%20server&f=false20:07
*** esker has quit IRC20:08
glangehttps://github.com/openstack/swift/blob/master/swift/common/daemon.py20:08
glange"daemonize = on" seems to make the service run just once20:09
vinshHad that up.. but i'm not getting the "why" for setting it on or off20:09
*** esker has joined #openstack-swift20:09
glangewhich seems to be the opposite of what you would think it would mean20:09
glangeyou could run it via cron if you do the run_once20:09
glangeor you could have it run forever on its own if you don't do the run_once20:10
glangeI think that is the difference20:10
*** minwoob has quit IRC20:10
portantenotmyname: great, that is what I had remembered from before, glad to see no one has bowed to that!20:10
*** haomaiwang has joined #openstack-swift20:10
wmn-techglange: disable_fallocate Can you please tell me the use20:10
vinshI wonder if it would use "interval" to run at the interval with daemonize20:10
ZyricGood Morning20:11
*** esker has quit IRC20:11
*** dhellmann has quit IRC20:11
vinshglange: Seems like on is default for reconstructor (in the config example atleast).20:12
vinshI'll play around with it and see how it behaves.  Thanks :)20:12
*** changbl has quit IRC20:15
*** dmorita_ has quit IRC20:16
*** haomaiwang has quit IRC20:17
*** esker has joined #openstack-swift20:20
*** esker has quit IRC20:21
*** openstackgerrit has quit IRC20:23
*** openstackgerrit has joined #openstack-swift20:25
*** tsg__ has joined #openstack-swift20:35
*** tsg_ has quit IRC20:37
*** itlinux has quit IRC20:42
*** dmorita has joined #openstack-swift20:47
*** petertr7 is now known as petertr7_away20:48
*** esker has joined #openstack-swift20:48
*** petertr7_away is now known as petertr720:51
*** itlinux has joined #openstack-swift20:52
*** dmorita has quit IRC20:53
*** dmorita has joined #openstack-swift20:53
openstackgerritTim Burke proposed openstack/swift: Make write-only container access consistent  https://review.openstack.org/26496120:56
*** esker has quit IRC20:56
*** changbl has joined #openstack-swift21:01
*** petertr7 is now known as petertr7_away21:04
*** petertr7_away is now known as petertr721:05
*** changbl has quit IRC21:06
*** itlinux has quit IRC21:09
*** itlinux has joined #openstack-swift21:10
*** lpabon has quit IRC21:12
*** haomaiwang has joined #openstack-swift21:14
*** trifon has quit IRC21:16
*** haomaiwang has quit IRC21:19
*** trifon has joined #openstack-swift21:29
*** nadeem has joined #openstack-swift21:32
*** blmartin has quit IRC21:32
*** esker has joined #openstack-swift21:36
mattoliverauMorning21:37
*** tsg__ has quit IRC21:39
*** tsg__ has joined #openstack-swift21:40
*** itlinux has quit IRC21:48
*** trifon has quit IRC21:50
*** wasmum- has quit IRC21:50
*** klrmn1 has quit IRC21:50
*** eranrom has quit IRC21:50
*** peluse has quit IRC21:50
*** trifon has joined #openstack-swift21:51
*** wasmum- has joined #openstack-swift21:51
*** klrmn1 has joined #openstack-swift21:51
*** eranrom has joined #openstack-swift21:51
*** peluse has joined #openstack-swift21:51
onovymattoliverau: morning, thanks a lot for you review21:54
*** itlinux has joined #openstack-swift21:57
notmynameacoles_: peluse: torgomatic_: any confirmation on this would be appreciated https://bugs.launchpad.net/swift/+bug/153200822:01
openstackLaunchpad bug 1532008 in OpenStack Object Storage (swift) "EC policy doesn't fallocate objects" [Undecided,New]22:01
notmynameand i don't know what the right math is to find the right on-disk size of an EC fragment given the client object size, the EC algo, and the segment size22:01
*** itlinux has quit IRC22:14
*** robefran has quit IRC22:15
*** haomaiwa_ has joined #openstack-swift22:16
torgomatic_notmyname: I think you just discovered why EC doesn't fallocate :p22:18
notmynameit's possible to do, right?22:18
torgomatic_notmyname: probably? if pyeclib can answer the question "how big is the fragment for a segment of size N", then it's possible22:19
notmynamealso, if we can calculate range offsets, we can find the total length22:20
*** haomaiwa_ has quit IRC22:22
*** tsg_ has joined #openstack-swift22:22
*** petertr7 is now known as petertr7_away22:22
*** tsg__ has quit IRC22:25
*** esker has quit IRC22:27
torgomatic_that's probably true22:28
*** esker has joined #openstack-swift22:28
*** itlinux has joined #openstack-swift22:31
notmynamebut to back up, did I just rediscover something already known? cause it looks like it was supposed to do the right thing, but it's not22:31
notmynameie instead of just not doing it at all22:32
*** blmartin has joined #openstack-swift22:32
*** itlinux has quit IRC22:33
*** itlinux has joined #openstack-swift22:36
*** gyee has joined #openstack-swift22:36
*** esker has quit IRC22:40
*** itlinux has quit IRC22:43
timburkenotmyname: torgomatic_: from get_segment_info, we should get segment_size, last_segment_size, fragment_size, last_fragment_size and num_segments. from there, i think the backend-obj-content-length should be fragment_size * (num_segments - 1) + last_fragment_size, right?22:43
torgomatic_timburke: sounds reasonable22:44
*** chsc has quit IRC22:44
*** zhill has quit IRC22:46
*** zhill has joined #openstack-swift22:49
notmynameI just discovered that there is a swift irc network22:51
notmynamehttp://www.swiftirc.net22:51
*** km_ has joined #openstack-swift22:56
mattoliverauonovy: no worries, I'll keep my eye on it :)22:56
*** bkmz_ has joined #openstack-swift23:03
*** trifon has quit IRC23:06
*** klamath has quit IRC23:06
*** bkmz has quit IRC23:07
*** robefran has joined #openstack-swift23:08
*** zhill has quit IRC23:09
*** mragupat_ has quit IRC23:20
notmynamemattoliverau: redbo_: could you take a look at patch 258704?23:25
patchbotnotmyname: https://review.openstack.org/#/c/258704/ - Fix IPv6 handling in MemcacheConnPool.23:25
mattoliveraunotmyname: I'll do my best to get to it today23:27
notmynamemattoliverau: thanks23:27
*** kei_yama has joined #openstack-swift23:34
*** kei_yama has quit IRC23:36
openstackgerritTim Burke proposed openstack/swift: Autovivify X-Versions-Location container  https://review.openstack.org/26501523:41
*** kei_yama has joined #openstack-swift23:42
claygtimur: re patch 25870423:51
patchbotclayg: https://review.openstack.org/#/c/258704/ - Fix IPv6 handling in MemcacheConnPool.23:51
claygtimur: is the [ip:v6:address] thing like common for configs that use ipv6 addresses - or did you just have to make it up to avoid 1.2.3.4:<port> looking like ipv6 because of the ':' ???23:52
* clayg realizes this might have all very well been in the commit message23:53
clayg"oprtional"23:53
openstackgerritTim Burke proposed openstack/swift: Fix versioned_writes functional test skipping  https://review.openstack.org/26501723:53
claygtimur: oh, i guess there's this -> https://en.wikipedia.org/wiki/IPv6_address#Literal_IPv6_addresses_in_network_resource_identifiers23:55
*** garthb__ has quit IRC23:57
*** garthb__ has joined #openstack-swift23:57

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