Earlier  
Posted Nick Remark
#openstack-nova - 2019-08-08
18:29:53 sean-k-mooney and mriedem fixed it 6 days ago https://github.com/openstack/openstacksdk/commit/799bd0a773fb082c1a45262922d87630abc9bd30
18:48:06 mriedem yeah, would be nice to get that released, mordred ^
18:48:18 mriedem otherwise we should add a warnings filter to squash that noise from our test logs
18:49:05 mordred mriedem: I have a release request in the releaseteam queue
18:49:17 mordred mriedem: https://review.opendev.org/#/c/674660/
18:49:17 mriedem cool
18:56:50 efried mriedem: gate failures are killinme, any problem if I fast approve those two patches to add logs and skip the test?
18:59:02 mriedem efried: i'm assuming dansmith or melwitt could hit these? https://review.opendev.org/#/q/topic:bug/1839515+status:open
19:00:11 dansmith it hath been done
19:00:16 mriedem danke
19:00:39 efried thanks dansmith
19:03:53 mriedem should see this drop off once that skip merges http://status.openstack.org/elastic-recheck/#1839515
19:06:09 mriedem mordred: +1 on that release request - could have probably been 0.32.1 given the contents but not a big deal when you're <1.0.0
19:08:10 mordred mriedem: yeah - but numbers are cheap too :)
19:15:32 openstackgerrit sean mooney proposed openstack/nova master: [WIP:U] support pci numa affinity policies in flavor and image https://review.opendev.org/674072
19:17:06 tbachman mriedem: Ben Affleck in “The Accountant”
19:17:56 dansmith hah
19:19:09 mriedem tbachman: i thought of that movie too
19:19:13 tbachman heh
19:19:20 mriedem and my neighbor who won't make eye contact
19:19:21 mriedem and is a CPA
19:19:30 tbachman steer clear of them
19:56:51 mriedem lordy test_verify_created_server_ephemeral_disk sometimes takes 5 minutes
19:57:43 sean-k-mooney is that a functional test?
19:58:13 sean-k-mooney or i guess proably a tempest senario test given the lenght
19:58:15 mriedem tempest
19:58:19 mriedem it's not a scenario test, api test
19:58:29 mriedem should probably be a scenario test
19:58:38 sean-k-mooney or at least in the slow set
19:58:43 mriedem gmann: what do you think about dropping the --serial for running scenario tests serially in tempest-integrated-compute ?
19:58:57 mriedem looking at https://logs.opendev.org/78/658478/16/check/tempest-integrated-compute/33847ea/controller/logs/stackviz/#/stdin/timeline?test=tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_hotplug_nic there are only 2 scenario tests that get run
19:59:53 mriedem hmm, why aren't things like test_stamp_pattern and test_volume_boot_pattern running in there?
20:00:13 mriedem nvm
20:00:13 mriedem oh b/c it's marked slow
20:01:27 sean-k-mooney any tests that ssh into a vm shoudl be grouped under senario but ya i guess it could be filtered out
20:01:47 mriedem sean-k-mooney: that's the way things used to be long ago,
20:01:56 mriedem qa team enabled run_validation in api tests quite awhile ago,
20:02:02 mriedem so a lot of the api tests are also ssh'ing into guests
20:02:14 sean-k-mooney well run validation is different
20:02:23 sean-k-mooney in that its optional
20:02:23 mriedem run_validation == enable ssh
20:02:39 mriedem sure, but it's basically on by default in tempest runs in the gate
20:02:41 sean-k-mooney e.g the test shoudl still be runale without it
20:02:47 sean-k-mooney ya
20:04:28 mriedem we should probably disable ssh validation in the nova-next job
20:04:50 mriedem we already get that in tempest-full and tempest-slow
20:05:16 sean-k-mooney well its realy jsut intened to prevent race conditions
20:05:46 sean-k-mooney e.g. in senario tests it can help with cases were you need to wait for the guest os to start before you proceed with the test
20:05:55 mriedem i don't think we're talking about the same thing
20:06:17 sean-k-mooney that is what the validation was ortinglly for as far as i knew
20:06:18 mriedem are you thinking of the nova vif_plugging_* options?
20:06:26 sean-k-mooney no
20:06:54 mriedem tempest uses it for all kinds of shit https://github.com/openstack/tempest/search?q=CONF.run_validation&unscoped_q=CONF.run_validation
20:08:25 sean-k-mooney yes but if i rememebr correctly it was originally added to make test pause on server create until you could ssh in
20:09:15 sean-k-mooney this was need for running tempst against ironic clouds
20:09:20 donnyd is the lxc driver for nova still functional?
20:09:31 sean-k-mooney am kind of
20:09:40 sean-k-mooney it was broke for 2 years
20:09:46 sean-k-mooney and got fixed recnetly
20:10:00 sean-k-mooney as in like a month ago
20:10:14 sean-k-mooney but we have not ci so maybe?
20:10:44 donnyd I see someone asking about lxd on the ml and was going to ask if we could point them at lxc instead... but figured i should ask the state of it first
20:11:40 sean-k-mooney cannoical are stoping developing nova-lxd and i dont think tere was much of a comunity outside of them maintaining it
20:12:06 sean-k-mooney the nova libvirt/lxc backend has little use or testing as far as i know
20:13:02 mriedem i'd be surprised if the lxc driver didn't shit the bed under normal usage
20:13:12 donnyd LOL mriedem
20:13:34 sean-k-mooney donnyd: the reason it was broken for ~2years was we change the args to mount
20:13:36 mriedem honestly, i tried getting a ci job going for that thing years ago and something would fail during server delete and it would just snowball and fail everything
20:13:39 donnyd seriously, that made me laugh harder than I should have
20:13:43 mriedem nbd mount issues from what i remember
20:14:30 mriedem donnyd: we could easily get a simple ci job setup for it which just runs a simple create/delete server scenario
20:14:35 mriedem and see what explodes
20:14:45 donnyd I have seen a couple lxd requests come across the ml recently and was curious to the state of it.
20:15:02 mriedem since nova-lxd isn't in tree it's not really our concern
20:15:05 mriedem our == nova
20:15:14 donnyd yea, makes sense
20:15:31 mriedem but yeah, as soon as someone kills support for something everyone comes out of the weeds
20:15:33 donnyd rather point them to something in tree anyways
20:15:40 mriedem "i was just about to go production!"
20:15:49 sean-k-mooney for what its worth i do like lxc. and it would actully be nice for developement and testing
20:16:14 donnyd I use them all the time for statefully things
20:16:36 mriedem osc is still all lxc right?
20:16:42 mriedem it's kolla that uses docker?
20:16:45 donnyd I think OSA is
20:16:49 sean-k-mooney im a bad conter person and jsut use docker for statefull things because i now how it works and can bend it to my will
20:16:50 mriedem yeah sorry, osa
20:16:58 donnyd yea, kolla, 3O
20:17:00 sean-k-mooney mriedem: kolla use docker yes
20:17:14 sean-k-mooney and osa used to support lxc for contol plane
20:17:52 donnyd I am pretty sure it still uses lxc, but i am not an osa expert so don't beat me too badly if they switched to docker
20:17:58 sean-k-mooney so osa used to install the compute nodes to bare metal but allow you to install the controler services in lxc
20:19:43 donnyd It would be great if we could get our CI to use LXC... at least for my shabby little cloud. I could probably do more
20:21:08 sean-k-mooney the first intel nfv ci was interesting... it used docker(pre 1.0) with the lxc backend to spin up super privaldges contaienr with which we then ran devstack in
20:21:53 sean-k-mooney we got really good density but it was entirly custom hacking with ducktape and sting
20:22:25 donnyd well duct tape does work... just sayin
20:23:24 sean-k-mooney it allowed use to handel every patch to neuton and respond back in less then 2 hours on a singel server with 40 cores and 128GB of ram
20:24:18 sean-k-mooney our nova ci that used vms to 3-4 servers to do the same with kvm
20:24:25 donnyd yea osa still uses lxc
20:25:34 donnyd i have 520 core and 1.1tb of memory here and I can only do 120 instances for nodepool
20:26:47 sean-k-mooney your ram limited

Earlier   Later