Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-03-06
15:20:18 mriedem yeah
15:20:19 efried yeah
15:20:20 efried whee
15:20:50 mriedem https://github.com/openstack-dev/devstack/blob/master/stackrc#L345
15:21:16 sean-k-mooney efried: i can mock up a quick test patch that ill pull in one of the ironic jobs and force it to use nova and ironcic client form source if iyou like
15:21:58 efried sean-k-mooney: If you have that at your fingertips, that would be great. It would take me a while to figure out.
15:22:48 sean-k-mooney efried: if you list a project in required-project and it auto adds it to LIBS_FROM_GIT and zuul follow the depends-on stuff to pull in the requried patches
15:23:06 sean-k-mooney efried: it should only take me a minute to create one
15:38:35 openstackgerrit Jose Castro Leon proposed openstack/nova master: Extend volume for libvirt network volumes (RBD) https://review.openstack.org/613039
15:39:24 openstackgerrit sean mooney proposed openstack/nova master: [DNM] tempest client testing jobs https://review.openstack.org/641421
15:39:37 sean-k-mooney efried: i think ^ will do what you want
15:40:42 efried ...
15:41:36 sean-k-mooney i proably should have also dropt the tox jobs but they are quick
15:41:41 efried sean-k-mooney: Cool. How is that pulling in the ironicclient patch?
15:42:17 sean-k-mooney it is based on your nova patch an your nova patch has a depends on
15:42:37 efried right, but I thought we established that the depends-on wasn't working?
15:42:57 sean-k-mooney so because i added the ironic client to the require projects it will pull it in when zuul prepares the git repos and add it ot devstack LIBS_FROM_GIT list
15:42:57 efried or is that magic instated by virtue of this having been done in .zuul.yaml?
15:43:05 efried okay, nice.
15:43:36 sean-k-mooney we should still check when it actully runs just to be sure but it should work
15:44:53 sean-k-mooney i might quickly resping to drop the tempest full and greade job too since i has not started in zuul yet
15:45:00 sean-k-mooney well its ther ebut no vms yet
15:45:09 efried sean-k-mooney: Thanks for doing that. I have plenty of work left to do on the code side, but if I can at least get it running, then I have a way to debug.
15:46:56 openstackgerrit sean mooney proposed openstack/nova master: [DNM] tempest client testing jobs https://review.openstack.org/641421
15:48:24 sean-k-mooney there we go i missed doce but that will be much more efficent
15:48:33 efried thanks sean-k-mooney
15:48:50 sean-k-mooney and no worries hopefully that works the way we want it too
15:49:44 sean-k-mooney if it does i can move those jobs into the experimental pipline or replace the current non voting jobs we have
15:49:59 mtreinish mriedem: hmm, well getting the time series graph took longer than I thought (I must be rusty): https://blog.kortar.org/wp-content/uploads/2019/03/v6_network_total-1.png
15:50:24 mtreinish we also must have dropped a test (or skip it in some configurations) which made the aggregation difficult after Sept 2018
15:50:50 mtreinish I also box and whiskered each individual test: https://blog.kortar.org/wp-content/uploads/2019/03/v6_network_scenario_run_times.png
15:51:07 mtreinish it's definitely way too slow
15:53:15 mriedem geez yeah
15:53:34 mriedem that aligns with the 2100 seconds i saw in that timed out job
15:53:51 mriedem so i posted https://review.openstack.org/#/c/641416/ as a short-term workaround for nova-next
15:54:51 mriedem i can't really decide if we should whitelist the scenario modules we care about in the nova-next job, because then new ones could be added and we'd miss them, but at the same time there is probably more we should blacklist
15:55:29 mriedem i remember the good old days when tempest took 45 minutes
15:55:35 mriedem the whole job
15:55:44 mtreinish man, that was a long time ago
15:55:45 dansmith stephenfin: can you answer my questions about the test assertions in this? https://review.openstack.org/#/c/624592
15:55:53 stephenfin dansmith: sure
15:55:56 mriedem granted, the gate was fubar'd on a weekly basis, but still
15:56:01 mriedem it was fubar'ed FAST
15:56:04 dansmith stephenfin: I was thinking it would be nice to merge another good chunk of those this cycle, but...
15:56:43 sean-k-mooney mriedem for what its work im hoping to get the os-vif gates down to that by droping the keystone and cinder apis test.
15:57:11 mtreinish keystone tests take like zero time
15:57:18 mtreinish dropping cinder will save a lot of time
15:57:45 mtreinish sean-k-mooney: if there is no integration between os-vif and cinder I was just disable cinder all together in those jobs
15:57:51 sean-k-mooney mtreinish: ya but os-vif is a lib that never talk to any other openstack service
15:57:53 mtreinish s/was/would/g
15:57:53 mriedem that's why i dropped the non-compute api tests from the nova-next job
15:58:08 sean-k-mooney mtreinish: yes im going ot
15:59:28 sean-k-mooney i think in the os-vif jobs i might keep the compute and networking api tests + the senario test for now and see what the job times look like
16:00:05 sean-k-mooney if they are under an hour ill be happy if i can get down to 45 mins or so even more so
16:02:11 mtreinish well if you disable cinder (not just blacklist the cinder api tests) it won't run a good chunk of the scenarios
16:02:37 mtreinish and those scenarios are individually among the slowest tests in a job
16:11:31 stephenfin dansmith: Done-zo https://review.openstack.org/#/c/624592/8
16:17:03 melwitt mriedem: ack, will fix. I think it's bc that patch changed things from counting instances => instance mappings, that test is probably only creating instance records and not mapping records
16:23:03 dansmith mriedem: probably need someone to make a call on breaking potentially n-net-only tests with this: https://review.openstack.org/#/c/624592
16:24:27 mriedem i know some of the converted privsep stuff is going untested because testing the privsep stuff is hard...
16:24:36 mriedem i remember wresting with trying to mock around that stuff at one point
16:24:38 mriedem i don't remember the details
16:24:49 mriedem *wrestling even
16:25:10 mriedem i'd rather not make that call today...
16:26:02 dansmith just seemed like some feature-y patches we could make independent progress on, and they were just refreshed, but.. I got stopped at the first one
16:27:00 sean-k-mooney dansmith: even in the nova-net case some of that code is likely dead code as os-vif will be used in most cases
16:28:05 dansmith sean-k-mooney: understand, but it's just hard to get on board with orphaning code with tests.. if it's dead code, then maybe we should remove it
16:28:10 mriedem in other fun news, when post live migration fails we don't set the instance to error status or reset the task_state to None apparently http://logs.openstack.org/43/635343/4/check/tempest-slow-py3/a2497ae/job-output.txt.gz#_2019-03-06_05_29_44_910801
16:28:18 sean-k-mooney the gateway code is likely still used
16:30:12 sean-k-mooney mriedem: ya i have seen that happen a few times
16:31:34 sean-k-mooney dansmith: by the way we were waiting mainly for cern to move to cellsv2 only before droping nova-networks
16:31:46 sean-k-mooney so can we drop it entirly in train?
16:31:59 dansmith sean-k-mooney: they're not fully off it, AFAIK
16:32:09 sean-k-mooney we are not going to froward port it to python3 im assuming
16:32:35 sean-k-mooney dansmith: ok we should check with them and see.
16:33:28 stephenfin There was a mail about this on openstack-discuss a few weeks back
16:33:52 stephenfin I recall they said they were planning to migrate *everything* to neutron, but I can't recall the timeline
16:34:13 dansmith yeah, that's been the plan for a while, I just haven't heard that they have
16:34:25 dansmith either way, removal is non-trivial so cern being off it isn't the only barrier :)
16:34:50 stephenfin Sounds like a challenge
16:35:24 stephenfin Does anyone know if config drives rely on the metadata service being up? I'm assuming 'nova-compute' handles stuff by itself but haven't dived too deep yet
16:35:35 melwitt mriedem: I have a osc-placement change up for a batch command for setting allocation ratios per aggregate in placement, if you're interested in reviewing https://review.openstack.org/640898
16:35:36 sean-k-mooney well i think we might be able to delegate some of the logic to os-vif in the interim
16:36:01 sean-k-mooney for example i want to pull the trusted vf stuff into a sriov plugin in os-vif
16:36:12 dansmith sean-k-mooney: if you think those gateway things are still used can you comment?
16:36:42 dansmith sean-k-mooney: I think there's also some default firewalling of nova services that still use a lot of the linux_net ip.* commands, right? like punching holes for nova-api, metadata, etc
16:42:50 sean-k-mooney dansmith: ya there is a bunch of firwalling stuff. i would prefer not to migrate that code to os-vif but we migth be able to clean it up abit
16:43:20 dansmith sean-k-mooney: yeah, not saying we should, I'm saying we shouldn't just be randomly dropping tests for stuff we convert to privsep because "it's hard" and "it might be only for n-net"
16:44:05 openstackgerrit melanie witt proposed openstack/nova master: Use instance mappings to count server group members https://review.openstack.org/638324
16:44:05 sean-k-mooney ill take a look and see if its used and ya.
16:44:57 sean-k-mooney i can take a look at some to the privisep changes and see if i can convert them or help if needed too
16:45:18 sean-k-mooney but that will be after ff
16:45:45 sean-k-mooney i am happy to work with stephen on paying donw that technical debt
16:46:50 dansmith I was just thinking that these feature-y patches might be a few easy wins to get in before FF, several were +2 already and just refreshed
16:46:55 dansmith but clearly I was wrong :)
16:47:49 sean-k-mooney actully they are more or less indepenate so maybe we can change the odering of some of the patches that dont drop tests/nova-net stuff
16:48:15 sean-k-mooney e.g. merge the stuff that is a driect port/obviously correct and deffer the rest
16:49:04 dansmith yep, I +W'd one above that first one
16:50:25 artom stephenfin, the config drive is independant of the metadata API
16:50:46 stephenfin artom: So put configuration in nova-compute?

Earlier   Later