Tuesday, 2016-11-29

*** klrmn has joined #openstack-swift00:03
*** catintheroof has joined #openstack-swift00:08
*** arch-nemesis has quit IRC00:19
kota_good morning00:53
kota_MoiingLemur, notmyname: if you are starting fromclean deployment, i don't think you need to hack the code, probably you mass up your SSDs into a region and assign other HDDs to other regions to simulate the handoff pool.01:14
kota_MooingLemur:^^ (sorry, typo)01:15
*** mmotiani_ has joined #openstack-swift01:17
claygkota_: good evening!01:18
kota_clayg: welcome back :D01:18
claygkota_: so... no movement on isa_l_rs_cauchy?01:19
MooingLemurkota_: that would require that the SSDs have a weight other than zero, correct?  I suppose 0.1 would work :P01:19
*** m_kazuhiro has joined #openstack-swift01:19
kota_clayg: i think nothing progressed after you add +2, i'm thinking of poking tsg- in this week.01:19
kota_MooingLemur: ah, you doesn't want to keep anything in SSD, hmm...01:20
MooingLemurand even if write_affinity is set to the ssd pool, there's no guarantee that they'd appear early enough in the handoff list to be chosen.01:21
kota_yeah, if no weight to the ssd handoff pool, the read would not head for them until the handoff are replicated into primaries.01:23
kota_current read affinity is just sorting in primaries.01:23
kota_AFAIK01:23
kota_clayg: and during waiting review, I'm dougting of why i didn't make base code for isa-l and instead of most of duplicated code from isa-l-vand.01:25
*** mmotiani_ has quit IRC01:28
MooingLemurkota_: perhaps a sane way of hacking it is to have a config option for dedicated handoff zone number, configured in tandem with write_affinity in each region.  All this does is simply sort the handoff list so that these appear as the first handoffs, ahead of everything else.  Or perhaps 2*n replicas of them by default.01:29
MooingLemurfor example in a 2 region (1 hdd and 1 ssd zone each) setup, region 1's proxies will see a primary list of r1z1, r2z1, r2z1, and then a handoff list of r1z2, r1z2, r1z2, followed by the rest of the normal handoffs01:32
kota_MooingLemur: r1 is for ssd right?01:33
MooingLemurr1z1 and r2z1 for hdd, r1z2 and r2z2 for ssd01:33
kota_k, zone each setup01:34
kota_gotcha, it could be.01:34
MooingLemurbut now we've got the possibility of incoherency of handoffs between regions for the read01:34
MooingLemurbecause I'd want r2z2 to be the first three handoffs on the r2 proxies01:35
*** klrmn has quit IRC01:36
kota_it sounds to work reasonable, if i can raise up another perspective, the write affinity depends on the proxy setting, so if we have proxies for each region, one may prefer r1 but the other may prefer r2 and it may be hard to know actually the object placed which region's ssds.01:37
kota_if we can assume looking up local region's ssd always, that may not be aproblem01:38
MooingLemurI think you're thinking about my most recent concern.  request_node_count is usually set to 2 * replicas, but if you read from a different region, you don't know where the handoffs are01:39
kota_MooingLemur: yeah, just thinking of you have same idea with me.01:39
MooingLemurThat may not be a severe problem as long as a primary is available.01:40
MooingLemurBut the idea is the handoffs will revert to primaries within a few minutes at most.01:40
MooingLemurso in practice it may not be a problem.01:40
kota_yes, the handoff should be propageted to primaries at least in the local region.01:41
*** clu_ has quit IRC01:54
*** klrmn has joined #openstack-swift02:07
openstackgerritMerged openstack/swift: Drop "--allow-insecure netifaces" from tox pip install  https://review.openstack.org/40199402:14
*** catintheroof has quit IRC02:16
*** catintheroof has joined #openstack-swift02:16
*** catintheroof has quit IRC02:20
charzmorning02:37
*** henryn has joined #openstack-swift02:38
*** nikivi has quit IRC02:40
*** bkopilov has quit IRC03:02
*** tqtran has quit IRC03:02
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Gather up common isa_l function to isa_l.c file  https://review.openstack.org/40399603:05
kota_charz: morning03:05
kota_clayg: if you have time, could you please check also https://review.openstack.org/403996? That may be more clean implementaion for isa-l cauchy than my older patch https://review.openstack.org/#/c/393263/03:07
patchbotpatch 403996 - liberasurecode - Gather up common isa_l function to isa_l.c file03:07
patchbotpatch 393263 - liberasurecode - ISA-L Cauchy support03:07
*** links has joined #openstack-swift03:10
*** links has quit IRC03:10
*** catintheroof has joined #openstack-swift03:25
charzkota_: o/03:34
*** Jeffrey4l has quit IRC03:54
*** Jeffrey4l has joined #openstack-swift03:55
*** ChubYann has quit IRC03:58
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Gather up common isa_l function to isa_l_common.c file  https://review.openstack.org/40399604:07
*** m_kazuhiro has quit IRC04:09
*** psachin has joined #openstack-swift04:09
*** ChubYann has joined #openstack-swift04:13
*** klrmn has quit IRC04:14
*** ppai has joined #openstack-swift04:15
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: Add soft warning log line when using liberasurecode <1.3.1  https://review.openstack.org/39874404:23
*** catinthe_ has joined #openstack-swift04:23
*** catintheroof has quit IRC04:26
*** catinthe_ has quit IRC04:26
*** catintheroof has joined #openstack-swift04:27
*** catintheroof has quit IRC04:27
*** dmorita has quit IRC04:34
*** bkopilov has joined #openstack-swift04:35
*** m_kazuhiro has joined #openstack-swift04:40
*** kei_yama has quit IRC05:18
*** kei_yama has joined #openstack-swift05:19
openstackgerritMerged openstack/pyeclib: Add soft warning log line when using liberasurecode <1.3.1  https://review.openstack.org/39874405:41
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: PyECLib 1.3.2  https://review.openstack.org/39875205:48
*** Jeffrey4l has quit IRC06:12
*** Jeffrey4l has joined #openstack-swift06:12
*** McMurlock1 has joined #openstack-swift06:30
*** dmorita has joined #openstack-swift06:34
*** dmorita has quit IRC06:39
*** SkyRocknRoll has joined #openstack-swift06:43
*** SkyRocknRoll has quit IRC06:50
*** sams-gleb has joined #openstack-swift06:54
*** sams-gleb has joined #openstack-swift06:55
*** tqtran has joined #openstack-swift07:01
*** SkyRocknRoll has joined #openstack-swift07:04
*** tqtran has quit IRC07:06
*** franklin25 has joined #openstack-swift07:09
notmynamefranklin25: did you have a question about cors?07:17
franklin25yes, I'm having a problem uploading files to a container07:20
notmynamefranklin25: I've always found cors to be rather ... confusing. but I'll try to help, if I can07:20
franklin25Thanks!07:21
*** pcaruana has joined #openstack-swift07:21
*** ChubYann has quit IRC07:21
notmynamewhat's not working the way you expected?07:22
franklin25I'm sorry though, but the developper who can generatte the problem is not yet present. and clearly skype finds it a good idea to clear chatlogs, so the error message is gone07:22
franklin25I could describe it to you, but I think I'd better give you exact error messages07:22
franklin25if it's allright with you I'd like to come back to this in I expect an hour or so07:22
notmynamefranklin25: it's pretty late for me (~11:30pm). I was about to go to bed. I saw your question in #openstack and hoped I could help, but I won't be here an hour from now07:23
franklin25ah, in that case I'll try to describe it best I can07:24
franklin25then trying to upload a file to a container we are getting an error in the preflight about 'allowed-credentials'07:25
franklin25I found the allow-credentials boolean in the keystone settings, which fixed q si,ilqr error07:25
franklin25s/si,ilqr/similar/07:26
franklin25sorry, typing on a strange keyboard07:26
notmyname:-)07:26
franklin25anyway, the first error was on a call to port 5000 which I identified as the keystone07:27
franklin25now we are getting a similar error on port 8080 which I identified as the proxy07:27
notmynameok07:27
franklin25correct settings have eluded me till now07:28
franklin25I am terribly sorry. seems like my boss needs me. This is an orphaned project -.- if you know anything, please feel free to post here I'll read it and test it. but have to go now07:29
notmynamefranklin25: for online info, I'd point you to http://docs.openstack.org/developer/swift/cors.html07:29
notmynamewhich I'm sure you've already seen07:29
*** takashi has joined #openstack-swift07:30
notmynamefranklin25: however, if there's more later, feel free to ask again in here. if I'm not around, there are people here from all sorts of timezones. perhaps someone else can help. I'll be back online tomorrow, myself07:30
mahatic_notmyname: o/ hope you had good thanksgiving celebrations07:36
notmynamemahatic_: thanks. I did :-)07:36
mahatic_nice07:37
*** m_kazuhiro has quit IRC07:42
*** hseipp has joined #openstack-swift07:43
franklin25notmyname: thanks! I'll follow it up when the developper arrived08:06
*** rledisez has joined #openstack-swift08:13
*** cbartz has joined #openstack-swift08:17
*** oshritf has joined #openstack-swift08:24
*** amoralej|off is now known as amoralej08:33
*** hseipp has quit IRC08:33
*** geaaru has joined #openstack-swift08:36
*** cbartz has left #openstack-swift08:38
*** rcernin has joined #openstack-swift08:56
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add more test for test_byteswapped_serialization  https://review.openstack.org/40409609:05
*** mvk has quit IRC09:13
openstackgerritChristian Schwede proposed openstack/swift: Fix non-deterministic suffix updates in hashes.pkl  https://review.openstack.org/40232409:18
franklin25while using cors to upload a file to a container, the preflight spits out following error message: XMLHttpRequest cannot load http://domain:8080/v1/AUTH_0aaa3028afff4b8fbadddc0372b2e38a/container1/objectName. Response to preflight request doesn't pass access control check: Credentials flag is 'true', but the 'Access-Control-Allow-Credentials' header is ''. It must be 'true' to allow credentials. Origin 'http://192.168.42.09:24
franklin25port 8080 is used by the swift proxy, but I am unable to find any documentation concerning the Access-Control-Allow-Credentials for the proxy or any other swift module. In the keystone it has been enabled09:25
franklin25I have tried adding "allow_credentials = true" to the cors block in swift-proxy.conf, but this did not give any positive results after restarting the swift-proxy09:26
*** onovy has quit IRC09:32
*** peterlisak has quit IRC09:33
*** onovy has joined #openstack-swift09:38
*** peterlisak has joined #openstack-swift09:38
*** 17WAANPQN has joined #openstack-swift09:43
*** mvk has joined #openstack-swift09:46
*** openstackgerrit has quit IRC09:48
*** openstackgerrit has joined #openstack-swift09:49
*** nexusz99 has joined #openstack-swift09:57
*** abalfour has quit IRC10:00
*** abalfour has joined #openstack-swift10:01
*** kei_yama has quit IRC10:10
*** sams-gleb has quit IRC10:48
*** sams-gleb has joined #openstack-swift10:48
*** acoles_ is now known as acoles10:50
*** sams-gleb has quit IRC10:53
*** tqtran has joined #openstack-swift11:03
*** sams-gleb has joined #openstack-swift11:05
*** takashi has quit IRC11:05
*** tqtran has quit IRC11:07
*** mvk has quit IRC11:08
openstackgerritMathias Bjoerkqvist proposed openstack/swift: Storing encryption root secret in Barbican  https://review.openstack.org/36487811:16
*** mvk has joined #openstack-swift11:20
*** psachin has quit IRC11:32
*** psachin has joined #openstack-swift11:35
*** nexusz99_ has joined #openstack-swift11:44
*** nexusz99 has quit IRC11:47
*** vint_bra has joined #openstack-swift12:01
*** nikivi has joined #openstack-swift12:12
*** bkopilov has quit IRC12:17
*** SkyRocknRoll has quit IRC12:27
*** catinthe_ has joined #openstack-swift12:37
*** xionchen_ has joined #openstack-swift12:41
*** npf has joined #openstack-swift12:49
*** vint_bra has quit IRC12:56
*** vint_bra has joined #openstack-swift12:58
*** vint_bra has quit IRC12:59
*** vint_bra has joined #openstack-swift13:07
*** amoralej is now known as amoralej|lunch13:08
*** ppai has quit IRC14:06
*** Worry has joined #openstack-swift14:09
franklin25I have to go. I'll probably revisit somewhere this week to pickup this problem again14:10
*** franklin25 has quit IRC14:10
*** zul has quit IRC14:18
*** daemontool has joined #openstack-swift14:19
*** amoralej|lunch is now known as amoralej14:23
*** ChanServ sets mode: +v tdasilva14:28
*** bkopilov has joined #openstack-swift14:42
*** NeverWorry has joined #openstack-swift14:42
*** Worry has quit IRC14:42
*** sams-gleb has quit IRC14:47
*** sams-gleb has joined #openstack-swift14:47
*** sams-gleb has quit IRC14:52
*** NeverWorry has quit IRC14:54
*** acoles is now known as acoles_15:04
*** tqtran has joined #openstack-swift15:05
*** sams-gleb has joined #openstack-swift15:09
*** tqtran has quit IRC15:09
*** Jeffrey4l has quit IRC15:09
*** chlong has joined #openstack-swift15:27
*** npf has quit IRC15:34
*** dmorita has joined #openstack-swift15:36
*** zul has joined #openstack-swift15:38
*** dmorita has quit IRC15:40
*** psachin has quit IRC15:40
*** klamath has joined #openstack-swift15:41
*** stradling has joined #openstack-swift15:43
*** Jeffrey4l has joined #openstack-swift15:44
*** stradling has quit IRC15:44
*** klamath has quit IRC15:45
*** mmotiani_ has joined #openstack-swift15:50
*** Jeffrey4l has quit IRC15:51
*** Jeffrey4l has joined #openstack-swift15:51
*** bkopilov_ has joined #openstack-swift15:56
*** bkopilov has quit IRC15:58
*** mmotiani_ has quit IRC15:58
*** madorn has quit IRC15:59
*** acoles_ is now known as acoles16:02
*** rcernin has quit IRC16:03
*** jlvillal has joined #openstack-swift16:03
jlvillalfoo,^]16:04
patchbotError: Spurious "]".  You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands.16:04
jlvillalnotmyname: ^^^  Not sure why patchbot does that.16:04
notmynamejlvillal: yeah. that. if I knew exactly why, I'd make it stop. it comes down to supybot config.16:05
notmynamego home patchbot. you're drunk16:05
jlvillalnotmyname: Okay thanks :)16:05
notmynamejlvillal: someday, I want to rewrite patchbot to be much much simpler and single-purpose16:06
*** chlong has quit IRC16:07
*** StraubTW has joined #openstack-swift16:08
*** winggundamth_ has joined #openstack-swift16:15
*** winggundamth_ has quit IRC16:18
*** chlong has joined #openstack-swift16:20
*** nikivi has quit IRC16:20
*** mmotiani_ has joined #openstack-swift16:25
*** pcaruana has quit IRC16:36
*** mvk has quit IRC16:36
*** dmorita has joined #openstack-swift16:37
*** dmorita has quit IRC16:38
*** dmorita has joined #openstack-swift16:38
*** klrmn has joined #openstack-swift16:45
*** dmorita has quit IRC17:01
*** dmorita has joined #openstack-swift17:01
*** xionchen_ has quit IRC17:04
*** dmorita has quit IRC17:07
*** asettle has quit IRC17:08
*** chlong has quit IRC17:10
openstackgerritDrew Balfour proposed openstack/swift: add byteorder information and logic to ring files  https://review.openstack.org/39523717:12
*** dmorita has joined #openstack-swift17:15
*** dmorita has quit IRC17:16
*** dmorita has joined #openstack-swift17:23
*** chlong has joined #openstack-swift17:23
*** rledisez has quit IRC17:28
*** diogogmt has joined #openstack-swift17:31
*** dmorita has quit IRC17:33
*** dmorita has joined #openstack-swift17:36
*** McMurlock1 has quit IRC17:38
*** daemontool has quit IRC17:39
*** mvk has joined #openstack-swift17:50
timburkenotmyname: franklin25: i think we'd need to add support for the Access-Control-Allow-Credentials header somewhere around https://github.com/openstack/swift/blob/2.11.0/swift/proxy/controllers/base.py#L20017:55
timburkesee https://www.w3.org/TR/cors/#access-control-allow-credentials-response-header -- is there any reason we'd ever want that to be anything but "true"?17:56
*** 17WAANPQN has quit IRC17:57
timburke(i'm also curious about what the client is doing that it interprets as "including credentials". i mean, sure, there's x-auth-token, but what browser knows about that being auth-related? from the description, i would expect it to only be a problem for client-side certs or Cookie/Authorization headers...)17:59
*** asettle has joined #openstack-swift18:01
*** arch-nemesis has joined #openstack-swift18:12
*** zul has quit IRC18:13
zaitcevit's for cookies18:20
zaitcevhas no effect on Swift18:20
*** _JZ_ has joined #openstack-swift18:21
*** zul has joined #openstack-swift18:21
zaitcev(in case of CORS-ed resource that a browser preflights)18:22
timburkezaitcev: except his XMLHttpRequest seemed to want to send cookies, i guess? and failed rather than just, y'know, not sending them18:22
zaitcevyes, but we ignore those, don't we18:23
zaitcevoh18:23
zaitcevOh, brother.18:24
zaitcevSo even Vary is not enough then (well, that one is for caching proxies)18:24
*** acoles is now known as acoles_18:31
henrynjoin18:33
patchbotError: You don't have the admin capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified.18:33
henrynI installed SAIO but now want to create a production environment for Swift. Any reco for good tutorials? The proc doc from OpenStack seems daunting to follow.18:36
*** henryn has quit IRC18:43
*** dmorita has quit IRC18:44
*** dmorita has joined #openstack-swift18:44
*** dmorita has quit IRC18:44
*** dmorita has joined #openstack-swift18:44
*** henryn has joined #openstack-swift18:50
*** silor has joined #openstack-swift18:50
*** dmorita has quit IRC18:52
notmynamegood morning18:52
*** dmorita has joined #openstack-swift18:52
*** dmorita has quit IRC18:52
notmynamehenryn: I'd recommend https://smile.amazon.com/OpenStack-Swift-Administering-Developing-Storage/dp/1491900822/ref=sr_1_118:53
*** dmorita has joined #openstack-swift18:53
*** tqtran has joined #openstack-swift18:54
*** mmotiani_ has quit IRC18:55
claygkota_: lgtm!18:57
*** geaaru has quit IRC18:59
*** clu_ has joined #openstack-swift19:04
henrynnotmyname: Thanks. I'm aware of the book from the SwiftStack site. Haven't ordered it yet but definitely will.19:10
zaitcevhenryn: Joe's book is quite good, specifically for the practical hints. But you can also follow one of the guides rooted here: https://github.com/openstack/swift/blob/master/doc/source/howto_installmultinode.rst19:11
henrynzaitcev: Thank you, I haven't seen that yet. The abundance of information out there is overwhelming and it's tedious to sift through most of them to find the good ones.19:21
*** amoralej is now known as amoralej|off19:21
openstackgerritClay Gerrard proposed openstack/pyeclib: ISA-L Cauchy support  https://review.openstack.org/39327619:27
openstackgerritMerged openstack/pyeclib: Add greedy test for decode/reconstruct result solid  https://review.openstack.org/39365619:27
*** mmotiani_ has joined #openstack-swift19:27
openstackgerritMerged openstack/pyeclib: Assorted combinatoric-test fixes  https://review.openstack.org/39864819:28
*** karenc has joined #openstack-swift19:31
zaitcevhenryn: Might as well select at random, I think. It all comes down to: 1) plan the nodes - storage and proxy, 2) implement the plan by building rings, modifying configs to match, and adding anything that's missing like memcached and rsync, 3) start the servers and daemons, 4) watch logs for errors, fix up19:35
*** silor has quit IRC19:36
claygtimburke: i'm looking at some unmerged cleanups and fixed for pyeclib that you worked on - i'm rebasing them on some other changed of kota's you +2'd that I merged19:42
timburkeclayg: sounds good. i noticed the +2, followed quickly by the fact that it couldn't merge. i was going to rebase myself, but if you'd rather, that's less work for me :)19:46
*** hseipp has joined #openstack-swift19:46
*** ChubYann has joined #openstack-swift19:50
jrichlitimburke, joeljwright, acoles, tdasilva: would you agree with my most recent post to bug 120455819:53
openstackbug 1204558 in python-swiftclient "Upload on container with write ACL reports errors" [Medium,Confirmed] https://launchpad.net/bugs/1204558 - Assigned to Peter Tran (pete-tran02)19:53
openstackgerritClay Gerrard proposed openstack/pyeclib: Fix formatted get_metadata memory leak  https://review.openstack.org/38518519:58
tdasilvajrichli: lol, i don't remember writing that patch19:59
timburkejrichli: i think the error is coming from the object HEAD around https://github.com/openstack/python-swiftclient/blob/3.2.0/swiftclient/service.py#L1846 -- we do this in an attempt to cleanup segments when overwriting. you can pass in a --leave-segments option to avoid it, and then (iirc) the upload succeeds with only a warning about being unable to create the container20:00
openstackgerritClay Gerrard proposed openstack/pyeclib: PyECLib 1.3.2  https://review.openstack.org/39875220:03
openstackgerritClay Gerrard proposed openstack/pyeclib: Use Py_BuildValue instead of manually building dicts  https://review.openstack.org/39585620:03
openstackgerritMerged openstack/pyeclib: Fix formatted get_metadata memory leak  https://review.openstack.org/38518520:04
jrichlitimburke: yes, we have had a customer that was confused by having the warning about the 403, but not having a confirmation of the upload succeeding.20:07
jrichlitimburke: so I was looking for confirmation that we have done all we could do, really, with it being a warning now.20:08
jrichliif we consider this bug resolved, it would be good to close it.  the customer referenced that bug as if it was an outstanding issue to fix.20:11
timburkeyeah, i'm not entirely happy about the LBYL approach, but the alternative seems to be to spin up a bunch of upload jobs which will all fail, attempt to create the container, then retry. so instead of one wasted request, we get like 20 :-(20:13
timburkei guess it's resolved? i think it's been left open because nobody likes the current situation but neither has anyone come up with workable solution20:13
timburkelook at clayg go, merging C code left and right!20:21
openstackgerritMerged openstack/liberasurecode: Fix posix_memalign handling  https://review.openstack.org/34070120:21
claygtimburke: no sense leaving a bunch of good code in gerrit if we're going to do a release!20:24
claygalso isn't the get_metadata leak thing critical?20:24
clayger.. rather *wasn't* it - because the fix is merged now!  pyeclib 1.3.2 is going to be the best pyeclib evar!20:25
timburkeclayg: idk about "critical"... it came up because i was thinking about calling it rather regularly in the auditor, then kota_ pointed out why it would be a terrible idea at the time :P20:31
*** nexusz99_ has quit IRC20:32
jrichlitimburke: btw, I don't think that the line you referenced is not involved in the particular test case I am looking at.  I am focused on the situation in test_shell.test_upload_with_read_write_access20:33
*** catinthe_ has quit IRC20:35
*** diogogmt has quit IRC20:40
*** diogogmt has joined #openstack-swift20:42
timburkejrichli: ah, ok. the bug report seemed to be talking about how the upload will actually fail if it can't read the container20:44
*** dmorita has quit IRC20:44
*** dmorita has joined #openstack-swift20:45
timburkethat test seems a little screwy though; it looks like we mock out two 403s (one for the container, one for the object), then only expect the message for the container to be displayed? or am i not reading that right?20:45
jrichliall I know is that I think I am reproducing the situation in the bug - and in the test - where I grant read and write access to a user for the objects in container, but not to container itself20:47
jrichliI think in the past, it was a container HEAD that would fail, but now it is the actual container create because we dont bother doing the HEAD first20:48
timburkeright20:48
*** dmorita has quit IRC20:50
jrichliand I do only see one error.  I will have to look at the test again to see this object mock.  must be for something that isn't called?  or its not asserted?20:50
jrichlii mean i only see one error when i test by hand20:51
zaitcev"I had a setup with < 10 parts and a dark suffix stuck " - OMG20:52
timburkejrichli: i think i must be mis-reading the test. the asserted behavior definitely matches what i'd expect given the test name; i must not quite be remembering what those 403s are doing for fake_http_connection20:52
timburkei wonder if it'd be worth adding a --skip-container-creation flag or something...20:53
jrichlithat would at least give us a way of replying to the problem report :-)  could maybe add that suggestion in the warning, too, to help out immediately20:55
jrichliI could take a stab at it.  it's a good way to get my feet wet in swiftclient ;-)20:56
jrichlibut then, if you know to add the flag, you'd probably know to ignore the warning20:57
timburkeoooh... and we could add a suggestion around https://github.com/openstack/python-swiftclient/blob/3.2.0/swiftclient/shell.py#L1111 to tack on a --leave-segments on 403s...20:58
timburkeyeah, but this gives them something immediately actionable to shut up the warning20:59
*** hseipp has quit IRC21:00
jrichliso, i didnt follow the thing about the cleaning of segments being an issue.  wouldnt that only apply to SLO?  I thought this was an error b/c we try to create the cont before the PUT.21:00
jrichliand it looks like the test uses --leave-segments, right?21:01
jrichliit'd be nice if there was a way to know that you have the weird acl thing going on : like a flag that says i only have acl to objs21:02
*** sams-gleb has quit IRC21:02
*** sams-gleb has joined #openstack-swift21:03
jrichlitimburke: oh, i see now.  if the test did not use that leave-segments flag, there would be more errors.  and I see its purpose now.21:05
*** sams-gleb has quit IRC21:08
*** dmorita has joined #openstack-swift21:28
mattoliverauMorning21:31
notmynamemattoliverau: I guess it's the time change, but it seems like you're getting online earlier now :-)21:32
notmynamebut yeah, we're only 5 hours apart now21:33
*** catintheroof has joined #openstack-swift21:34
mattoliveraunotmyname: yeah, day light savings here. So it 8:30am atm :)21:35
*** Jeffrey4l has quit IRC21:35
notmynameI've got a few widgets on my computer for major cities near swift devs ;-)21:35
MooingLemur18 hours away from me21:35
mattoliveraunotmyname: ahh, nice21:35
tdasilvanotmyname: heh, i do the same21:36
mattoliverauMooingLemur: but that also makes it 6 hours right21:36
MooingLemuryup21:36
tdasilvaMooingLemur: where are you based?21:36
MooingLemurPhoenix21:36
jrichlimorning, mattoliverau :-)21:37
*** catintheroof has quit IRC21:38
mattoliveraujrichli: o/21:39
*** mmotiani_ has quit IRC21:43
*** diogogmt has quit IRC21:46
*** Jeffrey4l has joined #openstack-swift21:47
*** catintheroof has joined #openstack-swift21:47
*** nikivi has joined #openstack-swift21:59
*** isotope has joined #openstack-swift22:01
isotopeI have swift working in my openstack22:03
isotopeand can create containers, upload files etc...22:03
isotopehowever that only works for the admin user22:03
isotopeWhat tool should I use to give other projects the ability to create containers?22:04
isotopeI am using keystone for authentication22:05
notmynameisotope: you could have created the admin user and added a swift entry for it (right?)22:08
notmynames/could/would22:08
isotopeI created the swift user22:10
isotopeand added the admin role to it22:10
notmynamethat's the same process you'd use for the other users. create them in keystone, give them the right role so they can use swift, and that's it. the user gets a token and uses it to talk to swift22:11
*** diogogmt has joined #openstack-swift22:12
*** chlong has quit IRC22:12
notmynameand you can choose if you assign every keystone user to the same account in swift or if you use different accounts22:12
isotope@noymyname if I have an existing tenant is that the same as the "user"22:21
notmynameyes22:22
isotopehmmm, okay I see now22:23
isotopeI have a tenant but not a role for that account22:23
openstackgerritMerged openstack/swift: breaking up functional/tests.py a bit further  https://review.openstack.org/40104722:24
notmynameisotope: "Account" is, unfortunately, and overloaded term22:28
notmynamein swift, an account is where you put stuff. like a bank account. it may or may not be authorized for one or more users22:28
isotopeyeah, I have a tenant defined and but no user in keystone associated with the account22:29
isotopeso some how I have to create a user and associte it with both the swift user and the tenant22:29
notmynamewait. I thought tenant and user were the same thing22:30
isotopewhen I do a openstack tenant list22:30
isotopeI see the project22:30
isotopewhen I do openstack user list I don't see that project22:30
notmynameok. keystone tenant == swift account.22:31
*** rcernin has joined #openstack-swift22:31
notmynamethe keystone user uses creds to get a token that is authorized for the tenant (swift account), based on their roles22:32
notmyname...and a partridge in a pear tree22:32
isotopeHa22:32
notmynameso create a user in keystone, and add a swift endpoint to it (in its service catalog). I think that's what needs to be done22:33
isotopeokay so I already had an keystone tenent22:33
* notmyname is in fact setting up a new dev environment where keystone can be used22:34
mattoliverauisotope: you shouhld have a swift role (like swiftoperators) which is defined in keystone and supplied to swift proxy.conf, any user you give that role will have access to swift, there account will be based of the tenent their in.22:37
mattoliveraureally there swift account will be <reseller_prefix>_<tenent_id>  which is what you should set in your swift endpoint in keystone.22:39
mattoliverauor more exact your swift endpoint in keystone should have internal/public urls that are in the form: 'http://1.2.3.4:8080/v1/KEY_$(tenant_id)s' where 'KEY_' is my reseller prefix defined in swift proxy config.22:43
mattoliverauat least that's how it's set up on my test env. noting this is running an older keystone server.22:43
*** klrmn has quit IRC22:44
isotopeyup, thats how I have my endpoints set up22:45
*** dmorita has quit IRC22:47
mattoliverauisotope: nice, so if you just make users apart of the swift role (you've defined in keystone and told swift about) then they should be able to access swift.22:48
openstackgerritClay Gerrard proposed openstack/pyeclib: WIP: cleanup lint errors  https://review.openstack.org/40445722:48
claygkota_: timburke: notmyname: tdasilva: how do we get a pep8 job on patch 40445722:49
patchbothttps://review.openstack.org/#/c/404457/ - pyeclib - WIP: cleanup lint errors22:49
timburkeclayg: good call. presumably some changes to project-config22:50
notmynameI'm looking22:53
claygtimburke: there's a pep8 section in the tox.ini?22:53
claygnotmyname: timburke: my bad - yeah the job is already configured; just the tox is running the wrong args/command22:54
claygi can fix that i think - question redacted22:54
openstackgerritClay Gerrard proposed openstack/pyeclib: WIP: cleanup lint errors  https://review.openstack.org/40445722:56
*** dmorita has joined #openstack-swift23:00
*** dmorita has quit IRC23:00
*** rcernin has quit IRC23:01
*** diogogmt has quit IRC23:01
*** StraubTW has quit IRC23:02
*** klrmn has joined #openstack-swift23:02
*** dmorita has joined #openstack-swift23:03
*** rcernin has joined #openstack-swift23:03
*** catinthe_ has joined #openstack-swift23:03
*** rcernin has quit IRC23:04
*** rcernin has joined #openstack-swift23:04
*** catintheroof has quit IRC23:06
*** vint_bra has quit IRC23:06
*** asettle has quit IRC23:08
*** dmorita has quit IRC23:17
*** dmorita has joined #openstack-swift23:20
*** dmorita has quit IRC23:26
*** isotope has quit IRC23:28
*** kei_yama has joined #openstack-swift23:32
*** dmorita has joined #openstack-swift23:35
*** rcernin has quit IRC23:41
openstackgerritClay Gerrard proposed openstack/pyeclib: Cleanup lint errors in test suite  https://review.openstack.org/40445723:46

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