Monday, 2016-09-19

*** tsg has quit IRC00:14
*** tsg has joined #openstack-swift00:14
*** ChanServ sets mode: +v jrichli00:30
openstackgerritMerged openstack/swift: Updating Bandit config file  https://review.openstack.org/36506500:33
*** nadeem has quit IRC00:36
*** vint_bra has joined #openstack-swift00:41
*** vint_bra has joined #openstack-swift00:50
*** nadeem has joined #openstack-swift01:10
*** nadeem has quit IRC01:15
*** sgundur_ has joined #openstack-swift01:34
*** sgundur_ has quit IRC01:38
*** zhengyin has joined #openstack-swift01:44
zhengyingood moring01:44
zhengyinmorning01:45
charzmorning01:56
*** fguillot is now known as fguillot_afk02:24
*** fguillot_afk has quit IRC02:26
*** frekoya_ has joined #openstack-swift02:27
zhengyincharz:morning02:28
*** frekoya_ has quit IRC02:30
mattoliverauzhengyin, charz: morning02:37
*** mingyu has quit IRC02:38
*** janonymous has joined #openstack-swift02:57
*** vint_bra has quit IRC02:57
zhengyinmattoliverau:morning02:58
*** SkyRocknRoll has joined #openstack-swift03:21
*** SkyRocknRoll has quit IRC03:26
*** SkyRocknRoll has joined #openstack-swift03:43
*** mingyu has joined #openstack-swift03:53
*** klrmn has quit IRC03:54
*** mingyu has quit IRC03:57
MooingLemur"mattoliverau:morning" looks like a user:group specification you'd pass to chown04:13
*** psachin_ has joined #openstack-swift04:32
*** ppai has joined #openstack-swift04:37
*** tsg has quit IRC04:59
*** pcaruana has quit IRC05:05
*** ChanServ sets mode: +v cschwede05:26
*** mingyu has joined #openstack-swift05:39
*** ChubYann has quit IRC05:40
*** mingyu has quit IRC05:43
timburkecnf: it's auth-system dependent. assuming keystone, there's an ec2-credential that can be created that will provide your access/secret keys05:50
timburketry `openstack ec2 credentials create --help`05:50
mattoliverauMooingLemur: isn't it nice that zhengyin decided to use my irc nick as his Linux username and must also be a morning person to have a groupname of morning :P05:51
mattoliverautimburke: your not asleep or weekending very well :P05:51
*** rcernin has joined #openstack-swift06:03
*** pcaruana has joined #openstack-swift06:17
*** hseipp has joined #openstack-swift06:42
*** rledisez has joined #openstack-swift07:17
*** oshritf has joined #openstack-swift07:18
*** oshritf_ has joined #openstack-swift07:18
janonymousnotmyname: Hi, i guess you were right when you said we can rethink about adding bandit to gate. Now i realize that.If you say i could remove it or if we choose to go with it then also it is great, but only thing that bothers me is it's maintainance..07:29
*** geaaru has joined #openstack-swift07:32
*** sams-gleb has joined #openstack-swift07:49
*** sams-gleb has quit IRC07:49
*** amitkqed has quit IRC07:53
*** amitkqed has joined #openstack-swift07:54
*** tsg has joined #openstack-swift07:55
openstackgerritMatthew Oliver proposed openstack/swift: Add process level concurrency to container sync  https://review.openstack.org/21009907:59
mattoliverau^^ Just a rebase, probe tests had diverged a little since it was last updated so had to do a bit on manual conflict merging. But probe tests now pass, so I think is all good :) Now to continue reviewing it :)08:00
*** kong has quit IRC08:01
acolesmattoliverau: thanks for rebasing that ^^ I had just noticed the -1 from Jenkins08:05
*** joeljwright has joined #openstack-swift08:06
*** ChanServ sets mode: +v joeljwright08:06
*** treyd has quit IRC08:12
*** tanee has quit IRC08:13
*** hugokuo has quit IRC08:13
*** kencjohnston has quit IRC08:13
*** clarkb has quit IRC08:13
*** portante has quit IRC08:13
*** treyd has joined #openstack-swift08:14
*** hugokuo has joined #openstack-swift08:14
*** sams-gleb has joined #openstack-swift08:14
*** tanee has joined #openstack-swift08:14
*** portante has joined #openstack-swift08:14
*** kencjohnston has joined #openstack-swift08:14
*** clarkb has joined #openstack-swift08:15
*** sgundur1 has joined #openstack-swift08:17
openstackgerritAlistair Coles proposed openstack/swift: api-ref: Move repeated paragraph to an include file  https://review.openstack.org/36747108:21
acolesmattoliverau: torgomatic: you had +2's on that ^^ but it fell into merge conflict, now fixed.08:23
cnftimburke thanks!08:29
cnf(no idea how long ago you responded ^^;08:29
openstackgerritAlistair Coles proposed openstack/swift: api-ref: fix some header definitions  https://review.openstack.org/36623208:29
acolescschwede: I will merge your patch 366569 into this ^^08:33
patchbothttps://review.openstack.org/#/c/366569/ - swift - api-ref: fix more header definitions08:33
*** asettle has joined #openstack-swift08:34
openstackgerritAlistair Coles proposed openstack/swift: api-ref: fix some header definitions  https://review.openstack.org/36623208:42
acolescschwede: ^^ rebased and with your change squashed in08:44
acolesdonagh: you had a +2 on previous version of that ^^08:44
openstackgerritAlistair Coles proposed openstack/swift: api-ref: clean up account listing examples  https://review.openstack.org/36621108:46
*** silor has joined #openstack-swift09:26
*** silor1 has joined #openstack-swift09:28
*** silor has quit IRC09:30
*** silor1 is now known as silor09:30
*** swifterdarrell has quit IRC09:42
*** swifterdarrell has joined #openstack-swift09:44
*** ChanServ sets mode: +v swifterdarrell09:44
*** kong has joined #openstack-swift09:49
*** a1|away has quit IRC09:55
*** pdardeau has quit IRC09:56
*** pdardeau has joined #openstack-swift09:56
*** hoonetorg has quit IRC09:56
*** a1|away has joined #openstack-swift09:56
*** gopenshaw has quit IRC09:57
*** hoonetorg has joined #openstack-swift09:57
*** gopenshaw has joined #openstack-swift09:58
*** mvk has quit IRC10:02
*** openstackstatus has quit IRC10:28
*** mvk has joined #openstack-swift10:39
*** yarkot1 has quit IRC11:00
*** mmotiani has quit IRC11:00
*** mmotiani_ is now known as mmotiani11:00
*** mmotiani_ has joined #openstack-swift11:01
*** mmotiani_ has quit IRC11:02
*** mmotiani_ has joined #openstack-swift11:03
*** mmotiani has quit IRC11:04
*** ntata has quit IRC11:04
*** smurke has quit IRC11:04
*** sgundur1 has quit IRC11:04
*** yarkot has quit IRC11:04
*** mmotiani_ is now known as mmotiani11:04
openstackgerritMerged openstack/swift: api-ref: Move repeated paragraph to an include file  https://review.openstack.org/36747111:04
*** mmotiani_ has joined #openstack-swift11:09
*** zul has joined #openstack-swift11:13
*** ntata has joined #openstack-swift11:14
*** yarkot has joined #openstack-swift11:20
*** yarkot1 has joined #openstack-swift11:20
*** hoonetorg has quit IRC11:23
*** tsg has quit IRC11:25
*** manous has joined #openstack-swift11:31
*** manous has quit IRC11:40
*** sams-gleb has quit IRC11:42
*** sams-gleb has joined #openstack-swift11:42
*** hoonetorg has joined #openstack-swift11:56
*** hoonetorg has quit IRC11:57
*** hoonetorg has joined #openstack-swift11:58
*** oshritf has quit IRC11:58
*** oshritf_ has quit IRC11:58
*** oshritf_ has joined #openstack-swift11:58
*** oshritf has joined #openstack-swift11:58
*** porunov has joined #openstack-swift12:03
porunovHello. How to configure proxy servers to use identity v3? Right now I am using tempauth for authentication. I use identity v1 (curl -v -H 'X-Auth-User: admin:admin' -H 'X-Auth-Key: admin' http://192.168.0.58:8080/auth/v1.0/). Is it possible to configure servers to use tempauth with v3 or v2 identity? This doesn't work: curl -H "Content-Type: application/json" -X POST -d '{"auth" : {"passwordCredentials" : {"username" : "admin","password" : "admin"},"12:04
porunovtenantName" : "admin"}}' http://192.168.0.58:8080/auth/v2.0/12:04
*** manous has joined #openstack-swift12:18
*** vint_bra has joined #openstack-swift12:22
*** tsg has joined #openstack-swift12:28
*** fguillot has joined #openstack-swift12:34
*** david-lyle has joined #openstack-swift12:38
*** david-lyle has quit IRC12:43
*** tsg has quit IRC12:45
*** fguillot is now known as fguillot_afk12:47
*** fguillot_afk has quit IRC12:48
*** fguillot has joined #openstack-swift12:52
*** tsg has joined #openstack-swift12:54
acolesporunov: docs to use keystone with swift are here might you be able to spare me some time to chat about your experience/tips for working remotely for barefoot? I am nowhere near any decision but thinking I should get myself informed.13:02
*** manous has quit IRC13:02
acolesporunov: http://docs.openstack.org/developer/swift/overview_auth.html#keystone-auth13:02
acolestempauth does not use v2 or v3 identity API13:02
*** tsg has quit IRC13:05
acolesporunov: with keystone you need to get a token from keystone service by passing credentials and then pass the token to swift, you do not send your id credentials to swift.13:06
acolesporunov: the swiftclient cli does this under the hood for v2 and v3 api (i.e. makes a request to keytone for token, then to swift). If you use swift CLI with the --debug option you will see the equivalent curl commands in the debug output13:07
*** asettle has quit IRC13:08
*** asettle has joined #openstack-swift13:09
*** manous has joined #openstack-swift13:10
*** fguillot is now known as fguillot_afk13:17
*** vint_bra has quit IRC13:23
*** vint_bra has joined #openstack-swift13:27
openstackgerritOndřej Nový proposed openstack/swift: Fixed cut and pasted paragraph from commit message in manpage  https://review.openstack.org/37193213:34
*** kong has quit IRC13:41
onovyacoles: thanks13:43
acolesonovy: np13:44
*** tsg has joined #openstack-swift13:46
porunovacoles: Could you explain me how how all requests are managed by proxy when we use keystone? I am not sure that I understand how keystone works. After client have received a token from keystone he have to put it in each request to work with openstack. But as I read about keystone it saves all tokens in a local database. So, if I want to put an object into swift then a client sends request to a proxy server to store an object and the proxy server13:47
porunovsends a request to the keystone server to check a token (each time for each request?). As I understand the performance can suffer if we have some latency between proxy and keystone servers. Am I wrong? I realy don't understand how all requests are managed by proxy servers when we use keystone. Sincerely13:47
*** vint_bra has quit IRC13:48
*** tsg_ has joined #openstack-swift13:50
*** vint_bra has joined #openstack-swift13:50
onovyi think tokens are cached in memcached on proxy servers13:50
onovyin swauth they are :)13:50
*** tsg has quit IRC13:50
acolesporunov: swift uses two pieces of middleware to support keystone - the authtoken middleware (which is part of the keystoneauth project so not in the swift repo) and kesytoneauth middleware (which is specific to swift). authtoken receives the token in client request and validates it with the keystone service, and also caches the token validation result for 5 mins (default time) http://docs.openstack.org/developer/keystonem13:52
acolesiddleware/middlewarearchitecture.html13:52
acoles http://docs.openstack.org/developer/keystonemiddleware/middlewarearchitecture.html13:52
acolesporunov: for a validated token, authtoken populates the request env with identity info (like user name, project etc) which keystoneauth then uses to authorise the request (or not)13:53
porunovacoles: Thank you very much. It is really great. Do you know how to change the time for cache from 5 mins to 60 mins?14:00
*** vint_bra has quit IRC14:01
porunovacoles: I found, thanks. token_cache_time )14:02
acolesporunov: according to this doc http://docs.openstack.org/developer/keystonemiddleware/middlewarearchitecture.html set the option 'token_cache_time = 3600' in the filter:authtoken section of proxy-server.conf14:02
acolesporunov: yep, that :)14:02
*** vint_bra has joined #openstack-swift14:04
acolesporunov: btw I noticed there is a bug in the doc I linked to you for swift config with keystone https://bugs.launchpad.net/swift/+bug/160467414:05
openstackLaunchpad bug 1604674 in OpenStack Object Storage (swift) "Doc error in Auth Overview for specifying keystone domain " [Undecided,New]14:05
*** oshritf has quit IRC14:06
*** oshritf_ has quit IRC14:06
acolesporunov: if you follow the openstack install guide, and create a keystone domain with name 'default' for your services, then the correct config for authtoken is as shown here: http://docs.openstack.org/mitaka/install-guide-ubuntu/swift-controller-install.html14:07
acolesporunov: historically the domain had id=default but now it is name=default.should patch the swift docs.14:07
* acoles should patch the swift docs14:08
*** tsg_ has quit IRC14:15
*** asettle has quit IRC14:15
*** asettle has joined #openstack-swift14:16
*** tongli has joined #openstack-swift14:16
*** sgundur has joined #openstack-swift14:19
*** sgundur_ has joined #openstack-swift14:19
*** tsg_ has joined #openstack-swift14:21
*** manous has quit IRC14:22
porunovacoles: Thank you very much for help =)14:31
*** sams-gleb has quit IRC14:33
*** manous has joined #openstack-swift14:36
*** openstackgerrit has quit IRC14:37
*** openstackgerrit has joined #openstack-swift14:37
*** SkyRocknRoll has quit IRC14:38
*** david-lyle has joined #openstack-swift14:40
*** david-lyle has quit IRC14:45
*** tsg_ has quit IRC14:50
*** manous has quit IRC14:51
*** manous has joined #openstack-swift14:55
*** juzuluag has joined #openstack-swift14:56
*** manous has quit IRC15:00
*** manous has joined #openstack-swift15:01
*** manous has quit IRC15:05
*** pcaruana has quit IRC15:07
*** ppai has quit IRC15:13
*** psachin_ has quit IRC15:18
*** manous has joined #openstack-swift15:18
*** oshritf has joined #openstack-swift15:18
*** oshritf_ has joined #openstack-swift15:19
openstackgerritAlistair Coles proposed openstack/swift: Update authtoken domain options  https://review.openstack.org/37257315:20
*** manous has quit IRC15:23
*** klrmn has joined #openstack-swift15:25
*** klrmn has quit IRC15:27
*** sgundur_ has quit IRC15:27
*** rcernin has quit IRC15:30
acolesnotmyname: might be worth trying to include that fix ^^ in the next release15:30
*** david-lyle has joined #openstack-swift15:32
*** manous has joined #openstack-swift15:36
*** manous has quit IRC15:41
*** Renich has joined #openstack-swift15:42
Renichhey guys15:43
*** manous has joined #openstack-swift15:43
RenichI am having these issues: https://paste.fedoraproject.org/431042/42998001/15:43
RenichAny idea what could be the cause?15:43
RenichIt is a 2-node Keystone + Swift installation15:44
RenichThe storage uses ZFS15:44
Renichjust 1 replica15:44
*** Jeffrey4l_ has left #openstack-swift15:46
*** sgundur_ has joined #openstack-swift15:46
*** sgundur_ has quit IRC15:49
*** manous has quit IRC15:55
*** sgundur_ has joined #openstack-swift15:55
*** oshritf has quit IRC15:56
*** oshritf_ has quit IRC15:56
*** tsg_ has joined #openstack-swift15:57
openstackgerritMahati Chamarthy proposed openstack/swift: Delete old tombstones  https://review.openstack.org/34686515:57
*** zaitcev has joined #openstack-swift15:59
*** ChanServ sets mode: +v zaitcev15:59
*** porunov has quit IRC16:01
*** arch-nemesis has joined #openstack-swift16:06
*** manous has joined #openstack-swift16:07
*** dmorita has joined #openstack-swift16:30
*** sgundur_ has quit IRC16:30
*** dmorita has quit IRC16:32
*** dmorita has joined #openstack-swift16:32
timburkegood morning16:33
Renicho/16:34
openstackgerritMerged openstack/swift: Turn on F812 check  https://review.openstack.org/37179916:35
*** sgundur_ has joined #openstack-swift16:40
timburkeRenich: is your object-server at 10.0.64.191:6000/1 running? it looks like you're getting timeout from the proxy-server trying to connect to it16:40
timburkealso, are you running with only one replica? that will drastically reduce your durability guarantees16:41
Renichtimburke: I think it is. The service is up. You mean swift-object.service, right?16:41
*** rledisez has quit IRC16:41
*** nadeem has joined #openstack-swift16:42
Renichtimburke: I've had the server lock up. I had to delete all the .lock files and restart the services to make it work again16:43
*** markstur_ is now known as markstur16:44
Renichtimburke: my boss is betting on ZFS's deduplication, compression and RAIDZ capabilities16:45
Renichtimburke: the use case involves a single dude uploading weather data from a satelite, and multimple readers16:46
timburkeyep, swift-object.service sounds right. from the proxy server, if you try `curl http://10.0.64.191:6000/` does the server respond?16:46
Renichtimburke: I've warned them about the RAID warning. They say it's irrelevant in our case16:46
Renichtimburke: Invalid path: /16:47
Renichit does16:47
timburkehurrah!16:47
Renich;=)16:47
timburkethen why did it time out... :-/16:47
zaitcevbecause it took too much time to complete the operation :-)16:47
Renichtimburke: I think it's related to ZFS in some way. What if I have low IOPs or something?16:47
Renichzaitcev: heh... yeah16:48
RenichThe dude is putting up to 1.4M files in a container16:48
Renichcould that have something to do?16:48
zaitcevThat, too, isn't going to help matters when proxy is doing get_info.16:48
*** ChubYann has joined #openstack-swift16:49
zaitcevThe good news is, all timeouts are configurable.16:49
Renichzaitcev: yeah, I've been mangling with them16:49
Renichup to 30s in some cases16:49
zaitcevI'd cry and headdesk if I were a few years younger but by the age of 50 I learned not to give shit about mistakes of the architects and people like Renich have to make right.16:50
zaitcevs/and people/that people/16:50
*** rcernin has joined #openstack-swift16:51
zaitcevI once read memoir of a famous tank designers, who created T-72B amoing other things. He described how he's been tasked with the start-up warmer for T-55. It was kinda this situation... The chief designed just handwaved it and said we'll have someone design a warmer, no problem.16:52
*** Suyi_ has joined #openstack-swift16:53
zaitcevI think the problem we're hearing about is very similar to what Gluster people did, e.g. R=1 etc.16:53
*** mvk has quit IRC16:55
zaitcevYou still have to put big containers on SSD though, I think. Otherwise timeouts alone aren't fixing it.16:55
*** mmotiani has quit IRC16:57
*** yarkot1 has quit IRC16:57
*** mmotiani_ is now known as mmotiani16:57
*** hseipp has quit IRC16:58
MooingLemurwhy is handoffs_first undesirable in normal cluster operation?16:58
*** mmotiani_ has joined #openstack-swift16:59
openstackgerritMerged openstack/swift: remove comment saying we ignore H233. we actually check it  https://review.openstack.org/37179016:59
openstackgerritMerged openstack/swift: DRY out probe.common  https://review.openstack.org/37032117:00
*** mmotiani_ has quit IRC17:00
Renichzaitcev: LOL, I hear ya! Well, ZFS has some cache drives. 8 SSDs so it captures writes fast enough. Given the info is being sent throught the Internet, these should, at least, help a bit on getting them fast into the cache, then, putting them, slowly, into the spinning drives17:00
Renichwe're talking about  ~900 TB here17:01
Renichon each server17:01
zaitcevOkay, just make sure you aren't flushing container data with object data.17:02
Renichzaitcev: what do you mean? Like mixing the concepts or putting everything on magnetics?17:03
zaitcevContainer needs to be on SSD so that SQLite can look up and update large indexes in a reasonable amount of time. If you keep files that back container DBs and your object files in the same cache, objects can easily crowd container out of the "cache".17:04
zaitcev(subject to many assumptions about how all this works)17:05
*** klrmn has joined #openstack-swift17:06
*** oshritf_ has joined #openstack-swift17:07
Renichzaitcev: OK, so metadata on the DBs have to live there. I might be able to do something to keep them in the cache17:07
*** oshritf has joined #openstack-swift17:07
Renichs@have@has@17:07
*** zul has quit IRC17:07
Renichzaitcev: the "containers" directory contains those, right?17:08
zaitcevRenich: yes. The file(1) should be able to confirm, I'd expect.17:09
*** oshritf_ has quit IRC17:09
*** oshritf has quit IRC17:09
Renichzaitcev: This is awesome, thanks a lot man. I think this will solve our issues17:10
*** geaaru has quit IRC17:11
*** asettle has quit IRC17:16
*** asettle has joined #openstack-swift17:22
MooingLemurRenich: I tried ZFS as storage, even with zil and l2arc, the iops were substantially amplified compared to something like ext4 with dm-cache, and the ZFS storage nodes were constantly at much higher iowaits than the ext4 ones.17:24
zaitcev[root@rhev-a24c-02 ~]# file /srv/node/b3/containers/197670/08f/c109ae48211709dd500ef97638af308f/c109ae48211709dd500ef97638af308f.db17:24
*** joeljwright has left #openstack-swift17:24
zaitcev /srv/node/b3/containers/197670/08f/c109ae48211709dd500ef97638af308f/c109ae48211709dd500ef97638af308f.db: SQLite 3.x database17:24
jaakkosMooingLemur: was that a raidz system17:24
MooingLemurnope, single disk per pool17:25
jaakkosoh17:25
zaitcevMooingLemur: how do you mange to use ext4? We at RH used to support ext4 as first class citizen for Swift, but gave up when it turned out that its maximum metadata size was too small.17:25
MooingLemurSSDs sliced up to have a log dev and a cache dev per pool17:25
MooingLemurzaitcev: really?  What is that maximum size?  I stopped using xfs because of the kernel not handling failed disks gracefully and spamming printks until reboot even after umount -fl on the bad mount so that no more filesystem accesses were happening17:27
MooingLemurGranted, this was 4 years ago on early 3.x kernels, but still.17:28
zaitcevMooingLemur: I think it was 64 KB. Note, that was in chunks of something like 1k? IIRC. Swift since removed chunking, so I cannot imagine it working at all.17:28
MooingLemurI mean, I made the inodes larger than default so most xattrs would fit inside the inode17:28
*** zul has joined #openstack-swift17:29
MooingLemurWell, this is news to me17:32
MooingLemurext4's limit for the entire set of keys and values on a file is apparently the block size of the filesystem (4k in my case)17:33
MooingLemurbut I don't think we've run into this17:33
*** sgundur_ has quit IRC17:34
*** tqtran has joined #openstack-swift17:36
*** sgundur_ has joined #openstack-swift17:38
MooingLemurzaitcev: appears the removal of chunking supposedly improved storage efficiency on ext4 (since there were fewer keys, more value can be stored), but otherwise there's no change.  I don't think we've ever had the issue of xattrs exceeding 4k here.17:42
*** asettle has quit IRC17:43
MooingLemurbut yeah, ext4 wasn't chosen because of performance, it was roughly equivalent to xfs, but xfs was disfavored because of how the kernel handled disappearing disks.17:44
MooingLemurWe started our cluster on pretty shoddy hardware, so that kinda colored the design choices :)17:44
*** mvk has joined #openstack-swift17:45
openstackgerritCharles Hsu proposed openstack/python-swiftclient: Add additional headers for DELETE requests.  https://review.openstack.org/37265617:47
*** arch-nemesis has quit IRC17:47
*** acoles is now known as acoles_17:50
*** oshritf has joined #openstack-swift17:54
*** oshritf_ has joined #openstack-swift17:54
*** oshritf has quit IRC17:55
*** oshritf_ has quit IRC17:55
*** oshritf has joined #openstack-swift17:56
*** oshritf_ has joined #openstack-swift17:56
RenichMooingLemur: reading...17:56
RenichMooingLemur: I was about to get into the SSD slicing17:57
*** manous has quit IRC18:14
*** tsg_ has quit IRC18:16
openstackgerritMerged openstack/swift: Bring "egregious range request" comment in line with reality  https://review.openstack.org/36906018:20
*** juzuluag has quit IRC18:23
*** manous has joined #openstack-swift18:27
*** sams-gleb has joined #openstack-swift18:41
*** sams-gleb has quit IRC18:42
*** asettle has joined #openstack-swift18:43
*** chsc has joined #openstack-swift18:47
*** asettle has quit IRC18:49
*** oshritf_ has quit IRC18:57
*** oshritf has quit IRC18:57
*** silor has quit IRC19:02
*** manous has quit IRC19:04
*** oshritf has joined #openstack-swift19:15
*** oshritf_ has joined #openstack-swift19:15
*** manous has joined #openstack-swift19:16
*** McMurlock1 has joined #openstack-swift19:16
openstackgerritThiago da Silva proposed openstack/swift: add policy info to swift-get-nodes  https://review.openstack.org/37271619:19
*** oshritf has quit IRC19:22
*** oshritf_ has quit IRC19:22
*** oshritf has joined #openstack-swift19:23
*** oshritf_ has joined #openstack-swift19:23
*** manous has quit IRC19:23
*** sgundur_ has quit IRC19:26
*** sgundur_ has joined #openstack-swift19:30
*** sgundur_ has quit IRC19:34
*** sgundur_ has joined #openstack-swift19:35
*** manous has joined #openstack-swift19:37
*** McMurlock1 has quit IRC19:37
*** manous has quit IRC19:41
*** asettle has joined #openstack-swift19:45
*** manous has joined #openstack-swift19:46
tqtranquestion: if i submitted a patch that tempest is failing on, do i submit an independent patch to tempest with a depends-on tag? or is there a different process?19:47
*** asettle has quit IRC19:50
*** asettle has joined #openstack-swift19:59
timburketqtran: generally, it depends on whether it's a consistent or intermittent failure20:00
*** sgundur_ has quit IRC20:03
*** nikivi has joined #openstack-swift20:09
tqtranits consistent, im getting it everytime.20:10
tqtranif i patch tempest, it will fail because the swift code isnt in. if i patch swift, tempest fails. i'll dig around the logs a bit more to make sure. but worse case, how do i patch both without one failing since they are co-dependent?20:12
timburkei take it we're talking https://review.openstack.org/#/c/356715/ ? does this mean that the old acl format doesn't work with that patch?20:17
patchbotpatch 356715 - swift - Supporting Account ACL in keystoneauth20:17
*** asettle has quit IRC20:19
timburkei don't think this is a problem with tempest. it *is* a sign that swift's func tests need to be more thorough. apparently we're getting a traceback like http://paste.openstack.org/show/581228/ during a /info request20:20
openstackgerritoshritf proposed openstack/swift: Add process level concurrency to container sync  https://review.openstack.org/21009920:21
timburkeposted some comments to help you along20:23
tqtranhm i see, thanks for the comments timburke20:24
*** sgundur_ has joined #openstack-swift20:24
timburkenp, happy to help!20:24
*** janonymous has quit IRC20:28
*** nikivi has quit IRC20:32
*** oshritf has quit IRC20:35
*** oshritf_ has quit IRC20:35
*** asettle has joined #openstack-swift20:38
*** asettle has quit IRC20:43
*** janonymous has joined #openstack-swift20:55
*** kong has joined #openstack-swift21:17
*** sgundur_ has quit IRC21:18
openstackgerritMerged openstack/python-swiftclient: Update help text around container ACL syntax  https://review.openstack.org/32473921:24
*** Renich has quit IRC21:31
*** vint_bra has quit IRC21:32
*** Renich has joined #openstack-swift21:32
*** Renich has quit IRC21:38
*** zul has quit IRC21:38
*** zul has joined #openstack-swift21:43
*** asettle has joined #openstack-swift21:44
*** asettle has quit IRC21:48
*** zul has quit IRC21:50
*** janonymous has quit IRC21:51
*** nadeem has quit IRC21:51
*** kencjohnston has quit IRC21:51
*** tdasilva has quit IRC21:51
*** bkeller` has quit IRC21:51
*** blair has quit IRC21:51
*** jaakkos has quit IRC21:51
*** kencjohnston has joined #openstack-swift21:51
*** bkeller` has joined #openstack-swift21:51
*** janonymous has joined #openstack-swift21:52
mattoliverauMorning21:57
openstackgerritTim Burke proposed openstack/swift: Expose encryption status in GET/HEAD/PUT/POST responses  https://review.openstack.org/34860322:00
openstackgerritTim Burke proposed openstack/swift: Expose encryption status to client  https://review.openstack.org/34860422:00
openstackgerritTim Burke proposed openstack/swift: Include object sysmeta in POST responses  https://review.openstack.org/35755922:00
*** tdasilva has joined #openstack-swift22:06
openstackgerritMerged openstack/swift: api-ref: clean up account listing examples  https://review.openstack.org/36621122:10
*** nadeem has joined #openstack-swift22:13
*** jaakkos has joined #openstack-swift22:16
*** rcernin has quit IRC22:27
openstackgerritTim Burke proposed openstack/swift: Make diskfile verification easier to reason about  https://review.openstack.org/37279922:36
*** nadeem has quit IRC22:37
*** blair has joined #openstack-swift22:41
*** asettle has joined #openstack-swift22:45
openstackgerritTim Burke proposed openstack/swift: Clean up api-ref examples  https://review.openstack.org/37184022:49
*** asettle has quit IRC22:51
openstackgerritTim Burke proposed openstack/swift: Expose encryption status in GET/HEAD/PUT/POST responses  https://review.openstack.org/34860322:56
openstackgerritTim Burke proposed openstack/swift: Expose encryption status to client  https://review.openstack.org/34860422:56
*** janonymous has quit IRC22:58
*** fguillot has joined #openstack-swift23:12
*** tgtanya has joined #openstack-swift23:14
*** chsc has quit IRC23:36
openstackgerritPete Zaitcev proposed openstack/swift: Add a configurable URL base to staticweb  https://review.openstack.org/37280923:37
*** openstackgerrit has quit IRC23:42
*** gopenshaw has quit IRC23:43
*** kei_yama has joined #openstack-swift23:44
*** gopenshaw has joined #openstack-swift23:45
*** Suyi_ has quit IRC23:45
*** asettle has joined #openstack-swift23:47
*** openstackgerrit has joined #openstack-swift23:47
*** asettle has quit IRC23:51
*** openstackgerrit has quit IRC23:51
*** zaitcev has quit IRC23:52
*** torgomatic_ has quit IRC23:52
*** torgomatic has joined #openstack-swift23:52
*** ChanServ sets mode: +v torgomatic23:52
*** zaitcev has joined #openstack-swift23:52
*** ChanServ sets mode: +v zaitcev23:52
*** hogepodge has quit IRC23:53
*** openstackgerrit has joined #openstack-swift23:55
*** hogepodge has joined #openstack-swift23:56

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