Wednesday, 2017-05-24

openstackgerritMerged openstack-infra/shade master: Allow a user to submit start and end time as strings  https://review.openstack.org/46725700:52
openstackgerritOpenStack Proposal Bot proposed openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/46742801:02
openstackgerritMerged openstack/os-client-config master: Revert "Use interface not endpoint_type for keystoneclient"  https://review.openstack.org/46214401:02
*** gouthamr has quit IRC02:33
*** gkadam has joined #openstack-shade03:20
*** slaweq has joined #openstack-shade03:50
*** slaweq has quit IRC03:55
*** ChanServ changes topic to "#openstack-shade"04:08
-openstackstatus- NOTICE: Sufficient free space has been reclaimed that jobs are passing again; any POST_FAILURE results can now be rechecked.04:09
openstackgerritRajat Sharma proposed openstack-infra/shade master: Replace assertRaisesRegexp with assertRaisesRegex  https://review.openstack.org/46748605:08
*** ioggstream has joined #openstack-shade06:51
*** ioggstream has quit IRC07:08
*** jroll has quit IRC07:12
*** ioggstream has joined #openstack-shade07:22
*** jroll has joined #openstack-shade10:25
*** ioggstream has quit IRC11:24
*** ioggstream has joined #openstack-shade11:52
*** noshankus has quit IRC12:05
*** noshankus has joined #openstack-shade12:05
openstackgerritMerged openstack-infra/shade master: Pick most recent rather than first fixed address  https://review.openstack.org/46738512:52
*** gouthamr has joined #openstack-shade13:50
Shrewsmordred: https://github.com/ansible/ansible/pull/24881 needs a second shipit to merge, if it looks good to you13:55
Shrewsor rcarrillocruz ^^^13:55
*** gkadam has quit IRC13:56
Shrewsmordred: also, bug in image endpoint discovery? https://github.com/ansible/ansible/issues/2478613:58
Shrewsmordred: last thing, i promise... these tempest modules being proposed feel a bit out of place (https://github.com/ansible/ansible/pull/24173 , https://github.com/ansible/ansible/pull/24153). How do you feel about them?14:03
mordredShrews: image endpoint discovery bug should be fixed in the latest shade that just got cut14:20
mordredShrews: although- I think we should put in a try/except around image discovery so that we always fall back to whatever's in the catalog14:23
Shrewsmordred: that method still exists in the current shade, so shouldn't the KeyError problem still exist?14:28
mordredShrews: yup14:37
Shrewsthen i remain confused14:43
mordredShrews: sorry - we fixed one thing related to image discovery exceptions - but then I realized this is a different issue14:44
openstackgerritMonty Taylor proposed openstack-infra/shade master: Use catalog endpoint on any errors in image version discovery  https://review.openstack.org/46764414:44
mordredShrews: then I stopped talkined to you so I could write that ^^14:44
Shrewsoh14:44
Shrewsby all means, stop talking to me to fix more things!14:44
mordredShrews: we ALMOST got all the way to the logic of "don't screw the user if image discovery doesn't work"14:44
mordredShrews: for the tempest modules - I chatted with that guya little while ago and told him they seemed like a fine idea ... there's another module he was working on for making a tempest config that actually needed shade (and needed new methods on shade)14:45
mordredbecuase it was talking to the api to find out what extensions and whatnot were enabled then writing a config14:46
Shrewsmordred: i left a comment on the tempest things. i just don't think they belong, but if you and others think they do, so be it14:46
mordredthat said - I do still think that "os_tempest_results" should just be "subunit" and should be elsewhere14:47
Shrewsjlk: btw, i invoked your name on PR 24173 above14:47
Shrewsi mean, i have NEVER run tempest before and have no interest in doing so, so I'm not going to test or fix bugs for the os_tempest_* modules14:49
Shrewsand this person is adding them for a final project for school, so it's likely he won't either14:50
* Shrews returns to non-ansible things14:51
*** pabelanger has quit IRC14:52
*** pabelanger has joined #openstack-shade14:52
*** fbaca has quit IRC14:58
*** slaweq has joined #openstack-shade16:49
*** slaweq has quit IRC16:53
*** slaweq has joined #openstack-shade16:53
openstackgerritMonty Taylor proposed openstack-infra/shade master: Log cloud name on Connection retry issues  https://review.openstack.org/46768616:59
mordredShrews: btw - the added non-voting py3 functional jobs actually show some py3 errors we're not trapping in unit tests17:02
mordredShrews: (shade side, obvs)17:02
Shrewsneat17:02
*** rcarrillocruz has quit IRC17:12
openstackgerritMonty Taylor proposed openstack-infra/shade master: Add time reporting to Connection Retry message  https://review.openstack.org/46768917:24
openstackgerritMonty Taylor proposed openstack-infra/shade master: Fix python3 issues in functional tests  https://review.openstack.org/46769317:35
*** rcarrillocruz has joined #openstack-shade17:47
*** rcarrillocruz has quit IRC18:27
*** rcarrillocruz has joined #openstack-shade18:36
openstackgerritMonty Taylor proposed openstack-infra/shade master: Fix python3 issues in functional tests  https://review.openstack.org/46769319:01
*** slaweq has quit IRC19:31
*** slaweq has joined #openstack-shade19:31
*** slaweq has quit IRC19:40
*** openstackgerrit has quit IRC19:48
*** rcarrillocruz has quit IRC20:27
*** slaweq has joined #openstack-shade20:28
slaweqmordred: hello20:35
*** rcarrillocruz has joined #openstack-shade20:35
slaweqmordred: I'm checking designateclient now and it looks that it's still using v1 API for domains and recordsets20:35
morganmordred: can i say, the whole "admin vs non-admin" API in keystone v2 is terrrrrrrrrrible20:36
slaweqso I think that I will do the same in first step and will only add calls using API v1 (and remove API discovery calls)20:36
mordredmorgan: very very bad20:36
slaweqI will also add TODOs with info about discovery to add20:37
mordredslaweq: yes - I think this is the right choice - then adding v2 and discovery later ...20:37
mordredyes - exactly20:37
slaweqand I will add this discovery in second step20:37
mordred\o/20:37
slaweqok, thx :)20:37
morganmordred: hmmm... trying to figure out how to ensure we're acting on admin API in shade when de-client-i-fying20:37
mordredbtw - we cut a new shade release today - so nodepool is now running with the neutron REST calls intead of neutronclient20:37
slaweq:)20:37
morganmordred: is it safe to assume we *always* act on admin api with shade in v2.0?20:38
mordredmorgan: yes - we have no end-user api calls (I don't think) in the 2.0 stack20:38
morganok cool so i can do just self._keystoneclient.get()...20:38
mordredmorgan: also - I *think* we added something in the latest occ to help with this20:38
morganwell, we'll see how it goes :P20:38
mordredmorgan: :)20:39
mordredmorgan: also - jamielennox said something a few weeks ago about being able to specify interface in endpoint_filters in an individual call20:40
mordredmorgan: but I think that assumes making a call on session not on a mounted adapter20:40
morganmordred: yeah20:40
mordredmorgan: but worth considering maybe if you get in a bind20:40
morganmordred: i'd like to not use self._identity_client, but that can be a future cleanup20:42
morganoh look... yeah that doesn't work20:42
morganbah20:42
morganat all20:42
mordredmorgan: I may be reading you backwards ... you want to not-use the adapter? or you're saying step-one workaround is using keystoneclient's get call to switch to the rest calls, and step 2 is swift from keystoneclient.get to ksa.adapter.get ?20:43
* mordred is foggy on things sometimes20:44
morganeventually i want to use KSA directly20:44
morgannot "identity_client" which is a ksc object20:44
morganeven though we call ".get" on it20:44
morganthats all20:44
morganso yeah ksc.get to ksa.adapter.get20:44
morganbut starting with self._identity_client20:45
mordredgotcha. so - fwiw, self._identity_client is the adapter and self.keystone_client is the ksa object20:47
mordredand yes - I think you have described an excellent future state20:47
morganmordred: oh man. we aren't doing adapter mounting at all here.20:56
morganksc does so much magic20:56
morgan.............20:56
mordredmorgan: all of the client libs do an enormous amount of magic, it turns out - and almost all of it just makes things harder20:56
morgani mean, is it safe to just do:20:56
morganhttps://www.irccloud.com/pastebin/vPT5f4yc/20:57
morganyes the join is explicitly needed in this case20:58
morganit seems like it fall back to v2.0 by default20:58
*** openstackgerrit has joined #openstack-shade20:58
openstackgerritMerged openstack-infra/shade master: Fix python3 issues in functional tests  https://review.openstack.org/46769320:58
morganif that is safe i need to muck with tests as well.20:58
mordredmorgan: it's probably safe - however, go take a peek at what we're doing in _image_client - where we do the api_version hack thing once when we make the adapter20:59
morganah20:59
morganok21:00
morgan*grump* stupid api versions being weird.21:00
mordredall of these hack should go away when we get version discovery finished in ksa - but we need to get the specs landed first - then I need to write a keystone spec for that ... so shade-level hacks will be here for at least a few weeks21:00
mordredmorgan: zomg tell me about it21:00
morganyou mean21:00
morganhttps://www.irccloud.com/pastebin/4RksW9n7/21:00
morgando something like that...21:01
morgan?21:01
mordrednope- one sec21:01
mordredmorgan: https://github.com/openstack-infra/shade/blob/master/shade/openstackcloud.py#L43421:01
morganoh i see21:02
mordredwhich gets called in https://github.com/openstack-infra/shade/blob/master/shade/openstackcloud.py#L49921:02
mordredits SO EVIL21:02
morgani mean... that seems like it will break the magic in ksc21:02
morganunless we replace all ksc calls at once.21:02
morganso non-magic calls will suddenly be pointed at the wrong thing?21:03
mordredidentity_client isn't ksc21:03
morganoh it isn't?21:03
mordredself.keystone_client is the ksc client21:03
morganooooooh21:03
morganok21:03
mordredself._identity_client is the adapter21:03
mordredmorgan: so there's a bit of logic you can see in the image version discovery - where we try to honor the version the user tells us - but if we can't we fall back to whatever we can find and then just set the internal config variable to 1 or 221:04
mordredthe reason is that shade knows how to do both - and absentspecific instructions from the user should prefer the latest version - but sometimes the user wants to tell us that versoin is broken (which happens)21:05
mordredoh - actually ...21:05
mordredmorgan: https://review.openstack.org/#/c/467644/ I just wrote that this morning based on a bug report21:05
mordredmight want to look at that too21:05
morganoh wonderful...21:27
morgankeystone doesn't have a "CURRENT" status21:27
morganall status is "STABLE"21:27
mordredmorgan: yup21:36
morganyeah this is notfun(tm)21:37
mordredmorgan: stable and deprecated iirc21:37
mordredmorgan: the entire enchilada is here: https://review.openstack.org/#/c/459405/18/guidelines/consuming-version-discovery.rst21:38
morgannow i need to figure out a couple things... but it's mostly in tests now... being wonky due to the next thing21:38
morganhttps://www.irccloud.com/pastebin/UsVj0v82/21:38
mordredcovers the keystone stable case and all the rest of it21:38
mordred(and can use review by smart people - especially smart people who are working on version discovery :) )21:38
mordredmorgan: yup- that looks about right21:39
morganhaha... oi i picked a rough one21:40
morgani should have gone with like update_user :P21:40
openstackgerritMorgan Fainberg proposed openstack-infra/shade master: First Pass: De-client-ify list_users  https://review.openstack.org/46778421:40
morganWIP, but i can't lose progress this way21:41
mordredmorgan: well - nice thing about picking a rough one first is you get all the plumbing done21:41
morgani have a RFE for git-review *and* zuul, 1) --WIP, which auto sets WIP mode, or similar when submitting, and in zuul, don't execute if in WIP *except* with a specific comment posted. though order of operations is a bit rough here because how notifies from gerrit work21:42
morganthere should be a "don't run tests unless i explicitly ask" mode for code pushes to gerrit...21:42
* morgan tries to figure out how to get there.21:42
morganworkflow-wise (not implementation wise)21:42
mordredmorgan: yup - that's actually been a long-standing request - we kind of had it WAY back in the day when we had a gerrit WIP plugin21:47
mordredbut since we upgraded to 2.6 (maybe 4 years ago) the WIP status in our gerrit is just an openstack local config setting so we've been avoiding adding the flag to git-review since there are other git-review users21:48
mordredBUT ...21:48
mordredwe're getting closer to actually getting WIP landed upstream21:48
mordred(if you think convincing openstack people about features is hard ...)21:48
mordredand as soon as that's a thing with an interface that other gerrit users can have too - I believe we'll all do a parade and dance in the streets with excitement - cause it'll mean a --wip flag to git-review should be totes happymaking21:49
mordred(this is one of those VERY long dependency chain hells)21:49
slaweqmordred: one more thing about designate zones22:02
slaweqitlooks that it's working only for v2 API22:02
slaweqso I will do it with v222:02
mordredwow. hahahaha22:03
slaweqI hope tomorrow I will push this patch to review22:03
mordredslaweq: so we have half a v1 and half a v2 support currently?22:03
slaweqzones are not available for v1 api (there are domains in v1 only)22:03
slaweqin designateclient it's in v2 directory also: https://github.com/openstack/python-designateclient/tree/master/designateclient/v222:04
slaweqbut quick look on designate client and I think that recordsets are using v2 also22:05
mordredcool - well, supporting v2 is more important than v1 anyway - so if we're doing v2 \o/22:05
slaweqso we have only v2 used because it's only things from designate in shade currently (or I missed something)22:05
slaweqso should be fine with v2 only22:05
slaweqI will push patch and You will see it22:05
mordredya. totally agree. if someone shows up who is dying without v1 support, we can talk about it then22:05
mordredexcellent22:05
mordredthanks!22:06
slaweqbut tomorrow - I need to go sleep now :) It's after midnight for me now22:06
slaweqbye22:06
slaweqand thx for help22:06
*** slaweq has quit IRC22:08
*** ioggstream has quit IRC22:11
mordredthank you!22:11
*** gouthamr has quit IRC22:32
*** squid has joined #openstack-shade22:32
*** squid is now known as calebb22:32
*** gouthamr has joined #openstack-shade23:04
openstackgerritOpenStack Proposal Bot proposed openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/46742823:11
openstackgerritMorgan Fainberg proposed openstack-infra/shade master: First Pass: De-client-ify list_users  https://review.openstack.org/46778423:57

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