Thursday, 2017-09-07

*** slaweq has joined #openstack-shade00:39
*** slaweq has quit IRC00:44
*** rods has quit IRC01:16
*** thrash is now known as thrash|g0ne01:27
*** slaweq has joined #openstack-shade01:40
*** slaweq has quit IRC01:45
*** slaweq has joined #openstack-shade02:41
*** slaweq has quit IRC02:46
*** slaweq has joined #openstack-shade03:42
*** slaweq has quit IRC03:47
*** gkadam has joined #openstack-shade03:49
*** yolanda has quit IRC04:15
*** gouthamr has quit IRC04:31
*** slaweq has joined #openstack-shade05:44
*** slaweq has quit IRC05:49
openstackgerritJulia Kreger proposed openstack-infra/shade master: Migrate additional machine tests  https://review.openstack.org/50157606:16
*** yfried has joined #openstack-shade06:42
*** slaweq has joined #openstack-shade06:45
*** slaweq has quit IRC06:50
*** umbSublime has left #openstack-shade06:56
*** gkadam is now known as gkadam-afk07:03
*** slaweq has joined #openstack-shade07:11
*** slaweq has quit IRC07:16
*** ioggstream has joined #openstack-shade07:54
*** rods has joined #openstack-shade08:08
*** slaweq has joined #openstack-shade08:12
*** slaweq has quit IRC08:17
*** slaweq has joined #openstack-shade09:13
*** rods has quit IRC09:15
*** slaweq has quit IRC09:18
*** gkadam_ has joined #openstack-shade09:34
*** gkadam-afk has quit IRC09:36
*** rods has joined #openstack-shade10:01
*** slaweq has joined #openstack-shade10:14
*** slaweq has quit IRC10:19
*** gkadam__ has joined #openstack-shade11:05
*** gkadam_ has quit IRC11:07
*** slaweq has joined #openstack-shade11:15
*** ioggstream has quit IRC11:17
*** slaweq has quit IRC11:20
*** rods has quit IRC11:23
*** rods has joined #openstack-shade11:23
*** rods has quit IRC11:24
*** rods has joined #openstack-shade11:24
*** rods has quit IRC11:25
*** rods has joined #openstack-shade11:25
*** thrash|g0ne is now known as thrash11:40
*** slaweq has joined #openstack-shade12:16
*** slaweq has quit IRC12:21
*** rods has quit IRC12:23
*** rods has joined #openstack-shade12:23
*** rods has quit IRC12:28
*** gkadam__ has quit IRC12:40
*** slaweq has joined #openstack-shade13:17
*** slaweq has quit IRC13:22
*** gouthamr has joined #openstack-shade13:30
*** slaweq has joined #openstack-shade13:33
*** slaweq has quit IRC13:33
*** yfried has quit IRC14:18
*** slaweq has joined #openstack-shade14:34
*** slaweq has quit IRC14:39
openstackgerritMonty Taylor proposed openstack-infra/shade master: Convert test_baremetal_machine_patch to testscenarios  https://review.openstack.org/50176815:19
mordredTheJulia: your patch looks great - I made this ^^ just to illustrate use of testscenarios for such a thing, in case that was a thing you weren't aware of15:19
TheJuliamordred: oohhhhh15:21
TheJuliamordred: although some of those fields are not changable, nor even exist if I think15:22
TheJuliaoh wait15:23
TheJuliaI get it15:23
mordredit's a magic thing- the first param in the list is what gets appended to the test method name - the other things are added to the test as self attributes15:24
mordredpile of black magic15:24
TheJuliaI was just about to say it looks like a pile of black magic15:25
mordred:)15:25
mordredit can be handy for cases like this where it's one test with a pile of different options15:26
TheJuliayeah, it makes ton of sense15:26
mordredTheJulia: I'm happy to either land it if it reads well to you or abandon it and keep the tests as you had them - whichever works for me15:26
TheJuliait reads really well to me, I do feel like putting a note in describing what is occurring, but it just my habit to be verbose for context.  I can do that in a later rev15:27
*** slaweq has joined #openstack-shade15:35
mordredkk cool15:38
*** slaweq has quit IRC15:40
openstackgerritMerged openstack-infra/shade master: Migrate additional machine tests  https://review.openstack.org/50157616:18
*** slaweq has joined #openstack-shade16:37
*** slaweq has quit IRC16:41
TheJuliaout of curiosity, anything shade specific discussions at the ptg?16:44
TheJulias/anything/any/16:44
mordredTheJulia: there's gonna be some discussions on tuesday I tihnk in the OSC room with dtroyer16:47
mordredTheJulia: main topic up for in-person discussion for htat is, I believe, my proposal to merge openstacksdk and shade :)16:48
mordredTheJulia: I also expect to sit down with samueldmq and chat about oaktree at some point16:48
TheJuliamordred: I just noticed the etherpad was empty :\  hence why I asked16:49
SamYaplemordred: ive been telling people to use shade over openstacksdk for quite a while now. so +2 to that16:52
samueldmqmordred: o/16:55
samueldmqthat'd be great16:55
mordredSamYaple: dunno if you saw my mailng list post froma while back, but basic issue is that openstacksdk isn't even an official project, but its name makes people think it is - plus the folks who were funding the devs to work on it have a much lower level of interest in funding that now16:55
mordredSamYaple: otoh - there actually IS some good stuff in there that I think can improve some of what we're doing at the shade level16:56
SamYaplei did not see that ML post, but i can believe that16:56
SamYapleit shocks alot of people coming into openstack that there is no one-true SDK for it16:56
mordredand - if we made a new object like "openstack.cloud.OpenStackCloud" that had all the methods we have in shade - but with the various lessons we've learned but can't fix because of backwards compat fixed16:57
SamYaplei normally point them at shade and they are happy16:57
SamYaple.... would that mean scraping shade?16:57
mordredthen we couldmake shade.OpenStackCloud a thin-wrapper around that objet that just swaps defaults and whatnot to keep people using it through the shade namespace from breaking16:57
SamYapleoh i see. hmmm16:58
SamYaplei mean i would like to learn from shade mistakes for sure...16:58
mordredSamYaple: it's a question - do we take it over as a low-level library and make the needed changes so that it could essentially take th eplace of shade/_adapter.py but keep the two separate libs with a requirements relationship16:58
mordredor do we merge the two but make sure we provide a seamless upgrade path for shade users16:59
SamYaplei like the idea of being able to rework shade as openstacksdk and then provide a shade compat lib for openstacksdk16:59
mordredwith a shim layer that does argument default or argument order translations but otherwise is passthrough16:59
SamYaplefix "endpoints", have a more unified way to pass context and objects, etc16:59
mordredexactly16:59
mordredwe learned a LOT in the last few years17:00
SamYapleindeed17:00
mordredbut also not breaking existing users is VERY important17:00
SamYaplethat was the whole shade mission, yea17:00
samueldmqmordred: quick question on the create endpoint sorcery17:01
* SamYaple hides17:01
mordredif shade.OpenStackCloud continues to exist and work as today, and we make a new thing called openstack.cloud.OpenStackCloud() that, once you have it is almost identical to shade.OpenStackCloud but has a few diferent defaults or argument orders17:01
samueldmqdoes EndpointCreate task get args on both v2.0 or v3 format and do the calls accordingly?17:01
mordredthen we can make a doc which is "if you want to migrate to use the new namespace, make these 12 changes"17:01
SamYaplesamueldmq: it recieves v2 OR v3 args, if its v2 on v3 it will make 3 calls17:02
mordredyes. that's right17:02
samueldmqSamYaple: yeah, but the 3 calls is in the for loop17:02
samueldmqfor args in endpoint_args:17:03
samueldmqso EndpointCreate is called 3 times anyways17:03
SamYapleyea good point17:03
mordredoh - yes17:03
samueldmqso it gets args in either v2.0 or v3 formats17:03
mordredsorry - misunderstood the question - yes - if the backend is v3, EndpointCreate will be called 3 times17:03
mordredif the backend is v2 it will only be called once17:03
samueldmqit can get things like 'adminurl': 'https://4560aab8be50452994939569b92d80d7.example.com/'17:03
samueldmqand also 'interface': 'public', 'url': 'https://3d42226d149e41b38b12b036cd937093.example.com/'17:04
SamYaplemordred: if backend is v3 it will be called 4 times, once with the v2 args then three times with the v3 args17:04
mordredSamYaple: wow. that's amazing17:04
samueldmqEndpointCreate is the cherry on the cake :-)17:04
SamYaplei could be wrong, its been a while since i looked at it17:04
SamYapleall i hear is "openstacksdk"17:05
samueldmqSamYaple: mordred: thanks I will take a deeper look at it (again)17:05
samueldmqneed to be careful when touching catalog code17:06
mordredSamYaple: yah - unfortunately the way its structured makes it unsuitable for being used as the rest layer for either shade or python-openstackclient17:06
SamYapleyup17:07
SamYaplei say screw v2! let it burn!17:07
mordredSamYaple: which is one of the other reasons for proposing merging the efforts -so that we can go in and make a few invasive breaking changes but do so in a way that makes it VERY suitable for shade/osc17:07
*** thrash is now known as thrash|biab17:07
mordredwhich, from my pov, is 'ok' as there is not yet a v1 of sdk17:08
SamYapleyea ive been wanting a way to do some breaking shade changes that didnt involve create_endpoint2()17:08
mordredSamYaple: https://review.openstack.org/#/c/501438/1/SHADE-MERGE-TODO.rst is what I've written up so far - that's also at the end of a long stack of non-functional patches that make most of the needed sdk changes17:09
SamYaple+117:11
SamYapleyou know, even with the mistakes that are being carried forward.... shade is pretty clean still17:11
mordredSamYaple: one of the wins is that sdk has a much richer system availble for doing what we do in shade/_normalization.py - and I think theirs allows de-normalizing back to the parameters the cloud knows about17:12
SamYapleif we could button up a few of the glaring ones, it would be really nice17:12
mordredyup17:12
SamYaplei would like to see an improvement and standardization on how we pass objects around. if i want to create a user and have a domain and project objects then it should be a single PUT, all operations should be like that17:13
SamYaplewe have patchy support for that right now17:13
SamYapleim getting kind of excited17:14
*** gouthamr has quit IRC17:33
*** slaweq has joined #openstack-shade17:38
SamYaplemordred: just promise me in openstacksdshade we are going to disable v2 syntax on v3 api17:41
SamYaplei would even opt for entirely diffrent functions17:42
*** slaweq has quit IRC17:43
samueldmqSamYaple: mordred: our code is weird for endpoints17:45
samueldmqsee https://github.com/openstack-infra/shade/blob/master/shade/operatorcloud.py#L92117:46
samueldmqthen L937, then L94817:46
samueldmqL948 will never evaluate to true17:46
SamYaplesamueldmq: not true!17:47
SamYaplesee L94717:47
samueldmqSamYaple: aha!17:48
SamYapleyoure welcome17:48
samueldmqSamYaple: thanks :)17:48
SamYaplevariable reuse ftw!17:48
SamYaple(sorry bout that)17:48
samueldmqI'm getting old maybe17:48
samueldmqno worries17:48
SamYapleno its shitty code17:48
SamYapleim sorry iwrote it17:48
*** thrash|biab is now known as thrash17:57
*** gouthamr has joined #openstack-shade18:01
*** slaweq has joined #openstack-shade18:39
*** olaph has quit IRC18:40
*** olaph has joined #openstack-shade18:41
*** slaweq has quit IRC18:43
*** slaweq has joined #openstack-shade19:12
mordredSamYaple: I'm sorry I asked you to write it too19:36
*** olaph1 has joined #openstack-shade19:40
*** olaph has quit IRC19:42
SamYaplemordred: are you trying to say you should have asked someone else to write it instead of me?21:09
SamYapledo you think youre better than me? NOBODY IS BETTER THAN ME21:09
mordred:)21:12
*** slaweq has quit IRC21:27
*** slaweq has joined #openstack-shade21:27
*** slaweq has quit IRC21:32
*** slaweq has joined #openstack-shade21:41
*** slaweq has quit IRC21:43
*** slaweq has joined #openstack-shade21:44
*** slaweq has quit IRC21:44
*** slaweq has joined #openstack-shade21:46
*** slaweq has quit IRC21:56
*** gouthamr has quit IRC23:09
*** slaweq has joined #openstack-shade23:58
*** gouthamr has joined #openstack-shade23:59

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