Thursday, 2016-06-23

*** tqtran has quit IRC00:03
*** lyrrad has quit IRC00:24
*** Jeffrey4l has joined #openstack-swift00:44
*** fbo has quit IRC00:52
*** mhu has quit IRC00:54
*** siva_krish has quit IRC00:59
*** fbo has joined #openstack-swift01:03
*** Suyash has quit IRC01:05
*** klrmn has quit IRC01:11
*** mhu has joined #openstack-swift01:12
*** dmorita has quit IRC01:12
*** awelleck has joined #openstack-swift01:21
*** StraubTW has joined #openstack-swift01:22
*** StraubTW has quit IRC01:23
*** cdelatte has quit IRC01:38
*** Suyash has joined #openstack-swift01:45
*** siva_krish has joined #openstack-swift01:53
*** siva_krish has quit IRC01:59
*** tqtran has joined #openstack-swift02:01
*** zul has quit IRC02:03
*** zul has joined #openstack-swift02:04
*** tqtran has quit IRC02:05
*** klrmn has joined #openstack-swift02:14
*** awelleck has quit IRC02:21
*** zul has quit IRC02:23
*** dmorita has joined #openstack-swift02:24
*** greghaynes has quit IRC02:27
*** dmorita has quit IRC02:28
*** _JZ_ has quit IRC02:37
*** greghaynes has joined #openstack-swift02:39
*** awelleck has joined #openstack-swift02:51
*** awelleck has quit IRC02:51
*** stevemar has joined #openstack-swift03:36
*** links has joined #openstack-swift03:51
*** SkyRocknRoll has joined #openstack-swift03:52
*** ppai has joined #openstack-swift03:57
*** psachin has joined #openstack-swift04:38
*** klrmn1 has joined #openstack-swift04:42
*** klrmn has quit IRC04:43
openstackgerritPete Zaitcev proposed openstack/swift: Patch through the error from NewReplicator  https://review.openstack.org/33310704:44
*** Suyash has quit IRC04:49
openstackgerritPete Zaitcev proposed openstack/swift: Add a global fix for anything that involves GetHashPrefixAndSuffix  https://review.openstack.org/33310804:51
*** zaitcev has quit IRC05:21
*** ChubYann has quit IRC05:26
*** dmorita has joined #openstack-swift05:27
*** dmorita has quit IRC05:32
*** tqtran has joined #openstack-swift06:02
*** tqtran has quit IRC06:06
*** rcernin has joined #openstack-swift06:15
*** jmccarthy has quit IRC06:42
*** jmccarthy has joined #openstack-swift06:44
*** jamielennox is now known as jamielennox|away06:48
*** oshritf has joined #openstack-swift06:54
*** rcernin has quit IRC07:02
*** tesseract- has joined #openstack-swift07:13
*** tesseract- has quit IRC07:14
*** tesseract- has joined #openstack-swift07:14
*** rcernin has joined #openstack-swift07:17
*** furlongm_ has joined #openstack-swift07:22
*** furlongm has quit IRC07:22
*** rledisez has joined #openstack-swift07:25
*** furlongm has joined #openstack-swift07:26
*** furlongm_ has quit IRC07:27
*** hseipp has joined #openstack-swift07:33
*** furlongm has quit IRC07:35
*** furlongm has joined #openstack-swift07:35
*** SkyRocknRoll_ has joined #openstack-swift07:37
*** SkyRocknRoll_ has quit IRC07:38
*** oshritf has quit IRC07:39
*** furlongm has quit IRC07:42
*** geaaru has joined #openstack-swift07:49
*** klrmn1 has quit IRC07:57
*** baojg has joined #openstack-swift08:05
*** geaaru has quit IRC08:16
*** mvk_ has quit IRC08:21
*** geaaru has joined #openstack-swift08:28
*** hosanai has joined #openstack-swift08:30
*** ChanServ sets mode: +v hosanai08:30
*** daemontool has joined #openstack-swift08:31
*** Jeffrey4l has quit IRC08:47
*** rcernin has quit IRC08:50
*** Jeffrey4l has joined #openstack-swift09:00
*** rcernin has joined #openstack-swift09:02
*** ouchkernel has quit IRC09:03
*** tqtran has joined #openstack-swift09:03
*** ouchkernel has joined #openstack-swift09:07
*** tqtran has quit IRC09:08
*** dmk0202 has joined #openstack-swift09:09
*** mvk_ has joined #openstack-swift09:11
*** silor has joined #openstack-swift09:11
*** silor1 has joined #openstack-swift09:16
*** silor has quit IRC09:18
*** silor1 is now known as silor09:18
*** zul has joined #openstack-swift09:23
*** mvk_ has quit IRC09:24
*** baojg has quit IRC09:26
*** Jeffrey4l has quit IRC09:28
*** dmorita has joined #openstack-swift09:28
*** dmorita has quit IRC09:33
*** kei_yama has quit IRC09:38
*** cbartz has joined #openstack-swift09:38
*** acoles_ is now known as acoles09:41
*** Jeffrey4l has joined #openstack-swift09:42
*** mvk_ has joined #openstack-swift09:43
*** jamielennox|away is now known as jamielennox09:43
*** pcaruana has joined #openstack-swift09:51
*** daemontool has quit IRC10:00
*** foexle has joined #openstack-swift10:01
*** zul has quit IRC10:23
*** dmk0202 has quit IRC10:29
*** zul has joined #openstack-swift10:35
*** zul has quit IRC10:38
*** zul has joined #openstack-swift10:52
*** jistr is now known as jistr|mtg10:56
*** zul has quit IRC11:16
*** zul has joined #openstack-swift11:17
*** ekarlso has quit IRC11:26
openstackgerritoshritf proposed openstack/swift: Add thread level concurrency to container sync  https://review.openstack.org/22533811:26
*** daemontool has joined #openstack-swift11:28
*** dmk0202 has joined #openstack-swift11:33
openstackgerritoshritf proposed openstack/swift: Add process level concurrency to container sync  https://review.openstack.org/33298511:50
*** ekarlso has joined #openstack-swift11:51
*** daemontool_ has joined #openstack-swift11:54
*** daemontool has quit IRC11:55
openstackgerritVictor Stinner proposed openstack/swift: Python 3: Fix basestring, long and StringIO  https://review.openstack.org/33329712:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: dict.iteritems() and dict.itervalues()  https://review.openstack.org/33329812:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: fix urllib import  https://review.openstack.org/33329912:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: fix usage of reload()  https://review.openstack.org/33330012:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: fix ConfigParser and httplib imports  https://review.openstack.org/33330112:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: Fix usage of dict methods  https://review.openstack.org/33330212:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: fix dict.values()[0]  https://review.openstack.org/33330312:02
*** dmorita has joined #openstack-swift12:09
*** dmorita has quit IRC12:14
*** manous has joined #openstack-swift12:35
*** SkyRocknRoll has quit IRC12:36
*** ametts has joined #openstack-swift12:43
*** tongli has joined #openstack-swift12:48
*** McMurlock1 has joined #openstack-swift12:49
*** janonymous has quit IRC12:51
openstackgerritChristopher Bartz proposed openstack/swift: Preserve query params in tempurl  https://review.openstack.org/33333112:57
*** hosanai has quit IRC12:57
*** pauloewerton has joined #openstack-swift12:58
*** manous_ has joined #openstack-swift13:09
*** manous has quit IRC13:11
*** StraubTW has joined #openstack-swift13:14
tdasilvagood morning13:23
*** jistr|mtg is now known as jistr13:31
*** catintheroof has joined #openstack-swift13:32
ntatagood morning13:35
*** foexle has quit IRC13:46
*** zul_ has joined #openstack-swift13:59
*** zul has quit IRC14:00
*** mwheckmann has joined #openstack-swift14:00
*** ppai has quit IRC14:00
*** zul_ has quit IRC14:01
*** zul has joined #openstack-swift14:02
*** manous_ has quit IRC14:04
*** manous_ has joined #openstack-swift14:18
onovyhi, https://review.openstack.org/#/c/323874/ and https://review.openstack.org/#/c/323877/ anyone? ;)14:22
patchbotonovy: patch 323874 - pyeclib - Change liberasure URL to new one14:22
patchbotonovy: patch 323877 - pyeclib - Bump liberasurecode dependency to 1.2.0 version14:22
onovyand https://review.openstack.org/#/c/323819/ :)14:22
patchbotonovy: patch 323819 - liberasurecode - Changed homepage to new one14:22
*** rfeusi has joined #openstack-swift14:24
*** foexle has joined #openstack-swift14:26
rfeusiI need help for a minimal openstack swift architecture. I have two datacenters next to each others (only a steet is between them, so latency is very small).14:27
*** jistr is now known as jistr|mtg14:38
*** links has quit IRC14:41
*** pcaruana has quit IRC14:41
onovyrfeusi: hi, we are using geocluster for this, so two regions and two replicas each14:48
*** foexle has quit IRC14:49
onovybut if latency is really small, and throughtput betwean them is not issue, you can make it as one region too14:49
*** manous_ has quit IRC14:56
*** siva_krish has joined #openstack-swift14:57
*** mvk_ has quit IRC15:02
*** amit213 has quit IRC15:04
*** tqtran has joined #openstack-swift15:06
*** tqtran has quit IRC15:10
notmynamegood morning15:14
*** sheel has quit IRC15:15
*** siva_krish has left #openstack-swift15:17
*** dmorita has joined #openstack-swift15:19
*** haypo has joined #openstack-swift15:33
*** Suyash has joined #openstack-swift15:33
*** dmk0202 has quit IRC15:46
*** psachin has quit IRC15:47
*** lyrrad has joined #openstack-swift15:50
*** arch-nemesis has joined #openstack-swift15:52
timburkegood morning15:52
*** diogogmt has joined #openstack-swift16:03
*** chsc has joined #openstack-swift16:09
*** rledisez has quit IRC16:17
*** tesseract- has quit IRC16:17
*** baojg has joined #openstack-swift16:18
*** dosaboy has quit IRC16:18
*** Suyash has quit IRC16:18
*** sheel has joined #openstack-swift16:22
notmynamejrichli: in keymaster.py, we're using sha256 for the hmac. what would you think about changing that to sha384?16:32
notmynameI just made the change locally, and I'm about to run tests against it16:33
*** Suyash has joined #openstack-swift16:36
*** SkyRocknRoll has joined #openstack-swift16:36
*** dosaboy has joined #openstack-swift16:39
*** jistr|mtg is now known as jistr16:42
notmynamewell that didn't work16:42
jrichlinotmyname: sounds good.  just wondering if there was a particular compliance issue that influenced that change?16:42
jrichlioh :-/16:42
notmynameand neither did the second thign16:42
*** SkyRocknRoll has quit IRC16:42
notmynamejrichli: I tried https://gist.github.com/notmyname/6b29fb06a7d32c9ee5911896265ece8b and I get a client disconnect (499) from the object servers16:43
notmynamethe reason I'm curious is for "checkbox compliance"16:43
notmynamebasically, when looking at some US government standards, AES256 is good for up to TOP SECRET, but SHA256 is only good to SECRET. SHA384 is also ok for TOP SECRET16:44
*** silor has quit IRC16:44
jrichlibut is that for encryption, or key derivation?16:44
jrichlithe use case matters16:45
notmynamecheckbox compliance ;-)16:45
jrichliid have to see the description of the checkbox item16:45
notmynamefrom that thing I linked yesterday...looking for the link again16:45
jrichlii have that link.16:45
jrichliill take a look16:45
jrichlibtw - we are needing a 256 bit key because of our encryption16:46
notmynameyeah, the suite B list on https://www.cnss.gov/CNSS/openDoc.cfm?lZsorLEWqomRp4GEC0ztzA==16:46
notmynamebut seriously. that's my whole thinking. someone asked if the algorithms used in swift are on the suite B list, and that's it16:47
notmynameso I thought it might be a relatively simple change. turns out it's probably not :-)16:48
jrichli"the algorithms used" usually means for the encyrption part16:48
notmynameyeah, but sha isn't an encryption algorithm16:48
notmynameand it's on the list16:48
jrichlibut deriving ivs or keys is a whole different use case.  the checkbox would be specific if it is addressing key derivation16:48
jrichli256-bit keys is what we decided on16:48
jrichliif you try to run with a longer key, crypto will complain16:49
notmynameyes I know (now) ;-)16:49
notmynamebut yeah, I see what you mean now16:50
notmynameand I because of what you said, I understand the question better. thanks16:50
jrichliso if AES with 256 bit keys is on the list (and i thought it was) than we dont need longer keys16:50
jrichliok, cool16:50
*** cbartz has left #openstack-swift16:55
*** klrmn has joined #openstack-swift17:03
*** baojg has quit IRC17:05
*** daemontool_ has quit IRC17:06
timburkenotmyname: do you have a title for that document? every time i try to follow your link, i get "We're sorry, but we're having trouble opening this document because we did not recognize your session variable." blah blah "Not all pages in this site can be bookmarked."17:07
notmynametimburke: it's the CNSSP 15 on https://www.cnss.gov/CNSS/issuances/Policies.cfm17:07
timburkethanks17:08
jrichliFWIW: this is what cca has said about our key derivation security: "Using HMAC for key derivation is sound and fits. The HKDF function serves a different scenario, more appropriate for a protocol context. Here we are in the scenario of NIST SP 800-108, and its KDF in counter mode with HMAC (sec. 5.1) is equivalent in security to what we use here. It is of critical importance that 'encryption_root_secret' has enough entropy (256 bits o17:09
jrichlir more)."17:09
*** McMurlock1 has quit IRC17:09
jrichliof course, this doesn't mention the hashing alg used within the HMAC call, but he knows we are using 256 bit keys.17:11
*** Jeffrey4l has quit IRC17:11
notmynameok17:11
notmynameI just learned about https://blake2.net. It looks really interesting as an alternative to where md5 is used in swift today (yes, I realize that would be a HUGE change)17:12
notmynamejust as fast or faster than md5, and it has some interesting options to have variable digest sizes depending on the use case17:12
notmynameand the FAQ even mentions that it's good for stuff like OpenStack Swift!17:13
*** tqtran has joined #openstack-swift17:13
jrichliinteresting17:14
timburkei wonder if the cryptography package would support 3AES with a 512 bit key (say, coming out of an HMAC-SHA512), similar to 3DES...not that i think we necessarily need or want to. just idle curiosity17:15
*** ChubYann has joined #openstack-swift17:17
timburkeoh hey, the FAQ even mentions Swift by name!17:18
notmynametimburke: yeah. cool, huh?17:18
jrichlinotmyname: the problem about researching the 'goodness' of our use of sha256 here is that typically HMAC is used for message authentication.  But we are not using it for that in this case.17:20
jrichlibut the issue is collisions - and yes, we want to not repeat keys if we can help it17:20
jrichliits a lot simpler if you can just say you generate random keys :-)17:21
*** raildo is now known as raildo-afk17:22
jrichlisimilar issue with discussions of md5 use in swift.  we dont use it as an HMAC.  so what everybody talks about doesnt apply17:22
notmynameright :-)17:22
timburkespeaking of random keys... do we have any data regarding the point at which having sufficient entropy becomes a bottleneck?17:24
jrichlia bottleneck to what exactly?17:25
*** hseipp has quit IRC17:26
timburkeif i PUT a whole bunch of tiny (<32 bytes, say) objects, the proxies will be getting 32 bytes worth of random key material for each. under enough load, i could see the proxy needing to either wait for more random data to be generated or accept lower-quality data17:34
*** rcernin has quit IRC17:38
timburkerandom experimenting would seem to indicate this is unlikely to be a problem. i think the standard handling-a-PUT overhead will far outweigh waiting on 32 bytes of entropy17:44
notmynametimburke: that's when you fork over $15 and plug one of these into the server http://altusmetrum.org/ChaosKey/17:46
timburkenotmyname: knowing when you need one is good, though17:48
notmynamesure. I guess "when /dev/urandom is slow" probably isn't a good metric ;0(17:49
notmynameor whatever that smiley thing is supposed to be17:49
*** mwheckmann has quit IRC17:51
timburkenotmyname: looks like v0.4 has a red LED! that's when you *know* you've made it http://git.gag.com/?p=hw/usbtrng17:53
notmynamewhoa!17:53
notmynametimburke: I'm sure v0.5 will have a blue LED17:54
timburkenotmyname: too late! maybe v0.6 http://git.gag.com/?p=hw/usbtrng;a=commit;h=531f5ef17:57
notmynameI remember once upon a time when redbo got fed up with how long the proxy server code was and refactored it into all the different proxy controllers. and now I'm scrolling through 2300+ lines of just the proxy object controller thinking it should be split up17:59
notmynamewhat with all the different putters and mimecontrollers18:00
*** McMurlock1 has joined #openstack-swift18:05
*** pauloewerton has quit IRC18:11
*** geaaru has quit IRC18:14
* jrichli is back from lunch. reading now18:14
jrichlitimburke: so you are talking about a scenario where somebody were to use random keys in swift?  Or are you talking about the possible strain of the random iv generation for our current scheme?18:20
*** zul has quit IRC18:20
timburkejrichli: current scheme. but like i said, it doesn't seem to add much overhead; i'm not worried18:21
jrichlitimburke: i am probably missing something.  we dont use random for anything except the ivs.  the item of sufficient entropy that christian was referring to was the root key that is fixed and supplied in config.18:22
timburkeyes, and that seems fine. i like our requirements on the root key18:24
timburkei'm thinking of the random ivs and body keys that are generated per PUT18:24
*** zul has joined #openstack-swift18:24
jrichlitimburke: oh, right.  we switched to random key for body sorta late in the game (when wrapping was introduced).  i had it my mind we were still using the derived key.18:27
timburkewith max meta around 90, we're talking about only <1.5k worth of random data per request18:28
tdasilvanotmyname: will the crypto work be merged to master as one single commit or multiple commits?18:29
timburketdasilva: the plan is to have multiple commits on the crypto-review branch which all come into master as a single merge commit18:29
notmynametdasilva: when we all like the crypto-review chain, we'll propose one merge commit to land on master18:29
*** siva_krish has joined #openstack-swift18:30
tdasilvanotmyname, timburke: ok, was just thinking earlier today if it would make sense to start merging separate patches as we are "done" with it...the first patch already has 3 +2s. I was wondering if that would make things easier in terms of maintaining the chain18:31
notmynameyeah, perhaps. actually, I want to leave that up to acoles and whatever local tools he has to manage it. but yeah, I'd be fine with landing the first one on the crypto-review branch now. I'd also be ok with leaving it as-is18:32
timburkeleaving it as-is has the benefit of letting us go back and change it if we somehow realized while looking at patch 5 (say) that something else should have been done in patch 1. at the same time, maybe the fact that we didn't realize it until patch 5 demonstrates that the change logically belongs in patch 5 anyway...18:34
patchbottimburke: https://review.openstack.org/#/c/5/ - openstack-infra/system-config - Fix problem with jenkins known_hosts url. (MERGED)18:34
patchbottimburke: https://review.openstack.org/#/c/1/ - openstack-infra/system-config - Add puppet module for ssh that installs an sshd_co... (MERGED)18:34
patchbottimburke: https://review.openstack.org/#/c/5/ - openstack-infra/system-config - Fix problem with jenkins known_hosts url. (MERGED)18:34
patchbottimburke: https://review.openstack.org/#/c/5/ - openstack-infra/system-config - Fix problem with jenkins known_hosts url. (MERGED)18:34
timburke:-(18:35
notmynametdasilva: don't poke happy fun patchbot18:35
notmynametimburke: ^18:35
tdasilvalol18:36
*** mlanner has quit IRC18:37
*** McMurlock1 has quit IRC18:37
jrichliwow.  threre really patch numbers that low18:37
acolesI can't resist.... patch 018:38
patchbotacoles: https://review.openstack.org/#/c/0/18:38
tdasilvatimburke: yeah, I thought of that too, but I think that could also be easily fixed. I guess I was striving for a couple of things. First really just perception. If we get to next Friday and there's only two or three patches in the chain to merge, I'd feel better. Also, it's really the last few patches that have the crypto work. Merging earlier patches as they are "done" might allow for a "softer soft freeze" on master18:39
tdasilva and we don't have to worry so much about conflicts18:39
*** mlanner has joined #openstack-swift18:40
*** tongli has quit IRC18:40
acolestdasilva: are you suggesting merging the earlier patches to master? otherwise I think it makes no difference wrt conflicts if they are merged on crypto-review or not18:41
acolesbut I will consider whether it could make life easier for me or reviewers in any other way18:42
tdasilvaacoles: yes, merge to master18:43
tdasilvaacoles: what got me thinking about this was the convo yesterday about the documentation and the sync work that is being held up18:43
acolesoic.18:43
jrichliI think tdasilva has a good idea.  I think at the rate we are going, one more week isn't going to be enough (I hate to say)18:43
timburkeas i recall, notmyname seemed opposed to it, but his opinion may have changed18:44
timburkeoh yeah, i meant to mention this in the meeting: i've been using a dash like https://goo.gl/f9gMj4 - other reviewers may find it useful. puts patches where you have a draft at the top, and categorizes all of them based on whether you left a positive or negative (or no) score18:44
notmynameno, I don't want to merge to master18:45
acolesthe sync work shouldn't conflict, I wonder if actually it was in conflict with master and hence crypto-review18:45
notmynamebut landing on crypto-review is ok18:45
acolesthe one advantage of landing on crypto-review is that if we want to go back and change stuff that landed we *may* be able to do it with a fresh patch at the top of the chain, and that avoids lots of rebase noise for the other patches. the disadvantage is that it opens the flood gates for adding patches to the top of the chain ;)18:47
notmynameI'd be fine with landing on crypto-review, but I'd have the same concern as timburke mentioned18:48
notmynameand I don't think the docs works should likely be held up for much longer. I do think we have a pretty good shot at landing this in the next 7 days18:49
jrichliyes, i see that point too.18:49
acolesas far as my process is concerned, I don't yet have a problem with managing an un-merged chain18:49
acolesnotmyname: +1 - done in 7 days or I -2 all the patches and ragequit ;)18:50
notmyname:-)18:51
jrichliacoles: dont even joke about that!18:51
notmynamewe'll have the alexit18:51
acolesoh, you just reminded me I need to vote!18:52
notmynamedo you have to go to a polling station, or can you do it online?18:53
notmynameahale and joeljwright need to go vote too :-)18:53
acolesonline ? (!*"$^  that'll be the day! believe it or not we use paper and pencil and there is no id check, you just state your name/address and get to vote.18:54
notmynamesame here (when it's not the closed-source electronic machines)18:55
clarkboregon and washington's mail in voting system is really nice18:57
*** amit213 has joined #openstack-swift19:00
redboIn texas, you have to show your gun to vote.19:00
*** sheel has quit IRC19:05
notmynamejrichli: on patch 328205 do you think we'll drop the x-backend-container-update-override-* at some point later?19:11
patchbotnotmyname: https://review.openstack.org/#/c/328205/ - swift (feature/crypto-review) - Make container update override headers persistent19:11
notmynameyou know, as much as we drop anything in swift19:11
notmynamejrichli: are you working with thai tran?19:14
jrichlinotmyname: to some extent yes, I with thai.  as for backend, i will have to look at some notes i had.  in a call now : will get back to you19:17
timburkenotmyname: the ones sent for EC support? i don't think so. the object server needs to account for it regardless, due to our upgrade-storage-nodes-then-upgrade-proxy-nodes recommendation. and since the object server needs to handle it anyway, we may as well keep sending it; then even if a proxy server upgrades before an object server, this particular thing will still work19:19
notmyname /lunch19:22
*** htruta is now known as henrique19:22
*** henrique is now known as Guest7841919:23
*** Guest78419 is now known as htruta19:23
*** siva_krish has quit IRC19:25
*** welldannit has joined #openstack-swift19:26
*** chsc has quit IRC19:35
*** haypo has left #openstack-swift19:36
acolesnotmyname: +1 what timburke said, don't see us dropping the old-style overrides for EC19:46
*** acoles is now known as acoles_19:47
*** zaitcev has joined #openstack-swift19:50
*** ChanServ sets mode: +v zaitcev19:50
openstackgerritTim Burke proposed openstack/swift: MockMemcached cleanup  https://review.openstack.org/33355419:56
openstackgerritTim Burke proposed openstack/swift: Tighten memcached tests  https://review.openstack.org/33355519:56
ahalehehe , do you have to shoot the polling card too redbo ?20:00
redboYeah, at 20 yards20:00
openstackgerritVictor Stinner proposed openstack/swift: Python 3: Fix usage of dict methods  https://review.openstack.org/33330220:02
openstackgerritVictor Stinner proposed openstack/swift: Python 3: fix dict.values()[0]  https://review.openstack.org/33330320:02
*** siva_krish has joined #openstack-swift20:06
*** chsc has joined #openstack-swift20:11
*** gyee has joined #openstack-swift20:16
zaitcevMy wife has a Walther Q5 that can easily do that.20:16
jrichlinotmyname: btw, thai tran is tqtran20:24
*** zul has quit IRC20:27
*** fbo has quit IRC20:27
*** hugokuo has quit IRC20:27
*** rsFF- has quit IRC20:27
*** remix_tj has quit IRC20:27
*** Anticimex has quit IRC20:27
*** MooingLemur has quit IRC20:27
*** peterlisak has quit IRC20:27
*** zigo has quit IRC20:27
*** ntata has quit IRC20:27
*** onovy has quit IRC20:27
*** _fortis has quit IRC20:27
*** CrackerJ- has quit IRC20:27
*** zacksh_ has quit IRC20:27
*** mmotiani has quit IRC20:27
*** j_king has quit IRC20:27
*** jamielennox has quit IRC20:27
*** mattoliverau has quit IRC20:27
*** mmotiani_ is now known as mmotiani20:27
*** j_king has joined #openstack-swift20:27
*** matt6434 has joined #openstack-swift20:27
*** rsFF has joined #openstack-swift20:27
*** onovy has joined #openstack-swift20:27
*** CrackerJackMack has joined #openstack-swift20:27
*** Anticimex has joined #openstack-swift20:27
*** hugokuo has joined #openstack-swift20:27
*** peterlisak has joined #openstack-swift20:27
*** MooingLemur has joined #openstack-swift20:27
*** remix_tj has joined #openstack-swift20:27
*** mmotiani_ has joined #openstack-swift20:28
*** zul has joined #openstack-swift20:28
*** zacksh has joined #openstack-swift20:28
*** zigo has joined #openstack-swift20:29
*** ouchkernel has quit IRC20:29
*** fbo has joined #openstack-swift20:30
*** McMurlock1 has joined #openstack-swift20:36
*** ouchkernel has joined #openstack-swift20:36
*** cebreidian has joined #openstack-swift20:36
*** ntata has joined #openstack-swift20:37
*** jamielennox has joined #openstack-swift20:38
*** dmorita has quit IRC20:43
*** dmorita has joined #openstack-swift20:44
*** adu has joined #openstack-swift20:50
*** mmcardle has quit IRC20:50
*** mvk_ has joined #openstack-swift21:02
*** nadeem has joined #openstack-swift21:07
*** foexle has joined #openstack-swift21:07
*** ozialien10 has quit IRC21:08
*** McMurlock1 has quit IRC21:17
timburkezaitcev: you may also like patch 33355421:19
patchbottimburke: https://review.openstack.org/#/c/333554/ - swift - MockMemcached cleanup21:19
*** catintheroof has quit IRC21:21
*** chsc has quit IRC21:23
*** adu has quit IRC21:26
zaitcevif new_val[0] == '-':  # ie, val is negative21:28
timburkeit felt less stupid than eval'ing str(int(current) + int(value)) twice. not by much, i'll admit...21:30
timburkeer, minus, not plus. you know what i mean21:31
zaitcevIt just seemed to me much too obvious.21:32
timburkei'm always happy to remove comments :-)21:32
zaitcevI'll check if  list+list still works in py3 after tea21:33
zaitcevactually looks like tuple+tuple here self.cache[key][:2] + (new_val, )21:33
zaitcevelse it's .append() or something, I dunn21:34
notmynamegoogle has a nice little readout https://www.google.com/#q=brexit+results21:42
timburkezaitcev: should be fine. py3 won't join two views (like from dict.keys() or dict.values()), but lists and tuples still work21:47
zaitcevnotmyname: You can tell it's going to be 51/49 for Remain without any Google. YOUGOV said so, it is so.21:55
*** chsc has joined #openstack-swift21:56
*** chsc has joined #openstack-swift21:56
*** rfeusi has quit IRC22:01
*** rfeusi has joined #openstack-swift22:02
*** ametts has quit IRC22:02
*** nadeem has quit IRC22:17
*** matt6434 is now known as mattoliverau22:18
*** ChanServ sets mode: +v mattoliverau22:18
mattoliveraumorning22:18
*** ouchkernel has quit IRC22:19
*** acoles_ is now known as acoles22:24
*** McMurlock1 has joined #openstack-swift22:27
acolesnotmyname: this is the best brexit indicator http://www.xe.com/currencycharts/?from=GBP&to=USD&view=12h22:27
notmyname:-)22:28
*** StraubTW has quit IRC22:30
*** diogogmt has quit IRC22:33
*** chsc has quit IRC22:36
*** chsc has joined #openstack-swift22:41
*** chsc has joined #openstack-swift22:41
*** natarej has quit IRC22:43
*** diogogmt has joined #openstack-swift22:44
*** natarej has joined #openstack-swift22:44
openstackgerritMerged openstack/swift: Patch through the error from NewReplicator  https://review.openstack.org/33310722:49
claygnotmyname: ok, how do you crypto?22:50
timburkeyay!22:51
notmynameclayg: the patches are organized really well. I started with the whole-view (ie start at the end) to understand the pieces, and now I'm going through from patch 0 to 622:51
notmynamethe commit messages are really good at explaining the need and what's being done. starts with a lot of refactoring, then adds the new functionality, then docs22:52
acolesoh no22:52
timburkehaha22:52
* acoles runs for cover22:52
claygtimburke: how did patch 333554 happen?  did you see something blow up?22:53
patchbotclayg: https://review.openstack.org/#/c/333554/ - swift - MockMemcached cleanup22:53
timburkeclayg: i saw patch 333303 and decided it didn't do enough to improve the situation22:53
patchbottimburke: https://review.openstack.org/#/c/333303/ - swift - Python 3: fix dict.values()[0]22:53
acolesclayg: patch 328209 might be a good place to start, before diving into the crypto code in patch 328208. 328203 - 328207 are supporting changes.22:55
patchbotacoles: https://review.openstack.org/#/c/328209/ - swift (feature/crypto-review) - Add encryption overview doc22:55
patchbotacoles: https://review.openstack.org/#/c/328208/ - swift (feature/crypto-review) - Enable object body and metadata encryption22:55
claygoh yay!  py3 patches are back!  yay!22:55
timburkeclayg: a relevant thread for that starts at http://lists.openstack.org/pipermail/openstack-dev/2016-June/097930.html - though i'm not sure how much you'd care to read it22:56
claygacoles: nice work on the rebase - chain looks solid22:59
timburkeacoles: good point on the derived iv! so if we use the object key for object-server etags...could we get away with using the same iv for all objects? hmm...23:01
acolestimburke: hmmm...now there's a thought23:03
acolesclayg: just about to push a new set of patches btw23:04
claygacoles: very good - please do23:04
*** siva_krish has quit IRC23:04
timburkeacoles: i'd be nervous about having it be a constant across *all* swift deployments...but across a *single* one, maybe...23:05
claygpatch 328207 looks right - no votes yet?23:05
patchbotclayg: https://review.openstack.org/#/c/328207/ - swift (feature/crypto-review) - Allow middleware to override metadata header checking23:05
notmynametimburke: did I miss something acoles said about the iv?23:05
notmynameacoles: after you push these, you're out until monday, right?23:05
acolesnotmyname: I just published some comments on patch 32820823:06
patchbotacoles: https://review.openstack.org/#/c/328208/ - swift (feature/crypto-review) - Enable object body and metadata encryption23:06
acolesclayg: yeah we have a review activity dip in the middle of the chain23:06
timburkenotmyname: in his most-recent comments on...yeah, that one. "If we switch back to using object key whenever we use a derived key then I think there is no longer a requirement for IV's to be distinct w.r.t. other object paths"23:06
acolessome start at the top, some start at the bottom, only the dedicated make it to the middle and beyond ;)23:07
notmynameI'm in the middle now. not sure if I'll make it out alive23:07
acolestimburke: notmyname ... but I think they will be anyway by virtue of the padding23:08
timburkealso, patch 328208 is just *big*. i keep coming back to it, biting off chunks, chewing on them a while...23:08
patchbottimburke: https://review.openstack.org/#/c/328208/ - swift (feature/crypto-review) - Enable object body and metadata encryption23:08
timburkei'm somewhere around the middle now23:08
acoleshmmm, except if path length is exactly 1623:08
timburkeacoles: but as you said, if we're using different keys, it shouldn't matter23:09
acolesteah23:09
acolesyeah23:09
openstackgerritAlistair Coles proposed openstack/swift: Support for http footers - Replication and EC  https://review.openstack.org/32820423:11
openstackgerritAlistair Coles proposed openstack/swift: Make container update override headers persistent  https://review.openstack.org/32820523:11
openstackgerritAlistair Coles proposed openstack/swift: Enable middleware to set metadata on object POST  https://review.openstack.org/32820623:11
openstackgerritAlistair Coles proposed openstack/swift: Allow middleware to override metadata header checking  https://review.openstack.org/32820723:11
openstackgerritAlistair Coles proposed openstack/swift: Enable object body and metadata encryption  https://review.openstack.org/32820823:11
timburkepatches galore!23:12
openstackgerritAlistair Coles proposed openstack/swift: Add encryption overview doc  https://review.openstack.org/32820923:12
acolestimburke: but are they the right ones? makes me so nervous doing this23:12
acolesok, known tasks still outstanding - rework the iv offset calculation ( jrichli is working on that ), torgomatic's unified Putter patch (I'm pinning its fate to the outcome of the uk referendum - to unify or not ;)23:14
acolesnotmyname: timburke tdasilva kota_ jrichli ^^23:14
notmynamethanks!23:15
acolesremind me of any other tasks23:15
*** kei_yama has joined #openstack-swift23:15
*** rcernin has joined #openstack-swift23:16
notmynameI don't know of any. and I think torgomatic's unified Putters is nice, but perhaps not a blocker23:16
notmynameacoles: you're offline until monday now, right?23:18
torgomaticyeah, if that had to wait until after the merge, that'd probably be okay23:18
acolestorgomatic: did you spot anything broken when you wrote that patch?23:23
torgomaticacoles: nothing broken, no23:23
acolesnotmyname: I am around tomorrow but have an early finish (taking son to visit possible future university over weekend). Then back on Monday.23:23
acolesnotmyname: that is, unless we brexit in which case the internet may be severed at the coast23:24
notmynameheh23:24
acolesnotmyname: I'll be on the phone conf tomorrow23:25
notmynameok23:25
notmynameright. I need to make sure my alarm is set23:25
*** arch-nemesis has quit IRC23:26
*** foexle has quit IRC23:26
acolestorgomatic: I did see some potential benefits in a single class while I was ironing out the conn resp references. Tactically it might save a load or rebase noise up the chain if we kept it for follow up.23:27
acoless/or/of/23:27
acolesgood night23:29
*** sheel has joined #openstack-swift23:29
*** acoles is now known as acoles_23:30
*** McMurlock1 has quit IRC23:33
clayglol @ a number of .data files thinking they're something -> /srv/node4/sdb4/objects/890/fe9/dea1f52fbcc16540744db6850e4b8fe9/1466724125.69735.data: Sendmail frozen configuration  - version m"\343\233q5\276C$\007\266\347:\341\015uFB\240\373\323\227D\273y\233T\316\341J\367A\262\033H\356\201\264\212\323I\354\331\3228\207\321fO/c\210U\006?Pg1,ml\201S23:36
clayg^ from `file /srv/node4/sdb4/objects/890/fe9/dea1f52fbcc16540744db6850e4b8fe9/1466724125.69735.data`23:36
*** ouchkernel has joined #openstack-swift23:38
*** adu has joined #openstack-swift23:40
*** dmorita has quit IRC23:41
*** dmorita has joined #openstack-swift23:45
*** chsc has quit IRC23:47
*** daemontool has joined #openstack-swift23:53

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