Wednesday, 2017-01-18

*** lespaul has quit IRC00:14
si1verCan swift3 use two auth backends?00:20
si1verI know aws4 requires keystone, and aws2 worked fine with tempauth, so now I am hoping I can use both.00:20
timburkesi1ver: yes, but pipeline ordering requires a bit of thought. as i recall,  you want something like ... swift3 s3token authtoken tempauth keystoneauth ... with delay_auth_decision=true for both s3token and authtoken00:22
timburkeit might be ... swift3 s3token authtoken keystoneauth tempauth ... though -- you'll probably want to experiment a little. maybe both are fine? i forget00:23
si1verthat's pretty close to what I have now. Maybe all I need to do is include both reseller prefixes in the s3token middleware, hopefully.00:24
timburkes3token's reseller prefix should match keystoneauth's. i'm pretty sure you can only give it one?00:25
si1verso s3token is only for keystone then.00:28
timburkeyes. its sole reason for existence is to talk to keystone to validate the signature provided00:29
si1vercan swift3 use s3token and tempauth at the same time.00:34
timburkeyes, provided that you've got a s3token that includes https://review.openstack.org/#/c/326765/ and you've set delay_auth_decision=true00:36
patchbotpatch 326765 - swift3 - Add delay_auth_decision config option (MERGED)00:36
timburke...and we may not have had an official release since that landed... hrmm... :-/00:36
*** sams-gleb has joined #openstack-swift00:37
timburkeyep, only on master: https://github.com/openstack/swift3/commit/ca9d9d000:37
timburkei should probably poke kota_ about that, but i think we may want to get https://review.openstack.org/#/c/406424/ in before a release?00:38
patchbotpatch 406424 - swift3 - Only make one request to Keystone per S3 request00:38
*** sams-gleb has quit IRC00:41
*** JimCheung has quit IRC00:49
si1verdelay auth decision is required to be able to use multiple backends right?00:51
timburkeyes. otherwise, authtoken (& s3token) either reject the request before any other auth middlewares have a chance to respond or ignore the other middlewares' authing00:54
timburkeyou *might* be able to get something like ... swift3 tempauth s3token authtoken keystoneauth ... to work for both through the S3 api, but i'm fairly certain the swift API would only work for keystone users00:55
timburkei really really ought to document what we actually expect to work :-/00:56
si1verI need swift3 to use tempauth for aws2 requests and keystone for aws4 requests.00:57
si1vertempauth would actually be fine for both, but since aws4 requires keystone I am working with that constraint.00:57
si1verI am using swift3 from master, so maybe I have a shot?00:58
si1ver(Probably should pin that....)00:58
timburkeyeah, we should be able to make that work00:58
timburkefwiw, i promise to really really try hard not to break it :-)00:59
si1verHa, sure I'll hold you to that. :p00:59
kota_good morning00:59
si1verspinning up a test env now.00:59
timburkehi kota_!00:59
kota_hi timburke00:59
kota_it looks like swift3 conversation in openstack-swift channel?01:00
timburkeyep. it was too quiet, anyway :-)01:00
kota_looking at the log01:01
kota_done, so we need to bump the version release01:02
kota_nice to have https://review.openstack.org/#/c/406424/01:02
patchbotpatch 406424 - swift3 - Only make one request to Keystone per S3 request01:02
timburkewell, we could, anyway. sounds like that shouldn't really affect si1ver, who's following master01:03
kota_and i got an answer from IBM that we can bump the minimum requirements of swift for swift3 to be newton stable01:03
kota_timburke: ^^01:03
kota_timburke: so i'll push the patch soon01:04
kota_timburke: i'd like to include it too01:04
kota_for the release01:04
timburkesounds good!01:04
*** _JZ_ has quit IRC01:04
*** JimCheung has joined #openstack-swift01:08
*** klamath has joined #openstack-swift01:09
*** jerrygb has quit IRC01:11
*** jerrygb has joined #openstack-swift01:14
*** klamath has quit IRC01:18
si1verok cool, getting both tempauth and keystone working with aws2 only required that delay auth decision directive in the swift3 block.01:20
si1vernow if aws4 still works, I'm all good.01:20
timburkesi1ver: awesome! if v2 works, i totally expect v4 to work as well (at least for keystone)01:21
*** stevemar has quit IRC01:27
*** Raymii has quit IRC01:27
*** stevemar has joined #openstack-swift01:29
*** Raymii has joined #openstack-swift01:29
si1vertimburke: thanks, adding delay_auth_decision to [filter:swift3] and [filter:s3token] did the trick.01:36
timburkeglad to hear it01:36
*** JimCheung has quit IRC01:47
*** clu_ has quit IRC02:00
*** mingyu has joined #openstack-swift02:11
*** sams-gleb has joined #openstack-swift02:39
*** sams-gleb has quit IRC02:44
*** mingyu has quit IRC02:44
*** JimCheung has joined #openstack-swift02:46
*** mingyu has joined #openstack-swift02:50
*** JimCheung has quit IRC02:51
*** NM has joined #openstack-swift02:54
notmynamehello, world02:55
*** mingyu has quit IRC02:57
*** mingyu has joined #openstack-swift02:58
*** mingyu has quit IRC03:00
*** mingyu has joined #openstack-swift03:00
*** mingyu has quit IRC03:01
*** NM has quit IRC03:13
*** tqtran has joined #openstack-swift03:16
*** tqtran has quit IRC03:18
klrmnnotmyname: oh, stop being so melodramatic =)03:22
*** jlwhite has quit IRC03:22
notmynameklrmn: oh am i? I just hadn't actually opened my laptop today03:22
notmynamejust taking some time to catch up03:22
notmynameseeing what new drama is happening on the ML ;-)03:22
klrmnthe 'hello world' all by itself there was looking very … drat, i hate it when my vocabulary runs and hides03:23
notmynamenormally I'd start with "good morning", but I kinda missed that window03:24
klrmnhugokuo: usually says good morning about this time…03:26
hugokuogood...... morning !03:27
jrichlinotmyname: o/  is there a meeting tomorrow?03:30
notmynameyes03:30
jrichliokie dokie03:30
jrichliyou having fun down under?03:31
notmynameyes, definitely. some great serendipitous conversations, good talks, beautiful venue03:31
jrichlinice.  I saw a tweet about a talk from cschwede - retweeted actually, but haven't gotten to watch yet.03:33
jrichliI didn't realize he would be there.  figured it was only you and mattoliverau03:33
notmynameyeah, I think I saw that too. that was an EU conference. not here03:34
jrichliOH. oops :p03:34
*** sheel has joined #openstack-swift03:34
notmynameand mattoliverau is probably the only other person you know here. although, there's quite a few IBM (Oz Labs) people here03:34
jrichlilike the people working on EC lib?03:35
jrichliI think there was one that I have talked to from there who wanted to make some enhancements03:36
notmynameactually, there is someone here I talked to who is working on that. but he hasn't pushed any code yet03:36
notmynamebut yeah, getting libec to run on power803:36
jrichlifirst name starts with a D ... will have to look at my mail03:36
jrichlidja is his handle.  Daniel?03:37
notmynameI don't know his IRC handle. I was just looking for it03:37
jrichligood you got to chat with him03:38
notmynamebut yeah DANIEL AXTENS03:38
notmynameyes, I did. well, briefly03:38
jrichli:-)03:38
notmynamecsmart is now working at rackspace and might be able to start contributing to swift. he's been lurking in here a while03:39
jrichligreat to hear it, csmart :-)03:42
*** links has joined #openstack-swift04:02
*** dmorita_ has quit IRC04:03
*** psachin has joined #openstack-swift04:14
*** jlwhite has joined #openstack-swift04:20
*** dmorita has joined #openstack-swift04:29
*** dmorita has quit IRC04:33
*** sams-gleb has joined #openstack-swift04:41
*** sams-gleb has quit IRC04:46
*** eckesicle has quit IRC04:55
*** manij has joined #openstack-swift04:58
*** ppai has joined #openstack-swift05:03
*** SkyRocknRoll has joined #openstack-swift05:04
openstackgerritJanie Richling proposed openstack/swift: WIP: Symlink support in container-sync  https://review.openstack.org/42166905:08
*** tanee_ has joined #openstack-swift05:10
openstackgerritJanie Richling proposed openstack/swift: WIP: Symlink support in container-sync  https://review.openstack.org/42166905:13
jrichlibtw, speaking of cschwede, I saw that patch 337297 got a +2 : yay!05:21
patchbothttps://review.openstack.org/#/c/337297/ - swift - Add support to increase object ring partition power05:21
openstackgerritKota Tsuyuzaki proposed openstack/swift: Optimize ec duplication and its md5 hashing  https://review.openstack.org/42167305:38
kota_clayg: you may like patch 42167305:39
patchbothttps://review.openstack.org/#/c/421673/ - swift - Optimize ec duplication and its md5 hashing05:39
*** psachin has quit IRC05:44
*** jerrygb has quit IRC05:45
*** jerrygb has joined #openstack-swift05:46
*** psachin has joined #openstack-swift05:49
*** jerrygb has quit IRC05:50
*** mingyu has joined #openstack-swift05:57
*** mingyu has quit IRC06:05
*** tqtran has joined #openstack-swift06:05
*** mingyu has joined #openstack-swift06:11
*** mingyu has quit IRC06:23
*** mingyu has joined #openstack-swift06:24
*** sams-gleb has joined #openstack-swift06:43
*** sams-gleb has quit IRC06:44
*** sams-gleb has joined #openstack-swift06:45
*** mingyu has quit IRC06:46
*** mingyu has joined #openstack-swift06:48
*** klrmn has quit IRC07:00
sanchitmalhotraHi, I am looking for some information on the following scenario for replication.07:08
sanchitmalhotraIs it possible in SWIFT that i replicate the existing data to some other remote location?07:08
sanchitmalhotraOr i have to do this at the time of initial system setup only while definiting the no. of replicas of each object and their device/location?07:08
*** bapalm has quit IRC07:16
*** bapalm has joined #openstack-swift07:18
*** Manish_ has joined #openstack-swift07:19
*** ChubYann has quit IRC07:22
*** mingyu has quit IRC07:22
*** tesseract has joined #openstack-swift07:25
*** tesseract has quit IRC07:25
*** tesseract has joined #openstack-swift07:26
*** dfflanders has quit IRC07:29
*** mingyu has joined #openstack-swift07:30
*** Manish_ has quit IRC07:30
*** mingyu has quit IRC07:32
*** Manish_ has joined #openstack-swift07:43
*** hseipp has joined #openstack-swift07:45
*** tqtran has quit IRC07:47
*** tanee has quit IRC07:51
*** onboard has quit IRC07:52
*** tanee_ is now known as tanee07:52
*** oshritf_ has joined #openstack-swift07:56
*** rledisez has joined #openstack-swift08:10
sanchitmalhotraHi... Can anyone help on the above query related to replication?08:15
*** mingyu has joined #openstack-swift08:23
*** sams-gleb has quit IRC08:26
*** sams-gleb has joined #openstack-swift08:26
*** sams-gleb has quit IRC08:30
*** mingyu has quit IRC08:34
*** SkyRocknRoll has quit IRC08:38
*** silor has joined #openstack-swift08:40
*** mingyu has joined #openstack-swift08:41
*** silor has quit IRC08:44
*** silor1 has joined #openstack-swift08:44
charzsanchitmalhotra: maybe you can setup another remote region and add nodes for the region, replicator will replicate data to that.08:45
charzsanchitmalhotra: if you're asking to rpelicate date to remove server that isn't a part of swift cluster. I think the answer is no, as I know.08:46
charzyou need 3rd party tools to do that.08:47
*** mingyu has quit IRC08:47
*** silor1 is now known as silor08:47
sanchitmalhotracharz: Thank you very much for the response08:47
sanchitmalhotracharz: Can I replicate data to a node which is not a part of swift cluster?08:48
charzfor backup purpose?08:48
sanchitmalhotrayes. as well as a replica site which can be used just in case08:51
charzobject-replicator follow the ring file to check the replicas and move replica to correct places, so if your node isn't a part of cluster (devices don't add to object ring), object-replicator won't do anything for drives.08:51
sanchitmalhotracharz: Ok. This is key information. Thank you very much.08:52
sanchitmalhotraIt means storage node and replication nodes cannot be entirely different08:52
charzmaybe you can consider to setup a global swift cluster.08:53
sanchitmalhotracharz: Okay.... I'll look into it.08:55
sanchitmalhotracharz: To get started, I'll search more information about global swift cluster.08:57
sanchitmalhotracharz: I hope I'll be able to get some more information from you if I get any further query on this topic.08:57
charzsanchitmalhotra: I'm not sure how you defince the "storage" and "replication" node. So maybe you can check swift docs to know each servers.08:58
charzsanchitmalhotra: you can ask question here, I believe developers will happy to answer your quesitons.09:00
sanchitmalhotracharz: Thank you very much :)09:00
*** anurgms has joined #openstack-swift09:01
charzsanchitmalhotra: np09:01
*** mingyu has joined #openstack-swift09:02
*** mingyu_ has joined #openstack-swift09:03
*** mingyu has quit IRC09:03
*** SkyRocknRoll has joined #openstack-swift09:03
*** mingyu_ has quit IRC09:05
*** Shashikant86 has joined #openstack-swift09:16
openstackgerritAnh Tran proposed openstack/swift: API: Correcting status code  https://review.openstack.org/42175909:16
*** dfflanders has joined #openstack-swift09:26
*** mattoliverau has quit IRC09:27
*** matt6434 has joined #openstack-swift09:28
*** Shashikant86 has quit IRC09:35
mathiasbacoles_: it looks like my problem was that I had both tempauth and keystoneauth in the pipeline, which led to the 401 issue for performing a GET on the container, even though everything else seemed to work09:39
*** Shashikant86 has joined #openstack-swift09:40
*** pcaruana has joined #openstack-swift09:41
*** mvk has quit IRC09:45
*** andymccr has joined #openstack-swift09:58
*** asettle has joined #openstack-swift09:58
*** sams-gleb has joined #openstack-swift10:15
*** SkyRocknRoll has quit IRC10:16
*** SkyRocknRoll has joined #openstack-swift10:18
*** mvk has joined #openstack-swift10:21
*** vint_bra has joined #openstack-swift10:24
*** pcaruana has quit IRC10:38
*** vint_bra has quit IRC10:38
*** acoles_ is now known as acoles10:39
acolesmathiasb: glad you found problem, curious though, it should be ok to have both auths as long as they have distinct reseller prefixes.10:40
*** JimCheung has joined #openstack-swift10:40
*** kei_yama has quit IRC10:42
acolessanchitmalhotra: here's a good place to start reading about global clusters http://docs.openstack.org/developer/swift/admin_guide.html#geographically-distributed-swift-considerations10:46
*** tqtran has joined #openstack-swift10:47
*** tqtran has quit IRC10:50
*** _JZ_ has joined #openstack-swift10:54
*** Manish_ has quit IRC10:57
*** NM has joined #openstack-swift11:00
*** Shashikant86 has quit IRC11:00
*** Shashikant86 has joined #openstack-swift11:04
*** dmorita has joined #openstack-swift11:04
*** dfflanders has quit IRC11:05
*** dmorita has quit IRC11:09
*** oshritf has joined #openstack-swift11:28
*** oshritf_ has quit IRC11:29
*** oshritf has quit IRC11:35
*** oshritf has joined #openstack-swift11:35
*** ppai has quit IRC11:36
*** oshritf has quit IRC11:43
*** ganders has joined #openstack-swift11:54
*** pcaruana has joined #openstack-swift11:56
*** geaaru has joined #openstack-swift11:56
csmartnotmyname: thanks :-)12:14
csmartjrichli: \o cheers12:14
*** cdelatte has joined #openstack-swift12:15
csmartjrichli: notmyname daniel axtens (dja) is an ex-colleague of mine12:15
* csmart looks forward to contributing to swift ;-)12:17
*** peterlisak has quit IRC12:18
*** onovy has quit IRC12:18
*** anurgms has quit IRC12:22
*** peterlisak has joined #openstack-swift12:26
*** onovy has joined #openstack-swift12:27
*** Shashikant86 has quit IRC12:28
*** manij has quit IRC12:29
*** NM has quit IRC12:38
*** links has quit IRC12:46
*** sams-gle_ has joined #openstack-swift12:50
*** sams-gleb has quit IRC12:50
*** klamath has joined #openstack-swift12:57
*** klamath has quit IRC12:57
*** klamath has joined #openstack-swift12:57
*** Shashikant86 has joined #openstack-swift12:58
*** jamielennox is now known as jamielennox|away12:59
*** tongli has joined #openstack-swift13:01
*** vint_bra has joined #openstack-swift13:14
*** JimCheung has joined #openstack-swift13:17
*** JimCheung has quit IRC13:17
*** jamielennox|away is now known as jamielennox13:19
*** NM has joined #openstack-swift13:28
*** vint_bra1 has joined #openstack-swift13:32
*** vint_bra has quit IRC13:32
*** vint_bra1 has joined #openstack-swift13:32
*** JimCheung has joined #openstack-swift13:38
*** ganders has quit IRC13:41
*** JimCheung has quit IRC13:42
*** ganders has joined #openstack-swift13:43
*** catintheroof has joined #openstack-swift13:45
*** jerrygb has joined #openstack-swift13:56
*** oshritf has joined #openstack-swift13:58
*** jerrygb has quit IRC13:59
*** jerrygb has joined #openstack-swift14:03
*** jerrygb has quit IRC14:03
*** jerrygb has joined #openstack-swift14:04
*** sams-gle_ has quit IRC14:16
*** sams-gleb has joined #openstack-swift14:17
*** sams-gleb has quit IRC14:21
*** jordanP has joined #openstack-swift14:25
*** NM has quit IRC14:27
*** NM has joined #openstack-swift14:27
*** sams-gleb has joined #openstack-swift14:34
*** tqtran has joined #openstack-swift14:40
*** Shashikant86 has quit IRC14:53
*** links has joined #openstack-swift14:56
*** links has quit IRC14:56
*** Shashikant86 has joined #openstack-swift15:00
*** tongli has quit IRC15:00
*** Shashikant86 has quit IRC15:02
*** NM has quit IRC15:02
*** NM has joined #openstack-swift15:03
*** mingyu has joined #openstack-swift15:03
*** jistr is now known as jistr|mtg15:05
*** openstack has joined #openstack-swift15:19
*** bobby2 has joined #openstack-swift15:19
*** asettle has joined #openstack-swift15:19
*** swifterdarrell has joined #openstack-swift15:20
*** ChanServ sets mode: +v swifterdarrell15:20
*** jlvillal_ is now known as jlvillal15:20
*** jlvillal is now known as Guest8897715:20
*** fungi has joined #openstack-swift15:20
*** BlackDex_ has joined #openstack-swift15:21
*** zacksh has joined #openstack-swift15:22
*** mgagne has joined #openstack-swift15:22
*** ejat has joined #openstack-swift15:22
*** mgagne has quit IRC15:23
*** mgagne has joined #openstack-swift15:23
*** mgagne is now known as Guest5853115:23
BlackDex_Hello there, i wonder if it is possible to link openstack using an external swift-storage/proxy to an openstack deployment, and if this maybe is possible with a juju charm?15:23
*** BlackDex_ is now known as BlackDex15:23
*** DuncanT has joined #openstack-swift15:26
*** briancurtin has joined #openstack-swift15:29
*** klrmn has joined #openstack-swift15:29
*** psachin has quit IRC15:33
*** Shashikant86 has joined #openstack-swift15:33
*** sheel has quit IRC15:37
*** kencjohnston_ has quit IRC15:42
*** kencjohnston has joined #openstack-swift15:43
*** david-lyle has joined #openstack-swift15:47
*** mvk has quit IRC15:48
openstackgerritChristopher Bartz proposed openstack/swift: Exclude containers for account quota  https://review.openstack.org/41423215:49
*** jistr|mtg is now known as jistr15:51
caiobrentano_Hi all15:51
caiobrentano_I'm writing a middleware for proxy-server. How much overload "swift.proxy.controllers.base.get_container_info" does to check a specific custom header?15:52
cbartzcaiobrentano_: In principle it does a container HEAD request. But the information gets cached afterwards.15:57
caiobrentano_cbartz: this HEAD would happen anyway along  the request flow?15:59
*** Jeffrey4l has quit IRC16:01
*** Jeffrey4l_ has joined #openstack-swift16:01
*** Jeffrey4l_ is now known as Jeffrey4l16:02
*** geaaru has quit IRC16:02
caiobrentano_cbartz: I mean, even if I don't call swift.proxy.controllers.base.get_container_info, somewhere in the proxy-server pipeline, a HEAD would be necessary to complete the request?16:02
cbartzcaiobrentano_: I think this depends on what your middleware does.16:03
*** mingyu has quit IRC16:04
caiobrentano_cbartz: I mean in a "default" proxy-server pipeline. For example, if I make a PUT request to create an object, does the proxy-server needs to HEAD the container to complete the request?16:07
cbartzcaiobrentano_: I think so, yes.16:08
tdasilvacaiobrentano_: unless it is cached, i'm pretty sure yes: https://github.com/openstack/swift/blob/master/swift/proxy/controllers/obj.py#L63416:08
*** geaaru has joined #openstack-swift16:09
caiobrentano_cbartz: If it always do a HEAD in order to complete a PUT request, I can assume this "HEAD" operation is always necessary. So, the overload would be minimal16:09
caiobrentano_cbartz: thanks! :)16:10
*** ganders has quit IRC16:10
cbartzcaiobrentano_: np16:10
cbartztdasilva: Hello Thiago. Do you might have time for reviewing patch 408596 ? Its the swiftclient side for the prefix-based tempurls support. Its needing only one c reviewer more. Would be cool to have support on the cli side, too.16:13
patchbothttps://review.openstack.org/#/c/408596/ - python-swiftclient - prefix-based tempurls support16:13
*** SkyRocknRoll has quit IRC16:15
tdasilvacbartz: hi! cool, i will try to review it.16:15
*** zul has quit IRC16:15
cbartztdasilva: Thx16:15
*** zul has joined #openstack-swift16:15
tdasilvacbartz: did you see the idea notmyname added to the ideas page regarding tempurl?16:15
tdasilvalooked interesting too16:16
tdasilvacbartz: https://blueprints.launchpad.net/swift/+spec/human-readable-tempurl-timestamp16:16
cbartztdasilva: Yes, sounds nice. Somebody working on it?16:20
tdasilvacbartz: honestly, i don't know, notmyname or somebody from swiftstack might know better....I don't remember seeing any patches...but I could have easily missed...16:20
*** ganders has joined #openstack-swift16:21
*** Guest88977 is now known as jlvillal16:25
*** ganders has quit IRC16:27
*** vint_bra has joined #openstack-swift16:35
*** chsc has joined #openstack-swift16:35
*** chsc has joined #openstack-swift16:35
*** vint_bra1 has quit IRC16:37
cbartzHey all. If somebody here is using git-lfs and needs a swift binding: On my github account I have published a git-lfs server implementation for swift and a transfer agent for the custom transfer type swift. This allows to upload objects larger > 5 GiB to your swift cluster with git-lfs. More information here: https://github.com/cbartz/git-lfs-swift-server and https://github.com/cbartz/git-lfs-swift-transfer-agent .16:38
*** vint_bra1 has joined #openstack-swift16:42
*** vint_bra has quit IRC16:45
*** sheel has joined #openstack-swift16:48
*** ChubYann has joined #openstack-swift16:57
*** Shashikant86 has quit IRC17:00
*** arch-nemesis has joined #openstack-swift17:01
*** ganders has joined #openstack-swift17:02
*** klrmn has quit IRC17:14
*** jordanP has quit IRC17:15
*** tesseract has quit IRC17:21
*** dmorita has joined #openstack-swift17:34
*** dmorita has quit IRC17:37
*** david-lyle is now known as bailing-wire17:37
*** mvk has joined #openstack-swift17:38
*** catintheroof has quit IRC17:44
*** catintheroof has joined #openstack-swift17:44
*** catintheroof has quit IRC17:44
*** catintheroof has joined #openstack-swift17:45
*** bailing-wire has quit IRC17:46
*** rledisez has quit IRC17:46
*** catintheroof has quit IRC17:50
*** JimCheung has joined #openstack-swift17:52
*** jordanP has joined #openstack-swift17:58
*** jordanP has quit IRC17:58
*** chsc has quit IRC18:01
*** klrmn has joined #openstack-swift18:02
*** chsc has joined #openstack-swift18:12
*** chsc has joined #openstack-swift18:12
*** jerrygb has quit IRC18:23
timburkegood morning18:26
timburkeacoles: mathiasb: you can have both auth systems set up, but you need to make sure (1) authtoken has delay_auth_decision=true and (2) the middlewares are in the correct order. i *think* it goes ... authtoken keystoneauth tempauth ... but i'd trust experimental results more than my memory18:28
*** NM has quit IRC18:33
*** ganders has quit IRC18:34
acolestimburke: morning. thanks, yes now you say it I also recall there an ordering requirement but like you I'm not sure which way works.18:35
*** ganders has joined #openstack-swift18:36
timburkethe big thing i always forget is the delay_auth_decision. really, it should *always* be set to true in a proxy server, but things will mostly still work if you omit it (and thus use the default of false)18:37
timburke...until you add a second auth system, at which point it starts assuming that the (valid) tempauth or swauth tokens should get 401s immediately18:37
openstackgerritAlistair Coles proposed openstack/swift: Add assertion to test_consolidate_hashes_raises_exception  https://review.openstack.org/42215918:39
*** NM has joined #openstack-swift18:43
*** philipw_ has quit IRC18:44
*** acoles is now known as acoles_18:45
*** philipw has joined #openstack-swift18:45
*** jerrygb has joined #openstack-swift19:24
*** caiobrentano_ has quit IRC19:24
*** jerrygb has quit IRC19:29
*** caiobrentano_ has joined #openstack-swift19:30
*** caiobrentano_ has quit IRC19:45
*** ganders has quit IRC19:45
*** caiobrentano_ has joined #openstack-swift19:45
*** jidar has left #openstack-swift19:46
*** caiobrentano_ has quit IRC19:50
*** lespaul has joined #openstack-swift19:52
lespaulHello. I can upload an object to a container via Dashboard however when trying to download the object from the proxy using swift command I get a permission denied error. Any ideas?19:56
*** silor has quit IRC19:57
jrichlilespaul: when running the swift command, are all the necessary OS env vars set?19:57
lespauljrichli: yes, i can even upload an object using swift command. Running swift stat shows the right env19:59
*** bailing-wire has joined #openstack-swift20:00
jrichlilespaul: I assume you are using the same credentials and account for both ... sounds like you'd have to look at logs20:00
lespaulok. also, swift stat still shows the old container name which i have already renamed. I've tried reloading the proxy-server but it persists20:01
jrichliah, so the inconsistent behavior is happening with a newly re-named container?  how much time has passed since the rename?20:02
*** bailing-wire is now known as david-lyle20:02
lespaul10-15 mins. i was thinking it will update eventually..20:03
jrichliare all the services running?20:03
jrichliupdaters and such20:04
lespaulhow long before it updates i don't know. i ran swift-init all restart20:04
jrichlii'd think 10-15 mins would be fine, unless there is some large error on the backend.  no major errors from logs?20:05
*** jerrygb has joined #openstack-swift20:05
jrichlican you download from the dashboard?  does the dashboard reflect the new name?20:08
timburkewhat do we mean by "renamed"? like, "created new container with the correct name, sent COPY requests to copy all data in the old container to the new one, then sent DELETE requests to all of the old object, and finally sent a DELETE request for the old container"?20:09
timburkewas all of this hidden behind an innocent-looking "rename" button in Horizon?20:09
*** klamath has quit IRC20:10
*** jerrygb has quit IRC20:13
lespaultimburke: i renamed the added storage policy in swift.conf, deleted the object-2 builder and ring files on the proxy and storage nodes. i then created a new ring and distributed them.20:27
*** caiobrentano_ has joined #openstack-swift20:31
timburkei... so the *container* wasn't renamed, but the *storage policy* was? was there only the one container with that policy? did the container previously have any objects in it?20:31
timburkehow certain are we that the new storage policy has the same config (replicated vs ec; if ec, the ec_type, ec_num_*_fragments) as the old one, and *only* the name has changed?20:34
*** zaitcev has quit IRC20:40
*** dmorita has joined #openstack-swift20:44
*** JimCheung has quit IRC20:46
*** dmorita has quit IRC20:48
lespaulI think the problem is on the EC storage policy since the default replication policy works fine. I have a storage policy of an EC. If I want to change to a new EC type, do I just change the type in swift.conf then distribute the conf file to the nodes?20:48
*** NM has quit IRC20:49
notmynamegood morning20:52
*** jerrygb has joined #openstack-swift20:53
notmynametdasilva: wrt the human-readable tempurl timestamps, AFAIK there's not currently anyone working on it (but I should check back in the office)20:53
tdasilvacbartz: ^^^20:54
notmynamecbartz: if you're interested in working on it, that would be great :-)20:54
timburkelespaul: once you have data stored in a storage policy, you never want to change the parameters of that policy. the name can change (although we recommend including the old name as an alias so as not to break existing clients that may expect the old name), but the ec_type, number of data/parity fragments, and fragment size have to stay the same or else swift won't know how to read the objects20:55
notmynameonovy: I see you've proposed a few backports. I'll look into those asap20:55
onovynotmyname: thanks!20:56
notmynameonovy: but FWIW, I'm at a conference this week, so my time in front of a computer is somewhat reduced :-)20:56
onovynotmyname: np20:56
onovyi already backported that for Debian package :)20:57
kota_morning20:57
notmynametimburke: you're ready to talk about the api thing in the meeting? or were you needing clayg (IIRC he's sick today?)20:59
*** m_kazuhiro has joined #openstack-swift20:59
notmynamemeeting time in #opestack-meeting21:00
timburkenotmyname: sure. should make it easier to get something landed :P21:00
notmynamekk21:00
lespaultimburke: if i understand correctly, if i want to use a new ec type i will need to create a new storage policy in swift conf, create a new builder/ring then distribute to the nodes. is that correct?21:01
timburkelespaul: yes. storage policies are an append-only sort of a deal21:03
lespaulthanks for the clarification21:04
*** acoles_ is now known as acoles21:06
*** caiobrentano_ has quit IRC21:07
*** dmorita has joined #openstack-swift21:17
*** zaitcev has joined #openstack-swift21:22
*** ChanServ sets mode: +v zaitcev21:22
*** zul has quit IRC21:25
*** JimCheung has joined #openstack-swift21:26
*** matt6434 is now known as mattoliverau21:26
*** jamielennox is now known as jamielennox|away21:26
*** ChanServ sets mode: +v mattoliverau21:27
mattoliveraumorning21:27
*** zul has joined #openstack-swift21:28
*** jerrygb_ has joined #openstack-swift21:30
zaitcevtdasilva: thanks for the mail. Imagine that, I updated Fedora, rebooted, and didn't start VPN at once... only got the mail now!21:32
tdasilvazaitcev: :)21:32
*** jerrygb has quit IRC21:33
*** Jeffrey4l has quit IRC21:35
* tdasilva wonders if this page would be helpful at all: http://breakingapis.org/21:35
*** Jeffrey4l has joined #openstack-swift21:35
*** dmorita has quit IRC21:38
*** dmorita has joined #openstack-swift21:38
notmynametdasilva: interesting21:40
*** dmorita has quit IRC21:41
*** dmorita has joined #openstack-swift21:43
*** vint_bra1 has quit IRC21:49
*** acoles is now known as acoles_21:50
*** sams-gleb has quit IRC21:50
*** sams-gleb has joined #openstack-swift21:51
*** sams-gleb has quit IRC21:55
*** m_kazuhiro has quit IRC21:57
openstackgerritKota Tsuyuzaki proposed openstack/swift: Optimize ec duplication and its md5 hashing  https://review.openstack.org/42167322:04
openstackgerritTim Burke proposed openstack/swift: Make test_get_more_nodes_with_zero_weight_region more robust  https://review.openstack.org/41808222:04
timburkei'm still annoyed at all the 412s we send when we mean 400, but clayg tells me we can't ever fix those, either :-/22:08
*** jamielennox|away is now known as jamielennox22:10
*** geaaru has quit IRC22:15
*** jamielennox is now known as jamielennox|away22:24
*** NM has joined #openstack-swift22:31
*** david-lyle has quit IRC22:32
*** david-lyle has joined #openstack-swift22:40
*** Bashta has joined #openstack-swift22:46
BashtaHi there22:46
*** _JZ_ has quit IRC22:50
Bashtahey was wondering if someone has already deplyed a vapor serverver with a remote mongodb db?22:57
*** Bashta has quit IRC23:04
*** JimCheung has quit IRC23:21
*** Jeffrey4l has quit IRC23:24
*** sheel has quit IRC23:24
*** fungi has quit IRC23:24
*** etienneme has quit IRC23:24
*** furlongm_ has quit IRC23:24
*** tanee has quit IRC23:24
*** stevemar has quit IRC23:24
*** Raymii has quit IRC23:24
*** Jeffrey4l has joined #openstack-swift23:24
*** sheel has joined #openstack-swift23:24
*** fungi has joined #openstack-swift23:24
*** etienneme has joined #openstack-swift23:24
*** furlongm_ has joined #openstack-swift23:24
*** tanee has joined #openstack-swift23:24
*** stevemar has joined #openstack-swift23:24
*** Raymii has joined #openstack-swift23:24
*** Bashta has joined #openstack-swift23:25
*** bobby2 has quit IRC23:27
*** bobby2 has joined #openstack-swift23:27
*** Jeffrey4l has quit IRC23:29
*** kei_yama has joined #openstack-swift23:30
*** chsc has quit IRC23:32
*** JimCheung has joined #openstack-swift23:37
*** StevenK_ is now known as StevenK23:40
*** Jeffrey4l has joined #openstack-swift23:41
*** JimCheung has quit IRC23:42
*** jerrygb_ has quit IRC23:42
*** Jeffrey4l has quit IRC23:42
*** Jeffrey4l has joined #openstack-swift23:42
*** NM has quit IRC23:45
*** jerrygb has joined #openstack-swift23:48
*** cdelatte has quit IRC23:59

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