Earlier  
Posted Nick Remark
#openstack-nova - 2021-10-20
12:07:25 sean-k-mooney stephenfin: while your looking at gate issues https://review.opendev.org/c/openstack/nova/+/814036 also ill joing the ptg shortly
12:13:51 sean-k-mooney oh right we are currently utc +1
12:15:22 opendevreview Wenping Song proposed openstack/nova master: Cleanup guest process when vm evacuate failed and then deleted https://review.opendev.org/c/openstack/nova/+/814746
12:15:28 stephenfin sean-k-mooney: I don't think it's trying to start it. I think it's trying to _configure_ it
12:16:29 stephenfin bauzas: I'll miss the first 30 minutes of the PTG, unfortunately
12:16:42 bauzas stephenfin: OK, then I'll flip some topics
12:17:05 bauzas stephenfin: we'll start with gibi's topic about the tox usage
12:17:24 sean-k-mooney well i think stephen is interested in that
12:18:02 stephenfin yeah, I was going to say. I can miss it though. I think a few people understand the problem so I'm sure you'll settle on something sensible
12:18:41 sean-k-mooney stephenfin: im hoping py39 will become a required testing env for yoga
12:20:17 sean-k-mooney just an fyi so we will need to be able to test with that locally but ya we understand what you were tryign to do
12:22:25 gibi stephenfin: ok, so we have global context_manager objects one for the api db and one for the main db. So that is what gets dirty and leaking between tests
12:23:24 gibi do we have some special handling for them in a fixture we use for every test case so in general test cases are not interacting? And don't we use the same fixture in the db_sync tests for a reason?
12:28:51 stephenfin gibi: Sigh, all the DB tests are using NoDBTestCase, so we're not actually using the Database fixture https://github.com/openstack/nova/blob/master/nova/tests/fixtures/nova.py#L611-L617
12:29:31 stephenfin I still don't know why running other tests first fixes the issue though...
12:30:57 gibi hm, so the normal way to deal with these globals is the Database fixture but for explicit DB testing we dont use that fixture
12:32:22 stephenfin that's my understanding from a quick inspection, but I'm juggling many things today and haven't had time to investigate it properly yet /o\
12:32:35 stephenfin it does seem strange that DB tests would not use the DB fixture though
12:32:36 gibi I think we have a poison fixture that prevent us touching the DB from a NoDBTestCase but it does not hit for the db_sync tests
12:33:08 stephenfin hmm, true
12:39:46 gibi I'm lost in oslo_db / sqla I guess our poision specific for the way nova objects are accessing the db and it still allows our direct get_engine calls
12:50:36 bauzas reminder : nova sessions start in 10 mins
13:02:56 bauzas sessions start by now :)
13:03:12 bauzas if people wanna come => https://www.openstack.org/ptg/rooms/newton
13:53:23 stephenfin I assume we're on a break?
13:53:58 gibi yepp
13:54:05 gibi stephenfin: you joined for the break :D
13:54:11 stephenfin classic me
13:54:15 gibi :)
13:55:11 bauzas stephenfin: we basically NACK'd all your ideas while you were gone :p
13:55:19 bauzas terrible me
13:58:19 bauzas belmoreira: we have an issue with the interop session being discussed one hour later that conflicts the vncproxy discussion we were planning to have at 15:40pm
13:58:32 bauzas belmoreira: can we make the discussion start at 4pm ?
13:58:39 bauzas dang
13:59:01 bauzas belmoreira: I meant, can we discuss the vncproxy thing at 3pm ?
13:59:06 bauzas (UTC)
13:59:28 stephenfin bauzas: just another PTG so
13:59:29 stephenfin :)
13:59:36 belmoreira bauzas 3pm utc works for me. thanks
14:00:41 bauzas just hope melwitt can be present at this time
14:00:56 bauzas belmoreira: ack, will flip the sessions
14:11:49 bauzas stephenfin: we'll do neutron things until 3pm UTC
15:07:48 bauzas dansmith: are you available ? belmoreira is discussing about moving instances between projects and we're talking of os-chown
15:08:12 dansmith bauzas: not right this moment, but I can try to join soon
15:08:19 bauzas dansmith: cool, appreciated.
15:11:24 dansmith bauzas: actually, this next topic is something I have to stay for, so it'll be a bit yet
15:11:37 bauzas ok
15:11:47 bauzas no worries
15:14:35 dansmith bauzas: I'm here for 15 mins
15:14:49 bauzas ta
15:17:34 dansmith which line is the vnc proxy thing?
15:17:48 stephenfin dansmith: 394
15:18:02 dansmith ah, in the "after 3pm" thing
15:18:32 stephenfin yeah, I've lost track of how we're picking stuff/what we've covered :)
15:58:06 bauzas side note: Jabra Evolve 2 65 are terrible headsets for a day long wearing them
15:58:29 bauzas my ears are pretty done with it
15:58:59 bauzas stephenfin: yeah, we cherry-picked topics
15:59:24 bauzas I don't wanna move topics too much as it's also confusing
17:26:48 bauzas brinzhang: when you're up, tell me when you want to discuss the cyborg suspend/resume spec ? we can do this either this Thursday 1pm or Friday 1pm if that suits your TZ
17:27:48 bauzas for the moment, placing it at the top of the discussions we have left so it would be discuss this at 1pm, but we can punt it for later
17:28:40 bauzas to nova folks, I flipped topics so the agenda should reflect the first topics to discuss, starting at L357
#openstack-nova - 2021-10-21
00:22:54 brinzhang bauzas:hi, about the suspend/resume an accelerator instance feature, there is no spec, before we completed rebuild/evacuate, shelve/unshelve, I just want to continue
00:24:33 brinzhang bauzas: today, I am not sure that time(1pm) which is ok for me, but if possiable, I think I can, thanks
08:29:32 bauzas brinzhang: OK, then we'll start with your topic, but in case you're not around, I'll punt it until tomorrow
08:30:39 gibi morning Nova
10:09:43 sean-k-mooney for what its worth i think it make sense to proceed with suspend/resume for cyborg without a spec in the same way i hope to do the same for vdpa
10:10:29 sean-k-mooney its just the completion of the existing work which does nto really require much design work so i think specless blueprint and code review should be suffincet in both cases
10:18:11 gibi I'm ok with a specless bp too
12:11:50 bauzas reminder : nova sessions start in 50 mins on https://www.openstack.org/ptg/rooms/newton
12:15:46 bauzas sean-k-mooney: gibi: yup I agree with both of you but given brinzhang asked to discuss for it, let's wait until we do
12:31:44 gibi sure
12:37:33 tbarron bauzas: do you have a window (however large) when you are targeting the virtios topic? manila folks plan to discuss at 23:15 this morning (I know Lee is out of course)
12:37:40 frickler with virt_type=qemu on qemu>=5.2 (bullseye, jammy, centos-stream-8) instances (i.e. rss of the qemu process) seem to use 3x as much ram as the flavor allocates, has anyone seen this behaviour before? it is causing failures in devstack CI with things just going OOM
12:39:06 tbarron bauzas: 13:15 :)
12:39:30 tbarron which isn't morning for lots of people, I know
12:43:46 sean-k-mooney frickler: no but i do know that in qemu 6.0 the -m attibute is nolonger required when using mem-backing args
12:44:09 sean-k-mooney frickler: so in 5.2 where we were seeing libvirt use both way that was still required
12:45:35 sean-k-mooney frickler: actully that chang is in 6.1 https://wiki.qemu.org/ChangeLog/6.1#Memory_backends
12:46:10 sean-k-mooney frickler: so the qemu command line generated form the libvirt xml that i looked at before i think was correct so this sound like a qemu bug
12:57:31 bauzas tbarron: others, sorry was taking a bit of timeoff before we start
12:57:41 frickler sean-k-mooney: do you have some contact at qemu to push that to?
12:57:50 bauzas tbarron: not sure we'll have time to discuss about the Manila spec today
12:58:12 bauzas tbarron: we can start to discuss it for tomorrow 1pm (or later if you prefer)
12:58:37 sean-k-mooney frickler: good question kashyap: do you know who could help root cause this
12:59:02 kashyap What's the context? /me catches up. (In a meeting now)
12:59:04 sean-k-mooney kashyap: context is that qemu on debian seams to be using 2-3x the ram that is allocated to the vm
12:59:13 kashyap What version of QEMU?
12:59:16 sean-k-mooney 5.2
12:59:32 kashyap Fairly recent (Dec 2020)
12:59:52 sean-k-mooney kashyap: we are seeign this result in OOM issues in the ci hence frickler concern
12:59:56 tbarron bauzas: *bit* is right :D. 1300UTC tomorrow would be great, manila sessions don't start till 1400.
13:00:26 stephenfin I'll be 20/30 minutes late to the PTG sessions again today
13:00:46 kashyap frickler: Very odd; is this something sudden? I can check w/ the upstream, but before that, I'd need a bug (with proper details)
13:01:05 kashyap frickler: Oh, wait
13:01:26 kashyap frickler: virt_type=qemu is already deadly slow: as you might know it's not using any hardware acceleration
13:02:24 kashyap frickler: What is the host OS? (I'm assuming this is a nested env; i.e. the "host" is a level-1 guest. And the baremetal is some cloud-vendor provided)
13:02:39 bauzas nova sessions start by now, people can join with https://www.openstack.org/ptg/rooms/newton
13:02:57 kashyap frickler: I'd need these, to start with: QEMU version and the complete QEMU command-line of the guest. You'll find it here: /var/log/libvirt/qemu/instance-yyyyyyyy.log
13:04:54 bauzas tbarron: okay then let's discuss this at 1300UTC tomorrow
13:05:30 bauzas sean-k-mooney: joing

Earlier   Later