Friday, 2017-09-01

openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify User Update  https://review.openstack.org/49928400:04
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Add User to Group  https://review.openstack.org/49934500:06
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Check User in Group  https://review.openstack.org/49935700:06
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Remove User from Group  https://review.openstack.org/49936000:07
*** gouthamr has joined #openstack-shade00:18
*** slaweq has joined #openstack-shade00:34
*** slaweq has quit IRC00:39
*** slaweq has joined #openstack-shade01:35
*** slaweq has quit IRC01:40
*** slaweq has joined #openstack-shade02:49
*** slaweq has quit IRC02:55
*** slaweq has joined #openstack-shade03:37
*** gkadam_ has joined #openstack-shade03:41
*** slaweq has quit IRC03:42
*** gouthamr has quit IRC03:53
*** slaweq has joined #openstack-shade04:38
*** slaweq has quit IRC04:43
*** slaweq has joined #openstack-shade05:58
*** slaweq has quit IRC06:12
*** slaweq has joined #openstack-shade07:01
*** slaweq has quit IRC07:06
*** slaweq has joined #openstack-shade07:13
*** ioggstream has joined #openstack-shade07:44
*** slaweq has quit IRC08:00
*** slaweq has joined #openstack-shade08:01
*** slaweq has quit IRC08:09
*** slaweq has joined #openstack-shade08:09
*** gkadam_ has quit IRC12:27
openstackgerritOpenStack Proposal Bot proposed openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/49998312:34
openstackgerritMonty Taylor proposed openstack-infra/shade master: Fix typo in tox.ini  https://review.openstack.org/50004513:13
*** gouthamr has joined #openstack-shade13:56
samueldmqmorning shade!14:17
samueldmqmordred: https://review.openstack.org/#/c/499284 needs a couple of extra eyes14:17
samueldmqI left a comment there with a question14:18
mordredsamueldmq: ah - so - the ansible os_user module is explicitly passing domain_id all the time, even when it's None - so our valid_kwargs isn't quite good enough14:21
mordred:(14:21
samueldmqmordred: maybe I could improve valid_kwargs to drop none things?14:22
samueldmqor do we want to keep none if passed in explicitly?14:22
mordredsamueldmq: well- that's just the thing- valid_kwargs is done to allow a kwarg to be passed as None and have that be meaningful14:22
samueldmqmaybe fixing os_user module would be more appropriate then14:22
samueldmqand do not pass domain_id if it is none14:23
mordredI think the issue here is actually in the os_user module BUT that's useful as it shows us behavior from before that we'd be breaking14:23
mordredwe can fix os_user, but another user might be using shade expecting the same behavior (whichis coming from keystoneclient dropping domain_id if it's None)14:23
samueldmqhmm from that point of view yes. I guess keystoneclient was the one disregarding none values14:23
mordredyah14:23
samueldmqok I will keep the same behavior, and add a note14:23
samueldmqand yah, we take backwards compatibility seriously in shade14:24
mordredso I think for now let's just add in some removing of kwargs entries with None values in this method - or maybe  ahelper function that takes a dict and strips None values?14:24
mordredsamueldmq: yes - we do -it's super annoying sometimes :)14:24
mordredsamueldmq: so - the important thign here actually ...14:24
mordredis that some of these values are things where someone might want to update a user to remove a setting ...14:25
samueldmqexactly and we dont know. we can't know for sure14:25
mordredlike - email14:25
samueldmqlet's just respect the behavior and continue with the same behavior so we dont break any one's apps14:25
mordredbut some are things where changing it to none makes no sense14:25
mordreddomain_id is one of those I think14:25
samueldmq++14:25
samueldmq++ I will just drop domain_id and leave a note for now14:26
mordredyah - I thin it's just domain_id that'st the problem14:26
samueldmqexactly14:26
mordredand honestly, domain_id as an argument to this method is really only useful for lookingup the user in the first place14:26
samueldmqwell, good thing that gate caught it14:27
mordredso you could potentially promote it to being a real keyword arg14:27
mordredsince it really never needs to be in the kwargs we pass to patch14:27
samueldmqhmm and treat the rest of kwargs consistently14:27
samueldmqthat works too14:27
openstackgerritMerged openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/49998314:29
openstackgerritMonty Taylor proposed openstack-infra/shade master: Remove errant print  https://review.openstack.org/50009014:53
*** slaweq has quit IRC14:54
openstackgerritMonty Taylor proposed openstack-infra/shade master: Use new keystoneauth version discovery  https://review.openstack.org/49358214:59
openstackgerritMonty Taylor proposed openstack-infra/shade master: Use new keystoneauth version discovery  https://review.openstack.org/49358215:10
Shrewsmordred: +3'd ^^15:14
openstackgerritMerged openstack-infra/shade master: Fix typo in tox.ini  https://review.openstack.org/50004515:33
mordredSamYaple: left you a nice long note on https://review.openstack.org/#/c/496992 - don't hate me :)15:43
SamYaplemordred: yea i dont really understand what you want15:46
SamYapleim trying to find an example15:47
mordredSamYaple: look in shade/_normalize.py ... hrm, maybe we just land this patch as is and move the identity normalization functions as a followup15:47
SamYapleyour call. this patch is not critical to me at all.15:49
mordredSamYaple: k. I'm going to put up a quick followup patch - identity turns out to be weird here in a few ways, but we already have some semantics defined for project15:58
*** thrash is now known as thrash|biab16:02
openstackgerritJulia Kreger proposed openstack-infra/shade master: De-clientify baremetal create/delete  https://review.openstack.org/50011916:14
openstackgerritJulia Kreger proposed openstack-infra/shade master: De-client-ify baremetal machine port list  https://review.openstack.org/50012016:14
openstackgerritJulia Kreger proposed openstack-infra/shade master: De-client-ify machine patch operations  https://review.openstack.org/50012116:14
SamYaplemordred: i guess thats whats confusing me because i dont know how role+domain_id relates to project16:39
SamYaplebut really, that patch was entirely a "here is part of the api we missed, it might be useful" thing.16:40
SamYaplei dont personally use roles assigned to domains, but that would be a cool way to limit who gets what roles16:40
SamYapleonly roles per domain, and no one can get a role outside of thier domain16:41
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify User Update  https://review.openstack.org/49928416:46
mordredSamYaple: yah- don't worry about it - I mostly just noticed that role hadn't been migrated to thenew normalization yet16:47
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Add User to Group  https://review.openstack.org/49934516:48
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Check User in Group  https://review.openstack.org/49935716:50
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Remove User from Group  https://review.openstack.org/49936016:54
*** ioggstream has quit IRC17:14
openstackgerritMerged openstack-infra/shade master: Use new keystoneauth version discovery  https://review.openstack.org/49358217:40
cmurphyooooh nice ^17:41
*** thrash|biab is now known as thrash18:25
mordredcmurphy: \o/18:27
SamYaplemordred: its ok. ill work on the role normalization thing, but dont let that hold up tagging was my point18:44
mordredSamYaple: oh - I'm not18:45
mordredSamYaple: and I've got a thing actually ... one sec18:45
openstackgerritMonty Taylor proposed openstack-infra/shade master: Allow domain_id for roles  https://review.openstack.org/49699218:49
openstackgerritMonty Taylor proposed openstack-infra/shade master: Move role normalization to normalize.py  https://review.openstack.org/50017018:49
SamYaple++18:53
mordredSamYaple: ^^ rebased your patch too, just because I needed to for local testing18:58
SamYaplenot a problem19:03
SamYaplealmost finished converting all the internal saltcode we have to using shade. without enabling any caching yet its ~2x faster19:08
SamYapleoh speaking of which. is the cache safe when multiple instances of shade is hitting it?19:09
SamYapleis there locking and what not19:09
mordredSamYaple: depends on the backend you configure it to use19:31
mordredSamYaple: also - there are (currently) 2 different caches - one that's using dogpile.cache and thatyou can configure to use a shared cache - but for list_servers, list_ports and list_floating_ips there is a built-in in-memory cache  that is written to work properly with the batched/ratelimited operations the multi-threaded task manager from nodepool uses19:32
mordredSamYaple: once we're done with restification (almost done!) the plan is swing back and finish getting everything to use dogpile - the last time we tried that is failed spectaularly so it'll be a few days of debugging fun when we try again :)19:33
*** gouthamr has quit IRC19:51
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Check User in Group  https://review.openstack.org/49935720:02
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/shade master: De-client-ify Remove User from Group  https://review.openstack.org/49936020:02
SamYaplei see20:09
SamYaplei wonder if salt can use the same cloud object across several states20:09
openstackgerritMonty Taylor proposed openstack/oaktree master: Add zuul v3 job to trigger readthedocs  https://review.openstack.org/49890520:13
mordredSamYaple: it's a good question. also - there is a file cache backend to dogpile too - I _think_ it's threadsafe - but I have not verified that in anger20:16
SamYaplemordred: there is a shared __context__ dict across all states in a single run, i can add oscloud and opcloud to that and reuse. which is nice20:17
mordredSamYaple: btw - there is also a new constructor parameter that we just landed ... or, rather,crappit, I thought it merged but it's got a merge conflict ...20:17
mordredSamYaple: woot!20:18
SamYapleyea we will see how this goes20:18
mordredSamYaple: in any case, this: https://review.openstack.org/#/c/494535/20:18
SamYaplei may not need dogpile after this20:18
mordredSamYaple: you may want to experiment with that flag from salt too (we added it because of a bug reported against ansible that things were doing too much listing)20:18
SamYapleoh yea... i may have made that merge conflict20:18
openstackgerritMerged openstack/os-service-types master: Updated from global requirements  https://review.openstack.org/50001420:19
SamYaplecool. ill see what i can do20:20
openstackgerritMonty Taylor proposed openstack-infra/shade master: Use direct calls to get_<resource>_by_id  https://review.openstack.org/49453520:21
*** gouthamr has joined #openstack-shade20:28
*** slaweq has joined #openstack-shade20:52
*** slaweq has quit IRC21:00
*** gouthamr has quit IRC21:16
openstackgerritJulia Kreger proposed openstack-infra/shade master: De-client-ify baremetal node_set_provision_state  https://review.openstack.org/49977321:39
openstackgerritPaul Belanger proposed openstack-infra/shade master: WIP: Add openstack-doc-build to shade  https://review.openstack.org/50020121:44
*** slaweq has joined #openstack-shade21:59
*** slaweq has quit IRC22:00
openstackgerritPaul Belanger proposed openstack-infra/shade master: Add openstack-doc-build to shade  https://review.openstack.org/50020122:34
*** gouthamr has joined #openstack-shade23:14
*** olaph has quit IRC23:36
*** olaph has joined #openstack-shade23:37
*** thrash is now known as thrash|g0ne23:57

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