Monday, 2017-07-10

*** thorst has joined #openstack-powervm00:02
*** thorst has quit IRC00:08
*** k0da has joined #openstack-powervm00:14
*** k0da has quit IRC00:28
*** thorst has joined #openstack-powervm00:36
*** thorst has quit IRC00:36
*** thorst has joined #openstack-powervm01:52
*** thorst has quit IRC01:56
*** svenkat has joined #openstack-powervm02:04
*** svenkat has quit IRC03:15
*** k0da has joined #openstack-powervm03:26
*** k0da has quit IRC03:33
*** burgerk has joined #openstack-powervm03:33
*** thorst has joined #openstack-powervm03:53
*** thorst has quit IRC03:57
*** burgerk has quit IRC04:36
*** thorst has joined #openstack-powervm05:54
*** thorst has quit IRC05:59
*** k0da has joined #openstack-powervm06:56
*** k0da has quit IRC07:08
*** YuYangWang has joined #openstack-powervm07:42
*** YuYangWang has quit IRC07:47
*** thorst has joined #openstack-powervm07:54
*** thorst has quit IRC08:00
*** k0da has joined #openstack-powervm08:26
*** thorst has joined #openstack-powervm09:23
*** thorst has quit IRC09:28
*** YuYangWang has joined #openstack-powervm09:45
*** openstackgerrit has joined #openstack-powervm10:21
openstackgerritArundhati Surpur proposed openstack/networking-powervm master: Removes unnecessary utf-8 encoding
*** edmondsw has joined #openstack-powervm11:25
*** edmondsw has quit IRC11:25
*** edmondsw has joined #openstack-powervm11:25
*** jwcroppe_ has quit IRC11:28
*** jwcroppe has joined #openstack-powervm11:29
*** thorst has joined #openstack-powervm11:53
*** smatzek has joined #openstack-powervm12:03
openstackgerritArundhati Surpur proposed openstack/networking-powervm master: Removes unnecessary utf-8 encoding
*** svenkat has joined #openstack-powervm12:14
*** svenkat has quit IRC12:21
*** fried_rice is now known as efried12:27
*** svenkat has joined #openstack-powervm12:29
*** mdrabe has joined #openstack-powervm12:29
thorstefried: I think I'm going to have to make a relatively large change for vif plugging  :-(12:34
edmondswthorst why's that?12:54
thorstas we're adding OVS to the REST API, we're hitting some interesting issues.12:54
thorstI think they're right...but they're...interesting.12:54
thorstI'm working through it now, *may* find a way to just do it all in REST.12:55
efriedthorst We knew the changes were going to be substantial.13:06
efriedBut it sounds like maybe you're going in a different direction than expected?13:06
efriedthorst Let's talk it through.13:06
thorstefried: I need to talk to nvcastet a bit more13:08
efriedthorst Yeah, what I fear is nvcastet making decisions that are suboptimal from a REST API perspective.13:08
*** esberglu has joined #openstack-powervm13:09
thorstefried: I'm not sure about that TBH13:16
thorstI think REST is pretty OK13:16
thorstits the backend...but let me think through once I'm out of meetings13:16
*** burgerk has joined #openstack-powervm13:51
*** jwcroppe has quit IRC13:59
*** esberglu has quit IRC14:02
*** esberglu has joined #openstack-powervm14:02
*** kriskend has joined #openstack-powervm14:12
*** jwcroppe has joined #openstack-powervm14:15
*** k0da has quit IRC15:15
*** jwcroppe has quit IRC16:39
*** jwcroppe has joined #openstack-powervm16:47
*** jwcroppe has quit IRC16:49
esbergluefried: edmondsw: See changes 5548 and 5549 to knock out a huge chunk of the skip list (156 lines)17:42
esberglu5548 is good to go17:42
esbergluI want to run 5549 through again to make sure I didn't remove or leave any tests errantly17:42
edmondswesberglu how did you determine which extensions to list in 5548?17:45
*** kriskend has quit IRC18:00
*** kriskend has joined #openstack-powervm18:05
*** kylek3h has joined #openstack-powervm18:11
*** kriskend_ has joined #openstack-powervm18:19
*** kriskend has quit IRC18:19
esbergluedmondsw: There is an openstack command for listing extensions18:55
esbergluopenstack extension list18:55
esbergluThen you can add --network18:55
esbergluTo list only the network extensions18:55
edmondswesberglu check the comments I added in 554818:55
esbergluedmondsw: Yep just looked at them18:55
edmondswesberglu what do you think of that blacklist idea? seems safer18:56
edmondswwould involve that cli you just mentioned18:56
esbergluedmondsw: Would be easier with a whitelist18:56
esbergluThen I can just filter the output of that command18:56
edmondswI think the whitelist leaves us open to not testing things we should be testing if/when something gets added18:57
esbergluThe whitelist would get generated each run18:57
edmondswesberglu maybe I'm not following you18:57
edmondswgenerated how?18:57
esbergluAfter you stack, you can run that command to list all of the enabled api extensions18:58
edmondswthe conf setting is a whitelist... so yes, you'd generate a whitelist each run... but how? I'm suggesting we generate it from running openstack extension list --network and then removing anything from a blacklist that we hardcode18:58
esbergluSo if any new features are added it would have to be a change at the devstack local.conf level18:58
esbergluI think openstack cli has ways to only output what you want18:59
esbergluSo I would only have it output the enabled extensions18:59
esbergluby name18:59
esbergluAnd then concatenate with commas and set it in tempest.conf18:59
edmondsw"if any new features are added it would have to be a change at the devstack local.conf level" doesn't seem like it would necessarily be true19:00
esbergluWell if we needed a change it would be. If a new extension is added that we don't want, we would have to disable it in the local.conf before stacking19:00
edmondswwe don't have anything in local.conf to do with most of the things in that list you've proposed19:00
esbergluAnd if a new extension is added that we do want, it will get picked up when stacking, then it will be present when generating the whitelist19:01
edmondswwhat's the diff between all and the list you've proposed in 5548? what are we actually disabling there?19:01
edmondswand you're saying everythig in that diff is explicitly disabled in our local.conf?19:02
esbergluThe extensions are enabled or disabled when stacking based on all sorts of things IIRC. Some have specific settings, some are side effects of other settings19:03
edmondswesberglu right, that's what I was afraid of19:04
edmondswso something new could get enabled based on some side effect or something, without us needing to do anything in local.conf19:04
edmondswbut we wouldn't be testing it in our CI like we should be19:04
*** k0da has joined #openstack-powervm19:05
edmondswalso it will be more readable to see what we want to disable than what we want to enable, right?19:06
edmondswefried you're welcome to chime in here at any point :)19:06
efriedReading backscroll...19:06
esbergluI think you're worrying to much about the list. This is just a short term solution so that I can start getting rid of tests in the skip list. This is all going away as soon as the devstack generated tempest.conf is up19:06
esbergluWe would just be subject to devstack defaults for enabled/disabled extensions. If it is enabled by default and introduced it either works or breaks us which is what we want either way19:06
esbergluIf it is disabled by default we would never know the difference19:07
esbergluAnd as far as readability19:07
esbergluWe aren't listing the extensions anywhere19:07
esbergluJust going through the output of a command19:07
edmondswesberglu you're listing them with 554819:07
esbergluedmondsw: Yeah I thought we had already determined that we were changing that19:08
esbergluI thought we were arguing white vs blacklist19:08
edmondswbut you're right about this probably being me overthinking things if this is all temporary19:08
edmondswassuming it really is temporary19:08
esbergluHow long "temporary" is depends on how many external changes are needed19:09
esbergluHere's the flow I want to happen19:09
esberglu1) Get devstack to generate a tempest.conf that matches our current tempest.conf19:09
esberglu1a) With the exception being anything that is in our current tempest.conf that shouldn't be19:10
edmondswso you'll change 5548 to use the output of `openstack extension list --network`?19:10
edmondswok, I'm cool with that19:10
esberglu2) While that is going on, start working through the skip lists19:10
esbergluand see what else we can get rid of/identify any bugs19:10
efried...and exclude anything in a blacklist of network extensions, said blacklist maintained... where?  how?19:11
esbergluefried: That's why I wanted a whitelist. The blacklist just adds one more piece to the puzzle19:11
edmondswefried in some CI code19:11
efriedesberglu I don't see how.19:12
efriedEither we're hardcoding the whitelist, or we're hardcoding the blacklist.19:12
esbergluopenstack extension list --network19:12
edmondswefried but I think esberglu has sold me on just calling that CLI he mentioned, once I realized that CLI lists everything that is enabled in devstack19:12
esbergluIt lists all of the enabled extensions after stacking19:12
esbergluIt's how I generated the list in 554819:13
esbergluI'm just gonna do it each run now instead19:13
efriedOh, sure, perfect.19:13
efriedI thought we were going to have to hardcode something one way or the other.19:13
edmondswefried I did to, but nope... so I think we all agree now :)19:14
*** k0da has quit IRC19:36
*** jay1_ has joined #openstack-powervm19:52
*** edmondsw_ has joined #openstack-powervm19:53
*** edmondsw has quit IRC19:56
*** edmondsw has joined #openstack-powervm19:57
*** edmondsw_ has quit IRC19:59
*** jay1_ has quit IRC20:05
*** k0da has joined #openstack-powervm20:12
esbergluefried: Okay I'm at the point where I have a comma separated list of extensions and want to set api_extensions in tempest.conf20:17
esbergluProblem is that there are multiple api_extensions (for each service)20:18
esbergluKnow a good way to find the correct api_extensions line to replace?20:18
efriedslack me an example of the output20:18
esbergluI need to get the api_extensions line in the [network-features-enabled] section20:19
efriedesberglu And you want to do this from bash (as opposed to python)?20:19
esbergluefried: I was going to try it in bash unless it's way more difficult that way20:20
esbergluFor now I could just put a placeholder in our tempest.conf20:20
esbergluOn that line20:20
esbergluBut I'm trying to improve my bash so I wanted something better20:22
efriedesberglu See
esbergluefried: Oh I forgot that was in there. Thanks20:23
efriedesberglu Yahyoubetcha.20:23
*** thorst has quit IRC20:42
*** thorst has joined #openstack-powervm20:45
*** thorst has quit IRC20:49
*** svenkat has quit IRC20:54
*** thorst has joined #openstack-powervm21:00
*** smatzek has quit IRC21:09
efriedesberglu You can also look up `iniset` in the devstack libs.21:30
efriedesberglu Actually, devstack/inc/ini-config is full of useful config-related functions :)21:32
esbergluefried: Cool I'll take a look tomorrow. Was having too much fun nuking the skip list today. Just knocked out another 80 lines21:42
*** esberglu has quit IRC21:49
*** svenkat has joined #openstack-powervm21:52
*** kriskend_ has quit IRC21:54
*** kylek3h has quit IRC22:00
*** thorst has quit IRC22:02
*** burgerk has quit IRC22:11
*** k0da has quit IRC22:31
*** svenkat has quit IRC22:56
*** thorst has joined #openstack-powervm23:17
*** thorst has quit IRC23:21
efriededmondsw Are you interested in being added to all of my ksa changes?23:28
edmondswefried will try to look tomorrow23:30
edmondswI can replace self with efried :)23:30
efriedI'll just walk 'em and add you.23:30
efriedThere's not that many.23:30
edmondswmy +1 will help you with the keystone guys23:30
edmondswthey know me pretty well at this point :)23:30
edmondswunlike nova...23:31
efriededmondsw Done.23:31
efriedThey're getting to know me :)23:31
efriedBut definitely appreciate your reviews.23:31
*** edmondsw has quit IRC23:40
*** thorst has joined #openstack-powervm23:57

Generated by 2.15.3 by Marius Gedminas - find it at!