Wednesday, 2017-01-18

htaccessmordred: thanks, feel free to ping me if you want a user perspective, I'm the person who requested the ability to setup vpns on our cloud, we use them extensively and i do everyhting else with ansible so having to go out of band to achieve vpn setup is a bit of an annoyance00:07
htaccessbut i fully understand the issue around this and totally undestand if the answer ends up as "no" :)00:08
htaccesss/ability to setup vpns on our cloud/ability to setup vpns on our cloud using ansible/00:09
*** stevemar has quit IRC01:27
*** stevemar has joined #openstack-shade01:29
*** gouthamr has quit IRC03:28
openstackgerritAndy Botting proposed openstack/os-client-config: Add support for Murano  https://review.openstack.org/42166804:56
openstackgerritAndy Botting proposed openstack/os-client-config: Add support for Murano  https://review.openstack.org/42166805:02
openstackgerritAndy Botting proposed openstack/os-client-config: Add support for Murano  https://review.openstack.org/42166805:10
*** abregman has joined #openstack-shade05:55
*** yfried has joined #openstack-shade06:26
*** dfflanders has quit IRC07:29
*** abregman has quit IRC08:27
*** abregman has joined #openstack-shade08:29
*** yfried has quit IRC08:32
*** abregman has quit IRC08:50
*** abregman has joined #openstack-shade08:53
*** ioggstream has joined #openstack-shade09:08
openstackgerritRoberto Polli proposed openstack-infra/shade: Add Neutron Network model.  https://review.openstack.org/42175309:11
fricklerwhen will there be a new release of shade?09:19
fricklerI'm working in a cloud now where availability_zone=nova isn't available. would it seem reasonable to add a default_az variable that would override the "nova" default per cloud? that would save me from having to specify this on every server creation09:22
*** dfflanders has joined #openstack-shade09:26
clarkbfrickler: sounds like the sort of thing that would be good in os-client-config?09:27
clarkb(also I think there is a nova setting on the cloud side that you can set to have it pick a default az, not useful if you don't manage the cloud)09:27
fricklerclarkb: yes. and in fact I don't manage that cloud09:58
*** larainema has quit IRC10:06
*** cdent has joined #openstack-shade10:58
*** dfflanders has quit IRC11:05
*** abregman is now known as abregman|afk11:39
*** ioggstream has quit IRC11:57
*** yfried has joined #openstack-shade12:46
*** jamielennox is now known as jamielennox|away12:59
*** ioggstream has joined #openstack-shade13:13
*** jamielennox|away is now known as jamielennox13:19
Shrewsmordred: took a quick-ish pass at 415739. best I could do before finishing my first coffee13:26
*** abregman|afk is now known as abregman13:28
Shrewsmordred: i don't mind the large upload method, but would be helpful to break it up with comments  :)13:28
*** yfried has quit IRC13:36
*** larainema has joined #openstack-shade13:53
Shrewsmordred: fwiw, i like this new async adapter14:08
*** gouthamr has joined #openstack-shade14:13
frickleris there a different channel for os-client-config or is it on-topic here? if I have two cloud definitions differing only in the project name, is there a way to deduplicate all the auth and other stuff?14:22
*** abregman is now known as abregman|mtg14:28
*** yolanda has quit IRC14:40
*** yolanda has joined #openstack-shade14:41
mordredfrickler: os-client-config in #openstack-sdks - or here (if you want occ features ultimately you'll want to wind up talking to me)15:05
mordredfrickler: for az - and other defaults - we've chatted a few times about adding general support for default values - default flavor and image and network all spring to mind as things people might want to set in a config file per-cloud15:07
mordredfrickler: for the other thing - no, there isn't a way to dedup that info - but I agree it would certainly be nice if there was15:08
mordredfrickler: that said - we do merge auth dicts, so you could just leave project out of the auth dict, and when you do the create you could do cloud='foo', auth={project_id='bar'} and I'm 95% sure it'll work15:09
fricklermordred: the idea would be that I would just need to change the cloud parameter in ansible:os-server for creating a server in one project or the other. or just export OS_CLOUD and run my openstack cli commands for either15:11
*** openstack has joined #openstack-shade15:17
*** thingee has quit IRC15:18
*** ioggstream has quit IRC15:18
*** thingee has joined #openstack-shade15:19
*** Matias has quit IRC15:19
*** dtroyer has quit IRC15:19
*** mgagne has quit IRC15:19
*** DuncanT has quit IRC15:19
*** kong has quit IRC15:19
*** Matias has joined #openstack-shade15:22
*** mgagne has joined #openstack-shade15:22
*** dtroyer has joined #openstack-shade15:22
*** Matias has quit IRC15:22
*** Matias has joined #openstack-shade15:22
*** mgagne has quit IRC15:23
*** mgagne has joined #openstack-shade15:23
*** mgagne is now known as Guest5853115:23
*** DuncanT has joined #openstack-shade15:26
*** kong has joined #openstack-shade15:26
mordredfrickler: yah. we should figure out support for that - right now it's just copy-paste15:35
mordredfrickler: well - I say that - pyyaml does support yaml anchors15:36
mordredso you could define your first auth dict with a named anchor and then just refer to that in the second copy15:36
mordredone sec - lemme get an example15:36
mordredfrickler: https://markusholtermann.eu/2016/04/reference-variables-in-ansible-yaml/15:37
mordredfrickler: the two things he shows at the bottom of that should work without any effort on occ's part15:38
fricklermordred: cool, let me try that15:38
mordredfrickler: http://paste.openstack.org/show/595410/15:44
mordredfrickler: got that to work15:44
mordredfrickler: also this: http://paste.openstack.org/show/595413/15:46
mordred(the original example I gave doens't really show how it works with dict overriding well I dont think)15:47
mordredfrickler: https://learnxinyminutes.com/docs/yaml/ has better examples15:47
ShrewsTIL new yaml things15:51
fricklermordred: fine, that works for me, too. after finding out that despite vim syntax highlighting suggesting otherwise, using "-" in anchor names leads to strange effects :-/15:53
fricklermordred: thanks alot15:54
*** abregman|mtg has quit IRC15:58
*** abregman has joined #openstack-shade16:01
*** larainema has quit IRC16:06
mordred\o/16:22
ioggmordred: I was watching the _upload_large_object method. does it make sense to put it in a separate file all that upload stuff ?16:43
ioggmordred: it resembles some twisted|tornado library ;)16:44
mordrediogg: :)16:45
mordrediogg: I've got a new rev coming that breaks it up a little bit more16:45
mordred(and adds comments)16:45
ioggmordred: it's some time I'm not into concurrent stuff so I avoid technical comments, but if that only applies to swift, it could have sense16:46
*** abregman has quit IRC16:47
mordrediogg: yah -it's really only for uploading large files to swift when they have to be broken into chunks. it's complex enough I really hope we don't have to use the same technique elsewhere :)16:47
mordredthere - that might be a little more readable: remote:   https://review.openstack.org/415739 Replace SwiftService with direct REST uploads16:48
Shrewsmuch more  ++16:49
ioggShrews: is there some neutron gui to validate the network model.rst?16:56
mordrediogg: ooh! thanks for digging in on the network normalization16:58
ioggmordred: sometimes you have to waterfall  ;) model before17:00
mordredhtaccess, Shrews: ok - I chatted with some folks, and I think accepting patches to add support for vpnaas would be fine. the project isn't dead, it's just in some administrative/governance limbo and we expect it to become 'official' again17:00
ioggrcarrillocruz: are you ansible-ing on openstack modules?17:01
mordredhtaccess: I'll likely be extra strict on it17:02
openstackgerritMikhail S Medvedev proposed openstack-infra/shade: Prevent tight poll loops when *_AGE are zero  https://review.openstack.org/42212617:25
openstackgerritMerged openstack/os-client-config: Add support for Murano  https://review.openstack.org/42166817:32
Shrewsiogg: umm, don't know, but i doubt it17:34
ioggShrews: wait=0 ?17:34
Shrewsiogg: neutron gui17:34
ioggShrews: ah, ok ;)17:34
ioggShrews: as I'm working on the rbac stuff I'd avoid big patches and I'm stop&go with acknowledged small patches17:35
mordredShrews: ooh! TypeError: range() integer step argument expected, got float.17:57
*** yolanda has quit IRC18:06
*** yolanda has joined #openstack-shade18:06
*** yfried has joined #openstack-shade18:32
ioggmordred: question on _iterate_timeout. with wait=0 it really seems a spin-lock18:36
mordrediogg: yah - it kind of is - but in the single-threaded context, there isn't much else to do while waiting18:37
ioggmordred: ok, but I'm just ogging the cpu waiting for a timeout18:39
mordredyah - I was actually thinking of having the unit tests set that delay to 0.1 seconds and see how that goes :)18:40
ioggmordred: while in all the _iterate_timeout usage I'm checking for nonzero18:40
ioggmordred: I'm not very much into shade, so I'm not pushiing  for a  specific18:41
ioggsolution18:41
mordredtotally - it's ... I think about this every time I run unittests and my fan turns on18:42
mordredbut then then unittests are done and I stop thinking about it :)18:42
ioggmordred: but the patch which controls everywhere if the calls uses zero18:42
ioggit seemed to me that it's worth checking18:43
iogga single solution in18:43
iogg_iterate_timeout18:43
ioggbut that's just my 2ยข18:44
ioggmorded now bye my kid is assaulting me18:44
ioggwithbattle calls :DDDD18:44
mordred\o/18:44
*** yfried has quit IRC18:48
*** iogg has quit IRC18:49
clarkbfwiw if you use time.sleep(0) that is used to force a context switch18:50
clarkbso it might wait more busily than if you slept for a second BUT it should relinquish the cpu to anything else that needs it too18:50
mordredclarkb: nod18:54
*** iogg has joined #openstack-shade19:08
*** cdent has quit IRC19:14
*** iogg has quit IRC19:20
*** abregman_ has joined #openstack-shade19:26
*** iogg has joined #openstack-shade19:28
openstackgerritMonty Taylor proposed openstack-infra/shade: Replace SwiftService with direct REST uploads  https://review.openstack.org/41573919:50
mordredShrews, clarkb: ^^ that should fix the real error - I'm mildly worried that the -legacy job has gone awol again - we'll see when it returns from that19:53
mordredbut there's a TON of unrelated failures: http://logs.openstack.org/26/422126/1/check/gate-shade-dsvm-functional-legacy/5aa292c/console.html19:54
mordredabout resource not found - which reminds me of the last time stuff broke because of the sdk problem19:54
mordredmorgan: ^^ you too - in case you have thoughts/ideas19:54
mordredI've got a nodepool job for holding a legacy node19:54
morganmordred: hey19:55
morganoh wow, yeah that looks ugly19:56
morganlooks like soething wonky with collecting data from keystone (wtf?)19:56
Shrewshrm, resource scarcity19:56
morganmordred: oh look it is getting 404s, either the setup is broken or something broke so it is constructing bad urls now19:57
morganstevemar: was a ksa release just done?19:57
morganout of curiosity?19:57
morganand/or keystoneclient and/or other such libs19:57
mordredmorgan: SOOOOOOOOOO20:02
mordredmorgan: I just logged in and can run list_users with shade against that devstack just fine20:02
mordredmorgan: I'm re-running the tests - but I'm starting to wonder if maybe race condition?20:03
morganmaybe?20:05
morganmaybe we need some extra setup time?20:05
morganor we're stomping across tests from one testcase to another20:05
morganfor some reason20:05
mordredmorgan: either one of those would be weird things to have just started20:06
stevemarmorgan: ksa and ksm yes20:06
stevemarmorgan: and pycadf20:06
stevemarksc will be next week20:06
morganmordred: ^ we did have a ksa release, just as a point20:06
mordredthe legacy job runs on stable/newton20:07
mordredstevemar: so - it's _possible_ that the ksa release maybe borked something for stable/newton?20:07
mordred(or the ksm one - more likely I'd guess)20:07
Shrewsmordred: umm, we don't install the latest things for stable/newton. we're limited by what was released at that point20:07
stevemarmordred: eh? they were relatively the same as last weeks20:08
mordredstevemar: grasping at straws currently - the jobs started failing today20:08
Shrewsmordred: even devstack should be limited to newton timeframe20:08
mordredstevemar: http://logs.openstack.org/26/422126/1/check/gate-shade-dsvm-functional-legacy/5aa292c/console.html is a log showing the failure20:08
mordredShrews: yah. agree.20:08
mordredshade.exc.OpenStackCloudException: Failed to list endpoints (Inner Exception: The resource could not be found. (HTTP 404) (Request-ID: req-809ce7ae-4844-47fc-83e2-0b97dc1d23a3))20:09
mordredboom. broke again20:09
stevemarmordred: http://logs.openstack.org/53/421653/1/check/gate-releases-tox-list-changes-ubuntu-xenial/4ffabac/console.html#_2017-01-18_04_15_11_477097 and http://logs.openstack.org/54/421654/1/check/gate-releases-tox-list-changes-ubuntu-xenial/69531c7/console.html#_2017-01-18_04_19_47_398049 for things that went into ksm/ksa20:09
stevemarmordred: do you test whatever the latest master is for newton or whatever is the latest release?20:11
stevemarmordred: we did backport some changes into stable/newton for keystone libs20:11
mordredstevemar: we just tell devstack-gate to use stable/newton - so I think latest tip of stable/newton20:12
morganwhich could mean we snagged a backport causing issues20:12
morganor it's a race.20:12
mordredWELL20:12
morganand we just happened to hit it today20:12
mordredif I run one test over again20:12
mordredit breaks - with no concurrency20:12
mordredand it breaks on list_endpoints :)20:13
morganok so lets say no race20:13
Shrewskeystoneauth1==2.12.220:13
Shrewskeystonemiddleware==4.9.020:13
Shrewsthose seem right?20:13
morganbut shade can list endpoints directly?20:13
morganjust not in the test?20:13
* morgan blinks20:13
stevemarShrews: those are the latest stable, not from tip thogh20:13
morganstevemar: keystone backports?20:14
morgani don't remember anything particular20:14
morganthat would be related.20:14
stevemarmorgan: right, just the stuff thta doesn't choke on binary stuff in the request/response20:15
morganmordred: you have a broken devstack right?20:15
morgancan we get more output, the URL for the .request() call?20:16
mordredWOAH it just got weirder20:16
Shrewsunpossible20:16
morganmordred: ?20:16
mordredone sec- paste coming20:16
morgankk20:16
mordredhttp://paste.openstack.org/show/595464/20:17
mordredstevemar, morgan, Shrews: ^^ the first form, using the operator_cloud shortcut - works - the second form, getting a cloud config and passing to the constructor - doesn't wor20:17
mordredwork20:17
mordredthe output is: http://paste.openstack.org/show/595465/20:18
*** Matias has quit IRC20:18
morganso.. bad keystone endpoint somehow?20:19
morganwhen built from config20:19
morgan*blinks*20:19
mordredbut why is one constructor form breaking? openstack_cloud is _supposed_ to be syntactic sugar around a call to OperatorCloud20:19
Shrewswhat the fudge20:20
mordredmorgan: http://paste.openstack.org/show/595467/ added in printing of the cloud_config object20:20
morganif you run the second form first, does it pass?20:20
mordrednope20:20
mordredthe second form always fails20:20
mordredhttp debug output coming20:20
* Shrews points out that there was a recent occ release20:21
mordredhttp://paste.openstack.org/show/595468/20:21
mordredShrews: yup. reverting occ fixes it20:22
mordrednow ... WHY?????20:22
morganhttp://198.72.124.18/identity/v2.0/endpoints vs http://198.72.124.18/identity_v2_admin/v2.0/endpoints20:22
morganthe first one is failing20:22
Shrewsmordred: because Trump?20:22
morganthe second one is passing20:22
mordredWEIRD20:22
morganyou're missing identity_v2_admin in the failing one you're getting just /identity/20:23
morgansince /identity/ is probably v3 only20:23
Shrewsmorgan: i suspect something with _validate_auth_ksc()20:23
morganso we mucked with something that changed the resulting endpoint when called via config?20:23
morganthis screams to me v2 vs v3 somewhere20:24
*** Matias has joined #openstack-shade20:24
mordredk. found it20:24
mordredstill don't know WHY - but I found the change that breaks it20:24
Shrewsmordred: which?20:25
morganShrews: yah.20:25
morganShrews: now i am curious20:25
Shrewsfa4e1bd maybe? the suspense is killing me20:26
openstackgerritMonty Taylor proposed openstack/os-client-config: Revert "Fix interface_key for identity clients"  https://review.openstack.org/42222220:26
mordredthat ^^20:26
mordredtotally is the thing that breaks20:26
morgani can tell yuou why20:27
mordrednow - I think it's very much worth figuring out why shade.operator_cloud works and shade.OperatorCloud doesn't - and why that patch breaks stable/newton20:27
mordredyay!20:27
morganbecause we have v2 split off from normal identity endpoints20:27
morganso you just basically exempted it from any endpoint_type logic20:27
morganyou're falling through to just "identity"20:27
morganand that is v3 only afaict20:27
mordredahhhhhh20:27
morganthis is a v2/v3 compat thing20:27
morganso you can test both with v2 enabled20:28
mordredso I'd need to put in an 'if api_version == 3, blah'20:28
*** abregman_ has quit IRC20:28
morganyep. and still fall to endpoint_type if version == 220:28
morganit's a wonky thing due to our setup for v2 vs v320:28
morganhopefully it doesn't run into v3 issues there, but i think it's sane (though i'd jsut 2x check that /identity/ is in-fact v3 only20:29
*** yfried has joined #openstack-shade20:29
Shrewsmordred: we should have caught this in our -libs-nv job, right? Doesn't that pull OCC master? Or is it just the released version20:30
Shrews?20:30
Shrewshrm, that job was still passing today20:31
Shrewsoh, it also needs to go against v220:31
morganyah20:31
mordredit only seems to break for stable/newton20:31
Shrewsdammit. do we need ANOTHER job20:31
mordredyah20:31
Shrews?20:31
morgannot sure why only stable/newton is busted20:31
mordredstable/newton is where we force testing as if the cloud does not have v3 endpoints20:32
Shrewsneed a -legacy-libs-nv20:32
morganahhhhh20:32
morganthat would explain it then20:32
Shrewsour job matrix is bigger than your job matrix20:33
mordredour job matrix DOES catch ALL of the bugs20:34
mordredsometimes at unfortunate times20:34
mordredbut it does eventually catch all of them20:34
Shrewsi'm actually quite proud of that20:34
morganshade and rally are really the "integrated gate"++ in catching things20:35
Shrewseven outside of OpenStack20:35
Shrewswe've caught some ansible bugs20:35
Shrewsanyone want the esteemed honor of adding the new job?20:37
mordredShrews: I can get it20:39
Shrewswell, hrm. that doesn't make sense since the idea is to test against unreleased versions of the clients. perhaps we should just change the current legacy job to pull the latest shade/occ?20:39
Shrewsmordred: what do you think? i mean, we always tell folks to upgrade to the latest shade to get better compatibility, so....  *shrug*20:41
mordredShrews: oh - well - so there's another thing20:41
mordredShrews: which is that we're not ACTUALLY testing what we think we are in the -libs job20:42
Shrewsneat20:42
mordredShrews: because we don't install the master versoins of the libs into our functional venv20:42
Shrewssuch fun. fun overload20:42
mordredShrews: what we're testing is do the master versions of those libs work as part of devstackas part of the install20:42
mordredyah20:42
mordredI'll fix that when I add the other job20:42
Shrewsk k20:43
Shrewsi thought that job passed WAAAAAAY to often20:43
Shrews:)20:43
Shrewsi mean, this is OpenStack after all20:43
* morgan gets ready to go back to coding mode20:44
morganunless you need more eyes on things20:45
morgani'd like to get to the point where i can pivot over to restification in shade20:45
morganbut while i'm thinking in debug/code review mode, happy to look at more things20:45
Shrewsmoar REST ++20:46
morganShrews: i know right?!20:53
morgankeystone will be a bit weird to do rest since v2 and v3...20:53
Shrewsmorgan: embrace the fun. feel the hate grow within you20:54
morganlol20:55
Shrewshttp://i0.kym-cdn.com/entries/icons/original/000/017/886/download.jpg20:55
*** iogg has quit IRC20:57
mordredmorgan: otoh - you get to revel in how enjoyable it is to write tests with jamielennox's requests_mock21:14
* mordred hands jamielennox a box of cupcakes21:15
mordredmorgan: now that swift is done- everything else uses Session already - which means that just rewriting unittests to use requests_mock instead of mocking client libs totally works and is a fun first step in the restification21:16
* Shrews understands that jamielennox is headed to Durham to visit mordred's old stomping grounds with olaph21:17
Shrewstoo bad i'll be snowboarding in WV when he visits21:17
* olaph stomps21:17
* Shrews stomps harder21:17
mordredstomp stomp stomp21:18
morganmordred: hehe21:25
morganmordred: ++21:25
* morgan makes coffeeeeeeeee21:25
*** jamielennox is now known as jamielennox|away21:26
*** gouthamr has quit IRC21:34
morganShrews: mmmm snowboarding21:35
*** yfried has quit IRC21:48
*** gouthamr has joined #openstack-shade21:58
*** yfried has joined #openstack-shade22:07
*** jamielennox|away is now known as jamielennox22:10
*** jamielennox is now known as jamielennox|away22:24
*** yfried has quit IRC22:27
openstackgerritMonty Taylor proposed openstack-infra/shade: Add helper script to install branch tips  https://review.openstack.org/42229322:43
openstackgerritMonty Taylor proposed openstack-infra/shade: Add helper script to install branch tips  https://review.openstack.org/42229322:55
openstackgerritMerged openstack/os-client-config: Revert "Fix interface_key for identity clients"  https://review.openstack.org/42222223:19
*** Matias has quit IRC23:24
*** stevemar has quit IRC23:24
*** Matias has joined #openstack-shade23:24
*** stevemar has joined #openstack-shade23:24
*** larainema has joined #openstack-shade23:34

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