Tuesday, 2015-07-14

notmynameI just registered for the Tokyo summit00:04
*** sorrison_laptop has joined #openstack-swift00:06
*** asettle has quit IRC00:07
*** kevinc_ has joined #openstack-swift00:13
notmynameUPDATE status SET random("Invalid", "Won't Fix) WHERE id = (SELECT * from launchpad_bugs WHERE date < 2014 AND status = "New");00:19
portantenotmyname: cute ... eh ... serious?00:34
portantemissing a double quote after "Fix"00:34
*** lyrrad has quit IRC00:39
notmynameportante: ehh...just being cute. and currently going through old bugs. mostly pseudo-SQL, not meant to be real :-)00:41
portante;)00:42
notmynamebut most of them end up being either invalid (now) or won't fix00:42
portanteso fedora closes most open bugs, slam door shut closed, after two releases (all bugs opened against F20 get closed once F22 goes), perhaps a good policy for swift?00:43
notmynameportante: like this one https://bugs.launchpad.net/swift/+bug/127396100:44
openstackLaunchpad bug 1273961 in OpenStack Object Storage (swift) "Unhandled exception in request" [Undecided,Invalid]00:44
notmynameso sometime well over a year ago there was an unhandled exception. not much I can do on it now :-)00:44
notmynameexcept change the status in order to beat the list of bugs down and make the list somewhat useful (I hope!)00:45
torgomaticespecially since the guy says he added some code to Swift, and then it blew the stack; while I sympathize, perhaps that's not worthy of a bug report, you know?00:45
torgomatic"Swift plus some stuff I typed in doesn't work"00:46
portantemakes total sense00:46
torgomaticme neither, but you don't see bug reports about it ;)00:46
notmynametorgomatic: to be fair, most of the stuff I type in for Swift doesn't work either ;-)00:46
portanteis there some bean counter that will cry foul?00:46
notmynameportante: I'm not too worried about the bean counters. only that we have a tool as a community that is useful for something00:47
portanteyes!00:47
portantepreach it!00:47
notmyname(but my launchpad karma is awesome!)00:47
notmyname(so I'm winning)00:47
portante;)00:47
portanteits the small battles that count00:47
notmynameI really don't like the categories LP gives00:48
notmynameI'd like something like "this is not a bug, but also not invalid"00:49
notmynamebut it's not a bug so I can't "won't fix" it because there's nothing to fix00:49
notmynamenor is it in-progress00:50
notmynamethe description on the "opinion" status is "doesn't fit with the project but can be discussed"00:51
notmynamebut why would you discuss it if it doesn't fit with the project?00:53
*** dmorita has joined #openstack-swift00:53
notmynameok, I'm out for now00:53
portantenotmyname: it seems lots of folks want to create a tool that simplifies the world so that they feel better about the world00:53
*** marzif_ has joined #openstack-swift01:01
*** gyee has quit IRC01:02
*** nexusz99 has joined #openstack-swift01:12
*** kota_ has joined #openstack-swift01:13
*** ChanServ sets mode: +v kota_01:13
*** marzif_ has quit IRC01:14
*** chlong-afk has joined #openstack-swift01:15
openstackgerritMerged openstack/swift: Cleanup error messages in ECDiskFileWriter.commit  https://review.openstack.org/19936201:15
kota_good morning01:15
*** ho has joined #openstack-swift01:16
*** sorrison_laptop has quit IRC01:22
*** kevinc_ has quit IRC01:28
mattoliveraukota_: morning02:04
kota_mattoliverau: good morning and I found you pushed nice patch, https://review.openstack.org/#/c/199863 a few days ago. I like this stuff :)02:05
kota_nice work02:06
mattoliveraukota_: thanks, that was because I needed a break from sharding and wanted to knock something off the OPs feedback list :)02:07
kota_i see02:08
hugokuohandoff zone affinity support !02:08
hugokuomornign02:09
kota_hugokuo: morning :) Are you interested in the patch too?02:11
hugokuokota_: Indeed. That's make sense for multiple region setup.02:12
kota_hugokuo: nice ;)02:12
*** mutoulbj has joined #openstack-swift02:17
*** bkopilov has quit IRC02:27
openstackgerritMatthew Oliver proposed openstack/swift-specs: Update sharding spec, notably regarding CountingTrie  https://review.openstack.org/20100002:44
*** mgriffin has joined #openstack-swift02:45
*** DericHorn-HP has joined #openstack-swift03:00
*** DericHorn-HP has quit IRC03:01
*** minwoob has joined #openstack-swift03:04
*** nexusz99 has quit IRC03:30
*** lyrrad has joined #openstack-swift03:41
*** hrou has quit IRC03:46
*** breitz has quit IRC03:53
*** breitz has joined #openstack-swift03:56
*** sanchitmalhotra has joined #openstack-swift04:00
*** minwoob has quit IRC04:05
*** bkopilov has joined #openstack-swift04:07
*** nexusz99 has joined #openstack-swift04:20
*** ppai has joined #openstack-swift04:30
openstackgerritPradeep Kumar Singh proposed openstack/swift: Emit warning log in object replicator  https://review.openstack.org/18506104:34
*** proteusguy_ has quit IRC04:44
*** kota_ has quit IRC05:02
*** nexusz99 has quit IRC05:07
*** sanchitmalhotra1 has joined #openstack-swift05:21
*** sanchitmalhotra has quit IRC05:23
*** SkyRocknRoll has joined #openstack-swift05:33
*** zaitcev has quit IRC05:53
*** SkyRocknRoll has quit IRC05:53
*** kota_ has joined #openstack-swift05:54
*** ChanServ sets mode: +v kota_05:54
*** chlong-afk has quit IRC06:09
*** SkyRocknRoll has joined #openstack-swift06:11
*** nexusz99 has joined #openstack-swift06:33
*** sanchitmalhotra has joined #openstack-swift06:42
*** psanchez_ has joined #openstack-swift06:44
*** sanchitmalhotra1 has quit IRC06:45
*** _fortis has joined #openstack-swift07:02
*** mutoulbj has quit IRC07:14
*** mutoulbj has joined #openstack-swift07:14
*** _fortis has quit IRC07:17
*** hseipp has joined #openstack-swift07:19
*** nexusz99 has quit IRC07:21
*** nexusz99 has joined #openstack-swift07:25
*** _fortis has joined #openstack-swift07:30
openstackgerritHisashi Osanai proposed openstack/swift: Make logic of unit tests responsive to the method names  https://review.openstack.org/20144207:32
*** chlong-afk has joined #openstack-swift07:37
*** jistr has joined #openstack-swift07:42
hugokuo 40 ffff8808715b4540 ffff8804819c58c0 ffff8802381f8d88 DIR  /srv/node/d224/quarantined/objects/b146865bf8034bfc42570b747c341b3207:55
hugokuoanyone knows why object-server try to open file in quarantined folder ?07:56
*** joeljwright has joined #openstack-swift08:37
*** ChanServ sets mode: +v joeljwright08:37
openstackgerritHisashi Osanai proposed openstack/swift: Improve Keystone v3 token support  https://review.openstack.org/20146108:44
*** aix has joined #openstack-swift08:51
*** aix has quit IRC08:58
*** aix has joined #openstack-swift09:03
*** dmorita has quit IRC09:04
*** sanchitmalhotra1 has joined #openstack-swift09:15
*** sanchitmalhotra has quit IRC09:17
*** sanchitmalhotra has joined #openstack-swift09:26
*** sanchitmalhotra1 has quit IRC09:28
*** marzif_ has joined #openstack-swift09:33
*** mahatic has joined #openstack-swift09:41
*** nexusz99_ has joined #openstack-swift09:50
*** nexusz99 has quit IRC09:53
*** sanchitmalhotra1 has joined #openstack-swift10:10
*** sanchitmalhotra has quit IRC10:12
*** aix has quit IRC10:21
*** kota_ has quit IRC10:34
*** mutoulbj has quit IRC10:34
*** aix has joined #openstack-swift10:34
*** sanchitmalhotra has joined #openstack-swift10:40
*** sanchitmalhotra1 has quit IRC10:41
*** psanchez_ has quit IRC11:01
*** openstackgerrit has quit IRC11:09
*** openstackgerrit has joined #openstack-swift11:09
*** mutoulbj has joined #openstack-swift11:15
*** psanchez_ has joined #openstack-swift11:17
*** ho has quit IRC11:21
*** mahatic has quit IRC11:25
*** kei_yama has quit IRC11:28
*** mahatic has joined #openstack-swift11:53
*** openstack has joined #openstack-swift12:13
*** ig0r_ has joined #openstack-swift12:23
*** annegent_ has quit IRC12:24
*** SkyRocknRoll has quit IRC12:24
*** annegentle has joined #openstack-swift12:25
*** nexusz99_ has quit IRC12:30
*** bkopilov has quit IRC12:32
*** proteusguy has joined #openstack-swift12:42
*** robefran has joined #openstack-swift12:49
*** hrou has joined #openstack-swift13:00
*** petertr7_away is now known as petertr713:10
*** ppai has quit IRC13:11
*** km has quit IRC13:15
*** joeljwright has quit IRC13:17
*** thurloat_isgone is now known as thurloat13:22
*** petertr7 is now known as petertr7_away13:25
*** sweeper has joined #openstack-swift13:26
sweepermorning folks13:26
sweeperI've got a swift cluster that lost 2 out of 40 drives yesterday, and it's being very very strange13:27
sweeperload average has shot up across the board13:27
sweeperwe haven't replaced the drives yet13:27
sweeperbut we haven't kicked off a rebalance either13:28
ctenniswhat process is driving the high load, the replicator?13:31
sweeperit looks like it's the object server13:31
sweeperdisk usage has gone way up as well13:32
sweeperso it may be part and parcel13:32
ctennisat first glance it sounds normal, things are replicating to get whole again13:32
*** marzif_ has quit IRC13:33
sweeperusage averages do seem to be slightly up...13:33
*** marzif_ has joined #openstack-swift13:33
ctennisthe swift logs may show what's going on behind the scenes, depending on hwere you're sending them.  We put them in /var/log/swift/all.log, you can check the progress of the replicator13:34
*** petertr7_away is now known as petertr713:34
sweeperherm13:35
*** mahatic has quit IRC13:35
sweeperit seems to be trying to replicate into unmounted directories..13:36
ctennisdo you have the mount check enabled?13:36
sweeperyea13:36
sweeperthere's a bug in that fwiw :P13:36
ctennisI've seen a bug there with respect to rsync yeah13:36
*** SkyRocknRoll has joined #openstack-swift13:38
sweeperit's weird. the object replicator reports the drive as unmounted, but persists in trying to rsync13:41
*** mahatic has joined #openstack-swift13:48
*** NM has joined #openstack-swift13:48
sweeperany idea why swift-recon would show only one unmounted drive, but object-replicator reports 3?13:55
wbhubernotmyname: yes, i am still working on the bug.  i have a couple of Q's for clayg related to the probe test changes he put in for us to test.13:55
*** doxavore has joined #openstack-swift13:57
*** petertr7 is now known as petertr7_away13:59
*** jrichli has joined #openstack-swift13:59
*** annegentle has quit IRC14:00
*** joeljwright has joined #openstack-swift14:00
*** ChanServ sets mode: +v joeljwright14:00
*** petertr7_away is now known as petertr714:00
*** tmcpeak has joined #openstack-swift14:03
tmcpeakhey all - I have a question about the Swift deployment guide, is this an appropriate place to ask?  Specifically I'd like to find out why this setting is recommended: net.ipv4.tcp_syncookies = 0  .  This has the potential to have a negative impact on security, so I'd like to understand if it's required14:04
*** lcurtis has joined #openstack-swift14:08
*** bkopilov has joined #openstack-swift14:12
*** jlhinson has joined #openstack-swift14:16
*** pbourke has quit IRC14:22
*** pbourke has joined #openstack-swift14:22
*** psanchez_ has quit IRC14:24
pelusetmcpeak, this is a good place to ask - I'm not the right one to answer though :(  I suspect folks that can answer will be around sometime soon though (few hours)14:24
*** minwoob has joined #openstack-swift14:26
*** samueldmq has quit IRC14:26
*** agentle_ has joined #openstack-swift14:28
ctennistmcpeak: it's just a preference.  most people aren't building publicly faceable swift clouds so the need for syn cookies isn't as important14:29
*** thurloat is now known as thurloat_isgone14:30
tmcpeakctennis: sure, that makes sense.  Is there a reason why disabling it is preferable though?14:30
tmcpeakseems like even internally having DoS protection is a good thing, if it isn't harming anything may as well leave it in?14:31
ctenniswell it only protects against specifically crafted DoS attacks that likely wouldn't originate from your internal network14:32
ctennismy best guess is that it's more performant without syn cookies on, and given the amount of TCP requests that happen in swift it's just a way of eeking out a bit of a performance gain14:32
ctennisit's not harming anything by leaving it on though14:33
tmcpeakctennis: ok, thank you14:36
mahaticctennis, hello, I think peluse mentioned about the S3-tests yesterday. Would you happen to know what should be placed in "access_keys" and "secret_keys"? in here https://github.com/ceph/s3-tests14:39
mahaticctennis, are those just the login credentials? or something else?14:39
ctennismahatic: yeah if you're using swiftstack auth or tempauth then access_key is just your username and secret_key is the password14:39
ctennisalso mahatic and peluse, confirmed that it was the ceph/s3-tests suite we used on those results I gave you14:43
*** tmcpeak has left #openstack-swift14:45
mahaticctennis, I'm not sure if I got that. Yes, I'm using the ceph/s3-tests currently14:45
mahaticctennis, oh I guess, I missed the conv yesterday. Got it14:47
mahaticctennis, I used the login credentials and my config file looks like this: http://paste.openstack.org/show/374535/ Could you let me know if I'm missing something there?14:48
mahaticctennis, With that config, it gives me a connection refused when I run the tests (http://paste.openstack.org/show/374552/)14:48
pelusectennis, she's jsut using an SAIO (not swiftstack installed) for the S3 tests14:48
ctennismahatic: I don't think your error is credential related, more HTTPS when expecting HTTP related14:49
pelusemahatic, make sure you undo your env proxy settings for actualling using your SAIO14:49
mahaticctennis, peluse hmm, I did remove the env proxy settings while trying that out14:51
*** jonb2 has quit IRC14:53
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925014:57
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:58
pelusemahatic, not sure... maybe hugokuo or timburke have tried this setup and seen something similar?15:04
*** ccavanna has quit IRC15:08
*** vinsh_ is now known as Vinsh15:09
*** ig0r__ has joined #openstack-swift15:10
*** ig0r_ has quit IRC15:10
hugokuomahatic: Paste 1) proxy-server.conf 2) "netstat -antulp" of the proxy server 3) use boto to talk to swift3 for testing to verify your Swift3 is setting properly.15:17
*** ig0r_ has joined #openstack-swift15:17
*** petertr7 is now known as petertr7_away15:18
hugokuomahatic: I suggest that to use http on proxy server as the beginning. I agree with ctennis's speaking about https/http15:18
*** ig0r__ has quit IRC15:19
mahatichugokuo, I did and 1) and 3) of what you mentioned. And not sure where to change the http/https?15:19
*** mahatic_ has joined #openstack-swift15:21
hugokuomahatic: May I have the link of proxy-server.conf ?     Does boto work for you? If yes, paste your boto script to pastebin please15:22
hugokuomahatic: regarding to the http/https it's in /etc/swift/proxy-server.conf15:23
hugokuomahatic: comment out these two lines https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L34-L3615:24
hugokuohow's your ST_AUTH looks like15:24
mahatichugokuo, http://paste.openstack.org/show/374626/ (proxy-server.conf)15:25
hugokuomahatic: For any configuration changes, you need restart proxy by $swift-init proxy restart15:25
mahaticah alright. Thanks for that info. Also I installed boto, but didn't specifically run a script, I thought the s3-tests took care of the conenction? I'm just running the s3-tests directly15:26
hugokuomahatic: confirmed. Your proxy-server listen on 8080 port w/o SSL. But your s3-test suite configuration specifies to use SSL http://paste.openstack.org/show/374535/  L12 , is_secure15:28
hugokuothe value should be "no"15:28
mahatichugokuo, oh okay, my bad! thanks much, I'll run the tests with that changed. Is there anything else I'm missing?15:31
hugokuomahatic: dunno yet. You can try it and let's see how's the result looks like15:32
mahatichugokuo, sure15:33
hugokuomahatic: btw, Swift3 wont't pass all test cases of ceph/s3-test15:33
hugokuoThere's portion of cases rely on Ceph's implementation.15:33
mahaticoh okay15:33
*** petertr7_away is now known as petertr715:35
*** mahatic__ has joined #openstack-swift15:36
*** mahatic has quit IRC15:37
*** fthiagogv has joined #openstack-swift15:39
*** ig0r__ has joined #openstack-swift15:40
*** ig0r_ has quit IRC15:43
*** lyrrad has quit IRC15:45
petertr7Are logs for this channel saved online somewhere?15:46
*** blmartin has joined #openstack-swift15:47
hrouyep: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/15:47
petertr7Thank you!15:50
*** marzif_ has quit IRC15:52
*** marzif_ has joined #openstack-swift15:52
robefranHi, I'm new here, and I'm interested in helping out with symlinks. Who should I contact?15:53
mahatic__hugokuo, http://paste.openstack.org/show/374659/ that's how the output looks. Still a forbidden error15:54
hugokuomahatic__: Perhpas you can read the log of proxy-server about why it's been denied15:56
hugokuowrong API entry or incorrect credential15:57
mahatic__yeah, I'm doing that. Just checking if you got something off the top of your mind :)15:57
*** mahatic_ has quit IRC15:57
hugokuoI ran s3-test about 1year ago. Can't remember all the details of the conf file tho15:57
mahatic__hmm okay15:57
charzmahatic__: try `sudo S3TEST_CONF=mys3.conf ./virtualenv/bin/nosetests -v`15:58
hugokuomahatic__: at least we figured out the first issue of http protocol :)15:59
mahatic__hugokuo, yup :)15:59
*** marzif_ has quit IRC15:59
hugokuocharz: hi champion , had you conduct s3-test suite recently. I remember that you did that around 2 months ago ?15:59
*** jlhinson has quit IRC16:01
*** jlhinson has joined #openstack-swift16:01
mahatic__charz, it tells me fuzz tests are ok. And the rest of the log gives error on functional tests (on __init__) like it's shown previously - forbidden16:03
charzhugokuo: I ran that a couple of months ago, I forgot.16:03
charzmahatic__: I think you need to look into the code of test, see how it work and also check the proxy's log.16:05
mahatic__yeah16:06
charzmahatic__: not all tests will pass, because s3-tests is develop for ceph, that's some behaviour are different than swift3.16:06
mahatic__charz, yeah. I'll dig into this issue, it showed at least show me it failed and probably not some error like this right?16:07
mahatic__it should at least*16:08
timburkemahatic__: what all users are defined for tempauth? my understanding is that user_id and display_name should both be of the form <account>:<username>, while access_key is just <username>16:11
timburkemahatic__: (though i must confess, i've not actually run the tests against tempauth)16:11
*** lyrrad has joined #openstack-swift16:11
charzmahatic__: sometime swift3 return some errors code that's not s3-tests expect. So you will got some response 404 or 403 from swift3.16:13
mahatic__timburke, oh okay. tempauth does not have my login credentials though (the ones I mentioned in S3 config) http://paste.openstack.org/show/374735/16:18
*** wbhuber has quit IRC16:25
*** thurloat_isgone is now known as thurloat16:34
*** thurloat is now known as thurloat_isgone16:38
*** robefran has quit IRC16:44
notmynamegood morning16:44
*** ccavanna has joined #openstack-swift16:46
notmynamejoeljwright: did I catch you or is it already too late?16:49
joeljwrightnotmyname: I'm here16:51
notmynamehmm..so swob implements HTTPServerError and HTTPInternalServerError. both map to a 500 status code. why do we do the same thing differently?16:51
notmynamejoeljwright: re swiftclient release16:52
notmynamejoeljwright: I looked yesterday. I don't see anything that should block a swiftclient release. did you find anything16:52
notmynamejoeljwright: if not, then I'll do that today16:52
joeljwrightnotmyname: I was planning on going through those tonight16:54
*** hseipp has quit IRC16:54
joeljwrightbut I'll have a look now and get back to you in ~30mins16:54
notmynamejoeljwright: thanks16:54
notmynamejoeljwright: I'm only looking for stuff that we can't release without instead of stuff that would be nice to have. there's a lot that would be nice to have16:55
notmyname(also, as part of prioritizing swiftclient better, I want to do more frequent releases)16:55
*** aix has quit IRC16:59
*** mgarza_ has joined #openstack-swift17:00
*** robefran has joined #openstack-swift17:01
*** doxavore has quit IRC17:02
*** doxavore has joined #openstack-swift17:05
*** petertr7 is now known as petertr7_away17:06
notmynameemail subject line: "What is a distributed database & do you need one?"17:09
joeljwrightnotmyname: there doesn't seem to be anything waiting that should postpone the release17:09
notmynameif you're asking me what a distributed DB is, then don't also ask me if you need one ;-)17:09
joeljwrightnotmyname: but an increase in release frequency would be nice17:09
notmynamejoeljwright: great, thanks!17:09
notmynamejoeljwright: I'll write up some release notes for an announce email today and make the tag17:10
joeljwright:)17:10
robefranIs anyone looking into tiering? I'm starting an investigation of tiering between containers with different policies (using symlinks)17:13
*** jistr has quit IRC17:14
peluserobefran, there are multiple specs in review/discussion to implmenet tiering - I am on my way out for a few hours but if you look at our specs repo you will see them.  There is also one that doesn't show up because of a -2 ; when I get back I can paste some links in if someone else hasn't already17:22
robefranpeluse: I've checked out the NetApp tiering proposal, but it got a lukewarm response. From the symlink proposal it looks like tiering based on symlinks would get more traction.17:23
peluserobefran, yeah, we talked at the summit and none of the specs "as is" is really what we're after.  Its a combination of a bunch of them and that considlation/summary work hasn't been done...17:26
* peluse heads out for a few hrs...17:27
*** NM1 has joined #openstack-swift17:28
*** NM has quit IRC17:30
robefranpeluse: I'm interested in helping out with symlinks, and with moving the tiering proposals forward.17:35
notmynamerobefran: that's great to hear!17:37
robefrannotmyname: Who is driving the symlink proposal? Who should I contact?17:39
notmynamerobefran: torgomatic first proposed it, and acoles_away and cschwede have also expressed interest. however, acoles_away is on vacation and torgomatic has been looking at a few other short-term things (ring improvements)17:41
notmynamerobefran: what would you like (from me) in order to get involved?17:41
*** NM1 has quit IRC17:42
robefrannotmyname: I see two parts to tiering, mechanics and decisions. I've been focusing on mechanics, and how to make sure that eventual consistency is maintained in the window between copying the hot-object to the cold-container, and creating the stub (symlink) in the hot container.17:47
robefrannotmyname: is there a current spec for tiering that is moving forward?17:48
notmynamerobefran: no. the only one I recall is the one from NetApp, which, as you said, had a "lukewarm response". like peluse mentioned, the mechanics are a combination of some different ideas, including symlinks, that haven't been gathered in one place17:50
*** NM has joined #openstack-swift17:51
*** openstackgerrit has quit IRC17:56
*** openstackgerrit has joined #openstack-swift17:56
robefrannotmyname: I could draft a tiering proposal based on symlinks, but I'm new to the community, and I could use some guidance on how to get a proposal started.17:57
openstackgerritMichael Barton proposed openstack/swift: go: fix expect 100-continue in replicator  https://review.openstack.org/20169017:57
notmynamerobefran: specs are simply text documents describing an idea that should get input before you start coding. it's not really a full-on up-front design spec. it's more of a way to have a conversation about an idea while we're on opposite sides of the world18:00
notmynamerobefran: but backing up a bit, are you familiar with the mechanics of contributing to any openstack project?18:01
*** agentle_ has quit IRC18:02
*** agentle_ has joined #openstack-swift18:02
mahatic__hugokuo, charz , timburke I gave the SAIO test credentials instead of my login in S3 config and it worked18:04
robefrannotmyname: this will be my first contribution to openstack. I've setup the SAIO, and my first step was to propose some additional functional tests for COPY-to-same-name. Then I planned to help out with the symlink implementation.18:04
charzmahatic__: oh, cool!18:05
notmynamerobefran: great! you've already proposed a patch? which one is it?18:05
robefrannotmyname: I haven't proposed the COPY-to-same-name functest patch yet, that was going to be my first step18:06
notmynameah ok18:06
notmynamerobefran: so you've got a SAIO. that's good. have you set up git-review and your credentials yet?18:06
*** petertr7_away is now known as petertr718:07
timburkemahatic__: oh good! you might want to tweak some of the middleware config options; turning on s3_acl and turning off dns_compliant_bucket_names help a decent bit. fwiw, the best test runs i've seen still have ~100 failures18:07
robefrannotmyname: I've registered at UbuntuOne and OpenStack (id robefran@ca.ibm.com for both). I've already added a review comment on the symlink proposol.18:09
notmynameok, that's good18:10
robefrannotmyname: I'll get to work on the functest and see how that goes. An additional functest should be harmless.18:11
notmynamerobefran: so now, with any openstack project you want to contribute a patch to, the process is (one time up front) do `git review -s` to set it up, then when you're on your branch with a single commit to propose, do `git review`18:11
notmynamerobefran: great. that would be a really good place to start18:11
notmynamerobefran: the only "odd" thing, IMO, with contributing to swift is that you need to propose your change as one patch, not a series of patches. that means you'll propose something, get feedback, update your local patch, and then have to do a `git commit --amend` before another `git review`18:12
mahatic__timburke, thanks for me letting me know. w/o acl, this what it looks like - SKIP=4, errors=88, failures=7318:12
*** janonymous_ has joined #openstack-swift18:23
janonymous_Could someone please have a look at these patches and review these : https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z18:24
janonymous_Thanks .18:24
*** wasmum- has joined #openstack-swift18:24
*** distroguy has joined #openstack-swift18:25
*** SkyRocknRoll has quit IRC18:26
notmynamerobefran: and I just drew all that up on the whiteboard for amandap here in the office. seems she's working on improving upstread docs on the process :-)18:27
notmynamerobefran: amandap: here's the swift contributing doc: https://github.com/openstack/swift/blob/master/CONTRIBUTING.md18:28
*** doxavore_ has joined #openstack-swift18:28
*** mgagne_ has joined #openstack-swift18:29
*** kcaj_ has joined #openstack-swift18:30
*** doxavore has quit IRC18:30
*** blmartin has quit IRC18:30
*** chlong-afk has quit IRC18:30
*** alpha_ori has quit IRC18:30
*** Abyss_ has quit IRC18:30
*** csmart has quit IRC18:30
*** Protux has quit IRC18:30
*** kcaj has quit IRC18:30
*** zhiyan has quit IRC18:30
*** timburke has quit IRC18:30
*** wasmum has quit IRC18:30
*** mgagne has quit IRC18:30
*** sileht has quit IRC18:30
*** mrda-away has quit IRC18:30
*** timburke_ has joined #openstack-swift18:30
*** CaioBrentano has joined #openstack-swift18:31
*** alpha_ori has joined #openstack-swift18:31
*** mgagne_ has left #openstack-swift18:33
*** timburke_ is now known as timburke18:34
*** SkyRocknRoll has joined #openstack-swift18:40
*** mgagne_ has joined #openstack-swift18:41
*** kcaj_ has quit IRC18:47
*** kcaj has joined #openstack-swift18:49
*** mahatic__ has quit IRC18:51
*** AJS_ has quit IRC18:51
*** openstackgerrit has quit IRC18:56
*** openstackgerrit has joined #openstack-swift18:56
zackmdavisjanonymous_, (speaking of the Py3 crusade, I notice the Python34 gate jobs on those patches are failing on importing rfc822; I had some thoughts earlier about what we might have to do about that, but haven't gotten around to writing a patch (as torgomatic pointed out, we're relying on rfc822 functionality that doesn't really exist in the more modern 'email' package))19:00
*** Guest1999 has joined #openstack-swift19:01
Guest1999Question about ring file. Did anyone try to hack the ring file to change zone information of a device.19:02
* torgomatic is interested to see what happens with the code using rfc82219:02
torgomaticGuest1999: you have to remove the device and then re-add it with its new zone19:03
Guest1999and there is no other way I guess then. because the assignment is based on that value right?19:03
torgomaticGuest1999: yeah, if you just edited the builder to change the zone in-place, your dispersion could get screwed up19:04
*** zaitcev has joined #openstack-swift19:04
*** ChanServ sets mode: +v zaitcev19:04
torgomaticlike if a partition has replicas in zones 1, 2, and 4, but then you change a disk's zone and now it's 1, 4, 419:04
torgomaticso that's why19:04
Guest1999Thank torgomatic got it thats what I thought. Also did you ever experience high CPU usage with affinity. I did an experiment with large parallel requests with small objects and affinity for read and write . In both cases the CPU get a very high utilization than non-affinity runs19:05
Guest1999i am referring to proxy19:05
torgomaticGuest1999: nope, I haven't observed that behavior19:05
Guest1999is this something that should happen with affinity i.e. CPU increase.19:06
*** mutoulbj has quit IRC19:07
janonymous_torgomatic : please tell me if i could do something to help19:07
torgomaticGuest1999: not to my knowledge19:07
torgomaticjanonymous_: figure out if there's something in py3 stdlib that can do what `rfc822.Message(fp, 0)` does :)19:08
Guest1999ok this is very strange behaviour . I ran profiler to check where the time is spent. most was in ring.py (get_more_nodes).... in case of affinity19:09
janonymous_I'll  search :)19:09
torgomaticjanonymous_: I tried to figure out how to do it with email.parser, but couldn't get it to stop slurping document bodies into memory; that was in response to someone saying rfc822 was deprecated in a review comment, though19:10
janonymous_I have kept on hold furthur patches as earlier were not reviewed. should i continue to submit patches ?19:10
*** joeljwright has quit IRC19:11
torgomaticjanonymous_: probably let the existing ones drain a bit first, then continue; otherwise you're constantly rebasing. Easier to have just a couple outstanding at a time.19:11
janonymous_Ohh.. i see19:12
*** Guest1999 has left #openstack-swift19:13
zackmdavistorgomatic, janonymous_, re header parsing without touching the rest of the file, I was thinking we're doomed to just include the 20ish lines of code we need to do it ourselves; you can see where it happens inside of email.feedparser, but email.feedparser is not modular enough to let us call just that: https://github.com/python/cpython/blob/master/Lib/email/feedparser.py#L220-23619:15
torgomaticzackmdavis: yeah, that'd work. it's either that or expose that as a method on email.feedparser, but that'd require patches to Python itself19:17
*** wbhuber has joined #openstack-swift19:20
*** agentle__ has joined #openstack-swift19:20
*** agentle_ has quit IRC19:24
janonymous_:o19:25
*** petertr7 is now known as petertr7_away19:28
*** barker has joined #openstack-swift19:31
*** fthiagogv has quit IRC19:31
*** petertr7_away is now known as petertr719:31
*** fthiagogv has joined #openstack-swift19:36
*** mgarza_ has quit IRC19:37
*** jrichli has quit IRC19:37
*** mgarza_ has joined #openstack-swift19:38
openstackgerritMichael Barton proposed openstack/swift: go: fix expect 100-continue in replicator  https://review.openstack.org/20169019:46
amandap@notmyname Thanks :) Everyone seems to do it a bit different but referring to the HowTo wiki and the Infra page seems most common.19:47
*** mgarza_ has quit IRC19:49
*** Abyss_ has joined #openstack-swift19:49
*** chlong-afk has joined #openstack-swift19:49
*** blmartin has joined #openstack-swift19:49
*** mgarza_ has joined #openstack-swift19:49
*** sileht has joined #openstack-swift19:49
*** mrda-away has joined #openstack-swift19:52
openstackgerritjanonymous proposed openstack/swift: Adding bandit for security static analysis testing in swift  https://review.openstack.org/19639519:54
*** mgarza_ has quit IRC19:57
*** mgarza_ has joined #openstack-swift19:57
*** Protux has joined #openstack-swift19:57
*** barker has quit IRC20:02
*** agentle__ is now known as annegentle20:02
*** zhiyan has joined #openstack-swift20:02
*** SkyRocknRoll has quit IRC20:03
*** robefran has quit IRC20:16
openstackgerritpaul luse proposed openstack/swift: Add ability for GET path to see/select alternate fragment archives  https://review.openstack.org/20128320:28
notmynamepeluse: that patch is resolving one of the EC bugs right?20:28
pelusetorgomatic, clayg ^ ready for some eyes.  Still needs more tests but please review the implementation20:28
pelusenotmyname, maybe :)20:28
pelusedepends20:28
pelusepossibly20:28
pelusewe'll see20:29
notmynamepeluse: heh, ok. if it is, a bug reference int he commit message would be nice. I remember you saying you were working on something when I was asking about one of the bugs. just don't remember the details20:29
pelusenotmyname, yeah.  all kidding aside this is something we talked about a while ago and since then some bugs have come up that are most definately related but ebcause I started this becfore those bugs were filled I'm not 100% sure20:30
peluseafter adding some probe tests it should be clearer20:30
notmynamegood20:31
pelusenotmyname, so it *might* have material impact on bug #145769120:34
openstackbug 1457691 in OpenStack Object Storage (swift) "Insufficient Fragments occurred on EC GET object" [High,Confirmed] https://launchpad.net/bugs/1457691 - Assigned to Bill Huber (wbhuber)20:34
pelusewill start by adding a suggestd probe test from clayg written up on that report20:34
wbhuberpeluse: I've tried running the probe test that clayg wrote up on the report.  it hung and i've been trying to zero in on where the train wrecks at.20:35
*** ccavanna has quit IRC20:36
*** janonymous has quit IRC20:36
pelusewbhuber, is there already a probe test written? I just see a scenario in english.  if you can post what you have I'll try it on my stuff20:37
wbhuberpeluse: sure.20:38
pelusewbhuber, also please take a look at https://review.openstack.org/#/c/201283/ when you get a chance20:38
*** sanchitmalhotra has quit IRC20:38
*** mgarza_ has quit IRC20:38
*** mgarza has joined #openstack-swift20:39
janonymous_could somone please confirm my understanding as mentioned in last comment on bug : https://bugs.launchpad.net/swift/+bug/143981620:39
openstackLaunchpad bug 1439816 in OpenStack Object Storage (swift) "If PID file becomes empty, swift-init throws exception" [Undecided,In progress] - Assigned to janonymous (janonymous)20:39
torgomaticjanonymous_: yep20:41
notmynametorgomatic: can you please mark it as fix committed?20:42
torgomaticSO MUCH CLICKING20:42
notmynameindeed20:42
notmynameyou'll get launchpad karma20:42
*** mgarza has quit IRC20:42
notmynamethat and $2 will get you a cup of coffee20:43
pelusecrappy coffee me thinks20:44
notmynamebetter coffee would require more LP karma20:45
openstackgerritMinwoo Bae proposed openstack/swift: EC: Handoff node to push existing fragment to the correct location.  https://review.openstack.org/19684820:45
pelusemore clicky cicky clicky20:45
torgomaticwe need an update to RFC 2324 with the POUROVER verb; the response SHOULD include an Origin header20:47
notmynameunfortunately, the response is always a 40220:48
*** sanchitmalhotra has joined #openstack-swift20:48
*** janonymous_ has quit IRC20:50
*** mgagne_ is now known as mgagne20:50
*** janonymous has joined #openstack-swift20:51
janonymouscoffee , wow :D20:53
notmynameseems that I no longer have the ability to push a release for swiftclient. working through the bureaucracy now21:09
*** petertr7 is now known as petertr7_away21:12
klrmnnotmyname: wow, if not you, then who did they expect to do it?21:14
notmynameseems I missed the announcement that it's a whole managed thing now21:15
*** sanchitmalhotra1 has joined #openstack-swift21:17
*** sanchitmalhotra has quit IRC21:19
*** janonymous has quit IRC21:20
notmynameso here's another thing that should be looked at by people in swift https://review.openstack.org/#/c/16403521:20
*** blmartin has quit IRC21:22
*** fthiagogv has quit IRC21:31
redbothe only sucky thing would be how often we use "with Timeout"21:33
notmynameredbo: not anything about having to have enough threads to handle 15k req/sec?21:34
openstackgerritNadeem Syed proposed openstack/swift: go: adding middleware & routing framework  https://review.openstack.org/19527921:35
redboWell, I figured it could be a regular wsgi application and we could still run it on eventlet if we wanted.21:35
*** jlhinson has quit IRC21:36
redboI'm assuming the people suggesting threads have never tried it.21:36
notmynamelol21:36
notmynamethat spec and the discovery that I can no longer make swiftclient releases makes me glad I bought a bottle of booze at lunch21:37
torgomaticThreads work really well compared to eventlet when you have a C-level mysql connection that blocks the eventlet hub constantly.21:37
torgomatic*cough* hypothetically21:38
redboThat's fair.  They might work well on our container server too.21:38
notmynametorgomatic: guess where the major point on server contention is in most other openstack projects ;-)21:39
redboThe GIL is supposed to be better in python 3, but on something like the proxy where it's all networking and python code, eventlet is still probably going to win.21:42
notmynamepython-swiftclient release is delayed at least until tomorrow while I figure out the new state of things21:44
*** NM has quit IRC21:50
*** delattec has quit IRC21:52
zaitcevI submitted a talk for M summit using the joke I made during IRC meeting and redbo seconded. If only I could use the IRC log somehow (well, assuming it gets accepted)21:56
*** shakamunyi has joined #openstack-swift21:58
*** doxavore_ has quit IRC22:00
openstackgerritBill Huber proposed openstack/swift: EC: Fix Insufficient Fragment on secondary GET call  https://review.openstack.org/20179122:06
wbhuberpeluse: here's a probe test written that is hung.  at your earliest convenience, https://review.openstack.org/#/c/201791/22:09
*** hrou has quit IRC22:12
*** kutija has quit IRC22:13
*** minwoob has quit IRC22:14
*** cdelatte has joined #openstack-swift22:14
*** delattec has joined #openstack-swift22:14
*** annegentle has quit IRC22:18
*** kutija has joined #openstack-swift22:20
*** sanchitmalhotra has joined #openstack-swift22:28
*** sanchitmalhotra1 has quit IRC22:29
*** zaitcev has quit IRC22:33
*** darrenc is now known as darrenc_afk22:35
*** kutija_ has joined #openstack-swift22:36
*** sanchitmalhotra1 has joined #openstack-swift22:38
*** kutija has quit IRC22:39
*** sanchitmalhotra has quit IRC22:40
mattoliverauMorning22:44
*** ccavanna has joined #openstack-swift22:46
*** wbhuber has quit IRC22:48
*** darrenc_afk is now known as darrenc22:56
*** km has joined #openstack-swift23:00
*** lcurtis has quit IRC23:00
*** hrou has joined #openstack-swift23:01
*** pgbridge has quit IRC23:18
*** delattec has quit IRC23:29
*** cdelatte has quit IRC23:29
*** bitblt has joined #openstack-swift23:31
*** barra204 has joined #openstack-swift23:35
*** shakamunyi has quit IRC23:36
*** cdelatte has joined #openstack-swift23:47
*** cdelatte has quit IRC23:47
*** ho has joined #openstack-swift23:50
hogood morning!23:50

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