Monday, 2014-06-02

*** otherjon has quit IRC00:18
*** otherjon has joined #openstack-swift00:19
*** matsuhashi has joined #openstack-swift00:27
*** dmorita has joined #openstack-swift00:34
*** nosnos has joined #openstack-swift00:43
*** fifieldt has joined #openstack-swift01:15
*** mkollaro has quit IRC01:30
*** diegows has quit IRC01:59
*** fifieldt has quit IRC02:47
*** nosnos has quit IRC03:34
*** leews has joined #openstack-swift03:37
*** sungju has joined #openstack-swift03:37
*** miqui has quit IRC03:51
*** zhiyan_ is now known as zhiyan03:54
*** nosnos has joined #openstack-swift04:26
*** ppai has joined #openstack-swift04:35
*** kashyapk has joined #openstack-swift04:37
*** nthacker_ has joined #openstack-swift04:40
nthacker_Hi Guys, one of my recent check-in's failed a pep8 test. :P . I wanted to verify the pep8 before I resubmit for review. I dont see a pep8 script that Jenkins uses in the Swift tree - can I assume that the pep8 jenkins runs is full pep8 check or there are some exclusions?04:41
*** kashyapk has quit IRC04:42
nthacker_or can someone tell me how I can see the contents of pep8_check.sh that Jenkins runs04:42
*** kashyapk has joined #openstack-swift04:42
*** sungju has quit IRC04:45
*** kashyapk has quit IRC04:47
*** kashyapk has joined #openstack-swift04:52
*** psharma has joined #openstack-swift04:53
*** kashyapk_ has joined #openstack-swift04:58
*** kashyapk has quit IRC04:58
mattoliveraunthacker_: hey, the pep8 job, used for swift is the a generic job. Its called run-pep8.sh. It's just using tox. You can see a copy of the script at http://is.gd/api.php?longurl=https%3A%2F%2Fgit.openstack.org%2Fcgit%2Fopenstack-infra%2Fconfig%2Ftree%2Fmodules%2Fopenstack_project%2Ffiles%2Fslave_scripts%2Frun-pep8.sh05:11
*** nthacker_ has quit IRC05:24
*** sungju has joined #openstack-swift05:24
*** sungju has quit IRC05:29
*** mkollaro has joined #openstack-swift05:33
*** sungju has joined #openstack-swift05:46
*** sungju has quit IRC05:49
openstackgerritNirmal Thacker proposed a change to openstack/swift: Fixes a low hanging fruit in container auditor  https://review.openstack.org/9714805:54
*** sungju has joined #openstack-swift06:03
*** sungju has quit IRC06:09
*** Midnightmyth has joined #openstack-swift06:17
*** sungju has joined #openstack-swift06:19
*** nshaikh has joined #openstack-swift06:24
*** mlipchuk has joined #openstack-swift06:57
*** mlipchuk has quit IRC07:01
*** kashyapk_ has quit IRC07:10
*** kashyapk has joined #openstack-swift07:11
*** mlipchuk has joined #openstack-swift07:15
*** kashyapk has quit IRC07:15
*** jamie_h has joined #openstack-swift07:19
*** fifieldt_ is now known as fifieldt07:26
mattoliverauGood night all, it has been a very quiet day, maybe I'm the only one here from an Australian like timezone!07:33
*** mkollaro has quit IRC07:44
*** nsquare has quit IRC07:47
*** kashyapk has joined #openstack-swift07:53
*** jamie_h has quit IRC07:58
*** nacim has joined #openstack-swift07:59
*** jamie_h has joined #openstack-swift07:59
*** mlipchuk has quit IRC08:04
*** haomaiwa_ has joined #openstack-swift08:14
*** haomaiwa_ has quit IRC08:19
*** jamie_h_ has joined #openstack-swift08:19
*** jamie_h has quit IRC08:19
*** mlipchuk has joined #openstack-swift08:22
*** mlipchuk has left #openstack-swift08:23
-openstackstatus- NOTICE: setuptools upstream has broken the world. it's a known issue. we're hoping that a solution materializes soon08:32
*** ChanServ changes topic to "setuptools upstream has broken the world. it's a known issue. we're hoping that a solution materializes soon"08:32
*** haomaiwa_ has joined #openstack-swift08:33
*** haomaiwa_ has quit IRC08:40
*** fbo has joined #openstack-swift08:42
*** nshaikh has quit IRC08:44
*** roock has joined #openstack-swift08:48
*** foexle has joined #openstack-swift08:58
*** mlipchuk1 has joined #openstack-swift09:02
*** haomaiwang has joined #openstack-swift09:08
ppaiis account name unique across swift cluster ? Or does it depend on reseller_prefix ?09:20
*** nshaikh has joined #openstack-swift09:22
*** sungju has quit IRC09:55
*** nshaikh has quit IRC10:01
*** nshaikh has joined #openstack-swift10:04
*** dmorita has quit IRC10:29
*** Midnightmyth has quit IRC10:33
*** sungju has joined #openstack-swift10:41
*** sungju has quit IRC10:42
*** ppai has quit IRC10:58
*** mlipchuk1 has quit IRC11:05
*** ppai has joined #openstack-swift11:16
*** zhiyan is now known as zhiyan_11:19
*** zhiyan_ is now known as zhiyan11:20
*** kashyapk has quit IRC11:26
*** diegows has joined #openstack-swift11:27
*** mlipchuk has joined #openstack-swift11:34
*** kashyapk has joined #openstack-swift11:35
*** Edward-Zhang has joined #openstack-swift11:39
*** nshaikh has quit IRC11:52
*** kashyapk has quit IRC12:05
*** kashyapk has joined #openstack-swift12:05
*** mkollaro has joined #openstack-swift12:06
*** erlon has joined #openstack-swift12:10
*** matsuhashi has quit IRC12:22
*** mlipchuk has quit IRC12:29
*** Midnightmyth has joined #openstack-swift12:32
*** kashyapk has quit IRC12:42
*** ppai has quit IRC12:42
*** mlipchuk has joined #openstack-swift12:44
*** psharma has quit IRC12:44
*** miqui has joined #openstack-swift13:03
*** mlipchuk has quit IRC13:04
*** Midnightmyth has quit IRC13:12
*** samuelmz has joined #openstack-swift13:13
samuelmzHi, when using devstack to install OS, it sets iniset operator_roles to  'Member' and 'admin' with 'iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:keystoneauth operator_roles "Member, admin"' at https://github.com/cloudbuilders/devstack/blob/master/lib/swift13:16
samuelmzIt may cause an inconsistence in some cases: suppose a cloud admin grants the '_member_' role to a user... then he will not be able to properly use swift13:17
samuelmzFor me, having Member and _member_ roles is inconsistent13:18
samuelmzI know it isn't a swift bug, but do you agree with me at this point?13:18
*** nosnos has quit IRC13:18
*** kashyapk has joined #openstack-swift13:20
*** mlipchuk has joined #openstack-swift13:21
*** kashyapk has quit IRC13:31
*** kashyapk has joined #openstack-swift13:32
*** kashyapk has quit IRC13:36
*** jamie_h_ has quit IRC14:00
*** jamie_h has joined #openstack-swift14:00
*** mlipchuk has quit IRC14:07
*** nshaikh has joined #openstack-swift14:10
*** jamie_h_ has joined #openstack-swift14:10
*** jamie_h has quit IRC14:11
*** byeager has joined #openstack-swift14:16
*** ChanServ changes topic to "Storage Policies have been proposed to master. Soft freeze in effect until these patches land | First SP patch: https://review.openstack.org/#/c/96026/ | Last SP patch: https://review.openstack.org/#/c/96049/"14:17
-openstackstatus- NOTICE: setuptools issue was fixed in upstream in 3.7.1 and 4.0.1, please, recheck on bug 132551414:17
*** mlipchuk has joined #openstack-swift14:22
*** Edward-Zhang has quit IRC14:35
*** Midnightmyth has joined #openstack-swift14:41
*** jamie_h_ has quit IRC14:52
*** jamie_h has joined #openstack-swift14:53
*** kenhui has joined #openstack-swift14:53
*** jamie_h has quit IRC15:02
*** jamie_h has joined #openstack-swift15:07
*** byeager has quit IRC15:08
*** byeager has joined #openstack-swift15:08
*** physcx has quit IRC15:12
claygcreiht: it's expensive to do the double updates in the trigger - plus the total counts in the container don't really help with backwards compat if they don't match the listing15:12
*** byeager has quit IRC15:13
claygcreiht: one thing I thought about was doing sp0 stats in the container_stat table - it'd just be some messy sql in the triggers and maybe a little meassy in the policy_stats query15:14
creihtclayg: ahh yeah I guess since the account updates are async performance in't as much of an issue then15:17
torgomaticso if someone upgrades to version w/SP then downgrades again, do their sqlite triggers stay upgraded?15:19
claygshit, i broke storage policies15:19
* torgomatic really doesn't know the answer to that15:20
claygcreiht: well i just know that single container upload is already a point of contention - creation of lots and lots of container is less worry some15:20
torgomaticI know user-defined functions have to be set up every time you open a DB, which is why I ask15:20
creihtyeha15:20
claygtorgomatic: yeah no the triggers stick around15:21
claygtorgomatic: so new databases would continue to track counts int he policy stat table - and then the get_info query won't know how to find the stats15:21
claygtorgomatic: I think a downgrade script to copy sp0 counts back into container_stat and delete/recreate the old triggers on the object table would work15:22
creihttorgomatic: well my biggest concern is during rolling upgrades15:22
creihtto make sure things work while everything is upgrading15:22
notmynamegood morning15:25
torgomaticcreiht: indeed15:25
claygcreiht: should be fine during upgrades, maybe if you have replication going while you're upgrading you'll get old servers with new db's rsync'd over15:26
claygcreiht: but the db's will still do the right thing15:27
creihthrm15:27
*** elambert has joined #openstack-swift15:28
creihtclayg: oh true15:28
*** byeager has joined #openstack-swift15:30
*** byeager has quit IRC15:31
*** byeager has joined #openstack-swift15:31
*** wasmum has joined #openstack-swift15:35
*** wasmum has quit IRC15:35
*** wasmum has joined #openstack-swift15:36
wasmumanyone using swift3 with keystone?15:37
*** foexle has quit IRC15:40
*** zaitcev has joined #openstack-swift15:43
*** ChanServ sets mode: +v zaitcev15:43
*** gyee has joined #openstack-swift15:53
redboI'm pro new funk15:55
*** zhiyan is now known as zhiyan_15:57
*** mlipchuk has quit IRC15:59
*** haomaiwang has quit IRC16:03
*** blinky_ghost has joined #openstack-swift16:06
*** haomaiwa_ has joined #openstack-swift16:07
blinky_ghosthi all, I'm trying to setup swift in HA mode through haproxy. When I run the command swift stat to my virtual IP I get this message: Account HEAD failed: http://192.168.151.202:8080:8080/v1/AUTH_0397893622aa4899b7bb59cbdb14fe48 503 Service Unavailable16:08
blinky_ghost If I use my physical IP it runs OK. What I'm missing? thanks16:08
notmynameblinky_ghost: looks like you have 2 ports there (:8080:8080). what's up with that?16:09
blinky_ghostnotmyname: yes I know. but If I delete my keystone endpoint and create it through my physical IP, it works fine. I don't understand this.16:10
zaitcevIt means the HTTP netloc parsing in HA proxy is more robust than in eventlet and the request is rejected16:11
*** byeager has quit IRC16:11
zaitcevprobably16:11
blinky_ghostzaitcev: do you have an haproxy conf template for swift?16:12
wasmumblinky_ghost: what does you auth line in your proxy.conf look like?16:12
blinky_ghostwasmum: auth_host = 192.168.151.20216:13
wasmumblinky_ghost: and that matches your endpoint?16:13
blinky_ghostwasmum: yes, It's my Virtual IP16:14
blinky_ghost| b6fb1e724f284264a8e503573cda71a9 | RegionOne | http://192.168.151.202:8080/v1/AUTH_%(tenant_id)s | http://192.168.151.202:8080/v1/AUTH_%(tenant_id)s |         http://192.168.151.202:8080          | 454e9332656b4e98b2bbc5d9029fe875 |16:14
blinky_ghostI have my endpoint created like this. If change the to 192.168.151.1 (the physical ip) of one of my servers it will work ok.16:15
wasmumyour vip, listening on port XX forwarding to proxy server 8080?16:16
*** nshaikh has quit IRC16:16
*** cutforth has joined #openstack-swift16:18
blinky_ghostwasmum: listening on the same port 8080, 192.168.151.202:8080 -> 192.168.151.1:808016:18
*** haomaiwa_ has quit IRC16:18
wasmumif your vip is sending the traffic to 8080 you do not have to specify that in the url.  just as +notmyname pointed out.  You have dual ports specified in the url16:19
wasmumremove the port setting in your endpoint and give that a try16:20
blinky_ghostwasmum: It's working now :) It was a problem in haproxy conf. I was using http protocol16:20
wasmumcool16:20
blinky_ghostthank you all :)16:20
*** byeager has joined #openstack-swift16:21
*** byeager_ has joined #openstack-swift16:22
*** jamie_h has quit IRC16:22
*** haomaiwang has joined #openstack-swift16:24
*** byeager has quit IRC16:25
blinky_ghostAnother question :)  I have 4 nodes with 2 disks each in RAID-1, where I will create a 200gb partition, and will use swift as glance backend. My question is what values should I use swift-ring-builder account.builder command? thanks :)16:29
openstackgerritSamuel Merritt proposed a change to openstack/swift: Remove unused variable  https://review.openstack.org/9728716:29
notmynameblinky_ghost: http://rackerlabs.github.io/swift-ppc/ might be helpful for you16:32
wasmumblinky_ghost: partition power = drives @ max cluster X 100, then take the closest number 2 to the power of x x = closest number to the drives X 100 and then x also = the partition power16:33
wasmumit's really impossibl to explain without a graphic16:33
wasmumsee the suggestion from +notmyname16:33
*** haomaiwang has quit IRC16:35
blinky_ghostwasmum: I want 4 replicas = 4 servers, 1 min drive = 1 partition from one server, 4 max drives = 4 total partitions from all the servers. Is my understanding correct? :)16:35
*** shakamunyi has joined #openstack-swift16:36
wasmumbloinky_ghost: swift-ring-builder container.builder create 9 4 416:40
wasmumgives you the part power of 9 4 replicas  4 zones?16:40
*** kenhui has quit IRC16:41
blinky_ghostwasmum: thanks :)16:42
*** haomaiwa_ has joined #openstack-swift16:43
*** byeager_ has quit IRC16:51
zaitcevoh just always use 18 unless you run 1GB RAM nodes or something16:51
*** byeager has joined #openstack-swift16:51
zaitcevI see no downside in oversized arrays except RAM16:51
zaitcevyour replication is going to be softer, not as chunky... 100k partitions for everyone16:52
wasmumblinky_ghost, update, should look somethin g like this "swift-ring-builder <builder_file> create <part_power> <replicas> <min_part_hours>" or swift-ring-builder container.builder create 9 4 1.  You do not want a <min_part_hours> set at 4 for that cluster16:53
blinky_ghostwasmum: 18 4 1 ?16:53
zaitcevmodern nodes are aways so crazy fat because of all XFS caches they have to carry to support 60 drives, 18-bit ring is like what16:54
blinky_ghostzaitcev: I will only use this for glance backend it will not have a big I/O16:55
*** byeager has quit IRC16:56
*** haomaiwa_ has quit IRC16:58
zaitcevI'm just saying17:00
zaitcev[root@rhev-a24c-01 ~]# swift-ring-builder /etc/swift/object.builder17:00
zaitcev262144 partitions, 3.000000 replicas, 1 regions, 3 zones, 9 devices, 0.00 balance17:00
zaitcevthat's 18 bits, right?17:00
zaitcevso17:01
zaitcev[root@rhev-a24c-01 ~]# ls -l /etc/swift/object.builder17:01
zaitcev-rw-r--r--. 1 root root 1836523 May 14  2013 /etc/swift/object.builder17:01
zaitcevSay, couple of megs for one ring (per process, of course)17:02
*** byeager has joined #openstack-swift17:09
*** mkollaro has quit IRC17:13
*** shri has joined #openstack-swift17:15
*** mkollaro has joined #openstack-swift17:17
*** byeager has quit IRC17:22
*** byeager has joined #openstack-swift17:22
*** kenhui has joined #openstack-swift17:25
*** byeager has quit IRC17:27
*** nsquare has joined #openstack-swift17:27
blinky_ghostI've setup replication using rsync and now I'm getting this error: http://pastebin.com/3jXBwR5k any hint?17:28
*** fbo is now known as fbo_away17:28
*** kenhui has quit IRC17:31
portantecreiht: did you ever get that 3D logo thing printed?17:32
*** mkollaro has quit IRC17:32
creihtportante: not yet17:32
creihtneed to do some work on it17:32
*** kenhui has joined #openstack-swift17:33
*** Thurloat has joined #openstack-swift17:35
*** kenhui has quit IRC17:37
openstackgerritPeter Portante proposed a change to openstack/swift: Handle func tests of swift cluster that hide /info  https://review.openstack.org/9729717:38
*** sandywalsh_ has quit IRC17:39
*** pberis1 has quit IRC17:46
*** byeager has joined #openstack-swift17:53
zaitcevpconstantine_: I'm stuck with shit IRC but I caught your Q and will look17:58
*** sandywalsh has joined #openstack-swift17:58
pconstantine_zaitcev: cool! I'll go home for now, will ping you tomorrow.17:59
zaitcevis this what you mentioned on IRC /query before18:00
zaitcevoh18:01
*** byeager has quit IRC18:01
*** zul has quit IRC18:08
*** zul has joined #openstack-swift18:13
blinky_ghostcan anybody explain me this error: ERROR syncing /srv/node/device1/accounts/153235/fd9/95a4c310f283c6953cd3b5b043292fd9/95a4c310f283c6953cd3b5b043292fd9.db {'replication_port': 6000, 'zone': 1, 'weight': 100.0, 'ip': '192.168.151.4', 'region': 1, 'port': 6000, 'replication_ip': '192.168.151.4', 'meta': '', 'device': 'device1', 'id': 4}: #012Traceback (most recent call last):#012  File "/usr/lib/python2.6/site-packages/swift/common/db_replica18:16
blinky_ghosttor.py", line 474, in _replicate_object#01218:16
*** swat30 has joined #openstack-swift18:18
zaitcevcheck if rsyncd is up and a/c/o section names match (e.g. no "test_vm=yes" that produces object600018:18
zaitcevsorry can't look closer right now but looks like that mismatch18:18
*** byeager has joined #openstack-swift18:26
*** shri1 has joined #openstack-swift18:30
*** shri1 has quit IRC18:31
*** shri has quit IRC18:34
redbopink starburst are best starburst18:44
blinky_ghostzaitcev: what do you mean "section names match"?18:44
*** fbo_away is now known as fbo18:44
zaitcevI like yellow18:44
redbogross18:44
notmynamered FTW18:45
zaitcevblinky: just look into /var/log/rsyncd.log18:46
Alex_GaynorSwift is now a programming language from Apple.18:46
dmsimardOh no18:46
dmsimardWhy did they do that18:46
*** openstackstatus has quit IRC18:50
zaitcevhttp://thenextweb.com/apple/2014/06/02/apple-announces-swift-new-programming-language-ios/18:50
redboprobably the same reason we ignored everything else already called swift when we named this18:50
*** openstackstatus has joined #openstack-swift18:52
*** ChanServ sets mode: +v openstackstatus18:52
*** pberis has joined #openstack-swift18:53
*** NM has joined #openstack-swift18:54
redbowell.. to be fair we didn't think it was an original name.  but we expected it to be internal forever.18:55
creihtevidently there was another scientific programming language called swift18:55
*** elambert has quit IRC18:57
Thurloatanother quantum -> neutron renaming in order?18:57
zaitcevI expect we wait for Apple to file C&D with Foundation19:01
zaitcevDo nothing until then19:01
notmynameplease do not talk about it online19:02
pandemicsynso when we gonna switch Swift to use Swift19:02
dmsimardlol ^19:03
*** caio has joined #openstack-swift19:04
*** caio is now known as Guest3143719:04
*** Guest31437 has quit IRC19:05
creihtinteresting that they link to the other swift scripting language at the bottom of the page19:07
*** CaioBrentano has joined #openstack-swift19:10
*** openfly has joined #openstack-swift19:14
*** tsg has joined #openstack-swift19:39
*** gyee has quit IRC19:41
*** nsquare has quit IRC19:43
*** pberis has quit IRC19:45
redboclayg: https://github.com/redbo/bertin/blob/master/pickle.go19:58
*** openstackgerrit has quit IRC19:58
*** byeager has quit IRC19:58
*** byeager has joined #openstack-swift19:58
*** byeager has quit IRC19:59
*** byeager has joined #openstack-swift19:59
*** nsquare has joined #openstack-swift20:03
*** openstackgerrit has joined #openstack-swift20:10
chmoueltricky :)20:12
chmouelor clever20:12
chmoueli heard that go is spawning a new thread everytime there is a concurrent access for C wrapped functions20:12
*** esmute has joined #openstack-swift20:13
*** Thurloat has quit IRC20:14
*** thurloat_ has joined #openstack-swift20:14
*** swat30 has quit IRC20:14
*** thurloat_ is now known as thurloat20:14
*** swat30 has joined #openstack-swift20:15
*** gyee has joined #openstack-swift20:15
blinky_ghostzaitcev: it's working now, my mistake creating the rings. I have it working with glance, but If I shutdown 2 swift servers, glance stops working. I have a total of 4 swift servers. Is this expected?20:18
notmynameblinky_ghost: how many replicas are you using?20:18
blinky_ghostnotmyname: 420:18
notmyname4 replicas will require 3 successful responses for quorum. therefore 2 servers down will cause problems20:19
zaitcevblinky_ghost: zones not on servers 1:1 I suspect, but dunno need to see details to answer, sorry20:19
zaitcevwhat, really? I thought quorum was 220:19
blinky_ghostnotmyname: I created like this:  swift-ring-builder account.builder create 18 4 120:19
notmynamezaitcev: quorum is replicas DIV 2 + 120:20
portanteclayg: https://gist.github.com/portante/a393d072615c0862481a20:21
portantethe above is a simple patch to get functional test skips to note why they are skipped20:22
*** wasmum has quit IRC20:22
blinky_ghostnotmyname: I would like some sort of HA, if all 3 nodes go down swift would still be working on the remaining node. Is this possible?20:23
zaitcevRight, I even reviewed it whenwe went to integer, but I fogot, sorry. I thought we needed 2 out of 4 for regions...20:23
ctennisblinky_ghost: you would still be able to read data, just not write data20:24
torgomaticclayg tried to do that at one point but got shot down; I don't remember why20:24
blinky_ghostctennis: Humm, I'll test it out20:25
ctennisalso blinky_ghost, you'd be better off getting rid of raid1 and using 8 disks for swift20:25
ctennisinstead of pairs of 420:25
*** shri has joined #openstack-swift20:28
blinky_ghostctennis: Yes, but this is only for saving some glance images and I have the swift running with other openstack services. If it still reads data it's acceptable to me. thanks i'll do some more tests.20:30
*** blinky_ghost has quit IRC20:30
zaitcevJust use R=3 and then it's classic unambiguous case and only uses 3x disk  space vs 4x20:31
zaitcevunless you have 2 datacenters on 2 continents20:32
zaitcevIMHO20:32
*** miqui has quit IRC20:39
*** CaioBrentano has quit IRC20:41
*** physcx has joined #openstack-swift20:43
torgomaticclayg: http://paste.openstack.org/show/aOpZEtt9IlmsayzUxb4V/20:50
torgomaticlook at the beautiful view ^20:51
*** CaioBrentano has joined #openstack-swift20:53
*** byeager has quit IRC20:56
*** byeager has joined #openstack-swift20:56
*** kenhui has joined #openstack-swift20:59
*** byeager_ has joined #openstack-swift20:59
*** byeager has quit IRC21:02
*** shri1 has joined #openstack-swift21:05
*** shri1 has quit IRC21:05
openstackgerritPeter Portante proposed a change to openstack/swift: Handle func tests of swift cluster that hide /info  https://review.openstack.org/9729721:06
*** shri has quit IRC21:06
*** kenhui has quit IRC21:13
*** kenhui has joined #openstack-swift21:14
*** Midnightmyth has quit IRC21:23
*** kenhui1 has joined #openstack-swift21:25
*** kenhui has quit IRC21:25
creihtzaitcev: http://imimotorsports.com/rentals.php21:46
*** miqui has joined #openstack-swift21:48
notmynamepandemicsyn: swift on swift in swift? and if we implement TCP over avian carrier, we can use swifts for that too21:48
*** byeager_ has quit IRC21:48
creihtin swift truck containers21:48
notmynameof course :-)21:48
notmynamefollowed by suzuki swift cars21:48
*** sileht has quit IRC21:52
*** kenhui has joined #openstack-swift21:55
*** kenhui1 has quit IRC21:59
*** sileht has joined #openstack-swift21:59
*** sileht has quit IRC22:04
*** sileht has joined #openstack-swift22:06
*** fbo is now known as fbo_away22:10
*** kenhui has quit IRC22:15
*** tsg has quit IRC22:20
anticwi see the container/account replicators timing out with the default conn_timeout=0.5s - but the load on the systems isn't that high22:37
anticwi wonder if we're not exceeding the socket backlog?22:37
*** NM has quit IRC22:38
anticwswift/common/wsgi.py defaults to 4096 - i can't imagine that's being over-run though22:39
portanteclayg: https://gist.github.com/portante/a393d072615c0862481a22:52
openstackgerritPete Zaitcev proposed a change to openstack/swift: isolate representation from content in GET request  https://review.openstack.org/9736322:57
openstackgerritPete Zaitcev proposed a change to openstack/swift: isolate object update logic from container PUT  https://review.openstack.org/9736422:58
mattoliverauGood morning all23:01
*** cutforth has quit IRC23:11
openstackgerritClay Gerrard proposed a change to openstack/swift: Update container storage_policy_index when auditing  https://review.openstack.org/9635223:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add functional tests for Storage Policy  https://review.openstack.org/9604223:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Fixes probe tests with non-zero default storage policy  https://review.openstack.org/9635323:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Update swift-container-info to be storage policy aware  https://review.openstack.org/9604323:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index  https://review.openstack.org/9604023:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Accounts  https://review.openstack.org/9604123:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to list_endpoints  https://review.openstack.org/9604623:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/9604723:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9604423:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9604523:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to ssync  https://review.openstack.org/9603423:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Put X-Timestamp in object 404 responses  https://review.openstack.org/9603523:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to the Auditor  https://review.openstack.org/9603223:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add storage policy support for the Replicator  https://review.openstack.org/9603323:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/9603823:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9603923:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/9603623:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/9603723:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support  https://review.openstack.org/9602723:20
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Containers  https://review.openstack.org/9602923:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeRing and FakeLogger  https://review.openstack.org/9602823:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Updates  https://review.openstack.org/9603123:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Server  https://review.openstack.org/9603023:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to the Account Reaper  https://review.openstack.org/9604923:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/9604823:21
claygportante: oh crap i forgot your fuctest updates23:21
mattoliverauclayg: looks like you've been busy :)23:37
*** CaioBrentano has quit IRC23:52
*** diegows has quit IRC23:54
*** matsuhashi has joined #openstack-swift23:59

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