Monday, 2016-08-08

*** ChanServ sets mode: +v tdasilva00:24
*** mingyu has joined #openstack-swift00:45
*** mingyu has quit IRC00:49
*** zhengyin has joined #openstack-swift01:24
*** mingyu has joined #openstack-swift02:00
*** mingyu has quit IRC02:05
*** hoonetorg has quit IRC02:20
*** zhugaoxiao has quit IRC02:57
*** mmcardle has joined #openstack-swift02:58
*** mmcardle has quit IRC03:16
*** mmcardle has joined #openstack-swift03:17
*** mingyu has joined #openstack-swift03:21
*** chlong has quit IRC03:25
*** mingyu has quit IRC03:25
*** zhugaoxiao has joined #openstack-swift03:36
*** chsc has joined #openstack-swift03:51
mattoliverauwow, quiet day here today03:52
*** mingyu has joined #openstack-swift03:58
*** mingyu has quit IRC04:04
*** chsc has quit IRC04:10
*** chromatin has quit IRC04:17
*** klrmn has quit IRC04:33
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925004:39
*** mmcardle has quit IRC04:43
*** vint_bra has joined #openstack-swift04:46
*** SkyRocknRoll has joined #openstack-swift04:59
*** KriskK has joined #openstack-swift05:00
*** flwang1 has quit IRC05:01
*** KriskK has quit IRC05:01
*** pcaruana has quit IRC05:03
*** mingyu has joined #openstack-swift05:20
*** ppai has joined #openstack-swift05:23
*** psachin has joined #openstack-swift05:25
*** mingyu has quit IRC05:25
*** vint_bra has quit IRC05:29
*** ChubYann has quit IRC05:32
*** mingyu has joined #openstack-swift05:38
*** mingyu has quit IRC05:45
*** chlong has joined #openstack-swift05:59
*** cdoron has joined #openstack-swift06:16
*** oshritf has joined #openstack-swift06:20
*** mingyu has joined #openstack-swift06:27
*** flwang1 has joined #openstack-swift06:37
*** pcaruana has joined #openstack-swift06:38
*** rcernin has joined #openstack-swift06:41
*** geaaru has joined #openstack-swift06:41
*** mingyu has quit IRC06:42
*** maestropandy has joined #openstack-swift06:48
*** tesseract- has joined #openstack-swift06:53
openstackgerritlokesh s proposed openstack/swift: Py3: Fixes AssertionError  https://review.openstack.org/34832207:00
*** flwang1 has quit IRC07:06
*** flwang1 has joined #openstack-swift07:06
*** flwang1 has quit IRC07:06
csmartmattoliverau: \o07:09
* csmart makes some noise07:09
mattoliveraucsmart: thanks man :)07:13
oshritfacoles_: morning07:19
*** rledisez has joined #openstack-swift07:21
*** permalac has joined #openstack-swift07:24
mattoliverauoshritf: o/ (noting I'm not acoles_)07:25
*** maestropandy has quit IRC07:25
*** Trixboxer has joined #openstack-swift07:32
oshritfmattoliverau: wouldnt confuse between you :)  Never better time than Bristol Monday  morning to discuss container sync07:33
mattoliverauLol, well it's Monday arvo (5:34pm) here so not as nice :)07:34
*** mingyu has joined #openstack-swift07:36
TrixboxerHi Everyone, I would like to know a possible way to set policy where users from same tenants do not get to rw *07:43
Trixboxerin that tenant07:43
oshritfmattoliverau: Working on container sync performance, https://review.openstack.org/#/c/210099/07:46
patchbotoshritf: patch 210099 - swift - Add process level concurrency to container sync07:47
*** flwang1 has joined #openstack-swift07:48
*** flwang1 has quit IRC07:54
cdoronmattoliverau: Good afternoon. Could you take a look at https://review.openstack.org/#/c/321041/ ? I got a +2 from Kota over 2 months ago.08:05
patchbotcdoron: patch 321041 - swift - Added a test for delayed reap.08:05
-openstackstatus- NOTICE: Gerrit is going to be restarted08:39
*** jistr|mtg is now known as jistr08:50
*** mingyu has quit IRC08:57
*** mingyu has joined #openstack-swift08:59
*** ouchkernel has quit IRC09:02
*** joeljwright has joined #openstack-swift09:03
*** ChanServ sets mode: +v joeljwright09:03
*** acoles_ is now known as acoles09:04
acolesoshritf: good morning09:06
acolesmattoliverau: good evening09:07
acolesTrixboxer: is your question in contecxt of keystone? if so then a user must have operator_role on the tenant/project in order to access the tenant's swift account09:09
acoleswhere operator_role(s) are defined in the swift proxy-server.conf keystoneauth section09:10
Trixboxeracoles: Yes, Im using keystone for authentication and have operator_role configured09:10
Trixboxermy query is, that from one tenant if two users are accessing their swift account, they both can see containers of each other and can operate on them09:10
*** ouchkernel has joined #openstack-swift09:10
TrixboxerI want to set a policy where each container is owned by creating_user and not the all users of tenant09:11
acolesTrixboxer: ok, so operator_roles isn't going to give you that level of control. you might close to what you need using container ACLs. With and ACL you could have a user with admin role create containers for other users and then set an ACL that grants the specific user RW access to that container09:14
*** daemontool has joined #openstack-swift09:14
Trixboxeracoles: right. Is there a way I can achieve this using policy.json ?09:18
acolesTrixboxer: unfortunately Swift doesn't yet support policy.json :/09:23
*** mvk has joined #openstack-swift09:24
*** mvk_ has joined #openstack-swift09:27
Trixboxeracoles: ouch. Will have to set ACL programatically then09:28
Trixboxeracoles: Does horizon+swift respect ACLs and work without issue ?09:29
acolesTrixboxer: I'm not too familiar with horizon, I've not heard of any issues in that respect but can't tell you for sure.09:30
*** daemontool has quit IRC09:31
*** silor has joined #openstack-swift09:32
*** joeljwright1 has joined #openstack-swift09:38
*** mvk_ has quit IRC09:38
*** joeljwright1 has quit IRC09:39
*** joeljwright has quit IRC09:41
*** silor1 has joined #openstack-swift09:41
*** silor has quit IRC09:43
*** silor1 is now known as silor09:43
cdoronacoles: I wrote a probe test for delayed reap. Could you take a look at it? https://review.openstack.org/#/c/321041/  . I got a +2 from Kota over 2 months ago.09:55
patchbotcdoron: patch 321041 - swift - Added a test for delayed reap.09:55
acolescdoron: is there a particular scenario that the new test is checking, when reaping is delayed, beyond what the unit tests cover?10:09
*** oshritf_ has joined #openstack-swift10:19
cdoronacoles: the new probe test also runs replicators and updaters and makes sure that the reaping continues to hold10:22
*** oshritf has quit IRC10:23
oshritf_join10:24
*** circ-user-3SNpi has joined #openstack-swift10:25
*** cshastri has joined #openstack-swift10:27
acolescdoron: ok10:27
circ-user-3SNpi Hi all.. I have tried swift storage with glusterfs backend which ends in failure. Whether glusterfs volume can be used as swift backend without swiftonfile?pls guide10:34
*** mingyu has quit IRC10:51
*** maestropandy has joined #openstack-swift10:57
*** circ-user-3SNpi has quit IRC11:01
*** maestropandy has quit IRC11:01
*** maestropandy has joined #openstack-swift11:04
*** maestropandy has left #openstack-swift11:05
*** jith_ has joined #openstack-swift11:05
jith_Hi all.. I have tried swift storage with glusterfs backend which ends in failure. Whether glusterfs volume can be used as swift backend without swiftonfile?11:06
*** pcaruana has quit IRC11:06
*** pcaruana has joined #openstack-swift11:07
*** permalac has quit IRC11:09
*** kei_yama has quit IRC11:14
*** cdelatte has joined #openstack-swift11:15
oshritf_acoles: hello11:20
*** oshritf_ is now known as oshritf11:23
*** furlongm_ has joined #openstack-swift11:23
*** maestropandy1 has joined #openstack-swift11:28
*** furlongm_ has quit IRC11:44
TrixboxerIf I have to create a hook in swift, so that the tenant:user creating the container will be sole owner of that container to do RW, where should I start ?11:45
*** furlongm_ has joined #openstack-swift11:48
*** cshastri has quit IRC11:51
*** furlongm_ has quit IRC11:51
*** mingyu has joined #openstack-swift11:52
*** furlongm_ has joined #openstack-swift11:54
*** mingyu has quit IRC11:57
*** furlongm_ has quit IRC11:59
*** baojg has joined #openstack-swift12:02
*** cshastri has joined #openstack-swift12:04
*** mingyu has joined #openstack-swift12:07
*** maestropandy1 has quit IRC12:09
*** furlongm_ has joined #openstack-swift12:10
*** baojg has quit IRC12:12
*** chmouel has joined #openstack-swift12:13
acolesTrixboxer: if you mean in middleware, keystoneauth.py maybe starting place12:15
*** SkyRocknRoll has quit IRC12:18
Trixboxeracoles: keystoneauth.py wont post acl permission on swift, I'll need hook in swift12:19
Trixboxersomething like  create_container from ./common/internal_client.py if headers=None12:20
*** furlongm_ has quit IRC12:21
openstackgerritMahati Chamarthy proposed openstack/swift: Delete old tombstones  https://review.openstack.org/34686512:22
ahale is that the kind of thing that the defaulter middleware was looking to do ? (i cant remember details)12:23
acolesTrixboxer: I'm not sure what you are looking for when you say 'hook' - do you want to intercept any container create request and set an ACL?12:24
acolesahale: possibly, but in this case it seems like the 'default' values would need to be dynamically generated from request auth parameters12:26
acolesdefault m/ware == patch 34285712:27
patchbotacoles: https://review.openstack.org/#/c/342857/ - swift - Add defaulter middleware12:27
Trixboxeracoles: yes, I want to intercept any container create request and set an ACL12:27
*** swat30 has joined #openstack-swift12:32
acolesTrixboxer: ok. I suggested looking at  keystoneauth.py because it creates a dict in the request environ (under key keystone.identity) with identity info from keystone authtoken, and illustrates how middleware can handle requests. So if you want to create a custom middleware there are some useful pointers in there.12:32
*** maestropandy has joined #openstack-swift12:33
*** maestropandy has left #openstack-swift12:34
Trixboxeracoles: Thanks for the much needed headsup12:34
acolesTrixboxer: Assuming your acl is based on the creating tenant/user id's, those id's are in that dict. (They are also in headers from authoken.py)12:34
*** chromatin has joined #openstack-swift12:35
*** baojg has joined #openstack-swift12:35
* acoles afk for lunch12:36
*** cshastri has quit IRC12:38
*** baojg has quit IRC12:51
*** furlongm_ has joined #openstack-swift12:57
*** baojg has joined #openstack-swift12:59
*** baojg has quit IRC13:00
*** baojg has joined #openstack-swift13:10
*** StraubTW has joined #openstack-swift13:14
*** furlongm_ has quit IRC13:15
*** vint_bra has joined #openstack-swift13:16
*** vint_bra has quit IRC13:16
*** maestropandy1 has joined #openstack-swift13:18
*** rvasilets___ has joined #openstack-swift13:21
*** furlongm_ has joined #openstack-swift13:21
*** furlongm_ has quit IRC13:22
*** furlongm_ has joined #openstack-swift13:29
*** baojg has quit IRC13:36
*** klamath has joined #openstack-swift13:41
*** klamath has quit IRC13:43
*** klamath has joined #openstack-swift13:44
*** ouchkernel has quit IRC13:49
*** baojg has joined #openstack-swift13:53
*** ouchkernel has joined #openstack-swift13:56
*** baojg has quit IRC13:58
*** ppai has quit IRC14:00
*** chromatin has quit IRC14:00
tdasilvagood morning14:07
openstackgerritAlistair Coles proposed openstack/swift: Tighten up expirer tests  https://review.openstack.org/35243814:08
*** esker has joined #openstack-swift14:10
*** baojg has joined #openstack-swift14:11
*** maestropandy1 has quit IRC14:12
*** ppai has joined #openstack-swift14:14
acolestdasilva: hi14:15
*** vint_bra has joined #openstack-swift14:16
tdasilvaacoles: hello! o/14:16
acolesoshritf: re. your comment on patch 348495, about testing deleted manifests...once deleted the manifest would be like any other deleted object, which is covered by the test_sync_* tests I think.14:16
patchbotacoles: https://review.openstack.org/#/c/348495/ - swift - Make container sync copy SLO manifests14:16
*** maestropandy1 has joined #openstack-swift14:20
*** maestropandy1 has left #openstack-swift14:20
*** maestropandy has joined #openstack-swift14:21
*** permalac has joined #openstack-swift14:21
*** maestropandy has left #openstack-swift14:21
*** StraubTW_ has joined #openstack-swift14:24
mmotianiGood Morning14:25
*** StraubTW has quit IRC14:27
*** zaitcev has joined #openstack-swift14:27
*** ChanServ sets mode: +v zaitcev14:27
oshritfacoles: perfect then14:32
oshritfacoles: Thanks for the great work on 210099! Highly appreciated14:33
oshritfwhat14:33
oshritf's the next step? squash them in?14:34
acolesoshritf: NP. yes, if you are ok with the proposals then let's squash them into 210099 (I can do that if you like - there is a pep8 error I should fix)  Bit I am just thinking about your comment re the changes impact on the threading patch.14:35
*** psachin has quit IRC14:35
oshritfI was wondering whether moving the child stats to local variables would have any impact on the future adding threads level, and add some minor comments - which I could fix/discuss after squashing them in14:35
oshritfacoles: oh, also - with the forking patch, your comment about having 2 processes instead of one with processes = 1 is still relevant14:37
oshritfacoles: but I'm not sure there is an elegant way to avoid it14:38
*** mingyu has quit IRC14:38
*** baojg_ has joined #openstack-swift14:39
*** baojg has quit IRC14:40
openstackgerritMohit Motiani proposed openstack/swift: Detect duplicate storage policy 0 section in func tests  https://review.openstack.org/35193414:40
*** ppai has quit IRC14:43
*** psachin has joined #openstack-swift14:46
*** asettle has joined #openstack-swift14:48
acolesoshritf: w.r.t. the stats updates with multiple threads, I think I would explore having each container_sync_row thread return its contribution to stats rather than updating a shared dict.14:49
acolesoshritf: re. 2 vs 1 processes, I'll give it some thought, I'm not sure its a big deal either way. It looks like the auditor does the same thing (i.e. concurrency==1 -> parent + 1 child process)14:53
*** kragniz has quit IRC15:00
acolesoshritf: so, are you going to squash those patches or shall I?15:00
oshritfacoles: yes, probably better since currently no locking mechanism too. Could later be performance compared as well. re fork + pipe, same mechanism as in auditor and updater15:01
oshritfacoles: please squash - I'll work on it after squashed15:01
acolesoshritf:  ok, and were you happy to use patch 350717 too?15:02
patchbotacoles: https://review.openstack.org/#/c/350717/ - swift - Refactor forking in container sync run_forever15:02
*** psachin has quit IRC15:02
*** baojg_ has quit IRC15:03
oshritfacoles: yes, I liked your proposal, appreciate the effort and your time15:06
*** StraubTW_ has quit IRC15:11
*** cdoron has quit IRC15:15
openstackgerritAlistair Coles proposed openstack/swift: Add process level concurrency to container sync  https://review.openstack.org/21009915:31
acolesoshritf: ^^ squashed version, we can work from that with any other changes15:31
*** oshritf has quit IRC15:35
*** pgbridge has joined #openstack-swift15:38
*** rfinn has joined #openstack-swift15:38
*** klrmn has joined #openstack-swift15:40
tdasilvaccccccdkkgthffjhkbltbeckeegrdendkgnclbkglctf15:46
zaitcevhe's going to blame the cat15:50
*** rcernin has quit IRC16:01
*** cdoron has joined #openstack-swift16:02
*** pkovar has joined #openstack-swift16:06
*** pcaruana has quit IRC16:11
*** chsc has joined #openstack-swift16:11
*** chsc has joined #openstack-swift16:11
*** permalac has quit IRC16:12
*** rvasilets___ has quit IRC16:17
*** chsc has quit IRC16:18
jrichliacoles: i see you doing container-sync this morning.  would you like if I take a look into the probe test failures for patch 352438 ?  I had gotten even different ones than the gate test.16:24
patchbotjrichli: https://review.openstack.org/#/c/352438/ - swift - Tighten up expirer tests16:24
*** catintheroof has joined #openstack-swift16:28
*** klrmn has quit IRC16:29
*** david-lyle_ has joined #openstack-swift16:29
timburkegood morning16:30
pkovarhi, could someone review this swift install docs patch for me? https://review.openstack.org/#/c/346925/16:30
patchbotpkovar: patch 346925 - swift - [install-guide] Include environment-networking16:30
notmynamegood morning16:31
*** asettle has quit IRC16:31
*** asettle has joined #openstack-swift16:32
*** david-lyle has quit IRC16:33
*** mmcardle has joined #openstack-swift16:35
*** rledisez has quit IRC16:37
zaitcevpkovar: Do you know why the install-guide is a separate directory and is not nested under docs? With this layout I cannot click on the docs gate and examine the formatted docs.16:42
zaitcevpkovar: actually, never mind. There's a separate job for it.16:42
pkovarzaitcev: for background info on this, see http://specs.openstack.org/openstack/docs-specs/specs/newton/project-specific-installguides.html16:42
pkovar(and http://specs.openstack.org/openstack/docs-specs/specs/newton/project-specific-installguides.html#publishing specifically)16:43
zaitcevpkovar: What do you think about moving the warnings outside of the node hierarchy (e.g. below "Second node") and just having one of each?16:44
zaitcevCurrently it looks like something that The OpenStack Department of Redundant Redundancies produced.16:45
pkovarheh. let me have a look16:46
zaitcevIt's more apparent in the formatted output - http://docs-draft.openstack.org/25/346925/1/check/gate-swift-install-guide/3d9f987//install-guide/build/html/environment-networking.html16:47
pkovarzaitcev: you mean moving the two admonitions to the bottom of the http://docs-draft.openstack.org/25/346925/1/check/gate-swift-install-guide/3d9f987//install-guide/build/html/environment-networking.html ?16:48
pkovari can do that, sure16:48
zaitcevYes. I can see why identical copies of /etc/hosts are included, to make it easier for guys going step by step.16:49
*** nadeem has joined #openstack-swift16:49
*** diogogmt has joined #openstack-swift16:50
*** nadeem has quit IRC16:50
pkovarzaitcev: right. i could also s/Edit the /etc/hosts file to contain the following:/Edit the /etc/hosts file to have the same content as the hosts file in the previous procedure/ -- but that would require people scrolling back16:53
zaitcevpkovar: exactly16:53
pkovarokay, let me update the patch then :)16:53
zaitcevthanks, didn't mean to make you sweat the details, but if it's possible, it's for the best16:54
zaitcevIMHO16:54
zaitcevin before second +2 comes around with "what the eff is this"16:55
*** nadeem has joined #openstack-swift16:55
pkovarnp. thanks for your feedback :)16:55
*** tesseract- has quit IRC16:57
*** esker has quit IRC16:58
pkovarand you were right, it looks much better in the preview16:58
*** mmcardle has quit IRC16:59
openstackgerritPetr Kovar proposed openstack/swift: [install-guide] Include environment-networking  https://review.openstack.org/34692517:00
pkovarzaitcev: done. thanks again17:01
*** asettle has quit IRC17:05
*** esker has joined #openstack-swift17:08
*** zul_ has joined #openstack-swift17:09
*** zul has quit IRC17:09
*** ChubYann has joined #openstack-swift17:11
*** esker has quit IRC17:13
*** chsc has joined #openstack-swift17:13
*** ozeri has joined #openstack-swift17:14
*** mmcardle has joined #openstack-swift17:16
*** daemontool has joined #openstack-swift17:16
*** _JZ_ has joined #openstack-swift17:17
*** asettle has joined #openstack-swift17:19
*** mmcardle has quit IRC17:21
*** asettle has quit IRC17:24
*** ozeri has quit IRC17:31
*** timss has quit IRC17:33
*** asettle has joined #openstack-swift17:33
*** klrmn has joined #openstack-swift17:33
*** asettle has quit IRC17:37
acolesjrichli: thanks for review, looks like I forgot about encryption :/17:39
*** mingyu has joined #openstack-swift17:39
acolesjrichli: and I guess you ran the test with encryption enabled17:39
jrichliacoles: yep17:39
*** geaaru has quit IRC17:41
*** david-lyle_ has quit IRC17:42
*** mingyu has quit IRC17:43
openstackgerritAlistair Coles proposed openstack/swift: Tighten up expirer tests  https://review.openstack.org/35243817:45
*** david-lyle has joined #openstack-swift17:45
*** asettle has joined #openstack-swift17:47
*** acoles is now known as acoles_17:47
*** asettle has quit IRC17:52
*** pkovar has quit IRC17:56
*** mingyu has joined #openstack-swift17:56
*** timss has joined #openstack-swift18:03
*** daemontool has quit IRC18:10
*** btorch has left #openstack-swift18:31
*** greghaynes has quit IRC18:35
*** mingyu has quit IRC18:39
*** rfinn has quit IRC18:40
*** greghaynes has joined #openstack-swift18:48
*** Anticime1 has joined #openstack-swift18:50
*** mtreinish_ has joined #openstack-swift18:50
*** ctennis has joined #openstack-swift18:50
*** thurloat_ has joined #openstack-swift18:50
*** thurloat has quit IRC18:50
*** swat30 has quit IRC18:50
*** mtreinish has quit IRC18:50
*** Anticimex has quit IRC18:50
*** ctennis- has quit IRC18:50
*** dabukalam has quit IRC18:50
*** thurloat_ is now known as thurloat18:50
*** mtreinish_ is now known as mtreinish18:50
*** swat30 has joined #openstack-swift18:50
*** dabukalam has joined #openstack-swift18:51
*** rfinn has joined #openstack-swift18:51
*** asettle has joined #openstack-swift18:54
*** fifieldt has quit IRC19:07
*** fifieldt has joined #openstack-swift19:18
*** silor has quit IRC19:29
*** vinsh has quit IRC19:29
*** vinsh has joined #openstack-swift19:30
*** jistr has quit IRC19:44
*** jistr has joined #openstack-swift19:48
*** jistr has quit IRC19:53
*** jistr has joined #openstack-swift19:56
*** cdoron has quit IRC19:56
openstackgerritThiago da Silva proposed openstack/swift: Symlink implementation.  https://review.openstack.org/23216220:11
*** rfinn has quit IRC20:21
*** ouchkernel has quit IRC20:23
*** mingyu has joined #openstack-swift20:25
*** ouchkernel has joined #openstack-swift20:25
*** tqtran has joined #openstack-swift20:29
*** mingyu has quit IRC20:29
tqtranhello quick question, whenever i perform a POST action (example posting account acl) I noticed that the backend is hit with a GETorHEAD request first, then the authorization, then the POST. Why does the GETorHEAD happen at all?20:30
tqtranIts been puzzling me, also I cant seem to locate where we are storing the headers as metadata. Seems like add_acls_from_sys_metadata only updates the response header, but where does the actual storage happen?20:31
*** tongli has joined #openstack-swift20:32
zaitcevthere has to be some get_info first, unless cached20:33
*** Jeffrey4l has quit IRC20:35
*** Jeffrey4l has joined #openstack-swift20:35
*** rfinn has joined #openstack-swift20:41
*** tongli has quit IRC20:52
*** acoles_ is now known as acoles21:06
*** natarej has quit IRC21:11
*** chromatin has joined #openstack-swift21:16
*** acoles is now known as acoles_21:26
*** kevinc has joined #openstack-swift21:34
jrichlitqtran: the add_acls_from_sys_metadata is in the proxy controller.  the proxy acct controller passes the POST request along with make_requests call in POST.21:39
jrichlitqtran: I think you are looking for swift/account/server.py POST21:39
*** admin6 has joined #openstack-swift21:39
*** mingyu has joined #openstack-swift21:40
kevincIs there any documentation how to delete projects/tenants in swift? When I delete the project from Keystone, using the Keystone API, it doesn't appear to delete the swift project/tenant. I deleted all of the containers and objects from swift before deleting the project in Keystone.21:40
*** catintheroof has quit IRC21:43
*** mingyu has quit IRC21:44
jrichlikevinc: AFAIK, this would be deleting an account.  you must be "reseller admin" in order to delete accounts.  Is this what you mean?21:49
jrichliand the proxy server must have have 'allow_account_management = true'21:51
kevincjrichli: Yes, it is. Sorry, it seems each OpenStack uses Account/Project/Tenant to mean the same thing.21:51
kevincWe have been running swift for a few using with swauth for authentication and I have been able to delete account using swauth. We recently added keystone (and nova) to our OpenStack service and I am finally getting around to purging some accounts that were created with keystone only.21:53
zaitcevI heard some people have all proxies with allow_account_management=false and 1 special proxy with allow_account_management=true, firewalled from the outside of course.21:59
mattoliverauMorning22:00
jrichlikevinc: I have searched the docs, and I don't see the DELETE to an account being individually addressed.  the account reaper manpages speak to some internal details, but I don't think that's what you are wanting.22:10
jrichlikevinc: I assume its just a DELETE to the account URL, given the conditions mentioned above are true.22:10
jrichlimattoliverau: morning!22:12
kevincjrichli: thank you! one more question, how can i tell if an account exists? when i do a get/head on https://url/v1/PREFIX_ACCOUNTID I get a http 204 status code if the account exists and if the account doesn't exist. The only difference i can tell is if the account exists the response includes headers for the storage policies. I would expect the query of a nonexistent would return an 404 error22:19
*** chromatin has quit IRC22:26
*** admin6 has left #openstack-swift22:35
*** chlong has quit IRC22:35
tqtranjrichli: yes, i had a breakpoint in both GETorHEAD and POST. seems like its hitting both. and along the way, only the response headers are modified. im just puzzled because at some point, the headers are saved as metadata. i cant seem to pinpoint in the code where exactly this steps happen22:36
torgomaticit's a shame there's no OutOfCheeseError in swift.common.exceptions22:36
*** asettle has quit IRC22:38
*** kevinc_ has joined #openstack-swift22:39
*** kevinc has quit IRC22:42
*** kevinc_ has quit IRC22:43
timburketqtran: you'll want to look around https://github.com/openstack/swift/blob/2.9.0/swift/account/server.py#L253, which calls out to the account broker at https://github.com/openstack/swift/blob/2.9.0/swift/common/db.py#L76522:45
timburketqtran: before that update_metadata call, the account had the old ACL; after it, the new22:46
*** rfinn has quit IRC22:46
tqtranthanks timburke, that is very helpful22:46
*** vint_bra has quit IRC22:58
*** nadeem has quit IRC23:01
*** chromatin has joined #openstack-swift23:03
*** mingyu has joined #openstack-swift23:10
*** mingyu has quit IRC23:15
*** chsc has quit IRC23:21
hogepodgehttps://review.openstack.org/#/c/324739/ ping on this review, hoping it lands for Newton. We also have an immediate need for it in some deployed projects fwiw. Documentation change23:28
patchbothogepodge: patch 324739 - python-swiftclient - Insufficent info about read and write ACL syntax23:28
*** kei_yama has joined #openstack-swift23:35
*** klamath has quit IRC23:36
*** _JZ_ has quit IRC23:40
*** furlongm_ has quit IRC23:44

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