Earlier  
Posted Nick Remark
#openstack-nova - 2019-05-29
16:26:54 mriedem https://blueprints.launchpad.net/nova/+spec/hide-hypervisor-id-flavor-extra-spec
16:27:00 sean-k-mooney it was already there
16:27:06 mriedem yes it was
16:27:14 mriedem https://blueprints.launchpad.net/nova/+spec/add-kvm-hidden-feature
16:27:40 mriedem https://review.opendev.org/#/c/459753/18//COMMIT_MSG@14
16:28:03 mriedem so jay was +W on that change, but not this other one to allow the same thing for windows guests
16:28:06 mriedem which i don't understand
16:28:14 sean-k-mooney huh in that case i guess i dont know why we have not made it work for windows guests
16:28:42 sean-k-mooney i had under stood this was not sepcifcally for the nvida case but i guess it was
16:28:45 openstackgerrit Stephen Finucane proposed openstack/nova master: Add reno for removed cells v1 policies https://review.opendev.org/662031
16:30:48 mriedem that said i don't see any cern people around to rev that patch
16:30:49 mriedem or ovh people
16:31:07 mriedem amorin: you're ovh right? do you guys want to revive this? https://review.opendev.org/#/c/579897/
16:31:27 mriedem looks like Maciej and Piotr cared about it at one point
16:32:44 phillw on a not totally dissimilar topic, I was actually paying attention on my last C7 installation and it offers to install a compute instance. Am I correct in my reading that this is a nova instance?
16:33:14 mriedem C7 = centos7?
16:33:23 phillw yes, sorry
16:33:25 mriedem "it offers to install a compute instance. Am I correct in my reading that this is a nova instance?" no idea
16:33:34 jcosmao hi mriedem, i'll forward info to my teammate (i work at ovh also)
16:33:43 mriedem jcosmao: thanks
16:34:05 phillw mriedem: home work for me, then :)
16:34:14 mriedem just make tim do it
16:35:20 openstackgerrit Matt Riedemann proposed openstack/nova master: Refresh instance network info on deletion https://review.opendev.org/660761
16:39:01 openstackgerrit Stephen Finucane proposed openstack/nova master: hacking: Resolve E731 (do not assign a lambda expression, use a def) https://review.opendev.org/651554
16:39:02 openstackgerrit Stephen Finucane proposed openstack/nova master: hacking: Resolve E741 (ambiguous variable name) https://review.opendev.org/652103
16:39:02 openstackgerrit Stephen Finucane proposed openstack/nova master: hacking: Resolve W503 (line break occurred before a binary operator) https://review.opendev.org/651555
16:39:03 openstackgerrit Stephen Finucane proposed openstack/nova master: hacking: Resolve W605 (invalid escape sequence) https://review.opendev.org/652104
16:40:20 aspiers mriedem: does this look familiar to you? b'/home/zuul/src/opendev.org/openstack/nova/.tox/lower-constraints/lib/python3.6/site-packages/pymysql/cursors.py:167: Warning: (1831, "Duplicate index \'block_device_mapping_instance_uuid_virtual_name_device_name_idx\' defined on the table \'fjisjekoia.block_device_mapping\'. This is deprecated and will be disallowed in a future release.")'
16:40:40 aspiers seems completely unrelated to my patch which is failing in the gate
16:40:50 aspiers and I think I've seen it a few times in the last 24 hours
16:43:00 aspiers oh, that's just a warning
16:43:34 aspiers still trying to find the real issue in http://logs.openstack.org/66/661266/4/gate/openstack-tox-lower-constraints/7af4be7/job-output.txt.gz
16:43:42 aspiers I see a bunch of timeouts
16:45:26 openstackgerrit Merged openstack/os-vif stable/stein: Prevent "qbr" Linux Bridge from replying to ARP messages https://review.opendev.org/655678
16:47:06 kashyap aspiers: Remind me again, in 'os-traits' repo, what to do when 'tox' complains too long lines for a URL?
16:47:23 aspiers kashyap: isn't that just a warning?
16:47:36 aspiers if not, I guess # noqa or similar
16:48:05 kashyap aspiers: It moans an ERROR -- "E501 line too long (108 > 79 characters)"
16:48:28 kashyap aspiers: Before I go off shortly, I'm pushing the change. For convenience, I'm including a short "changelog" noting explicitly what I addressed
16:48:55 kashyap ... so that if you want to rebase on it tomm.
16:49:01 aspiers kashyap: http://flake8.pycqa.org/en/3.1.1/user/ignoring-errors.html#in-line-ignoring-errors
16:49:09 aspiers # noqa: E501
16:49:42 kashyap Right, thanks!
16:53:52 mriedem aspiers: that duplicate index thing is super old yes
17:05:10 aspiers mriedem: the failures are very similar to https://bugs.launchpad.net/nova/+bug/1823251, but without the InterfaceError
17:05:11 openstack Launchpad bug 1823251 in OpenStack Compute (nova) "Spike in TestNovaMigrationsMySQL.test_walk_versions/test_innodb_tables failures since April 1 2019 on limestone-regionone" [High,Confirmed]
17:06:12 aspiers I wonder if the InterfaceError is just one symptom of a timeout
17:06:24 aspiers My timeouts show stuff like IndexError: tuple index out of range
17:06:46 aspiers and 'sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.'
17:08:26 aspiers ah, that latter one looks similar to https://bugs.launchpad.net/nova/+bug/1793364
17:08:28 openstack Launchpad bug 1793364 in Manila "mysql db opportunistic unit tests timing out intermittently in the gate (bad thread switch?)" [Undecided,In progress] - Assigned to Goutham Pacha Ravi (gouthamr)
17:09:00 mriedem right
17:09:05 mriedem i've been down that road
17:10:41 aspiers I guess elastic recheck will tell me as much when the other gate jobs finish
17:11:20 openstackgerrit Kashyap Chamarthy proposed openstack/os-traits master: hw: cpu: Rework the directory layout; add missing traits https://review.opendev.org/655193
17:12:42 kashyap aspiers: When you get a moment, does the short change log address all things you want --^
17:12:50 aspiers kashyap: already looking at it
17:13:00 kashyap Thank you very much, sir.
17:14:06 kashyap aspiers: Yeah, I wondered, too. Just cargo-culted it.
17:15:04 aspiers +1
17:15:50 kashyap aspiers: Ah, thanks. My focus was in Gerrit, and I saw the "Update" pop-up (your comment). I was expecting a firm -1 :D
17:16:02 aspiers Oh ye of little faith :)
17:16:03 kashyap Okay, now I cook food
17:16:07 aspiers Good plan
17:35:27 ganso lyarwood, melwitt, dansmith: Hello! When you have a minute, could you please take a look at those backports that are missing just a final +2? https://review.opendev.org/#/c/652153 , https://review.opendev.org/#/c/658136 and https://review.opendev.org/#/c/661349 ? Thanks in advance! =)
17:35:30 ganso tonyb: thanks a lot =D
17:49:23 openstackgerrit melanie witt proposed openstack/nova master: Follow up for counting quota usage from placement https://review.opendev.org/662056
18:24:03 melwitt mriedem: replied to your comments on https://review.opendev.org/#/c/638073
18:24:22 melwitt and I dunno if you saw, but it looks like https://review.opendev.org/661391 fixes the novnc tests on the multi-cell job
18:36:34 openstackgerrit Artom Lifshitz proposed openstack/nova master: Run revert resize tests in nova-live-migration https://review.opendev.org/653498
18:36:34 openstackgerrit Artom Lifshitz proposed openstack/nova master: Revert resize: wait for events according to hybrid plug https://review.opendev.org/644881
18:36:35 openstackgerrit Artom Lifshitz proposed openstack/nova master: [DNM] use iptables in nova-multinode https://review.opendev.org/660782
18:37:07 artom mriedem, ^^ when you get some time, assuming unit tests pass (I've fixed all of them, normally). I think sean-k-mooney and I have finally figured it out.
18:37:49 artom The DNM patch is... optional? I'm not sure what we want to do upstream, but it's good to have it on top to show that both hybrid and normal plug work
18:47:53 sean-k-mooney the DNM patch change the job to use iptables. if we wanted to merge it we should add a second job that use iptable rather then changing multinode job to use it instead of the defualt contrack driver
18:49:11 konetzed will the scheduler honor setting ram_weight_multiplier as extra metadata on a host aggregate? The goal is just to have one host aggregate stack vs spread.
18:50:52 sean-k-mooney konetzed: i dont think so https://github.com/openstack/nova/blob/master/nova/scheduler/weights/ram.py
18:51:33 sean-k-mooney https://github.com/openstack/nova/blob/master/nova/scheduler/utils.py#L1089
18:51:43 melwitt konetzed: to do that, I think you'd have to set ram_weight_multiplier as desired in the nova.conf of the compute hosts that are a member of the host aggregate you want to stack vs spread
18:51:47 sean-k-mooney actully look like it might
18:52:11 melwitt ok, I didn't know that :\
18:52:45 sean-k-mooney neither did i i assume we broke that when we broke the allocation ratios
18:52:49 sean-k-mooney i guess not
18:53:42 sean-k-mooney its proably suppor fragile if the host is in two aggrates with different values
18:54:57 mriedem you can have per-aggregate weights
18:55:27 sean-k-mooney well from the code yes but if a host is in two aggrates and they have differnt values im not sure what we do
18:55:43 konetzed melwitt: sean-k-mooney: thanks for the quick answer.
18:55:54 mriedem https://docs.openstack.org/nova/latest/user/filter-scheduler.html#weights
18:56:00 mriedem "If more than one value is found for a host in aggregate metadata, the minimum value will be used."
18:56:02 mriedem depends on the weigher
18:56:05 mriedem but the docs are all tehre
18:56:06 mriedem *there
18:56:10 mriedem per-aggregate weights is new in stein
18:56:13 mriedem yikun added it
18:56:27 melwitt konetzed ^ updated answer :P sorry
18:57:12 konetzed mriedem: thanks. Looks like i need to update from Rocky ;)
19:26:34 mriedem melwitt: ack i'll get back to it in a bit
19:26:42 melwitt thanks
19:27:01 mriedem unrelated plug for a question about the first stable stein release for anyone that has input http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006617.html
19:27:11 mriedem otherwise i'll probably just punt and un-WIP the release patch

Earlier   Later